Home Office

Home Office IPT Programme Caseworking and DPM Delivery Partner

Incomplete applications

0
Incomplete applications

Completed applications

29
Completed applications
13 SME, 16 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Friday 29 July 2016
Deadline for asking questions Friday 5 August 2016 at 11:59pm GMT
Closing date for applications Friday 12 August 2016 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work Software delivery and on-going maintenance of the services delivered by major agile projects with the goal of replacing legacy systems by building a new extensible and reusable framework to meet the needs of immigration and asylum claims within UK Visas and Immigration (UKVI).
Latest start date 30th November 2016 (plus or mins 1 Month)
Expected contract length 2 years
Location London
Organisation the work is for Home Office
Budget range

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The Immigration Platform Technologies (IPT) Programme has supplier partners delivering its Caseworking and Data Platform and Migration (DP&M) projects. These are major agile projects with the goal of building a new extensible and reusable framework to meet the needs of immigration and asylum claims within UK Visas and Immigration (UKVI). As a result of delivering the framework a number of business critical legacy systems will be replaced. Supplier partners are accountable for the software delivery and ongoing maintenance of the services delivered by these projects through provision of Scrum Teams.
Problem to be solved The Programme is building services to transform the way the Home Office (HO) manages immigration into the United Kingdom. Its key deliverables include:
• The core Case working system used by Home Office staff, which replaces the existing ASYS, BRP, CID, ICW and PBS systems that collectively support several thousand concurrent users, and mange decision making on hundreds of thousands of Immigration and Visa cases per year
• Configurable technology modules tailored to a specific business service need
• Automation of existing manual, paper-based processes and supported decision-making to drive consistency
Who the users are and what they need to do As a UKVI caseworker I need to be able to:
• Resolve the identities of individuals applying for Visa and Immigration products
• Manage information about individuals and their cases
• Perform and record the outcomes of checks, including calculations, for example to assess whether a threshold in the Points Based System is met
• Record decisions made about cases and the fulfilment of those decisions – eg to provide a Visa, or provide Asylum Support

So that I can ensure applications are completed within agreed SLAs.
Early market engagement Some market engagement has been done within the Home Office, Cabinet Office and with CCS
Any work that’s already been done Components are in different stages of delivery, there are a number of live services, further releases are also in development, and others are in discovery. As such, the Project has identified or established:
• Key business stakeholders, SMEs, and engaged them
• Conducted User Research and Business Analysis and established detailed business architecture for the release in progress, and high-level architecture for the next release
• A micro-services architectural design, aligned to Programme standards
• Established environments and the delivery toolsets to build the new system
• A delivery team
• Built and tested the foundation shared services / micro-services
Existing team There are a number of suppliers working within the Caseworking Project, elsewhere in the Programme and that support systems that the Caseworking system will integrate with, all of which the new supplier will need to work collaboratively with. Some of the main suppliers are:
• 6 Point 6 Ltd
• Atos
• Deloitte Digital
• HP
• IBM
• Mastek
• NETbuilder / QA
• PA Consulting
• Transform
Current phase Not applicable

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place London
165 Fleet Street London EC4A 2AE
Metro Point Croydon CR0 2EU
Working arrangements The supplier will be expected to be co-located with the customer with the option for near shore and/or offshore working.
The incumbent suppliers have delivered code for the current release. The new supplier will need to gain an understanding of the existing solution to be able to provide support and bug fixes if required and to ensure that future developments are compatible with the current solution.
It is important to note that the Programme retains the right to place resources into a Scrum Delivery Team from other suppliers where a supplier or resource has a particular strength.
Security clearance Supplier personnel need to be compliant with BPSS (Baseline Personnel Security Standard) as a minimum.
Depending on the nature of the role, individuals requiring access to production or production-like environments must already hold or be capable of achieving SC clearance.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions Team sizes up to 8 Teams:
1xDelivery Manager (Scrum Master), 5xDevelopers (at least 1 must be a senior developer), 2xDevelopers to support live service, 1xWeb Operations (DevOps),
Additional, capabilities: Developers for the front-end/User Interface of web applications, Designers (Front-end Design and Interaction Design), Researcher (User Research-UX Design), Quality Assurance Analysts (Test Engineers and Test Analysts), Business Analysts. Pricing - suppliers must provide a Rate Card all the roles above
Bids must be on T & M basis however, SoW different pricing models ranging from FP, T&M or Capped T&M may be used. See Q&A for further info

