As illustrated in the following diagram, requirements were organized into categories that match the major functions in the corridor management workflow:
The main categories (in blue) support these workflow functions:
| Function | Category of Requirements |
| People and organizations work together to manage, resource, fund, and maintain a working Integrated Corridor Management system that is accepted by all stakeholders. | Institutional Support |
| Stakeholders routinely plan, review, and update responses to incidents. | Strategic Incident Response Planning |
| Real-time corridor status information is continually monitored. | Corridor Monitoring |
| An incident is identified and characterized. | Real-Time Incident/Event Monitoring |
| Predefined response plan components and the current corridor state suggest tailored response plans. | Real-Time Response Planning |
| Once a response plan is chosen, it will then be implemented by corridor resources. | Response Plan Implementation |
These activities are further supported by four categories (in green) of crossing-cutting requirements:
| Function | Requirements |
| Day-to-day management of data used to support system operations | Data Management |
| Use of common algorithms and rules | Decision Support |
| Link systems and processes to enhance coordination; common presentation and use of data | System Integration |
| Ensuring the overall availability of a safe, secure working environment | System Management |