Requirements checklist
What to ask for when choosing software for sCADA system integrators.
A checklist built from how sCADA system integrators work, to print or save as a PDF and bring to any supplier meeting.
What the software should cover
Tick each one that matters to your business.
- Tag list and point count baseline
- Screen and alarm design tracker
- Point-to-point test log
- Server and hardware register
- Software licence and backup register
- Factory and site acceptance
- Support contracts and remote calls
Roles that need their own access
Who logs in, and what each person may see or change.
- For project managers
- For SCADA engineers
- For commissioning engineers
- For support engineers
- For account managers
Reports to ask for
Ask to see each one with your own sample data.
- I/O points quoted against points built, by project
- Loop check status by area and tester
- Sites whose last backup is older than your rule
- Licences, dongles and support contracts due for renewal
- Calls by site, category and age
- Engineering days booked against days quoted, by phase
- Switches, gateways and servers received and outstanding by site
Systems it may need to connect to
Note which ones you already run.
- Calendar
- Remote access tool links
- Accounting export
- SMS
Questions for any vendor
Put these to every supplier you are comparing.
- Can quotes be built from point counts?
- Does it connect to the live SCADA?
- How are point tests recorded?
- Where are licence keys kept?
- Can the system flag an old backup?
- Can support be billed by contract or per call?
- How would we start?
- How is the software priced?
Where the work usually breaks today
Circle the ones you recognise. They set the order of the project.
- The tag list changes after the quote
- Point-to-point tests are on spreadsheets
- Licences and keys are lost between jobs
- Remote support lacks the project file
- Site work hours overrun
Prefer to talk it through? See the sCADA system integrators page.