KDOT PMS Replacement Project

Requirement Diagram - R-PMS System - Master Requirements for KDOT Replacement PMS System link

Jump to:
Layers
:Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency :Dependency Session Termination-Inactivity Log out:Requirement Session Termination-Manual Log out:Requirement Session Management:Requirement Default Local Accounts:Requirement Least Privilege:Requirement Note:An ordered list of these requirements can be found selecting the link in the upper left: Model Lists: Glossary, Requirements, and Use Cases and then selecting the R-PMS Requirements List in the lower left pane.:Note External Reporting and Analysis tool support:Requirement Other Miscellaneous Data:Requirement Interface or ingest GPS data tied to the collection process and LRS.:Requirement Interface or ingest image files from pavement surface data collection system.:Requirement Interface or ingest native format files (FIS) from pavement surface data collection system. :Requirement Interface or ingest NOS collection data from Van and data processing:Requirement Interface or ingest current data reported through a form by field personnel indicating that a project is completed - CRF:Requirement Interface or ingest current data about current or scheduled pavement surfacing projects - PROJECT:Requirement Interface or ingest current data for project tracking for Pavement Management purposes:Requirement Interface or ingest current inventory data for historic traffic - TRAF:Requirement Interface or ingest current inventory data References- REF:Requirement Interface or ingest current inventory data for the Highway Performance Management System - HPMS:Requirement Interface or ingest current inventory data for the State Highway System - GEOM:Requirement Interface or ingest current inventory data:Requirement Interface or ingest historic segmented action history data:Requirement Interface or ingest historic CSTATE data:Requirement Interface or ingest historic Mean Texture Depth data:Requirement Interface or ingest historic Remaining Life data:Requirement Interface or ingest historic HPMS data:Requirement Routine data integrity:Requirement Data Integrity:Requirement Estimated cost of equipment/ hardware (KDOT Hosted):Requirement Hardware Requirements (KDOT Hosted):Requirement System Hardware (KDOT Hosted):Requirement Data Protection and Recovery:Requirement Disaster Recovery:Requirement History Tracking:Requirement Data Segregation:Requirement Data Privacy:Requirement Data Encryption:Requirement Denial of Service:Requirement Logging Security Violations:Requirement Security Authentication and Authorization:Requirement User Timeout:Requirement Restrict Access:Requirement Group Configuration:Requirement Default User Group:Requirement User Group Security Access:Requirement Member of User Groups:Requirement Multiple User Groups:Requirement Authorization level:Requirement Automated User Access List updates:Requirement Accessibility--2:Requirement Accessibility--1:Requirement Single Sign on:Requirement Multiple Users:Requirement AD Configuration:Requirement Active Directory Integration:Requirement AD Authentication:Requirement State Security Policy:Requirement User Documentation:Requirement Documentation:Requirement Architecture:Requirement Communication Bandwidth:Requirement Windows Server:Requirement Oracle or SQL Server Management:Requirement SOA Architecture API:Requirement SOA Architecture:Requirement Browser Capability:Requirement Compute Environment Compatibility:Requirement Workflow Functionality:Requirement Forms Functionality:Requirement Mobile Support:Requirement System Configurability:Requirement Interface Functionality :Requirement Report Data:Requirement Report Functionality:Requirement provide GIS visualizations showing analysis outputs:Requirement provide GIS visualizations of the network(s):Requirement Generate Compliance:Requirement General System Requirements:Requirement Operating System:Requirement Security Requirements:Requirement Technical Architecture:Requirement Use or replace CRF web app to get project Workflow:Requirement Forms:Requirement Configuration:Requirement Pavement Data and Analysis with Relevant Systems Integration:Requirement Managing Pavement Reporting Functions:Requirement Alert Transportation Planning of completed CRFs:Requirement Interface with KDOT project management systems:Requirement Project Management Systems Integration:Requirement GPS Data:Requirement Interface with KDOT (or other commercial) pavement condition image viewing and reporting systems:Requirement Data Quality Checks:Requirement What has been collected/what remains:Requirement Where to collect:Requirement Comprehensive process from collection through analysis:Requirement Interface with KDOT (and other typical) pavement condition collection systems:Requirement Pavement Condition Collection Systems and Data Integration:Requirement Interface or ingest historic ride data:Requirement Interface or ingest historic rigid pavement surface condition data:Requirement Interface or ingest historic flexible pavement surface condition data:Requirement Interface or ingest historic continuous pavement surface friction data:Requirement Interface or ingest historic pavement surface friction expanded data:Requirement Interface or ingest historic pavement surface friction point data:Requirement Interface or ingest historic pavement surface friction data:Requirement Interface or ingest historic pavement Joint Distress Collection data:Requirement Interface or ingest historic pavement TSD data:Requirement Interface or ingest historic pavement FWD data:Requirement Interface or ingest historic pavement csv report data:Requirement Interface or ingest historic pavement core data:Requirement Interface or ingest historic pavement condition data:Requirement KDOT Historic Pavement Condition Data Integration:Requirement Provide typical GIS functions:Requirement provide mark up and feedback on maps:Requirement provide GIS visualizations showing attributes related to pavement inventory or analysis:Requirement provide GIS visualizations showing condition vs previously predicted changes related to pavement analysis:Requirement provide GIS visualizations showing predicted future condition:Requirement provide GIS visualizations showing condition changes related to pavement analysis:Requirement provide GIS visualizations showing condition (or measured output) related to pavement analysis:Requirement provide GIS visualizations showing where collected data has completed the processing and loading steps:Requirement provide GIS visualizations showing collection/processing status :Requirement Either provide GIS tools or Interface with KDOT implementation of ArcGIS:Requirement KDOT GIS Systems Integration:Requirement Use K-Hub Interface to push PMS pavement condition data:Requirement Use K-Hub Interface to update PMS inventory data:Requirement Interface with KDOT implementation of Roads and Highways called K-Hub:Requirement Use K-Hub Interface to update PMS highway network and LRS:Requirement KDOT Highway Inventory Systems Integration:Requirement Run Analyses to Determine related Pavement Performance, Work Types, and Funding for the TAMP :Requirement Allow for economic assumption flexibility:Requirement Allow for constraint set naming:Requirement Allow for work type constraint flexibility:Requirement Allow for pavement action set naming:Requirement Allow for action feasibility and cost flexibility:Requirement Allow for pavement deterioration model definition set naming:Requirement Allow for condition deterioration model flexibility:Requirement Allow for pavement condition definition set naming:Requirement Allow for pavement condition flexibility:Requirement flow and track TAMP (pavement) data for submittals:Requirement Pavement Related Asset Management Processes:Requirement compile pavement condition data following KDOT Performance Measures requirements and pass to KDOT Performance Measures Dashboard:Requirement flow and track pavement condition data for KDOT Performance Measures Dashboard submittals:Requirement run analyses to determine predicted pavement performance measure:Requirement flow and track predicted pavement condition data for KDOT Performance Measures Dashboard submittals:Requirement Non-State-maintained data collected in one calendar year must be passed to Planning before June 15 of the following year:Requirement Non-Interstate data collected in one calendar year must be passed to Planning before June 15 of the following year:Requirement Interstate data collected in one calendar year must be passed to Planning before April 15 of the following year:Requirement generate pre-HPMS submittal Report Card:Requirement Conflation to Planning Network/LRS:Requirement compile pavement condition data following HPMS requirements and pass to KDOT Transportation Planning:Requirement Flow and Track HPMS (pavement) data for submittals:Requirement KDOT and Federal Pavement Performance Monitoring Processes:Requirement Accommodate future expansion of Pavement Management coverage:Requirement Allow for flexibility in Priority Formula Attributes and Segmentation:Requirement Provide Data or Interface to Feed the Priority Formula:Requirement Generate Remaining Pavement Life Attribute:Requirement Allow for economic assumption flexibility:Requirement Allow for constraint set naming:Requirement Allow for work type constraint flexibility:Requirement Allow for pavement action set naming:Requirement Allow for action feasibility and cost flexibility:Requirement Allow for pavement deterioration model definition set naming:Requirement Allow for condition deterioration model flexibility:Requirement Allow for pavement condition definition set naming:Requirement Allow for pavement condition flexibility:Requirement 3R PPS - Analysis :Requirement Allow for economic assumption flexibility:Requirement Allow for constraint set naming:Requirement Allow for work type constraint flexibility:Requirement Allow for pavement action set naming:Requirement Allow for action feasibility and cost flexibility:Requirement Allow for pavement deterioration model definition set naming:Requirement Allow for condition deterioration model flexibility:Requirement Allow for pavement condition definition set naming:Requirement Allow for pavement condition flexibility:Requirement Provide Analysis to develop and support the Allow for economic assumption flexibility:Requirement Allow for constraint set naming:Requirement Allow for work type constraint flexibility:Requirement Allow for pavement action set naming:Requirement Allow for action feasibility and cost flexibility:Requirement Allow for pavement deterioration model definition set naming:Requirement Allow for condition deterioration model flexibility:Requirement Allow for pavement condition definition set naming:Requirement Allow for pavement condition flexibility:Requirement Pavement Project Selection Processes:Requirement Provide Analysis to develop and support pavement future condition based on different funding programs:Requirement Allow for economic assumption flexibility:Requirement Allow for constraint set naming:Requirement Allow for work type constraint flexibility:Requirement Allow for pavement action set naming:Requirement Allow for action feasibility and cost flexibility:Requirement Allow for pavement deterioration model definition set naming:Requirement Allow for condition deterioration model flexibility:Requirement Allow for pavement condition definition set naming:Requirement Allow for pavement condition flexibility:Requirement Provide Analysis to develop and support pavement funding program based on future desired conditions:Requirement Pavement Funding Programs:Requirement Replacement Pavement Management System (R-PMS):Requirement Replacement Pavement Management System (R-PMS):Requirement

KDOT PMS Replacement Project