Job Description

BIDDING INSTRUCTIONS

Services under this SOW are to be provided by one candidate to cover the required profile outlined in the SOW below.

Technical Proposal

Bidders shall include in the Technical Proposal:

a.: The CV of the proposed candidate, clearly indicating relevant experience for the specific requirements (Section 11).

b.: Related attestation.

c.: Compliance matrix demonstrating how the candidate meets all specific requirements for their assigned profile (Section 11), justified by relevant experience.

Price Details

Bidders shall provide a unit price for each deliverable (D-3.1, D-3.2, D-3.3, D-3.4, and D-3.5) for the 2026 BASE period. Price shall be all-inclusive, incorporating all costs necessary for the delivery of the outputs, including any travel costs as described in Section 10.

Technical Compliance

Each bid will be assessed for technical compliance on a profile basis. A bid is technically compliant only if the proposed candidate passes the compliance assessment.

Deadline Date: Monday 01 June 2026

Requirement: Obsolescence Management Support

Location of Performance: 60% off-site at contractor's premises; 40% on-site at NCIA premises in Braine-l'Alleud, Belgium. This location is expected to be vacated during 2027 (final closure no later than 31 December 2027), with the place of performance transitioning to Brussels or Mons, Belgium depending on operational requirements.

Period of Performance: 2026 BASE: As soon as possible, no later than 29 June 2026 (tentative) – 31 December 2026.

2027 OPTION: 1 January 2027 – 31 December 2027 (if exercised).

2028 OPTION: 1 January 2028 – 31 December 2028 (if exercised).

Required Security Clearance: NATO SECRET

1. INTRODUCTION

The NATO Integrated Mission Services Centre (NIMSC) – Engineering Management Office (EMO) provides expertise in design and maintenance of mobile infrastructure such as: DCIS, Dispersible systems and highly mobile systems, SATCOM, and Wireless Communications in support of Projects, Services, and POWs. With this SOW, EMO pursues industry services to manage obsolescence, while maintaining control over standards and quality.

The NIMSC-EMO requires Obsolescence Management Services to provide the technical depth and strategic oversight required to sustain a resilient, future-ready Hardware (HW) and Software (SW) estate. The aim is to shift the organisation from a reactive stance to a predictive, intelligence-driven lifecycle posture. The focus is on safeguarding operational continuity, reducing risk exposure, and ensuring that critical systems remain supportable, secure, and aligned with long-term capability needs.

2. INTENDED BUSINESS OUTCOME

The intended business outcome of this contract is to ensure continuous, high-quality obsolescence management processes. Specifically, the NCIA seeks to:

Reduce operational risk: Minimise the likelihood and impact of unplanned obsolescence events that could compromise mission-critical systems.

Achieve optimised investment planning: Enable smarter, data-driven decisions on technology refresh, vendor engagement, and long-term capability sustainment.

Improve predictability and control: Transition from reactive to proactive lifecycle management, achieving stable and predictable operations.

Attain enhanced system availability and resilience: Ensure that essential communication and information services remain reliable, supportable, and compliant throughout their lifecycle.

Adhere to governance standards in engineering: Structured processes and technical guidance.

The successful delivery of this contract will result in NIMSC having reliable obsolescence management services with a critical emphasis on Unplanned Obsolescence Management (UOM) mitigation and long-term Lifecycle Management (LCM).

3. SCOPE OF WORK

The scope of this contract covers the establishment of a comprehensive deployable CIS obsolescence-management framework by developing an inventory process that captures stakeholder knowledge, conducting a gap analysis, and mapping technical and operational dependencies across systems. The scope also includes assessment and prioritization of obsolescence risks and development of risk management methodologies. The standardized approach encompassing governance and business continuity includes the development of Standard Operating Procedures (SOPs). Deliverables as listed below will enable sustained lifecycle visibility and risk mitigation for critical CIS assets.

3.1 Production of Obsolescence Management Process Framework

