A Case Study from Phoenix Sky Harbor. April 29, 2009

Transcription

1 Implementing ArcGIS Server as a Hub within an Enterprise Architecture A Case Study from Phoenix Sky Harbor International Airport Dave Feuer Dave Feuer April 29, 2009

2 Objectives of Aviation Geospatial Technology Programs Airports GIS? Leased space accurate financial information As-builts information Maintenance and Asset Management Systems. Catalog assets for cost accounting Condition assessments Additionally, FAA and Aviation Organizations Efficiently plan for and maintain the air transportation system. 405 obstruction survey information on a larger scale

3 Objectives of Aviation Geospatial Technology Programs Aviation GIS provides the foundation for connecting the airports, FAA, and statewide aviation organizations by creating a central database for storing survey, charting, analysis, and planning data. Federal Aviation Administration

4 City of Phoenix, Arizona Department Of Aviation

5 Phoenix Background Airport facilities owned by the City of Phoenix Phoenix Sky Harbor International Deere Valley Goodyear Williams Gateway Sky Harbor International 9th busiest US Airport 3,000 Acres inside the fence 3.5 million square feet in 3 terminals 30,000 parking spaces 31,000 jobs

6 Sky Harbor International $3 B in Planned Enhancements

7 Project Components Extensive Project Management Requirements Project and Process Documentation Hardware and Software Massive Data Development Enterprise Systems Development Comprehensive Portal 16 Additional Applications Testing, Training, Documentation, Warranty Services

8 Project & Process Documentation ti Standards Aerial Photography Coordinate System Spatial Data Metadata CADD Geodatabase Design Exterior Airside (ie: runways) Exterior Landside Interior and Exterior Utilities Interior Floor Plans and boundaries (ie: sprinkler heads, toilets ) Planning, community and environmental Macro Micro

9

10 Lessons Learned Project & Process Documentation 1. Importance of standards particularly when integration is envisioned. Ie: Lots of aerials noise contours, looking at valve covers 2. Only build what you plan on maintaining understand d how data will be used. Question, question, question

11 Data Development Options A Create Features from Plans with no Field Work (ie: fountains) Estimated % of Data Meeting Accuracy Requirements B Create Features from Plans where Available and Collect Remainder in the Field C Create Critical Features in the Field, Remainder from Plans or Field D Create all Features in the Field (ie: defibrillators) 96-98

12 Data Development Standardize on Data Presentation No ready-made symbols for internal assets

13 Lessons Learned Data Development 1. Determine accuracy requirements by developing an understanding of how data will be utilized.classify the level of effort 2. Data development is not an either/or proposition beg, borrow, steal, horse trade 3. Factor in visualization requirements prior to data development (pilots work best)

14 Hardware & Software Considered critical, but not a life safety related system. Needed d to fit within overall business continuity plan for City Offsite redundancy and failover Scenarios would be tested

15 Hardware & Software

16 Lessons Learned Hardware & Software 1. Involve the vendors all of them. Their success is based on your success.

17 Enterprise Systems Development

18 Building Navigator

19 Enterprise Systems Development Door Alarms

20 Not Just a Web App

21 Aerial Photo Management

22 Integration ti with Critical Systems

23 Enterprise Systems Development

24 Enterprise Systems Development

25 Enterprise Systems Development Account for Change and Growth Visualize spatial data Gather user input Display tabular results Print Map Extract Buffer Get Attributes Enterprise Service Bus Query Ping GIS Get WO Ping Scheduling Enterprise GIS (ESRI) Work & Asset Mgmt (SAP) Document Imaging Project Scheduling (Microsoft (Primavera) EPM)

26 Approach Benefits Obvious Improved scalability Adapts well to change in systems Adapts well to system upgrades Not So Obvious Better performance Friendlier user experience Easier to maintain

27 Lessons Learned Enterprise Systems Development 1. Importance of an agile development methodology. 2. Importance of a structured testing and deployment approach. 3. Benefits of a service oriented approach to support integration.

28 Surprise Uses Visualization

29 Lessons Learned Surprise Uses 1. Keep your eyes and ears open py y p opportunities for creating additional champions can arise at any time.

30 Project Results Viewed as model project for City of Phoenix and in airport industry Processes Technical Architecture t Design (Business Continuity) it Completeness of data and applications Quality

31 Questions/Discussion i Thanks for your time! Dave Feuer dave.feuer@woolpert.com