Upload
bryce-adrian-walsh
View
215
Download
3
Tags:
Embed Size (px)
Citation preview
Acquisition, Technology and Logistics
1
DISDIG Meeting 10 October, 2012
AGENDA:
1. Introductions
2. Army “Military Range & Training Model” – discussion & vote
3. DGMP Working Group – name change vote
4. New Investment Review Process, I&E Governance Board
5. Update from GISi re: SDSFIE website
6. Change Requests & Status of SDSFIE 3.1
7. DISDI CIP Data Call, 2012
8. Other DISDIG business– Data request update– Member issues, topics, Q&A
SDSFIE Overview & BackgroundSDSFIE Vision: To be the single DoD spatial standard that supports common
implementation and maximizes interoperability for Installation, Environment, and Civil Works Missions
• SDSFIE provides a set of geographically referenced feature types and attributes sufficient to meet a majority of the collective DoD I&E business needs
• SDSFIE focuses on a geospatial representation of features and maintains a minimum number of attributes to link business databases for attribute data, while not duplicating those in business databases
Army Pilot ProjectsGoals & Objectives
• Obtain an estimated level of effort to convert an installation geospatial dataset from SDSFIE v2.6 to SDSFIE 3.0
• Determine the extent of data loss that might occur when moving from 2.6 to 3.0 & propose an Army Adaptation to prevent data loss or corruption of data
• Capture information that will inform the planning and execution of SDSFIE 3.0 training, migration timeline, and data management
Results• Test installations (Fort Bragg, JBLM, & Camp Ripley) discovered:
– Level of effort required to convert to SDSFIE 3.0 is significant– Data conversion tools have rigid SDSFIE 2.61 compliancy requirement.– Manual conversion is the most viable option for Army
Army Implementation Plan
• Outlines document purpose and provides SDSFIE overview
• Provides driver references and defines key terms and common acronyms
• Defines implementation roles and responsibilities throughout Army IGI&S
• Details exact adaptation process for each level of Army IGI&S (HQ, Army Organizations, & Installations)
• Outlines all physical implementation rules as mandated by DISDI & OACSIM
• Provides brief overview of way forward
Army Quality Assurance Plans• Set of documents defining geospatial data & metadata content
specifications, validation methodology, acceptable data sources, internal handling controls and how GIS data is aligned with Army business systems
• Living documents reviewed & updated annually by HQDA Proponent
• Outlines all acceptable geometry types
• Written to SDSFIE 2.6 but contains preliminary SDSFIE 3.0 Army Adaptation information
• Prepares for business system alignment
Foundational Attributes• All SDSFIE Gold Foundational Attributes are included within the Army
Adaptation.• Additional Army Adaptation foundational attributes were added to all
applicable feature types. All are Army IGI&S or Army Real Property requirements.
Attribute JustificationPrimaryKeyIDPK SDSFIE 3.0 Gold, Army QAPsdsID SDSFIE 3.0 GoldsdsFeatureName SDSFIE 3.0 GoldsdsFeatureDescription SDSFIE 3.0 GoldsdsMetadataID SDSFIE 3.0 Gold
featureArea Army QAP
featureAreaUOM Army QAP
featureLength Army QAP
featureLengthUOM Army QAP
featurePerimeter Army QAP
featurePerimterUOM Army QAP
coordinateX Army QAP
coordinateY Army QAPinstallationID Army QAPrealPropertySiteUniqueID Army QAPrealPropertyUniqueIdentifier Army QAPfacilityNumber Army QAPvalidSource Army QAPmediaURL** Army QAP
Army SDSFIE Working Group
SDSFIE 3.x Army Adaptation Development Work Flow
Purpose: To finalize the SDSFIE 3.0 Army Adaptation, establish best management practices for implementing the Army Adaptation, and to
manage change.
• Consists of Army IGI&S staff & SMEs from all levels of the Army
• Has met quarterly since Jan 2011• Responsible for:
– Establishing subgroups with specific focuses
– Create common feature type, attribution, and enumeration recommendations
– Document and provide justification for all additional Army requirements
Army SDSFIE WG Subgroups
• Objective: Identify requirements for feature types, attributes, enumerations, and relationships to make up the SDSFIE 3.0 Army Adaptation.
• Requirements are provided to IGI&S Working Group for approval.
Current Subgroups:Recreation Natural Resources
Planning ENV Restoration
Public Works Cultural Resources
Real Property Military Range & Training
Common/Cross-Functional
Army SDSFIE WG MRT Subgroup• Military Range and Training Subgroup began on March 3, 2011 and concluded
meetings on June 15, 2011.
• Meetings consisted of HQ SRP, Installation IGI&S, Installation DPW, Installation SRP, USACE, and SRP SME staff.
• Each Sustainable Range Program QAP was reviewed and compared to SDSFIE Gold to identify definition, attribute, and concept matches.
• All decisions made during meetings are being used to update existing SRP QAPs in preparation for distribution to the SRP community with the new SDSFIE 3.0 Army Adaptation Module.
• Additional coordination was completed following completion of meetings to iron out final modeling details, justifications, etc.
Army Adaptation Documentation• Offical documentation required
by DISDI for Adaptation approval
– Extensions, Profiles, Enumerations, Subclasses, Justifications, etc.
• Army Documentation– Written Data Dictionary– Visualization of Model– Physical, Distributable Geodatabase
Questions/Comments?
Visit IGI&S:
AKO Portal: https://www.us.army.mil/suite/page/igis
Email:[email protected]
Vince NicchittaIGI&S Program [email protected]
Chris SchulzeIGI&S [email protected]
Martina HarmonQuality Assurance & Communications
Lead / SDSFIE [email protected]
Metadata Working Group
September 25, 2012 Meeting Summary:
• State of DGMP
• NSG Metadata Framework (NMF) insights
• ArcGIS 10.1 Template
• Implementation Guidance
• Potential Additions to DGMP 1.1
• Name Change
• Recommendations concerning the way forward
Metadata Crosswalk (for ArcGIS 10.1)
• The new Metadata Crosswalk is complete and is under final DISDI Program review
• Once the Crosswalk is finalized by the DISDI Program it will be distributed to the DISDI Group for its review
• After review and approval by the DISDI Group, an ArcGIS metadata template(s) will be produced and distributed to the DISDI Group
Metadata Standard - Name Change
Recommendations:
• SDSFIE Metadata Profile (SMP)
• SDSFIE Metadata Framework (SMF)
• SDSFIE Metadata Foundation (SMF)
• ACTION: As discussed at the most recent Metadata Working Group meeting, the DISDIG concurs with changing the name of the DISDI Geospatial Metadata Profile (DGMP) to SDSFIE Metadata Foundation (SMF).
FY2012 NDAA
• Section 901 of the Fiscal Year 2012 National Defense Authorization Act (FY2012 NDAA) continues to refine the IRB Process:– Single cross-functional, enterprise-wide IRB/Defense Business
Council (DBC), chaired by the Deputy Chief Management Officer (DCMO) to certify investmentso Defense Business Systems (DBS) that will have a total cost in excess
of $1M over the period of the current future–years defense program (FYDP)
– New investment management process intended to:o Emphasize Business Process Reengineering (BPR) o Strengthen and influence the Business Enterprise Architecture (BEA)o Become the foundation for the Enterprise Transition Plan (ETP)
New IRB Process – Functional Business Strategy
• Requires the development of a functional business strategy from each business area which: – Defines the business area’s strategic vision, goals, and
targeted outcomes based on the Quadrennial Defense Review (QDR) and the Strategic Management Plan (SMP)
– Is developed by the Principal Staff Assistants(PSAs)– Provides general direction for business area as a whole or
may focus on specific sub-functions within a business area– Will be used to drive the BEA– Ensures Component Organizational Execution Plan (OEP)
to functional strategy– Requires submission to the IRB/DBC and approval
I&E Sub-FunctionsBusiness Functions tied to Joint Capability Areas
General Engineering– The ability to employ engineering capabilities and activities, other than combat
engineering, that modify, maintain, or protect the physical environment. Examples include: the construction, repair, maintenance, and operation of infrastructure, facilities, lines of communication and bases; terrain modification and repair; and selected explosive hazard activities.
Real Property Life Cycle Management– The ability to acquire, operate, sustain, recapitalize, realign, and dispose of real
property assets to meet the requirements of the force.
Installation Services– The ability to deliver selected services not related to real property (or personnel
services) to meet the requirements of the installation population and mission.
Geospatial Engineering– The ability to portray and refine data pertaining to the geographic location and
characteristics of natural or constructed features and boundaries in order to provide engineer services. Examples include: terrain analyses, terrain visualization, digitized terrain products, nonstandard tailored map products, facility support, and force beddown analysis.
Source: http://www.bta.mil/products/bea_7_0/BEA/iwp/bealist_jointcapabilityarea_na.htm
23
I&E Functions and Capabilities Map to BEA
Installation and Environmental Management
Real Property Life
Cycle Management
Installation Services
Geospatial Engineering
Functional Area
Sub-Functional Area
I&E Capabilities
Develop and Maintain Facilities
Economic Adjustment Activities
Perform Receipt, Acceptance and
Return
Perform Installations
Support
Manage Geospatial Information and
Services
I&E Process Models
I&E Functional Strategy Business Enterprise Architecture (BEA 9.0)
Facilities Support
Disposal of Installation Assets
Utilize Geospatial Data
Emergency Services
Real Property Acceptance
Environmental Liabilities
Identification and Valuation
Manage Property and Materiel
Perform ESOH Services
Core Capabilities
General Engineering
Security Services
installation Safety
Master Facility Design
Repair and Restore
Infrastructure
Housing Services
Provide Installation Assets
Sustainment of Installation Assets
Recapitalization of Installation Assets
Perform Build and Make and
Maintenance and Sustainment
Perform Build and Make and
Maintenance and Sustainment
Manage Property and Materiel
Hazardous Materials Process
Controls and Information
Management
Real Property Inventory
Range & Airfield Management
Port Services
End-to-Ends
Acq
uire
to
Ret
ire (
A2R
)
Pro
cure
to
Pay
(P
2P)
Env
ironm
enta
l Lia
bilit
ies
(EL)
Ord
er t
o C
ash
(O2C
)
New IRB Process – Component OEP
• Requires development of OEPs, which: – Are developed by each Component– Requires review and submission to the IRB/DBC through the
component Pre-Certification Authority (PCA) for approval– Helps to identify and balance technology needs and align to the
BEA– Must be linked with the business area functional strategy – Are used for review, evaluation and certification– Assists Components with grouping DBS into portfolios
I&E Organizational Execution Plans (OEP)Review Process Take Aways
• Data Quality Critical– DoD Information Technology Portfolio Repository– Select and Native Programming Data Input System – Information
Technology– OEP and Assertion Memo
• I&E Preview and Discussion Sooner in Process
• Update Functional Business Strategy– Better define weak areas (e.g. Installation Support, Energy)
25
New IRB Process - IPTs
• IRB/DBC establishes Integrated Product Teams (IPTs):
– Standing I&E IPT are proposed and would:o Be responsible for assisting the AT&L IRB/DBC member in
assessing portfolio investments by determining compliance with laws, identifying redundancies and gaps, and validating business value of portfolios
o Address all I&E functions and capabilities covered by the BEAo I&E representation from Component and Defense agency
Charter - I&E Functional Business Governance Board
• Charter establishes I&E Functional Governance Board:– As authoritative governance body for DUSD– As main governance body for oversight, direction and support to
provide single integrated I&E approach to enable interoperability and manage data quality for enterprise capabilities across I&E
– As support for functional responsibilities IAW U.S.C. Title 10, the DISP and the I&E Functional Business Strategy
– As responsible to ensure compliance with DCMO guidance and in accordance with OEPs.
27
30
APPROVED (22) CANCELED (7) DEFERRED (4) FURTHER REVIEW (17)
29 144 46 118 4240 150 91 147 43*49 169 117 168 44*50 176 143 189 11551 177 148 11952 178 174 12453 179 182 145*81 180 146*92 181 14994 183 171
116 185 172173*175*184
186 187 188
As a result of the SDSFIE Working Group meeting…
CH
AN
GE
RE
QU
ES
TS
*Special Case CRs – see next slide
Change Requests – Further Review
• DISDI PM e-mail, 4 October: Special case CRs that need further collaboration between one or more services in order to finish the CR recommendation for final group review/action
31
Special Case CRs Services Description
43 USAF Additional detail including specifics about how the USACE and DoD cases are different and proposed solution(s).
44 USAF and NAVY Coordinate and develop a concrete proposal on the structure of this feature.
145 USMC USMC to follow up with functional lead to finalize USMC concurrence.
146 USMC USMC to follow up with functional lead to finalize USMC concurrence.
173 ARMY Provide proposed items and definitions.
175 USAF and USMC Need coordination between USAF and USMC, with USAF responding to USMC proposed name.
Change Request Status
32
Status # Description
APPROVED 22 CRs approved by DISDIG and will be implemented in SDSFIE 3.1.
CANCELED 7 CRs canceled. These will not be implemented in SDSFIE 3.1 and may be returned to at a later date if needed.
DEFERRED 4 CRs reviewed by DISDIG, will be postponed until a later date and will not be implemented in 3.1.
Need Further Review 17CRs require additional review in order to finish the CR recommendation and final Group decision for implementation into 3.1.
IMPORTANT DATES:October 17 – Comments DUE for all CRsOctober 24 - Final vote for implementation into 3.1
Acquisition, Technology and Logistics
34
DISDI CIP Feature List - 2012
* Based on SDSFIE 3.0 Gold LDM
AccessControl MilitaryRangeAdministrativeBoundary MilitaryTrainingLocationAirAccidentZone PavementSectionBridge PavementBranchBuilding RailSegmentEnvironmentalRemediationSite RecreationAreaFence RoadCenterlineGolfCourse SiteImpactArea TowerInstallationArea VehicleParkingLandParcel Wetlands
REPI SITES!so…what is new?
Readiness and Environmental Protection Initiative – What is it?
Acquisition, Technology and Logistics
36
Data Call Features & Geometry
gate_line line
gate_point point
military_access_point pointinstallation_area polygon
air_accident_zone_area polygon
road_bridge_area polygon
shed_site point and/or polygon
structure_existing_site point and/or polygon
environmental_restoratn_site point and/or polygon
oe_hazard_concern_site point and/or polygon
oe_hazard_invest_sector_area polygon
oe_hazards_rac_score_area polygon
fence_line line
golf_course_area polygon
dudded_impact_site point and/or polygon
non_dudded_impact_area polygon
historic_impact_area polygon
dod_rpi_land_parcel_area polygon
military_range_area polygon
military_live_fire_range_area polygon
training_site point and/or polygon
military_parade_ground_site point and/or polygon
military_training_sub_site point and/or polygon
airfield_surface_area polygon
curb_area polygon
pedestrian_sidewalk_area polygon
road_area polygon
vehicle_driveway_area polygon
railroad_centerline line
athletic_court_area polygon
athletic_field_area polygon
swimming_pool_area polygon
boating_site point and/or polygon
hunting_area polygon
miscellaneous_recreation_area polygon
picnic_site point and/or polygon
recreation_park_area polygonroad_centerline line
dod_rpi_site_area** polygon**
tower_site point and/or polygon
vehicle_parking_area polygon
wetland_area polygon
*As defined in SDSFIE 2.X Prior Release
Acquisition, Technology and Logistics
37
Next Steps
• Data call to Components– 60 days to complete
• DISDI team compiles data, coordinates with Components to resolve issues
Data Requests and Projects Update
DATA REQUESTS
Data Requested Requestor Organization
Purpose and Intended Use Request Date
Completed Date
2012 DSL Point and Boundary USACE The purpose is to make the DSL worldwide data set available to Corps of Engineers employees on the internal production network. This network is not classified. But it is a controlled access, non-public network within the COE firewalls.1) Intended use is via geospatial overlay with Corp of Engineers data2) DSL Worldwide boundary and points3) Corps of Engineers internal production network4) Users are Corps Employees with access to production network via CAC or VPN5) No data distribution, this is for online web access
7-Sep-12 11-Sep-12
2012 DSL Point and Boundary Defense Intelligence Agency (DIA)
This data will be primarily used for cartographic and geospatial analytical purposes, focusing on worldwide COOP (Continuity of Operations) and contingency planning issues dealing with military intelligence entities. The building facilities and human resource departments task us with assisting in any planning for moving personnel to another facility in case of emergency or construction. They also task us with analysis of facilities that could be affected by disasters, whether natural or man-made. There may also be times when the data will be used for publication purposes (just as a display file, no analysis on the data). These publications will only be accessible on classified channels by people with a minimum U//FOUO clearance. If the publication is moved to a lower classified network, we will contact DISDI for guidance on this. This data will be removed from our network when it is either no longer needed for projects or we request an update that replaces the current file.
20-Sep-12 21-Sep-12
38
Data Requests and Projects Update
DATA REQUESTS
Data Requested Requestor Organization
Purpose and Intended Use Request Date
Completed Date
2012 DSL Point and Boundary NAVFAC Atlantic To support USFF environmental planning and range sustainment efforts NAVFAC Atlantic requests DISDI's Defense Site Location (point and polygon) Worldwide geospatial dataset.
The data will be made available on the Navy's Environmental Information Management System (EIMS). EIMS is a Geographic Information System (GIS)-based toolset designed to provide the Navy with a more effective and efficient means of fulfilling its regulatory compliance obligations by leveraging existing data and technologies. EIMS supports environmental planning, natural resources management and encroachment issues for Navy range and OPAREA events.
EIMS is a PKI enabled system with access limited to Navy personnel and contractors with CAC/hardware tokens. Data disclosure agreements prevent users from downloading and distributing data from the system.
24-Sep-12 1-Oct-12
DAFIF QinetiQ Assist the US to avoid interference between wind turbines and military and civil operations. The data will be used in an early siting tool for wind turbines and other large obstacles to predict and avoid interference with aviation operation. The tool will reside on QNA secure, encrypted computers.
1-Oct-12 2-Oct-2012
39
Data Requests and Projects Update
MAP REQUESTS
Map Requested Requestor Organization
Purpose and Intended Use Request Date Completed Date
Map showing greater San Diego Area defense sites
OSD For OSD situational awareness. 4-Sep-12 4-Sep-12
Maps of Hawaii, Guam, and Okinawa defense sites
OSD For OSD situational awareness. 4-Sep-12 6-Sep-12
Physical map of Kodiak Island, Alaska showing FUDS sites.
OSD For OSD situational awareness; Tribal Affairs office. 10-Sep-12 17-Sep-12
Map of Alaska Towns and Defense sites
OSD/Facilities Energy and Privatization
For OSD situational awareness; Interagency Alaska Working Group on Energy.
14-Sep-12 18-Sep-12
Map of Alaska Railbelt OSD For OSD situational awareness; Interagency Alaska Working Group on Energy.
2-Oct-12 In progress.
40