2025-0300 Data Entry Assistant (NS) - MON 1 Sep

Deadline Date: Monday 1 September 2025

Requirement: Data Entry Assistant

Location: Braine-l’Alleud, BE

Full Time On-Site: Yes

Time On-Site: 100%

Period of Performance: BASE period: As soon as possible but not later than 29th 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 CO-115786-AAS+ Special Provisions article 6.5.)

Required Security Clearance: NATO SECRET (Please see Paragraph 7 in SOW)

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:

Track open ticket,

Coordinate with stakeholders and technical SME to gain insights in to data

Register data in database following data format convention.

Identify data integrity and gaps, raise tickets for tracking and remediation.

Assign tickets to SMEs.

This SOW covers the data entry of network elements across multiple security domains (NU, NR, MR, MS, NS).

3. 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 contractor`s 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