The penalties for requirements that miss the true business needs are huge. At best the project takes longer than planned due to design and development on features that are not required. At worst, the factory runs for years suboptimally.
How do you systematise your requirements phase to ensure a high quality system, yet still allow for local standardisation?
This checklist is a list of questions to facilitate the requirements phase of a project. It allows a standard process, while remaining flexible to the method that requirements are documented.
- How should recipe values be managed? Should these be managed on the HMI, or on an external system?
- Is any synchronisation with other systems (ERP, MES) required?
- Are there requirements to send data to specialised devices (barcode scanners, label printers)
- What language should the application/documentation be in?
PS – I wrote about this in more detail in Control Engineering Magazine
Just enter your email below so I know where to send the download link for the requirements checklist.
As an added bonus, I’m also including 3 templates for requirements documentation from (S88, GAMP, and another integrator that has given permission)