HanweiSmart Gas

Search Hanwei Smart Gas

Products, solutions and technical guides

Hanwei Smart Gas

Home / Smart Gas Platform Planning & Integration

Smart Gas Platform Planning & Integration

Start with your operating task, available device data and responsible teams. Define the required records and interfaces, then confirm the software version and delivery scope for your project.

Platform Project Scope

Connect Information with Responsibility

Define the event data, review roles and retained records before selecting modules or interfaces.

  1. 1.Identify the event

    Event identity and the associated asset.

  2. 2.Review the signal

    Reviewed status and the reason for follow-up.

  3. 3.Arrange field response

    Assignment, action and work-order reference.

  4. 4.Verify and retain

    Outcome, verification and a traceable event history.

Conceptual review sequence, not a software screenshot. Available functions require project confirmation.

Answer Summary

This hub helps gas utilities and integrators define platform requirements before selecting software. Use the planning guides to separate field alarm functions, device connections, event review, operating responsibilities and reporting. These guides do not identify separate software models; available functions need version-specific 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.

Choose Your Planning Task

Gas Alarm System Planning

Plan the roles of gas detectors, local controllers, warning devices and remote monitoring before selecting a system configuration.

Gas Safety Operations Planning

Define operating responsibilities, record handovers and review requirements before choosing a gas safety platform configuration.

Requirements to review

Operational records for gas safety management

Use these topics to define the records your team needs. This is a requirements checklist, not a list of confirmed software modules. Functions and interfaces need version-specific documentation.

01

Monitoring Map

02

Alarm Classification

03

Device Status

04

Pressure Trend

05

Odorization Trend

06

Inspection Records

07

Response Workflow

Scope Methane and LDAR Records

For a proposed LDAR workflow, identify the alarm, location, inspection, repair and verification records your team needs. Confirm which records exist, who owns them and which interfaces the selected software actually supports.

Data availability and interfaces require project confirmation. Emissions accounting and verification follow the applicable methodology; alarm records alone do not establish an emissions reduction.

Review LDAR workflow requirements

From 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. 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. 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. 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. 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.