Skills and experience

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

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • Experience in use of the technologies (see the Q&A for further information) used to build the current Solution 8%
  • Experience in bespoke software application development of browser based software 8%
  • Experience in using agile delivery methodologies including Scrum, Continuous Delivery and Agile at Scale 8%
  • Experience in bug resolution across the delivery lifecycle and in Live support 8%
  • Experience of infrastructure and web operations for the design, setup and running of large scale browser based, RESTful micro-services in the Cloud 8%
  • Experience of successful collaborative working as part of a multi-supplier delivery team 8%
  • Experience of release planning with agile delivery teams to articulate detailed delivery plans e.g. in 3-6 month blocks 8%
  • Experience of scaling processes and approach to meet challenging needs such as complex integration with legacy systems, and complex data migration from legacy systems 8%
  • Experience of managing dependencies between Scrum Delivery Teams within the project and supporting the management of dependencies external to the Project 8%
Nice-to-have skills and experience
  • Experience of front end design and development 3.5%
  • Experience of Integration design 3.5%
  • Experience of User Researcher and UX Design 3.5%
  • Experience of Exploratory testing and test automation 3.5%
  • Experience of Business analysis and Business Design 3.5%
  • Leadership in Agile adoption in large organisations 3.5%
  • Ability to deploy teams off-site and, potentially, off-shore 3.5%
  • Provision of documentation associated with the delivery 3.5%

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 6
Proposal criteria
  • Availability of suitable resources from the required date 5%
  • Whether the proposed delivery team includes any subcontractors or partnered resources 5%
  • Capability of standing up the team from the contract award date 5%
  • Ability to deploy the team onsite at the Customer’s location (or appropriate near-shore / off-shore location) 5%
  • Ability to adopt the technical solution developed so far and methodology, gain a detailed understanding to allow ongoing support and further development, where applicable enhance the solution and methodology 5%
  • Reference track record 5%
  • Willingness to align with the Programme Approach (for example the Definition of Done, the Test Strategy, the Release Planning Approach etc.), but to offer opportunities for improvements were identified5%
  • Team structure and organisational makeup 5%
  • Identification of risks and dependencies that might impact deliver-ability of the Project, and suggested approaches to manage them 5%
  • Value for money / Competitive whole life costs 5%
Cultural fit criteria
  • Work as a team with our organisation and other suppliers 4%
  • Transparent and collaborative when making decisions 4%
  • Have a no-blame culture and encourage people to learn from their mistakes 4%
  • Application of Agile Principles 4%
  • Ability to add value 4%
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Presentation
Evaluation weighting

Technical competence

50%

Cultural fit

20%

Price

