Validation and Project 1 requirements baseline:

- Receive the documents prepared to date (BRD v3.0 Volumes 1 and 2, the readiness assessmentreport and the executive presentation) and review them against the Ministry s as-is situation its current HR processes and practices, organizational structures, existing systems (including the electronic employee census, staffing tables, electronic contracts and referrals systems) and data, and the governing legislation (including Law No. 12 of 2010 and its executive regulations, Cabinet Decree No. 86 of 2021 and Circular No. 3 of 2026 on appointment and contracting) and against its to-be situation, i.e. the target processes and operating model agreed with the MoCS.

- Select and prioritize (e.g. MoSCoW) the BRD flows that form the Project 1 scope, and document the scope boundary and exclusions (national roll-out, salary scales, payroll calculation, and external interfaces not yet approved).

- Prepare Arabic summaries of the BRD domains within the Project 1 scope, to enable review by MoCS process owners.

- Classify the decisions left open in the BRD for the Project 1 scope the competent authority (CFG-AUTH), thresholds and time limits (CFG-THRESHOLD) and the pending items of the design decision register (DDR-02) into (i) decisions that affect the scope, price or design of the solution and must be settled before the RFP is issued, and (ii)

configuration values that the vendor will implementas configurable parameters, to be decided by the MoCS during implementation before they are configured. Record both groups in a configuration decisions log.

- Resolve with the MoCS, for the Project 1 scope, the decisions in the first group and the other items left open in the BRD, including:o Decisions affecting scope, price or design, including the in-scope processes, integrations, data migration volume and hosting arrangements o The Libyan legal instruments to be referenced, and the initial content of the legislative

o The mapping of the accountable offices proposed in the BRD to existing MoCS and entityorganizational units

o Differences between the BRD release plan (Foundation, R1 R4) and the three-project scope (e.g. vetting, delegation, workforce planning, attendance and data quality)

- Complete the cross-cutting requirements for Project 1:

o Hosting on the central server provided under the programme, and the site, network and continuity readiness to be provided by the MoCS

o Security, role-based access control, audit trail, and personal data protection

o Arabic right-to-left interface, availability, performance, backup and recovery

o Integration with attendance devices, and provisions for future integration with national systems (civil registry, Ministry of Finance, Central Bank of Libya)

- Define the data migration and cleansing requirements for the pilot: source systems (including theelectronic employee census system), the employee files and contracts in scope, validation, cleansing and reconciliation rules, and the cut-over approach.

- Update the BRD documents as needed to reflect the results of the as-is and to-be review, the decisions taken with the MoCS and the comments received correcting, completing, adding or removing requirements, flows and business rules, and adding the applicable legal references

while maintaining version control and a change log recording each modification and itsjustification.

- Facilitate review sessions with the MoCS process owners and a validation workshop; consolidate comments in a comments matrix, correct the documents accordingly, and obtain the formal sign- off of the MoCS on the Project 1 requirements baseline.

- Produce a Project 1 Requirements Traceability Matrix (RTM) linking each requirement to its BRD flow, legal basis and acceptance test.

b. Prepare the RFP technical package

- Draft the vendor Terms of Reference / Statement of Work: objectives, scope, delivery approach and phases, respective roles of UNDP, the MoCS and the vendor, deliverables, milestones and timeline.

- Prepare the technical specifications and a requirements compliance matrix in which bidders state, for each requirement, whether it is met through standard functionality, configuration or customization, or is not met.

- Define the acceptance and testing framework, building on the BRD s standard acceptance tests (normal path, state transitions, audit, right-to-left interface, privacy and security), and covering system integration testing, user acceptance testing and data migration reconciliation.

- Specify the technical contractual provisions: ownership of source code, configuration and data; documentation; knowledge transfer and handover; warranty, support and service levels; information security and personal data protection; and exit arrangements.

- Propose deliverable-based payment milestones tied to acceptance, the required profiles of the vendor team, and a financial proposal template.

- Prepare the technical evaluation criteria and scoring grid, scripted demonstration or proof-of- concept scenarios drawn from priority BRD flows, and a procurement risk register.

c. Support the procurement process

- Provide technical inputs to our client in line with its procurement rules, including participation in the pre-bid conference and the drafting of technical responses to bidders requests for clarification.

- Support the technical evaluation as a technical adviser, including the review of bidders compliance matrices and the conduct of scripted demonstrations, and contribute technical inputs to the evaluation report.

- Support the finalization of the vendor s statement of work, implementation plan and acceptance criteria before contract signature.

- Prepare a final assignment report with a handover note that would allow the MoCS, or another expert, to follow up on the implementation.

Desired Candidate Profile

Key competencies

Thorough knowledge of human resource business processes and HRMIS good practices (position management, establishment control, payroll integration).

Ability to critically review, correct and complete large requirements documents prepared by others.

Ability to translate business requirements into technical specifications, compliance matrices and testable acceptance criteria.

Knowledge of the procurement procedures of international organizations (our client, World Bank or similar) for information systems.

Sound knowledge of software testing and user acceptance testing methodologies.

Proficiency with project, requirements and test management tools (e.g. Jira/Confluence, MS Project, Enterprise Architect or similar).

Excellent analytical and structured writing skills.

Experience in working and collaborating with governments, and ability to deal with multi-stakeholder groups.

Excellent facilitation and communication skills.

Demonstrates integrity and fairness by modelling United Nations values and ethical standards.

Demonstrates professional competence and is conscientious and efficient in meeting commitments, observing deadlines, and achieving results.

High sense of relational skills, including cultural, gender, religion, race, nationality and age sensitivity and adaptability, with a demonstrated ability to
work in a multidisciplinary team.

Knowledge of the Libyan civil service legal and institutional framework.

Familiarity with interoperability standards, data protection and information security principles.

Experience working with our client or other international organizations.

Knowledge of agile delivery methods and of the Libyan IT services market.