HMCTS Reform - Civil, Family and Tribunal Services – Tribunals Jurisdiction

Description

Summary of the work Flexible, outcome based Managed Service, meeting outcomes to timescales, budget and government service standards, delivering digital services to users of Tribunal services including development and live running of Beta services. Will include transition to new supplier and staged transition into business as usual as projects complete. Expected Contract Length 24 months with option to extend for further 25% as per DOS terms. Latest start date Friday 20 August 2021 Budget Range The budget range of the contract is approximately £5m to £5.5m for the term of the contract. Budget ranges for the extension period will be agreed if required. HMCTS does not guarantee volume or duration of work for the winning bidder. Pricing will be evaluated out of 40% and pricing submission documents will be issued to suppliers who pass Round 1. Suppliers will be evaluated as per DOS criteria. The initial Statement-of-Work and Roadmap is available upon request from HMCTSCommissioningandCommercial@justice.gov.uk. It is recommended that interested parties request this document. Why the Work is Being Done The HMCTS Reform Programme is responsible for delivering the future HMCTS operating model through a portfolio of programmes aimed at delivering pioneering judicial services that better serve the public. The Reform Programme includes modernising the court estate, utilising the latest technology to digitise services where appropriate, speeding up and streamlining working practices, refurbishing buildings to reduce maintenance costs and providing much improved services for users, especially vulnerable witnesses and victims. The Reform Programme includes the CFT Programme, which aims, with its partners, to transform the Civil, Family and Tribunals jurisdictions through the design and delivery of new digital services. These digital services are being developed within a coherent architecture which maximises reuse, and to support the resolution of Civil, Family and Tribunal cases fairly and speedily, providing new routes to justice that fulfil the ambition of an ‘online court’. HMCTS is seeking a managed service provider to ensure that high quality digital services are developed for the Tribunals Jurisdiction that are simple, easy to use and meet the government service standard. The managed service provider will be responsible for delivering the outcomes as specified in the contract and Statement of Work (SOW). Problem to Be Solved The deliverables are categorised by the following: • Development of digital services for external users in line with user research, service designs and requirements. • Development of back end systems in line with service design and business requirements. • Integration with Programme Common Components for wider Programme functionality. • Live operations support, bug fix and product enhancement. • Handover to BAU. Position of Tribunal Projects: • Immigration and Asylum – Legal Representative digital service is in Public Beta, BAILS MVP has not yet commenced, design in place. Appellants in person has been paused in Private Beta. • Immigration and Asylum – integration with Home Office systems. • Social Security and Child Support – citizens digital service is in Public Beta. • Employment and Special Tribunals – initial discovery work completed. • Immigration and Asylum will take on Work Allocation, which is included in scope for CFT and will be taken forward for this contract. The delivery timeframes by project: • Immigration and Asylum – Closure March 2022 • Social Security and Child Support – Closure December 2021 • Employment Tribunals –closure August 2022 • Special Tribunals –closure March 2023 • Work Allocation – closure across CFT March 2022. Who Are the Users • Appellants in Person/Citizens –These infrequent users are typically experiencing major life events such as appealing decisions by organisations about immigration, asylum and benefits, are bringing an employment tribunal case or similar. • External professionals - such as solicitors, intermediaries and other legal representatives acting on behalf of their clients, local authorities or government departments. • Internal HMCTS staff – such as case workers, customer contact centre support workers, legal operations, finance, administration. • Judicial users – such as judges and their staff. • Other Government Departments (OGDs) Early Market Engagement None Work Already Done The CFT Programme has been running for several years and has delivered improvements to the legal process for all users. The digital services are being developed with a common capability approach; building common features and components once for all services, using a consistent design system, sharing understanding of users and their needs, maximising reuse of design patterns and reducing duplication of design effort. Some projects are in public beta stage whereas some are yet to commence and are only at the design stage. More details will be made available at Stage 2. Existing Team The current development is supplied by one external supplier supported by other CFT based suppliers for UX, QA and Architecture services which will remain separate. It is the intention not to award contracts for the upcoming CFT QA and Architecture procurements to a supplier who is providing services to a CFT Jurisdiction. The team consists of management functions and developers but the exact make up and numbers will be decided by the bidders. Current Phase Not applicable Skills & Experience • Experience of delivering complex transformation programmes, working in multi-supplier teams, managing cross-stream/ team dependencies, and planning with agile teams to articulate detailed delivery plans in 3-6-month blocks (SAFE planning). • Experience of business requirements analysis, epic priority and user story development. • Experience in implementing software using the following development practices and processes; Behaviour-driven development (BDD) and Test-driven development (TDD). • Experience of building and maintaining code with a cloud-based infrastructure (e.g. Azure) using supportive technologies (e.g. Kubernetes). • Experience with full stack tech products such as - front-end (.Node JS, HTML5, CSS3, SASS, Javascript), back-end (SQL, Java, Java Message Service and Apache ActiveMQ), database (Postgres, Redis, NoSQL). • Experience of working with a complex microservices/platform environments integrating with common capabilities to provide an end to end business experience. • Technical expertise in integration technology (API's, protocols and standards), particularly developing and maintaining micro-services architectures - such as RESTful APIs using JAX-RS and messaging using JMS. • Experience of agile testing/QA strategies and automation including Building unit and e2e: eg Jasmine, Karma, Protractor, Webdriver, Sourcelabs, Codecept, Mocha, Chai, WebDriver, Sinon.js, SuperTest, CucumberJVM, Gatling, Pa11y. • Expertise operating DevOps and continuous integration/ deployment principles such as Jenkins, Kubernetes, Ansible/Terraform, virtualisation for developing, e.g. Docker, Vagrant to build dev VMs proficiency. • Ability to scale up development teams quickly to meet requirements, e.g. scaling to deliver through private and public beta. • Ability to work with other teams developing common components for reuse: how they communicate requirements and work with those teams to ensure consistency and commonality in delivery. • Demonstrable understanding of applying appropriate security controls within a complex digital transformation. Nice to Haves • Experience of working in highly regulated environments with high transaction volumes. • Experience of working with workflow integration engines e.g. Camunda. • Experience of working on large volume API integrations with a multi supplier/ market model. • Experience of working on platform as a service (PaaS) e.g. Azure Cloud Native Platform • Experience of working as a team to pass GDS assessments or similar for external services including preparing and presenting work for assessment panels. • Demonstrate experience of knowledge transfer to the buyer’s organisation to build permanent back-end capability including user guides and training. Work Location Primarily London and remote working (post pandemic) Working Arrangments HMCTS services are built to government service standards using a Scaled Agile Framework (SAFe) essential. SoWs will be issued to define the development outcomes of each project phase and typically span three to six months. For any work performed at a non-base location and outside London (outside of the M25), all reasonable travel and expenses costs shall be met in accordance with the rates set out in the MoJ travel and subsistence policy. All expenses will require prior approval from HMCTS before being reimbursed. Security Clearance All supplier resources must have a Baseline Personnel Security Check (BPSS) which must be dated within three months of the start date. Any development work that requires access to production areas within HMCTS IT systems will require SC clearance which the supplier should provide. For further guidance see: https://www.gov.uk/government/publications/government-baseline-personnel-security-standard Additional T&Cs The initial Statement-of-Work (SOW) will be Capped Time & Materials but the Buyer reserves the right to use alternative payment mechanisms such as Fixed-Price, Incremental Fixed Price or Time & Materials for future SOWs. Suppliers shall provide transparency on the rates paid to resources and third-parties in the supply-chain on request enabling full visibility of charges and costs including overheads and profit-margin in an auditable form. There will be a 4-week transition period working in conjunction with existing service providers. HMCTS Reform use a monthly project performance dashboard to measure Supplier performance and to agree rectification plans where appropriate. No. of Suppliers to Evaluate 5 Proposal Criteria • Please explain how you would deliver the outcomes for this service including previous examples. (8%) • Please give an example of where you have previously approached transition from an existing supplier to minimise disruption to the project. (5%) • Please detail your approach to the leading and owning of such a project on a managed service basis to ensure an effective and efficient delivery, incorporating previous cases. (8%) • Please outline your approach, with examples, to implementing software using the following development practices and processes - Behaviour-driven development (BDD) and Test-driven development (TDD). (4%) • State your approach, with examples, to the handing over of live services to buyer teams and other supplier teams –developing buyer capability and capacity and maintaining an exit strategy (5%) • Outline how you approach working with other teams developing common components for reuse including how you communicate requirements, and work with those teams to ensure consistency and commonality in delivery(8%) • Please outline lessons learnt from previous managed service contracts that you would utilise in this contract. (5%) • Please explain how you plan to sustain pricing within changing market conditions and how the proposal offers value-for-money for HMCTS. (8%) • Please provide evidence of communication skills, working with all stakeholders, gathering and interpreting feedback and communicating to technical/non-technical audiences. (4%) Cultural Fit Criteria • Describe your approach for working with multi-vendor and client teams across multiple projects at different locations with examples. (2%) • Explain how you would develop and share good practice and processes, including how you would support HMCTS to develop its in-house capabilities. Use previous examples. (2%) • Please explain how you will ensure collaboration at all levels of delivery between users, team members, and management. Give examples of how you will maximise the value from collaboration.(1%) Payment Approach Capped time and materials Evaluation Weighting Technical competence 55% Cultural fit 5% Price 40% Questions from Suppliers 1. Who is the incumbent supplier? HMCTS will not be advising the name of the incumbent supplier. 2. Who is the incumbent supplier? HMCTS will not be advising the name of the incumbent supplier. 3. Hello. Is the incumbent provider bidding for this opportunity and/or are they eligible to do so? As the closing date is Friday 18th June, it would be helpful if this question could be answered prior to Thursday 17th. Thanks. The incumbent supplier may bid on this procurement if they choose to do so. 4. What type of role titles to you envisage needing? As HMCTS are procuring a managed service, it would be the supplier's responsibility to determine job roles. 5. is it possible to get the weighting/points for each of the essential and nice to have questions? There are no weightings or points on the Essential or Nice to have criteria. They are scored using the Digital Marketplace scoring table. 6. Is there a SFIA rate cap on roles? HMCTS is seeking a managed service supplier who will decide the types and number of roles to meet the outcomes in the contract and the SOW. However, as an indication only to assist Bidders in their responses, target rates for this contract are in the region of £750-800 for a SFIA Grade 6, £550 for SFIA Grade 5 and £450 for SFIA grade 4. This is not an exhaustive list and Bidders will need to establish for themselves the roles and SFIA levels required. 7. Are there maximum day rates that apply to this opportunity? HMCTS is seeking a managed service supplier who will decide the types and number of roles to meet the outcomes in the contract and the SOW. However, as an indication only to assist Bidders in their responses, target rates for this contract are in the region of £750-800 for a SFIA Grade 6, £550 for SFIA Grade 5 and £450 for SFIA grade 4. This is not an exhaustive list and Bidders will need to establish for themselves the roles and SFIA levels required. 8. For the question, “Extensive experience of working with a complex microservices/platform environments integrating with common capabilities to provide an end to end business experience.”, can you provide some examples of Common Capabilities? Two examples of common capabilities are on line fee and pay functionality and new scheduling and listing functionality. 9. Why cannot incumbent be named? Isn’t digital marketplace about being open ? HMCTS does not see how disclosing the current incumbent supplier would be beneficial to the procurement process.