The

Defense Installation Spatial Data Infrastructure Group (DISDIG)

Strategy for the Development and Implementation of SDSFIE 3.0

Version 1.0

Office of the Deputy Under Secretary of Defense (Installations & Environment)

Business Enterprise Integration Directorate

February 11, 2009

Document Revision History

Release Date Revision Description File Name

Rough Draft 15 October 2008

Rough Draft of the SDSFIE Implementation Strategy was prepared and released to stimulate document input to establish a consensus based SDSFIE implementation strategy.

SDSFIEImplementationWhitepaper_RD.doc

Working Draft

10 December 2008

Working Draft represents a major elaboration of the material in the Rough Draft based on comments from the DISDIG and a maturing understanding of the SDSFIE Implementation processes as a result of this strategic planning effort.

SDSFIEImplementationWhitepaper_WD.doc

Draft Final 5 January 2009

The Draft Final is the incorporation of all comment and edits collected after the release of the Working Draft and sections have been completed that were marked as To Be Developed in the Working Draft.

SDSFIEImplementationWhitepaper_DF.doc

Final 11 February 2009

The Final is the incorporation of the DISDIG final round of review comments.

SDSFIEImplementationWhitepaper_Final.doc

Revision 1 14 October 2009

Revised to include the Communications Plan into Appendix C.

SDSFIEImplementationWhitepaper_FinalwithRevision1.doc

10/19/2009 Ver. 1.0

2

10/19/2009 Ver. 1.0

3

Table of Contents Key Terms and Definitions................................................................................................. 6 Section 1: Introduction....................................................................................................... 8

Purpose and Scope ........................................................................................................ 10 Governance ................................................................................................................... 10 Types of Activities: Standard or Data........................................................................... 11 Organizations ................................................................................................................ 11 Roles and Responsibilities ............................................................................................ 12 Communication............................................................................................................. 13 SDSFIE Development and Implementation Strategy Overview .................................. 14

Section 2: Phase 1 – LDM Development......................................................................... 17 Primary Activities - Development Phase...................................................................... 17 STARS Team Responsibilities - Development Phase .................................................. 18 DISDIG Responsibilities - Development Phase ........................................................... 18 IGI&S Program Responsibilities - Development Phase ............................................... 19 Implementation Level Organizations Responsibilities - Development Phase.............. 19 Data Proponents Responsibilities - Development Phase .............................................. 19 USACE Responsibilities - Development Phase............................................................ 19

Section 3: Phase 2 - Approval.......................................................................................... 20 Primary Activities for the Approval Phase ................................................................... 20 STARS Team Responsibilities - Approval Phase......................................................... 21 DISDIG Responsibilities - Approval Phase.................................................................. 21 IGI&S Programs Responsibilities - Approval Phase .................................................... 22 Implementation Level Organizations Responsibilities - Approval Phase .................... 22 Data Proponents Responsibilities - Approval Phase..................................................... 22 USACE Responsibilities - Approval Phase .................................................................. 22

Section 4: Phase 3 - Implementation ............................................................................... 23 Primary Activities for the Implementation Phase......................................................... 23 STARS Team Responsibilities - Implementation Phase .............................................. 24 DISDIG Responsibilities - Implementation Phase ....................................................... 25 IGI&S Programs Responsibilities - Implementation Phase.......................................... 25 Implementation-Level Organizations Responsibilities - Implementation Phase.......... 26 Data Proponents Responsibilities - Implementation Phase .......................................... 28 USACE Responsibilities - Implementation Phase........................................................ 28

Section 5: Phase 4 - Transition ........................................................................................ 29 Primary Activities for the Transition Phase.................................................................. 29 Important Execution Considerations for the Transition Phase ..................................... 30 STARS Team Responsibilities - Transition Phase ....................................................... 30 DISDIG Responsibilities - Transition Phase ................................................................ 30 IGI&S Programs Responsibilities - Transition Phase................................................... 30 Implementation Level Organizations Responsibilities - Transition Phase ................... 31 Data Proponents Responsibilities - Transition Phase ................................................... 31 USACE Responsibilities - Transition Phase................................................................. 31

Section 6: Next Steps ....................................................................................................... 32

10/19/2009 Ver. 1.0

4

Develop enterprise-level change management plan for sustaining and evolving the standard......................................................................................................................... 32 Refine governance and meta-governance ..................................................................... 32

Appendix A: Adaptation of SDSFIE 3.0 LDM ............................................................... 33 Appendix B: SDSFIE Governance .................................................................................. 38 Appendix B: SDSFIE Governance .................................................................................. 38 CSP (Configuration Support Panel).................................................................................. 40 Appendix C: Communications (TBP).............................................................................. 41 Appendix D: IGI&S Implementation Plans..................................................................... 65

D.1: IGI&S Program Plan for Governance.................................................................. 65 D2: IGI&S Program Plan for Adaptation .................................................................... 66 D3: IGI&S Program Plan for Communication ............................................................ 67 D4: IGI&S Program Plan for Change Management .................................................... 67

Appendix E: Organization Activities by Phase ............................................................... 70

10/19/2009 Ver. 1.0

5

Key Terms and Definitions Adaptation: Adaptations are formalized alterations to the LDM resulting in a data schema which is tailored to the particular business requirements of an implementing organization. An Adaptation consists of a specific Profile and all the Extensions required to meet specific user requirements. (see Appendix A for more details) Best Management Practice: An approach to performing some business activity that is known to be successful, as documented in industry practice, professional literature, or enterprise business rules. Data Activities (DA): SDSFIE Implementation activities that specifically relate to geospatial data including the development of migration plans, technical solutions for ensuring continuity of operations, creation of data schemas and generation of implementation-specific migration tools Data Proponent: (1) Organization or staff element that has primary responsibility for materiel or subject matter expertise in its area of interest or charged with accomplishment of one or more functions (Army definition); (2) An agency, department, activity or organization that has lead responsibility for coordinating the collection, coverage and stewardship, including maintenance and update, of a specific spatial data theme or mission dataset (USMC definition for “Functional Dataset Lead”). DISDI Geospatial Metadata Profile (DGMP): The DGMP is a profile of the International Organization for Standardization (ISO) 19115:2003 Geographic Information – Metadata that provides the technical details for supporting the objective to define a well-structured and unified set of data elements to describe DoD Installations & Environment (I&E) Business Mission Area geospatial data assets. Extension: The addition of a new element (e.g. Feature Type or attributes) to the SDSFIE 3.0 LDM provided that element does not conflict with the definitions of elements already defined by higher authority. (see Appendix A for more details) GEOINT Structure Implementation Profile (GSIP): An interdependent set of components that together to define a common method for specifying and encoding GEOINT and related geospatial (e.g. Common Operation Picture and METOC) data in the NSG. Governance: The means for coordination, regulation, orchestration and decision making within federations that are self-forming and self-regulating. Logical Data Model (LDM): A structured logical representation of business requirements validated and approved by business representatives which contains entities and relationships of importance within an organized framework , and business textual definitions and examples. It becomes the basis of physical database design.

10/19/2009 Ver. 1.0

6

National System for Geospatial-Intelligence (NSG): A unified community of geospatial intelligence producers and users, leveraging expert tradecraft, regional expertise, and strength in numbers in the delivery of multi-source, multi-intelligence data and knowledge to all stakeholders. Physical Data Model: The representation of a data design typically derived from a logical data model that takes into account the character and constraints of a given database management system; includes all the database artifacts required to create relationships between tables or achieve performance goals, such as indexes, constraint definitions, linking tables, partitioned tables or clusters. Profile: The result of selective removal of SDSFIE 3.0 elements subject to any higher authority mandatory restrictions directing the removal of optional elements from SDSFIE Gold to create an Adaptation. (see Appendix A for more details) SDSFIE Implementation: After development and approval, implementation is the process of executing governance, creating adaptation schemas, then migrating existing data sets from SDSFIE 2.x versions to 3.0. Implementation is complete when SDSFIE 3.0 compliant datasets are in production use at each implementation-level organization. Standards Activities (SA): SDSFIE Implementation activities that promote the standard both within the community as well as within DoD standards management bodies

10/19/2009 Ver. 1.0

7

Section 1: Introduction As established by the Deputy Under Secretary of Defense for Installations and Environment, the Defense Installation Spatial Data Infrastructure Group (DISDIG) is responsible for overseeing the implementation of SDSFIE, which includes providing the technical oversight and guidance to facilitate the deployment of the re-engineered SDSFIE 3.0 standard across the DoD enterprise. The SDSFIE has become an essential data standard for DoD installations and environment business requirements, and each of the Components has established policy or guidance requiring its use for business domain geospatial data. As part of the SDSFIE 3.0 development, the standard will also become an integral part of the data standards used in the National System for Geospatial-Intelligence (NSG), as required by DoD Directive 5105.60, “The National Geospatial-Intelligence Agency.” In the first decade of the SDSFIE development, it was generally seen as a technical activity with a project-level scope. It was governed primarily by technical staff and was revised annually according to user-level technical inputs. Given the new realities of the DoD information enterprise, the SDSFIE must now be seen in a programmatic context as an essential element of the Department’s information resource management infrastructure (see Goal 3, below). The standard must be governed and resourced in a manner commensurate with its enterprise role. A programmatic view of how the current SDSFIE re-engineering activity relates to the overall evolution of SDSFIE is depicted in Figure 1.

Figure 1: A programmatic view of the evolution of the SDSFIE. Figure 1 depicts the major activities governed by this strategy document, and how these fit into the long-term evolution of the standard. The development and use of SDSFIE has been a continuous activity which began in 1992, with updates happening more or less annually between 1996 and 2006. Prior to SDSFIE 3.0, all earlier versions were not (in

10/19/2009 Ver. 1.0

8

the strict sense) built upon a logical data model (LDM). In November, 2006, the leaders representing the Installation Geospatial Information and Components (IGI&S) programs from each Component and the US Army Corps of Engineers held a workshop to develop a five-year vision for the Spatial Data Standards for Facilities Infrastructure and Environment (SDSFIE). Their consensus SDSFIE Vision Statement is:

SDSFIE will become the single DoD spatial standard that supports common implementation and maximizes interoperability for Installations, Environmental and Civil Works Missions.

This group also developed a set of Guiding Principles, Goals, and Objectives for SDSFIE (a copy of this document is available upon request). Through brainstorming and discussion, the group developed a comprehensive set of goals listed below in order of their potential to contribute to achieving the vision:

• Goal #1 Advance and maintain the standard in order to achieve interoperability for both data and systems, using accepted industry practices.

• Goal #2 Align SDSFIE with functional community mission requirements and the DOD Business Enterprise Architecture (BEA).

• Goal #3 Implement a coordinated SDSFIE program management process. • Goal #4 Educate, train, and support the implementation of the SDSFIE within the

user community. • Goal #5 Promote SDSFIE adoption DOD-wide.

These goals were intended to apply across a 5-year time horizon, 2007 through 2012. Figure 2 is a more detailed view of the phases in Figure 1, including the specific documents supporting each phase of the cycle for the transition to SDSFIE 3.0. This strategy document is written from the DoD enterprise level, and is intended to integrate with other strategies and plans as shown in the figure. For example, this DISDIG strategy calls for a number of Component-specific plans to be developed, collectively referred to here as “IGI&S Strategies.” This DISDIG strategy is also based in part on the plans and governance documents associated with the execution of the Geospatial-Intelligence (GEOINT) Structure Implementation Profile (GSIP).

10/19/2009 Ver. 1.0

9

Figure 2: The DISDIG Strategy for Development & Implementation of SDSFIE 3.0 – Key Phases and Source Documents.

Purpose and Scope If a data standard is to be an effective tool for data sharing, it must be developed by a consensus of the users and uniformly adopted across the enterprise. Regardless of the technical rigor and innovation in SDSFIE 3.0, it will fail to achieve the vision and goals laid out by the DISDI Group if any one part of the business enterprise fails to implement it properly. The DISDI Group consensus purpose for this strategy document is to facilitate implementation of the standard. The scope of the strategy is two-fold: 1) to establish I&E domain-level implementation guidance, and 2) to serve as a framework for the Components’ implementation strategies or plans. This strategy is primarily intended to function as guidance. It articulates a consensus enterprise level (programmatic) approach for the SDSFIE, and it will remain a living document. The DISDIG intends to use this document to capture best practices and lessons learned as they occur throughout the 3.0 data standard re-engineering event cycle. This document consists of an over-arching SDSFIE 3.0 implementation “roadmap,” including key activities to occur along the way and “best practice” options for accomplishing the activities. Many elements of this strategy are intended to also serve as a model for the Component-level implementation strategies and plans necessary to complete the development and implementation of SDSFIE 3.0.

Governance Establishing governance is the most significant activity necessary to ensure successful implementation of the SDSFIE 3.0, and to ensure its sustainment and evolution into the future. Why is governance so important? In short, governance is the “best management

10/19/2009 Ver. 1.0

10

10/19/2009 Ver. 1.0

11

