DRAFT Activity Plan

Federal Enterprise Architecture

Geospatial Profile Pilot

Version 0.4

February 21, 2006

DRAFTGeospatial Profile IE Activity PlanVersion 0.1

Title:

FEA Geospatial Profile Evaluation Pilot

Status:

Proposed

Initiator Organizations:

Organization #1
Business POC / Technical POC
Name: / Name:
Title: / Title:
Street Address: / Street Address:
Email Address: / Email Address:
Phone: / Phone:
Fax: / Fax:
Organization #2
Business POC / Technical POC
Name: / Name:
Title: / Title:
Street Address: / Street Address:
Email Address: / Email Address:
Phone: / Phone:
Fax: / Fax:
Organization #3
Business POC / Technical POC
Name: / Name:
Title: / Title:
Street Address: / Street Address:
Email Address: / Email Address:
Phone: / Phone:
Fax: / Fax:

Description:

This document describes a two-phase activity to test the Geospatial Profile of the FEA by documenting and implementing solutions architectures based on enterprise architecture practices specified by the Profile. The first phase of the pilot will validate the methodologies proposed in the Profile document in the context of agencies’ business planning; the second phase will adapt and deploy a solutions architecture in the context of business processes common to multiple organizations. Both phases will provide feedback to the Profile, Version 2.0 of which will be published for review in late 2006.

This FEA Geospatial Profile Evaluation Pilot will identify elements of the Performance, Business, Data, Services, and Technology Reference models as described by the Geospatial Profile from the Federal Enterprise Architecture (FEA). The business requirements driving the Test Application will be those of multiple agencies in the mission-critical access to common-use geospatial data. These data will include basic “Framework” data layers defined by a draft American National Standard and data and functions deemed useful to business processes shared between agencies.

This Pilot will involve one or more of the following specifications:

  • OpenGIS® Web Map Service (WMS) Implementation Specification, Version 1.3
  • OpenGIS® Web Feature Service (WFS) Implementation Specification, Version 1.1 (as modified to include GML Simple Features)
  • OpenGIS® Geography Markup Language (GML) Encoding Specification, Version 3.1.1
  • OpenGIS® Web Map Context Implementation Specification, Version 1.1
  • OpenGIS® Catalogue Service Implementation Specification, Version 2.0
  • ISO 19115:2003(E)—Geographic Information—Metadata (or FGDC Content Standard for Digital Geospatial Metadata, 1998)
  • ISO19115/ISO19119 Application Profile for CSW 2.0 (or FGDC Application Profile of CSW)
  • GML simple features profile, 05-033r16
  • ISO 19135—Geographic information—Procedures for item registration
  • ISO 19139—Geographic Information—Metadata—XML schema implementation

Technical Approach:

The FEA Geospatial Profile pilot will involve multiple organizations that have related business processes in support of a shared business activity in the context of emergency management and response. Multiple activities based on affiliation, jurisdictional arrangements, and geography may take place within the broader pilot activity. The following technical approach is proposed for the pilot:

  • Identify candidate mission application area(s). The mission application area must be the result of a valid multi-agency business requirement and this business requirement must map to the FEA BRM. This pilot will treat each mission application as an IT initiative. The proposed broad business area involves emergency response and operations to be addressed by federal, state, and local participants.
  • For each identified mission application in an organization collaborating in the Pilot:
  • Determine and document mission application performance requirements to include Measurement Indicators that follows the FEA Geospatial Profile’s Geospatial Performance Architecture Guidance and appendices and provides suggested clarification to the Profile.
  • Elaborate and document mission application business requirement to include Geospatial Business Statements that follow the FEA Geospatial Profile’s Geospatial Business Architecture Guidance and appendices and provides suggested clarification to the Profile.
  • Adapt and document a data architecture that utilizes guidance from the FEA Geospatial Profile’s Data chapter and appendices and provides suggested clarification to the Profile.
  • Adapt and document a service component architecture that utilizes and updates guidance from the FEA Geospatial Profile’s Services chapter and appendices and provides suggested clarification to the Profile.
  • Adapt and document a technology architecture that utilizes and updates guidance from the FEA Geospatial Profile’s Technology chapter and appendices and provides suggested clarification to the Profile. This architecture should include all appropriate standards and specifications.
  • For each organization participating in the implementation validation (Phase II) of the Pilot:
  • Design and document a solutions architecture that integrates the data, services, and technology architecture into a solutions architecture that can be implemented. The solutions architecture must include complete discussion of the usage of all specifications and standards.
  • Deploy the solutions architecture, measure the result against the performance measurement indicators and business requirements and document the results. Report any interoperability or implementation issues discovered with respect to the application of specifications and elements of the FEA.
  • Transfer the resulting documentation to a permanent site and provide links to maintained operational capabilities and artifacts so they can be accessed as a realization of the FEA Geospatial Profile.

Deliverables/Outcomes:

  • For each mission application area, the pilot will deliver a complete architecture document containing performance, business, data, services, technology, and solution architectures.
  • The pilot will document recommended updates to the FEA Geospatial Profile, FEA Reference Models, and related standards and specifications.
  • The pilot will document best practices in constructing and addressing shared geospatially-enabled business processes addressing emergency management and response.
  • For each mission application area developed in Phase II, the pilot participants will deliver a mission application demonstration capability.

Schedule:

Activity / Target Date
Mission application candidates selected / March 15, 2006
IE Activity Plan finalized and submitted / March 22, 2006
IE Activity Plan approved and IE participation announcement made / April 10, 2006
Planned kickoff date / May 15, 2006
Performance and business architectures completed / June 15, 2006
Data, services, technology, and solution architectures completed / July 15, 2006
Implementation begins / July 15, 2006
Implementation completed / September 15, 2006
Documentation finalized / October 15, 2006
Planned execution end date / November 1, 2006

Resource Plan:

Staffing:

Initiative Manager: Brenda Smith, EPA and Ivan Deloatch, FGDC

Initiative Technical Lead: Doug Nebert, FGDC

Hardware

As required and documented in the solution architecture.

Software

As required and documented in the solution architecture.

Facilities:

As required and documented in the solution architecture.

Requirements for Participation:

To participate in this initiative, members must be willing to supply one of the following elements:

  • Mission application requirement and support to the development of the architecture documentation.
  • Support to the development of the architecture documentation.
  • Support to the development of FEA Geospatial Profile updates or OGC specification feedback.
  • Support to the implementation of the solution architecture for one or more of the mission application areas.
  • Data and services support: Provide documented data and services into the GOS portal (geodata.gov) and make it accessible via a WMS and a WFS
  • Services support: Provide other services as stipulated in solution architecture.
  • Application development support: Provide support to the development of the application.
  • Hosting of the resulting capabilities and documentation.

Draft Date: November 1, 2005Page 1 of 5