2026-0075 C2 Senior Software Developer (NS) - MON 8 Jun

BIDDING INSTRUCTIONS 1. Bidding Instructions Bidders shall submit a proposal (all four parts in one document) clearly providing the following information: a. Cover page: Company name; name(s) of assigned contractor personnel; role(s) and responsibilities assigned to each profiled contractor personnel. b. Past Performance: Evidence of successfully delivering one to three projects of similar scope to this statement of work within the last five years. Each piece of evidence shall demonstrate proof of performance and be comparable in size and scope to the requirements of this role. Include a detailed case study highlighting the Purpose, Objective, Output and Outcome (PO3) as referenced in Annex C. Evidence shall display the ability to manage and deliver standard conformance criteria and test reference components for ADatP-5658 by following customer requirements. c. CVs: CVs of the proposed contractor personnel for the project. d. Effort Estimation (for evaluation purposes only): Estimated total labour and operational costs associated with the delivery of services, including licensing, hosting and travelling; and a breakdown of estimated effort per work package expressed in FTE, where 1 FTE represents one full-time resource working one standard working day (7.6 hours). Deadline Date: Monday 08 June 2026 Requirement: C2 Senior Software Developer Number 1 – NATO FORACS IDATS Software Location: Remote, with occasional on-site work at NCIA The Hague (NLD), NATO HQs / NATO FORACS (BEL) & NATO FORACS Ranges (GRE/USA/NOR) Period of Performance: As soon as possible, but no later than 06 July 2026 – 31 December 2026 Required Security Clearance: NATO Secret STATEMENT OF WORK 1. Introduction The NATO Information and Communication Agency (NCIA) located in The Hague, The Netherlands, is the Interoperability Assurance Authority for NATO. In the light of this responsibility, the Assurance Solutions Branch (ASB) of the Chief Quality Office is looking for a service contract to provide NCIA with development of NATO FORACS IDATS software. 2. Objectives The objectives below define the overarching outcomes the Contractor is expected to achieve through the delivery of the work packages described in this document. The Contractor is expected to align their approach, methodology, and resource planning with these objectives throughout the duration of the engagement. a: During the kick-off meeting the Contractor shall be assigned to the IDATS C2C project. The scope, priorities, dependencies, and initial backlog shall be reviewed. b: Maintaining and updating the development backlog, including progress reporting, comments, risk identification, and issue tracking. Utilising JIRA as the depository and planning tool. Ensure the documentation and maintenance of all produced deliverables. c: Participate in development sprints. Working on agreed JIRA tickets. d: Support FORACS Ranges in testing IDATS software either remotely or via on-site participation. e: Supporting formal knowledge handover sessions prior to contract completion to ensure continuity, maintainability, and long-term sustainability of the delivered solutions. All source code, scripts, configuration items, and documentation produced under this contract shall be stored and maintained under configuration management within the NATO Software Factory environment. Coordination and development activities shall be performed remotely through secure access to NCIA systems using the unclassified development laptop provided by the NCI Agency. The Contractor shall operate as part of a multidisciplinary development team following the SCRUM methodology. The scope, content, and acceptance criteria of each deliverable shall be defined by the Technical Leader and formally approved by the Project Manager. Completion and acceptance of deliverables shall include verification that adequate documentation and knowledge transfer activities have been performed. 3. Scope of Work The Contractor shall provide the following deliverables classified per service: Service A – Kick-Off Meeting Active participation in the project kick-off meetings with NATO FORACS Technical Lead. Deliverable: Project Kick-Off Meeting Report Output: Kick-off meeting report summarising the scope, priorities, dependencies, and initial backlog. Outcome: An agreed roadmap for software development which will lead to a software build release as directed by the project sponsor. Acceptance Criteria: The report includes key decisions, action items, and the Contractor's contributions. The Contractor's contributions support the clarification, improvement, or extension of the IDATS software. KPI – Report Completeness: Inclusion of all required sections (decisions, actions, contributions). Target = 100%. KPI – Contribution Relevance Score (1–5): Stakeholder evaluation of usefulness of contributions. Target >= 4.0. Service B – JIRA-Based Development Reviewing and updating sprint planning within JIRA with the aim of achieving consistency and traceability of the sprint-based development period. Deliverable: Updated JIRA IDATS Software Tickets Output: An updated version of the JIRA IDATS Software tickets incorporating all required amendments and newly defined criteria covering the full IDATS sprint planning, presented in the agreed-upon format. Outcome: A finalised and fully aligned set of JIRA tickets for the planning of the sprint. Acceptance Criteria: All amendments and new criteria are included in the updated JIRA documentation; all conformance criteria are deemed testable by the project sponsor; the updated conformance criteria follow the agreed format consistently; the document is complete and ready for stakeholder review. KPI – Completeness: Percentage of the standard covered by the acceptance criteria list. Target = 100%. KPI – Testability Rate: Percentage of conformance criteria that are testable. Target = 100%. KPI – Format Compliance: Adherence to agreed template/format. Target >= 95%. KPI – Clarity Score (1–5): Stakeholder evaluation on clarity, readability, and structure. Target >= 4.0. Service C – Development Sprints Active participation in the development sprints of the IDATS software. Deliverable: Sprint Development Period Output: Weekly updates on development summarising the progress, priorities, dependencies, and remaining backlog. Outcome: An agreed completion of software development sprint as agreed with NATO FORACS Technical Lead which will lead to a software build release as directed by the project sponsor. Acceptance Criteria: The report includes key decisions, action items, and the Contractor's contributions. The Contractor's contributions support the clarification, improvement, or extension of the IDATS software. KPI – Report Completeness: Inclusion of all required sections (decisions, actions, contributions). Target = 100%. KPI – Contribution Relevance Score (1–5): Stakeholder evaluation of usefulness of contributions. Target >= 4.0. Service D – Technical Artefacts / Documentation Reviewing and updating the existing IDATS Software documentation (release/installation instructions) with the aim of achieving completeness and consistency. Deliverable: Updated IDATS Software Documentation Output: An updated version of the IDATS Software conformance criteria incorporating all required amendments and newly defined criteria covering the full IDATS documentation, presented in the agreed-upon format. Outcome: A finalised and fully aligned set of IDATS Software documentation conformance criteria ready for stakeholder use. Acceptance Criteria: All amendments and new criteria are included in the updated document; all conformance criteria are deemed testable; the updated conformance criteria follow the agreed format consistently; the document is complete and ready for stakeholder review. KPI – Completeness: Percentage of the standard covered by the acceptance criteria list. Target = 100%. KPI – Testability Rate: Percentage of conformance criteria that are testable. Target = 100%. KPI – Format Compliance: Adherence to agreed template/format. Target >= 95%. KPI – Clarity Score (1–5): Stakeholder evaluation on clarity, readability, and structure. Target >= 4.0. Service E – On-Site Operation at NATO FORACS Ranges Participation at NATO FORACS live test events as directed by the project sponsor. Deliverable: On-Site Operation of IDATS Software at NATO FORACS Ranges Output: On-site operation of the IDATS software to support the execution of NATO FORACS testing at FORACS ranges located in the USA, NOR, and GRC. Outcome: Consistent and reliable operation of the software, enabling successful execution of maritime tests. Acceptance Criteria: The IDATS software is operated reliably throughout the event's execution phase; interoperability tests are supported and executed as required; any operational issues are addressed promptly to maintain test continuity. KPI – System Uptime: System availability during the event. Target >= 95%. KPI – Average Issue Resolution Time: Average time to fully fix any operational issues. Target <= 1 hour. Travel Requirement: At least one member of the Contractor's personnel shall be present on-site at one of the FORACS ranges if requested by the project sponsor. 4. Deliverables Compatibility The expected deliverables shall be fully compatible with the IDATS platform and its underlying technology stack. The following requirements shall be met: a: IDATSvX application is developed using Java, currently Java 21. Any other technology selection shall be agreed with the NCIA/NATO FORACS POCs. b: Application components can be implemented in any suitable technology, if previously agreed with the NCIA/NATO FORACS POCs. c: The target environment is MS Windows laptops on a segregated network on-board the ship under test (SUT), with a custom diode being used to connect to the CMS interface of the SUT, which can also be a submarine or helicopter. d: All conformance tests are in JUnit, specifically JUnit5. The Customer is responsible for any further testing. e: All deliverables shall comply with the security requirements instructed by the NCIA POC. 5. Work Packages Delivery Schedule Each work package represents a discrete and manageable unit of work comprising one or more deliverables that together contribute to the overall objectives of the engagement. The Contractor shall deliver specified outputs within the indicated target delivery dates and in accordance with the defined acceptance criteria. WP01 – Services A & B: Deliverables: Kick-off meeting report and updated JIRA sprint planning. Target Delivery Date: 2 weeks after the start of the assignment. Bid Percentage: 15%. WP02 – Service C: Deliverable: Active participation in development sprints. Target Delivery Date: 16 December 2026. Bid Percentage: 70%. WP03 – Service D: Deliverable: Updated IDATS Software documentation. Target Delivery Date: 16–17 December 2026. Bid Percentage: 5%. WP04 – Service E: Deliverable: On-site operation of IDATS Software at NATO FORACS Ranges. Target Delivery Date: As directed by project sponsor. Bid Percentage: 5%. WP05 – Service F: Deliverable: Supporting formal knowledge handover sessions prior to contract completion. Target Delivery Date: 18 December 2026. Bid Percentage: 5%. Note: The Work Packages Delivery Schedule and scope of outputs may be subject to modification in the event of unforeseen circumstances or changes in NCIA customer requirements, provided such modifications do not affect the total price of the bid. Any such modifications shall be made by mutual agreement between NCIA POC and the Contractor and documented in writing. 6. Payment Milestones and Proofs of Deliverable Payment shall be dependent upon successful acceptance of the deliverable completion report and the Delivery Acceptance Sheet (DAS). Final payment for each deliverable shall be determined in accordance with the extent to which the defined KPIs have been achieved. KPI validation shall be performed by the NCIA POC. Payment Structure: 70% Fixed Payment released upon formal acceptance of deliverable; 30% Variable Payment contingent upon KPI performance. KPI Band – Meets or exceeds target (100%): 100% of KPI weight KPI Band – Minor deviation (90–99%): 90% of KPI weight KPI Band – Moderate deviation (80–89%): 75% of KPI weight KPI Band – Significant deviation (70–79%): 50% of KPI weight KPI Band – No compliance (<70%): 0% of KPI weight Payment Milestone A: 2 weeks after the start of the assignment Payment Milestone B: 2 weeks after the start of the assignment Payment Milestone C: 16 December 2026 Payment Milestone D: 17 December 2026 Payment Milestone E: As required Payment Milestone F: 18 December 2026 Invoices shall be accompanied by a Delivery Acceptance Sheet signed by the Contractor and the NCIA POC or the assigned Service Delivery Manager. Work packages cannot be invoiced before their defined payment milestone. 7. Coordination and Reporting a: The Contractor shall deliver services under the guidance of the NCIA IDATS PM team and NATO FORACS Technical Lead. b: The Contractor shall deliver services remotely, unless the deliverable explicitly states on-site delivery at the indicated location. c: For each work package to be considered complete and payable, the Contractor must report the outcome of their work (Deliverable Completion Report) by email to the appointed NCIA POC. d: The Deliverable Completion Report shall be subject to review by the NCIA POC, who shall provide a response including the evaluation of the applicable KPIs for the relevant deliverable. 8. Security a: Performance of the services described in this SOW requires a valid NATO SECRET security clearance prior to the start of the engagement. b: It is the responsibility of the contracting company to obtain and maintain the security accreditation of all individuals working on this arrangement. 9. Constraints a: All documentation provided under this statement of work shall be based on NCIA templates or the format agreed with the NCIA POC. b: All scripts, documentation, and required code shall be stored under NATO Software Factory platforms and tools. 10. Practical Arrangements a: This is a deliverables-based contract. b: The Contractor shall be provided a user account for access to the NATO Software Factory (Azure DevOps). c: This SOW requires scheduled travel as detailed in Section 3.E. Travel, lodging, and associated expenses are included in the total price of the bid; NCIA shall not be invoiced separately for scheduled travel. d: Extraordinary Travel (Purchaser Directed Travel) may be required to other NATO or non-NATO locations as necessary. The cost of all travel and subsistence for such unforeseen meetings will be addressed through a contract amendment. e: Extraordinary Travel expenses will be reimbursed in accordance with Article 5.5 of the AAS+ Framework Contract, as a separate PO line with a not-to-exceed value, reimbursed upon submission of all receipts and invoices in line with NCIA processes. f: The services depicted in this SOW may be carried out by either one contractor personnel or a team of contractors. It is up to the bidder to propose the size of the team that delivers the services and produces the deliverables within the allocated timelines. 11. Qualifications [See Requirements] ANNEX B – KPI-TO-PAYMENT MAPPING MODEL This Annex establishes the mechanism by which the achievement of defined Key Performance Indicators (KPIs) shall be mapped to the payment due for each deliverable under this Statement of Work. It describes how KPI results will be evaluated and applied for the purpose of determining the final payable amount. Overall Payment Model For each deliverable, payment is structured as follows: Fixed Payment (70%): Released upon formal acceptance, subject to the deliverable meeting the applicable acceptance criteria. Variable Payment (30%): Contingent upon KPI performance. Each KPI applicable to a deliverable is assigned an equal weighting within the 30% variable payment component. The proportion of each KPI weight payable is determined in accordance with the KPI scoring bands below. KPI Achievement – Meets or exceeds target (100%): 100% of KPI weight payable KPI Achievement – Minor deviation (90–99%): 90% of KPI weight payable KPI Achievement – Moderate deviation (80–89%): 75% of KPI weight payable KPI Achievement – Significant deviation (70–79%): 50% of KPI weight payable KPI Achievement – No compliance (<70%): 0% of KPI weight payable Total Payment Formula: Total Payment = Fixed Component + Variable Component, where Fixed Component = 70% of deliverable value, and Variable Component = Sum of (KPI Weight x Percentage of KPI weight). 8. Security Performance of the services described in this SOW requires a valid NATO SECRET security clearance prior to the start of the engagement. REQUIREMENTS Each contractor personnel must meet the following requirements: At least 10 years of professional experience in the industry of software development. At least 5 years of proven knowledge of, and practical experience in, the operational or technical use of FORACS IDATS systems and software supported by NCI Agency. Proven experience in the design and test of secure message exchange protocols. Experience with and deep knowledge of electrical and data specifications for communication between marine electronics, such as NMEA and EMM. Practical understanding of the operations of maritime systems such as GPS, INS, Radar, Sonar, and Towed Array. Strong mathematical skills, as the work includes implementation and verification of complex calculations. Experience with and deep knowledge of message specifications for data links between combat management systems and external systems, specifically ANEP82. Practical experience in the area of computer networks and messaging security, including DNS, domains, PKI certificates, network designs, OAuth, and OpenID. Proven experience with and knowledge of NoSQL databases, MongoDB in particular, and also experience with Morphia for integrating MongoDB in Spring-based applications. Proven knowledge of, and practical experience in, modern test engineering and test management methods and paradigms. Proven up-to-date knowledge of computer system architectures, systems security, client/server, LAN/WAN and network concepts, test techniques, Database Management Systems (DBMS), and data management concepts. 5 years of programming experience in Java. Recent experience with XML and JSON technologies. Willingness to work in challenging environments, including within confined spaces on board active warships and submarines. Must have the nationality of one of the NATO nations. Excellent command of spoken and written English.