practice” (BMP) for executing change management in large organizations like DoD. Governance activities need to be established at all levels of the organization, in order to handle the spectrum of change management challenges (e.g. from enterprise-level integration and resourcing down to technical schema/logical model content approval). The need for governance of technical changes is paramount to the standard’s success in the long-term. This has already been established in the SDSFIE Architecture v 1.5: “Profiling1 is defined as the generation of a strict subset of an LDM to form another LDM. Extension2 is the addition of LDM elements to one LDM to form another LDM. Profiles and Extensions have been viewed as undesirable by some, but actually they are highly desirable because they allow for the local Adaptation that makes a model more immediately useful. Extensions, when controlled by a definitive set of rules, can be easily managed and manipulated using common tools.” The control of who can develop adaptations (profiles and extensions), and what the scope of those adaptations can be is an essential task which the Components should govern using consensus-based business rules. This document establishes a department level governance plan for SDSFIE 3.0 (Appendix B), including a feedback loop to capture gaps or lessons learned as identified by the SDSFIE contractor or the Components during execution of their implementations. These gaps will be reported to the DISDIG as they are identified, and may be distributed as lessons learned to assist others implementing SDSFIE 3.0.

Types of Activities: Standard or Data The evolution of SDSFIE from 2.6 to 3.0 will be a complex process. The types of activities required to make SDSFIE 3.0 an implementation success can be logically divided into two primary categories: Standards Activities (SA) and Data Activities (DA). Standards Activities (SA) include all steps needed to promote the standard both within the community as well as within DoD standards management bodies. Obtaining Domain Governance Board approval and achieving DISR mandated status are examples of such activities. Data Activities (DA) include developing migration plans, technical solutions for ensuring continuity of operations, creating data schemas and generating implementation-specific migration tools. Central to the success of SDSFIE evolution is training. Training activities are considered a Data Activity (DA) because it affects both the transition from 2.6 to 3.0 as well as future sustainment and management.

Organizations DISDI Group – The OSD level cross-service working group designated by the Installations & Environment (I&E) Domain Governance Board (DGB); responsible for

1 For the consensus definition of profile, see Key Terms at the beginning of this document 2 For the consensus definition of extension, see Key Terms at the beginning of this document

overseeing the implementation of SDSFIE. It manages SDSFIE transformation under the leadership of the DISDI Program Manager. IGI&S Programs – The component headquarters level activities responsible for oversight, policy, and guidance pertaining to installation geospatial information and services. The IGI&S program leaders are members of the DISDI Group. Implementation Level Organizations – As defined by each IGI&S program; these are the organizations that participate in actual implementation of the SDSFIE standard. They collect and maintain geospatial data and provide geospatial related services. Data Proponents – Lines of business or functional organizations that have an interest in a specific mission dataset. The data proponents are responsible for collecting and maintaining the mission dataset (see also: Key Terms). U.S. Army Corps of Engineers (USACE) – The designated contract management agency for SDSFIE technical support. On behalf of the DISDIG, USACE scopes and awards activities to the SDSFIE support services contractor team. STARS Team – The Solutions and Technology for the Advancement of the SDSFIE (STARS) Team is the SDSFIE support services contractor team.

Roles and Responsibilities The organizations listed above, and all users of the SDSFIE, must have a clear understanding of their roles and responsibilities. At the DoD enterprise level, there are five distinct SDSFIE 3.0 implementation roles for the purposes of this strategy:

Program Management: Develop consensus-based guidance for the lifecycle of activities necessary to develop, deploy, and refine the SDSFIE at the enterprise level. Project Management: Execute discrete portions of the overall program; e.g. manage the STARS Team of contractors. Governance: Providing the management controls necessary to ensure effective implementation of SDSFIE 3.0 as a DoD standard. Technical Support: Providing the technical capabilities necessary to develop, deploy, and sustain the SDSFIE 3.0 standard. Tactical Execution: Performing the activities required to operationally implement the SDSFIE 3.0 standard.

Table 1 identifies the organizations involved in SDSFIE 3.0 implementation, and outlines their primary responsibilities (aligned by role).

10/19/2009 Ver. 1.0

12

Table 1: Organizational Roles and Responsibilities.

Organization Roles Responsibilities Program Management

Programmatic technical oversight Strategic planning Coordination & resource oversight

DISDIG

Governance Develop top-down guidance Monitor compliance

Tactical Execution Develop migration & adaptation plans Convert existing data

IGI&S Programs

Governance Customized top-down guidance Implement custom guidance Monitor compliance

USACE Project Management Contract management of the STARS Team Manage resources

Tactical Execution Maintain spatial data resources Data Proponents Governance Develop spatial data requirements

Manage spatial data resources STARS Team Technical Support Develop SDSFIE 3.0 data model

Develop conversion toolset Develop O&M toolset Prepare training and education materials Develop and maintain help-desk capabilities Provide thought leadership & industry best practices

Communication This strategy should be communicated to all stakeholder organizations. Successful implementation and sustainment of SDSFIE also hinges on communicating the new standard to the community, building knowledgeable champions at every level, and rolling out a multi-tier training program. Table 2 provides a high level description of important communications necessary to support SDSFIE 3.0 implementation. A more detailed communications plan is presented in Appendix C.

10/19/2009 Ver. 1.0

13

Table 2: SDSFIE Communications Matrix.

Installations & Environment NGA Top-Down Bottom Up Socialization

GWG Focus Group briefings Out-reach Engage NGA Leadership Informative Briefings Descriptive Documents

Strategic Support GSIP Strategy Documents Vision Statements Long-range Planning Docs

Tactical Support GSIP component plans Technical Documents Operate Help Desk Report questions Change Management Change Requests Rollout Education & Training Compile Lessons Learned Identify Gaps & Lessons Learned

Data Reporting Data Requests Data Reports

Governance GWG Guidance Publish Guidance/policy Provide Feedback Participate in Governance Participate in Governance

Groups Compliance

Compliance Criteria Compliance Monitoring Compliance Reporting

Coordination Review Documentation in Focus Groups

Document Standard for Approvals

SDSFIE Development and Implementation Strategy Overview The “roadmap” of this SDSFIE 3.0 strategy document is expressed as a timeline with four distinct phases. The phases are a framework for the key milestones and activities necessary to achieve development and implementation of the standard, and the organizations responsible for them. In the following sections of the document, the phases are described in detail and, where possible, recommended best practices and solutions are provided. The actual timeline and methods to be employed, beyond the level of detail outlined in this document, are at the discretion of the Components. In fact, a key requirement of this enterprise-level strategy is that each Component (DISDIG member organization) must develop their own strategy as a follow-on activity, with detailed implementation processes, milestones, and governance plans applicable at their level. The phases of the SDSFIE 3.0 development and implementation process, illustrated in Figure 3, are described as follows:

10/19/2009 Ver. 1.0

14

LDM Development: The Development phase, largely complete by the date of this strategy, includes activities for completing the SDSFIE 3.0 LDM and Implementation support tool sets. Other activities included are: strategic planning, preparation of training and education materials, and development of a suitable governance process. Approval: After the SDSFIE 3.0 LDM is complete, a brief approval phase will follow. This will include governance approvals, formal release (publishing), and other actions such as registering and publishing the standard in DoD enterprise registries. Implementation: Activities during the implementation phase need to only be done once, at the onset of the release. These activities include the development and implementation of Adaptations, and conversion of existing databases from previous versions of the SDSFIE to SDSFIE 3.0. Transition: The final phase in this strategy begins when initial migration of existing data and systems is essentially complete and focuses on fully implementing governance and feedback plans. It includes all activities necessary to transition use of SDSFIE 3.0 into a steady-state operation and maintenance mode. Example activities include gathering and evaluating lessons learned in order to translate them into potential requirements for a future standard update.

Figure 3: Phases of the SDSFIE 3.0 Development & Implementation Strategy. Each of these phases has a range of activities which must be executed in a logical sequence. Table 3 lists the primary activities, grouped by phase, and the organization with primary responsibility for execution. The implementation process phases and activities serve as the outline structure of the remainder of this document. 10/19/2009

Ver. 1.0 15

Table 3: SDSFIE implementation high level -activities grouped by phase.

SDSFIE High Level Activity Resource Names Phase 1: LDM Development Complete SDSFIE 3.0 LDM STARS Team Create Implementation Tools STARS Team Develop Training Courses STARS Team Review and Align DGMP with SDSFIE DISDIG Develop DISDIG Strategy DISDIG Integrate SDSFIE with GSIP DISDI PM Phase 2: Approval Acceptance of Standard DISDIG DGB Approval DISDIG Publish Standard DISDIG Register SDSFIE with DoD MDR DISDI PM Propose Standard for DISR DISDI PM Advocate SDSFIE to ITSC and GWG DISDI PM Deploy Implementation Tools STARS Team Create and Maintain Registry and Repository STARS Team Integration of SDSFIE with GSIP DISDI PM Create SDSFIE Deployment Help Desk STARS Team Phase 3: Implementation Develop Component Level Strategy IGI&S PROGRAMS Deploy Training Courses STARS Team Operate and Maintain Registry and Repository STARS Team Deploy Adaptation Tools STARS Team Create and Register Profiles and Extensions IGI&S PROGRAMS Pilot Study Data Migration IGI&S PROGRAMS Convert Existing data Implementation Level Implement Communications Plan IGI&S PROGRAMS Monitor Migration Compliance IGI&S PROGRAMS Integration of SDSFIE and GSIP DISDI PM Implement SDSFIE Deployment Help Desk STARS Team Phase 4: Transition Identify Business System Modification for SDSFIE Linkage Implementation Level Monitor Standard Compliance DISDIG & Components Implement Change Management Plan DISDIG & Components Implement Communications Plan IGI&S Programs Implement Component Level Governance Plan IGI&S Programs Integration of SDSFIE with GSIP DISDI PM Maintain SDSFIE Deployment Help Desk STARS Team

10/19/2009 Ver. 1.0

16

Section 2: Phase 1 – LDM Development The LDM Development Phase began in November, 2006 with the 5-year Vision for SDSFIE. It will conclude when the SDSFIE 3.0 LDM is accepted by the COR (USACE TEC) and the DISDIG. The focus of this phase is the top-down activities to design, build, and review the SDSFIE 3.0 Logical Data Model (LDM) and various strategic planning documents. Primary execution responsibilities for this phase rest with the DISDIG and the STARS Team. Figure 4 is a detailed Phase 1 activities list including key milestones and responsibilities. The durations and milestones are subject to change.

PHASE 1 – LDM Development: consists of top-down activities for completing the SDSFIE 3.0 LDM, a suite of implementation & support tools, and strategic planning.

Figure 4: Gantt Chart showing execution sequence and draft timelines for Phase 1.

Primary Activities - Development Phase Phase 1 consists of six primary activities, three of which have sub-activities.

Complete SDSFIE 3.0: Complete the SDSFIE 3.0 LDM, deliver it for government review and finalize for acceptance. Create Implementation Tools: Create a suite of web-based tools necessary to support the SDSFIE Implementation activities such as data migration, adaptation,

10/19/2009 Ver. 1.0

17

editing, and registration. These tools must be in place in order to start many activities in Phase 3 (Implementation). Develop Training Courses: Scope and prepare the training materials required to support the roll-out of the SDSFIE 3.0 to the Components. These courses will help establish the foundation of knowledge necessary for users to develop physical implementations of the SDSFIE 3.0 LDM. DGMP / SDSFIE Alignment: Ensure the SDSFIE 3.0 LDM aligns with the DGMP v 1.0 specification. Develop DISDIG Strategy for SDSFIE 3.0 (this document): Articulate the major activities necessary for completion and initial implementation of the standard. Describe the logical sequence of activities and dependencies in order to promote a coordinated implementation effort. Document how the DISDIG will achieve the 5-year vision, goals and objectives, through rollout of the new standard and transition into a stable operation & maintenance cycle at the enterprise level. Integration of SDSFIE with GSIP: Socialize the emerging SDSFIE 3.0 LDM with the GEOINT standards community to ensure it will be interoperable with the GSIP.

The assignment of these primary activities to the SDSFIE organizations is presented in Table E-1 in Appendix E.

STARS Team Responsibilities - Development Phase During the Development Phase, the STARS Team is responsible for the lion’s share of SDSFIE 3.0 critical path activities. The three critical path activities are:

• Completion of the SDSFIE 3.0 LDM. • Creation of the Suite of SDSFIE Implementation Tools (the Model Registry and

Repository, Database Creation Tool, Migration Tool, and Validation Tool). • Development of Training Courses and materials. This includes the on-line

materials related to use of the suite of tools.

DISDIG Responsibilities - Development Phase The DISDIG is responsible for oversight and review of the SDSFIE 3.0 LDM development, ensuring authoritative inputs are being provided from the various business lines and data proponents. The DISDIG is also responsible to the I&E Domain Governance Board for creating a strategy for the effective deployment of SDSFIE 3.0 across the DoD. The foundations of oversight and strategic assignment of responsibilities must be clearly established during the Development Phase. The DISDIG is responsible for completing two critical path activities during this phase:

• Development of the DISDI Group Strategy for the Development and Implementation of SDSFIE 3.0 (i.e. this document).