The Obsolescence Management Process Framework shall include: an inventory of all obsolescence-related processes, workflows, ownership, and associated systems; a gap analysis of the obsolescence-related processes, workflows, ownership, and associated systems to identify inconsistencies or inefficiencies; and recommendation and action-oriented proposals to streamline the processes and workflows.

In the course of delivery, the Contractor shall engage with relevant stakeholders in structured elicitation sessions, including workshops and one-on-one interviews, with several Purchaser-designated Points of Contact (PoCs) to validate existing documentation and extract implicit operational knowledge. The obtained information shall be structured in formal documents with registers or logs, including roles and responsibilities, decision-making processes, risks, pain points, and workarounds.

3.2 Dependencies Mapping Framework

The Contractor shall develop a structured framework that defines how service, system, and component dependencies are identified, assessed, and documented, accompanied by practical case studies demonstrating how dependencies influence obsolescence risk. The framework shall include: principles, definitions, and methodology for identifying and classifying dependencies; criteria for assessing dependency criticality and impact; and standardized templates and/or visualization formats (e.g., diagrams, matrices).

The Contractor shall regularly assess the impact of the developed Dependencies Mapping Framework and shall provide updated Dependency and Impact Maps containing: updated systems, updated relationships, and optimization actions.

3.3 Process Modelling

Based on the gap analysis, the Contractor shall identify and prioritize missing processes. The Contractor shall develop models of the top priority processes in BPMN (Business Process Model and Notation) format compliant with the Agency Process Framework (AProF).

3.4 Standard Operating Procedures (SOP) Development

The Contractor shall standardize processes across systems and stakeholders through formal documentation, by developing SOPs and/or Process Guidance Documents (PGDs) focused on Unplanned Obsolescence Management (UOM) that define governance, workflows, and responsibilities.

The Contractor shall develop SOPs covering the 3 most impactful processes from deliverable 3.1, using ServiceNow, Configuration Management Database (CMDB), and other existing toolsets. The Contractor shall regularly assess and provide updated SOPs and/or PGDs including: process improvements, updated workflows, new decision criteria, and clarified roles and responsibilities.

3.5 Risk Consolidation and Management Methodology

The Contractor shall develop: a structured and consolidated Risk Log integrating financial, operational, and technical risk assessments with risk prioritization based on impact and likelihood, ensuring integration with existing NCIA Risk Management tools; a refined Risk Management Methodology; and an updated Obsolescence Risk Alerts Package containing a report on obsolescence performance, early-warning intelligence, and action-oriented mitigation proposals.

3.6 DELIVERABLES, ACCEPTANCE CRITERIA, AND PAYMENT SCHEDULE

The following deliverables define the expected outputs of this contract. Payments shall be determined based on monthly KPI performance and the application of Service Credits in accordance with Section 4.3. The Purchaser reserves the right to exercise a number of deliverables which may vary according to NATO operational needs. The profile shall be staffed by a single, dedicated individual for the duration of the contract period.

3.6.1 Deliverables Table

The Purchaser reserves the right to exercise a number of deliverables which may vary according to NATO operational needs.

D-3.1 Production of Obsolescence Management Process Framework

What is being delivered: Obsolescence Management Process Framework including: inventory of all obsolescence-related processes, workflows, ownership, and associated systems; gap analysis identifying inconsistencies or inefficiencies; and recommendation and action-oriented proposals to streamline processes and workflows.

Specific Requirement 1: Develop and maintain secure, scalable data pipelines and repositories to consolidate CIS inventories, lifecycle data, vendor EOL/EOS information, and supply chain indicators — defines the data backbone of the framework.

Specific Requirement 2: Integrate data from NCIA systems, logistics platforms, asset databases, and OEM sources — enables centralized obsolescence monitoring within the framework.

Specific Requirement 3: Ensure compliance with NATO security policies (INFOSEC, CIS Security Accreditation, C-M (2002)49) — ensures framework is security-compliant.

Specific Requirement 4: Maintain data governance, lineage, and auditability — supports governance layer of the framework.

