Engineering guide
For legacy device protocol inventory, map costs to work packages, deliverables and external inputs as shown below. This defines scope rather than a lump-sum price, fixed schedule, payment terms or default charging rules.
Work packages and deliverables
Swipe the table horizontally to view all columns.
| Work package | Deliverables to agree | External inputs and scope |
|---|---|---|
| Documentation inventory | Versions, interfaces, permissions and documentation gaps | Assign responsibility for document permissions and vendor support |
| Protocol checks | Raw messages, field definitions, unknowns and verification steps | Itemize sample devices, adapters and necessary test equipment |
| Integration assessment | Read-only scope, risks and subsequent work packages | Scope site work, gateway development, control writes and device modification separately |
What inputs are needed before starting?
Models and firmware, interface wiring, authorized protocol documentation, raw messages, site access and read-only scope. Check document versions and availability first and retain missing items as unresolved inputs.
How should delivery and acceptance be defined?
Trace each confirmed field to the device version, request, raw response and documentation; retain unknowns and exceptions explicitly. A protocol inventory does not include unauthorized command probing or establish compatibility with every device or firmware.
Enterprises in Ningbo, China, can submit these inputs for remote review. Agree prototype integration, sample shipment, site work and associated costs for the specific project.
Review the service scope and submit the project inputs before agreeing on development and delivery. Original Chinese service scope
Online
Phone
WeChat
Top