Traffic management

Cover of Current Practice and Developments in Concept of Operations across Road Agencies in Australia and New Zealand
Current Practice and Developments in Concept of Operations across Road Agencies in Australia and New Zealand
  • Publication no: AP-R553-17
  • ISBN: 978-1-925671-13-1
  • Published: 16 October 2017

Though network operations planning is growing, there is a perceived disconnect between those who work at the strategic end of the process and those involved in the tactical or operational day-to-day end.

Roles and responsibilities are not always clear and defined, feedback loops not always transparent, and stakeholders seem to have relatively low visibility of what goes on at each end of the process and the respective challenges faced by those people who operate the road network.

A Concept of Operations (ConOps) document would bridge the gap and provide a best practice resource for all those involved in network operations planning.

These guidelines do not attempt to give detailed instructions on developing a ConOps, rather they set out several principles to be considered in developing a ConOps.

  • Summary
  • 1. What is a Concept of Operations?
    • 1.1. Purpose
    • 1.2. Context
    • 1.3. Concept of Operations - Possible Examples
      • 1.3.1. Auckland:
      • 1.3.2. Victoria, Australia
    • 1.4. Network Operations Planning
      • 1.4.1. Context
      • 1.4.2. What is the Status of Network Operations Planning
  • 2. Developing a Concept of Operations
    • 2.1. Concept of Operations – Principles Summary
    • 2.2. Governance
      • 2.2.1. Benefits of Good Governance
      • 2.2.2. Current Examples of Governance
      • 2.2.3. Establishing a Governance Structure
      • 2.2.4. Governance Summary
    • 2.3. Stakeholder Engagement
      • 2.3.1. The Stakeholders
      • 2.3.2. Ownership
      • 2.3.3. Maintenance
      • 2.3.4. Engagement approach
      • 2.3.5. Participation Spectrum
      • 2.3.6. Ongoing considerations
      • 2.3.7. Stakeholder Engagement Conclusion
    • 2.4. Accountability, Roles and Responsibilities
      • 2.4.1. Accountability, Roles and Responsibilities – Program and Project Managers
    • 2.5. Defining Success and Measuring Performance
    • 2.6. The Customer (Road System User)
      • 2.6.1. ConOps – Road Users (Customers)
      • 2.6.2. Customer Information
      • 2.6.3. Level of Service – Network Operation Planning
      • 2.6.4. The Customer (Road System User) in the Centre
    • 2.7. Integrated Transport, Land-use and Road Safety Planning
      • 2.7.1. Guide to Traffic Management Part 4: Network Management
      • 2.7.2. Safe System in the Planning Process
      • 2.7.3. Assessment of Key Road Operator Actions to Support Automated Vehicles
    • 2.8. Integrated Management of the Transport System
      • 2.8.1. Core Linkages
    • 2.9. Enablers - People, Guidelines, Tools and Technology
  • 3. Conclusion
  • References
  • Appendix A Network Operations Planning in Australasia
  • A.1 Characteristics of Network Operations Planning
  • A.1.1 Existing Network Operation Plan resources
  • A.2 Network Operation Plan Adoption in Australasia
  • A.2.1 Stakeholder involvement
  • A.3 Structure of Network Operation Plans
  • A.3.1 Strategic Objectives
  • A.3.2 Road User Hierarchy
  • A.3.3 Operating Gap Analysis and Tactical Action Identification
  • A.3.4 Road Safety
  • A.3.5 Development and Evaluation of NOPs
  • A.4 Summary
  • A.5 Agencies Responsible for Network Operation Plan Development and Delivery
  • A.6 Movement and Place and Network Operations Planning Discussion
  • A.6.1 Description of Movement and Place
  • A.6.2 Movement and Place in Australasia
  • A.7 Network Operation Planning International Comparison