BACKGROUND

As agencies progress toward the next generation of traffic management systems (TMSs), new software that adds functions has to be implemented within TMSs. A TMS software could be modular or stand-alone, but has to be integrated within a software subsystem of TMSs. These software subsystems could use proprietary, commercial-off-the-shelf (COTS), open-source, or customized software or a combination produced by agency staff and external developers. Agencies will benefit from an understanding of options and best practices for designing, procuring, and managing software subsystems to address current and evolving needs of traffic management and TMS.

For this project, a software subsystem includes software programs that support the functions and services of the TMS and may share software products with the entire TMS and specific software programs installed for other subsystems or decision support tools. Assorted software programs and application programming interfaces (APIs) may be integrated into this overall software subsystem to carry out management and operating requirements. 

Limited resources exist to support identifying requirements and evaluating design options and different technologies (e.g., cloud, server, hybrid cloud, and server) or solutions (e.g., distributed, centrally managed) when contemplating or pursuing the integration or incorporation of new or evolving TMS software subsystems, programs, or applications and managing them. Research is needed to provide insights into and understanding of options and best practices for developing and managing requirements as well as planning, designing, procuring, evaluating, and maintaining TMS software subsystems, programs, and APIs.

OBJECTIVE 

The objective of this project is to develop a technical guide to manage the entire life cycle of software subsystems within a TMS for state departments of transportation (DOTs) and other agencies.

At a minimum, the technical guide will assist agencies in:

• Identifying needs, requirements, and issues when planning, designing, procuring, managing, and integrating a new software subsystem or upgrades to an existing or new TMS;
• Developing procedures and requirements for testing, accepting, and initializing the use of new software subsystems, programs, or APIs with existing or new TMS;
• Identifying issues (e.g., installation, modification, software security) to consider when deciding whether to procure or develop software (e.g., proprietary, COTS, open source) or APIs to integrate with existing TMS software; and 
• Identifying issues to consider when software subsystems or applications need to meet the current and evolving needs of a TMS.

Accomplishment of the project objective will require at least the following tasks.

List of Tasks

PHASE I

Task 1. Conduct interviews or surveys on current state DOT and industry practices to accomplish the project objective. Identify a list of practitioners for an in-depth interview or survey to gather information. The list of practitioners and interview/survey questions shall be approved by the NCHRP. Synthesize the practices and summarize the findings based on the interview/survey results as part of the Interim Report to be developed in Task 4. 

The in-depth interviews or surveys shall cover topics that agencies should consider when installing new software or upgrading an existing TMS with respect to:

• Needs, requirements, and issues to consider in planning, design, and procurement;
• A checklist to assess the capability and performance, including technical and other issues, of a TMS’s existing software subsystem, installed software programs, and APIs;
• Configuration, design, integration, procurement, and management issues when assessing the development, acquisition, or installation of a new software subsystem and software programs on a software subsystem;
• Requirements, methods, procedures, tools, and resources to test, accept, and initialize new software programs or APIs;
• Issues, requirements, data elements, testing, and acceptance criteria when deciding whether to
  • initialize new software programs or APIs,
  • integrate software programs or APIs into a TMS’s software subsystem, or
  • procure or develop software (e.g., proprietary, COTS, open source) or APIs;
• Configuration management plans, policies, procedures, tools, and practices in support of managing TMS software subsystems, programs, and APIs; and
• Staffing (e.g., knowledge, skills, abilities, position descriptions, level of effort, and staffing needs) and resource issues (e.g., services to contract) regarding maintaining, managing, and supporting the operations of a TMS’s software subsystem, software, and APIs.

Task 2. Develop a draft annotated outline for the technical guide to be developed in Task 5. The draft annotated outline is intended to provide the foundation, context, and framework for the subject matter to be included in the technical guide. It will include key technical and associated issues, major concepts, current practices, examples highlighting the lessons learned, and interview/survey results for consideration. 

At a minimum, the technical guide shall cover the following topics:

• TMS software subsystems and software;
• Different types of software (e.g., proprietary, COTS, open source);
• Linking agency constraints (e.g., budget, hardware, legacy systems) and TMS requirements for selecting types of software;
• Planning, designing, procuring, developing, implementing, testing, managing, using, and maintaining TMS software subsystems, software, and APIs;
• Integrating TMS software subsystems, software, and APIs (e.g., managing changes, using APIs to transmit data); and
• Services and options to meet the day-to-day needs of supporting software.

Task 3. Organize a virtual meeting with the NCHRP panel to review and obtain feedback on the draft annotated outline developed in Task 2. Revise the draft annotated outline based on written and oral feedback from the NCHRP panel meeting.

Task 4. Prepare an interim report documenting the findings of Tasks 1 through 3 and provide an updated work plan for the remainder of the research no later than 9 months after the subaward is awarded. The updated work plan must describe the methodology and rationale for the work proposed for Phase II. 

Note: Following a 1-month review of the interim report by the NCHRP panel, the research team will be required to meet with the NCHRP project panel in-person to discuss the interim report. Work on Phase II of the project will not begin until authorized by the NCHRP. Phase I budget shall not exceed $100,000.

PHASE II

Task 5. Execute the approved Phase II work. Develop a draft of the technical guide reflecting the final version of the annotated outline. Submit the draft technical guide to the NCHRP for review and approval. 

Task 6. Revise the draft technical guide based on comments from the NCHRP.

Task 7. Present the draft technical guide virtually to two appropriate technical committees, such as the American Association of State Highway and Transportation Officials (AASHTO) Committee on Transportation System Operations (CTSO) Intelligent Transportation Systems Workgroup and/or the Federal Highway Administration Transportation Management Center (TMC) Pooled-Fund Study (PFS) for comments and propose any revisions to the NCHRP panel. Finalize the draft technical guide after consideration of practitioners' feedback. 

Task 8. Develop a presentation (30-40 slides) with speaker notes reflecting the technical guide developed in Task 7. The presentation slides shall specify the research purpose, objective, key issues addressed, research products developed, and benefit or value of the research. 

Task 9. Prepare the final deliverables, including:

• A final technical guide to manage the entire life cycle of software subsystems within a TMS for state DOTs and other agencies;
• A final report documenting the research process; 
• A technical memorandum titled “Implementation of Research Findings and Products” (see Special Note J); and
• A presentation of the research findings and conclusions.

Note: The research plan may include additional deliverables and panel meetings via teleconferences. 

Note: Following receipt of the draft final deliverables, the remaining 3 months shall be for NCHRP review and comment and for research agency preparation of the final deliverables.

STATUS: The project panel will meet to select the prefered contractor.