• Ensure SDSFIE and DGMP are Aligned. The DISDI staff will lead this activity, through the Metadata Working Group.

10/19/2009 Ver. 1.0

18

IGI&S Program Responsibilities - Development Phase The IGI&S Programs are not principally responsible for activities during this phase except for participation in the DISDIG, and support for ensuring authoritative inputs are being provided from the various business lines and data proponents.

Best Management Practice: Users who will be migrating existing SDSFIE data to version 3.0 should validate their current SDSFIE data at the earliest opportunity possible. Existing 2.5 or 2.6 data sets can be validated using the SDSFIE Assistant tool available at www.sdsfie.org.

Implementation Level Organizations Responsibilities - Development Phase The Implementation Level Organizations do not have direct activity responsibilities during this phase, but should be participating in or monitoring the SDSFIE 3.0 LDM development.

Data Proponents Responsibilities - Development Phase The Data Proponents are responsible for providing Subject Matter Experts during the SDSFIE Development.

USACE Responsibilities - Development Phase The USACE key responsibilities are management of the scope & resources applied to the technical support contract (STARS Team). The USACE Contracting Officer’s Representative (COR) plays a key role in this phase and will need to interact closely with the DISDIG to ensure the support contract is accomplishing the tasks and priorities set by them.

10/19/2009 Ver. 1.0

19

Section 3: Phase 2 - Approval Phase 2 begins when the SDSFIE 3.0 LDM is accepted by the government, and ends when the standard is fully registered in the DoD Metadata Registry (MDR) and the DoD IT Standards Registry (DISR). After concurrence by the I&E DGB, Phase 3 activities (implementation) can begin in parallel with remaining Phase 2 activities. As in Phase 1, primary execution responsibility for the Approval activities rests with the DISDIG and the STARS Team. Figure 5 is a detailed Phase 2 activities list including key milestones and responsibilities. The durations and milestones are subject to change.

PHASE 2 - Approval: a brief phase preceding implementation; includes governance approvals, formal release, and other actions such as registering and publishing the standard in DoD enterprise registries.

Figure 5: Gantt Chart showing execution sequence and draft timelines for Phase 2.

Primary Activities for the Approval Phase This phase consists of six primary activities one of which has sub-activities. These six primary activities are explained as follows:

Acceptance of Standard: Accept the SDSFIE 3.0 LDM from the STARS Team when the LDM has been reviewed and finally delivered. DGB Approval: Propose the standard for approval by the Domain Governance Board. Publish Standard: Physically publish the standard to the SDSFIE web page and other outlets as appropriate. Propose Standard for DISR: Submit the SDSFIE 3.0 standard to the GEOINT Working Group (GWG) and its focus groups for inclusion in the DISR.

10/19/2009 Ver. 1.0

20

Register SDSFIE with DoD MDR: Insert SDSFIE LDM in the DoD MDR upon approval into DISR. Advocate SDSFIE to Information Technology Standards Committee (ITSC) and GWG: Part of the process to include the SDSFIE in the DISR is that the community has to advocate the standard to ITSC. The ITSC chartered the GWG to review and recommend all geospatial standards for inclusion into the DISR. As part of this process, the DISDIG will need to present to the GWG the technical aspects of the standard and show its widespread use. The GWG will use this information to decide if SDSFIE will be recommended for inclusion into the DISR. Deploy Implementation Tools: Tools created in Development phase will be deployed during this phase in preparation for the Implementation (Phase 3). Integration of SDSFIE with GSIP: Ensure that SDSFIE supports the cross-system interoperability goals of the GSIP. Create and Maintain Registry and Repository: Create the registry and repository used to record SDSFIE 3.0 Profiles and Extensions. Create and Maintain SDSFIE Help Desk Support: Help desk support needs to be created to support SDSFIE data managers and technical support personnel.

The assignment of these primary activities to the SDSFIE organizations is presented in Table E-2 in Appendix E.

STARS Team Responsibilities - Approval Phase After the SDSFIE 3.0 LDM is officially published, the STARS Team will be preparing to technically support SDSFIE 3.0 Implementation and Transition. The STARS Team is responsible for completing three activities that are critical path during the approval phase:

• Deploy Implementation Tools. • Create and maintain the Model Registry and Repository. • Provide Help Desk Support.

There are no predecessor critical path activities that could impede the progress of any STARS Team activities in this phase.

DISDIG Responsibilities - Approval Phase Most of the activities in the SDSFIE 3.0 LDM Approval phase are related to the official approval and registry of the standard, and these activities are the responsibility of the DISDIG. The DISDI Program staff plays a key role in executing many activities and coordination on behalf of the DISDIG. 10/19/2009

Ver. 1.0 21

The DISDIG is responsible for completing seven activities during the SDSFIE Approval phase as follows:

1. Acceptance of Standard - The SDSFIE 3.0 LDM will be accepted by the DISDIG when it has been delivered by the STARS Team and approved as accepted by the DISDIG.

2. DGB Approval – Upon acceptance of the final release from the STARS Team, the DISDIG will place SDSFIE on DGB agenda and seek its approval.

3. Publish Standard –After DGB Approval, the DISDI PM will publish SDSFIE as a final standard to DISDIG members.

4. Register SDSFIE with DoD MDR – Upon DGB approval, the DISDI PM will start the process to insert SDSFIE in the DoD MDR.

5. Propose standard for DISR – The DISDI PM will introduce the SDSFIE to the DISR standards committee.

6. Advocate SDSFIE to ITSC and GWG – The DISDI PM will prepare and present the SDSFIE to the working groups designated by the DISR secretariat (likely GWG) and seek recommendation to insert in DISR as mandated, based on its wide adoption and because it is a DoD IGI&S consensus standard.

7. Receive DISR Mandated status – Finally, SDSFIE will obtain mandated DISR status.

All seven activities are important for accepting the SDSFIE 3.0 LDM, but only the DGB approval is a critical path activity. The risk of these activities triggering a change to the accepted standard is very small. After DGB approval, implementation phase activities can be started in parallel with these Approval Phase activities.

IGI&S Programs Responsibilities - Approval Phase The IGI&S Programs do not have any direct activity responsibilities during the SDSFIE Approval phase other than participating in the DISDIG and monitoring the progress of the SDSFIE 3.0 LDM registration and approval process.

Implementation Level Organizations Responsibilities - Approval Phase The Implementation Level Organizations do not have any direct activity responsibilities during this phase.

Data Proponents Responsibilities - Approval Phase The Data Proponents do not have any direct activity responsibilities during this phase.

USACE Responsibilities - Approval Phase The USACE key responsibilities continue to be management of the scope & resources applied to the technical support contract (STARS Team). The USACE Contracting Officer’s Representative (COR) plays a key role in this phase and will need to interact closely with the DISDIG to ensure the support contract is accomplishing the tasks and priorities set by them.

10/19/2009 Ver. 1.0

22

Section 4: Phase 3 - Implementation The implementation phase begins when SDSFIE 3.0 is formally published by the DISDIG, and ends when the Components are mostly complete with adaptation and migration of existing SDSFIE datasets to the new standard. In Phase 3, the focus shifts from a top-down to bottom-up perspective, with the primary execution responsibility shifting to the IGI&S Programs. Early in Phase 3, IGI&S program staff will establish Component-specific rules for adaptations, develop implementation plans, and define Component-level governance. The primary Phase 3 activity deals with establishing the SDSFIE 3.0 as the operational standard at the installation level. A key element of this activity is the migration of previous SDSFIE version geospatial databases to the 3.0 version.

PHASE 3 - Implementation: After approval of the standard, these one-time activities include development and implementation of adaptations and the conversion of existing databases from older versions of the SDSFIE to SDSFIE 3.0.

Primary Activities for the Implementation Phase The SDSFIE 3.0 Implementation Phase is too complex to be simply and accurately described as a single linear timeline of the activities. The strategy below, however, identifies the key activities required during the Implementation Phase to successfully migrate to SDSFIE 3.0. The most important activity is the development of IGI&S program level (Component level) strategies and plans. These subordinate plans will elaborate on and adapt the activities outlined below into specific execution plans, applicable to the requirements of the Components. The Component IGI&S Programs can begin creating their specific Implementation Plans as soon as the DISDIG SDSFIE Strategy is complete. Throughout the Implementation Phase, Components should use their governance groups (or other means) to begin gathering feedback from lower organizations, users, and vendors. This feedback will be vetted, and appropriate cross-service issues will be reported to the DISDIG.

Develop Component Level Strategy (see Appendix D): Implementation plans will be prepared by the Components to direct the deployment of the SDSFIE 3.0 standard in their respective IGI&S communities. These plans will be tailored to the Component’s specific operational characteristics and will include:

• A governance plan for the development of adaptations and extensions and initial required metrics; boilerplate contracting language that can be used to effectively structure contractual data collection/generation activities to direct contractors to produce spatial data work products that are compliance with the SDSFIE 3.0 standard

• A Component specific governance plan for the long-term operation and maintenance of the SDSFIE.

10/19/2009 Ver. 1.0

23

• A system of compliance metrics to measure and assess compliance of various IGI&S SDSFIE 3.0 deployments.

Deploy Training Courses: The training courses developed in Phase 1 will be delivered to IGI&S Programs execution level to ensure proper use of the migration toolset and effective deployment of SDSFIE 3.0. Operate and Maintain Registry and Repository: Management of SDSFIE LDM Registry and Repository and implementation of access control measures identified by Components adaptation governance plans. Create and Register Adaptations: The Component SDSFIE Adaptations including the Adaptation’s profile and various extensions must be registered in the SDSFIE Registry and Repository to be officially accepted. Based on the governance process, each Component will document the SDSFIE Adaptation and its profile and various extensions they have accepted for use in their functional communities. Conduct a Pilot Study Data Migration: Conduct a data migration pilot study for an implementation level organization in the group to identify migration issues. One key issue which should be addressed is how external spatial standards will be incorporated into the process or migrated data sets. Migrate Existing Data Sets: Convert all geospatial data holdings to the SDSFIE 3.0 data model according to the established Component Adaptations. Create and deploy SDSFIE 3.0 Component Adaptation physical data models. Generate scripts to convert data from previous SDSFIE versions to SDSFIE 3.0 Implement Communication Plan: A communication plan will be implemented to continue establishing functional buy-in, ensure compliance and identify proponents, dialogue with users after release to discover issues as they develop, and engage vendors/industry who will largely do the implementation. Integration of SDSFIE with GSIP: Ensure that SDSFIE supports the cross-system interoperability goals of the GSIP.

The assignment of these primary activities to the SDSFIE organizations is presented in Table E-3 in Appendix E.

STARS Team Responsibilities - Implementation Phase The STARS Team role during Implementation will focus on providing the technical support required to train and educate the end users on how to migrate existing SDSFIE databases, and managing the registration & implementation of adaptations. The STARS Team help desk support will be instrumental to success in this phase. The STARS Team will also implement Component specific requirements resulting from their adaptation governance plans.

10/19/2009 Ver. 1.0

24

• Deploy Training Courses • Deploy Transition Tools • Operate and Maintain Model Registry and Repository • Provide Help Desk Support

DISDIG Responsibilities - Implementation Phase The DISDIG role during Implementation will focus on providing the management and technical oversight to ensure the SDSFIE 3.0 LDM is effectively deployed across the DoD enterprise. Additionally, the DISDIG will be responsible for ensuring the foundations of oversight and strategic planning established during the Development and Approval phases are properly executed.

IGI&S Programs Responsibilities - Implementation Phase The IGI&S Programs begin to take a prominent role in the deployment of the SDSFIE 3.0 LDM during the Implementation phase. The deployment of Component specific SDSFIE 3.0 adaptations will require the following activities:

• Develop Component Level Implementation Plan • Create Logical Data Model Adaptation(s) • Register profiles and extensions • Create Physical Data Model • Create and Test Migration Scripts • Conduct a Pilot site data migration • Implement migration compliance checks

10/19/2009 Ver. 1.0

25

Best Management Practice: Data Migration Pilot Study IGI&S Programs are responsible for migrating their existing SDSFIE data to the newer SDSFIE 3.0 format. The process used by the Components to perform the migration is largely at their discretion. As a Best Management Practice, however, a carefully planned and executed Data Migration Pilot is recommended before a program-wide migration is performed. The Data Migration Pilot Study will afford the IGI&S Program an opportunity to discover and resolve issues related to the migration in a controlled setting, and provide valuable first hand experience before attempting to complete the conversion for all implementation level organizations. A suitable existing SDSFIE data set from a single installation should be selected for the Data Migration Pilot Study, one that is representative of the other SDSFIE data across the IGI&S Program and of comparable quality and complexity. The Data Migration Pilot Study should be carefully planned according to the data migration approach described in the IGI&S Program’s SDSFIE Implementation Plan. This will test the rigor of the plan as well as specific issues related to the Program’s other existing data.

