Requirement: Support NIRIS Development
Location: Remote, with occasional on-site work at NCIA The Hague (NETHERLANDS)
Not to Exceed: 39,060, EUR
Period of Performance: 24 August 2026 - 31 December 2026
Required Security Clearance: NATO Secret
Please do NOT apply for any NATO contract positions unless you meet ALL the following criteria:
- Current National or NATO SECRET clearance
- Nationality of one of the NATO member countries
- Current work visa for the specific location if applying for an in-country position
Introduction
- The NATO Information and Communication Agency (NCIA) located in The Hague, The Netherlands, is the Interoperability Assurance Authority for NATO.
- In light of this responsibility, the C2 Service Centre is looking for a service contract which can provide NCIA with supporting the continued development , maintenance, and evolution of the Networked Interoperable Real-Time Information Services (NIRIS) software.
The list below defines the overarching objectives of the engagement and establishes the intended outcomes that the Contractor is expected to achieve through the delivery of the different work packages described in this document.
Under the direction and guidance of the Solution Architect, Service Delivery Manager, Test Manager, and Project Manager, the services to be provided are related to the development , update, maintenance, and testing of NIRIS software modules. It is envisioned that these services shall be provided by one experienced software developer.
- Develop, update, and maintain NIRIS software modules in accordance with agreed requirements, priorities, technical direction, and project planning.
- Develop and update Java software components supporting the continued evolution and sustainment of the NIRIS software baseline.
- Support the full software development lifecycle of NIRIS, including analysis, design, implementation, integration, testing, defect resolution, and documentation.
- Develop and conduct unit testing and automated testing of software components to support software quality, maintainability, and regression testing.
- Support integration and verification activities to ensure that developed or updated software components operate correctly within the wider NIRIS system.
- Analyse, investigate, and resolve software defects, technical issues, and implementation gaps identified during development , testing, integration, or operational support activities.
- Develop, update, and maintain software documentation, including technical documentation, design information, test-related documentation, and other project deliverables as required.
- Contribute to virtual and in-person meetings, reviews, planning sessions, technical discussions, and coordination activities with NCIA stakeholders and project team members.
- Ensure that all developed, updated, and maintained software components and associated deliverables comply with applicable NCIA development standards, quality requirements, configuration management practices, and agreed project procedures.
- Update and expand the produced software components and documentation as necessary to accommodate new, revised, or emerging requirements throughout the duration of the engagement.
The Contractor shall provide the following deliverables classified per service:
Service: NIRIS baseline software development , maintenance, release preparation, and Java technology uplift
Acceptance criteria:
- Assigned software development , maintenance, uplift, defect correction, and release-related tasks are completed in accordance with agreed requirements, priorities, sprint planning, release scope, or work package timeframe.
- Updated software modules are implemented in line with the agreed technical design, coding standards, configuration management practices, and project guidance.
- Software changes are committed, reviewed, and made available in the agreed configuration management environment.
- Delivered software changes are integrated, or made suitable for integration, into the relevant NIRIS development , baseline, or release branch.
- Implemented changes support the functional and technical objectives of the planned NIRIS baseline or release.
- NIRIS Java modules are reviewed and updated where required for compatibility with the agreed Java LTS version.
- Deprecated, obsolete, or incompatible Java constructs are identified and addressed where applicable.
- Updated modules compile, build, and execute successfully in the agreed development and test environments.
- Implemented changes do not introduce known critical or high-severity defects.
- Development support is provided for defect correction, stabilization, integration, and release preparation activities.
- Release-related technical inputs are provided when required.
- Changes take into account the expected support timelines of both the NIRIS baseline and the Java runtime.
Acceptance criteria:
- Unit tests are developed or updated for newly implemented or modified software components where applicable.
- Automated tests are developed or updated to support regression testing of relevant NIRIS functionality.
- Tests are executable in the agreed development , build, or test environment.
- Test results are documented or made available through the agreed tooling.
- Failed tests are analysed and corrected or documented for follow-up.
Acceptance criteria:
- Assigned logging-related development , maintenance, correction, and enhancement tasks are completed in accordance with agreed requirements, priorities, sprint planning, release scope, or work package timeframe.
- Updated logging functionality is implemented in line with the agreed technical design, coding standards, configuration management practices, and project guidance.
- Software changes are committed, reviewed, and made available in the agreed configuration management environment.
- Logging improvements are integrated, or made suitable for integration, into the relevant NIRIS development , baseline, or release branch.
- Logging can be configured or applied at the agreed level of granularity, such as port, endpoint, interface, component, or service, where technically applicable.
- Logging filters are implemented or improved to allow more efficient identification and analysis of relevant log entries.
- Stack traces are handled in a more user-friendly and operationally manageable way, including collapse, grouping, or improved display where included in the agreed scope.
- Updated modules compile, build, and execute successfully in the agreed development and test environments.
- Relevant technical or operational documentation is updated where the logging functionality, configuration, or behaviour has changed.
Acceptance criteria:
- Assigned interface, interoperability, configuration, correction, enhancement, and test-support tasks are completed in accordance with agreed requirements, priorities, sprint planning, release scope, test-event planning, or work package timeframe.
- Updated interface and interoperability-related software components are implemented in line with the agreed technical design, coding standards, configuration management practices, and project guidance.
- Software changes are committed, reviewed, and made available in the agreed configuration management environment.
- Delivered changes are integrated, or made suitable for integration, into the relevant NIRIS development , baseline, or release branch.
- Implemented changes support the agreed provider, consumer, interface, format, protocol, or interoperability objectives.
- Interface-related changes are aligned with agreed interface control documents, standards, configuration requirements, or test-event requirements where applicable.
- Support is provided for agreed standards and formats, such as Link 16 / JREAP, OTH-Gold, DIS, VMF, AIS, or other agreed NIRIS-supported interfaces, where included in the agreed scope.
- OANT/SMAQ-related configuration or analyser limit issues are addressed where included in the agreed scope.
- Support is provided for agreed interoperability events or activities, including CWIX, TDLITS, INTEND, or customer visit test support, where applicable.
- Interface and interoperability changes are tested or made ready for testing in the agreed development , integration, or test environment.
- Implemented changes do not introduce known critical or high-severity defects.
- Updated modules compile, build, and execute successfully in the agreed development and test environments.
- Relevant interface, configuration, test, or release-related technical inputs are provided when required.
- Identified interoperability issues are analysed, corrected, documented, or escalated in accordance with agreed project guidance.
Acceptance criteria:
- Assigned documentation update, maintenance, review, and release-related tasks are completed in accordance with agreed requirements, priorities, sprint planning, release scope, or work package timeframe.
- Documentation is updated to reflect implemented software changes, configuration changes, interface changes, test support functionality, and operational impacts where applicable.
- User manual documentation is updated where user-facing functionality, workflows, screens, configuration steps, or operational procedures have changed.
- Governance documentation is updated where project, release, process, compliance, or management information has changed.
- Internal technical documentation is updated where architecture, design, implementation, configuration, deployment, or maintainability information has changed.
- Interface documentation is updated where supported interfaces, data providers, data consumers, protocols, formats, mappings, or configuration parameters have changed.
- Test documentation is updated where test cases, test procedures, test evidence, validation activities, or test-event support information has changed.
- Release-related documentation is updated where required to support release preparation, acceptance, deployment, or operational transition.
- Documentation updates are reviewed in accordance with the agreed review and approval process.
- Documentation is stored, versioned, and made available in the agreed configuration management or document management environment.
- Documentation is clear, consistent, and aligned with the implemented software baseline or agreed release scope.
- Documentation updates do not contain known major omissions or inconsistencies against the implemented changes.
- Required technical or project inputs are provided to support documentation review, release governance, or acceptance activities.
