1
DATA
2
The Performance Guidance provides a summation of the key decision points necessary to 3
determine the most effective and efficient design, development, and implementation of the 4
geospatial system investment. 5
Table 4-7. Stakeholder Performance Guide: Data
6
STAKEHOLDER PERFORMANCE GUIDE CHAPTER 4 – DATA
Role Responsibility Approach Benefit
Exe cu tiv e L e ad e rshi p
•Authorize a Business Needs Analysis to identify geospatial data requirements using the Baseline Assessment Matrix: Data.
•Agreed upon data authorized source to reduce redundancy and determine Enterprise License Agreement (ELA) opportunity with data provider/vendor.
•Require any/all funded data creation or enhancement initiatives (e.g., contract award, cost-share, grant, etc.) include metadata standard compliance.
•Work with other Executives to acknowledge the need to reduce data costs by leveraging investment and performing the Baseline Assessment based upon mission/business needs.
•Based upon business/mission need during Data Matrix assessment, may require Service Level Agreement and cost share for availability and Enterprise License Agreement (ELA) with vendor/provider.
•Working with Exec Leadership approach Chief Procurement Officer to require contract language for the inclusion for all financial obligations.
•Signatory with defined responsibility and stated measurable results (e.g., IT Asset Inventory for OMB Open Data Policy reporting and a quantifiable data resource inventory).
•The inventory would facilitate the identification of desired datasets; identifies redundant data assets for decommissioning; identifies opportunities to reuse or extend a data asset rather than creating a new one; and the opportunity to reduce
redundancy costs based upon the establishment of enterprise licensing agreements and allows for cost share for economies of scale.
•Provides a way to uniformly describe data, thereby supporting its discovery and sharing resulting in cost avoidance. Compliance with government Open Data Policy.
STAKEHOLDER PERFORMANCE GUIDE CHAPTER 4 – DATA
Role Responsibility Approach Benefit
Program
Manage
r
•Coordinate across organization’s geo investment PMs for completion of Data Matrix and document business/mission functional requirements that drive data needs.
•Determine which dataset will be used enterprise-wide based upon data content, currency, and availability.
•Work with PMs across enterprise to perform review of internally produced data includes metadata with a common taxonomy and cataloged for discovery.
•Post datasets in open standards to appropriate catalogs for discovery.
•PMs prepare Data Matrix and schedule survey and follow-on interviews to clarify Data findings with business owners to understand functional needs.
•Detailed assessment of datasets and how they meet the mission/business functional requirements. May require ELA with broader use terms and additional attributes requiring cost-share.
•Review procurement vehicles to ensure metadata standard compliance language. Develop a common taxonomy for
cataloging the metadata enhanced data resources.
•Ensure enterprise data are exposed or ‘harvestable’ to appropriate web catalog services.
•Awareness and understanding of enterprise data requirements and business/mission owner functional needs that drive data.
•Reduced contracting for vendor provided data, ELA discounts for volume-based pricing, data Steward responsibility as opposed to multiple posting/storage of datasets.
•Ability to identify, search, discover and share datasets across the enterprise.
•Facilitates the search and identification of geospatial data sharing. Compliance with government Open Data Policy.
Sol u ti on Arc h itect
•Data Assessment Matrix design and development.
•Ensure data are cataloged and available in open standards and posted to web catalog service.
•Assist the data matrix interview with mission/business owner to determine functional
requirements that drive data and application needs.
•Develop technical approach for ensuring enterprise data resources are available, vetted, and provided in compliance with open data requirements.
•Technical vetting and validation across investments for desired To-Be end-state environment. Understand functional requirements to optimize application development and data resource acquisition.
•Facilitates the search and identification of geospatial data sharing. Compliance with government Open Data Policy.
1 2
5 APPLICATION/SERVICE REFERENCE
1MODEL
25.1 INTRODUCTION
3Definition/Description (What) – is a mission/business driven functional framework that provides 4
guidance and evaluation practices used to identify, document, classify, discover, deliver, and 5
share geospatial application and service (App/Svc) capabilities. It provides the basis for 6
categorizing IT App/Svc investments across an organization’s enterprise geospatial architecture. 7
Purpose/Function (Why) – as an organization documents and catalogs their current and planned 8
App/Svc investments, gaps and redundancies will become evident, which will aid in identifying 9
opportunities for sharing, reuse, consolidation, redesign, renegotiating or developing new 10
sources. Organizations and enterprise architectures will benefit from economies of scale by 11
identifying and reusing the best solutions and technologies for applications that are developed, 12
provided or subscribed to support their mission, business functions and target geospatial 13
architecture.90 This chapter provides a process to document and leverage IT investment assets
14
from a shared services perspective by: 15
• Establish a process for base lining and documenting geospatial applications and 16
services. 17
• Providing an understanding of design principles for shared services. 18
• Provide guidance for complying with Federal shared services policy. 19
• Provide [limited] references to resources for shared applications and services. 20
Stakeholder Performance Guide (Who & How) – Executive Leadership and Program Managers 21
responsible for policy setting and compliance, strategic program direction, resource planning and 22
approval (e.g., fiscal and human), and Solution Architects for identifying, documenting, and 23
sharing technical solutions for applications and services. This model helps managers or architects 24
understand the geospatial services delivered by their organization, and others; and assess 25
whether there is an opportunity to group like services and create opportunities for reuse or 26
shared services. 27
28
90 Segment Architecture Analysis of the Geospatial Platform, Version 1.0, December 21, 2010. Federal Geographic Data Committee, in
support of the Federal Chief Information Officers Council. Available at http://www.fgdc.gov/geospatial-lob/draft-segment- architecture-review/Segment-Architecture-Analysis-of-the