Format: Report/Documents (Word/PDF), Gantt Chart, Registers/logs (Excel/CSV).

Acceptance Criteria 1: Complete inventory of all existing obsolescence-related processes, workflows, roles, and systems.

Acceptance Criteria 2: Gap analysis clearly identifies inconsistencies, inefficiencies, and missing processes.

Acceptance Criteria 3: Recommendations are actionable, prioritized, and aligned with NCIA governance.

Acceptance Criteria 4: Stakeholder engagement evidence provided (workshop notes, interview summaries).

Acceptance Criteria 5: Registers include roles, responsibilities, decision points, risks, pain points, and workarounds.

Verification Method: Final Quality Control review by NCIA. Validation against Data Product Specification agreed with the customer.

Expected Outcome: A validated, structured understanding of current obsolescence processes, enabling NCIA to identify weaknesses, standardize practices, and plan targeted improvements.

D-3.2 Dependencies Mapping Framework

What is being delivered: Structured Dependencies Mapping Framework including: principles, definitions, and methodology for identifying and classifying dependencies; criteria for assessing dependency criticality and impact; standardized templates and/or visualization formats (e.g., diagrams, matrices). Updated Dependency and Impact Map containing: updated systems, updated relationships, and optimized actions.

Specific Requirement 1: Map system, software, and platform dependencies in line with NAF — core deliverable contribution.

Specific Requirement 2: Integrate multi-source data (CIS, logistics, OEM) — feeds dependency mapping with accurate, cross-domain data.

Specific Requirement 3: Collaborate with engineers and service owners — validates dependency models and relationships.

Format: Documents (Word, PDF), Templates, diagrams, matrices, Dependency and Impact Maps (Visio, PDF, or approved NCIA format).

Acceptance Criteria: Produced within agreed timeline and requirements defined by the Customer; passed QC.

Verification Method: Final Quality Control review by NCIA. Validation against Dependencies Framework Specification agreed with the customer.

Expected Outcome: NCIA-aligned method for mapping dependencies, enabling better risk forecasting, lifecycle planning, and obsolescence mitigation.

D-3.3 Process Modelling

What is being delivered: BPMN models of the top-priority missing processes identified in the gap analysis.

Specific Requirement 1: Build analytical models and dashboards to identify high-risk components and forecast trends — supports modelling of decision-support processes.

Specific Requirement 2: Develop data flows and pipeline logic — forms the basis of process models (data ingestion, analysis, action).

Specific Requirement 3: Support development of methodologies aligned with LCM and NCIA practices — translates into formal process models.

Format: BPMN 2.0 diagrams (Visio or BPMN-compliant tool); supporting documentation (PDF/Word); compliance statement with AProF.

Acceptance Criteria 1: Models follow BPMN 2.0 standards and AProF conventions.

Acceptance Criteria 2: Processes reflect validated workflows, roles, and decision points.

Acceptance Criteria 3: Models address the highest-priority gaps identified in Deliverable 3.1.

Acceptance Criteria 4: Diagrams are clear, unambiguous, and ready for integration into NCIA repositories.

Verification Method: Review by NCIA Process Owners and AProF custodians. Conformance check against AProF modelling rules.

Expected Outcome: Standardized, NCIA-compliant process models that support consistent execution, training, and future automation.

D-3.4 Standard Operating Procedures (SOP) Development

What is being delivered: Developed SOPs/PGDs for the three most impactful processes identified in Deliverable 3.1, with periodic updates.

Specific Requirement 1: Support development of obsolescence management methodologies and SOPs — direct contribution.

Specific Requirement 2: Collaborate with stakeholders to validate data accuracy and workflows — ensures SOPs are operationally viable.

Specific Requirement 3: Ensure compliance with NATO policies — embeds security procedures into SOPs.

Format: Documents (Word/PDF), workflow diagrams (Visio/PDF), integration guidance for ServiceNow, CMDB, and other NCIA tools.

Acceptance Criteria 1: SOPs clearly define governance, workflows, roles, responsibilities, and decision criteria.

