Integration scope worksheet

One row per machine or system. A row is ready to commit only when the system name, the version, the protocol and the released interface documentation are all present — three out of four is an assessed row, not a committed one.

Add a row

The four fields that decide a row

Nothing added yet. A row with only a name is still worth adding — it shows what the survey has to establish.

Why the version field matters

The same controller family can expose different registers between firmware versions, so a protocol name without a version is not yet an interface. This is the field most often left blank and most often responsible for a data point moving from committed to assessed.

The worksheet

Row status as it stands

Add at least one row, then summarise.

What this worksheet does not do

It does not commit an interface and it does not replace the survey. Where the controller is closed or the documentation cannot be released, the row stays assessed and the proposal prices a gateway, an added sensor or a controller change instead.

Send the completed worksheet with your equipment list and the integration assessment starts from your rows rather than from a blank sheet.