2025-0253 Web developer for NATO NISC ID&E NRA -Python/CSS (NS) - THU 21 Aug

Deadline Date: Thursday 21 August 2025

Requirement: Web developer for NATO NISC ID&E NRA Python/CSS

Location: Braine lAlleud BE

Full Time On-Site: Yes

Time On-Site: 100%

Period of Performance: BASE period: As soon as possible but not later than 17th September 2025 31st December 2025

2026 Option: Up to a maximum of 4 sprints (price per sprint will be determined by applying the price adjustment formula as outlined in COAAS Special Provisions article 6.5.)

Required Security Clearance: NATO SECRET

1. INTRODUCTION

NATO Communication and Information Agency (NCIA) provides end-user services to customers throughout NATO. These services are supported by Innovation Deployable & Engineering (ID&E) Naming Registration Authority provided by the NATO Infrastructure Services Centre (NISC) Business Area of NCIA. All services provided by NCIA regardless of whether they are end-user services or supporting services are under the responsibility of Service Delivery Managers (SDM).

The NATO Infrastructure Service Centre (NISC) Business Area Lead (BAL) is accountable for planning and executing the full lifecycle management activities (design transition and operations) for the identified area of responsibility. NISC provides generic domain independent technical functionality that enables and facilitates the operation and use of Information Technology resources. NISC services (including: subject matter expertise; acquisition; project management operations and maintenance; and disposal) are provided in the following technical domains: Network Services (to include routing switching and transmission services) infrastructure hosting storage and processing infrastructure networking HW and SW management databases and web platform services as well as identity management. Services are provided throughout the lifecycle to both internal and external customers in both static and deployable settings.

2. OBJECTIVES

The main objectives of this Statement of Work (SOW) can be summarized as follows:

Ensure high-quality Front end web applications for IP database website (referred to herein as AskNRA)

Build a modular front end website.

Develop and deploy iterative updates to the askNRA front end aligning with evolving business requirements.

Use minimal libraries or packages that are not already in use.

No dependency on 3rd party CDN or online packages.

3. This SOW covers the development of a web front end for IP reporting across multiple security domains (NU NR MR MS NS). SCOPE OF WORK

The following deliverables are expected from this Statement of Work:

1) Complete the activities/tasks agreed in each Sprint meeting as per sections 2 above.

2) Produce sprint completion reports (format: e-mail update) which include details of activities performed. Specifically the front end element worked on frameworks and approaches used maintenance guidelines per element.

3) The Contractor will participate in the weekly reporting and planning activities (weekly face to face) as well as the required participation in workshops events and conferences related to the supported services as requested by the Service Delivery Manager or deputy.

3.1. Support Activities:

3.1.1. Support Weekly Data comparison work (Exception report)

Due to the AGILE approach of this project the specific deliverables and associated acceptance criteria will be defined for each sprint between the NCI Agency and the Contractor in writing based on the activities defined above.

3.2. Sprints Planning Execution and Review:

3.2.1 Sprint Planning:

Objective: Plan the objectives for the upcoming sprint

Kick-off meeting: Conduct a monthly meeting with the Contractor to plan the objectives of upcoming sprints and review contractors manpower to meet the agreed deliverables.

Set sprint goals: Define clear achievable goals for the sprint and associated acceptance criteria including specific delivery targets Quality standards as well as Key Performance Indicators (KPIs) for each task to be recorded in the sprint meeting minutes.

The Contractor needs to be assigned at the beginning of the each sprint to be able to fulfil the agreed activities (i.e. in case there is a requirement for development activities developers need to be assigned to the sprint)

Agree on the required level of effort for the various sprint tasks.

Backlog Review: Review and prioritise the backlog of tasks issues and improvements from previous sprints.

Assess each payment milestone cycle duration of one calendar month. Review and agree the state of completion and validation of each sprint status and sign off sprints to be submitted for payment as covered in Section 4.

3.2.2 Sprint Execution

Objective: Contractor to execute the agreed sprint plans with continuous monitoring and adjustments.

Regular meetings between NCI Agency and the Contractor to review sprint 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 NCI Agency staff instructions.

Continuous improvement: Contractor to establish a continuous feedback loop to gather input from all stakeholders for ongoing improvements and their subsequent implementation depending on NCIA approval.

Progress Tracking: Contractor to use a shared dashboard or tool to track the status of the sprint deliveries and any issues.

Quality Assurance/Quality Check: Contractor shall ensure that the quality standards agreed for the sprint deliverables are maintained throughout the sprint.

Quality Control: NCIA to perform the Final Quality Control of the agreed deliverables and provide feedback on any issues.

3.2.3 Sprint Review

Objective: Review the sprint performance and identify areas for improvement.

