Concept of Operations (27)
Description:
In this building block, the lead RUC agency project team follows systems engineering principles to describe the RUC system in a single, high-level document called the concept of operations (ConOps). This document should be understandable even for those without a technical background. The ConOps is developed from the use cases (see System Needs Assessment building block), the RUC-enabling law, and any documents available from the research and planning stage, including the pilot system specification documents and the selection of preferred operational concept document. The ConOps serves as the background for the detailed specifications, including system requirements, interface specifications, and business rules. The ConOps includes both state and vendor components. If separate systems are used for the types of vehicles included in the enabling legislation (e.g., heavy-duty vs. passenger vehicles), a ConOps should be developed for each system.
Details:
Follow standard systems engineering procedures to create a ConOps, including the following:
- All mileage reporting concepts indicated by the law
- High-level systems architecture
- List of major system stakeholders
- Description of the usage scenarios
- List of major system failure modes
Primary Use:
Guide and introduce system specification documents (requirements, etc.).
Best Practices/Lessons Learned:
- Focus on readability by a nontechnical audience; everyone should understand the ConOps.
- Review other RUC ConOps documents as examples for how to compose the new one.
- Be thorough but reasonable. Attempt to describe all major functionality, but do not be so comprehensive that the document loses readability.
- Do not specify how functions are fulfilled. State what the system does, not how the system does it.
- Revise the ConOps when needed, including when developing specification documents and when aspects of the ConOps no longer accurately describe the system.
State Government Context and Assumptions:
The implementing RUC agency, following the assembly of the System Needs Assessment building block, completes this task.