Project fit & buying priorities
Public-service integrators, industry software vendors, facility operators and field-equipment buyers can assess the workflow, integration and ongoing support together. Operations should define tasks and exceptions, IT should validate interfaces and access, and procurement should compare complete configurations and service scope.
Rugged or hazardous-location naming alone does not qualify a device for fire exposure, life-safety control or high-temperature zones; follow project-approved use conditions.
From field action to a complete record
- 01Receive response task and site information
- 02View maps and equipment lists
- 03Record resource status and handover
- 04Return task and equipment-review results
System integration & delivery responsibilities
Use response job, site, equipment, resource status, handover, review as the integration checklist. Define field ownership, required values and exception handling. Complete one representative job from terminal to API and backend review before scaling to more teams or sites.
SOTEN supplies industrial terminals, modules and integration support. Project integrators own platforms, algorithms and delivery organization. Define recognition and capture use by project authorization and actual configuration.
Turn requirements into testable selection criteria
| Criterion | Confirm with the project team | Evidence to request |
|---|---|---|
| Use and configuration | Confirm capture methods, environment and operator interaction against the criteria above | Representative jobs, tags and peripheral list |
| Systems and interfaces | Service / dispatch / incident and work-order platforms application version, fields, SDKs and protocols | Installable software, API specification and test account |
| Operations and support | Actual shifts, power, network, mounting and spare-unit plan | Full-shift test, installation drawing and support responsibilities |
Product platforms to evaluate
Select a platform by workflow, then confirm the branch, operating-system version and modules. The suggestions below do not mean every option is included in every configuration.
H81
Field forms & system integrationMultifunction tablet for business forms and capture options; select the system platform and module combination.
View platform and configurations ↗
H101
Field maps & information viewingField-tablet option for maps, layers, forms and peripheral integration.
View platform and configurations ↗
T80
Field capture & equipment recordsField tablet platform; review modules and interfaces for mapping, capture or hazardous-location branches.
View platform and configurations ↗Pilot validation & procurement acceptance
Test glove use, offline maps, task handovers and equipment scans in safe drills without treating the result as fireground qualification.
- Operations: confirm completion, exception review and result retrieval against real workflows.
- IT / integration: verify fields, permissions, offline recovery and duplicate handling.
- Procurement / support: freeze the tested device, software and accessories, and agree delivery, spares and service terms.
Questions before the project starts
Can this connect to our existing system?
Service / dispatch / incident and work-order platforms are integration targets, subject to application compatibility, interface access and SDK validation. Share the software version, API specification and an anonymized workflow sample for a device pilot. Agree device supply, integration and rollout as explicit work packages.
What should we prepare before selecting pilot devices?
Provide forms, role permissions, image and location fields, peripherals and existing platform interfaces. Include deployment region, estimated quantity, project stage and intended rollout date to define candidate configurations and a test plan.