Acceptance Criteria 2: SOPs incorporate Unplanned Obsolescence Management (UOM) requirements.

Acceptance Criteria 3: Updated versions include improvements, new criteria, and clarified responsibilities.

Acceptance Criteria 4: SOPs are compatible with NCIA toolsets (ServiceNow, CMDB).

Verification Method: Review and acceptance by NCIA Service Owners and CIS engineering teams. Validation through tabletop exercises or scenario walkthroughs. Compliance check with NCIA documentation standards.

Expected Outcome: Consistent, standardized execution of obsolescence processes, reducing ambiguity and improving operational readiness.

D-3.5 Risk Consolidation and Management Methodology

What is being delivered: A consolidated risk log, refined risk-management methodology, and updated Obsolescence Risk Alerts Package.

Specific Requirement 1: Build analytical models and dashboards to identify high-risk components — core risk identification capability.

Specific Requirement 2: Consolidate data across inventories, lifecycle, and supply chain indicators — enables risk aggregation.

Specific Requirement 3: Advise on technical and financial aspects of obsolescence — supports risk evaluation and prioritization.

Specific Requirement 4: Support mitigation planning with stakeholders — feeds risk treatment strategies.

Format: Documents/Alert Packages (Word/PDF), Logs (Excel/CSV and dashboard if applicable).

Acceptance Criteria 1: Risk log integrates financial, operational, and technical risks.

Acceptance Criteria 2: Risks are prioritized using impact and likelihood scoring aligned with NCIA tools.

Acceptance Criteria 3: Methodology is clear, structured, and compatible with NCIA risk-management frameworks.

Acceptance Criteria 4: Alerts package includes performance reporting, early-warning indicators, and mitigation proposals.

Verification Method: Review and acceptance by NIMSC-EMO Head and Risk Management Office. Cross-checking risk scoring with existing NCIA tools and frameworks. Validation of early-warning indicators against real system data.

Expected Outcome: A unified, actionable risk-management approach that strengthens NCIA's ability to anticipate, prioritize, and mitigate obsolescence risks across CIS assets.

3.6.2 Deliverable Evaluation and Acceptance

The Contractor shall submit, no later than five (5) working days following the end of each calendar month, all deliverables completed during the reporting period together with associated KPI performance results. Each deliverable shall be evaluated against three assessment criteria: Timeliness of Delivery; Fitness for Purpose; and Completeness. Each criterion is scored 2 (fully compliant), 1 (partially compliant), or 0 (non-compliant). The Total Score (TS) = A + B + C, with a maximum of 6.

Score 6: Excellent

Score 5: Good

Score 4: Acceptable

Score 3: Weak

Score 0–2: Unacceptable

Deliverables that do not achieve at least a Good performance level shall be revised and resubmitted by the Contractor at no additional cost until the required quality level is met.

3.7 Option Year Deliverables

The Purchaser reserves the right to exercise deliverables at a later time, which may vary according to NATO operational needs. If the annual options are exercised, the deliverables described above shall apply for the relevant option year. Pricing for option years will be determined by applying the price adjustment formula as outlined in CO-115786-AAS+ Special Provisions article 6.5. Option year payments shall be made monthly as per KPI completion.

3.8 COORDINATION AND REPORTING

NCIA project team and the Contractor personnel will have regular meetings to review progress, address issues, and make necessary adjustments to the processes or production methodology. The meetings will be physically in the office, or in person via electronic means using Conference Call capabilities, according to the NCIA business manager's instructions.

To ensure effective delivery and quality of the defined deliverables, the following coordination and reporting arrangements shall apply:

3.8.1 Deliverable Assignment and Planning

A monthly coordination meeting shall be held between the NCI NIMSC-EMO Head and the Contractor to review priorities, timelines, and acceptance criteria. These shall be recorded in meeting minutes. A backlog of task progress and issues shall be maintained and reviewed at each coordination meeting.

3.8.2 Progress Monitoring

