IEEE 1362-1998

1362-1998 is a Concept of Operations (ConOps) document standard focused on computing and processing systems. It helps define how a system is expected to be used, who will use it, and what operational goals it should support before detailed design begins. As an active English-language standard, it is useful for teams that need a clear, shared operational view to guide requirements, planning, and later implementation decisions.

1362-1998 overview

This standard provides a structured way to describe the intended operation of a system in practical terms. In the context of computing and processing, a Concept of Operations document typically captures user needs, system boundaries, operational scenarios, and interactions between people, processes, and technical functions. 1362-1998 is therefore relevant when organizations want early agreement on how a system should work in use, not just how it will be built.

Typical use cases

1362-1998 is commonly used when preparing concept-level documentation for software-intensive systems, control applications, or other computing platforms where operations must be understood before development advances. It may support system acquisition, stakeholder reviews, and early lifecycle planning for teams that need to align on workflows, responsibilities, and expected behavior. The standard is especially helpful when multiple groups must coordinate around operational scenarios and define a shared baseline for the system concept.

Why this standard matters

For computing and processing projects, a clear ConOps can reduce misunderstandings that often lead to design rework, incomplete requirements, or mismatched expectations. 1362-1998 matters because it encourages a disciplined description of operational intent, which can improve consistency across procurement, development, verification, and acceptance activities. Using 1362-1998 as a reference can also help teams document assumptions more clearly and manage risk when systems must support defined operational roles and use conditions.

• Concept of operations structure
• Operational roles and responsibilities
• System boundaries and environment
• Usage scenarios and workflows
• Early requirements alignment