Skip to main content
Zemerc
OMSOperate · Asset Integrity & Reliability

Obsolescence Management System

Will the stock outlast the exposure?

Obsolescence management across the asset lifecycle for physical items and for software, firmware, operating systems, licences and support agreements. The application governs manufacturer notices, cases, criticality and deterministic risk, equivalence, inventory exposure and lifetime-buy decisions, aligned with IEC 62402.

0
Canonical lifecycle states
0
Report families
0
Governed datasets
0
Business domains
Canonical lifecycle

Eight lifecycle states between active support and obsolescence

Obsolescence is not binary. An item may progress through several lifecycle conditions before discontinuation, so the lifecycle position is maintained as a governed state supported by verified evidence rather than as an informal status field.

Active
Lifecycle
Mature
Lifecycle
Declining
Demand
Not recommended
OEM monitoring
End of sale
Notices
Last-time buy
Lifetime buy
Discontinued
Inventory
Obsolete
Cases

Active. In production and fully supported, providing the baseline for subsequent lifecycle states.

How lifecycle status is determined

Lifecycle status is a conclusion derived from governed evidence.

Lifecycle status is derived from verified evidence. Superseded events cease to govern; verified events take effect from their effective date; the most severe in-force state determines the current position; and where no qualifying evidence exists, the status is reported as unknown rather than assumed active.

Verification queue

Ingested evidence remains pending until verified

New and imported lifecycle events enter a verification queue and do not affect status until checked against source evidence.

  • Only verified lifecycle events can change status
  • Superseded events cease to govern from their supersession point
  • Where no qualifying event exists, lifecycle status is reported as unknown rather than null or active
Reporting

Nineteen report families designed for defined business audiences

Executive and management; programme; risk and criticality; lifecycle intelligence; equivalence; installed base; inventory and planning; supplier intelligence; software and firmware; and programme-performance reports. Each states its intended audience, reporting basis and available output formats.

OMS report catalogue covering executive and management reporting, obsolescence programme, risk and criticality, lifecycle intelligence, equivalence, installed base, inventory and planning, supplier and manufacturer intelligence, software and firmware, and programme performance

A report is configured for scope and period, previewed, then generated as a numbered revision that can be issued.

  • Where-used analysis traces components through
    Bills of material to dependent installations, making exposure countable.
  • Physical and software assets follow
    The same lifecycle model so supportability can be assessed consistently across hardware, software, firmware and licences.
  • Aligned with IEC 62402
    The programme follows the structure of the obsolescence-management standard. Alignment is stated as alignment rather than certification.
Criticality and risk

Risk derived from governed evidence and configured rules

Criticality records the consequence of loss, while lifecycle position records the current supportability state. Deterministic risk combines the governed inputs so status changes when verified lifecycle evidence changes.

Safety critical
Production critical
Important
Standard
Active
Mature
Declining
End of sale
Medium
High
Critical
Critical
Medium
High
High
Critical
Low
Medium
High
High
Low
Low
Medium
High
Lifecycle position
Capability architecture

One obsolescence programme governing the installed base and resulting decisions

OMS navigation follows notices and cases through assets, assessments, inventory and supporting evidence.

  • The obsolescence programme

    Manufacturer product-change and discontinuation notices feed governed cases and verified lifecycle positions for affected items.

    • Cases
    • Notices
    • Notice intake
    • Lifecycle
    • OEM monitoring
  • Assets and installed base

    The installed-base hierarchy covers equipment, tags, items, product families, bills of material and installations, with where-used relationships showing dependency and exposure.

    • Hierarchy
    • Equipment
    • Tags
    • Items
    • Product families
    • BOMs
    • Installations
    • Where used
  • Assessments

    Equivalence supports qualified alternatives, criticality defines consequence, and deterministic risk combines governed inputs rather than relying on ad hoc scoring.

    • Equivalence
    • Criticality
    • Risk
  • Inventory and forecasts

    Stock, recorded demand, depletion forecasts and lifetime-buy decisions connect supportability analysis to procurement action.

    • Inventory
    • Demand
    • Forecasts
    • Lifetime buy
    • Exposure
  • Software and firmware

    Operating systems, firmware, licences and support agreements are governed within the same obsolescence model as physical items so software and hardware supportability are assessed consistently.

    • Software and firmware
    • Integrations
    • Integration health
  • Evidence and governance

    Documents, transmittals and technical records, with governance, configuration, reference data, metadata, data management and data quality beneath the programme.

    • Documents
    • Transmittals
    • Technical records
    • Governance
    • Reference data
    • Data quality
Two operating contexts

Screen engineering bills of material or manage the installed base

Project mode screens engineering bills of material before handover so obsolescence can be addressed while design options remain open. Operations mode manages installed-base supportability, inventory and equivalence decisions.

  • Project mode for engineering, procurement and package engineers
  • Operations mode for reliability, maintenance and materials
  • Field lookup for identifying installed equipment and supportability context
Programme controls and supporting records

Four governed rules determine lifecycle state

The governing lifecycle rules are stated explicitly in the application so the basis for each status decision remains visible.

  • Only verified events affect lifecycle state

    Ingested evidence does not affect lifecycle status until verified against its source. Rejected or unverified events are excluded from status determination.

  • Correction through governed revision, not erasure

    Superseded events stop governing. Corrections create replacement events without erasing prior evidence, preserving the event history behind lifecycle changes.

  • The most severe in-force lifecycle state governs

    Where multiple verified events are in force, the most severe lifecycle state governs, with ties resolved by effective date and verification chronology according to stated rules.

  • Unknown is an explicit lifecycle result

    Where no qualifying lifecycle event exists, status is reported as unknown rather than null or assumed active.

Also in OMS

More of what the application covers

  • Project mode for screening a bill of materials before handover
  • Operations mode for the installed base
  • Where-used across installations and bills of material
  • Equivalence assessment for qualified alternatives
  • Depletion forecasts against recorded demand
  • Supplier and manufacturer intelligence
  • Field lookup for identifying installed equipment and supportability context
  • Documents, transmittals and technical records as evidence
OMS

Review OMS using one of your installed bills of material.

Bring one bill of material and its manufacturer notices. The demonstration will show resulting lifecycle states, associated criticality and whether available stock covers the assessed exposure.