Regular progress meetings shall be held between the NCIA and the Contractor to review the status of deliverables, address issues, and make necessary adjustments. Meetings will be held physically at the office or via electronic means using conference call capabilities. The Contractor shall use a shared dashboard or tool to track the status of all deliverables and issues, and shall provide a monthly KPI performance report including progress against targets, supporting data, and identified risks or deviations.

3.8.3 Reporting Requirements

The Contractor shall provide regular reporting to ensure visibility of progress, risks, dependencies, stakeholder engagement activities, and overall performance.

Monthly Service Performance Report

No later than five (5) working days following the end of each calendar month, the Contractor shall submit a Monthly Service Performance Report containing at a minimum: executive summary of activities performed during the reporting period; progress status against each deliverable and associated milestones; status of workshops, interviews, and stakeholder engagement activities; summary of completed, ongoing, and planned tasks; KPI performance results; identified risks, issues, dependencies, and mitigation actions; status of action items and decisions; updates to registers, logs, dependency maps, SOPs, or risk-management artefacts; planned activities for the following reporting period; and deviations from agreed timelines with justification and recovery actions. The report shall be submitted in Microsoft Word and/or PDF format, together with any applicable supporting registers, dashboards, diagrams, logs, or spreadsheets.

Ad Hoc Reporting

The Contractor shall provide ad hoc reports, analysis, dashboards, process updates, dependency mappings, risk assessments, or management briefings upon request by the Purchaser within agreed timelines. The Contractor shall prepare meeting material, presentations, status updates, and meeting minutes when requested.

Risk and Issue Reporting

The Contractor shall promptly notify the Purchaser of any identified risks, blockers, delays, data inconsistencies, dependency conflicts, security concerns, or operational issues. Such notifications shall include: description of the issue or risk; impact assessment; affected systems, processes, or stakeholders; proposed mitigation actions; and expected resolution timeline.

4. PERFORMANCE MANAGEMENT

4.1 Key Performance Indicators (KPIs)

The Contractor's performance shall be measured against the following KPIs on a monthly basis:

KPI 1 – Knowledge Formalization Rate: The percentage of identified implicit knowledge documented and converted into formal SOPs. Target: 100% conversion of identified critical legacy workflows. Measured monthly.

KPI 2 – Data Integrity and Sync Score: Variance between physical inventory records and digital records (e.g., ServiceNow / FocalPoint). Target: less than 3% variance (high-fidelity synchronization). Measured monthly.

KPI 3 – Proactive Lead Time: Time between identification of a risk (e.g., vendor EOL announcement) and its registration in the Risk Log. Target: less than 5 business days. Measured monthly.

KPI 4 – Evaluation of Deliverables: Evaluation of deliverables D-3.1 to D-3.5 against agreed acceptance criteria including timeliness, fitness for purpose, completeness, and compliance with NCIA/NATO standards, using the methodology defined in Section 3.6.2. Target: 100% of deliverables achieve a minimum Good performance level (Total Score 5 or above). Measured monthly.

KPI 5 – Monthly Service Reporting Timeliness: Timeliness, completeness, and usability of monthly service reporting, measured by delivery of all required reports by the fifth working day of the reporting period, ensuring all reports are complete and fit for purpose. Target: 100% compliance. Measured monthly.

4.2 KPI Monitoring

KPI performance shall be reviewed on a monthly basis. The Contractor shall demonstrate measurable progress toward KPI targets in each reporting period. For KPIs with defined target dates, incremental progress and trajectory toward the target shall be evaluated monthly. Lack of progress, regression, or insufficient supporting evidence may result in a lower score under fitness for purpose and/or completeness. KPI reporting shall be included in the Contractor's monthly submission and may be used by the Purchaser to validate service quality, support acceptance decisions, and justify performance scoring and associated payment adjustments.

4.3 Service Credits

4.3.1 KPI Weighting

KPI 1 – Knowledge Formalization Rate: 1% weighting.

KPI 2 – Data Integrity and Sync Score: 1% weighting.