External Spatial Data Standards External spatial data standards that are complementary to the SDSFIE 3.0 LDM are known to exist, and some of these standards must be used in the IGI&S communities by Federal or DoD mandate. Currently, three external spatial data standards have been identified (i.e. the FGDC’s soils classification standard and wetlands mapping standard, and the international airfield spatial data standard, AIXM, used by NGA). One objective of the IGI&S Program Pilot Study should be to identify other external spatial data standards. The pilot study results should identify as many as possible of the external standards in use and a procedure for dealing with these in the remaining adaptations and migrations to be done by the Component. The procedure should include a way to control the use and update of these external standards within the bounds of IGI&S governance mechanisms. External standards will likely impact the Adaptation of the SDSFIE 3.0 LDM described in Appendix A.

Implementation-Level Organizations Responsibilities - Implementation Phase Implementation-Level Organizations are the execution level of the SDSFIE conversion process. Some IGI&S Programs will perform all existing data migration acting as an Implementation-Level Organization. Others will direct their implementation level organizations to perform these existing data migrations.

10/19/2009 Ver. 1.0

26

As directed by the IGI&S Programs’ implementation plans, the Implementation Level Organizations take a prominent role in the deployment of the SDSFIE 3.0 during this phase. After Component specific SDSFIE 3.0 issues have been addressed by the IGI&S Programs’ Data Migration Pilot Study, the Implementation Level Organizations will migrate existing data and commence operational use of the SDSFIE 3.0 standard.

Best Management Practice: Data Migration Process Diagram and Activities (see below)

As a Best Management Practice, existing data migration will be performed using the following sequence of activities (as illustrated in Figure 6): Validate and fix existing data: An important first step in the migration of existing SDSFIE data is establish that there are no SDSFIE format issues with the existing data. The SDSFIE Assistant can be downloaded from the www.sdsfie.org Web site. This application will identify any deviations from the previous SDSFIE version (i.e. 2.4-2.61). Any identified anomalies must be corrected before the existing data can be converted. Implementation level organizations are encouraged to perform these checks as soon a possible. Develop Migration Plan: Using the IGI&S Program SDSFIE Implementation Plan as a guide, the implementation level organization needs to develop a existing data Migration plan to formally describe the sequence of events that will be performed on the existing SDSFIE data set to effectively migrate it.

Test Migration Plan: After the existing data Migration Plan has been prepared and reviewed, its effectiveness needs to be confirmed in a test environment. Typically, this test will be performed in a copy of the full production existing SDSFIE data set that has been segregated into a separate schema (preferable a separate database instance). Evaluate Test Migration: The test existing data set needs to be carefully reviewed after the test migration to ensure the existing data very converted as planned. If anomalies are observed, any issues that caused them need to be addressed in a revision of the Migration Plan, and this new Migration Plan needs to be tested. This cycle needs to be repeated until the test existing data set does not contain any anomalies.

10/19/2009 Ver. 1.0

27

Create Production Backup and Freeze Data Maintenance: When an error free Migration Plan has been developed and adequately tested, an export backup copy of the production existing data needs to be created and data maintenance of the production existing data set needs to be suspended until after the data migration process is complete and verified. This production backup will be held at a minimum until after the production data have been migrated and that migration has been verified as correct. Migrate Production Data: After a reliable backup copy of the existing production data exists, the Migration Plan will be used to migrate all existing SDSFIE production Data. Evaluate Production Migration Process: Upon completion of the production existing data migration process, the migrated production existing data set needs to be carefully reviewed to ensure the existing data were converted as planned. If anomalies are observed, any issues that caused them need to be addressed in a revision of the Migration Plan, and this new Migration Plan needs to be tested. This cycle needs to be repeated until the production existing data set does not contain any anomalies. Resume Data Maintenance of the New Existing Data: Routine data maintenance can be resumed on the SDSFIE 3. 0 compliant data set when a production data set has been successfully migrated (i.e., no errors detected in review). Migrate Existing Applications: All data applications need to be migrated to work with the new SDSFIE 3.0 production data set. Migration of these applications can be started at anytime after the SDSFIE 3.0 LDM has been released so that they can be ready in parallel with the migration of the production data. Maintain Existing Business Data Connections: Any SDSFIE data that did not directly convert to the new SDSFIE 3.0 format will be diverted into business specific data tables that will be suitably linked to the various SDSFIE feature classes.

Data Proponents Responsibilities - Implementation Phase If IGI&S Programs have identified data proponent organizations they must take the role of an Implementation-Level Organization and proceed to implement the SDSFIE 3.0 transition as identified in Component Implementation Plans.

USACE Responsibilities - Implementation Phase The USACE key responsibilities are management of the scope & resources applied to the technical support contract (STARS Team). The USACE Contracting Officer’s Representative (COR) plays a key role in this phase and will need to interact closely with the DISDIG to ensure the support contract is accomplishing the tasks and priorities set by them. USACE project management focus will likely shift to supporting the IGI&S programs’ implementation of the standard through STARS Team supporting tasks.

10/19/2009 Ver. 1.0

28

Section 5: Phase 4 - Transition Because the implementation of SDSFIE 3.0 is such a fundamental shift for the DoD I&E business mission area, a distinct transition phase is needed to finalize implementation and begin a consensus-based change management lifecycle which will be very different from past change management of SDSFIE. The final phase in this strategy begins when migration of existing data is essentially complete. The transition phase focuses on fully implementing governance and feedback plans; thus, this phase is considered complete once all governance plans are fully enacted and the use of SDSFIE 3.0 is in a steady-state operation and maintenance mode. Once this phase is complete, as a follow-on activity the DISDIG and Component headquarters must manage the forward evolution of the standard and monitor compliance.

PHASE 4 - Transition: all activities necessary to transition use of SDSFIE 3.0 into a steady-state operation and maintenance mode; includes establishing governance bodies and business practices to manage the evolution of the SDSFIE.

Primary Activities for the Transition Phase Please note that actual Transition phase activities for each IGI&S Program may require multiple iterations, e.g. identifying and connecting existing business databases to SDSFIE 3.0 databases. Components will use their governance groups (or other means) to continuously gather feedback from lower organizations, users, and vendors. This feedback will be vetted, and appropriate cross-service issues will be reported to the DISDIG.

Document Interim Solutions for SDSFIE/Business System Continuity of Operations: Interim solutions for SDSFIE/business system data relationships (not otherwise covered through adaptations) should be documented in preparation for developing more permanent solutions. These solutions could be either an SDSFIE change or a data proponent action. Collect and Evaluate Lessons Learned: Utilize implementation and conversion process lessons learned to gather information for improvement of training materials, governance processes, and other activities that are continued in the operations and maintenance phase of SDSFIE 3.0. Monitor Standard Compliance: IGI&S SDSFIE 3.0 deployments will be monitored for compliance throughout deployment using the compliance metrics developed in the Implementation Phase. Implement Change Management Plan: Translate Change Management plan into system requirements. Modify model registry to allow for access control, user and role management.

10/19/2009 Ver. 1.0

29

Implement Communication Plan: Implement and disseminate governance plan for SDSFIE change management and adaptation control. Actively pursue gathering of feedback from the implementation phase, by requesting Components and implementation-level organizations to provide migration reports. Implement Component Level Governance: Implementation of governance plan to include organizing decision bodies and assignment of roles in the SDSFIE change management and adjudication processes. This will be conformant to Strategic Governance plan presented in appendix B. Integration of SDSFIE with GSIP: Ensure that SDSFIE supports the cross-system interoperability goals of the GSIP.

The assignment of these primary activities to the SDSFIE organizations is presented in Table E-4 in Appendix E.

Important Execution Considerations for the Transition Phase

STARS Team Responsibilities - Transition Phase The STARS Team role during Transition will be providing help desk support to all DoD organizations converting SDSFIE existing data to 3.0. The STARS Team will implement access and user/role management tools and be the change agent for the forward evolution of the standard. During Transition, the STARS Team will provide the necessary technical support to identify interim solutions for continuity of operations for Components’ business systems. The Team will also perform changes to the SDSFIE as directed through the governance process led by the DISDIG.

DISDIG Responsibilities - Transition Phase The DISDIG role during Transition will continue to focus on providing the management and technical oversight to ensure the SDSFIE 3.0 LDM is effectively used and managed across the DoD enterprise. Additionally, the DISDIG will be responsible for ensuring the foundations of oversight and strategic planning established during the previous implementation phases are properly executed.

IGI&S Programs Responsibilities - Transition Phase The IGI&S Programs begin to take a prominent role in the deployment of the SDSFIE 3.0 LDM during the Implementation phase. Component specific SDSFIE 3.0 issues need to be addressed by the IGI&S Programs that will structure deployment of the SDSFIE 3.0 in that Component. Document interim solutions for SDSFIE/business system data relationships (not otherwise covered through adaptations). Identify more permanent solutions, to ensure business continuity, through an SDSFIE change or a data proponent action. 10/19/2009

Ver. 1.0 30

Implementation Level Organizations Responsibilities - Transition Phase As with the IGI&S Programs, the Implementation Level Organizations have the prominent role in the SDSFIE 3.0 Transition phase. Following Component specific SDSFIE 3.0 guidance the Implementation Level Organizations will perform the various activities necessary to put the SDSFIE 3.0 standard into operational use such as collect lessons learned from the migration process, identify existing databases to link to SDSFIE 3.0 data, self audit SDSFIE 3.0 compliance, and communicate proposed standard changes through the SDSFIE Change Management process.

Data Proponents Responsibilities - Transition Phase Interim solutions adopted to ensure business continuity between SDSFIE and data proponent business system need to be reviewed to assess future actions. These data relationships (not otherwise covered through adaptations) should be documented in preparation for developing more permanent solutions. If these solutions require data proponent action, an action plan should be developed.

USACE Responsibilities - Transition Phase The USACE is responsible for the project management of the STARS Team including making sure funding is applied to all aspects of the SDSFIE activities and management oversight of STARS Team contract issues. USACE project management of SDSFIE activities continue into the SDSFIE Transition phase

10/19/2009 Ver. 1.0

31

Section 6: Next Steps The SDSFIE evolution to a Logical Data Model requires that sound governance and a change management process will be employed to incorporate and adjudicate any future proposed modifications. The standard will be reviewed annually to ensure currency and adequacy. New requirements will be drafted and adjudicated at the lowest authoritative level, presented for adjudication and recommendation to the DISDI Group (the SDSFIE Governance body), and decided upon by the I&E DGB. Each version change to the standard will be implemented according to the phases and activities outlined in this strategy, to include a transition phase, similar to Phase 4.

Develop enterprise-level change management plan for sustaining and evolving the standard While this strategy calls for Components to develop a change management plan at their level, a DoD enterprise level plan is also necessary to integrate the Component plans. Such a plan would include recommendations for how to identify and document authoritative feedback from users, which may indicate patterns of problems and candidates for improving the standard. It should also include instructions for maintaining proper documentation, and history for future sustainment efforts to include resourcing and standard process timelines. The major types of sustainment activities are:

1. Corrective – diagnosis and correction of errors after release. 2. Perfective – the addition of new capabilities and functionality. 3. Adaptive – modification to interface with a changing environment. 4. Preventive – modification to improve future maintainability or reliability

Refine governance and meta-governance The existing governance structures will be relied upon to oversee SDSFIE adaptation (profiles and extensions). These governance structures are people and policies that define what adaptations are allowable and who is allowed to create them. More detailed guidance on adaptation can be found in Appendix B. This is an initial framework. It should be reviewed for effectiveness throughout the first three phases of implementation, and if necessary, refined during phase 4 (transition). The governance framework should remain stable during sustained operation and maintenance of the standard. When new versions are developed the governance framework should again be reviewed and optimized as necessary. As described in Appendix B, SDSFIE governance happens at two levels: the DoD Enterprise level and the Component Enterprise level. It is important to recognize that governance itself requires governance, i.e. meta-governance. Meta-governance focuses explicitly on the practices and procedures that secure IGI&S input, as well as command and control within the multiple SDSFIE governance structures. SDSFIE meta-governance is accomplished at the DoD Enterprise level (DGB/DISDI Group).

10/19/2009 Ver. 1.0

32

Appendix A: Adaptation of SDSFIE 3.0 LDM The ability to adapt the SDSFIE 3.0 Logical Data Model (LDM) is the primary mechanism by which the user community can tailor the standard to meet implementation-level business requirements. The implementation flexibility afforded by adaptation, however, needs to be sufficiently constrained in order to ensure the integrity of the standard. This document describes rules and guidelines intended to provide a suitable measure of constraint. These rules and guidelines shall be incorporated into the DISDIG Strategy for SDSFIE 3.0, and included in the SDSFIE 3.0 Specification Document to be published with the standard’s release. Key Term Definitions SDSFIE 3.0 Gold: The sum collection of all elements (defined below) resulting from the SDSFIE modeling efforts across all Business Mission Areas and the Common-Cross Functional group. Adaptation: Adaptations are formalized alterations to the LDM resulting in a data schema which is tailored to the particular business requirements of an implementing organization. Feature Type: A class of spatial features, sometimes included in a single spatial table. Commonly called Feature Classes or Entity Types in prior releases of the SDSFIE. Referential Integrity Rules: Rules defined by designers and administered by the relational database to ensure users and applications don’t enter inconsistent data. For example, a foreign key is a referential integrity rule that keep records from being entered into one of two related tables without also having information in the other. Element: Any individual component of the SDSFIE LDM including Feature Types, Feature Geometries, Attributes, Enumeration or Domain Values, and Associations or Relationships. Profile: The result of selective removal of SDSFIE 3.0 elements subject to any higher authority mandatory restrictions directing the removal of optional elements from SDSFIE Gold to create an Adaptation. Extension: The addition of a new element to the SDSFIE 3.0 LDM provided that element does not conflict with the definitions of elements already defined by higher authority. Discipline: A predefined set of Feature Types or Elements of SDSFIE Gold intended to meet the business needs of a mission function. Renaming: The process of altering or replacing SDSFIE Gold Element names (e.g. feature type names or attribute names). 1. Adaptation Requirements: For the purposes of SDSFIE 3.0, an Adaptation is a specific profile (i.e. strict subset of SDSFIE 3.0 LDM Gold Standard Feature Types) and all the extensions (i.e. additional feature types, attributes, and constraints) that have been added to the LDM or profile to support the unique business requirements of an implementing organization. Adaptations shall conform to the following rules:

