About this job

Sapienza Consulting is recruiting a FMN Architecture Support to work at NATO NCIA in Norfolk, USA.

Responsibilities

1. Introduction

ACT contributes to preserving peace, security and territorial integrity of Alliance member states by leading, at Strategic Command level, Warfare Development required to enhance NATO’s posture, military structures, forces, capabilities and doctrines. Capability Development Directorate (CAPDEV) comprises two Divisions – Requirements and Capabilities. Directorate supports SACT in his Capabilities Requirement Authority (CRA) role. It is responsible for holistic through lifecycle Capability Development approach that infuses innovation and transformative efforts that are integral part of Warfare Development. This includes responsibilities for elicitation, development, capture and collection, quality review, traceability and visibility of capability requirements. Requirements Division executes requirements management for NATO capabilities. It develops capability requirements, provides traceability and quality assurance of capability requirements, performs gap analysis and supports interoperability and implementation options across DOTMLPFI spectrum. Federated Interoperability (FI) Branch supports and enables the delivery of coherent and interoperable capabilities by developing and verifying associated capability specifications in order to ensure Day Zero interoperability of people, processes, and technologies.

Federated Interoperability Branch performs four functions, but in context of this SOW the deliverables are derived from RRIS presented in Reference C, which are supported by NCI Agency Project at Reference D. Specifically, this line of effort supports coordination with FMN Affiliates and maintenance of 10-year time-frame coherent roadmap to evolve interoperability specifications in successive increments of FMN Spirals, and supports this information with a consistent and coherent interoperability architecture. The contributions made by the contractor in satisfying this SOW comprise essential products which, together with the efforts of NATO ACT PE staff and other entities, will enable the achievement of Alliance transformation objectives and the mitigation of imminent interoperability architecture needs during development of specifications for FMN Spirals 4 and 5.

2. Task-specific Background

To achieve an incremental and continuous increase in the level of maturity of FMN Ready Forces and their requirements for Federated Mission Networking FMN Framework follows a spiral approach. FMN Spirals run incrementally building upon each other at a rate of 2 years, which is the aim of the FMN Vision and Roadmap which are contained in Ref. A. Each FMN Spiral foresees a core period of 4 years from the definition of common goals, which are reflected in a document called FMN Spiral Specification, until their implementation and availability for Federated Mission Networking.

At this time FMN Spiral 1, 2, 3 Specifications have been approved by FMN Management Group (MG), as well as FMN Roadmap which is a longer term vision. The proposed FMN Spiral 4 Specification has been developed and has been approved by the FMN MG. Delivery of a consistent and coherent interoperability architecture is one of crucial factors in development of a balanced spiral specification. This architecture needs to establish an arrangement with the overarching architectures such as the C3 Board-approved C3 Taxonomy and industry standards. Also, it needs to align the individual contributions in interoperability architecture that are provided by the various expert communities that are involved in the development of procedural and service instructions. Work to be done within this initiative will be focused on these two perspective (top-down and bottom-up) in order to distil the fundamental building block for interoperability in the context of FMN.

3. Scope of Work

Intent of this initiative is to address the specific requirements in RRIS activity M87 – to support, track and monitor progress in the development of architectures in the FMN framework and to support the creation of an FMN architecture repository that will provide the Affiliates with reference documentation, tools, architecture building blocks and tailored models, arranged per topic, syndicate, instructions and spiral. This architecture repository will serve as a data-driven decision support tool supporting leadership of the Capability Planning Working Group (CPWG).

Per FMN Spiral Specification the architecture repository will provide the basic elements of an interoperability architecture that includes models created by CPWG Architecture Requirements Syndicate (CARS). The FMN interoperability architecture needs to be fully aligned with the C3 Taxonomy and where necessary, change proposals will be submitted to the proper authorities to change, improve and update that taxonomy to follow the developments in FMN Framework in line with RRIS activity O74.

It is necessary to create an operating model to address the full lifecycle of specification elements from business intake through service delivery to full implementation of mission networks. The operating model should provide information that can be used to prioritize elements of spiral specification development and support a detailed definition and analysis of FMN capability development with a specific target on the improvement of interoperability.