KPI 3 – Proactive Lead Time: 5% weighting.

KPI 4 – Evaluation of Deliverables: 5% weighting.

KPI 5 – Monthly Service Reporting Timeliness: 3% weighting.

4.3.2 Calculation of Service Credits

Where a KPI is determined to be Non-Compliant (Not Met), the corresponding percentage shall be applied as a Service Credit. Total Service Credit (%) = sum of percentages assigned to each KPI that is Not Met. Service Credit Value = Total Service Credit (%) x Monthly Service Fee. Service Credits shall be calculated based on validated KPI results, documented in the Service Performance Report, reviewed and confirmed during service review meetings, and deducted from the corresponding invoice.

4.3.3 Cap on Service Credits

The total service credits applied in any reporting period shall not exceed 15% of the applicable monthly service fee.

4.4 Audit and Verification

The Contractor shall ensure that all KPI measurements and service credit calculations are accurate, transparent, and auditable. The Purchaser reserves the right to verify KPI results, request supporting evidence, and challenge any calculation deemed incorrect.

5. PAYMENT

5.1 Monthly Service Fee

The work carried out under this Statement of Work shall be delivered on the basis of a fixed Monthly Service Fee. This fee covers all costs associated with delivery of the services, including personnel, management, tools, overheads, and travel as defined in this SOW.

Monthly Fixed Fee: 85% of the Monthly Service Fee, payable upon acceptance of the services delivered during the applicable reporting period.

Monthly Performance-Based Fee: 15% of the Monthly Service Fee, subject to performance assessment against the applicable KPIs defined in Section 4.1 and adjusted through the application of Service Credits in accordance with Section 4.3.

5.2 Payment Adjustment

The monthly payment shall be subject to adjustment based on the Contractor's KPI performance. Payable Monthly Performance-Based Fee = Monthly Performance-Based Fee minus Service Credit Value. Final Payment = Monthly Fixed Fee + Payable Monthly Performance-Based Fee.

5.2.1 Invoicing

The Contractor shall submit invoices on a monthly basis in arrears. Each invoice shall: correspond to the services delivered during the relevant calendar month; include the applicable monthly service fee; clearly identify any applicable Service Credits; and be supported by the Service Performance Report for the same period.

5.2.2 Acceptance of Services

Payment of the monthly invoice shall be subject to: delivery of services in accordance with this Statement of Work; submission of the Service Performance Report; and validation of KPI performance and Service Credit calculations.

6. ROLES AND RESPONSIBILITIES

NIMSC-EMO Head: Main stakeholder. Responsible for overseeing service performance, validating KPI outcomes, and confirming monthly acceptance of services and deliverables based on the agreed performance framework.

Contractor: Responsible for delivering all services and outputs in accordance with the defined KPIs, performance standards, and acceptance criteria. Also responsible for ensuring continuous compliance with KPI targets and timely corrective actions where required.

7. SCHEDULE

This task order will be active immediately after signing of the contract by both parties. The BASE period of performance shall commence as soon as possible but not later than 29 June 2026 (tentative) and will end no later than 31 December 2026. If the annual options are exercised, the period of performance is 1 January to 31 December of the relevant year (2027 or 2028).

8. SECURITY

Performance of the services requires a valid NATO SECRET Personal Security Clearance. The Contractor shall ensure that all Contractor staff or anyone working under the remit of the Contractor requiring recurring access to on-site locations hold a valid NATO Personal Security Clearance at least to the NATO SECRET level.

9. CONSTRAINTS

All documentation provided under this statement of work will be based on NCIA templates and/or agreed with the NCIA NIMSC-EMO Head or their delegated representative. All developed solutions, tools, and code under this project will be the property of the NCIA.

10. TRAVEL

The contractor will develop deliverables 60% at their own premises and 40% at the NCIA NIMSC-EMO office in Braine-l'Alleud. This location is expected to be vacated during 2027, with the place of performance transitioning to Brussels or Mons, Belgium depending on operational requirements.

