Montana DOT Strategic Enterprise Architecture Presentation to 2016 IHEEP Annual Conference. September 12, 2016

Transcription

1 Montana DOT Strategic Enterprise Architecture Presentation to 2016 IHEEP Annual Conference September 12, 2016

2 Introductions Jack Dartman Application Development Supervisor and Enterprise Architect MDT Information Services Robert Cooney, PMP President and Managing Partner evision Partners, Inc. 2

3 Agenda Presentation Objectives Project Background Project Approach Key Conclusions & Recommendations EA Implementation Plan Discussion, Questions, Wrap Up 3

4 4

5 Challenges with Current MDT Technology Application systems fragmented in scope and purpose Application systems which are narrowly focused on the needs of a single business unit Limitations in data sharing between systems resulting in redundant data entry Key functional gaps in applications Often results in the need for end users to develop off-line applications or shadow A number of application systems developed in older programming languages Difficult to enhance/maintain Many IT systems approaching the end of their technical useful life New systems being procured to meet silo needs of a specific business unit 5

6 Other Business Drivers Impacting DOTs Need for greater transparency Need for greater accountability Expectations for enhanced organizational efficiency and effectiveness Requirements for enhanced collaboration with partners Flat or reduced budgets Reduced staffing levels Increased utilization of alternative financing or alternative delivery models 6

7 Strategic Enterprise Architecture Design & Implementation Plan To better align MDT s future technology investments in support of executing the agency s mission 7

8 Enterprise Architecture Seeks to Achieve Business and Technology Alignment Business Invest in technology Seek solutions to meet business need Collaboration Deliver technology services to address business needs Influence business change Technology Not just alignment but collaboration Investment in and delivery of technology solutions reflect business priorities Business decisions consider technology implications Adapted from Enterprise Architecture and TOGAF, presentation by Alan McSweeney 8

9 Enterprise Architecture Defined Strategic Enterprise Asset Base Establishes the organizational mission Identifies information necessary to perform the mission Identifies technologies necessary to perform the mission Provides transitional processes for implementing required technologies The primary purpose of an EA is to inform, guide, and constrain the technology decisions for the enterprise Based on Federal CIO Council Definition,

10 Enterprise Architecture Framework Business Architecture What do we do? Who does it? What information is required? Where is a function performed? Information Systems Architecture Technical Architecture Data Application Technology Integration Technology Data Technology Applications Geospatial Analysis Document Management Collaboration Integration Security Network & Communications Hardware Platforms 10

11 Enterprise Architecture in Other State DOTs 11

12 12

13 EA Project Objectives Analyze and document the As-Is organizational business processes and supporting information systems architecture for MDT Make specific recommendations for a To-Be future state Business processes and information system architecture Prepare an implementation plan for transitioning to the To-Be state Develop recommendations for the implementation of appropriate governance mechanisms and change management procedures 13

14 Key Tasks Project initiation Situation analysis Enterprise architecture design Strategic options and initiatives Implementation plan 14

15 Enterprise Architecture Framework 15

16 MDT Analysis Framework 16

17 Mapping of Business Drivers to Strategic Objectives Business Driver Quality Safety Cost Effectiveness Economic Vitality Conduct maintenance and asset management operations in a streamlined and efficient manner Perform winter maintenance activities that provide consistent levels of service and optimize MDT resources Continue to research new equipment, materials, and processes to improve winter driving conditions of roadways Environmental Sensitivity 17

18 Mapping Systems to Business Functions System under development 18

19 To-Be State Guiding Principles Implement common solutions where practical Foster data sharing and data integration Leverage existing MDT or State solutions Implement best practices Strengthen governance processes 19

