About this role

BIDDING INSTRUCTIONS Technical Proposal 1. Bidders shall include in the Technical Proposal: a. CV of candidate, focusing on qualifications defined in Section 10 of the Statement of Work. b. Technical execution approach for each deliverable. c. Fixed-price quotation per deliverable (no time-and-materials). d. Resource and schedule plan. e. Description of similar completed projects. f. Assumptions and dependencies, if any.

2. Compliance matrix referring how each candidate meets qualifications listed in Section 10, justified by relevant (project) experience to carry out the work listed in Section 3 of the Statement of Work. Deadline Date: Thursday 17 September 2026 Requirement: APSS ISR Collection Tool Developer Support Location: Off Site Note: Please refer to your Subcontract Agreement, article 6.4.1.a, which states 'Off-Site Discount: 5% (this discount is applicable to all requirements, and applies when the assigned personnel are permitted to work Off-Site, such as at-home)'.

Please be sure to price this discount in your overall price proposal when submitting bids against off-site RFQs. Period of Performance: Base Year 2026: 15 October (tentative) – 31 December. Option Year 2027: 01 January – 31 December. Required Security Clearance: NATO SECRET 1. INTRODUCTION SHAPE and the NCI Agency are jointly delivering the Alliance Persistent Surveillance from Space Programme. This programme serves NATO and the nations and presents an opportunity to enhance and accelerate situational awareness and decision making through a dedicated programme for the access to shared space data and the integration of the data into NATO systems.

Through pioneering the ability of the Alliance to harness space capabilities and deliver operational effect from the Space Domain, this proposal will deliver a step change in the Alliance ability to remain informed through access to Space data. 2. SCOPE OF WORK Under the direction of the NCI Agency, the incumbent will perform duties to include the following: Collection Tool Data Integration: Managing ACO requirements for APSS commercial data integration.

Collection Tool User Interface Management: Supporting ACO requests and investigating/implementing changes to user interface. System Troubleshooting: Investigating and resolving data flow bottlenecks and technical issues in production environments. Collaboration & Documentation: Working with cross-functional teams to define requirements and maintaining documentation for the APSS Collection Tool. 3. DELIVERABLES The contract will be managed through milestone-based deliverables as follows: Deliverable D1: Document Collection Tool status report for Reporting Period 1 (Base Year 2026), covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations.

Acceptance Criteria A1: Accepted periodic report satisfying the KPI and Acceptance Criteria framework set out below. Deliverable D2: Document Collection Tool status report for Reporting Period 2 (Option Year 2027), covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations. Acceptance Criteria A2: Accepted periodic report satisfying the KPI and Acceptance Criteria framework set out below.

Deliverable D3: Document Collection Tool status report for Reporting Period 3 (Option Year 2027), covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations. Acceptance Criteria A3: Accepted periodic report satisfying the KPI and Acceptance Criteria framework set out below. Deliverable D4: Document Collection Tool status report for Reporting Period 4 (Option Year 2027), covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations.

Acceptance Criteria A4: Accepted periodic report satisfying the KPI and Acceptance Criteria framework set out below. Deliverable D5: Document Collection Tool status report for Reporting Period 5 (Option Year 2027), covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations. Acceptance Criteria A5: Accepted periodic report satisfying the KPI and Acceptance Criteria framework set out below.

Deliverable D6: Document Collection Tool status report for Reporting Period 6 (Option Year 2027), covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations. Acceptance Criteria A6: Accepted periodic report satisfying the KPI and Acceptance Criteria framework set out below. Deliverable D7: Document Collection Tool status report for Reporting Period 7 (Option Year 2027), including a consolidated six-period trend assessment, covering operational and technical status; issues arising or handled during the period; service and collection metrics; and risks, actions, and recommendations.

Acceptance Criteria A7: Accepted final periodic report and consolidated six-period analysis satisfying the KPI and Acceptance Criteria framework set out below. Required Content of Each Deliverable (Deliverables D1–D7) Each deliverable shall contain, as a minimum: 1. Executive summary and overall RAG status. 2. Availability and operational status of the Document Collection Tool. 3. Status of its components, interfaces, collectors, repositories, and scheduled jobs.

