1 Constructing WMATA’s Enterprise GIS: Strategy, Action, Issues Washington Metropolitan Area Transit AuthorityConstructing WMATA’s Enterprise GIS:Strategy, Action, IssuesEd Wells, GIS ManagerAnurag Mehta, GIS ArchitectGIS in Public Transportation ConferenceOctober 13, 2011
2 Present WMATA case study in implementing an enterprise transit GIS PurposePresent WMATA case study in implementing an enterprise transit GISSetting strategyReengineering business processesBuilding on legacy data assetsDelivering and maintaining GIS in a dispersed agencyIntegrating GIS with other IT applications
3 WMATA: Scope and Scale of Services Provides passenger transit rail, bus and paratransit services for DC and surrounding areas of MD and VA (1,500 sq mi).Rail: 103 mi track; 86 stations; 850 railcars; 217M annual ridershipBus: 350 routes; 1,480 buses; 124M annual ridershipParatransit: 600 vehicles; 2.4M annual ridershipPolice force; planning; real estate; environmental responsibilities
4 WMATA GIS Purpose and Role Purpose: Enterprise GIS integrates mapping and databases to support consistent information across the enterprise, efficient operations, and informed stakeholders.Role: GIS is a service, not an application.GIS owns few business processes andsupports many:Geographic data base displayGeographic analysisGeographic data captureData integrity testingData integrationGIS
5 IT Span of GISSoftware – ESRI ArcGIS (upgrading to 10 this year)HardwareProduction, staging, dev environments; education and map production environmentsManaged storage (SAN and NAS)ApplicationsDataIntegration – Maximo and Trapeze in progressWeb services – Agency-wide intranet viewerBusiness processesUser support
6 GIS Current Role Enterprise system System of record and data maintenanceAll mapping dataBus stop and route attributesSystem integration driverData integration driverGeographic and RDBMS data integrity enforcement driverData display and analysis tool
7 GIS Viewer: Key Points Web viewers vs. ArcGIS client software Scale: Entire service area to engineering detailCore DataAll mainline and yard trackRail station platforms and entrancesBus stops and routesCompact jurisdiction boundariesBase maps and imageryBasic functionality: Search, identify, measure, printWeb service links:Public services: Google StreetView, Bing imageryWMATA internal: Maximo, other applicationsDocument retrievalSketch tools
8 GIS Development Chronology 2007-2011 FY08 Strategic plan FY09 Enterprise Architecture Enterprise GIS software installation; as-is data loading FY10 WebADF GIS web viewer and core data FY11 Flex GIS web viewer Integrated bus stop and route database Bus stop and route data posted to public web site Rail linear referencing system for mainline track Began integrating GIS with asset/work order management system (Maximo)
9 Rail, Bus, Van, Road Network Setting Strategy: A Portfolio ApproachStrategic Portfolio of GISParcelFacilityAmenityRail, Bus, Van, Road Network40% Fixed AssetManagement40% Transit OperationsStops, time points, chain markers, waypointsPatterns, routes, lines, transfersPerformance (vehicles, trips, blocks)20% Support OperationsMTPD, Plan, Real Estate; Environmental, IT
10 Building Alliances Across Departments PrinciplesIT is a support departmentKeep the domain expert in charge of information decisionsKeep IT in charge of data and system architecture decisionsLessonsDo not start applications unless the data is compiledDo not compile data you are not prepared to maintainWhat is the business process?What is the IT process?Make it easy for the domain expert to feed information to the GIS staffUse the maintenance process to drive business process reengineering
11 Business Process Reengineering Business Process Reengineering: The PayoffUse the maintenance process to drive business process reengineeringWork incrementally:Add GIS to the existing data flow at firstLet GIS become the source for authoritative dataThen build GIS data maintenance into a revised workflowUse the interim process to define more automated interfaces and applications
12 Legacy Data Assets Legacy Data Are An Asset Choices Keep what is good Compile newConvert one existing data sourceConvert multiple sources, cross-check, and reconcile the discrepanciesKeep what is goodUse geography to cross-check legacy data and reconcile multiple data setsBreak down the silosAim toward consistent information across the enterprise
13 Enterprise GIS Architecture: Business Considerations Key Business NeedsServe available dataCAD data, documents, GIS dataAdd geographic valueMake simple apps availableDesktop software, web viewers, dashboards, reportsDefine and set standards/practice/key datasetsMetadata, QA tests, common base layers, remove duplicationEnable mobile architectureHand-held devices, versioning
15 Five Components of Enterprise Architecture Design Architecture Strategy and DesignWhat are the information flows and standardsInfrastructure and Systems ArchitectureHow will physical realization occur, how will users interactData ArchitectureWhat data will be stored, reportedProcess ArchitectureHow will data be maintained and standards enforcedApplications ArchitectureHow will information be used, how will value addition occur
16 WMATA Enterprise GIS Architecture Architecture DesignServices Oriented ArchitectureSOAP compliant web servicesIntegrate with Enterprise Services via Enterprise BusSupport nimble Applications Arch.: Mashups, API overlaysFlexible presentation layer – lots can happen at interface levelEg: Track Signal (Asset) and GIS
18 WMATA Enterprise GIS Architecture Infrastructure and Systems ArchitectureSeparate Data and Application NodesData node: support for spatial functions and SQLnet callsData node supports Application node via SQLnet serviceApp node: hosts web services and web applicationsBoth nodes expose APIsIllustration of a SQL function call:SELECT bt.bus_idfrom bustable bt, counties ctwhere bt.avltime=(SELECT CURRENT_TIMESTAMP from DUAL) andct.name = ‘Arlington’ andsde.st_within (bt, ct) = 1;
22 Delivering GIS Across the Enterprise Web services and Web APIs to make the GIS accessible to non-users agency-wideDeploying and administering client ArGIS software for power usersThe center of the enterprise:ServersStorageRedundancySecurity
23 Application Integration Key Integration PointsRail, Asset Management: Plant, Elevator/Escalator, Power, ATCS, AFCS, Track and Structure Maintenance, IT-CommunicationsApplications: Maximo, AutoCADBus: Bus Planning, Scheduling, Bus TechnologyApplications: Maximo, Trapeze, Clever, Trip Planner, FareboxSupport: MTPDApplications: Dispatch, Crime Records
24 Application Integration Choices Levels of IntegrationDataSoftwareBusiness processMethods of IntegrationWeb servicesData synchronization
25 Program / Project Overview Major FY12 Task GroupsTG1: ArcGIS 10 – Oracle 11g – Windows 2008 upgrade; CTF failoverTG2: GIS-MMMS integration: design, software implementation; dataTG3: Transit route network: software tools; constructionTG4: Intranet: AVL, APIs, integration servicesTG5: Public website enhancements: bus stops and routesTG6: Building interior mapping: floor plans, 3-DTG7: User support, metadata, and trainingTG8: Mobile GIS
26 TG 1: ArcGIS 10 UpgradeGoal: Conform to IT standards by upgrading GIS software to ArcGIS 10, Oracle 11, and Windows Add failover servers at CTFBenefits: Supports Maximo 7.5 upgrade (incompatible with ArcGIS 9.3.1); failover provides continuity of operations even if JGB is offlineCost: $378,971Deliverables/Timeline:7/11: ArcGIS 10 dev environment in operation3/12: CTF failover for production environment in operation6/12: ArcGIS 10 production environment in operationRisks/Mitigation:If Maximo 7.5 upgrade is delayed, ArcGIS 10 upgrade will be too. Mitigation: Continue using during the interimKey tools may have different upgrade schedules. Mitigation: Plan to maintain two versions with redundancy for several months
27 TG 2: GIS-MMMS Integration Goal: Ensure consistent asset inventories between GIS and MMMS; provide mapping capabilities to MMMS.Benefits:Safety: what is near an emergency that must be protected?Efficiency: Improved deployment and reduced travel timeDeliverables/Timeline:8/11 – Geodatabase design implemented; data conversion plan defined12/11 – Maximo Spatial in development environment6/12 – Key asset classes mappedRisks/Mitigation:Maximo Spatial has few large installations; none under 7.5; and none for transit. Mitigation: Retain good consultants that can resolve unexpected problemsLegacy data may be inconsistent/incomplete> Mitigation: Cross-check all data sets; resolve inconsistencies
28 TG 3: Transit Route Network Goal: From stop and route data, create a routable network of WMATA bus and rail servicesBenefits: Supports integrated maintenance and QC of WMATA stop, timepoint, pattern, and route dataDeliverables/Timeline:10/11 – Evaluate/procure available software tools12/11 – Linear referencing added to bus routes3/12 – Transfer segments added to bus and rail routes6/12 – Network topology added to bus and rail routesRisks/Mitigation:Linear reference networks are complex to build and require specialized software tools to manage. Only one GIS-based vendor is known. Timing of vendor upgrade to ArcGIS 10 is not known. Mitigation: Be prepared to create tools in house if the product is unsatisfactory or too expensive.
29 TG 4: Intranet Improvements Goal: Add functionality and data to GIS viewer. Support Silverlight and Flex APIs. Create web services for application data integrationBenefits: Increased use of GIS viewer within WMATA. Provision of GIS views and map controls to other applications. Consistent data across applications.Deliverables/Timeline:9/11 – Bus AVL and train location data shown displayed in web viewer.9/11 – Silverlight GIS API is available to other applications12/11 – GIS – Trapeze data exchange web service defined and testedRisks/Mitigation:Trapeze data exchange capability is untested. Mitigation: Include QC and verification of data exchange.
30 TG 5: Public Website Enhancements Goal: Add bus stop and route maps to wmata.com website.Benefits: Bus system becomes more familiar to the public. Bus stop data is accessible to MetroAccess customers.Deliverables/Timeline:9/11 - Application available internally12/11 – External security and design complete3/12 – Internal testing of public application6/12 – Application available publiclyRisks/Mitigation:Public interface testing/marketing approval process is not known. Mitigation: Ascertain the approval process. Hold schedule for technical development, but adjust as needed to accommodate approval process.
31 TG 6: Building Interior Mapping Goal: Georeference rail station floor plans and site plans and add to GIS. Create 3-D imagery and floor plans of bus garages (no plans exist now).Benefits: Provides a base for in-station infrastructure mapping. Supports more intelligent crime mapping. Supports betterDeliverables/Timeline:3/12 – Rail station georeferencing procured and completed.6/30 – Bus garage mapping procured and completed.Risks/Mitigation:AutoCAD files for rail station plans have not been reviewed. Mitigation: if data is incomplete, determine how best to create or update it.3-D mapping is new technology. Mitigation: one pilot test has been done.3-D data requires a custom data viewing add-on. Upgrade plans to ArcGIS 10 are not known. Mitigation: Defer action until WMATA and vendor upgrade plans are known.
32 TG 7: User SupportGoal: Support GIS use in WMATA departments via tech support, creation of map publications, metadata, and training courses.Benefits: Use justifies WMATA’s investmentsDeliverables/Timeline:12/11 – Bus route map series completed3/12 – Training course offered in WMATA GIS resources and use6/12 – Training course offered in basic GIS concepts6/12 – Complete metadata compiled for all feature classes shown in the web viewerRisks/Mitigation:Hiring restrictions preclude adding FTEs. Mitigation: Use contract services, and/or adjust goals to fit reduced capacity.
33 Questions and Discussion Washington (DC) Metropolitan Area Transit AuthorityEd Wells,Anurag Mehta,