1 / 11

Strategy & Planning Enterprise Architecture

Strategy & Planning Enterprise Architecture. COTS-based modules for: 1) Network Delivery & Development 2) Traffic Management. HAPMS – As-Is. Based on Pitney Bowes Insight “Confirm” COTS package. Supports multiple application modules including: SWEEP Whole-Life Costs Scheduled Road Works

roden
Download Presentation

Strategy & Planning Enterprise Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Strategy & PlanningEnterprise Architecture COTS-based modules for: 1) Network Delivery & Development 2) Traffic Management

  2. HAPMS – As-Is • Based on Pitney Bowes Insight “Confirm” COTS package. • Supports multiple application modules including: • SWEEP • Whole-Life Costs • Scheduled Road Works • Accident Records • Delay Cost Model • Not all in-scope for IAM Programme

  3. Network Delivery & DevelopmentIAM COTS Example Main candidates: Pitney Bowes Insight (Confirm), Exor, Symology.

  4. TI2011+ Move towards COTS? • e.g. ITIS Holdings - TrafficScience

  5. INM - Move towards COTS • CUTLAS is fully compliant with UTMC specifications. • Integrates data from traffic control, street asset and other traffic/highway-related subsystems. • Implements high performance ENVITIA MapLink command and control to provide full GIS capability.

  6. UTMC-IAM Integration Case Study: Oxfordshire County Council

  7. Standards-based Integration • Service-Oriented Architecture (SOA). • Enterprise Service Bus (ESB). • Incremental Deployment. • Re-use of Legacy Systems which still provide business value. • Sweat assets instead of wholesale “rip and replace”. • Reduce costs.

  8. Typical COTS Features • GIS User Interface • Support for leading Spatial Databases • Support for OGC standards – WMS, WFS, etc. • Flexible Web Services • OS MasterMap ITN support • Snap to OS MasterMap facility • Support for the Traffic Management Act (TMA) • Network Definition & Management with multiple linear referencing • Compliance/Integration with BS7666 – National Land & Property Gazetteer • 2-way transmission of EToN Notices • Spatial representation & Management of: • Link/Node Network structures • Street Gazetteer • Associated street data • UK PMS Defects & Treatments • Street works • Traffic pinch points • Import/Export and maintenance of NSG

  9. Common Denominators • GIS User Interface • Spatial Data Infrastructure • Spatial database • Standard OGC Web Services • Modular design • Open interfaces • Multiple location referencing systems may be overlaid with automatic translation from one referencing system to another.

  10. INSPIRE Network Transformation Web Service • INSPIRE requires interoperability across Europe. • Needs a standards-based Public (external) schema. • Transformation services allow organisations to meet their legal obligation whilst ensuring continuity of their existing business systems.

  11. Conclusions • URNM was originally conceived against an As-Is Architecture with 22+ siloed solutions. • The To-Be Architecture is converging on two COTS-based Application Frameworks: • ND&D: IAM (currently out to OJEU); • TMD: Integrated Network Management is rolling out Envitia’s Cutlas (UTMC) system. • Each of these are converging on Open standards such as OGC Web Services. • URNM is in danger of “Reinventing the wheel” and breaking the EA Principle of “Re-use before buy before build”.

More Related