Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
IEC 10164-2-95 amd1-1999 (2013) — State Management Function for OSI Systems Management
Technical overview of the amendment and consolidated edition defining state attributes and procedures for managed objects
The IEC 10164-2-95 amd1-1999 (2013) standard, part of the ISO/IEC 10164 series on Information Technology – Open Systems Interconnection – Systems Management, specifies the state management function. This function provides a consistent model for representing the operational condition of managed objects within an OSI environment. The 1999 amendment introduced significant enhancements, and the 2013 consolidated edition brings together the base specification and all amendments.
Scope and Purpose
The scope of IEC 10164-2-95 amd1-1999 (2013) is to define a set of state attributes and procedures that enable management applications to query and control the state of managed objects. The standard establishes a uniform state model applicable to any resource modelled as a managed object—whether hardware, software, or logical entities. The purpose is to achieve interoperability among implementations from different vendors by providing a common language for state representation.
The standard addresses both the static definition of state attributes and the dynamic behaviour of state transitions. It covers:
- Definition of state attributes and their allowed values.
- State transition rules and event generation.
- Relationships between state attributes.
- Use of state information for control and monitoring.
Tip: When applying this standard, ensure that all managed objects that manifest state information implement at least the mandatory state attributes. Refer to the GDMO (Guidelines for the Definition of Managed Objects) templates for correct attribute definitions.
Technical Requirements
State Attributes
As amended, the standard defines the following state attributes:
| Attribute | Values | Description |
|---|---|---|
| operationalState | enabled, disabled | Whether the resource can provide service (enabled) or is non-operational (disabled). |
| administrativeState | unlocked, locking, locked | Permissive state: unlocked allows use, locked prohibits use; locking indicates a transitional shutdown. |
| usageState | idle, active, busy | Capacity utilisation: idle means not in use, active means processing but not fully occupied, busy means at capacity. |
| standbyState | providingService, hotStandby, coldStandby | Added by Amd 1 to indicate the redundancy role of the resource. |
| availabilityStatus | inTest, failed, powerOff, offLine, offDuty, dependency, degraded, notInstalled, logFull, softwareLoad, unknown | Additional status information complementing operational and administrative states. |
| proceduralStatus | initialising, reportingTerminated, notInitialised | State of procedures relative to the management of the object. |
| controlStatus | subjectToTest, partOfServicesLocked, reservedForCapacity, reservedForControl | Used to indicate that the object is subject to specific control actions. |
The standard also defines the state transition diagram and the allowed transitions between values within an attribute and across attributes. The amendment refined these diagrams and clarified the semantics of transitional states such as locking in administrative state.
State Model and General Procedures
The state model is built on the following principles:
- Each managed object may have zero or more state attributes, but at least one should be supported.
- State changes shall generate notifications (state change events) to inform managing systems.
- The relationship between attributes is defined: e.g., an object cannot be “active” if its operational state is “disabled”.
Important: The 2013 consolidated edition aligns the state attribute definitions with the 1995 base specification and incorporates amendment 1:1999. Ensure you reference the exact version of the base standard (1995) when claiming conformance. The amendment 1:1999 is mandatory for full compliance to the 2013 edition.
Implementation Considerations
Implementing state management according to IEC 10164-2-95 amd1-1999 (2013) requires careful design of managed objects. The following aspects are critical:
- Mapping to GDMO: Each state attribute should be specified using the GDMO attribute templates. The standard provides references for attribute naming and syntax.
- State change notification: Implementers shall ensure that state transitions generate the appropriate
attributeValueChangeorstateChangenotifications as specified in the associated systems management standards (ISO/IEC 10164-5). - Consistency constraints: The implementation must enforce the logical consistency rules between state attributes (e.g., when administrativeState is “locked”, operationalState should reflect that).
- Extension: The standard allows for additional state attributes specific to a resource type, but they must not contradict the standard set.
Benefit: A well-defined state management model reduces complexity in network management systems and ensures predictable behaviour across multi-vendor environments.
Compliance and Conformance
Conformance to IEC 10164-2-95 amd1-1999 (2013) is claimed at two levels:
- Static conformance: The implementation shall support at least the mandatory state attributes and procedures as defined in the standard. Optional features must be declared in the Implementation Conformance Statement (ICS).
- Dynamic conformance: The behaviour of managed objects during state transitions shall match the defined state model. State change events shall be generated correctly.
Testing for conformance typically involves verifying:
- Correct representation of state attributes as per ASN.1 definitions.
- Generation of state change notifications under appropriate triggers.
- Adherence to transitional rules (e.g., from “unlocked” to “locking” before “locked”).
Caution: Non‑conformance to the state model can lead to interoperability failures. Always validate your implementation against the formal conformance test suites defined in ISO/IEC 10164-14 (if available).
References
The standard is part of a larger framework. Related documents include:
- ISO/IEC 7498-4: OSI Reference Model – Management Framework
- ISO/IEC 10164-1: Systems Management – Object Management Function
- ISO/IEC 10164-5: Event Report Management Function
- ISO/IEC 10165-4: Guidelines for the Definition of Managed Objects (GDMO)
Frequently Asked Questions
Q: What is the main purpose of IEC 10164-2-95 amd1-1999 (2013)?
A: It defines a standardised way to represent the operational, administrative, and usage states of managed objects in OSI systems management, facilitating interoperability and consistent management across different implementations.
A: It defines a standardised way to represent the operational, administrative, and usage states of managed objects in OSI systems management, facilitating interoperability and consistent management across different implementations.
Q: What are the key changes introduced by Amendment 1?
A: Amendment 1:1999 added new state attributes (standbyState, availabilityStatus, proceduralStatus, controlStatus) and clarified transition rules, aligning the state model with evolving requirements.
A: Amendment 1:1999 added new state attributes (standbyState, availabilityStatus, proceduralStatus, controlStatus) and clarified transition rules, aligning the state model with evolving requirements.
Q: How does this standard relate to GDMO?
A: The state attributes defined in this standard are typically specified using GDMO templates. The standard provides the ASN.1 definitions and behaviour rules that GDMO definitions reference.
A: The state attributes defined in this standard are typically specified using GDMO templates. The standard provides the ASN.1 definitions and behaviour rules that GDMO definitions reference.
Q: Is the 2013 edition the latest version?
A: As of this writing, the 2013 consolidated edition is the current version. Check with your national standards body for updates or amendments.
A: As of this writing, the 2013 consolidated edition is the current version. Check with your national standards body for updates or amendments.
© 2026 Technical Standards Publishing. All rights reserved.