Equipment Management, Engineering Lifecycle, and Governance

The Industrial Equipment and Protection Management System is not a static list. Complete create, view, update, clone, and delete capabilities support the full lifecycle required to turn reusable reference content into approved site protection while retaining traceability.

Managed objects

Managed object	Typical management operations
Equipment definition	Create, inspect, search, clone, edit, version, export, and retire
Operational point	Add, describe, classify, edit, remove, and associate with equipment
Safety profile	Define and revise states, ranges, alarms, commands, prerequisites, and response
Protection entry	Create, associate, review, customize, activate, export, and retire
Operational asset	Instantiate from a versioned definition and maintain site-specific identity and bindings

The 13 equipment definitions supplied with the product are starter records within this system. They accelerate adoption but do not constrain the customer's managed inventory.

From reference definition to protected asset

Delivered equipment definition
        ↓
Customer point-map and limit review
        ↓
Approved site-specific definition
        ↓
Operational asset created from a versioned snapshot
        ↓
Traffic validation and monitored commissioning
        ↓
Approved enforcement
        ↓
Controlled review and revision

Figure — Engineering lifecycle from reference definition to protected and reviewed assets.

Complete management capability

Authorized users can:

• create equipment definitions and reusable protection entries;
• view complete equipment, point, safety, and protection details;
• search and filter by equipment identity, class, point, and protection purpose;
• update definitions as engineering knowledge changes;
• duplicate and adapt a reviewed definition for another device family or site;
• remove individual or selected entries with dependency awareness;
• export a reviewed library for controlled transfer, backup, or audit evidence;
• preserve the source definition and version used for an operational asset.

These capabilities are available through the product's management workspace, but the catalog itself does not depend on that workspace: the equipment inventory, profile model, protection coverage, and representative cases are documented in this chapter set for offline and printed review.

Definition and operational instance are separate

A library definition is reusable engineering knowledge. An operational asset is a site-specific application of that knowledge, with its own identity, network binding, approved limits, and effective protection posture.

When an asset is created, it receives a snapshot of the selected definition and its version. Later library edits do not silently change that deployed asset. An engineer can review the new definition, assess impact, and deliberately adopt it under change control.

Dependency-aware change

Equipment, points, safety profiles, and protections are related records. Management actions therefore expose their dependencies. Removing or revising an equipment entry is treated as an engineering change that may affect point profiles and linked protections, not as deletion of an isolated label.

Recommended approval records include:

Record	Why it matters
Equipment definition and version	Identifies the engineering baseline used
Point-map source	Connects the model to the approved device documentation
Limit and state approval	Shows who confirmed operational values
Command and prerequisite approval	Shows who authorized control behavior
Monitoring/enforcement decision	Records rollout posture and operational risk acceptance
Validation evidence	Demonstrates behavior against representative operations
Effective date and change reference	Supports audit and later investigation

Suggested responsibilities

Role	Primary responsibility
Operations	Confirm operating meaning, expected states, and switching practice
Protection and control engineering	Confirm point map, limits, sequences, interlocks, and relay context
OT security	Confirm network enforcement posture, logging, and evidence requirements
Asset owner	Approve applicability and production adoption
Change authority	Approve activation, revision, rollback, and retirement

The product does not force one organizational model; it provides the traceable content needed for the customer's existing management-of-change process.

Commissioning approach

1. Select or duplicate the closest delivered equipment definition.
2. Map every point to the approved device point list.
3. Replace generic labels with customer terminology where required.
4. Confirm units, scaling, permitted ranges, normal states, alarms, and critical limits.
5. Confirm approved commands, Select-Before-Operate, and plant prerequisites.
6. Review the generated baseline protections with operations and engineering.
7. Validate using representative normal, abnormal, and unauthorized-control cases.
8. Operate in monitoring posture where evidence is still being gathered.
9. Enable blocking only after the relevant customer approval.
10. Preserve the adopted version and validation evidence.

Scaling across sites

A reviewed definition can be reused across similar devices without losing local control. Corporate engineering can maintain common equipment families and minimum protections; individual sites can add approved point mappings, thresholds, and operating constraints. Versioned snapshots prevent central library maintenance from becoming an uncontrolled production change.

Operational boundary

Network-level protection adds visibility and an independent decision point, but does not replace relay protection, process interlocks, safety instrumented functions, equipment settings, switching orders, or trained operator authority. The library is designed to align network enforcement with those industrial controls and make deviations visible, reviewable, and—where approved—blockable.

Return to the Industrial Equipment and Protection Library.