Ministry of Justice

System Integration Services

25 Incomplete applications

19 SME, 6 large

0 Completed applications

Important dates

Published
Monday 20 June 2022
Deadline for asking questions
Monday 27 June 2022 at 11:59pm GMT
Closing date for applications
Monday 4 July 2022 at 11:59pm GMT

Overview

Off-payroll (IR35) determination
Contracted out service: the off-payroll rules do not apply
Summary of the work
Build a consistent set of long-lived interfaces that expose data from HMPPS systems in a coherent and consistent way.
Latest start date
Friday 28 October 2022
Expected contract length
2 years
Location
No specific location, for example they can work remotely
Organisation the work is for
Ministry of Justice
Budget range
£2m including VAT

About the work

Why the work is being done
The MOJ has a bold strategic vision for the delivery of digital, data & technology in Her Majesty's Prison and Probation Service (HMPPS) which includes:
● Deliver digital prison services that replace legacy systems and support rehabilitation
● Build strong digital & technology capability

As part of this there is a clear need to build a consistent set of long-lived interfaces that expose data from HMPPS systems in a coherent and consistent way.
Problem to be solved
The MOJ has data about prisoners and probationers that comes from many different systems (in particular, NOMIS, nDelius, OASys, PPUD). Many of these systems hold data about the same individuals but using different structures. The MOJ is also planning on replacing at least one of these systems over the next few years. HMPPS Digital has a number of existing APIs and message queues that expose data, but many of these are tied to legacy systems and data models.

The MOJ needs to deliver a set of new interfaces that will provide data from HMPPS systems in a way that abstracts the above difficulties away from the consumers of the interfaces. We require a managed service team to continue defining the high-level data requirements, investigate the technical requirements and constraints, develop a consistent approach in line with our architectural standards and technical governance, and develop a service to meet both the long term needs of HMPPS Digital and the identified needs of data consumers. The new interfaces are likely to consist of two parts: a set of person-focussed APIs, and a set of queue-based domain events.
Who the users are and what they need to do
The actual users will be using the resulting services not directly but via other systems: where we have limited scope for change. For this requirement, we should instead consider the system to system integration
Early market engagement
N/A
Any work that’s already been done
Some initial high-level data requirements have been defined and discussions have taken place with an external organisation. We have some technical standards, but not a complete set
Existing team
There will likely be a need to work closely with existing development teams within HMPPS Digital, but this will be a new team managed by the supplier.
Current phase
Not started

Work setup

Address where the work will take place
Working remotely although occasional travel may be required to either:
- 102 Petty France, London SW1H 9AJ
- Sheffield Digital Studio, Greenfield House, 32 Scotland Street, Sheffield, S3 7DQ
Working arrangements
The majority of work can be completed remotely i.e. homeworking. However, there may be a requirement to work with MoJ Digital or business stakeholders who are predominantly based in London and Sheffield or to visit users at HMPPS locations.
Security clearance
SC clearance is required

Additional information

Additional terms and conditions
This is a technical piece of work and will likely not go through the same kind of Alpha, Beta, etc. phases as a user-facing service would normally go through

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Essential skills and experience
  • 1. Proven track record of delivering digital services through agile methods, and defining and meeting non-functional requirements
  • 2. Demonstrable capabilities in Kotlin development within an AWS environment
  • 3. Proven experience and expertise in collaborating across teams and departments
  • 4. Experience of delivering technology services, including APIs and transferring ownership to in-house teams
Nice-to-have skills and experience
  • 1. Experience within the probation and prison environment
  • 2. Knowledge of technical and security standards
  • 3. Cyber Essentials Plus accreditation

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

How many suppliers to evaluate
4
Proposal criteria
  • A recent and relevant case study of a similar project explaining your approach and methodology and how it ensured successful delivery. This should include how the delivery met non-functional requirements
  • Explain your approach and methodology for successfully creating and maintaining live digital products
  • Provide an example team structure including skills, experience, responsibilities, and relevance of individuals, and explain how you will ensure the team successfully delivers the required outcomes
  • Explain your exit strategy to successfully handover to an internal team at the end of the contract.
  • Provide a project plan for what your team would deliver during the timescales
Cultural fit criteria
  • 1. Is responsive to the needs of the team and organisation shaping and adjusting teams to ensure the optimum performance and cohesion
  • 1. Is responsive to the needs of the team and organisation shaping and adjusting teams to ensure the optimum performance and cohesion
  • 3. Encourages new entries to their digital professions and upskills and develops their workforce
  • 4. Encourages diverse representation in their workforce
Payment approach
Capped time and materials
Additional assessment methods
Presentation
Evaluation weighting

Technical competence

70%

Cultural fit

10%

Price

20%

Questions asked by suppliers

1. Can you share the “high-level data requirements have been defined”?
Information regarding data requirements will be released at the start of phase 2 to short-listed suppliers.

Log in to ask a question