SECTION A: REQUIREMENTS
1 Project Title:
IDEAS Coalition Data Exchange Mechanism
2 Brief Project Scope and Functional Requirement:
Project Scope
The scope of this CIOG/ISD/IAM project extends to the activities associated with integrating and maintaining new architecture data exchange technology, developed in collaboration with Australia’s Coalition Partners (AUS, CAN, UK, US), into the Defence Information Environment (DIE), in support of new coalition business practices being introduced to improve force planning for coalition operations.
The project work is challenging with a significant portion of the work needing to be completed remotely by the participating nations, with limited interaction, across 18 time zones.
The aim of the new business practices is to allow seamless sharing of architectures between the partner nations that employ differing frameworks, meta-models and tool suites.
The scope of work does not include costs associated with the collaboration efforts associated with the management and technical development required to conceptualize and formalize the IDEAS ontology, much of which has already been accomplished. However this proposal does include those activities associated with implementation, testing and ongoing maintenance, required to maintain currency of national coalition architecture meta-model mappings against the IDEAS ontology.
Functional Requirement
The semantic issues associated with integrating force planning data from participating nations during formation of a coalition task force, have until recently been overlooked, mainly due to their difficult nature, or for reasons of presentation and simplicity. Coalition planners have been forced to make certain assumptions that participating nations use the same domain taxonomy and vocabulary for describing Defence capabilities and processes when planning operations, as until recently, a means to deal with the semantic issues of coalition data integration has not been available.
Obviously this is a weak assumption, when planners are trying to identify and source C2 shortfalls prior to coalition JTF designation and formation, in such an open information environment. In practice, it is has been demonstrated that participating nations use a local taxonomy and vocabulary, different from those used by other participating nations.
It has been realised that such diversity in description of national capabilities and processes should be eliminated in order to successfully enable formation of rapidly deployable and interoperable Joint C2 capabilities.
IDEAS is an emerging coalition capability being developed to overcome the semantic issues associated with integration of architecture data when used in force planning for coalition operations. IDEAS addresses the issue of semantic integration through a series of mediation layers defined in the IDEAS ontology that act as intelligent agents and enable the appropriate translation of national architecture terms into a common relatable format.
3 Operational Concept:
The IDEAS mission, in support of new coalition business practices being trialed by USJFCOM, is to supplement existing HQJOC coalition pre-mission planning capabilities through provision of an architecture data exchange mechanism, which expresses through a common ontology, national processes and capabilities of participating nations contributing to a coalition operation.
HQJOC will use the IDEAS capability to reduce the ambiguity of a nation's architecture terminology when employed for describing processes and nominated capabilities contributing to a coalition operation.
The operational concept for IDEAS is further described in the IDEAS OCD, provided as supplementary information.
4 Contribution to Fundamental Inputs to Capability (FICs):
IDEAS will contribute to FICs in the following ways:
Personnel and Organisation. Introduction of the IDEAS capability will not impact organisational or personnel requirement in HQJOC or CIOG.
Collective Training. The approach to operationalise IDEAS is being implemented via the US Joint Experimentation, Test and Evaluation and Advance Concept Technology Demonstration (JETA) Program. USJFCOM J7 will take the lead for integrating this emerging joint capability into national programs via a series of joint training events for testing and validation. USJFCOM J7 in consultation with participating national points of contact, will examine if the IDEAS capability offers a potential solution to coalition planning deficiencies and / or improves joint operational readiness, and will also assist with presenting validated solutions to higher levels of national authority. 'The USJFCOM JETA Integration into Joint Training Manual' is attached FYI. This document defines the USJFCOM process being adopted to operationalise the IDEAS capability.
Major Systems. IDEAS has been designed for integration into the as-is and to-be HQJOC joint planning environment and as such will compliment existing and planned defence computing infrastructure.
Support. CIOG will provide maintenance and support of the IDEAS capability to HQJOC to ensure that the currency of coalition architecture meta-model mappings against the ontology is maintained.
Facilities. Computing systems (hardware and software) will be procured under this project to deliver the IDEAS repository and reporting system that will interface with HQJOC joint planning system.
Command and Management. IDEAS will contribute to efficiency gains achieved through reduced planing times when trying to jumpstart formation and operation of a Joint Task Force (JTF), thus enabling the JTF CMDR to focus more time on the JTF mission versus assembling JTF C2 capability.
5 Hurt Statement:
Justification and expected benefits. IAM Branch has been involved with the IDEAS coalition working group since development efforts commenced in November 2005. The joint effort that has gone into this capability, and the results of progressive experimentation and testing, have received international recognition such that the IDEAS capability is currently identified in both the UK’s Ministry of Defence Architecture Framework and the NATO Architecture Framework roadmap documents as being core to future development directions. The USDoD have also demonstrated their support for IDEAS in proposing that US JFCOM J7, take the lead for trialing and integrating this emerging joint capability into national programs via a series of joint training events for testing and validation tentatively planned for the April 2009 timeframe.
As such, there appears strong evidence that the IDEAS capability and the new business practices to be trialed as part of the JFCOM training exercise, will introduce new concepts in the application of Enterprise Architecture (EA) data to military operations and further reduce the ad-hoc nature of JTF formation.
Clearly, Australia is not as advanced in EA as the larger military nations, WRT the quantity and quality of military EA that resides in repositories across Defence, (e.g. Australia may need to generate military EA for the JFCOM exercise). However, our ability to utilize this capability lay not only in generating Australian military architecture data in IDEAS format for consumption when operating as a member of a coalition, but also with ingesting other nation’s architecture data at times when Australia leads a coalition task force.
The identified benefits to all allied nations intending to use the IDEAS Model and Exchange Mechanism are as follows:
Better ability to plan coalition activity: The IDEAS capability will allow more detailed and rapid exchange of planning data at the architectural level, with greater certainty and consistency of meaning from nation to nation.
Consistent format for informing allies of capabilities and processes: The IDEAS model will allow a consistent methodology for transmission of information on capability and process, at the architectural level, ensuring that common understanding is maintained through the coalition planning process.
Operation over secure coalition networks: the IDEAS capability will, in its final form, be progressed through all required accreditation and certification processes to allow its use over secure coalition networks.
Enable Coalition Task Force Commanders to quickly analyse the force structure of contributing capabilities: The IDEAS model and exchange mechanism will be enabling technologies to support enhanced command decision making in coalition situations, by allowing rapid delivery of force structure and capability data from all participating nations to a common point in a common format with uniform understanding.
6 Policy Basis:
Introduction of the IDEAS data exchange mechanism and the business benefits it will deliver are consistent with CIO’s strategy that improved management of information is critical to the successful conduct of military operations and the effective management of Defence.
7 Priority and Justification - Ranges from 1 (Mandatory and Critical) to 5 (New Initiative and Routine):
Priority 3. Support to military operations / Routine
8 Risks associated with the Project and Proposed Mitigation Strategies:
Risk No. / Risk Type & Description(Technical, Schedule, Cost) / Risk assessment (L, M, H) / Mitigation Strategy / Risk Assessment after Mitigation strategy
(L, M, H)
1 / Schedule risk associated with completing the technical development activities to meet USJFCOM training exercises in April 2009. / H / DAS to attend all IDEAS WG meetings and teleconferences. / M
2 / Cost. Availability of national funding to support national implementation strategy. / H / DIEP / M
3 / Technical Support. Engineering new data exchange technology increases Defence reliance upon a small number of people with very specialist skills. / M / Establish contact with other CMTH areas (CSIRO) working through similar issues to broaden national support base. / L
9 Related Activities:
· JP2030: ADF Joint Command Support Environment. No impact to project.
· Introduction of the Defence Architecture Repository System
· Introduction of System Architect to the DRN
· DAF Review
10 Legacy System being Replaced:
NIL. IDEAS is a new capability that will augment existing computing infrastructure.
11 Project In-service Date and Useful Life:
Projected in-service date is 4th QTR 2009. This time frame is required to enable completion of ontology development activities and trial and refinement of supporting coalition business practices.
SECTION B: RESOURCES
12 Scope of Work requested of CIOG and Dependencies:
It is proposed that implementation of the IDEAS Project Management activities by undertaken by staff located within CIOG / ISD / IAM’s Directorate of Architecture Support. DAS staff retains specialist knowledge required to support implementation of this capability onto the DIE, and to maintain the domain following implementation.
CIOG / ISD staff will be consulted for Security Accreditation, Network Change Instruction (NCI) registration, Performance Management Assessment and to endorse the Request to Implement (RTI) servers and software into the DIE.
13 Project Components being undertaken outside of CIOG:
Will DSG Regional Staff be required for the delivery of the project? Yes No X
DAS will retain responsibility for managing and delivering all aspects of the project. DSG regional staff will not be required for delivery of this project.
14 Estimated CIOG people effort (FTE/APS/PSP) for project delivery:
DAS will retain responsibility for managing and delivering all aspects of the project.
1 x APS Project Manager: Part Time
1 x APS Technical specialist: Part Time
15 Delivery Organisation(s): CIOG Customer DMO
16 Acquisition Funding Source(s): CIOG Customer DCP Green Book DIEIF
17 Estimated Project Acquisition Budget: (CIOG Costs Only)
/ Project Budget$m / Contingency / Total / FTE
PSP/APS / Level of
Confidence /
Funds Recipient (Group/Division/Branch/ Directorate)
Capital / Operating / $m / $m / Numbers Required / H, M, L, VL / Capital / OperatingFY 0708 / 0.090
FY 0809 / 0.200 / 0.030
FY 0910 / 0.090 / 0.040
FY 1011 / 0.060
Later
Total / 0.380 / 0.100 / 0.030 / 0.510 / M
NOTE: Details of how these estimates were derived must be provided at Annex A.
18 Net Personnel and Operating Costs Funding Source (eg through life support):
Will there be a requirement for NPOC? Yes NoWill there be ongoing requirement for FTE/APS/PSP? Yes No
Has Sponsor agreed to secure and arrange transfer of ongoing NPOC dollars and FTE requirements?
Yes No
If NO, state how NPOC dollars and FTE/APS/PSP personnel requirement will be funded.
Proposal is for NPOC dollars to be funded out of Project budget.
One Star authoriser of NPOC commitment (Name & Position) / Mr Denis Healy (A/ASIAM)
19 Estimated NPOC (Do not include Contingency)
Operating
/ Ongoing NPOC(Sustainment) requirements
$m / FTE / APS / PSP Numbers Required / Level of Confidence
(H, M, L, VL) / Source of NPOC (Group/Division/ Branch/ Directorate) / Recipient of NPOC (Group/Division/ Branch/ Directorate)
FY 0607
FY 0708
FY 0809
FY 0910 / 0.040
FY 1011 / 0.060
Mature
Total / 0.100
NOTE: Details of these estimates must be provided at Annex A.
SECTION C: SCHEDULE
20 Timeframe for Project Deliverables:
IDEAS Experimentation successfully concluded in UK September 2007
Coalition Demonstration of new data exchange technology to be presented in USA April 2008
USJFCOM Joint Training Exercise planned: April 2009
Formal introduction into service: July 2009
Annual maintenance update cycle follow IDEAS introduction into service.
SECTION D: CONSULTATION
21 Enterprise Business Owner (EBO)/Enterprise Process Owner (EPO):
Name & Position / Division/Branch/Directorate/Unit / Phone No. / Fax No. / Email Address22 DSG NOD Regional ICT:
Name & Position / Division/Branch/Directorate/Unit / Phone No. / Fax No. / Email Address23 CIOG Contacts:
Name & Position / Division/Branch/Directorate/Unit / Phone No. / Fax No. / Email Address24 Sponsor’s Group Finance Officer:
Name & Position / Group/Division/Branch/Directorate/Unit / Phone No. / Fax No. / Email Address25 Authorisation and Sponsorship
Originator (Name, Rank & Position requesting officer)Doug Wilson (MADS) / One Star Sponsor (Name, Rank, Position of sponsor)
A/ASIAM
Group/Division/Branch/Directorate or Unit
(please use abbreviations as appropriate)
ISD/IAS/DAS / Group/Division/Branch or Unit
(please use abbreviations as appropriate)
CIOG/ISD/IAM
Telephone Number
62187582 / Facsimile Number
6128 7630 / Telephone Number / Facsimile Number
6128 7630
Email Address
/ Email Address
Signature Date / Signature Date
Project Mandate Form - Version 4
ANNEX A
DETAILED PROJECT AND NPOC ESTIMATES
Details of how the estimated project acquisition budget (paragraph 17) was derived will enable full Committee consideration and a decision on whether to expend Commonwealth funds on this project. If necessary, tailor these tables and/or include a narrative so as to provide details on how the budget costs have been derived.
Table 1: Acquisition Costs
PROJECT ACQUISITION COSTS $M (CONTINGENCY IS TO BE SHOWN IN “Contingency” COLUMN)$m / FY0607 / FY0708 / FY0809 / FY0910 / FY1011 / Contingency / Total
Hardware / 0.030 / 0.030
Software / 0.030 / 0.100 / 0.130
User Devices / 0.010 / 0.010
Common Services
Networks/datalinks
Bearers
Project Management / 0.060 / 0.090 / 0.090 / 0.240
Administration
FTE-APS or PSP Numbers
TOTAL / 0.090 / 0.200 / 0.090 / 0.030 / 0.410
Note: Contingency should be decided on the basis of risk. If cots hardware is being procured and is able to be reliably costed, you might allocate 5%. At the other end of the spectrum, integration or development work that is assessed as high risk might be allocated up to 50%. Please explain any comparatively large amounts of contingency as a note.