GGISIS Int Integraegratiotion n wwiithth E Entntererprise ... · PDF fileGGISIS Int...
Transcript of GGISIS Int Integraegratiotion n wwiithth E Entntererprise ... · PDF fileGGISIS Int...
Colorado Department of Transportation Colorado Department of Transportation GIS Integration with Enterprise Resource GIS Integration with Enterprise Resource
Planning (ERP) Implementation Planning (ERP) Implementation
Marvin Marvin Koleis Koleis, Colorado Department of Transportation , Colorado Department of Transportation
Michael Michael Wierzbinski Wierzbinski, , Farragut Farragut Systems Inc. Systems Inc. March 27, 2007 March 27, 2007
Presentation Focus Presentation Focus
• CDOT’s business processes and the GIS touch points in the ERP implementation
• Identify the technology stack (software and hardware)
• Implementation successes • Challenges and future directions
ERP Goal ERP Goal
Materials Management
• Enterprise Resource Planning
• Replace more than 50 standalone customdeveloped software systems, primarily in human resources and financial, with a new integrated system that will allow us to meet our business and information needs much more quickly and accurately.
ERP Components: ERP Components:
• Timesheets • Funds Management • Federal Aid Billing • Project Scheduling & Asset Management • Budget • Materials Management • Real Estate • Plant Maintenance • Finance • Inventory
ERP Timeline ERP Timeline • BPR Teams Formed (Fall 2004)
• GIS Contractor Selection – Farragut Systems Inc. (May 2005)
• ERP Software Selection SAP (June 2005)
• Integrator Selection – Deloitte LLC (June 2005)
• IV&V Selection – Solbourne (June 2005)
• LRS Unification Project Begins (October 2005)
• SAP Project Kickoff (September 2005)
ERP Timeline ERP Timeline (cont (cont’ ’d) d)
Phase 1 ‘Go Live’ Human Resources April 2006
Phase 2 ‘Go Live’ November 2006
CDOT / Deloitte Integration Timeline
GIS Goals GIS Goals
• Lightweight Simple mapbased Web Interface • MAPS2 Replacement • One GIS Interface • Display and Query Project Information • One departmental LRS • LRS Coordination and Business Rules
GIS Goals (cont GIS Goals (cont’ ’d) d)
• Easy access to GIS data • Minimal training required • Mapbased selection for enterprise reporting facilities
• Roundtrip integration with SAP (Project locations and SAP attributes generated by geo spatial processing)
GeoMAP GeoMAP / SAP Business Process Flow / SAP Business Process Flow
SAP R/3
SAP B/W BDW
5
1
4
3
Geo DB Publishing
Geo DB Editing
GeoMap Application
Rattler
2C
2B
2D
2A
6
GeoMAP GeoMAP / SAP Business Process Flow / SAP Business Process Flow
1) Extract project related data from SAP into BDW 2a) Extract project related data from SAP R/3 PS into CSV File 2b) Rattler Program
2c) Rattler Program 2d) GeoDatabase Publishing 3) Display Project Layer in GeoMap 4) Display List of Projects for Editing
5) Update Project related data in SAP R/3 PS
6) Display reports from BDW
Challenges Challenges Painting a Moving Car Painting a Moving Car
• Evolving Enterprise Architecture – WebSphere and SAP became enterprise required architecture standards after the project started
– Adapting a design to a changing environment can be done • Not easily • Not with out costs (resources, time, dollars)
– Flexibility of participants is key – Program Management give and take
Too much to chew Too much to chew
• Enterprise reporting deferred to phase 2 – DBA staff fully occupied with SAP deployment – SAP is changing the way CDOT looks at (and measures) its business
– Decided to wait until reporting requirements were better understood before integration with GeoMap
– ArcGIS Server may impact reporting architecture
LRS Discrepancies LRS Discrepancies Synchronization of Routes, Beginning and Ending Reference Points, Facility Limits, Total Lengths and Matching Intermediate Segmentation
Detailed Proposal and Description Expand our data entry and QC effort to sync up and consolidate with the Traffic Safety and MMS data systems. This will be a programming, editing/data collection effort that will take realtime highway measurements and the adoption of roadway miles including frontage roads and flyover connection ramps and extensions that are owned and maintained by the state of Colorado.
Project Goal The goal of this project to provide a product that is more useful to state wide customers. The LRS effort will produce matching data segmentation for project development, field construction, safety, FHWA reporting as well as asset management and planning. We will also set in place future change management controls to help keep cross systems in sync. Once the GIS model is in full compliance customers and owners of collaborating systems operate from a common data source.
Benefits to Users With the (LRS) matching the field limits (or Full Coverage) our GIS data model will support facilities and asset management, work orders, work flows, project costing, project scheduling and detailed job tracking. The current model can not supply functional locations within the states ROW.
Data Sets being Consolidated . . . DTD/GIS (Transys), MMS, Traffic Safety’s (TCORIS)
–Goal: to standardize on one Linear Referencing System across all business units within the Department –Project includes staff from Transportation Development, Maintenance Management and Traffic Safety
Technical Resources: Technical Resources: GPS Field Work, GPS Registered AutoCAD, Video Imagery GPS Field Work, GPS Registered AutoCAD, Video Imagery
and Aerial Photography = Data Accuracy and Aerial Photography = Data Accuracy
Historic CORIS Segment Measures Historic CORIS Segment Measures Mile Groups & GPS imagery Mile Groups & GPS imagery
Statewide GPS Centerline Adjustment Statewide GPS Centerline Adjustment In terms of spatial accuracy our GIS Onsystem features have been optimized in this migration/restructure. The vector data has been spatially analyzed or glued to corrected GPS provided by MMS.
We now have Anchor Point stations and meaningful Centerlines.
GPS’ed
Non GPS’ed
GIS Goals GIS Goals – – Hits and Misses Hits and Misses
• One departmental LRS • LRS Coordination and Business Rules • Lightweight Simple mapbased Web Interface • Display and Query Project Information • MAPS2 Replacement • One GIS Interface
GIS Goals GIS Goals Hits and Misses (cont Hits and Misses (cont’ ’d) d)
• Easy access to GIS data • Minimal training required • Mapbased selection for enterprise reporting facilities
• Roundtrip integration with SAP (Project locations and SAP attributes generated by geo spatial processing)
Futures Futures
• Implement Enterprise Reporting • Migration to ESRI ArcGIS Server
– Inline with CDOT/ESRI strategies • Deliver GeoMap Services to both Intranet and Internet audiences – LRS Services – Pavement Condition/Digital Video Logs