Coordination Assessment and Analysis Architecture Development

The Kick-off marks the beginning of the Execution phase of the initiative. Using the agreed upon work package as the governing documents for the conduct of the initiative, the stakeholders will begin the principal tasks of developing or enhancing engineering specifications, developing prototypical software components that exercise the newly developed specifications, and testing those components and specifications. The key outcome of the initiative is an Interoperability Program Report see section 13.6 for a detailed explanation of Interoperability Program Reports or IPRs. In the stages where the IPR is being developed and reviewed it will be typically referenced as a Draft Interoperability Program Report DIPR. The participants in conjunction with one another, the Sponsors, and IP Team will begin developing relevant DIPRs pertaining to requirements identified by the Sponsors. One stakeholder representative will act as the lead author for the document, but a group of participants are expected and obligated to support the actual creation and development of the DIPR; this group is referred to as a Work Group. The author may be a participant technical representative, a Sponsor representative typically technical, or on some rare occasions an IP Team member. The DIPR is iterated until the Work Group believes it to be sound enough for prototypical interoperable software components to be developed or enhanced to test the specification. This act of testing specifications and the prototypical software components exercising them is called a Technology Integration Experiment TIE. It is anticipated that a TIE will go through some number of iterations before Prototypical Software Components share information interoperably. A TIE is generally understood to minimally include a participant providing a client component and another participant providing a server component working in conjunction to test the implementation of a particular specification. 4 Execution Phase Tasks This section describes a flexible framework of standard, repeatable tasks for the execution phase of a testbed. These tasks may be performed by any of the Testbed Team members. The task are adapted as necessary to address the requirements of the specific Testbed. These tasks are executed with a Virtual Team Infrastructure. These tasks are used to define the SOW for in a Participant Agreement. Figure 5 – Testbed Execution Phase Tasks

4.1 Coordination

This task enables overall Testbed coordination between OGC Staff, OGC IP Team, Sponsors, Participants, and other TCPC Members as required. Initiative Coordination includes the following Subtasks: 5  Collaborative Environment - OGC IP Team provides synchronous and asynchronous collaboration environments for cross organizational, globally distributed, virtual teams working interdependently to execute Initiative Orders . Activities under this subtask include reading email and engaging in collaborative discussions such as regular teleconferences.  Initiative Plan Development – Support development of Project Plans, Project Schedules and Work Breakdown Structures Work Package. May include Technical and Project Management Approach, TasksSchedules, Communications Plans, Resource Plans, Risk and Mitigation Strategies, and definition of the Specification andor Component Development and Integration Tasks necessary to realize the Technical, Operational and Systems Architectures.  Management - Services ensuring Initiative Order participants are staying within designated budgets, that the work is progressing according to the agreed schedule, and that the tasks identified in the Statement of Work, including status reporting, are executed..  Communication – Includes communicating ongoing and planned Initiative and Work Item Status to OGC and other organizations such as ISO. This task does not include IP Business Development functions.

4.2 Assessment and Analysis

This task analyzes and documents an organization’s or domains existing capabilities and assesses requirements for OGC compliant technology. This task can occur as part of any testbed planning process. .

4.3 Architecture Development

This task defines the architectural views for any given Initiative. In the context of the Open GIS Interoperability Program, there are potentially three–and perhaps more - architectural views for any given effort. These views are the Operational Architecture, Technical Architecture, and System Architecture. Part of the Architecture Development task may be the use of an RFQCFP to industry to enable organizations interested in participating in an Interoperability Initiative to respond with a proposal. This task may also be implemented during Planning Studies.

4.4 Initiative Preparation