The contractor must travel to NATO sites once a month to one of the NIMSC-EMO locations in Wesel (Germany), Grazzanise (Italy), Brunssum (Netherlands), or Bydgoszcz (Poland), related to deliveries within this SOW. Such travel is at the contractor's expense and included in the deliverable price.

Extraordinary Travel (Purchaser Directed Travel) may be required to other NCIA/NIMSC-EMO locations as necessary. In such cases, the cost of all travel and subsistence will be addressed through a contract amendment and reimbursed in accordance with Article 5.5 of AAS+ Framework Contract. All travel arrangements are the responsibility of the contractor.

11. REQUIRED QUALIFICATIONS

[See Requirements]

12. PRACTICAL ARRANGEMENTS

Working environment is 60% off-site at contractor's premises and 40% on-site support at NCIA premises in Braine-l'Alleud as required. The contractor will provide services under an NCI Agency contract issued through the Prime AAS.

In the event that the contractor filling the profile leaves during the contract period, the Prime AAS shall provide a single replacement candidate who meets the required qualifications (Section 11) for the relevant profile. The replacement candidate shall be dedicated to the same profile. All NCIA Terms and Conditions apply.

NCIA hours of operations: Monday to Thursday 08:30–17:00 and Friday 08:30–15:00 (CET). NCIA official holiday schedules for the locations specified in Section 10 apply and will be provided to the contractor.

The Contractor shall furnish everything required to perform the contract, except for access to necessary tools, data, and NATO networks, which will be provided by NCIA subject to Agency policies, security authorization, and coordination.

Requirements

SECURITY

• Performance of the services requires a valid NATO SECRET Personal Security Clearance. The Contractor shall ensure that all Contractor staff or anyone working under the remit of the Contractor requiring recurring access to on-site locations hold a valid NATO Personal Security Clearance at least to the NATO SECRET level.

REQUIREMENTS

Technical Qualifications

• MSc degree in Data Engineering, Systems Engineering, Cybersecurity, or Defence Technology; or BSc degree in Data Engineering, Computer Science, Information Systems, Systems Engineering, or a related technical field. Exceptionally, the lack of a university degree may be compensated by at least 6 years of extensive and progressive expertise in duties related to the function of the post.
• ITIL Foundation certification of completion or certificate (highly valued within NCIA service management frameworks).
• Certificate of completion or certificate in ServiceNow Administrator.
• Certificate of completion or certificate in Functional Principles of Oracle ERP-EBS and SaaS (SCM).
• Certificate of completion or certificate in Power BI.
• 7 or more years of experience in data engineering, data architecture, or lifecycle data management.
• Strong proficiency in SQL, Python, and distributed data processing frameworks (e.g., Spark, Kafka).
• Strong proficiency in ETL/ELT development, data modelling, metadata management, and data quality frameworks.
• Strong proficiency in integrating data from CMDBs, logistics systems, ERP platforms, and OEM lifecycle sources.
• Experience with obsolescence-related datasets (EOL/EOS, vendor roadmaps, supply chain risk indicators).
• Familiarity with CIS architectures, configuration management, and interoperability standards.
• Minimum 2 years of experience working in NATO, NCIA, defence, military, or multinational secure CIS environments.
• Demonstrated ability to work under strict cybersecurity, accreditation, and information assurance constraints.
• At least 2 years of experience using a data orchestration tool such as KNIME or equivalent.
• At least 2 years of experience in advanced data visualization such as Power BI Desktop or equivalent.
• At least 2 years of experience using data architecture: SQL.
• At least 2 years of experience using ServiceNow and Enterprise Business Applications (EBA).
• Fluent in Business English.

Professional Qualifications

• Ability to translate complex lifecycle and configuration data into actionable obsolescence insights for senior stakeholders.
• Excellent communication skills and comfort working in a multinational, multi-stakeholder environment.
• Proactive, structured, and detail-oriented approach to managing complex data ecosystems supporting mission-critical CIS.