pacaf geobase: internet mapping framework imf and airfield obstruction system aobs

1. As of: 03 Oct 2006 1 PACAF GeoBase: InternetMapping Framework (IMF)and Airfield Obstruction System (AOBS)

2. 2

3. 3 A Broken System No standard obstruction submission process Software commonly used by USAF for airfield obstruction management became obsolete & non-maintainable in 2004 Previous solution relied on expensive and maintenance prone �thick client� software (ArcMap)--$3K per PC Many planners still tracked obstructions manually due to complexity of system Existing obstruction data bases contained deficient data due to complexity of previous solution The previous system (AOMS) became non-maintainable with the release of Access 2003 and subsequent adoption by the USAF as the standard; the reason for this was AOMS was software imbedded in the Access 2000 data base as �macros�; a security compromising software strategy eliminated by MS with Access 2003. Quote $550K-$1M to fix �Thick client� means that you have to purchase software for every desktop computer that is running the system. With AOMS it meant a $3000 license for every desktop. Additionally, you have the issues associated with maintenance of the software every time there is an upgrade. The AOMS system was very complex requiring planners to have a good working knowledge of ArcMap and Access data bases. Many of our planners did not have this background nor the funding or access to training required. The training provided by the AOMS contractor �assumed� that all planners had this knowledge or aptitude. Not true. Much of our existing obstruction data was erroneous due to the complex nature of adding and modifying records. Also, on original deployment by the AOMS contractor, much erroneous data was included due to their lack of familiarity with airfield obstruction regulations as well as base specific issues. Your Notes: AOMS desktop solution vice AOBS web-based solution Airfield managers have to go to Community Planner�s desktop to view AOMS still relying on ArcMap @ $3K Install in 2000 w/ some trng and manuals. In 2003 the Microsoft 2003 came out. AOMS could not use Access 2003 without a $550K for PACAF and $1M for AMC. Complete rewrite�security challenges� The previous system (AOMS) became non-maintainable with the release of Access 2003 and subsequent adoption by the USAF as the standard; the reason for this was AOMS was software imbedded in the Access 2000 data base as �macros�; a security compromising software strategy eliminated by MS with Access 2003. Quote $550K-$1M to fix �Thick client� means that you have to purchase software for every desktop computer that is running the system. With AOMS it meant a $3000 license for every desktop. Additionally, you have the issues associated with maintenance of the software every time there is an upgrade. The AOMS system was very complex requiring planners to have a good working knowledge of ArcMap and Access data bases. Many of our planners did not have this background nor the funding or access to training required. The training provided by the AOMS contractor �assumed� that all planners had this knowledge or aptitude. Not true. Much of our existing obstruction data was erroneous due to the complex nature of adding and modifying records. Also, on original deployment by the AOMS contractor, much erroneous data was included due to their lack of familiarity with airfield obstruction regulations as well as base specific issues. Your Notes: AOMS desktop solution vice AOBS web-based solution Airfield managers have to go to Community Planner�s desktop to view AOMS still relying on ArcMap @ $3K Install in 2000 w/ some trng and manuals. In 2003 the Microsoft 2003 came out. AOMS could not use Access 2003 without a $550K for PACAF and $1M for AMC. Complete rewrite�security challenges�

4. 4 Airfield Obstruction Solution Keep It Simple Use existing PACAF GeoBase standards and capabilities: No new or custom software! One base, one map (previous solution used personal data base for planner which was not synchronized with base CIP) Develop business process where planners would be responsible for obstruction identification/analysis and Geo Integration Office (GIO) would be responsible for graphic data Scrub all existing obstruction data bases as integral part of the Airfield Obstruction System (AOBS) deployment In January 2006, PACAF A7PB and A7OG agreed that the best solution was to use existing GeoBase tools go web-based vs. using the proprietary software solutions that created previous problems. GeoBase was already an investment! Previous AOMS solution had stand alone map on PC not integrated into the PACAF GeoBase map layers. Planners only worry about identifying obstructions and interpreting criteria. The GIO provides support through spotting obstructions on the map and providing links to the data. As part of the AOBS deployment, all data was reviewed and scrubbed prior to loading it in the system. Do it right begin with! Your Notes: No CAC protection in Internet Mapping Service. CAC login credentials provide the edit and/or read/write rights. Integration tool, like going from DOS to Windows In January 2006, PACAF A7PB and A7OG agreed that the best solution was to use existing GeoBase tools go web-based vs. using the proprietary software solutions that created previous problems. GeoBase was already an investment! Previous AOMS solution had stand alone map on PC not integrated into the PACAF GeoBase map layers. Planners only worry about identifying obstructions and interpreting criteria. The GIO provides support through spotting obstructions on the map and providing links to the data. As part of the AOBS deployment, all data was reviewed and scrubbed prior to loading it in the system. Do it right begin with! Your Notes: No CAC protection in Internet Mapping Service. CAC login credentials provide the edit and/or read/write rights. Integration tool, like going from DOS to Windows

5. 5 GeoBase Internet Mapping Framework (IMF) Screen Shot PACAF GeoBase set up the first web-based Internet Mapping Framework (IMF) that gives end users online editing. IMF makes GeoBase work better because it is an integration tool that pulls others databases into one map and allows users to analyze the data in one location. It�s like going from DOS to Windows. It provides improved situational awareness and customized mission management capabilities. Front Page to get to data and read or update data. CAC protected, Geo office at base gives access rights for read, read write, etc. PACAF GeoBase set up the first web-based Internet Mapping Framework (IMF) that gives end users online editing. IMF makes GeoBase work better because it is an integration tool that pulls others databases into one map and allows users to analyze the data in one location. It�s like going from DOS to Windows. It provides improved situational awareness and customized mission management capabilities. Front Page to get to data and read or update data. CAC protected, Geo office at base gives access rights for read, read write, etc.

6. 6 IMF Tools Email Red Line Mark Up Create Maps Save Sessions Share Sessions Extract to Excel/PDF Edit master database Within IMF, tools exist that allow for collaboration and workflow management. Within a file session, you can manipulate the data, save the changes or markups and email it to any users, on the access control list, for collaboration. Users can create and print high quality map products in .pdf�s (like the screenshot) which are a much smaller file size in comparison to the old .dwg files Your Notes: Can choose different size files Within IMF, tools exist that allow for collaboration and workflow management. Within a file session, you can manipulate the data, save the changes or markups and email it to any users, on the access control list, for collaboration. Users can create and print high quality map products in .pdf�s (like the screenshot) which are a much smaller file size in comparison to the old .dwg files Your Notes: Can choose different size files

7. 7 IMF Benefits Enforces data integrity Reduces licensing costs Provides service to cross-functional communities Utilizes AF CAC card for security Gives data ownership to functional communities Aligns AF business processes Web-based COTS software allows editing of multiple databases Offers rapid capability deployment 2 weeks to create AOBS tool and 6 months to field & implement it across PACAF IMF has the ability to provide drop down list of standard data eliminating the chance of user error (FORM 48) Reduces the need for expensive editing software at every workstation It can support across the Wing Meets AF security requirements Allows functional communities to edit their own data and controls who has access to the data. IMF aligns AF business processes Web-based COTS software allows direct editing of multiple databases IMF is series of ready made tools for developers to mix and match to build website solutions rapidly. Your Notes: GeoBase is central collection pt. IMF is the �universal translator� or like internet explorer All AF Class B r/w�s including Eareckson and Wake First time confidence in database USAFE through portal IMF=web-based COTS software which is a collection of script/code which allows direct editing into multiple databases from a single pt. SDS�std database languageIMF has the ability to provide drop down list of standard data eliminating the chance of user error (FORM 48) Reduces the need for expensive editing software at every workstation It can support across the Wing Meets AF security requirements Allows functional communities to edit their own data and controls who has access to the data. IMF aligns AF business processes Web-based COTS software allows direct editing of multiple databases IMF is series of ready made tools for developers to mix and match to build website solutions rapidly. Your Notes: GeoBase is central collection pt. IMF is the �universal translator� or like internet explorer All AF Class B r/w�s including Eareckson and Wake First time confidence in database USAFE through portal IMF=web-based COTS software which is a collection of script/code which allows direct editing into multiple databases from a single pt. SDS�std database language

8. 8 IMF Deployment Cost Prior Investments: Highly skilled contractors at the base that can support the technology Hardware Software (e.g. IMS) Spiral 5 � IMF deployment cost Labor: $129,348.00 Travel: $39,476.00 ODC: $166,177.00 TOTAL: $335,000.00 Two Person teams for Spiral 5 - (One individual costs 'sunk' from existing contract) 9 enterprise licenses of IMF (Enterprise license = unlimited installs within domain (i.e. Hickam.af.mil) Your Notes: $20K/site license ~ $160K 42 to 37 by Jun 07 Also, 2 of the positions are unit funded We bought storage capability Two Person teams for Spiral 5 - (One individual costs 'sunk' from existing contract) 9 enterprise licenses of IMF (Enterprise license = unlimited installs within domain (i.e. Hickam.af.mil) Your Notes: $20K/site license ~ $160K 42 to 37 by Jun 07 Also, 2 of the positions are unit funded We bought storage capability

9. 9 Airfield Obstruction System � AOBS� First use of Internet Mapping Framework (IMF) capability with a functional user A7O/A7P established partnership Simplify the process of airfield obstruction data updates; created electronic waiver packets Single interface, integrated, web-based database with standardized forms Verified & photographed all existing obstructions First time high confidence in data The perfect opportunity arose with the AOBS initiative. GeoBase leveraged the IMF web tool for the first time in conjunction with setting up the Airfield Obstruction mission data layer. GeoBase partnered with A7P to develop web-based interface to manage airfield obstructions (AOBS). The airfield obstruction updates was simplified with the creation of the electronic waiver packet, PACAF Form 48, which is the interface that the planners see to update their airfield obstruction data. Then they deployed the capability to PACAF planners at 9 Main Operating Bases (MOB�s), Earackson and Wake, trained them, and verified locations of existing obstructions within 6 months. A7P has high confidence in their airfield management program for the first time ever. (PACAF/CV signed memo for airfield obstruction removal to Wing Commanders, dated 15 Mar 06, SUBJ: Recent Mishaps and Responsibilities for Airfield Obstruction Removal)The perfect opportunity arose with the AOBS initiative. GeoBase leveraged the IMF web tool for the first time in conjunction with setting up the Airfield Obstruction mission data layer. GeoBase partnered with A7P to develop web-based interface to manage airfield obstructions (AOBS). The airfield obstruction updates was simplified with the creation of the electronic waiver packet, PACAF Form 48, which is the interface that the planners see to update their airfield obstruction data. Then they deployed the capability to PACAF planners at 9 Main Operating Bases (MOB�s), Earackson and Wake, trained them, and verified locations of existing obstructions within 6 months. A7P has high confidence in their airfield management program for the first time ever. (PACAF/CV signed memo for airfield obstruction removal to Wing Commanders, dated 15 Mar 06, SUBJ: Recent Mishaps and Responsibilities for Airfield Obstruction Removal)

10. 10 Simplified InterfacePACAF Form 48 The old system had separate systems; one for the data base and one for the map (you could only work one system at a time). The new AOBS system has an integrated screen where both data and map are viewed and accessible simultaneously. Airfield waiver editing allowed through the standard PACAF Form 48. Your Notes: Previously, AOMS had over 60 data tables. Now you have 2 tables. Lots of table referencing another tableThe old system had separate systems; one for the data base and one for the map (you could only work one system at a time). The new AOBS system has an integrated screen where both data and map are viewed and accessible simultaneously. Airfield waiver editing allowed through the standard PACAF Form 48. Your Notes: Previously, AOMS had over 60 data tables. Now you have 2 tables. Lots of table referencing another table

11. 11 AOBS Screen Shot of Hickam AFB Mapping/Obstruction Viewer Tool Data on left, each waiver drop down menu w/ associated obstructions, map on right, all tools available and visible together. The AOBS tool was the first graphic/data airfield obstruction management tool of it�s kind in the Air Force.Data on left, each waiver drop down menu w/ associated obstructions, map on right, all tools available and visible together. The AOBS tool was the first graphic/data airfield obstruction management tool of it�s kind in the Air Force.

12. 12 AOBS Screen Shot of Hickam AFB Obstruction Identification This screen shows a specific obstruction highlighted on the map along with all data associated in the GeoBase data tables. The data on the left includes the obstruction�s coordinates, height, structure name or type, owner, etc.This screen shows a specific obstruction highlighted on the map along with all data associated in the GeoBase data tables. The data on the left includes the obstruction�s coordinates, height, structure name or type, owner, etc.

13. 13 AOBS Screen Shot of Hickam AFBObstruction Photos This screen shot shows the capability of AOBS to link photos of the obstructions to the highlighted obstruction on the GeoBase map.This screen shot shows the capability of AOBS to link photos of the obstructions to the highlighted obstruction on the GeoBase map.

14. 14 AOBS Screen Shot of Hickam AFB Measuring Distance to Obstruction This screen shows the measurement tool for analyzing obstructions. The red line on the map was drawn from the obstruction, Bldg 2050 to the center line of the adjacent peripheral taxi lane. On the left hand side you can see the mapping coordinates of the start/stop point of the line along with the distance. In this case the distance is 145.4 feet. Analysis of airfield criteria indicate this is only an obstruction for the C-5 aircraft which has a minimum clearance of 162 feet. Since no C-5 will use this spot, eliminated the obstruction. Old UFC said base on C-5; new UFC says most demanding aircraft on DV ramp at Hickam will never be a C-5.This screen shows the measurement tool for analyzing obstructions. The red line on the map was drawn from the obstruction, Bldg 2050 to the center line of the adjacent peripheral taxi lane. On the left hand side you can see the mapping coordinates of the start/stop point of the line along with the distance. In this case the distance is 145.4 feet. Analysis of airfield criteria indicate this is only an obstruction for the C-5 aircraft which has a minimum clearance of 162 feet. Since no C-5 will use this spot, eliminated the obstruction. Old UFC said base on C-5; new UFC says most demanding aircraft on DV ramp at Hickam will never be a C-5.

15. 15 Achieving GeoBase Vision Web-based solutions are the way to do business in the 21st century Makes data available from base level to higher HQ�s Responsibilities: GIO - collect new obstructions/spatial data Planner � maintain obstruction attributes Web-based solutions are the way to business because it enables management of lots of data easily all in one location. It makes situational awareness better for the base all the way up to higher HQ�s. The GIO office and end user, the Planner, share the responsibilities. The GIO creates the obstruction data point on the map while the community planner populates associated data tablesWeb-based solutions are the way to business because it enables management of lots of data easily all in one location. It makes situational awareness better for the base all the way up to higher HQ�s. The GIO office and end user, the Planner, share the responsibilities. The GIO creates the obstruction data point on the map while the community planner populates associated data tables

16. 16 AOBS Deployment Project Kickoff: 11 Mar 06 Development Completion: 1 Apr 06 Deployment Dates: 1 May - 29 Aug 06 Project Completion: 30 Sep 06 Before deploying and training the application all existing obstructions data needed to be validated and formatted. Validation was required to ensure the accuracy of data. Formatting was required to ensure the data fit the requirements of the application and enterprise system. Over the course of time data sources existed in many forms and versions, spatially with previous deployment of software, in custom spreadsheets or databases developed individually by planners, etc. Consolidating this information created a mixture of unreliable information. Additionally, many installations had not updated their obstructions data for many years. GeoBase would validate the position of features in the field and supply basic attribution. A7P then visited each installation and worked with the planner to validate and format this data. Before deploying and training the application all existing obstructions data needed to be validated and formatted. Validation was required to ensure the accuracy of data. Formatting was required to ensure the data fit the requirements of the application and enterprise system. Over the course of time data sources existed in many forms and versions, spatially with previous deployment of software, in custom spreadsheets or databases developed individually by planners, etc. Consolidating this information created a mixture of unreliable information. Additionally, many installations had not updated their obstructions data for many years. GeoBase would validate the position of features in the field and supply basic attribution. A7P then visited each installation and worked with the planner to validate and format this data.

17. 17 AOBS Deployment Costs Prior Investments: IMF Deployment Cost: $335,000.00 AOBS Deployment Cost: Labor: $180,792.00 Travel: $62,315.00 ODC: $313.00 AOBS TOTAL: $243,420.00 IMF and AOBS TOTAL: $578,420.00 Air Obstruction Management for nine main operating bases and Wake Island and Earackson Two Person teams for AOBSAir Obstruction Management for nine main operating bases and Wake Island and Earackson Two Person teams for AOBS

18. 18 Lessons Learned Data Scrub All data at all installations required significant amounts of editing The best product developed through teamwork There were a number of common problems Incorrect UFC references Incorrect distance measurements Incorrect classification of violation types Many obstructions had multiple violations Standardized obstruction naming conventions All data at all bases was processed on schedule and under budget. Some anomalies existed in terms of obstruction id�s (AVR is vertical designation but not at all bases), not all bases follow same procedure for multiple violation points � some have extra points in the map while others hold extra violations in the table. Where we find extra violations we recorded in the Form 48. TEAMWORK: The quickest and most accurate AOBS deployments were at installations where the community planner, GIO, and airfield manager worked closely together.� This occurred �during the review and coordination of existing obstruction data prior to the deployment team arriving as well as during the actual deployment data scrub.� Because each of these three team members was looking at the data from different perspectives, a 360 degree view encompassing all aspects of data quality (graphic standards, interpretation of regulations, engineering analysis, and operational realities) was achieved. Sample data changes from Misawa Misawa is an approximate median for changes per installation Originally 1332 records Overall 3846 changes to 882 database records 450 records required no changes A single record may have multiple changes Most changed items Distance from centerline � 503 records Violation distance � 475 Justification � 308 Feature penetration � 200 Priority zone - 159 All data at all bases was processed on schedule and under budget. Some anomalies existed in terms of obstruction id�s (AVR is vertical designation but not at all bases), not all bases follow same procedure for multiple violation points � some have extra points in the map while others hold extra violations in the table. Where we find extra violations we recorded in the Form 48. TEAMWORK: The quickest and most accurate AOBS deployments were at installations where the community planner, GIO, and airfield manager worked closely together.� This occurred �during the review and coordination of existing obstruction data prior to the deployment team arriving as well as during the actual deployment data scrub.� Because each of these three team members was looking at the data from different perspectives, a 360 degree view encompassing all aspects of data quality (graphic standards, interpretation of regulations, engineering analysis, and operational realities) was achieved. Sample data changes from Misawa Misawa is an approximate median for changes per installation Originally 1332 records Overall 3846 changes to 882 database records 450 records required no changes A single record may have multiple changes Most changed items Distance from centerline � 503 records Violation distance � 475 Justification � 308 Feature penetration � 200 Priority zone - 159

19. 19 Priority Areas Added to Database We never previously had priority areas in our Airfield Obstruction database which made it very difficult in planning for removal of obstructions and funding projects New data element in the PACAF Form 48 This diagram depicts those priority areas: The PA-1 area is shaded red. It is 350� from the runway center line with a 1000�x2000� area in the clear zone PA-2 is shaded yellow. It is 1400� in width and centered on the runway PA-2 is shaded green. It is the remainder of the end-of-runway and lateral clear zonesWe never previously had priority areas in our Airfield Obstruction database which made it very difficult in planning for removal of obstructions and funding projects New data element in the PACAF Form 48 This diagram depicts those priority areas: The PA-1 area is shaded red. It is 350� from the runway center line with a 1000�x2000� area in the clear zone PA-2 is shaded yellow. It is 1400� in width and centered on the runway PA-2 is shaded green. It is the remainder of the end-of-runway and lateral clear zones

20. 20 Before and After Comparison of number of airfield obstructions before and after AOBS implementations Over 50% of previous airfield obstruction data records were modified during detailed implementation/deployment of AOBS Although numbers of PA-1s and PA-2s look close when added up, there were significant anomalies at individual basesAlthough numbers of PA-1s and PA-2s look close when added up, there were significant anomalies at individual bases

21. 21 Scoping the Problem Statistical modeling techniques used to develop ROM for obstruction removal Only those obstructions technically feasible for removal included in cost model PACAF now has a budgetary model for funding airfield obstruction removal projects The statistical model used a twenty item sample from each entire PA group of obstructions PACAF wide PA-1 : $21.55K/obstruction * 194 obstructions = $4,180,700 PA-2 : $35.50K/obstruction * 303 obstructions = $10,756,500 PA-3 : $41.25K/obstruction * 461 obstructions = $19,016,250 NA (apron, taxiway) : $43.00K * 725 obstructions = $31,175,000The statistical model used a twenty item sample from each entire PA group of obstructions PACAF wide PA-1 : $21.55K/obstruction * 194 obstructions = $4,180,700 PA-2 : $35.50K/obstruction * 303 obstructions = $10,756,500 PA-3 : $41.25K/obstruction * 461 obstructions = $19,016,250 NA (apron, taxiway) : $43.00K * 725 obstructions = $31,175,000

22. 22 AOBS Summary Elimination of problematic/outdated custom software Utilizing existing GeoBase tools/maps 100% Web-based, no software compatibility issues Leveraging in-house capabilities with shared ownership by community planner and GIO No dependence on outside contractors to support system. AOBS was developed in-house and will be maintained using in-house resources Complete validation of all obstruction data--reliable Ability to easily query, sort, analyze, and prioritize removal of all airfield obstructions throughout the command

23. 23 What is Coming! Space Utilization Management Tool Drivers: AFSO21, 20-20 by 2020, RPIR Reduce infrastructure, optimize/know what you have Similar to AOBS, split screen graphic/data Ability to switch between data and graphic information User friendly, ACAD or ArcMap expertise not needed Use standard elements from ACES RP/RPIR Use what we have; provide linkage Query tool including: Summary by category, location, etc. Breakdown of utilization; where is free space Expert tool for co-locations, centralize functions Links to maps and floor plans Business Process Development Critical !

24. 24 Space Utilization Tool Concept Sketch tenant units Attribute Report and query Refine and update usingas-builts

25. 25 Questions?