Specifications include, but are not limited to: a. All design and development of the IRIS system relative to the Functional and System Requirements as stated herein, shall be in keeping with the functional workflow processes for each specific ROW and Utility function. b. The IRIS system must have or create Web APIs for connectivity between them and other systems that TDOT deems necessary. c. The IRIS system must have an API to interface with the FRA, or a State managed dataset to accept and download required data related to crossings (such as the number of trains, Railroad owners, etc.). d. The IRIS system shall interface with the GIS data environment so that translation is an automated and seamless process used by other State agencies. e. The IRIS system must accept attachments that can be permanently archived within the system or TDOT’s electronic document repository system. f. The IRIS system must be able to search and retrieve archived documentation of historical transactions related to the current projects. g. Road projects within the system shall be able to draw applicable data from other functional areas within the same overall road project. (For instance, the Acquisition function for a certain tract should be able to draw data from the Appraisal function of the same tract, and the Appraisal function should be able to draw information from the ROW Design function) h. The IRIS system must contain an automated assistant component that can guide users through each process when setting up and entering information into one or more functional areas to include form data, submissions, red flags, error reporting, approvals, and overrides. The application automation must be able to recall previous "unfinished" or "incomplete" data that can prompt the user to complete the process until all relevant data entry is complete. Previous sessions by the user must be able to be recalled and prompt the user to the place where the user last stopped working.
