This section of the supplemental guidance contains the geospatial data lifecycle stages matrix that agencies should use when developing, managing, and reporting on nationally significant datasets under the auspices of OMB Circular A–16.  The matrix establishes a framework of standard terminology and processes for seven geospatial data lifecycle stages.  The figure below summarizes the data lifecycle stages, which are Define, Inventory/Evaluate, Obtain, Access, Maintain, Use/Evaluate, and Archive.

The stages associated with the management of the data lifecycle allow stakeholders to assess whether A–16 data production activities meet business requirements and utilize best practices that enable shared or common services.  The data lifecycle is not intended to be rigidly sequential or linear.  The quality assurance and (or) quality control (QA/QC) functions for the data should be included at every stage of the data lifecycle.

Business requirements drive what needs to occur at each stage.  This concept is illustrated in the figure below by the purple arrows that point from the business requirements circle to each lifecycle stage.  The orange arrows that point to the business requirements circle represent the feedback loop that needs to occur at each stage to reassess the business requirements.  <Use the graphic to make an Image Map to link the lifecycle stages, Vaishal said he could do this (http://www.htmlcodetutorial.com/images/images_famsupp_220.html)>

The data lifecycle.

The expected outcomes of adopting this framework include:

• Timely and high-quality geospatial data to support business processes and operations;

• Stronger partnerships across all levels of government and, when appropriate, the private sector, to increase cost efficiency and return on investment; and

• Improved strategies for completing and maintaining nationally significant themes and datasets associated with OMB Circular A–16 to enhance services to citizens.

Data Lifecycle Stages

Stage 1 - Define
Stage 2 - Inventory/Evaluate
Stage 3 - Obtain
Stage 4 - Access
Stage 5 - Maintain
Stage 6 - Use/Evaluate
Stage 7 - Archive

Differences between the ISO System Lifecycle and the Data Lifecycle

The International Organization for Standardization (ISO) system lifecycle and the A-16 data lifecycle are both necessary. These two lifecycles are not the same or interchangeable, but are complementary. The ISO system lifecycle provides the framework on which to build a specific application that supports the collection, maintenance, and delivery of data to users. It is physically oriented (focused on computer hardware and software) and has a technical lifespan that requires upgrading and eventual replacement because of its dependency on programming and technical specifications. The data lifecycle uses many of the same concepts but focuses specifically on the data, which may exist within a system or be maintained by one or more specific applications. The data and the data lifecycle should be platform and system independent so that the data can evolve or be migrated to a new platform or application as the business requirements change. Unlike an interface, which may change in response to future developments, the data may change in form but not necessarily in content; the data should be multiple-use (that is, the data should be able to be accessed by multiple users, on multiple systems, for multiple purposes).