KEY TAKEAWAYS
- Define deliverables, dependencies and exclusions before quoting the project.
- Test data meaning and failure behaviour as well as the user interface.
- Make documentation, training and ownership part of technical acceptance.
In this resource
Define the project boundary before the bill of materials
The word turnkey is useful only when everyone understands what will be handed over. A monitoring dashboard, a control-system change and an electrical retrofit carry different engineering responsibilities. List the assets, interfaces, measurements and operating functions included in the project.
Also list exclusions and dependencies. The customer may provide network access or an installation window; another contractor may provide electrical panels or instruments. A shared responsibility matrix helps prevent those assumptions from becoming a commissioning delay.
Agree the design evidence
Before implementation, review the architecture, tag list, instrument ranges, communication paths and reporting definitions. For supervisory functions, describe permissions, alarm behaviour and the relationship between local control and the supervisory application.
Treat screenshots as an interface reference rather than a full specification. A screen can look complete while units, timestamps and failure behaviour remain undefined. Acceptance criteria need to describe the information and behaviour behind the screen.
Test normal, boundary and interrupted conditions
A representative test should compare selected readings and events with a known source. Check scaling, counters, quality flags, time alignment and the agreed report calculations. Record the inputs, expected result, observed result and person responsible for resolving a difference.
Include communication interruption and recovery tests where appropriate to the agreed design. Determine what is buffered, what is lost and how an operator recognises stale data. Carry out any control or electrical tests only under the site’s approved procedures and responsible engineering supervision.
Make handover an engineering deliverable
Collect the asset list, configuration references, operating instructions, backup responsibilities and a record of outstanding issues. Define where the customer receives credentials through an appropriate channel, and who owns ongoing administration.
Training should use the actual reporting and operating tasks the team will perform. Ask whether a new user can identify an offline instrument, understand a shift report and find the agreed support route. A sign-off is more useful when it points to this evidence than to a general statement that the system works.
Connect the checklist to the commercial agreement
Separate technical acceptance from warranty, support hours, response targets and future changes. Those commercial commitments need explicit agreement; the presence of a dashboard or a completed installation does not define them.
WhereFy engineering services can help structure a project around requirements, integration, validation and handover. Bring an equipment inventory and an initial problem statement to the discussion so the scope can be specific before the quotation is finalised.
Have a site-specific question about these ideas?
Discuss your application