Active Traffic Management System

The Vendor is required to provide knowledge, and capability to furnish, and operationally deploy a statewide Active Traffic Management System (ATMS).
- The system description must include:
• The ATMS and associated software that will be deployed
• Hosting configuration (on-premises, cloud, etc.)
• Server provisioning requirements and system resiliency approach
• Integration with systems
- In cases where an element is not supported by the ATMS solution, a statement of whether the element could be added through system customization with an estimate of time and expense.
- System Architecture Design Document (ADD) - Technical architecture of the proposed ATMS, including the system architecture diagram, component descriptions, hosting model, and failover and recovery design
- Data Dictionary and Entity Relationship Diagram (DD/ERD) - combined document describing all ATMS data entities, attributes, relationships, data types, and retention rules
- Integration Design Document—Design for each integration in Section 4.5, defining authentication, APIs, data flows, error handling, and failure modes
- System Security Plan (SSP)—Security controls, access management and user roles, encryption at rest and in transit, logging and audit approach, and compliance posture
- Regression Testing – Regression testing is the process of testing changes to computer programs to ensure the older programming still works with the new changes.
- Integration Testing – Integration testing is a software development process in which program units are combined and tested as groups in multiple ways. In this context, a unit is defined as the smallest testable part of an application. Integration testing can expose problems with the interfaces among program components before trouble occurs in real-world program execution.
- Functional Testing – Functional testing is primarily used to verify that software meets the business requirements of the end user. Typically, functional testing involves evaluating and comparing each software function with the business requirements. Software is tested by providing it with some related input so the output can be evaluated to see how it conforms, relates, or varies compared to its base requirements. Functional testing also checks the software for usability, such as ensuring that navigational functions work as required. Functional testing techniques typically include smoke testing, white box testing, black box testing, and unit testing.
- Performance Testing – Performance testing determines the speed or throughput of an application. This process can involve quantitative tests such as measuring the response time or the number of instructions per second at which a system functions. Qualitative attributes such as reliability, scalability and interoperability may also be evaluated. Performance testing is often done in conjunction with load testing.
- User Acceptance Testing – User acceptance testing (UAT) is the last phase of the software testing process. During UAT, actual software users test the software to make sure it can perform required tasks in real-world scenarios, according to specifications. UAT is one of the final and critical software project procedures that must occur before newly developed or customized software is deployed. UAT is also known as beta testing, application testing, or end user testing. In some cases, UAT may include piloting the software.
- Artificial Intelligence Use
• GenAI model name
• Product owner
• Product description (including purpose, functionality, and key characteristics)
• Use case or goal (e.g. Image recognition, natural language processing, text summarization)
• The intended information use (context for how information is used in the model) for the GenAI included in the proposal
• The geographical location of the tool
• How the Proposer monitors and audits the tool’s compliance on use restrictions, data restrictions, legal compliance (non-discriminatory outputs), and biases in the tool’s outputs.