SPS-02319 Prisoner Records 2 (PR2) – Technical Change

The contract timeline includes an "Initial Term" of three years from the "Commencement Date". The "Contract Term" is seven years, commencing on the "Go Live Date", which is when the technical change is completed and accepted by the Purchaser.

Key phases and milestones are:

• An "Implementation Period" from the "Commencement Date" to the "Operational Services Commencement Date".
• Migration is expected to be completed within 18 months from "Contract Commencement". [cite: 2 in previous search]
• Specific implementation milestones (Milestone 2, Milestone 3, Milestone 4, Milestone 5) mark the implementation to "Live" of 25%, 50%, 75%, and 100% of the application's scope, respectively. [cite: 1 in previous search]
• Support and maintenance are outlined for Year 1 through Year 7. [cite: 1 in previous search]
• The total duration of any "Extension Periods" beyond the "Initial Term" shall not exceed six years. [cite: 2 in previous search]

The core scope of work for this tender involves the delivery of agreed works, services, and deliverables, as outlined in the Statement of Work (SOW). The SOW is a document that details these aspects to be provided by the Supplier as part of the contract. Additionally, a Statement of Requirements sets out the specific services the Supplier has committed to provide, potentially including service levels.

The core deliverables include:

• Project Governance:
• A detailed project plan, developed in coordination with the Current Provider and the Purchaser.
• A project governance structure, encompassing elements like a schedule of standups, project team meetings, project board, and approval milestones.
• A clear split of roles and responsibilities during development and transition phases.
• Release management, which includes Module Pre-release testing and approval.
• Technical Deliverables:
• Modernised modular application components, with the provision of code to an ESCROW repository accessible by the Purchaser.
• Integration components to enable hybrid operation with the Current System.
• A collaboration and software development management environment (e.g., GitHub or equivalent) to facilitate CI/CD pipelines and DevSecOps workflows.
• Cloud architectural documentation and environment administrative privileges.
• A proposal for the subsequent database cloud migration for approval by the Purchaser, which may include a change of database platform (the cloud migration of the database is not part of the initial migration).
• Proof of the security of the cloud environment and application through an independent PEN test.