Attachment__G_Tech_Reqs_Matrix_-_Final_525-20_-_IBI_GROUP.xlsx
XLSX spreadsheet 308 KB Posted
- Attached to
- Competitive Selection OH|DOT52520-2
- Contract number
- DOT52520-2
- Issued by
- Ohio
About this file
This document appears to be a detailed technical requirements matrix for the Ohio Department of Transportation (ODOT) Advanced Transportation Management System (ATMS) Replacement Project. The document involves IBI Group as the primary technology vendor, with the project focused on developing a comprehensive integrated software platform called inSIGHT. The document outlines technical specifications for a state-level transportation management system that will interface with multiple existing systems and technologies across Ohio's transportation infrastructure.
The proposed system encompasses extensive capabilities including incident management, device control, road and weather condition reporting, lane closure reservation, traveler information dissemination, and integration with various external data sources like Waze, INRIX, and National Weather Service. The contract includes multiple deployment phases, with some functionalities to be implemented immediately (Day 1) and others planned for future implementation. Key technical requirements cover graphical user interfaces, data exchange protocols, device management for dynamic message signs, cameras, ramp meters, and variable speed limit signs, as well as robust security, reporting, and decision support features. The system is designed to support statewide traffic operations, incident response, traveler information, and infrastructure management across Ohio's transportation network.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 525-20.pdf | ||
| 525Pricing_-_IBI_GROUP.xlsx | XLSX spreadsheet | |
| 525-20-add6.pdf | ||
| ODOT_525-20_-_IBI_GROUP.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Disposition of Comments
| Document | Page | Comment | Dispostion | Addendum # |
| RFP | 7 | Prebid meeting date (day and date conflicted) revised to Thursday, June 13 | Revised by Addendum | 1 |
| Attachment G | General Reqs | In GEN-OM-08, "as per" reference was incorrect and revised to IT-HW-02. | Revised by Addendum | 2 |
| Attachment G | Data Reqs | In DATA-EXCH-24, "as per" reference contained a typo. Revised to "IT-GEN-05." | Revised by Addendum | 2 |
| RFP | 7, 23 | Proposal submission deadline extended to July 10, 2019. | Revised by Addendum | 2 |
| RFP | 26 | Revised resumes to be submitted in Attachment B: Vendor Qualifications and Experience Section | Revised by Addendum | 2 |
| Attachment G | IT Reqs | IT-OIT-07 changed to YEAR 1+ | Revised by Addendum | 3 |
| Attachment G | IT Reqs | IT-SEC-10 deleted so that all users require Microsft AD to access system per IT-SEC-09 | Revised by Addendum | 3 |
| RFP | 7 | Deadline to submit Prebid questions Revised to 2pm June 27, 2019. | Revised by Addendum | 4 |
| RFP | 11 | Added Source Code Escrow as an option | Revised by Addendum | 4 |
| Attachment G | Device Reqs | Dev-GEN-15 (initially Null) marked YEAR 1+ | Revised by Addendum | 5 |
| Attachment G | Device Reqs | DEV-VSL-24 (initially null) revised to YEAR 1+ | Revised by Addendum | 5 |
General Reqs Meets Requirement (via Configuration) w/ No Additional Development Meets Requirement w/ Additional Development Included in Bid Meets Requirement w/ Alternative Approach Does Not Meet Requirement
| Deployment Timeline | |||||||||||
| CAT | Sub | ||||||||||
| CAT | Req# | Requirement | Day 1 | Year 1 + | User Role(s) | Feature XREF | Service Bucket / Priorities | Bidder Approach | |||
| GENERAL REQUIREMENTS (GEN) | |||||||||||
| GEN | GUI | Graphical User Interface (GUI) | |||||||||
| GEN | GUI | 01 | The system shall provide a user interface through which users and administrators can access all system functionality. | ü | ü | The inSIGHT user interface (UI) provides access to all platform features and functions, including device and platform configuration. ITS device configuration views are accessible to authorized users via device list and management views, while all other configuration views (e.g. response rules and templates) are accessible via the main menu. Please refer to Attachment C (several sections) for details. | |||||
| GEN | GUI | 02 | The primary user interface must be web browser based. | ü | ü | The inSIGHT user interface (UI) is browser‑based, and has been developed using the latest widely adopted web technologies, approaches and frameworks, including HTML5, Angular and Responsive Design. Please refer to Attachment C, 'Section 2 - Browser-Based User Interface' for details. | |||||
| GEN | GUI | 03 | The user interface shall also provide a mobile application alternative for use on iOS and Android tablets and smart phones. | ü | ü | The inSIGHT user interface (UI) is browser‑based, and has been developed using the latest widely adopted web technologies, approaches and frameworks, including HTML5, Angular and CSS4, and supports several different device platforms, including Windows, Android and iOS workstations, and laptops and tablets, with a minimum recommended display resolution of 1280 x 900. Much more efficient and effective user workflows and interactions can be achieved with larger displays, and IBI Group chose not to sacrifice these workflows/interactions to have the inSIGHT UI also support devices with small displays (smart phones). |
IBI Group will work with ODOT to design and implement a Progressive Web App version of the inSIGHT UI, which can be effectively used on iOS and Android devices with smaller displays.
| GEN | GUI | 04 | The system shall provide a user-friendly, standardized method to manage installation and periodic update of each user interface. | ü | ü | IBI Group will implement a controlled and automated software release pipeline using Team City and Octopus Deploy, to simplify and streamline the software release (and rollback) process, while minimizing the potential for human error. | |
| GEN | GUI | 05 | The user interface shall allow for selection of actions and options using drop downs menus, trees, tables, etc. | ü | ü | The inSIGHT user interface (UI) allows for the selection of all devices and data objects (e.g. events) through both map and list based views, and wherever possible, allows for the selection of values from a configurable list, instead of requiring or allowing free-text entry. Please refer to Attachment C (several sections) for details. | |
| GEN | GUI | 06 | The user interface shall allow authorized users to manage the system configuration, such as templates, standard reports, and table data. | ü | ü | The inSIGHT user interface (UI) provides access to all platform features and functions, including device and platform configuration. ITS device configuration views are accessible to authorized users via device list and management views, while all other configuration views (e.g. response rules and templates) are accessible via the main menu. Please refer to Attachment C for details. | |
| GEN | GUI | 07 | The system shall allow authorized users to view all events, or to select filters to limit the events displayed. Examples of filters may be currently active, expired, future, event type, roadway, area, active dates, created date, event author, etc. | ü | ü | The inSIGHT user interface (UI) allows users to filter events based on type, status (active, planned / future), activation data (for planned / future events), and ownership. Please refer to Attachment C, 'Figure 8 - Event Map Filter'. | |
| GEN | GUI | 08 | The user interface shall stop the user from entering an event if the system identifies a “fatal” error in the data entry. The user interface shall inform the user of the error. An example may be that the user has not entered data that is required for an event entry. | ü | ü | The inSIGHT user interface (UI) does not allow users to save an event with any data entry errors, including missing mandatory data. The user is notified of any errors upon attempting to save the event. Please refer to Attachment C, 'Section 3.3.1 General' for details. | |
| GEN | GUI | 09 | The system shall have online contextual help to support operation, current with each update of functionality. For example, the solution may allow a user to hover over an icon, image, text or hyperlink and the solution may provide an alert containing information regarding the purpose and use of the targeted text, icon, etc. | ü | ü | The inSIGHT user interface (UI) has been designed to be highly intuitive, limiting the need for extensive contextual help. The UI does provide a mouseover content for all map icons, UI controls and menu items, containing information about the meaning or purpose of the item. | |
| GEN | GUI | 10 | The contextual help tool may be user-editable and configurable by an authorized user. | ü | ü | IBI Group will work with ODOT to enhance the inSIGHT user interface (UI) to support the configuration of contextual help items, as deemed beneficial / appropriate by ODOT. | |
| GEN | GUI | 11 | The user interface shall allow users to customize and save workstation views to be used in subsequent sessions. | ü | ü | The inSIGHT user interface (UI) allows users to name/label and save custom map views, which can be accessed in subsequent sessions, and (optionally) shared with other users. These views incorporate map centroid, zoom level, and enabled/displayed map layers, including devices, events and other information layers (e.g. county boundaries). Please refer to Attachment C, 'Section 2.1 Map View' for details. | |
| GEN | GUI | 12 | The user interface shall be capable of displaying and differentiating devices using standardized, easily recognizable, and colored icons. Furthermore, device types shall also have color schemes to allow easy visual identification of each device type (e.g., DMS one color, Portable DMS another color, etc...) | ü | ü | The inSIGHT user interface (UI), for each map layer, depicts data objects as an icon (e.g. field devices, traffic events), or as a roadway segment overlay (e.g. traffic conditions, queues). The icons and roadway overlays are designed specifically to draw the user’s attention to, and quickly convey, key characteristics / details. The iconography design combines color schemes, pictogram design, orientation to roadway, and badges to achieve highly intuitive visual encoding, thereby minimizing user cognitive load. For field devices, icons distinguish between online, offline, device failure states (communication or other), and device type specific operational states. Please refer to Attachment C, 'Section 2.2 Iconography and Roadway Overlays' (and several other sections) for details. | |
| GEN | GUI | 13 | The user interface shall have an administrator interface to allow the administrator to edit field device information in the ATMS. | ü | ü | The inSIGHT user interface (UI) provides access to all platform features and functions, including device and system configuration. ITS device configuration views are accessible to authorized users via device list views and map icons, while all other configuration views (e.g. response rules and templates) are accessible via the main menu. Please refer to Attachment C (several sections) for details. | |
| GEN | GUI | 14 | The administrator user interface shall allow the administrator to add a new device using a new device template and or default settings for a given device type. | ü | ü | The inSIGHT user interface (UI) provides access to all platform features and functions, including device and system configuration. ITS device configuration views are accessible to authorized users via device list views and map icons. These views support adding and modifying devices, using a combination of free text entry and configurable / selectable values and templates. For example, a single display format template is configured for a group of DMS with the same display characteristics (e.g. dimensions, color depth, etc.), and selected in the configuration of each relevant DMS, such that they need not be re-entered for each DMS. Please refer to Attachment C, 'Section 4.9 Configuration' for a representative example (DMS). | |
| GEN | GUI | 15 | The user interface shall display device information when an existing device is selected by the user. | ü | ü | The inSIGHT user interface (UI) displays device information / details when a device is selected. When users hover over a map device icon, the device's subtype, ID, name and location are displayed in a mouseover, and when users select device properties via device list views or map icons, a device properties view is displayed, with detailed device state, status and properties information. Please refer to Attachment C (several sections) for details. | |
| GEN | GUI | 16 | The administrative user interface shall allow users to select a device from a table or list to control the device, expose the device details, enter/edit the device data and obtain information being transmitted by a field device (e.g., DMS messages). | ü | ü | The inSIGHT user interface (UI) allows authorized users to select a device via list based views or map icons, to open a device properties view that displays detailed device state, status and properties information. These views present the real-time information provided by the device, and support device control (if applicable). For DMS, the view also presents the current message displayed on the DMS, along with all messages that have been inserted into the sign's message queue, along with their source and priority level. Please refer to Attachment C, 'Section 4.2 Properties View' for a representative example (DMS). | |
| GEN | GUI | 17 | The user interface shall allow users to select a device by clicking on a representative icon from the system map to control the device, expose the device details, enter / edit the device data and obtain information being transmitted by a field device (e.g., DMS messages). | ü | ü | The inSIGHT user interface (UI) allows authorized users to select a device via list based views or map icons, to open a device properties view that displays detailed device state, status and properties information. These views present the real-time information provided by the device, and support device control (if applicable). For DMS, the view also presents the current message displayed on the DMS, along with all messages that have been inserted into the sign's message queue, along with their source and priority level. Please refer to Attachment C, 'Section 4.2 Properties View' for a representative example (DMS). | |
| GEN | GUI | 18 | The system shall have an automatic spell check function for all user data entry. | ü | ü | The inSIGHT user interface (UI) includes a spell check for relevant free text entry fields. For example, this includes the text entry fields used to (optionally) edit auto-generated message text for distribution via HAR, Email, API and SMS. Please refer to Attachment C, Section 3.2 Response Management' for a representative example. | |
| GEN | GUI | 19 | The user interface shall allow authorized users to configure and view dashboards that display transportation network performance information. | ü | ü | IBI Group will work with ODOT to design and build into the inSIGHT UI, dashboards providing transportation network performance information. IBI Group could (alternatively) provide a separate, existing IBI Group dashboard product, which is entirely user configurable. | |
| GEN | GUI | 20 | The system shall have a geographically accurate display map of all roads in the state for display purposes approved by the ODOT GIS Section. It is preferred the map will come from a cloud-based source. All ITS elements, events and other data should be able to be overlaid on this map in layers. Map management functions must support map data creation and management, including updates to any existing mapping. | ü | ü | The inSIGHT user interface (UI) includes a geographically accurate display map of all roads, which is provided by a cloud-based source (Google Maps). All ITS elements are overlaid on the map in layers, as per the system configuration. Please refer to Attachment C, 'Section 2.1 Map View' and 'Section 2.2 Iconography and Roadway Overlays' for details. | |
| GEN | GUI | 21 | The system shall provide the capability to add and configure GIS map services such as JSON, GeoJSON, and be able to spatially integrate disparate data sets. | ü | ü | The inSIGHT user interface (UI) includes the ability to integrate GIS map services for the purpose of displaying additional map information layers than can be toggled on and off. Please refer to Attachment C, 'Section 2.1 Map View' for details. | |
| GEN | GUI | 22 | The responder shall work with the ODOT project manager to manage any necessary changes to the roadway segmentation and properties. | ü | ü | IBI Group will work with ODOT to implement any required roadway network configuration changes. | |
| GEN | GUI | 23 | The system shall be capable of displaying additional or third party data features, such as other states' 511 data. Where possible and appropriate, third party data shall be conflated with the ODOT's roadway network (e.g., INRIX and Waze data). | ü | ü | inSIGHT includes the ability to ingest events and alerts from external sources (i.e. other agencies, CAD, Waze, etc.), and present them to inSIGHT users for review, confirmation/promotion and response management. Please refer to Attachment C, 'Section 2.3 Notifications and Alerts' and 'Section 3.5 External Events Management' for details. | |
| GEN | GUI | 24 | The base map shall display unique features using standard, easily identifiable icons. | ü | ü | The inSIGHT user interface (UI) includes the ability to integrate GIS map data for the purpose of displaying additional map information layers than can be toggled on and off. IBI Group will work with ODOT to select the specific static icons / markers used for these information layers. Please refer to Attachment C, 'Section 2.1 Map View' and 'Section 2.2 Iconography and Roadway Overlays' for details. | |
| GEN | GUI | 25 | The display map shall display icons for static features, to include at a minimum: |
- Icons
- Reference (Mile) Markers
- Exit Numbers
- Lane configurations
| - Ramp Lane Configurations | ü | ü | The inSIGHT user interface (UI) includes the ability to integrate GIS map data for the purpose of displaying additional map information layers than can be toggled on and off. IBI Group will work with ODOT to select the specific static icons / markers used for these information layers. Please refer to Attachment C, 'Section 2.1 Map View' and 'Section 2.2 Iconography and Roadway Overlays' for details. | ||||||
| GEN | GUI | 26 | The map shall be able to display data thematically based on its attributes. Themes and attribute thresholds shall be configurable by administrators. Examples include coloring roadway segments based on speeds, coloring device icons based on device status, etc. | ü | ü | The inSIGHT user interface (UI) includes the ability to display traffic conditions reported by ITS roadway infrastructure and external data sources as roadway segment overlays on the map, indicating the current speed, volume or occupancy. The color scheme and data thresholds used in rendering these overlays are configurable. Please refer to Attachment C, 'Section 2.1 Map View' and 'Section 2.2 Iconography and Roadway Overlays' for details. | |||
| GEN | GUI | 27 | The system shall include a method of managing icon density at various zoom levels, such as clustering or a similar technique. | ü | ü | The inSIGHT user interface (UI) manages icon density through using smaller icons for devices, external events, and alerts at lower zoom levels, and (optionally) using Google Maps icon clustering for one or more map layers. Please refer to Attachment C, 'Section 2.1 Map View' for details. | |||
| GEN | GUI | 28 | The display map shall allow users to size and navigate maps without restriction on range. It shall include the ability to store and recall user configurable preset views location, zoom level, and visible layers) and location bookmarks. | ü | ü | The inSIGHT user interface (UI) map (Google Maps) allows users to size and navigate without restriction on range. The UI allows users to name/label and save custom map views, which can be accessed in subsequent sessions, and (optionally) by other users. These views incorporate map centroid, zoom level, and enabled/displayed map layers, including devices, events and other information layers (e.g. county boundaries). Please refer to Attachment C, 'Section 2.1 Map View' for details. | |||
| GEN | GUI | 29 | The display map shall include intuitive map navigation controls. | ü | ü | The inSIGHT user interface (UI) map (Google Maps) includes intuitive map navigation controls. | |||
| GEN | GUI | 30 | The display map shall show dual direction highways and directionality of travel if appropriate and when zoomed in to the appropriate level. | ü | ü | The inSIGHT user interface (UI) map (Google Maps) shows dual direction highways and directionality of travel when zoomed in to the appropriate level. | |||
| GEN | GUI | 31 | The display map shall have a distance measurement tool. | ü | ü | inSIGHT user interface (UI) map view will be updated to include a distance measurement tool. | |||
| GEN | GUI | 32 | The display map should have a search tool (points of interest, routes, layers, events) | ü | ü | The inSIGHT user interface (UI) includes a map search tool, which can be used to search for points of interest, reference markers, intersections, addresses, street names and lat/long coordinates (e.g. 39.9612, -82.9988). The map search tool can also be (optionally) configured to search for devices and events. Please refer to Attachment C, 'Section 2.1 Map View' for details. | |||
| GEN | GUI | 32 | The display map shall be searchable on any feature or device attribute exposed to the map, including the following attributes at a minimum: |
- Reference (mile) marker
- Intersection
- Address
- Street Name
- Lat & Long Coordinates
| - Device Name/ID | ü | ü | The inSIGHT user interface (UI) includes a map search tool, which can be used to search for points of interest, reference markers, intersections, addresses, street names and lat/long coordinates (e.g. 39.9612, -82.9988). The map search tool can also be (optionally) configured to search for devices and events. Please refer to Attachment C, 'Section 2.1 Map View' for details. | |||||
| GEN | GUI | 33 | Map elements shall have refresh periods appropriate for that element. For example, sensor data is refreshed every 20 seconds, and NWS data is refreshed every 5 minutes. Refresh rates may also be automatically adjusted based on automatically detected connection speed. Refresh rates may also be adjusted via administrative configuration. | ü | ü | The inSIGHT user interface (UI) receives asynchronous updates from inSIGHT back-end services in real-time, to ensure that inSIGHT users are always presented with the latest information. All data refresh periods are configurable at the inSIGHT back-end service level. | ||
| GEN | GUI | 34 | The system shall incorporate a variety of base maps such as Google, OpenStreetMap, imagery, ESRI, ODOT base map, etc. so that users can switch between different base map views. | ü | ü | The inSIGHT user interface (UI) incorporates the Google Maps API, which supports the display of other base maps as layers that users can switch between. Google satellite and terrain layers can be enabled, along with any base map that is supported by the Google ImageMapType, including both ESRI/ArcGIS and OpenSteetMap. Please refer to Attachment C, 'Section 2.1 Map View' for details. | ||
| GEN | GUI | 35 | The display map shall utilize a dual direction and ramp representation for events and resources. | ü | ü | The inSIGHT user interface (UI) utilizing a dual direction and ramp representation for events and resources. | ||
| GEN | GUI | 36 | The display map shall use attributes to represent lane level events and resources. | ü | ü | The inSIGHT user interface (UI) uses key attributes to present lane level events and resources. Please refer to Attachment C, 'Section 2.2 Iconography and Roadway Overlays' for details. | ||
| GEN | GUI | 37 | The display map shall use on-highway and cross street names. | ü | ü | The inSIGHT user interface (UI) map (Google Maps) uses on-highway and cross street names. The higher the zoom level, the more street names are displayed (including minor streets). | ||
| GEN | GUI | 38 | The system shall place events and resources at their actual location on the map. | ü | ü | The inSIGHT user interface (UI) places events and resources at their actual (lat/long) location on the map. Please refer to Attachment C, 'Section 2.2 Iconography and Roadway Overlays' for details. | ||
| GEN | GUI | 39 | The system shall provide the ability to identify concurrent highways and enclosing jurisdictional areas for a given point or segment. | ü | ü | The inSIGHT user interface (UI) provides the ability to identify concurrent highways and enclosing jurisdictional areas for a given point or segment. Please refer to Attachment C, 'Section 3.1 Event Creation' for a representative example. | ||
| GEN | GUI | 40 | The system shall provide capabilities to enter and manage ITS devices and integrate these with ODOT's GIS system. | ü | ü | The inSIGHT user interface (UI) provides access to all platform features and functions, including device and system configuration. ITS device configuration views are accessible to authorized users via device list views and map icons, while all other configuration views (e.g. response rules and templates) are accessible via the main menu. Please refer to Attachment C (several sections) for details. |
inSIGHT also includes an External Web API (REST/JSON) that can be used to provide device configuration, state and status information to external systems. Please refer to Attachment C, 'Section 16 External Web API' for details.
GEN GUI 41 The system shall provide capabilities to enter and manage travel time routes and other segmentations and integrate these with ODOT's GIS system. ü ü The inSIGHT user interface (UI) provides access to all platform features and functions, including the configuration of travel time routes, diversion routes and other segments. Please refer to Attachment C, 'Section 12.2 Configuration' for a representative example (travel time route configuration).
inSIGHT also includes an External Web API (REST/JSON) that can be used to provide device configuration, state and status information to external systems. Please refer to Attachment C, 'Section 16 External Web API' for details.
| GEN | GUI | 42 | The system shall be able to store and use contact information that is geospatially located. For example, district maintenance staff contact information is geospatially linked to the district area. | ü | ü | inSIGHT includes the ability to store and use contact information by geospatial location (i.e. polygon), type and role. inSIGHT utilizes this information to populate the External Contacts response plan element, which lists the contacts users should coordinate with in responding to / managing a given event. Please refer to Attachment C, 'Section 3.2.1.6 External Contact Response Element' for details. | |
| GEN | GUI | 43 | The system shall allow authorized users to manage contact information by geospatial location, contact type and contact role. Contacts may be state, local, private, and may or may not be associated with a location. | ü | ü | inSIGHT will allow authorized users to manage contact information by geospatial location (i.e. polygon), type and role. This is under development as part of committed work to be completed in August 2019. Please refer to Attachment C, 'Section 3.2.1.6.1 Configuration' for details. | |
| GEN | GUI | 44 | The system shall be able to provide contact information for events based on location and type of event. For example, for road work in a district the system will provide a district maintenance contact; for an emergency in a major city the system will provide state and local emergency responder contact information. | ü | ü | inSIGHT includes the ability to store and use contact information by geospatial location (i.e. polygon), type and role. inSIGHT utilizes this information to populate the External Contacts response plan element, which lists the contacts users should coordinate with in responding to / managing a given event. Please refer to Attachment C, 'Section 3.2.1.6 External Contact Response Element' for details. | |
| GEN | GUI | 45 | The system shall be able to ingest and make available geospatial contact information imported in an industry-standard geospatial data format. | ü | ü | inSIGHT is able to ingest / provide geospatial contact information in an industry-standard geospatial formats (e.g. GeoJson). | |
| GEN | DOC | Documentation (DOC) | |||||
| GEN | DOC | 01 | The responder shall provide thorough documentation for all new hardware and software deployed as part or in support of the system. | ü | N/A | ü | IBI Group will comply. |
| GEN | DOC | 02 | All documentation shall be in an electronic format with hyperlinks, searchable, and formatted for 8.5" x 11" printing. | ü | N/A | ü | IBI Group will comply. |
| GEN | DOC | 03 | The responder shall provide system administration/configurations manuals for all modules and components of the system. | ü | N/A | ü | IBI Group will comply. |
| GEN | DOC | 04 | The responder shall provide user/operator manuals and updated manuals prior to any system upgrade or new release. | ü | N/A | ü | IBI Group will comply. |
| GEN | DOC | 05 | The responder shall provide operator software/system troubleshooting guides. | ü | N/A | ü | IBI Group will comply. |
| GEN | DOC | 06 | The responder shall provide logical and physical diagrams showing network design, server and personal computers (PC), labeling of any fixed internet protocol (IP) addresses and configuration information, master account and password list for any devices or software programs. | ü | N/A | ü | IBI Group will comply. |
| GEN | DOC | 07 | The responder shall provide system administration documentation. | ü | N/A | ü | IBI Group will comply. |
| GEN | UAT | Acceptance Testing (UAT) | |||||
| GEN | UAT | 01 | The responder shall conduct acceptance testing on all aspects and modules of each system. The results of all testing shall be acceptable to the DOT prior to system/module activation. | ü | ü | IBI Group will comply. | |
| GEN | UAT | 02 | The responder shall establish a comprehensive test plan covering internal testing, end-to-end interface testing and user acceptance testing. | ü | ü | IBI Group will comply. | |
| GEN | UAT | 03 | The acceptance testing plan shall include testing scripts that can be conducted by ODOT staff or its designated representatives. | ü | ü | IBI Group will comply. | |
| GEN | UAT | 04 | The system test and training environment shall be used for all acceptance testing prior to the release of any new or modified system functionality. | ü | ü | IBI Group will comply. | |
| GEN | UAT | 05 | The responder shall conduct comprehensive acceptance testing on all system components and modules and document the test results. | ü | ü | IBI Group will comply. | |
| GEN | UAT | 06 | The system shall undergo two cyber security penetration tests prior to acceptance. The penetration testing shall be scheduled, arranged, and paid for by ODOT and performed by independent, third-party contractors employed by ODOT. The purpose of the penetration testing is to detect potential security vulnerabilities. Issues and problems identified by the penetration tests shall be resolved by the responder prior to system acceptance. | ü | ü | IBI Group will comply. | |
| GEN | TRN | Training (TRN) | |||||
| GEN | TRN | 01 | The responder shall provide a training plan and conduct user and administrator training sessions on system functionality. | ü | ü | IBI Group will comply. | |
| GEN | TRN | 02 | The responder shall develop training plans for operators and administrators and submit them to the DOT for review and approval prior to training. | ü | ü | IBI Group will comply. | |
| GEN | TRN | 03 | The responder shall provide a minimum of three on-site operator training classes, covering all system functionality, prior to system activation. | ü | ü | IBI Group will comply. | |
| GEN | TRN | 04 | The responder shall provide on-site administrator training class(es) prior to system activation. | ü | ü | IBI Group will comply. | |
| GEN | OM | O&M / Support (OM) | |||||
| GEN | OM | 01 | The responder shall ensure continuity of operation and maintenance through the means of dedicated staff and standard operating procedures. | ü | ü | IBI Group will comply. | |
| GEN | OM | 02 | The responder shall provide 24/7/365 support for resolution of software and system operations issues. After-hours support can be by telephone, email, chat, or other mechanisms. | ü | ü | IBI Group shall comply (24/7/365 1-800 number and JIRA project / ticketing system will be provided). | |
| GEN | OM | 03 | The responder shall acknowledge notification of critical system issues within 15 minutes and resolve or provide a plan for resolution within 1 hour of notification. Critical system issues consist of the loss of functionality of one or more primary system components. During this resolution period, the responder shall provide frequent and regular updates on resolution status along with other mitigation support as needed. | ü | ü | IBI Group will comply. | |
| GEN | OM | 04 | The responder shall resolve major system issues within 48 hours of notification. Major system issues consist of any fault or issue that inhibits effective or correct operation. The responder shall provide frequent and regular updates on resolution status. If a workaround is proposed, it must be reasonable and acceptable by ODOT. | ü | ü | IBI Group will comply. | |
| GEN | OM | 05 | The responder must resolve minor system issues in the next software build or within 14 calendar days, whichever is sooner. Minor system issues do not inhibit effective software functionality. | ü | ü | IBI Group will comply. | |
| GEN | OM | 06 | ODOT may request that major or minor system issues be resolved sooner than required by GEN-OM-04 and GEN-OM-05. If such resolution is technically feasible but would require additional cost, the Responder shall work with ODOT to negotiate compensation for the additional effort. | ü | ü | IBI Group will comply. | |
| GEN | OM | 07 | The responder shall provide issue tracking that allows the responder and ODOT staff to report system problems and track their progress to resolution. Summary reports of issue status and resolution shall be provided regularly at project management meetings, and the responder’s contract performance will be assessed based on adherence to all support requirements. | ü | ü | IBI Group will comply. A JIRA project / ticketing system will be provided for issue reporting and tracking through to resolution. Summary reports of issue status and resolution shall also be provided at project management meetings. | |
| GEN | OM | 08 | It is desirable the system not be taken offline during scheduled maintenance activities, but that the failover capability described in GEN-HW-01 IT-HW-02 be used to minimize downtime. | ü | ü | IBI Group will comply. | |
| GEN | OM | 09 | If downtime for maintenance is unavoidable, the responder must schedule with ODOT a minimum of 5 working days in advance and perform maintenance between 8pm and 5am. ODOT shall have the option to postpone scheduled maintenance at any time based on priority operational conditions such as weather or other events. | ü | ü | IBI Group will comply. | |
| GEN | OM | 10 | The responder shall be required to provide all software and operating system updates and upgrades for the duration of the contract at no additional cost. | ü | ü | IBI Group will comply. |
IT Reqs Meets Requirement (via Configuration) w/ No Additional Development Meets Requirement w/ Additional Development Included in Bid Meets Requirement w/ Alternative Approach Does Not Meet Requirement
| Deployment Timeline | |||||||||||
| CAT | Sub | ||||||||||
| CAT | Req# | Requirement | Day 1 | Year 1 + | User Role(s) | Feature XREF | Service Bucket / Priorities | Bidder Approach | |||
| IT REQUIREMENTS (GEN) | |||||||||||
| IT | OIT | ODOT IT (OIT) | |||||||||
| IT | OIT | 01 | At a minimum, the responder will comply with and adhere to all Department and State information technology standards, including without limitation, all technical and security standards, procedures and protocols. | ü | N/A | ü | IBI Group will comply. | ||||
| IT | OIT | 02 | At a minimum, all hardware components shall meet the requirements of the ODOT Office of the Information Technology (OIT). | ü | N/A | ü | IBI Group will comply. | ||||
| IT | OIT | 03 | At a minimum, the system shall provide data backup measures which meet the requirements of OIT. | ü | N/A | ü | IBI Group will comply. | ||||
| IT | OIT | 04 | At a minimum, all internet and web components of the system shall meet the requirements of OIT. | ü | N/A | ü | IBI Group will comply. | ||||
| IT | OIT | 05 | The user interface shall be fully web based and operational on modern version(s) of publicly available browsers. At a minimum, the system shall support Internet Explorer, Chrome (preferred), and Safari. | ü | N/A | ü | IBI Group shall comply. The inSIGHT UI was designed to support all modern HTML5 compliant browsers. Internal (unit and QA) and formal (FAT and SAT) testing is generally conducted using Google Chrome (by default). | ||||
| IT | OIT | 06 | The system hardware for servers shall use the most current version of Microsoft Windows Server supported by OIT. | ü | N/A | ü | IBI Group will comply. | ||||
| IT | OIT | 07 | The system shall include a mobile application to interface with the primary application. Those mobile applications shall be developed for both iOS and Android. | ü | ü | N/A | ü | IBI Group will include a mobile application to interface with the primary application, which can run on iOS and Android. | |||
| IT | SEC | Security (SEC) | |||||||||
| IT | SEC | 01 | At a minimum, the responder will comply with and adhere to all Department and State information technology cybersecurity standards. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 02 | The system shall provide a System Security Plan that describes the strategy to ensure the system's compliance with the OIT security policies. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 03 | For responder-provided cloud-based processing services, the system shall automatically detect and prevent malicious attacks such as distributed denial of service. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 04 | For responder-provided cloud-based processing services, the system shall automatically detect and notify authorized users when the system is experiencing a potential malicious attack such as a distributed denial of service. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 05 | The responder shall provide a Disaster Recovery and Incident Response Plan. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 06 | An independent security assessment shall be performed on the system annually. This assessment will be by a third party hired by the ODOT. The responder shall respond to all results of the annual security assessment within 30 days including remedies or timeline to implement remedies. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 07 | All facilities provided by the responder for hosting system components shall be located in the United States and Federal Risk and Authorization Management Program (FedRAMP) certified (www.fedramp.gov). | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 08 | The system shall require each user to have a unique username and password combination to access any non-public functionality. | ü | ü | inSIGHT requires that each user has a unique username and password combination. | |||||
| IT | SEC | 09 | The system shall utilize Microsoft Active Directory as the core environment for application services, including user authentication, overall system security for users and components, including password control, and permission-based access to data and components. | ü | ü | inSIGHT supports Microsoft Active Directory integration for user authentication. | |||||
| IT | SEC | 10 | The system shall also provide access to users not using Microsoft Active Directory, such as external users from partner agencies or contractors. | ü | ü | inSIGHT supports providing access to users without Microsoft Active Directory accounts. | |||||
| IT | SEC | 11 | The system must provide for and support 2-factor authentication using Microsoft Active Directory. | ü | ü | IBI Group will comply. | |||||
| IT | SEC | 12 | The system shall limit access to functionality based on the permissions of the user. | ü | ü | The inSIGHT user interface (UI) supports the assignment of permissions to users/user groups, for the purpose of limiting access to specific inSIGHT functions. Please refer to Attachment C, 'Section 2.4 User Administration' for details. | |||||
| IT | SEC | 13 | The system user permissions shall be able to limit a user's access by, at a minimum: |
- a geographic area
- specific system functions
- system environment (e.g., user may only use the test environment) ü ü The inSIGHT user interface (UI) supports the assignment of permissions to users/user groups, for the purpose of limiting access to specific inSIGHT functions. The inSIGHT UI will be configured to incorporate geographic area based user rights. Please refer to Attachment C, 'Section 2.4 User Administrator' for details.
inSIGHT supports the creation of separate accounts in production and test/training environments, with different permissions. For example, a user may be trained to be an administrator on the test/training environment, without providing them with access to production environment administrative functions.
| IT | SEC | 14 | The system shall allow a user to have multiple permissions. For example, a supervisor may have permissions to perform operations and to generate usage or staffing reports. | ü | ü | The inSIGHT user interface (UI) supports the assignment of multiple permissions to users/user groups. Please refer to Attachment C, 'Section 2.4 User Administrator' for details. |
| IT | SEC | 15 | The system shall have a permission for administration functionality. Administration functionality shall include at a minimum: |
- User account creation, deletion and management
- System status monitoring
- System configuration management
- Audit of login and log out times
- Audit of data entry activity.
- Audit of traffic management activity.
- Audit of user activity. ü ü The inSIGHT user interface (UI) supports the assignment of permissions to users/user groups, for the purpose of limiting access to specific inSIGHT functions, including administrative functions, such as user account and group management, system status monitoring and configuration management. Please refer to Attachment C, 'Section 2.4 User Administrator' for details.
inSIGHT supports the auditing of user access, data entry, traffic management and other activities through its reporting functions, which are accessible to administrators.
| IT | SEC | 16 | The system shall prevent unauthorized access. | ü | ü | inSIGHT requires that each user has a unique username and password combination. | ||
| IT | SEC | 17 | The system shall log unsuccessful access attempts. | ü | ü | inSIGHT logs all access attempts. | ||
| IT | SEC | 18 | The system shall log all actions made by system users such that it can review all actions taken by the users for the data entered into the system. | ü | ü | inSIGHT logs user access, data entry and other traffic management actions its operational database for reporting and auditing purposes. | ||
| IT | HW | Hardware Platform (HW) | ||||||
| IT | HW | 01 | The system shall provide High Availability (HA) operations of 99.99% | ü | N/A | ü | IBI Group will comply through leveraging the state's virtualized compute platform, as required by the State IT Computing Requirements, for on-premises solutions. | |
| IT | HW | 02 | HA operations should be achieved in part by maintaining primary and secondary (backup) production sites in disparate locations and/or other strategies proposed by the Responder (provide a description in this matrix or in the proposal) and approved by ODOT. | ü | N/A | ü | IBI Group will comply through leveraging the state's virtualized compute platform, as required by the State IT Computing Requirements, for on-premises solutions. | |
| IT | HW | 03 | Responders may propose a system consisting of local physical servers, a cloud-based computing services solution or a hybrid combination designed to meet all needs of the system. Please be specific when describing the proposed solution. | ü | N/A | ü | IBI Group proposes using the state's virtualized compute platform to host the inSIGHT platform. | |
| IT | HW | 04 | The System shall be deployed using SQL Server. If another database product is proposed, responder must include details here and necessary pricing. | ü | N/A | ü | The inSIGHT platform incorporates a Microsoft SQL Server database. Please refer to Attachment C, 'Section 1 Overview' for details. | |
| IT | HW | 05 | The System shall include and utilize monitoring tools to monitor the overall system health. Real-time data from those network monitoring tools shall be made available to ODOT staff and assignees. The system shall also provide a dashboard view of any data being received/monitored by the network monitoring tools. | ü | N/A | ü | IBI Group will provide the Paessler PRTG Network Monitor, also deployed on the state's virtualized compute platform, for the purpose of monitoring overall platform health. ODOT personnel will be provided with access to the data and dashboards made available by PRTG. | |
| IT | ENV | Environments (ENV) | ||||||
| IT | ENV | 01 | In addition to the Responder's own development environment, the responder shall provide environments for ODOT to use for this project. | ü | N/A | ü | IBI Group will provide inSIGHT platform environments for production, staging/training and testing/QA. | |
| IT | ENV | 02 | The ATMS responder shall provide environments for ODOT to use for testing, staging/training, and production. | ü | N/A | ü | IBI Group will provide inSIGHT platform environments for production, staging/training and testing/QA. | |
| IT | ENV | 03 | All solution development shall be conducted by the responder in their own development environment before being moved to ODOT project environments. | ü | N/A | ü | All development will be conducted on IBI Group's internal / corporate IT infrastructure. | |
| IT | ENV | 04 | The testing environment shall be available to authorized users for testing and demonstrating all system functionalities and upgrades without impacting the performance or functionality of the production system. | ü | N/A | ü | The testing/QA environment will be made available to authorized IBI Group and ODOT personnel for testing, feature demonstrations, and Agile design reviews. The performance of the production system will not be impacted; the testing/QA environment will not utilize production environment resources (i.e. virtual machines). | |
| IT | ENV | 05 | The training environment shall be available to authorized users for training TMC operators without impacting the performance or functionality of the production system. | ü | N/A | ü | The inSIGHT staging/training environment will be made available to authorized IBI Group and ODOT personnel for training inSIGHT users and administrators. The performance of the production system will not be impacted; the staging/training environment will not utilize production environment resources (i.e. virtual machines) | |
| IT | ENV | 06 | The responder shall support the DOT's needs in the use of the testing and (for the ATMS responder) training environments by assuring, with notice, the correct software/module versions are installed to support the necessary testing and/or training activities. | ü | N/A | ü | IBI Group will comply. | |
| IT | ENV | 07 | The system shall have a production environment that provides all implemented system functionalities. The production environment shall be the most recent versions of all modules that have been tested and accepted by ODOT. | ü | N/A | ü | The inSIGHT production environment will host the most recent versions of the software modules that have been tested and accepted by ODOT. | |
| IT | GEN | General (GEN) | ||||||
| IT | GEN | 01 | The ATMS functions of the system shall be scalable to allow for 1) growth in both the number of devices managed and controlled and 2) the number simultaneous authorized users. | ü | N/A | ü | The inSIGHT platform (production environment) will be distributed and configured to accommodate a 300% increase in the number of devices, and a minimum of 200 concurrent users. | |
| IT | GEN | 02 | The ATMS functions of the system shall be capable of handling a minimum of 300% of the number of field devices that exist on the first day of system activation. | ü | N/A | ü | The inSIGHT platform (production environment) will be distributed and configured to accommodate a 300% increase in the number of devices, and a minimum of 200 concurrent users. | |
| IT | GEN | 03 | The ATMS functions of the system shall support a minimum of 200 users simultaneously. In the event the number is exceeded, TMC operators shall have priority access. | ü | N/A | ü | The inSIGHT platform (production environment) will be distributed and configured to accommodate a 300% increase in the number of devices, and a minimum of 200 concurrent users. inSIGHT will be updated to provide TMC operators will have priority access if the maximum number of concurrent users is exceeded. | |
| IT | GEN | 04 | The ATMS system workstation user interface shall have the capability to be displayed on multiple monitors. | ü | N/A | ü | The inSIGHT user interface (UI) will have the ability to be displayed on multiple monitors. | |
| IT | GEN | 05 | System, software, and interfaces should be compliant with ITS industry standards except where such compliance limits desired functionality or significantly increases costs. Standards include but are not limited to: |
• Institute of Transportation Engineers (ITE) Traffic Management Data Dictionary (TMDD)
• Society of Automotive Engineers (SAE) J2354 ATIS Message Set Standard
• Institute of Electrical and Electronics Engineers (IEEE) Incident Management 1512 Family of Standards
| • Applicable National Transportation Communications for Intelligent Transportation System Protocol (NTCIP) Standards for device control and for center-to-center (C2C) communications | ü | N/A | ü | IBI Group will comply. | ||||||
| IT | GEN | 06 | The system shall include a fully integrated Truck Parking Information and Management System solution. | ü | ü | inSIGHT implements a fully integrated Truck Parking Information and Management System. Please refer to Attachment C, 'Section 15 Truck Parking Systems Integration' for details. | ||||
| IT | GEN | 07 | The system shall include a Signal System integration, such that the ATMS can control (automatic and otherwise) signals from within the GUI. | ü | ü | IBI Group will work with ODOT to update inSIGHT to support signal systems control from the inSIGHT user interface (UI). | ||||
| IT | GEN | 08 | The system shall allow the Operator to log a call from an outside entity (e.g., State Police, etc.…) and include any pertinent information gathered on that call. The Operator shall then have the ability to use that call log to create a new incident that inherits the information within. | ü | Editor, Manager | ü | inSIGHT will be updated to include the described call log. | |||
| IT | ALRT | Alerts & Alarms (ALRT) | ||||||||
| IT | ALRT | 01 | The system must provide alerts and alarms to bring relevant items to the attention of the operators for their action. The specific mechanism and manner of display should be designed with the operator in mind, to reduce cognitive load by displaying relevant information only and streamlining the user interface for maximum operational effectiveness. The requirements in this section represent ODOT's needs and a concept for displaying, managing, and responding to alerts and alarms. If the Responder's alerts management system varies from these requirements, describe in detail how the proposed system meets these needs and is effective for operations. | ü | ü | The inSIGHT user interface (UI) provides robust notification capabilities to alert users to new information requiring attention, which are designed to streamline user workflows, while minimizing cognitive load through presenting only relevant, key information. Please refer to Attachment C, 'Section 2.3 Notifications and Alerts' for details. | ||||
| IT | ALRT | 02 | Alerts from Incident and Queue detection algorithms and other traffic operations sources should be displayed in a manner where they are prominent and be available for the operator to address after taking care of other priority needs. | ü | ü | Incident and queue detection alerts, whether from internal or external sources, are prominently displayed and sorted by priority in the inSIGHT user interface (UI) notification panel, and on the inSIGHT UI map view. Please refer to Attachment C, 'Section 2.3 Notifications and Alerts' for details. | ||||
| IT | ALRT | 03 | Notifications of hardware and equipment malfunctions and central software issues shall be separate from traffic operations alerts and shall not interfere with traffic operations responses. | ü | ü | The inSIGHT user interface (UI) notification panel will be configured to separately display all notification items stemming from ITS device and equipment malfunctions, such that they do not distract from event and response management activities. Please refer to Attachment C, 'Section 2.3 Notifications and Alerts' for details. |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .