1. 17-Oct-07 Spatial Engineering, Inc.1 Installation Management Agency Korea Region Office KOROGIS CADD/GIS Interoperability Presented By: Anna Austin, GISP Spatial Engineering, Inc.

2. 17-Oct-07 Spatial Engineering, Inc.2 Background –History –Issues –Objectives Approach –Initial – Without Oracle Spatial –Revised – With Oracle Spatial Current Configuration –Overall Data Flow –Interoperability Data Flow Conclusions Overview

3. 17-Oct-07 Spatial Engineering, Inc.3 History 1997 Camp Humphreys and Camp Carroll ~ $700k –MGE/Oracle –Data Maintenance Other Duties 1999 Camp Casey Enclave (6 sites)~$550k –GeoGraphics/Access –Data maintenance personnel, no equipment 1999 Yongsan Garrison~$3M –GeoGraphics/Oracle  FME  ArcIMS –Data maintenance by Contract Over $4M spent……..

4. 17-Oct-07 Spatial Engineering, Inc.4 Issues HQ KORO Observed: –Limited access/use High $$$, few (1-2) people able to use Inconsistent products from installations to HQ –Irregular Data Maintenance Other duties as assigned Planimetrics & utilities maintained in MicroStation DGN. (EN/PN) Environmental & Training maintained in ArcView SHP. (ITAM/EV) Multiple versions (“Who has the latest?”) –System/data compatibility questioned Why is data from locations different? Why is data from Directorates (DPW, ITAM) different? Installation specific development and functionality

5. 17-Oct-07 Spatial Engineering, Inc.5 A “Common Installation Picture (CIP)” for all sites. Easy access to all authorized KORO users (US and KN) Support all geospatial platforms used –MicroStation CADD –ArcGIS GIS Standard data structure (SDSFIE) all sites. Up-to-date consistent data all sites. Standard tools for all users/sites. Objectives

6. 17-Oct-07 Spatial Engineering, Inc.6 Background –History –Issues –Objectives Approach –Initial – No Oracle Spatial –Revised – Oracle Spatial Current Configuration –Overall Data Flow –Interoperability Data Flow Conclusion Overview

7. 17-Oct-07 Spatial Engineering, Inc.7 2002 KOROGIS Enterprise Implementation Plan Provide On-site Support Personnel (Michael Baker, Jr., Inc.) –GIS Manager/DBA (GDBA) –Area Support Managers (ASM) for Area I, II, III, and IV Knowledgeable of CADD and GIS Software –MicroStation GeoGraphics/Access (Geospatial CADD) –ArcGIS 8.3 (GIS) –ArcSDE/Oracle 9i (ArcSDE_Binary RDBMS) –ArcIMS (Web Publisher) Goal –Support Geospatial Data (CADD (MicroStation) and GIS (ArcGIS)) –Secure multi-level web access to over 80 camps, 1000+ routine users –Maintain single corporate spatial database. Eliminate multiple copies. –Use Standard data schema. (SDSFIE) Initial Approach

8. 17-Oct-07 Spatial Engineering, Inc.8 GIS Server 2 (Camp Henry) GIS Server 1 (Yongsan) Area I ASM (Camp Casey) Area IV ASM (Camp Henry) Area III ASM (Camp Humphreys) Area II ASM (Yongsan) GIS DBA (Yongsan) ASM – (Area Support Manager) responsible data maintenance within assigned area GIS DBA – Manages overall system. GIS Server – Redundant servers replicate to ensure reliability Locations

9. 17-Oct-07 Spatial Engineering, Inc.9 Initial Data Workflow Pros –Data maintained at DPW by ASM. –CADD access at DPW. –Central spatial database supports GIS and WEB access. –Controlled data input. (by ASM) –One common map.

10. 17-Oct-07 Spatial Engineering, Inc.10 Initial Data Workflow Cons –Convert data (DGN  SHP  SDE_Binary) –Conversion problems –Multiple data type –Enterprise spatial database does not support CADD –Difficult finding knowledgeable support in CADD AND GIS. Users know dialog boxes!

11. 17-Oct-07 Spatial Engineering, Inc.11 2003 Migration Plan - Enterprise Oracle Spatial –SDSFIE Adjustments Match CADD Feature to GIS Feature Class Match CADD Category to GIS Feature Data Set –Data Maintenance adjustments Extend MicroStation GeoGraphics (DBQue) Define update procedures per application (Do’s and Don’ts) Capture updates to the central server nightly Train support staff on one data format (SDO_Geometry) Revised Approach

12. 17-Oct-07 Spatial Engineering, Inc.12 Our Goal

13. 17-Oct-07 Spatial Engineering, Inc.13 Oracle Spatial Workflow Pros –Data maintained in CADD (GeoGraphics) at DPW –Central spatial database supports CADD and GIS. –Single common data type (SDO). No Conversion. –Oracle procedures automate/support QC/QA process.

14. 17-Oct-07 Spatial Engineering, Inc.14 Oracle Spatial Workflow Cons –Oracle Spatial Cost ($2,500/CPU on ITL BPA). –Train support personnel on new workflow. (This is minor since a total spatial solution requires training.) –Adjustments required to accommodate vendor requirement/deficiencies. (“IOP”)

15. 17-Oct-07 Spatial Engineering, Inc.15 Background –History –Issues –Objectives Approach –Initial – No Oracle Spatial –Revised – Oracle Spatial Current Configuration –Overall Data Flow –Interoperability Data Flow Conclusion Overview

16. 17-Oct-07 Spatial Engineering, Inc.16 Overall Data Flow

17. 17-Oct-07 Spatial Engineering, Inc.17 PROS –CADD  GIS  WEB  GIS  CADD –Stores element geometry in the SDO_GEOMETRY (SDO) data type. –Data can be accessed using standard SQL procedures and commands. –Bentley and ESRI support the Oracle Spatial SDO format. –No Conversion of geometry. Accuracy and content are maintained. –Enterprise spatial database supports CADD, GIS and WEB applications. –Oracle Spatial provides additional data validation tools. –Data stored in Oracle through its life-cycle. –Simple geometry makes edits simple. CONS –Must understand vendor requirements and limitations. –Geometry must be simple polygon, line, and point elements for interoperability. –Must have data maintenance procedures to account for vendor limitations. –Additional cost for Oracle Spatial. Implementing Oracle Spatial

18. 17-Oct-07 Spatial Engineering, Inc.18 Conclusion Collect and edit data once, use by many (users & applications) Manage a single data format (SDO) to support CADD and GIS. NO conversion, minimize pre/post-process time. Data maintenance procedures critical. Use CADD/GIS technology that best satisfies the specific need. –Engineers use CADD (MicroStation) –Planners use GIS (ArcGIS) –Leverage current investment in technology, personnel and data development. Paradigm change - –CADD and GIS are tools or the engine! –Data is the fuel! –You would not buy a KIA Sorento that ONLY used KIA fuel!!!

19. 17-Oct-07 Spatial Engineering, Inc.19 Conclusion KORO owns the data. The cost to convert to CADD or GIS: $ZERO

20. 17-Oct-07 Spatial Engineering, Inc.20 Questions KOROGIS CADD/GIS Interoperability By: Anna Austin, GISP aaustin@spateng.com