Role requires engagement with POCs Headquarters SACT, SHAPE, NATO Headquarters, NCI Agency and selected CPWG syndicates (including CARS).

4. Tasking and Deliverables

4.1 Tasks.

1. Support FI Branch in its role as the FMN CPWG Core Team to develop and improve the FMN Architecture Repository in support of FMN Capability Planning;
2. Support FI Branch in its role as the FMN CPWG Core Team in development of an Interoperability Architecture report per FMN Spiral Specification, aligned with the C3 Taxonomy, in close cooperation with CARS;
3. Support the FI Branch to submit change proposals for the improvement and further maturation of the C3 Taxonomy, in consideration of developments in the FMN Framework;
4. The contractor will provide a monthly report listing the progress in development of FMN Architecture Repository and change logs for the Interoperability Architecture products;
5. Contractor is to track and monitor progress made in the FMN Spiral specifications and in the C3 Board Architecture Capability Team;
6. Contractor is to identify opportunities for process improvement and training for a better understanding of the employment of architectures in support of interoperability.

Contractor will be hosted by the Allied Command Transformation, Requirements Division, Federated Interoperability Branch, Interoperability Requirements Capture and Specification Section.

Contractor will report to the Interoperability Requirements Capture and Specification (IRCS) Section Head and will be supervised by the Section Head or delegated authority.

4.2 Planned Deliverables.

Deliverables to be supported by the contractor as described in paragraphs above are:

• FMN Architecture Repository
• FMN Spiral 4 Interoperability Architecture (contribution)
• FMN Spiral 5 Interoperability Architecture (draft)
• CPWG Architecture Development Process
• CPWG Architecture Development Training

Further, deliverables will consist of monthly reports.

5. Expected Deliverables

• 31 July 2020: Delivery of a Monthly Report
• 31 August 2020: Delivery of a monthly report, proposal for the FMN Architecture Repository
• 30 September 2020: Delivery of a monthly report, contributions to Final FMN Spiral 4 Interoperability Architecture.
• 30 October 2020: Delivery of a monthly report, installation of FMN Architecture Repository
• November 2020: Delivery of a monthly report
• 23 December 2020: Delivery of a monthly report, proposal for CPWG Architecture Development Process
• 29 January 2021: Delivery of a monthly report, proposal for CPWG Architecture Development Training
• 26 February 2021: Delivery of a monthly report, delivery of a draft for Proposed FMN Spiral 5 Interoperability Architecture.
• 31 March 2021: Delivery of a final report

7. Contract Type and Period of Performance
8. Period of Performance: from 10 August 2020 to 31 Dec 2020.
9. Level of Effort: Full Time, pro rate based on 40hrs/week, to a maximum of 1040 Hours.
10. Location and Travel

Contractor support is to be provided on-site at HQ SACT, Norfolk, VA, USA.

It is possible that the incumbent may be required to undertake duty travel to NATO or FMN Affiliate Nations in Europe in the execution of this SOW. It is expected that there will a maximum of 3 duty trips required in the period of performance. Each duty travel should be no more than 1 week in duration. Travel and per diem costs will be reimbursed in accordance with NATO Travel Regulations.

9. Security

NATO SECRET clearance is required for work on this task and for access to HQ SACT and to use the NATO SECRET Wide Area Network.

Profile

• Required Security Clearance: NATO SECRET
• Organized, self-motivated Subject Matter Expert with experience of applying business analysis techniques in International Military Environment
• Proven track record in analyzing, defining and implementing capabilities to track, monitor and report upon complex parallel activities from involving multiple stakeholders
• Experience of NATO with deep knowledge of NATO Command Structure, NATO C3 Sub Structure and NATO Communications and Information Organization
• Skills and experience in formal reporting
• Familiar with content and employment of NATO C3 Taxonomy
• Preferably have experience in training development

Candidates must be eligible to work in the USA

For information on how we process the personal data in your application, please see the Sapienza Privacy Statement here.