1 / 19

Authoritative Source for Location

Authoritative Source for Location. Lora Muchmore Director ODUSD(I&E) Business Enterprise Integration Directorate January 29, 2008. Where am I?. What’s around me ?. Location Defined. Where’s my stuff?. Absolute versus Relative. Challenges Today.

karen-wyatt
Télécharger la présentation

Authoritative Source for Location

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Authoritative Source for Location Lora Muchmore Director ODUSD(I&E) Business Enterprise Integration Directorate January 29, 2008

  2. Where am I? What’s around me? Location Defined Where’s my stuff? Absolute versus Relative

  3. Challenges Today • Association of people and equipment to location • Many different sources of location data/standards • GEOLOCs • DoDAACs • Installation Codes • DMDC location codes • UICS • Data integration • Accuracy problems • Costly • Timely

  4. Policy Drivers for Change • DoDD 8320.2, Data Sharing in a Net-Centric Environment, December 2, 2004 “Data interoperability shall be supported by making data assets understandable and by enabling business and mission processes to be reused where possible.” • USD AT&L, Policy for Unique Identification (UID) of Real Property Sites and Assets, May 11, 2005 “Real Property UID will enable real property data linkage across business mission areas to achieve the AT&L vision of linking real property, personal property, and people – any place, any time, any where.” • DoDD 8320.03, Unique Identification (UID) Standards for a Net-Centric Department of Defense, March 23, 2007 • “Develop and promulgate policy guidance for defining, implementing, and maintaining location UID standards…”

  5. DoD Business Transformation –Business Process Modeling

  6. Conceptual RPI Logical Data Model

  7. Site UID Creation Site UID Creation Context: UID—Integrated Situational Awareness of People, Places and Things Today -- No UIDs To Be State -- UIDs No integrated planning view Integrated planning view • Requirement: Capability to integrate force structure planning for identifying and constituting deployable combined force modules. • Who is available? • With what equipment? • Where are they now? • How long can we support them? People, things and property related to force structure. Deployment and constitution options can be continuously evaluated. Required items identified, pre-positioned and tracked with RFID. People and things can be identified to sites and facilities for rapid deployment response. RFID Tracking Questions Questions answered

  8. To Be UID Environment Enterprise Visibility Accountability Value Organization Acq Program Location Status Disposition Formal Ad Hoc Budget ACAT Absolute Relative Condition AT&L/P&R PA&E AT&L CJCS/P&R/AT&L CJCS/P&R/AT&L Property (AT&L) People (P&R) Real Property Personal Property Person Role AT&L P&R RPUID IUID FMID EDIPI

  9. Installation Facility(ies) Land Parcel(s) Facility(ies) Land Parcel(s) Installation and Site Relationship • Installation • Composed of one or more sites • Managed by a single Service • Site • Composed of one or more Land Parcels and/or Facilities • Over 8,000 sites worldwide (and probably much greater) Site A Site B Site .. • Asset • Either individual facility (e.g., building, structure, linear structure)or land parcel • Over 577K facilities on over 29M acres • Approximately 2.38B square feet of building space

  10. Real Property Site Unique Identifier (RPSUID): A non-intelligent code used to permanently and uniquely identify a DoD real property site. Real Property Unique Identifier Registry Web services interface FOC for Sites: June 2007 Over 8000 sites associated to almost 200 installations Data Collection: $1.6M contract to digitize Real Estate Summary maps at the Service repositories Site identification and validation completed through Service inventory systems Solution – Site UID

  11. Installation Data Elements Installation Code Installation Name Installation Virtual Indicator Installation Close Date Installation Reporting Component Code Site Data Elements Real Property Site Unique Identifier Site Name Site Creation Date Site Primary Activity Code Site Primary Indicator Site Operational Status Code Site Release Date Site Close Date Site Reporting Component Code Congressional District Code Metropolitan Statistical Area Code Site Code EPA Region Code GSA Region Code Headquarters Data Elements Associated to Site UID

  12. Data Elements Associated to Site UID • Address Data Elements • Address Street Direction Code • Address Street Name • Address Street Number • Address Street Type Code • City Code • County Code • State or Country Primary Subdivision Code • Site Rural Urban Code • Country Code • Postal Code

  13. Solution: RPUID • Real Property Unique Identifier (RPUID): A non-intelligent code used to permanently and uniquely identify a DoD real property asset. • Real Property Unique Identifier • Web services interface • Asset UIDs FOC scheduled for December 2007 • Over 600,000 assets to associate to sites • Data Collection • $1.8M contract to digitize deeds, permits, and licenses at Navy repositories and Air Force installations • DoDI 4165.14, Real Property Inventory and Forecasting • Real Property Information Model

  14. Site Boundaries Land Parcels (owned) Land Parcels (non-owned) Data Elements associated to RPUID • Asset Data Elements • Real Property Unique Identifier • RPA Name • Facility Number • Land Acquisition Tract Identifier • RPA Type Code • Acquisition Date • RPA Interest Type Code • RPA Predominant Design Use FAC Code • RPA Operational Status Code • Disposal Completion Date • Congressional District Code • And Address related Data Elements • Sites & Assets • Buildings • Structures • Linear Structures • Land Parcels

  15. Geo-Enabling Real Property Data Using Spatial Data Standards Spatial Data Standards for Facilities, Infrastructure and Environment (SDSFIE)

  16. Transforming the Business – Real Property Inventory Mapping Pilot • Mapping Legal Boundaries is a Key Part of the RPI • Based on land descriptions from Tract Maps, Summary Maps, Deeds, or other Acquisition Records • Entered via Digitization or Coordinate Geometry (COGO) • Two phases of pilot prototyping; 75+ installations or sites • Goal: Pilot the creation of an authoritative geospatial database for Real Property Site and Parcel data, which can be linked to the RPUID Registry

  17. RPI Sites RPI Land Parcels(Owned / fee simple) Owned land parcel polygons may not overlap All owned land parcels contribute to site boundaries RPI Land Parcels(Non-Owned / Less-than-fee rights and interests in-granted to DoD) All non-owned lands contribute to site boundaries Non-owned land parcels may not overlap with owned land parcels, but may overlap other non-owned lands Map Layers and Spatial Relationships for RPI Land Assets Contribution to Site Boundaries Map Layers(Themes or SDSFIE* “Entity Types”) Overlap Rules Site polygons may not overlap SDSFIE = DoD Spatial Data Standards for Facilities, Infrastructure, and Environment

  18. Enabling “Location” In The Enterprise • DoD systems using onesource for identifying DoD location • Authoritative: Legal Interest • Efficient: Web Services • Accurate: Real-time update Minimizes human error Independent Verification and Validation

  19. Questions? David LaBranche, P.E. Mission Assurance Liaison Defense Installation Spatial Data Infrastructure (DISDI) Office of the Deputy Undersecretary of Defense for Installations & Environment, Business Enterprise Integration Directorate ODUSD(I&E) BEI E-mail: david.labranche.ctr@osd.mil Ms. Lora Muchmore Director Business Enterprise Integration Office of the Deputy Undersecretary of Defense for Installations & Environment ODUSD(I&E) BEI E-mail: lora.muchmore@osd.mil

More Related