Configuration and Change Order Management. During the course of the iFlorida program, requests for change orders are likely, due to uncertainty in project requirements and specifications, or for unanticipated conditions. FDOT will make every effort to minimize the potential for change orders through early standards and specifications work that will support enhanced communications between the contractor/partner. Early project scoping and requirements meetings will be held to address potential conflicts or concerns of the contractor/partner in the project. When change orders are justified, they will be reviewed for technical, cost, and schedule implications. Specific written justification will be provided to the Core Management Team and FHWA. A joint Core Management Team and FHWA will provide a final review and approval. Once the baseline design has been established and approved by FDOT and FHWA, requests for change orders or changes to the baseline design will be evaluated by a formal Configuration Control Board and controlled by FDOT. Changes to the baseline design approved by the Configuration Control Board will be documented as a change order to the design and/or requirements. Changes to documents and drawings will be documented to ensure appropriate internal control has been observed. Additionally, all hardware and commercial-off-the-shelf (COTS) software will be kept under configuration control. Configuration control for the iFlorida program will consist of an Excel spreadsheet program. All interfaces will be managed by an FDOT Interface Control Working Group and documented via an Interface Control Document. Modified and newly developed software written for this project will come under strict FDOT software configuration management (CM) control. Software contractors for the iFlorida program will be required to provide a Software CM plan with their initial proposal and implement their plan for the life of the project. Software CM, at a minimum, will encompass the following tasks: • Identify the software components that will be placed under configuration control. • Identify the components via a numbering or some other scheme. • Maintain a current status of all parts (revision number, etc.) that are in a baseline (i.e., configuration control). • Maintain a backup copy of the baseline. At any point in time, it shall be possible to go back and faithfully reproduce a previous baseline on the system (i.e., configuration control). • For modified and newly developed software FDOT will chair and manage ...
