Development Scope
Device and interface access
Connect to the controller interface of air compressors, water pumps and other equipment to read working conditions, accumulated working hours, maintenance counts and fault codes, and retain the original equipment control responsibilities.
Product business functions
Access working conditions, running hours and fault codes, and develop remote logs, parameter configurations, maintenance reminders and customer equipment files.
Platform and data connection
Combine the business link of device and controller → collection or routing gateway → 4G link → enterprise platform → after-sales and operation and maintenance, and define the device identity, data fields, update time, abnormal status and result confirmation method.
Exception handling and operational constraints
Remote parameters must be set with value ranges, effective conditions and operation records; equipment fault judgment is based on status and logs.
Data and Operational Workflow
Equipment status collection → Fault and operation record upload → Customer equipment files → After-sales positioning issues → Processing record archiving.
The device side, communication side and platform side retain necessary status and logs respectively. Project integration testing is checked with actual equipment data and execution results, and network connection status and business completion status are recorded separately.
Project Inputs
- Existing device models, interface and wiring diagrams, licensing agreements, data samples and available codes.
- Business processes and parameters: equipment fault codes, working condition fields, parameter permissions and after-sales processing processes.
- Target location, operator, SIM/APN, power supply, installation method and equipment size.
- Existing platform interfaces, user roles, development modules, number of prototypes and planned nodes.
Deliverables and Acceptance
| Deliverables | Delivery content | Verification method |
|---|---|---|
| product realization | Hardware design data, prototypes or existing equipment modification data involved in the project, as well as corresponding firmware and interfaces | Check the mapping between fault codes and on-site status. |
| Business integration testing | Data fields, status definitions, platform adaptation procedures and business integration testing records | Verify parameter modifications, read acknowledgments, and out-of-bounds rejections. |
| Version and test data | Target hardware and software versions, build or deployment instructions, parameter configurations and test logs | Test offline log saving, reconnection upload and device restart. |
First confirm the scope and key functions, then complete prototype or software development, system integration testing and stage acceptance. The acceptance conditions list the prototype, version, environment, duration and passing threshold; source code, design documents, third-party licenses, materials, traffic, cloud resources and on-site work are agreed separately.
Frequently Asked Questions
Can it be retrofitted without replacing the device's main controller?+
Priority can be given to evaluating external acquisition terminals or communication boards. The device needs to open interfaces and provide protocols; for internal states that cannot be read, the replenishable sensors and the actual visible data range should be determined first.
Can I entrust only some functions of the device remote operation and maintenance terminal?+
The device interface, terminal program, 4G communication and platform integration testing can be split based on the existing R&D foundation. Please provide existing information and target boundaries, first check "equipment fault codes, working condition fields, parameter permissions and after-sales processing procedures", and then clarify the deliverables and interface responsibilities of each module.
How are costs and cycle time assessed?+
Split the workload based on target devices, interfaces, existing data, and verification criteria. This project focuses on checking equipment fault codes, working condition fields, parameter permissions and after-sales processing procedures; when prototypes, on-site integration testing or third-party platform cooperation are required, the corresponding costs, prerequisites and nodes will be listed separately.
Online
Phone
WeChat
Top