30%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Given the size of this piece of work, please could you provide a briefing or any additional background information This is an initial process to short-list potential suppliers for the Delivery Partner requirement. Following the short listing process against the essential and, if necessary, nice-to-have requirements, more information will be provided to the short-listed suppliers under appropriate obligations of confidentiality.
2. If we choose not to bid for this procurement, will we be precluded from bidding from future IPT procurements? No. We will not preclude suppliers who choose not to bid for this procurement from bidding for future IPT procurements. On the contrary, we expect most suppliers will choose to bid for some parts of IPT and not for others. We expect IPT to have multiple contracts with a number of different suppliers.
3. Will the Home Office pay expenses for supplier office space being made available? No
4. By what method will the authority down select interested suppliers in order to identify the five suppliers to take forward for further evaluation? IPT is following the DOS assessment process for short listing. Following the short listing process against the essential and then nice-to-have skills and experience. If there are still more than 5 suppliers, we will request evidence to support the short listing process prior to the further evaluation stage.
5. Are you able to provide further information about future projects to be procured under this IPT programme? The IPT Programme continues to conduct market engagement activity to determine how it can best meet its requirements, and reach out to the supply market. The Programme will continue to publish opportunities through different procurement routes, which may include Digital Marketplace, when they arise. Also please see response to question 1 regarding further information.
6. What are the time-frames and steps for the procurement up to and including contract award? Specifically, when will suppliers be notified of their progression to the next round, and what are the intended timings for this next phase? Time-scales for the next step depend upon the outcome of the initial process step, described in the answer to question 4. If a further step is required bidders will have one week to provide evidence. Evaluation of this evidence will take in the region of one week. Following this we will issue the documentation to short list bidders for the next stage; and anticipate in the region of 28 calendar days for responses.
7. What information do you require by the closing date for applications? When will you be releasing the full tender documents and what are the associated time-scales? The information that can be provided by the closing date for applications is determined by the Digital Marketplace tool. The information that can be submitted is the email address of your contact for this opportunity, a series of yes/no responses to questions and when you could start work. See answer to question 4 for further information.
8. The evaluation contains a weighting of 20% against cultural fit; please define what you mean by 'cultural fit' Please see the cultural fit criteria on our requirements under ‘How Suppliers will be Evaluated’
9. Where work is detailed as already done are you able to share whether external support was provided to the Authority, i.e. Is there an incumbent supplier? Yes, there are a number of suppliers that have been, and continue to be supporting delivery including:
• HP
• Mastek
• PA Consulting
• Tranform
. QA
10. Does the Authority anticipate if the supplier is expected to co-locate, and would all require co-location from Contract Start, or if there would be a 'ramp-up' in the team size? Co-location is preferable, but we will consider near-shore and off-shore offerings. As part of the evaluation we will seek to understand the proposed ramp up and transition plans as it is expected that not all suppliers bidding will be able to resource a number of teams immediately.
11. Assuming more than 6 suppliers meet the criteria when would the Authority expect to issue the skills, experience and evidence document to suppliers? We will evaluate the response to the initial stage the by 19/8/16 and expect, to issue the evidence template to prospective bidders by the (19/8/16).
12. When completing the skills, experience and evidence document, does the Authority intend to request suppliers to provide evidence for the specific people who will be doing the work? At this stage we expect bidders to provide evidence based on their organisational capability
13. Are the written proposal and case studies likely to be issued by the Authority together or separately and if separately what are the timelines for each? There will be a single requirements pack issued to the short-listed bidders. This will include details of what is expected in terms of proposal and case studies.
14. Are each of the Yes/No responses scored equally and can the Authority confirm it is looking for a single supplier who can provision capability in all 9 question areas? There are 9 Essential Skills & Experience points and 8 Nice-to-have Skills & Experience points. The shortlisting is based upon the Essential points first and if there are more than the maximum bidders to be taken forward to the next stage, the Nice-to-have points are then evaluated. All Essential requirements are weighted equally at the Yes/No stage. As part of this procurement, we will award to a single supplier. We reserve the right as part of a non-exclusive award to also subsequently obtain certain services from other routes.
15. Does the Authority expect to award to more than 1 supplier and if so how many? As part of this procurement, we will award to a single supplier. We reserve the right as part of a non-exclusive award to also subsequently obtain certain services from other routes.
16. Can a Supplier state Yes to any of the mandatory select questions if their offering on the DOS framework is currently No, but they can provide suitable evidence of that capability? For example a Supplier may have said No to User Research on their framework submission but now has the capability to offer it for this opportunity. Your answer should be in the context of this requirement and relates to your organisational capability. This is an outcomes (Lot 1) call off. Any bids you may have made relating to other Lots within the overall DOS Framework have no bearing.
17. In Phase the work is currently in, you’ve indicated ‘N/A’, can you explain why this is the case please As above, different components are in different stages of delivery so the project is simultaneously in Live operation of some components delivering Alpha/Beta releases of new components and Discovery of future releases yet to star development.
18. In Essential skills and experience, the first criterion mentions the technologies used to build the current Solution, what are they? Our technology stack includes: Java, Spring MVC, JBoss RESTEasy, Jackson (FasterXML), Spring DI (Spring Core), Google Guice, jmustache, Tomcat, PostgreSQL, HBase, Hibernate, Junit, Mockito, Easymock, Powermock, SLF4J, Logback, Maven, Swagger, Selenium, jsoup, RESTEasy Client, and Jackson provider.
19. Does the Authority have any additional information on Security Clearance? Individuals will not be allowed access to systems until it has been confirmed that they hold the appropriate level of security clearance. Many systems only require BPSS, others will require SC.”. A minimum of two resources per team must be capable of achieving SC clearance.

