What if the statewide ITS architecture is at odds or conflicts with the regional ITS architecture, e.g. project prioritization is not the same?
Project prioritization is a local/regional decision. The regional and/or statewide ITS architecture should only consider sequencing of projects, not their priority for deployment. Statewide and regional ITS architectures should be consistent with each other. In fact, any regional ITS architectures that overlap should be consistent with each other. As a suggestion, the operational concepts, functional requirements, interconnects, information flows, project sequencing, agency agreements and ITS standards sections should be compared for compatibility. If there is a gap or an unnecessary overlap, the stakeholders can agree to change one or both architectures as needed. The changes can occur then or at the next maintenance cycle, as appropriate.
Related Questions
- Is the goal of Statewide Student Information System project to replace the Student Information System (SIS) which local districts have purchased?
- What if the statewide ITS architecture is at odds or conflicts with the regional ITS architecture, e.g. project prioritization is not the same?
- Was Honeywell-Bull Distributed System Architecture derived from Cyclades INRIA project ?