4. Issues opened, resolved, outstanding, or carried forward during the reporting period. 5. Incident impact, root cause, corrective action, owner, and target resolution date. 6. Collection metrics for the reporting period. 7. Comparison against the previous period and applicable targets. 8. Identified risks, dependencies, constraints, and recommended actions. 9. Traceability to supporting monitoring, ticketing, and collection records.

10. Purchaser decisions or support required. KPIs and Acceptance Criteria (Deliverables D1–D7) Timely Submission: Measurement: Submission date compared with the contractual due date. Target: 100% on time. Acceptance Criteria: Deliverable submitted by the agreed deadline. Reporting-Period Coverage: Measurement: Days covered ÷ total days in the reporting period × 100. Target: 100%. Acceptance Criteria: Entire reporting period is covered, with gaps explicitly explained.

Required-Content Completeness: Measurement: Completed mandatory sections ÷ required sections × 100. Target: 100%. Acceptance Criteria: All required sections and annexes are present and populated. Tool Status Coverage: Measurement: Reported tool components ÷ components in the agreed reporting baseline × 100. Target: 100%. Acceptance Criteria: Status is provided for every agreed component, interface, collector, and scheduled process.

Status Accuracy: Measurement: Correct status records ÷ sampled status records × 100. Target: ≥98%. Acceptance Criteria: Reported status reconciles with monitoring and operational records. Tool Availability Reporting: Measurement: Available service time ÷ scheduled service time × 100. Target: Report actual; target established in SLA. Acceptance Criteria: Availability is calculated correctly, exclusions are identified, and evidence is provided.

Collection-Job Success Rate: Measurement: Successfully completed collection jobs ÷ scheduled collection jobs × 100. Target: ≥98%, unless otherwise agreed. Acceptance Criteria: Successful, failed, retried, and cancelled jobs reconcile to platform records. Document Collection Success Rate: Measurement: Successfully collected documents ÷ documents attempted × 100. Target: ≥98%. Acceptance Criteria: Volumes reconcile with logs; failed and rejected documents are classified.

Processing Success Rate: Measurement: Documents successfully processed or ingested ÷ documents collected × 100. Target: ≥98%. Acceptance Criteria: Processing failures and exclusions are quantified and explained. Collection Timeliness: Measurement: Documents collected within the agreed collection window ÷ documents due for collection × 100. Target: ≥95%. Acceptance Criteria: Delayed collections are identified, quantified, and linked to causes or issues.

Duplicate-Document Rate: Measurement: Duplicate documents detected ÷ documents collected × 100. Target: ≤2%, or agreed baseline. Acceptance Criteria: Duplicate calculation is reproducible and material trends are explained. Error Rate: Measurement: Failed collection or processing transactions ÷ total attempted transactions × 100. Target: ≤2%. Acceptance Criteria: Errors are categorized by source, severity, cause, and corrective action.

Issue-Record Completeness: Measurement: Issues containing required fields ÷ issues recorded during the period × 100. Target: 100%. Acceptance Criteria: Each issue includes identifier, description, severity, dates, impact, owner, status, and target resolution date. Issue Capture Completeness: Measurement: Issues in report ÷ issues in authoritative ticket register × 100. Target: 100%. Acceptance Criteria: All relevant issues opened, active, or closed during the period are included.

Critical/High Issue Notification: Measurement: Critical/high issues notified within contractual notification time ÷ total critical/high issues × 100. Target: 100%. Acceptance Criteria: Evidence demonstrates that all critical/high issues were notified on time. Issue Resolution Performance: Measurement: Issues resolved within applicable SLA ÷ issues due for resolution × 100. Target: ≥95%. Acceptance Criteria: Resolution dates and SLA calculations reconcile with the ticketing system.

Root-Cause Coverage: Measurement: Major or recurring issues with documented root-cause analysis ÷ major or recurring issues requiring analysis × 100. Target: 100%. Acceptance Criteria: Root cause, corrective action, preventive action,

Source listing: himalayas_belgium_p2