10/19/2009 Ver. 1.0

33

1 All Adaptations, including Disciplines, shall be derived from SDSFIE Gold.

2 All Adaptations must be created and registered with the SDSFIE Repository before they can be used for Schema Generation or Migration.

3 All Component Adaptations shall be direct descendents of SDSFIE Gold. All other Adaptations by a Component (including User Adaptations) shall be derived from the Component Adaptations.

4 The Component shall determine and promulgate the review and approval policy for all subordinate Adaptations. It is the Component’s responsibility to define the policy. It shall be the STARS Teams responsibility to ensure the adaptation tools conform to that policy.

5 Only one Adaptation shall be registered per implementing organization.

6 Only one Adaptation shall apply per SDSFIE compliant physical data model.

7 An Adaptation shall consist of no more than one profile, and as many rule-compliant extensions as required.

8 Adaptations must be created with the SDSFIE 3.0 LDM Adaptation Toolset.

9 An Adaptation must be reviewed, approved, and registered according to guidelines determined by the DISDI Group and IGI&S community governance bodies. These governance bodies shall adjudicate all adaptation rule interpretations, and shall consider rule changes as part of the SDSFIE change management process.

10 Approved and registered Adaptations shall be considered part of the SDSFIE 3.0, and subject to DISDI Group governance.

11 Each new Release of the SDSFIE shall cascade downward to require a review of all SDSFIE Adaptations from the Prior Release.

Adaptation Creation Rules: The following rules describe the modification of elements allowed during the creation of an Adaptation, subject to the governance policies of the DISDI Group and the individual Components, as appropriate.:

1 Feature Types may be profiled.

2 Feature Types may be added provided they do not conform to a definition already included in either SDSFIE Gold or the Component Adaptation. The names of newly added Feature Types shall not duplicate any SDSFIE Gold Feature Type Name

3 Feature Types must contain all SDSFIE Gold Attributes.

4 Attributes may be added to a Feature Type provided their definition does not conform to any existing Gold SDSFIE Attribute and their names may not duplicate any existing attribute name.

5 If a Gold Attribute is included in an Adaptation, all constraints that apply to that attribute in the Gold must apply to the Adaptation.

10/19/2009 Ver. 1.0

34

6 All relationships between Feature Types derived from Gold must be included in the Adaptation along with necessary Foreign Key attributes.

2. Renaming SDSFIE Element Names No SDSFIE 3.0 LDM Adaptation can change the definition or data type of an existing element. Changing SDSFIE Feature Type or Attribute names is highly discouraged because it has very significant interoperability implications, but it will be allowed in special situations with due consideration of these guidance constraints:

a. a specific implementation reason must exist to support the name change such as COTS naming constraints and compatibility with legacy systems where implementation level aliases (described below) are not possible.

b. written justification must be provided in the adaptation approval process defending the name change in lieu of correcting SDSFIE naming issues with implementation level aliases (described below).

Implementation Level Aliases: Compatibility of SDSFIE compliant datasets with existing systems or applications may require different Feature Type and attribute naming. In these cases, the preferred solution is to employ the various technology approaches for aliasing (e.g., views and queries). Aliases may be recorded in the implementing organization’s SDSFIE 3.0 LDM Adaptation in order to facilitate the development of SDSFIE database creation scripts and general ease of implementation. 3. Profiles Implementation level organizations may not need to implement all the Feature Types of the SDSFIE 3.0 LDM. Profiling is the process of selectively excluding optional Elements (most notably Feature Types) from the SDSFIE 3.0 LDM to create a standard SDSFIE 3.0 LDM Profile for an implementing organization (e.g. installation, MAJCOM, or regional center). The rules governing the creation of an SDSFIE 3.0 LDM Profile (below) must be strictly followed to ensure the integrity of the standard. 3.1 Profile Rules

a. A Feature Type can be excluded from the LDM for a specific implementation profile if the implementing organization does not manage or create any spatial data of that particular type. The implementing organization may not eliminate a Feature Type and collect and manage spatial data of that type in an alternate, nonstandard Feature Type.

b. All profiled Feature Types (i.e. all Feature Types included in the Profile) must include:

i. all core SDSFIE Feature Type attributes designated in the 3.0 LDM.