20 To-Be Architecture Preconstruction Management GeoMS Storm Water Outfall Inventory System (Outfall) As-Built (AA-6) Systems and Project Planning Planisware (AA-5) Project data lookup New Program / Project Management System (AA-1) Candidate Projects Construction Management Construction and Materials (AA-8) LIMS (AA-9) SiteManager Cost estimation information Geotechnical data & Inventory data AASHTO Bridge Rating Structures Bridge and culvert condition data SMS/Advitam (AA-12) Transportation Asset Management Multi-Modal and Grants Management Grants Management (AA-18) PCR Process Pavements Pavement condition information Agile Assets Pavement Analyst Pathway (Pathview/Pathweb) Pavement History Stripmap (add-on) External/Other Agency Systems HPMS Fleet AgileAssets EVMS (AA-17) AgileAssets Statewide Fleet Fuel Logs Fuel Tax SmartCOP (AA-16) Detailed Crash Analysis (Excel files) Crash data Crash data Safety Scour Analysis Vehicle Inventory, usage Status and History AgileAssets Safety Analyst Montana Accident Reporting System (MARS) Grade Crossing Animal Carcass Asset inventory, condition and treatment information Bridge plans and projects EMS and Conviction Data (AA-11) ADA Inventory Grants & Asset Data Safety projects Pavement performance Data, plans and projects Integrated Asset Management System (AA-10) Maint. Plans and projects Ancillary Assets (Inv, Loc, Attributes) Labor, Equip, Materials Other asset needs, priorities Agile Assets Maintenance Manager Railroad crossing database Guardrail, Striping,Barriers / Attenuators Radio Towers / Communication Assets Ramps, Crosswalks, ADA, ROW/Utility (AA-4), Permits Ancillary Assets Agile Assets (Phase 2) Ancillary Assets Federal and State Reporting Outdoor Advertising (AA-15) Signals, Signs, Overhead Lighting & Structures Drainage Pipes and Small Culverts Dynamic Message Signs (DMS) Load restrictions information Project time charges NBI Department of Public Safety Systems Operations Management Permit Data Agile Assets Maintenance Manager Location Reference Productivity Tools Project data, data reporting Case Management (AA-26) Transport Info Sys / LRS (Esri Roads and Highways) (AA-3) Productivity Tools MODCOMP (Reflection Analysis) Business Support and Technology Support CADD / 3D (AA-7) TIS/Road Log Roadway Information System Esri Traveler Info Sys (AA-14) Fixed Assets Traffic Count Document Management System (AA-2) (AA-24, Records Management) (TA-5, Collaboration Tools) Business Intelligence (BI) and Data Warehouse (DW) (DA-2) Finance (AA-19) Finance / Accounting (AA-20 ERP) BDS Budget Dev. System HR / Time and Leave (AA-22) (AA-23) MMOS Payroll Procure ment Contract Management (AA-21) Manual Tool Automatic Interface Existing Systems Legend Recently Implemented Systems (3 years) Automation for larger entities OR Semi-automation Planned Systems 20

21 21

22 Highlights of Recommendations Enterprise Resource Planning (ERP) System Enterprise Contract Management System Next Generation TIS/LRS Next Generation PPMS Enterprise Asset Management System Strategy AASHTOware TM Construction and Materials e-construction Enhanced Traveler Information System Enterprise Content Management Data Governance Data Warehouse/ Business Intelligence Technology Governance 22

23 Enterprise Asset Management Systems Strategy Opportunity MDT has implemented/is implementing various best in class asset management tools No defined strategy for integrating individual asset management applications Recommendation Define an asset management systems strategy to: Provide data integration between individual asset management systems (bridge, pavement, safety and the next generation maintenance management system) Establish a home system for ancillary assets Support agency business requirements defined in the MDT transportation asset management plan 23

24 Enterprise Asset Management Systems Recommended Initiatives Implement asset data repository linking existing asset information Establish asset data governance Identify assets to be registered Establish owners Confirm home system(s) Migrate ancillary assets into AgileAssets in phased approach Evaluate future asset analysis needs and monitor vendor capabilities 24

25 e-construction Opportunity Current design models don t utilize available technologies Red-lining tools Integration with GIS Use of these technologies can improve review, final acceptance and asset management integration Recommendation Re-engineer As-Built process to utilize available technologies Incorporate model-centric design + GIS and asset management requirements Begin piloting and phased deployment based on established strategy 25

26 Enterprise Content Management (ECM) Opportunity Document Management System (DMS) is at end-of-life Significant requirements for ECM functionality across MDT Engineering is currently undertaking a requirements effort Focused on CAD, not enterprise-wide in nature Recommendation Complete time sensitive Engineering project to address DMS end-oflife Define an ECM strategy to meet all agency requirements Solution may involve multiple COTS products Document collaboration (project-specific) vs. Enterprise DMS Solution should leverage existing State investments 26

27 ECM Components Document Management Web Content Management Records Management Imageprocessing Applications Social Content Content Workflow Extended Components Mobile Applications, Digital Asset Management, search, analytics and packaged integration (such as portals, CRM, or ERP) 27

28 Data Governance Opportunity Need for a greater emphasis on data stewardship and data sharing between and across functional areas Recommendation Establish a data governance initiative to implement industry best practices Data governance, data standards and data stewardship 28

29 Data Governance 101 Business function that develops and executes plans, policies, practices, and projects that acquire, control, protect, deliver, and enhance the value of data and information Information is one of the four basic resources Information First, Technology Second Data Governance goes hand-in-hand with EA as part of an integrated governance structure 29

30 Data Governance Methodology Roles (Data Architect, etc.) Rules Standards The process is iterative and intended to be executed over and over each time improving information management maturity (IMM) Policies Principles Controls Processes Data Architecture Reviews DMBOK Training 30

31 31

32 Implementation Plan Prioritization of recommendations Order-of-magnitude cost estimate for each recommendation High-level work plan for each recommendation Program-level work plan Anticipated benefits Risk management plan 32

33 33

34 Implementation Risks/Challenges IT Convergence and other State level initiatives Federal compliance MDT budget constraints MDT resource constraints 34

35 Anticipated Benefits of EA Structured documentation of an organization s business drivers Improved planning and decision making Improved communication and collaboration Process standardization and business efficiencies Improved sharing of information across the enterprise Consistency, accuracy, availability and timeliness of information Structured technology investment process Better leveraging and management of MDT s technology spend 35

36 Next Steps Initiate governance and process activities IT governance Data governance 36

37 37