Engineering guide
For instrument SDK integration, 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 |
|---|---|---|
| SDK wrapper | Agreed interfaces, error mapping and a calling example | Agree source, binary redistribution and third-party library scope |
| Drivers and environment | Target environment list, installation steps and exception records | List vendor drivers and support conditions separately and agree the provider |
| Integration and delivery | Records for calls, disconnections, exit and reconnection on the specified instrument | Assign responsibilities for licensing, instruments, calibration and on-site work |
What inputs are needed before starting?
The specified instrument, SDK and license terms, driver/firmware versions, target runtime and raw data samples. Check document versions and availability first and retain missing items as unresolved inputs.
How should delivery and acceptance be defined?
Run the minimal call sequence on the specified instrument and environment; retain identity, raw results, errors and reconnection records. Communication and SDK calls do not establish measurement validity or accuracy; record simulator and physical-device results separately.
Enterprises in Suzhou, 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