Hanwei Smart Gas
Home / Platform
Platform
Bring connected gas safety information into a shared operating view: asset locations, alarm events, device status, inspection records and response progress. Functions and interfaces are scoped to the project.
Platform Project Scope
Connect Information with Responsibility
Define the event data, review roles and retained records before selecting modules or interfaces.
- 1.Identify the event
Event identity and the associated asset.
- 2.Review the signal
Reviewed status and the reason for follow-up.
- 3.Arrange field response
Assignment, action and work-order reference.
- 4.Verify and retain
Outcome, verification and a traceable event history.
Conceptual review sequence, not a software screenshot. Available functions require project confirmation.
Platform Value
The platform is the software and records layer, not a detector or a substitute for local protective functions. Review which field signals are available, who handles events and which inspection and response records your team needs to retain. Integration scope is confirmed project by project.
Platform view
Operational records for gas safety management
The platform value is to organize field signals, device status, inspection records and response steps so utility teams can review events with context.
Monitoring Map
Alarm Classification
Device Status
Pressure Trend
Odorization Trend
Inspection Records
Response Workflow
Methane and LDAR data support
The platform can connect alarm events, asset locations, inspection records, repair work orders and post-repair verification results, helping utilities build structured data for gas loss reduction and methane management.
Data availability and interfaces require project confirmation. Emissions accounting and verification follow the applicable methodology; alarm records alone do not establish an emissions reduction.
Explore LDAR workflow and MRV-ready data supportFrom an Alarm to a Reviewed Outcome
Use this illustrative workflow to define the data, people and records your project needs. It is not a software screenshot or a demonstration of delivered modules; interface support and workflow functions must be confirmed for the selected platform.
1.Identify the event
- Information needed
- Asset ID, location, event time and available detector or monitor readings.
- Operational review
- Check the reporting device and site context before interpreting the indication.
- Record to agree
- Event identity and the associated asset.
2.Review the signal
- Information needed
- Alarm category, device status, communication gaps and available trend history.
- Operational review
- Distinguish an alarm indication from a device or reporting fault; agree review responsibility.
- Record to agree
- Reviewed status and the reason for follow-up.
3.Arrange field response
- Information needed
- Responsible team, site access and the agreed operating procedure.
- Operational review
- Assign follow-up and track progress where the selected workflow supports it. Remote records do not replace local protective functions.
- Record to agree
- Assignment, action and work-order reference.
4.Verify and retain
- Information needed
- Field findings, repair details and post-repair verification where applicable.
- Operational review
- Review the outcome and retain the agreed records. A closed alarm alone is not proof of a repaired leak or an emissions reduction.
- Record to agree
- Outcome, verification and a traceable event history.