Equipment and source materials
Identify the owner of drawings, accessible backups and third-party device documentation. List items to be supplied and mark any missing project files before estimating investigation work.
WORKING TOGETHER
A project is easier to deliver when the boundaries are clear.
Start with the requirement, agree the responsibilities, and verify the work against a defined scope.
- 01
Define the problem
Tell us what the equipment does, what is available now and what needs to change.
- 02
Agree the boundaries
Confirm the platform, deliverables, exclusions, responsibilities and acceptance checks.
- 03
Develop & review
Build the scoped logic, screens and documentation, then review them against the agreed requirements.
- 04
Test & hand over
Carry out the agreed checks, resolve observations and hand over the specified project files and records.
Bring a clearer brief to the first discussion.
A plain-text checklist for hardware, required functions, project files and acceptance responsibilities. No upload or automatic submission.
Before development
- Confirm the equipment, platform and source materials.
- Agree functions, exclusions and deliverables.
- Define how changes will be reviewed.
- Identify test hardware and onsite responsibilities.
Before handover
- Review the scoped functions and outstanding observations.
- Confirm agreed engineering-file and document delivery.
- Separate commercial licences from development deliverables.
- Record commissioning boundaries and the next responsible person.
MAKE THE INTERFACES EXPLICIT
Know who supplies,
who reviews and who tests.
The scope should cover the people and dependencies around the code. This avoids discovering missing hardware, licences or test access at the end.
Change and review rounds
Record decisions against a project version. Explain whether a request corrects the agreed function or changes the scope; confirm its effect on files, tests, timing and price before proceeding.
Installed-equipment checks
Agree the authorised onsite person, hardware availability and the conditions under which actions can be checked. Offline screen or logic tests do not replace field wiring and equipment verification.
Files and ownership at handover
List editable projects, software versions, comments, tags, drawings and operation notes. Treat runtime licences, third-party restrictions and maintenance responsibilities as distinct deliverables.
REMOTE COLLABORATION
Develop remotely.
Validate responsibly.
Some development and review tasks can be carried out remotely. Safe physical operation still depends on the actual machine, access conditions and an authorised onsite person.
We agree who provides the equipment, who can operate it, which checks are required and when an issue must be handled on site. Remote connectivity is not a substitute for those responsibilities.
COMMON QUESTIONS
Clarify the practical details.
Can the work be developed remotely?
Development and review can be organised remotely where the available files and test arrangements make that practical. Physical commissioning requires an authorised onsite person, agreed access and application-specific safety checks.
Are editable project files included?
Editable engineering projects, comments, tag lists and other documents should be specified in the quotation. Proprietary components, existing third-party programs and licence restrictions must be considered separately.
Are SCADA or HMI runtime licences included?
Do not assume they are. Engineering services, the generated project and commercial runtime licences are different items; the quotation should list what is and is not included.
START WITH THE REQUIREMENT
Tell us what your
equipment needs to do.
A process description and an equipment list are a useful starting point.