At the end of each sprint there will be a meeting between the NCI Agency and the Contractor to review the outcomes against the acceptance criteria comprising sprint goals agreed quality criteria and Key Performance Indicators (KPIs).

Define specific actions to address issues and enhance the next sprint.

3.2.4 Sprint Reporting

For each sprint to be considered as complete and payable the Contractor must report the outcome of their work during the sprint first verbally during the retrospective sprint review meeting and then in writing within three days after the sprints end date. A report must be sent by email to the NCI Agency manager highlighting all work performed against the agreed tasking list set for the sprint.

The Contractors payment for each sprint will be depending upon the achievement of agreed Acceptance Criteria/KPIs for each task defined at the sprint planning stage. This will include specific delivery targets quality standards as well as Key Performance Indicators (KPIs) for each task.

If the Contractor fails to meet the agreed Acceptance criteria for any task the NCI Agency reserves the right to withhold payment for that task/sprint.

4. PAYMENT MILESTONES AND DELIVERABLES

Payment Schedule will be at the end of each sprint of four (4) working weeks following the acceptance of the sprint report.

The NCIA team reserves the possibility to exercise a number of options based on the same scrum deliverable timeframe at a later time depending on the project priorities and requirements.

The payment shall be dependent upon successful acceptance of the sprint report and the Delivery Acceptance Sheet (DAS) (Annex B).

Invoices shall be accompanied with a Delivery Acceptance Sheet (Annex B) signed by the Contractor and the NCIA Point of Contact (POC).

4.1 2025 BASE: 17 September 2025 to 31 December 2025

Payment Milestones: Completion of each milestone will be documented in the Delivery Acceptance Sheet Template (DAS) which will be signed for acceptance by the authorized point of contact and the Contractor.

This document will accompany the invoice.

Number of sprints is calculated considering a starting date 17th September 2025. This will be adjusted based on actual starting date.

5. COORDINATION AND REPORTING

5.1 The content and scope of each sprint will be agreed with the service delivery manager during the sprint-planning meeting in writing.

5.2 Services need to be provided during standard working hours of NCIA (9-17).

5.3 The Contractor shall report to the Line Manager (or deputy).

6. SCHEDULE

This task order will be active immediately after signing of the contract by both parties.

6.1 The BASE period of performance is as soon as possible but not later than 17th September 2025 and will end no later than 31st December 2025

7. SECURITY

7.1 Performance of the services described in this SOW requires a valid NATO SECRET clearance.

7.2 The Contractor SHALL ensure that all the Contractor staff or anyone working under the remit of the Contractor requiring recurring access to on-site locations for the delivery of the services under this SoW have a valid NATO Personal Security Clearance at least to the NATO RESTRICTED level.

8. CONSTRAINTS

8.1 All the documentation provided under this Statement of Work will be based on NCIA templates or agreed with project point of contact

8.2 All scripts documentation and required code will be stored under configuration management and/or in the provided NCIA tools.

8.3 No external dependencies on libraries or packages (not already on the NATO approved software list).

9. PRACTICAL ARRANGEMENTS

9.1 This is a deliverables-based sprints contract.

9.2 The Contractor shall provide services On-site at Location of Performance in Braine-lAlleud (BEL).

9.3 The work will be executed onsite. Remote work cannot be performed offsite NATO entities since the nature and classification of the work requires the Contractor to be present at the office. Exceptionally requests can be agreed on a case by case basis.

9.4 The work depicted in this SOW is to be performed by ONE Contractor.

10. TRAVEL

10.1 There are no requirements to travel to other sites within NATO for completing these exceptional case where travel is needed the following applies:

Travel arrangements will be the responsibility of the contractor and the expenses will be reimbursed in accordance with Article 5.5 of AAS Framework Contract and within the limits of the NCIA Travel Directive.

Annex B: Delivery Acceptance Sheet Template (DAS)

11. QUALIFICATIONS

The consultancy support for this work requires the following qualifications:

Technical Qualifications

At least 4 years progressive experience in web application development roles:

• Proficient in WSGI applications
• Flask
• Jinja2
• Sqlite
• Python
• CSS Bootstrap
• JavaScript
• Flask Blueprints
• JQuery
• Ajax
• Experience and applied knowledge of Python programming
• Proven ability to communicate effectively orally and in writing with good briefing skills
• Strong and open communication skills
• Entrepreneur and strong networking skills
• Autonomous problem-solver and drives towards results

Professional Qualifications

Must have excellent spoken and written English communication and presentation skills as demonstrated by recent experience (within the past 5 years)

Excellent communication skills to effectively interact with users team members and stakeholders

Must demonstrate the ability and self-motivation to work on his/her own but must also work well within groups as part of a team

Must demonstrate an ability and keen sense for problem-solving

Able to work independently with minimal supervision

Knowledge of NATO responsibilities and organization.