2026-0125 Solutions Architect (NS) - FRI 2 Oct EXTENDED AMENDMENT 1

BIDDING INSTRUCTIONS

1.1 Technical Proposal

Bidders shall include in the Technical Proposal a CV of the proposed candidate, clearly indicating relevant experience for the requirements (Section 3) and qualifications (Section 9) in the Statement of Work.

Bidders shall also include a compliance matrix referring how each candidate meets each of the stated requirements (Section 3) and qualifications (Section 9) of the Statement of Work, justified by relevant (project) experience.

Deadline Date: Friday 02 October 2026

Requirement: Solutions Architect – Amendment 1

Location: Off-site (80%), on-site in The Hague or Brussels (20%)

Period of Performance: Base: 11 November 2026 (Tentative) – 31 March 2027. Option: 01 April 2027 – 31 December 2027.

Required Security Clearance: NATO SECRET

1. INTRODUCTION

The NCIA Chief Technology Office requires Solutions Architect services to capture and document the as-is and to-be NATO Intelligence System Architecture as well as a roadmap for how to transition the as-is to the to-be architecture.

The services include the capturing of the current architecture through the delivery of an as-is architecture with generated documentation, the capturing of the to-be architecture as well as the implementation roadmap including transition architecture in order to assure future programmatic technical coherence. With a focus on documenting the architecture and engagement with all NATO Intelligence Enterprise key stakeholders, the services will ensure the delivery of high-quality technical products that align and will inform current and future NATO Intelligence Enterprise programmes.

2. SCOPE OF WORK

The purpose of this project is to provide the NATO Intelligence Enterprise (NIE) “as-is” and “to-be” architecture and implementation roadmap. To achieve this scope, the Contractor shall:

• Engage with NCIA staff (Technical Subject Matter Experts, Project Managers and Enterprise/Segment Architects) to understand and document current and future system/service capabilities.
• Develop high level overview of as-is architecture.
• Develop the NIE as-is architecture, capturing selected current NIE, applications and system capabilities; their inter-dependencies and the technologies by which they are implemented and the standards they comply with to ensure interoperability.
• Develop the high level NIE to-be architecture.
• Develop the implementation roadmap that provides direction on how to transition towards the to-be architecture.
• Advise on technological synergies, gaps and opportunities identified.

3. DELIVERABLES

3.1 “As-Is” Architecture

The Contractor shall deliver the “as-is” NIE architecture models, which comprise Application Architecture, Business Architecture, Technical Architecture, and Data/Information Architecture. The metamodel guiding the architecture models will be provided upon onboarding.

The “as-is” architecture report will, to the maximum extent, be generated from the architecture models. The report shall cover the following areas:

Executive Summary

Description: Brief overview of the goals and objectives, stakeholders, architecture views and scope.

KPIs: 100% coverage of goals, objectives, scope, stakeholders and required architecture views.

Acceptance Evidence: Approved scope checklist, traceability links, review record and editable source.

Accept When: Decision-focused summary is complete, consistent with the package and approved by the Purchaser PM and Lead Architect.

Current Architecture Overview

Description: High-level description of the current NIE architecture / NISA.

KPIs: KPI 1 — 100% of in-scope domains, boundaries, external actors, key dependencies and integration points represented against the baseline inventory. KPI 2 — 100% of overview views reviewed by designated domain SMEs; 0 unresolved Critical or Major modelling inaccuracies.

Acceptance Evidence: Context/dependency views, inventory reconciliation and SME validation log.

Accept When: Views describe the current state, agree with domain models and contain no unapproved future-state content.

Stakeholders and Roles

Description: List of stakeholders and their roles and responsibilities.

KPIs: KPI 1 — 100% of identified stakeholder groups have role, responsibility, interest and required archite