ii. all mandatory SDSFIE Feature Type attributes must remain mandatory (i.e. they must be collected and managed for the Feature Type

4. Extensions

10/19/2009 Ver. 1.0

35

The concept of extending the SDSFIE 3.0 LDM enables implementing organizations to make additions to the standard to better address the specific business requirements of that organization. Before creating an extension, the SDSFIE 3.0 LDM and all registered Adaptations must be thoroughly reviewed to ensure that the extension(s) being considered are not already addressed in some portion of the standard. The rules governing the creation of an SDSFIE 3.0 LDM Extension (below) must be strictly followed to ensure the integrity of the standard. 4.1 Extension Rules

a. Addition of New Feature Types: The creation of new feature types is allowed as part of an SDSFIE 3.0 LDM Adaptation if a valid business requirement exists to support the need and no SDSFIE 3.0 LDM Gold standard Feature Type addresses it. If a Feature Type is not available, the implementing organization may create it for temporary storage of data and propose it through the governance process for inclusion in the next release of the standard. Only new features that support specific business requirements are allowed so long as these Feature Types are not redundant of any SDSFIE 3.0 LDM Feature Type. b. Sub-typing SDSFIE Feature Types: Sub-types of SDSFIE 3.0 LDM Gold Standard Feature Types are allowed, but they must be created in strict conformance to these guidelines:

i. a formal, unique definition must be prepared for each sub-type that is created. This definition must be based on policy or business requirements and thoroughly vetted during the approval process.

ii. sub-type names will be created by appending an underscore and a single key word to the end of the SDSFIE Feature Type that is being sub-typed.

iii. the sub-type must retain all the attributes as its parent SDSFIE Feature Type.

iv. attributes may be added to the sub-type using the new attribute rule stated below for Feature Types.

c. Addition of New Attributes to a Feature Type: In general, non-spatial (business) feature attributes should be collected into business data tables that are separate but linked to the SDSFIE 3.0 LDM Feature Type. In exceptional cases however, new attributes shall be allowed to be added to SDSFIE 3.0 LDM Feature Types. New attributes may be added to a Feature Type for the following reasons:

iii. A foreign key relationship needs to be established with some existing business system or data set in the implementing organization.

iv. Non-spatial or “business” attributes may be added to an SDSFIE Gold Standard Feature Class in special situations with due consideration of these guidance constraints:

1. a business reason must exist to support the addition.

10/19/2009 Ver. 1.0

36

2. written justification must be provided in the adaptation approval process defending the addition attributes in lieu of collecting them in a separate business table or database.

3. the number of attributes being added must be kept to a minimum. The intent is to reduce burden on technicians who may otherwise be required to enter data they don’t readily know.

4. the business line responsible for the addition must also be directly responsible (i.e. the proponent) for the creation and maintenance of the Feature Type being extended.

d. Extensions to Referential Integrity Rules: At the discretion of the implementing organization, stricter obligations of existing referential integrity may be implemented as required.

e. Extensions to Domains: Implementing organizations are allowed to impose more restrictive domain values on SDSFIE 3.0 LDM elements

v. if the standard contains five values in the domain of an existing SDSFIE 3.0 LDM element, the extension may specify that its domain consists of three domain values. The extension shall require that the user select a value from the three domain values.

vi. the number of values in a code list may be expanded as needed by the implementing organization.

5. External Spatial Data Standards: As external spatial data standards (see discussion in Section 4: Phase 3 – Implementation) are discovered and procedures are developed by the Components, common processes or issues may need to be addressed in this Adaptation Guidance. As the Pilot Implementations are completed the DISDI Group will consider revising this guidance to capture lessons learned. 6. Adaptation Best Practices

a. Registered Adaptations shall be consulted before embarking on the development of a new Adaptation.

b. The profile shall be provided to anyone receiving spatial data that was created according to that profile.

c. Adaptations will be created with the SDSFIE 3.0 LDM Adaptation Tool. d. The validation tool needs to be run before an Adaptation is approved and

registered. 7. Registering Adaptations: A completed Adaptation must be reviewed and approved by Component IGI&S governance groups before it can be registered and used. Adaptations can only be registered by organizations or users designated by the DISDIG or Component IGI&S governance groups. After approval, the Adaptation will be recorded (“registered”) in the implementing organization’s Component IGI&S Program SDSFIE Adaptation Repository.

10/19/2009 Ver. 1.0

37

Appendix B: SDSFIE Governance In May, 2007, the Assistant Secretary of Defense for Networks & Information Integration and Department of Defense Chief Information Officer ASD(NII/CIO) issued an Information Sharing Strategy followed more recently by an implementation guidance document titled “Federated Governance of Information Sharing Within the Extended Enterprise.” The governance of SDSFIE shall conform to that guidance, tailored for the specific needs of the DISDIG and IGI&S community. In principle, our governance approaches shall be:

• Self-forming, self-organizing and self-regulating; • Required, to support the establishment and maintenance of consensus decisions; • Agile – supporting rapid change in business requirements; • Light-weight – reliably implemented with minimal burden.

Governance: The means for coordination, regulation, orchestration and decision making within federations that are self-forming and self-regulating.

“Federated Governance of Information Sharing Within the Extended Enterprise” ASD (NII/CIO)

Governance, as defined above, shall be implemented at two levels for SDSFIE:

• DoD enterprise level (DGB and DISDIG) This level is indicated by the blue (upper) rectangles in Figure B-1.

• Component enterprise level (Component HQ and IGI&S program) This level is indicated by the white (lower) rectangles in Figure B-1.

Figure B-1 depicts the community of groups or activities which currently exist to provide DoD enterprise level governance. SDSFIE governance at this level is focused on the DISDIG – in other words, the DISDIG coordinates all activities and inputs relative to governing the standard, adjudicates issues, and recommends decisions to the DGB. This is an initial framework. According to the SDSFIE strategy, this framework should be reviewed for effectiveness throughout the first three phases of implementation, and if necessary, refined during phase 4 (transition).

10/19/2009 Ver. 1.0

38

Figure B-1: SDSFIE Governance Framework at the DoD Enterprise Level

10/19/2009 Ver. 1.0

39

Table B-1 is a matrix showing the activities or items to be governed, what the drivers are affecting governance, and the expected outcome(s) of governing these items or activities. Table B-1: SDSFIE Governance Items at the DoD Enterprise Level Items to Govern Drivers Mechanisms Outcomes

LDM Domains (Phase 1)

BEA BT Initiatives

Domain Modeling Sessions CSPs STARS

LDM is built in accordance with authoritative business requirements

Adaptation Minimums (Phase 3)

Best Practices Policies NSG Requirements BT Initiatives

DISDIG -> STARS Strategy Document LDM Cardinality

Registration Minimums (Phase 3)

Best Practices Policies NSG Reqmnts BT Initiative

DISDIG -> STARS Strategy Document Business Rules

Tools (Phase 1-3)

TBP DISDIG -> STARS Only authorized users have access to SDSFIE suite of tools

Access (Phase 1-3)

TBP DISDIG -> STARS Only authorized users have access to SDSFIE registry and repository

Change Management & Version Control (Phase 4+)

TBP DISDIG -> STARS Governance groups

Vetted business requirements drive new versions of SDSFIE

Compliance (Schema) (Phase 3+)

TBP TBP TBP

Compliance (Data) (Phase 3+)

TBP TBP TBP

CSP (Configuration Support Panel) BT (Business Transformation TBP (To Be Published)

10/19/2009 Ver. 1.0

40

Appendix C: SDSFIE Communication Overview The success of SDSFIE 3.0 becoming the next Department of Defense (DoD) business enterprise geospatial standard depends greatly upon an effective communication strategy. The communication strategy should not only address the variety of geospatial users and leaders, but also non-geospatial leaders – success depends upon building knowledgeable, supportive champions in all these communities. The core of SDSFIE 3.0 is a Logical Data Model (LDM) and therefore represents a significant technical change from previous SDSFIE releases. More importantly, the LDM schema will require a set of implementation tools and methods which are very different (from the user perspective) than previous versions of SDSFIE. Given these major differences it is apparent that implementing SDSFIE 3.0 will require equally different approaches to communicating the new standard to users and leaders alike. While users will experience the greatest need to understand the “nuts and bolts” differences between old and new SDSFIE versions, leaders will need to understand just how important this standard has become to the IGI&S community. Leaders will also need to appreciate the significant role they will play in implementing SDSFIE 3.0 and its future versions. The intent of this communication plan is to frame the various audience levels and messages in a coherent, coordinated fashion.

2.0 Communication Objectives The successful deployment of the SDSFIE 3.0 LDM is more than the simple release of the data model. It is a complex set of processes that must effectively address a number of management focus areas. The main objective of this communication plan is to articulate a coherent, coordinated approach to informing the network of key players so that they understand their roles, interrelationships, and expectations throughout implementation of the standard. The other communication objectives for SDSFIE 3.0 are intended to support each of the goals established for the re-engineering effort. Two primary goals of the SDSFIE re-engineering effort were to (1) improve the standard’s ability to facilitate interoperability of spatial data across the enterprise by providing a common vocabulary and (2) align SDSFIE with functional Installations and Environment (I&E) business line requirements, including the DoD Business Enterprise Architecture (BEA). Spatial data standards from other sources, such as the Federal Geographic Data Committee (FGDC) and National Geospatial-Intelligence Agency’s (NGA) GEOINT Structure Implementation Profile (GSIP), must also be adequately coordinated with SDSFIE so that users are not presented with a hodgepodge of irreconcilable standards. The key communication messages for SDSFIE 3.0 are:

10/19/2009 Ver. 1.0

41

• SDSFIE is the common spatial data standard for all IGI&S capabilities;

implementation is required. • SDSFIE 3.0 implementation will require a process known as adaptation. • Adaptations will be managed according to Component-level business rules and

decision processes. • SDSFIE 3.0 will be harmonized with applicable GEOINT and DISA standards. • SDSFIE 3.0 is compliant with ISO, OGC, and FGDC guidelines and

requirements. • SDSFIE 3.0 is less complex than previous versions, but is completely adaptable to

all I&E business requirements. • Implementation and future changes to the standard will be primarily driven by

I&E business lines, business systems, and the BEA.

3.0 A Simple Communication Model Effective communication is the controlled flow of information from those who have the information to those who need it. The key elements in this simple communication model are a Communicator (i.e. someone who needs to transmit information), an Audience (i.e. those who need to receive the information), a Channel (i.e. a mode of communication that is available and capable of conveying the information), and a ‘communication initiating Event’ (i.e. something that triggers the need for a particular communication). The Communication Channels can either provide information from the Communicator to the Audience or the Communicator and the Audience can interact. Given the level of detail of some portions of the SDSFIE schema, a data sensitivity review is currently underway to develop releasability criteria. It is likely that releasability restrictions may be imposed on all communications channels to ensure information is made available to those who need it but is suitably protected from unauthorized users. Releasability Criteria will be based on the sensitivity of a particular piece of information (or a particular aggregation of multiple data sets) and employ a particular means to enforce the security required for that piece of information. Since SDSFIE communication requirements are very complex, the overall communications process is broken down into a series of smaller communication networks called Lines of Communication. These Lines of Communication are built on a series of management focus areas that collectively represent all the management activities required to develop, implement, and sustain the SDSFIE. The SDSFIE Lines of Communication, a description of their management functions, and their corresponding communication objectives are illustrated in Figure A-1 and described in detail in Table A-1. The finer details of executing the communication plan are contained in the attachment, consisting of discussions of each Line of Communication.

10/19/2009 Ver. 1.0

42

Figure A-1: SDSFIE lines of communication.

10/19/2009 Ver. 1.0

43

Table A-1: SDSFIE Lines of Communication Line of Communication Management Function Communication Objectives Strategic Guidance The top-down management that

articulates a vision, strategy, and long-range plan for the development, implementation, and long-term sustainment of the SDSFIE. Integrate SDSFIE with I&E business mission requirements, policy, and standards.

• Deploy an effective SDSFIE vision and goals.

• Deploy an SDSFIE development and implementation strategy.

• Communicate requirements, goals and milestones regarding migration to version 3.0.

• Inform senior leaders about GEOINT and FGDC policies, standards, and requirements.

Tactical Support The operational support required to re-engineer the standard and implement and sustain it according to geospatial industry best practices and DoD enterprise requirements. Optimize migration from previous SDSFIE to SDSFIE 3.0.

• Inform SDSFIE implementation community about SDSFIE resources (e.g., tools, documents, and the Standard).

• Train spatial data managers how to migrate and maintain SDSFIE 3.0 data sets.

Governance The means for coordination, regulation, orchestration and decision making within the self-forming and self-regulating SDSFIE federation. Publish guidance or policy for implementing the standard. Establish compliance criteria. Establish and support governance and meta-governance teams for SDSFIE.

• Establish a tiered approach to informing the SDSFIE user community to ensure efficient communication.

• Communicate implementation strategies and tasks which achieve the objectives determined under Strategic Guidance.

• Communicate SDSFIE governance and meta-governance guidance to all SDSFIE spatial data managers.

Coordination across Organizational Boundaries

Those activities required to ensure the diverse SDSFIE community is adequately informed about the SDSFIE and that all cross organizational requirements (e.g. DISR registrations) are properly addressed.

• Coordinate with those developing external standards.

• Coordinate SDSFIE with FDGC and NAS GSIP activities.

• Collect and coordinate spatial data requirements of I&E business line proponents and SMEs.

Socialization of the Standard

The process of informing the IGI&S COI about the SDSFIE 3.0 and the adaptation process/tools. This includes gaining buy-in from the IGI&S COI through briefings and formal comment processes.

• Inform leadership about the role & value of SDSFIE.

• Ensure all elements of the standard are correctly understood.

• Inform IGI&S Program leadership about the requirements to convert to SDSFIE 3.0.

• Provide opportunities for business line proponents, SMEs and IGI&S users to review and comment on the standard.

• Communicate the standard to the entire IGI&S COI including leaders from OSD, the Components, NGA, and federal partners.

Feedback Loop for the Standard

The process of collecting and responding to any relevant feedback from those SDSFIE users such as error reports or new requirement suggestions.

• Gather user-level feedback about technical aspects of SDSFIE 3.0 (e.g. bug reports, help desk issues, understandability, etc.)

• Collect and coordinate proposed changes and refinements to all elements of the standard (schema, tools, specification).

• Vet feedback through appropriate IGI&S governance groups for approval.

Compliance and Metrics

The business rules, actions, and reports necessary to ensure all IGI&S data sets are migrated to SDSFIE 3.0 in a timely manner, according to the implementation guidelines established by the DISDI Group and the respective IGI&S programs.

• Coordinate compliance & metrics reports at Component headquarters level.

• Gather status reports from ILOs at regular intervals from the start of migration to completion.

• Track metrics indicating the completion and effectiveness of adaptations.

10/19/2009 Ver. 1.0

44

4.0 IGI&S Community of Interest Stakeholders A Community of Interest (COI) is a group of people who have a common interest and need to share information. COI members work together across organizational lines to resolve the issues that affect the community. The DoD IGI&S COI is the focus of this communication plan, and it consists of a wide variety of organizations each with distinct organizational boundaries. The specific business needs of the IGI&S COI stakeholders combined with the overarching DoD business enterprise drivers make the IGI&S COI an existing, viable, organizational construct within which to accomplish the revision and maintenance of the SDSFIE. The stakeholder groups of the IGI&S COI are listed in Table A-2. The details of how these stakeholders will effectively communicate are presented in the discussions of Lines of Communications below. Table A-2: IGI&S Community of Interest stakeholders.

Stakeholder Description

DISDI PM, USACE COR, or I&E DGB Member

An individual with programmatic and/or budgetary authority over development and maintenance of the SDSFIE, for its implementation, and/or for programs or systems that utilize data contained in implementations.

I&E DGB The I&E Domain Governance Board (DGB) oversees the development and implementation of the DoD Business Enterprise Architecture (BEA) for all real property, installation management and environmental business areas under the purview of the Deputy Under Secretary of Defense (I&E). The Board serves as the primary interface between the Business Management Modernization Program (BMMP) governance structure and the DoD Component's I&E organizations in implementing the BEA architecture within the I&E community.

DISDI Group The DISDIG is responsible for ensuring that existing and planned I&E spatial information resources are organized and leveraged to deliver business capabilities that support DoD strategic warfighting missions, goals, and objectives; AT&L guidance and direction; and the DoD BEA. The working group consists of members from the Military Departments, the Washington Headquarters Services, the Army Corps of Engineers, and other members as appropriate. These members are senior managers with authority to represent their Components’ spatial information resource program.

STARS Team The STARS Team is the technical support contractor providing subject matter expertise, re-engineering, implementation tools, and training for SDSFIE. It consists of individuals from the STARS prime and sub contractors.

IGI&S Program Managers

IGI&S Program Managers are Component headquarters level managers responsible for the non-GEOINT geospatial information and services. Although these managers typically represent their Component on the DISDI Group, this stakeholder role focuses specifically on their Component level responsibilities.

ILO Spatial Data Managers

Spatial data managers at the individual implementation level organizations (ILO) are an important IGI&S COI stakeholder. They are typically responsible for geospatial information and services at an installation, regional headquarters, or major command.

10/19/2009 Ver. 1.0

45

Data Proponents and Subject Matter Experts

Data proponents and subject matter experts may be headquarters or ILO level individuals who: are directly responsible for defining, creating, and maintaining a particular mission data set (proponents); or have best-available knowledge/expertise about a particular mission data set.

Non-DoD Programs

In its long history, SDSFIE has been adopted by a number of non-DoD organizations as a standard for their spatial data requirements. This non-DoD community will continue to have an interest in the SDSFIE, and their interests will require a level of support to be determined by the DISDI Group.

GEOINT Functional Manager (NGA)

NGA is designated by EO 12333 as the Functional Manager for GEOINT and lead for all DoD geospatial information & services. While the SDSFIE is primarily targeted to the I&E community, NGA is a member of the IGI&S COI. NGA recognizes the unique I&E character of the SDSFIE, and the standard is intended to serve an integral role in the GSIP as the data dictionary for DoD infrastructure information. This stakeholder role interacts with the SDSFIE community through the GEOINT Standards Working Group (GWG).

5.0 Communication Plans at the Component IGI&S Program Level This document presents a department-level overview of SDSFIE communication requirements; additional communication requirements exist at or below the Component IGI&S Program level (operational level). Each Component IGI&S Program should develop communication plans from their operational perspective (see below). The contents of this document are meant to serve as an overarching strategy, schema, and a guide in the preparation of Component-specific plans. Important IGI&S Lines of Communication Three of the seven lines of communication are of particular importance to the IGI&S programs. Given that their primary focus is operational (i.e. migrating production SDSFIE 2.x spatial data sets and application infrastructures), the three lines of communication that deal most directly with these operational aspects are Tactical Support, Governance, and Compliance and Metrics. At a minimum, the IGI&S program’s communication plan should provide detailed approaches to these three lines of communication. The greatest level of detail will be required for the Tactical Support line of communication; this is where each IGI&S Program will establish the communications infrastructure between the various organizations internal to the Component involved in the SDSFIE 3.0 implementation. Lines of Communication Details The simple communication model (Section 3) introduced the five key communication elements (i.e. Communicator, Audience, Channel, communication initiating event, and releasability criteria). Given the strategic perspective of this document, it does not address lower level communication channels, initiating events or releasability criteria. These three elements must be addressed in sufficient detail at the operational level so that all participants in a given IGI&S Program’s implementation of SDSFIE 3.0 clearly 10/19/2009

Ver. 1.0 46

understand their communication requirements, and the accepted approaches of the ILO. Details provided in the attached descriptions of the various lines of communication provide additional information to assist the IGI&S Programs in the creation of their Component’s SDSFIE Communication Plan. A key stakeholder omitted from this document is the user. Users are ultimately the “customers” of the SDSFIE and include GIS Managers, Installation GIS data stewards, database administrators, data users, data creators, and content SME’s. They must be satisfied with the ability of the SDSFIE schema and tools to support mission needs as well as the standard’s ability to support optimal software and database performance (i.e. business systems). IGI&S Program level communication plans should include the elements needed to address SDSFIE users at the lowest level.

10/19/2009 Ver. 1.0

47

Attachments: Lines of Communication Descriptions

Strategic Guidance Strategic guidance is the top-down management that articulates a vision, strategy, and long-range plan for the development, implementation, and long-term sustainment of the SDSFIE. It must be effective to ensure SDSFIE properly integrates with I&E business mission requirements, policy, and standards. Specific communication objectives of the strategic guidance focus areas are to:

• Deploy an effective SDSFIE vision and goals. • Deploy an SDSFIE development and implementation strategy. • Communicate requirements, goals and milestones regarding migration to ver. 3.0 • Inform senior leaders about GEOINT and FGDC policies, standards, and

requirements. The line of communication supporting Strategic Guidance for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-2. This figure depicts the stakeholders principally involved, the types of information to be communicated, and the direction the information is going. Further details are provided in Table A-3, where the stakeholders shown in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

10/19/2009

Ver. 1.0 48

Figure A-2: Communication lines for strategic guidance of the standard.

10/19/2009 Ver. 1.0

49

Table A-3: Stakeholder strategic guidance primary communication activities.

Stakeholder Communications Activity

NGA NGA as the designated DoD functional manager for GEOINT needs to be informed about the Vision and Strategy driving the implementation of SDSFIE 3.0. The DISDI Group is responsible for providing these materials to NGA in the form of documents and briefings.

IGI&S Program Manager (PM)

Component IGI&S PMs must have a clear understanding of the DISDI Group’s consensus intent (Vision and Strategy) for SDSFIE 3.0, and the DISDI Group Implementation Plan is the key document for communicating these ideas to the Component IGI&S Programs.

STARS Team The DISDI Group Vision and Strategy are the driving forces behind the re-engineering of SDSFIE. As such, it is very important that the STARS Team have a clear understanding of the DISDI Group requirements and receive DISDI Group strategies documents such as the Implementation Plan.

DISDI Group

I&E DGB The I&E DGB needs to be informed of various aspects of the SDSFIE re-engineering effort such as the Vision and Strategy, Migration Requirements, and Milestones.

Data Proponents (DP) & SMEs

Data Proponents in the Components will be impacted by the implementation of SDSFIE 3.0. They need to understand SDSFIE Vision and Strategy and be aware of the SDSFIE Implementation Plan. Additionally, they need to have a channel available to provide Comments and Feedback to their Component IGI&S Program.

IGI&S Program Manager (PM)

DISDI Group Component perspectives on and requirements for the SDSFIE 3.0 development and implementation need to be effectively communicated to the DISDI Group. Component level Comments and Feedback to the DISDI Group support this communication requirement.

STARS Team DISDI Group The DISDI Group has a very interactive role in the re-engineering of SDSFIE and needs to receive Comments and Migration Status reports from the STARS Team.

10/19/2009 Ver. 1.0

50

Tactical Support Tactical support is the collective operational support required to re-engineer the standard, implement, and sustain SDSFIE 3.0 according to geospatial industry best practices and DoD enterprise requirements. One important SDSFIE 3.0 tactical support objective is to optimize migration from previous SDSFIE versions to SDSFIE 3.0. Specific communication objectives of the tactical support focus area are to:

o Inform SDSFIE implementation community about SDSFIE resources (e.g., tools, documents, and the Standard).

o Train spatial data managers how to migrate and maintain SDSFIE 3.0 data sets.

The line of communication supporting Tactical Support for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-3. This figure depicts the stakeholders principally involved, the types of information to be communicated, and the direction the information is going. Further details about the communication messages are provided in Table A-4. In this table, the stakeholders illustrated in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

Figure A-3: Communication lines for tactical support of the standard.

10/19/2009 Ver. 1.0

51

Table A-4: Stakeholder tactical support primary communication activities.

Stakeholder Communications Activity

STARS Team Component IGI&S Programs need to be able to communicate Bug Reports and Support Questions to the STARS Team.

DISDI Group Operations Reports need to be provided to the DISDI Group to keep them informed about the Component’s progress in implementing SDSFIE 3.0.

IGI&S Program Manager (PM)

Data Proponents & SMEs

Data Proponents need to understand Data Generation and Maintenance Guidance and specific Business Rules that relate to the deployment of SDSFIE 3.0, and they need to be able to ask Data Questions and provide Feedback on the SDSFIE 3.0 standard.

IGI&S Program Manager (PM)

SDSFIE 3.0 specific Training and end user support Documents need to be provided to the IGI&S Programs by the STARS Team.

STARS Team

Non-DoD Program Managers

Non-DoD Program Managers will need access to technical Documents developed by the STARS Team if support to them is continued with the release of SDSFIE 3.0.

10/19/2009 Ver. 1.0

52

Governance Governance is the means for coordination, regulation, orchestration and decision making within the self-forming and self-regulating SDSFIE federation. Governance is responsible for publishing guidance or policy for implementing SDSFIE 3.0. Governance teams for SDSFIE will establish compliance criteria to support SDSFIE 3.0 implementation. Specific communication objectives of the governance focus area are to:

• Establish a tiered approach to informing the SDSFIE user community to ensure efficient communication.

• Communicate implementation strategies and tasks which achieve the objectives determined under Strategic Guidance.

• Communicate SDSFIE governance and meta-governance guidance to all SDSFIE spatial data managers.

The line of communication supporting Governance for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-4. This figure depicts the stakeholders principally involved, the types of information to be communicated, and the direction the information is going. Further details about the communication messages are provided in Table A-5. In this table, the stakeholders illustrated in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

Figure A-4: Communication lines for governance of the standard. 10/19/2009

Ver. 1.0 53

Table A-5: Stakeholder governance primary communication activities.

Stakeholder Communications Activity

NGA It is of high importance that the SDSFIE 3.0 Governance Approach be effectively communicated to NGA.

IGI&S Program Manager (PM)

It is of high importance that the SDSFIE 3.0 Governance Approach be effectively communicated to IGI&S Program Manager (PM).

STARS Team It is of high importance that the SDSFIE 3.0 Governance Approach be effectively communicated to STARS Team.

DISDI Group

I&E DGB It is of high importance that the SDSFIE 3.0 Governance Approach be effectively communicated to I&E DGB.

Data Proponents (DP) & SMEs

Data Proponents need to Participate in and provide Feedback to the Component IGI&S Program development and implementation of SDSFIE.

Data Proponents have a low level need to understand the elements of the Governance Approach that applies to them.

IGI&S Program Manager (PM)

DISDI Group The IGI&S Program Manager needs to be able to Participate in and provide Feedback to the DISDI Group’s development and implementation of SDSFIE.

10/19/2009 Ver. 1.0

54

Coordination Coordination consists of those activities required to ensure the diverse SDSFIE community is adequately informed about the SDSFIE and that all cross organizational requirements (e.g. DISR registrations) are properly addressed. Specific communication objectives of the coordination focus area are to:

• Coordinate with those developing external standards. • Coordinate SDSFIE with FDGC and NAS GSIP (via NGA) activities. • Collect and coordinate spatial data requirements of I&E business line proponents

and SMEs. • Distribute DISDI Group decisions and directions (e.g. pilot study guidance) to the

IGI&S Programs and the STARS Team for execution. The line of communication supporting Coordination for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-5. This figure depicts the stakeholders principally involved, the types of information to be communicated, and the direction the information is going. Further details about the communication messages are provided in Table A-6. In this table, the stakeholders illustrated in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

Figure A-5: Communication lines for coordination of the standard. 10/19/2009

Ver. 1.0 55

Table A-6: Stakeholder coordination primary communication activities.

Stakeholder Communications Activity

NGA DISDI Group keep NGA informed on the SDSFIE progress by providing the Data Standard and related documents. NGA supplies DISDI Group with GISP Requirements and Reports.

FGDC DISDI Group keep FGDC informed on the SDSFIE progress by providing the Data Standard and related documents. FGDC supplies DISDI Group with Content Standards.

STARS Team The STARS Team needs to receive DISDI Group Decisions and Directions and provide the DISDI Group with Tools, Documents, and the Standard.

DISDI Group

IGI&S Program Manager (PM)

The IGI&S PM needs to receive DISDI Group Decisions and Directions and provide the DISDI Group with Pilot Project Adaptations Feedback and SME Input.

Data Proponents (DP) & SMEs

DP provides PM with SME Input to ensure correct information about data in the business mission area is properly represented. PM provides DP with the Standard Adaptation and all related Documents and Tools to fully support migration of data to SDSFIE 3.0.

DISDI Group At the conclusion of the Component Pilot Studies, PM will communicate Pilot Study findings to the DISDI Group. Using the these findings, PMs will develop a Component Implementation Plan, an Adaptation Strategy and the definition of the Implementation Level Organization which will be delivered to the DISDI Group.

IGI&S Program Manager (PM)

STARS Team The STARS Team needs to receive IGI&S Program Pilot Project Feedback and SME Input and provide the IGI&S Program with Pilot Project Adaptations and Documentation.

10/19/2009 Ver. 1.0

56

Socialization Socialization is the process of informing the IGI&S COI about the SDSFIE 3.0 and the adaptation process/tools. This includes gaining buy-in from the IGI&S COI through briefings and formal comment processes. Specific communication objectives of the socialization focus area are to: • Inform leadership about the role & value of SDSFIE. • Ensure all elements of the standard are correctly understood. • Inform IGI&S Program leadership about the requirements to convert to SDSFIE 3.0. • Provide opportunities for business line proponents, SMEs and IGI&S users to review

and comment on the standard. • Communicate the standard to the entire IGI&S COI including leaders from OSD, the

Components, NGA, and federal partners. The line of communication supporting Socialization for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-6. This figure depicts the stakeholders principally involved, the types of information to be communicated, and the direction the information is going. Further details about the communication messages are provided in Table A-7. In this table, the stakeholders illustrated in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

10/19/2009 Ver. 1.0

57Figure A-6: Communication lines for socialization of the standard.

Table A-7: Stakeholder socialization primary communication activities.

Stakeholder Communications Activity

NGA Documents and Standards need to be provided to NGA, and they need to have an opportunity to return Review and Comments on those materials into the SDSFIE development and implementation process.

IGI&S Program Manager (PM)

Decisions, Directions, and Education to support the SDSFIE development and implementation must be provided to the IGI&S Programs.

STARS Team The STARS Team needs to be able to provide all the Tools, Documents, Standard, and all other Deliverables to the DISDI Group. The DISDI Group will return Review Comments and Decisions and Directions.

I&E DGB Information and Recommendations about the SDSFIE 3.0 effort must be provided to the I&E DGB so that they may provide informed Decisions and Directions back into the SDSFIE development and implementation process.

DISDI Group

FGDC FGDC needs to be Informed about the progress of the SDSFIE 3.0 efforts and given an opportunity to provide Feedback to the effort.

Data Proponents & SMEs

The IGI&S Program needs to inform the Data Proponents & SMEs about the Tools, Documents, Standard, and Education. The Data Proponents will return Review Comments and Informal Feedback.

DISDI Group The DISDI Group needs IGI&S Program Informal Feedback and Review Comments to ensure its their requirements and concerns are adequately addressed in the SDSFIE 3.0 re-engineering effort.

IGI&S Program Manager (PM)

STARS Team The STARS Team needs deliver/inform the Tools, Documents, Standard, and Education to the IGI&S Program. The IGI&S Programs will return Review Comments and Feedback.

10/19/2009 Ver. 1.0

58

Feedback on the Standard Feedback on the standard is the process of collecting and responding to any input relevant to change management of the standard (e.g., error reports or new requirement suggestions) from SDSFIE users. Specific communication objectives of the feedback on the standard focus area are to:

• Gather feedback about SDSFIE 3.0 (e.g. new requirements, bug reports ) • Collect and coordinate proposed changes and refinements to all elements of the

standard (schema, tools, specification, etc.). • Direct vetted feedback through appropriate IGI&S governance groups for

approval. The line of communication supporting Feedback for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-7. This figure depicts the stakeholders principally involved, the types of information to be communicated, and arrows indicating the direction the information is going. Further details about the communication messages are provided in Table A-8. In this table, the stakeholders illustrated in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

10/19/2009 Ver. 1.0

59

Figure A-7: Feedback Communication Lines for Standard Management

10/19/2009 Ver. 1.0

60

Table A-8: Stakeholder feedback on the standard primary communication activities.

Stakeholder Communications Activity

DISDI Group The DISDI Group receives New Requirements and Recommendations from the STARS Team, and supplies the STARS Team with Decisions and Directions on how to proceed with the SDSFIE re-engineering effort.

IGI&S Program Manager (PM)

Documents, the Standard, Tools, Help Desk and Training are provided to the IGI&S Programs by the STARS Team. The IGI&S Programs supply Bug Reports and New Requirements to the STARS Team.

STARS Team

Non-DoD Program Manager

Documents, the Standard, Tools, Help Desk and Training are provided to the Non-DoD Program Managers by the STARS Team. The Non-DoD Program Managers supply Bug Reports and New Requirements to the STARS Team.

10/19/2009 Ver. 1.0

61

Compliance and Metrics The compliance and metrics focus area includes the business rules, actions, and reports necessary to ensure all IGI&S data sets are migrated to SDSFIE 3.0 in a timely manner, according to the implementation guidelines established by the DISDI Group and the respective IGI&S programs. Specific communication objectives of the compliance and metrics focus area are to:

• Coordinate all compliance and metrics reports at the Component headquarters level.

• Gather status reports from ILOs at regular intervals from the start of migration to completion.

• Migration status reports will be prepared at both the enterprise and IGI&S levels. • Track metrics indicating the completion and effectiveness of adaptations (metrics

are to be determined at both the DISDI Group and Component levels). The line of communication supporting Compliance and Metrics for the development and implementation of SDSFIE 3.0 is illustrated in Figure A-8. This figure depicts the stakeholders principally involved, the types of information to be communicated, and the direction the information is going. Further details about the communication messages are provided in Table A-9. In this table, the stakeholders illustrated in the figure are listed with an anticipated list of their corresponding activities and communication inputs and output required to support those activities.

10/19/2009 Ver. 1.0

62

Figure A-8: Communication lines supporting compliance and metrics.

10/19/2009 Ver. 1.0

63

Table A-9: Stakeholder compliance and metrics primary communication activities.

Stakeholder Communications Activity

NGA NGA needs to be informed about SDSFIE 3.0 Migration Status.

IGI&S Program Manager (PM)

IGI&S Program Managers need DISDI Group compliance Guidance to gauge their performance.

STARS Team The STARS Team receives Guidance and Direction from the DISDI Group and report Migration Status and Compliance Issues back to them.

I&E DGB The DISDI Group reports Migration Status to the I&E DGB and receives I&E DGB Guidance and Direction back from them.

DISDI Group

Data Proponents & SMEs

Data Proponents should provide Subject Matter Expert Input directly to the DISDI Group.

Data Proponents (DP)

Data Proponents need IGI&S Program Manager compliance Guidance to gauge their performance and prepare Coordinated Compliance Reports and Migration Status reports.

IGI&S Program Manager (PM)

DISDI Group IGI&S Program Managers prepare Coordinated Compliance Reports and Migration Status reports for the DISDI Group.

10/19/2009 Ver. 1.0

64

Appendix D: IGI&S Implementation Plans Each Component (IGI&S program) is expected to prepare a suite of implementation plans based on this strategy document. The requirement for component-level plans is called out in “Section 4: Phase 3 – Implementation” of this document, but described in more detail here.

D.1: IGI&S Program Plan for Governance As referenced in Appendix B, component-level governance plans are necessary to ensure the SDSFIE 3.0 implementation goals are met and to provide a reliable framework for operation and maintenance of the standard. Component enterprise level governance groups shall be the only authoritative input sources for feedback to the DoD enterprise level governance groups. In general, component enterprise level governance should conform to the principles and framework described in Appendix B. The following additional goals and activities should be included in component-level plans. Governance Goals:

• Provide venues that represent the entire spectrum of key users or proponents. • Make the governance groups the authoritative source for consensus

recommendations concerning SDSFIE. • Inform the broader IGI&S or business line communities of the governance

groups, including their authoritative nature and roles/responsibilities. • Empower the governance groups to build consensus in a manner that suits their

members, and to coordinate with other groups. Governance Activities:

• Establish venues (groups) which align logically with business lines or proponents. • Create a standing process for identifying and endorsing governance groups around

business lines or proponents. • Establish a process for creating a “fair broker” to reconcile and arbitrate

differences between governance groups (aka meta-governance). • Create templates (charters or business practices documents) to be used for

formalizing each governance group’s roles, responsibilities, and practices. • Governance groups should establish meeting schedules, membership rosters

(voting/non-voting), agendas and milestones for completing their activities.

10/19/2009 Ver. 1.0

65

D2: IGI&S Program Plan for Adaptation As referenced in Phase 3, Implementation, component-level plans for how to execute Adaptations are necessary to ensure the SDSFIE 3.0 implementation goals are met. Component IGI&S programs (DISDIG members) shall be the only authoritative sources for direction to the STARS Team on who will create, register, and test SDSFIE 3.0 Adaptations using the suite of implementation tools. In general, component level governance of Adaptations should conform to the principles and framework described in Appendices A & B. The following additional goals and activities should be included in component-level plans. Adaptation Goals:

• Ensure effective, registered Adaptations are developed as needed by the entire spectrum of business lines (key users) or proponents.

• Use governance groups as the authoritative source for consensus recommendations concerning SDSFIE Adaptations.

• Adaptations should ensure continuity of operations for existing IGI&S business processes.

Adaptation Activities:

• Establish venues (groups) which align logically with business lines or proponents.

• Inform the broader IGI&S or business line communities of the authorized adaptation process, including how they can provide input.

• Review existing SDSFIE data holdings and business processes they support to ensure continuity of operations through SDSFIE 3.0 Adaptations.

• Develop and document Adaptation requirements and purpose.

• Build, test and register the Adaptation using SDSFIE suite of tools.

10/19/2009 Ver. 1.0

66

D3: IGI&S Program Plan for Communication The key to successful SDSFIE 3.0 implementation in an IGI&S Program depends greatly upon an effective communication strategy because success depends upon building knowledgeable, supportive champions in all IGI&S data user, end user, and leadership communities. The IGI&S Program Communication Plan will frame the various audience levels and messages in a coherent, coordinated fashion. Detailed information to support the creation of the IGI&S Program Communication plans is presented in Appendix C.

D4: IGI&S Program Plan for Change Management When the SDSFIE 3.0 LDM 1.0 is officially released, it will be version controlled by the change management process described in this document. This change management process details administrative control, review and release schedules, critical change management roles and responsibilities, and the change request process for the Standard. The central governance body for this change management process is the DISDI Group. The change management guidelines described here are presented from the DoD enterprise level perspective. The Components will need to build on these guidelines to develop a specific change management plan at their level. The Component plan would clearly state how SDSFIE users will identify and document problems with the schema, definitions, attributes, tools, etc. as well as how this user feedback will be reported up the chain of command to the DISDIG. The major types of anticipated sustainment activities are:

1. Corrective – diagnosis and correction of errors after release. Corrective sustainment activities will result in an incremental update to the release (i.e., 3.0 --> 3.0.1).

2. Perfective – the addition of new capabilities and functionality. Perfective sustainment activities will typical result in a major SDSFIE release (i.e., 3.0 to 4.0)

3. Adaptive – modification to interface with a changing environment. update unless that change is a result of a change in a DoD Business requirement.

4. Preventive – modification to improve future maintainability or reliability. Administrative Control The SDSFIE 3.0 LDM will be delivered by the STARS Team to the administrative control of the DISDI PM on behalf of the DISDI Group. The DISDI Group will assume functional and technical control of the Standard on behalf of the I&E DGB, in accordance with DUSD(I&E) policy. By consensus of the DISDI Group, governance procedures shall be adopted to establish version control of the Standard and direct the administrative functions necessary to execute the change management approach described in this guidance.

10/19/2009 Ver. 1.0

67

Review and Release Schedules The SDSFIE 3.0release will be reviewed periodically (i.e. annually initially) to determine if a new release is required. This review will cover all new standard adaptations and all submitted change requests to evaluate this need for a new release. Additionally, a review may be performed at any time at the discretion of the DISDI Group to address specifically identified standard problems that require immediate attention. Solutions to these urgent problems that prompted these ad hoc reviews may result in a new release of the standard outside the established periodic review/release schedule. Roles & Responsibilities An important element of the SDSFIE 3.0 LDM Change Management process is a clear understanding of the various administrative roles in the process and what change management responsibilities exist for each role. Five key roles have been identified for the SDSFIE 3.0 LDM Change management process as follows:

DISDI Program Manager (PM): The DISDI PM and DISDI support staff operates through the DISDIG to ensure the SDSFIE 3.0 LDM is properly maintained and managed. The DISDI PM is responsible for the administrative support required to manage the SDSFIE 3.0 LDM. DISDI Group (DISDIG): The DISDIG consists of representatives from each of the Department Components and has review and oversight responsibilities to ensure the SDSFIE 3.0 LDM addresses all their collective needs. IGI&S Programs: The component headquarters level activities responsible for oversight, policy, and guidance pertaining to installation geospatial information and services. The IGI&S program leaders are members of the DISDI Group. SDSFIE Users: SDSFIE users are all those individuals who use, generate, or maintain Department spatial data resources. They are responsible for implementing the SDSFIE 3.0 LDM in the spatial data that they create for their specific organization. Additionally, they are responsible for identifying changes that need to be considered to improve the SDSFIE LDM into future releases. STARS Team: The Solutions and Technology for the Advancement of the SDSFIE (STARS) Team is the SDSFIE Support Services contractor team.

These Key SDSFIE 3.0 LDM Change Management roles and their corresponding responsibilities are detailed in Table 1. Table 1: DGMP Specification change request roles and responsibilities.

Role Change Request Responsibilities

10/19/2009 Ver. 1.0

68

10/19/2009 Ver. 1.0

69

Collect change requests Submit to DISDI Group review Make change

DISDI PM

Manage SDSFIE versions Review Change Request DISDI Group Accept or deny request

IGI&S Programs Screen change requests from its SDSFIE users to the DISDI Group Identify and Document changes SDSFIE Users Implement approved changes

STARS Team Make changes as directed by the DISDI Group SDSFIE 3.0 LDM Change Management Process Changes to the SDSFIE will likely be identified by data end users and individuals who are responsible for the generation and maintenance of spatial data assets. As possible changes are identified, they will be reported in a written form to the Component’s IGI&S Program for consideration and review. The exact nature of these Component IGI&S Program change request review procedures are left to the discretion of that specific program, but the end result of that review process with be that the change request is accepted and passed up to the DISDIG review or it will be rejected and the requestor will be notified of the result and rationale. At the DISDIG review level, change requests will either be accepted and passed into the SDSFIE Standard revision release schedule or denied and the requesting IGI&S Program will be notified of the result and rationale. This SDSFIE change management process is illustrated in Figure 1 below.

Figure 1: SDSFIE change management process.

Appendix E: Organization Activities by Phase

10/19/2009 Ver. 1.0

70

Table E-1: Phase 1 activities by organization.

Critical Path Organization Activity Activity Type Predecessor Descendant

Milestone

Complete SDSFIE 3.0 LDM SA None Everything beyond Phase 1 SDSFIE 3.0 LDM Create Implementation Tools SA None Implementation Level

Migrations Implementation Tools

STARS Team

Develop Training Courses SA None IGI&S Training Training Materials Review and Align DGMP with SDSFIE

SA None None

Develop SDSFIE Strategy SA None IGI&S Implementation Plans SDSFIE Strategy Document Review and Align DGMP with SDSFIE

SA None None None

DISDIG

Integration of SDSFIE with GSIP SA None IGI&S Governance Guidance Meta governance Document IGI&S Programs None None None None Implementation Level Organizations

None None None None

USACE STARS Team Project Management SA None None None

Table E-2: Phase 2 activities by organization.

Critical Path Organization Activity Activity Type Predecessor Descendant

Milestone

Deploy Implementation Tools SA Test Implementation Tools Create and Maintain SDSFIE Help Desk

DA None None STARS Team

Create and Maintain Registry and Repository

DA None Registry Profiles and Extensions

Acceptance of Standard SA Deliver Final SDSFIE 3.0 LDM

DBG Approval

DGB Approval SA Acceptance of Standard Publish Standard Publish standard SA DGB Approval Register SDSFIE with DoD MDR SA DGB Approval None Propose Standard for DISR SA DGB Approval None Advocate SDSFIE to ITSC and GWG

SA DGB Approval None

DISDIG

Integration of SDSFIE with GSIP SA Acceptance of Standard None IGI&S Programs None None None None Implementation Level Organizations

None None None None

USACE STARS Team Project Management SA None None None

10/19/2009 Ver. 1.0

71

10/19/2009 Ver. 1.0

72

Table E-3: Phase 3 activities by organization.

Critical Path Organization Activity Activity Type Predecessor Descendant

Milestone

Deploy Training Courses SA Develop Training Courses None None Operate and Maintain Model Registry and Repository

DA Create and Maintain Registry and Repository

Create and Register Profiles and Extensions

None STARS Team

Integration of SDSFIE and GSIP SA None None None IGI&S Programs Develop Component Level Strategy SA Develop DISDIG SDSFIE 3.0

Strategy All Other IGI&S Program Implementation Activities

Component Level Strategy document

Create and Register Profiles and Extensions

DA Develop Component Level Strategy

Migrate Existing Data

Pilot Study Data Migration DA Develop Component Level Strategy

Migrate Existing Data Pilot Study Lessons Learned

Monitor Migration Compliance DA Develop Component Level Strategy

None

Implementation Level Organizations

Migrate Existing Data DA Develop Component Level Strategy Create and Register Profiles and Extensions Pilot Study Data Migration

None Migrated data set

USACE STARS Team Project Management SA None None None

Table E-4: Phase 4 activities by organization.

Critical Path Organization Activity Activity Type Predecessor Descendant

Milestone

STARS Team None NA Migrate Existing Data None None Monitor Standard Compliance SA Migrate Existing Data None None DISDIG Integration of SDSFIE with GSIP SA Migrate Existing Data None None

IGI&S Programs Monitor Standard Compliance SA Migrate Existing Data None None Implement Change Management

Plan SA Migrate Existing Data None None

Implement Communication Plan SA Migrate Existing Data None None Implement Component Level

Governance Plan SA Migrate Existing Data None None

Implementation Level Organizations

Document Interim SDSFIE Solutions for SDSFIE/Business System Continuity of Operations.

DA None None None

USACE None NA None None None