Suppliers shall ensure that all systems are operated in such a manner to support Home Office compliance with: HMG Security Policy Framework located at http://www.cabinetoffice.gov.uk/resource-library/security-policy-framework
20. Can the Authority provide an example of team sizes? Expected team sizes.
Up to 8 Scrum Teams each comprising of:
• 1 x Delivery Manager (Scrum Master)
• 5 x Developers (of which at least 1 must be a senior developer)
• 2 x Developers to support live service
• 1 x Web Operations (DevOps)

Additionally, suppliers must also be able to provide the following Capabilities to supplement the Programme if required:
• Developers for the front-end/User Interface of web applications
• Designers (Front-end Design and Interaction Design)
• Researcher (User Research - UX Design)
• Quality Assurance Analysts (Test Engineers and Test Analysts)
Business Analysts
21. Will the Authority only use one pricing methodology at SoW level? For pricing submission, suppliers need to provide a cost that includes all the roles identified in question 20

Bids must be priced on a Capped T & M basis however bidders must note due to the nature of the project the Authority may raise scope of work with different pricing models ranging from Fixed Price, T & M or Capped T &M
22. The deadline for asking questions and the closing date for applications have been stated as Friday 5 August 2016 and Friday 12 August 2016 respectively. Could you please confirm the cut-off time for both these dates. The deadline on both dates Friday 5 August 2016 and Friday 12 August 2016 respectively will be 5 pm.
23. Will we need to provide evidence of where we have scaled to have 8 concurrent scrum teams previously in order to be down-selected? Supplier who meet all of the essential criteria outlined in this notice will be required to provide evidence of their experience in the next phases.
24. Please confirm the expected contract length. Expected contract length is upto 2 years.
25. Is there an existing Scaled Agile (SAFe) approach with release trains identified along with the appropriate Release Train Engineers, Product Managers and System Architects/Engineers?

Or would the Delivery Partner be expected to provide this?
Yes we have an approach.

We have RTEs, Product Managers / Product Owners and Architects
26. Do the Agile teams use KanBan or Scrum as their primary methodology? Scrum is the primary methodology
27. Do the delivery toolsets support Continuous Integration and Continuous Delivery (CI/CD)? Yes
28. Can you share details on the CI/CD pipelines that have been established? At this time No, Bidders are only required to confirm they meet the essential criteria

We unable to upload diagrams in this space.

We have a number of tools including Git, Jenkins, Puppet and Ansable.

The primary artefact that we deploy are RPMs deployed onto VMs. We are migrating to containers (docker) for the majority of our services. We expect to have moved to this model by Q4 2016.
29. Have the environments and the delivery toolsets to build the new system been implemented? Yes
30. Some market engagement has been done. Are you able to estimate how much market engagement will be required from the DP? None
31. How will knowledge transfer to the Delivery Partner be achieved?

Do you expect the supplier resource required to effect this to be costed into the proposal?
We aim to onboard suppliers in the weeks prior to a Programme Increment (PI) Planning Event. We identify components to be given to each team. Prior to PI Planning the team will perform spikes to understand the component(s) they are taking on. With an opportunity to work with the discovery team to understand the release that they will be planning out in PI Planning. During PI planning the team will take the stories assigned to them that relates to a component, elaborate the stories and estimate them. The phases described above are T&M and should be costed in your proposal.
32. As part of the working arrangements (in the section ‘Work Setup’) how will you be able to assess progress and performance of a supplier if some of the teams are mixed? Our architects, BAs, Release Train Engineer and PM will all work with the teams during on boarding / planning to help the new team understand the next release the component(s) they are taking on. While doing this these resources will have a view as to whether there are capability / performance issues in the team. If these are apparent we will discuss with the Scrum Master and / or escalate as appropriate.
33. You say that ‘components are in different stages of delivery’. Does this mean that some could be behind plan and need remedial attention? Not necessarily. We work on releases in parallel. Not all components are needed for all releases – hence they can be at different stages of delivery.
It is possible that a component may have issues. We would highlight this to you if there were issues. You will also be given the opportunity during on boarding to perform spike on components to understand them.
Any remedial actions would need to be included in PI Planning.
34. Will the Home Office be supplying the Info Sec oversight? Yes including a ITHC prior to a release.