For example, a screen or application for the shop floor foreman should be designed for rapid data entry, while...
a reporting screen designed for a power user would have much more complexity. With roles defined, usability should be designed with the "end in mind." What reports and information are needed by the user to make a decision? What common tasks should be set up so the user can quickly address these issues? What scenarios and channels must the system support for this role?
A key part of this would be how to support administrative tasks by the business user. How easy will the software be to maintain and support RICE (i.e. Reports, Interfaces, Customizations and Extensions)?
Related Q&A from R "Ray" Wang
ERP systems are a large investment. In this expert response, find out how to estimate the ROI of ERP software, including payback periods and business...continue reading
Open source ERP software is a rapidly-growing technology, but deployments aren't always a success. In this expert response, learn some of the warning...continue reading
There are many questions to be considered when starting the ERP software selection process. Find out what questions you should ask when evaluating ...continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.