NHS Health Education England

Trainee Information System (TIS) Core Services delivery

Incomplete applications

Incomplete applications
8 SME, 4 large

Completed applications

Completed applications
7 SME, 2 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Thursday 16 February 2017
Deadline for asking questions Thursday 23 February 2017 at 11:59pm GMT
Closing date for applications Thursday 2 March 2017 at 11:59pm GMT


Opportunity attribute name Opportunity attribute value
Summary of the work The required outcome is delivering an Alpha and Beta (Note: requirement says Beta due to DOS portal limitations) of the TIS Core, including: Microservices and complementing User Interfaces, a granular security model, integrations with HEE HR/recruitment systems, data migration from existing Trainee Management systems, capability/knowledge transfer to HEE delivery teams.
Latest start date 15/03/2017
Expected contract length Six months as a guide and bidders are welcome to propose others describing how they would do so
Location No specific location, eg they can work remotely
Organisation the work is for NHS Health Education England
Budget range

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done HEE’s primary role is to manage the training and development of NHS clinical workforce trainees which includes dentists, doctors, healthcare scientists and pharmacy learners
HEE is developing a replacement of its existing legacy systems under a programme called TIS.
Problem to be solved Improved data reliability/availability, vfm and convergence of business process harmonisation, a reduced number of IS systems.
Specifically through the Delivery of Alpha and Beta phases of the TIS Core services, which will include:
Microservices and complementing User Interfaces for Core entities including People, Programmes, Posts and Placements
Security model to support appropriate granular access to these entities
Integrations with HEE systems for HR/Recruitment.
Data migration from existing systems.
As a service under the GDS definition it is also important to HEE that the permanent team develops the knowledge/capability to support and extend TIS Core services through active collaboration during delivery.
Who the users are and what they need to do The end users of the system will be HEE core staff – administrators, clinical and academic – and clinicians in training
Early market engagement
Any work that’s already been done The Solution Architecture, Cloud Hosting, DevOps, User Centred Design and Agile processes elements of the wider TIS eco-system have been established and proven through the delivery of an initial selection of TIS Services into Live with a limited internal user base.
The current activities include scaling out the existing Live services, Discovery and Alpha activities on new services and transitioning the model to permanent HEE team members.
Discovery for the Core Services is nearing completion including an object model, interface definitions and underlying data structures.
Existing team TIS have an existing Delivery team including Service Managers, Product Owners, Delivery Manager, Technical Architects, Lead Dev, Service Designer and User Researcher/BA.
We expect the successful bidder to collaborate with the HEE team on designing the proposed service, sharing knowledge and building internal capabilities.
The existing team will be based at HEE – Stewart House, Russell Square, WC1N 5DN.
Current phase Beta

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place To be proposed by the supplier
Working arrangements The supplier should propose their preferred working arrangements to deliver the outcome.
The TIS Programme is using Agile practices including fortnightly sprints and daily standups.
The existing delivery team will be based at HEE – Stewart House, Russell Square, WC1N 5DN.
End user are based across England in HEE Regional Offices.
Security clearance

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions

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
  • Demonstrable experience of projects that include blended, multi-discipline, multi-vendor team environments focused on meeting user needs using agile methodologies and delivering digital improvement outcomes.
  • Demonstrable experience of projects that have successfully delivered high transaction digital services to national organisations in complex and highly regulated environments.
  • Demonstrable experience of projects with successful User Research, User Experience, and Content Design to deliver ongoing user needs throughout a product lifecycle.
  • Demonstrable experience of projects with successful software development using open-source Full-Stack products – front-end coding (AngularJS, JavaScript, Bootstrap) and back-end coding (Java 8, Spring Boot), using BDD and TDD.
  • Demonstrable experience of projects that have successfully implemented integration technology (API's, protocols, open standards and open source), particularly developing and maintaining microservice architectures.
  • Demonstrable experience of projects with successful agile testing strategies and automation and in specific testing tools and methodology (Cucumber, JUnit, Mockito, JMeter).
  • Demonstrable experience of projects with successful utilisation of cloud vendor technologies and tools (e.g Azure)
  • Demonstrable experience of practices that enable safe, sustainable releases into live production, mitigating risk to existing operations
  • Demonstrable experience of projects with successful transition of in-progress/working/live services to a client’s user and delivery teams, e.g. developing capability and capacity in addition to providing knowledge transfer.
Nice-to-have skills and experience
  • Demonstrable experience of projects for three or more digital by default government services with high transaction volumes (100k p/a) and meeting digital by default service standard criteria.
  • Demonstrable experience of projects with rapid and effective deployments of a multi-discipline team able to fulfil the required outcomes

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 4
Proposal criteria
  • Overall Solution and Approach - High Level Delivery Plan, Approach and Method, Timescales, Risks and Dependencies and Quality
  • Proposed team structure (including roles and example CVs of typical resources)
  • Approach to collaborating with HEE and knowledge and capability transfer into HEE permanent teams
  • Value for Money - how the proposal will optimise costs and generate savings
Cultural fit criteria
  • Demonstrable experience of projects with high levels of daily collaboration with client teams for Digital Service delivery including both knowledge and capability transfer to the purchaser’s teams
  • Demonstrable experience and understanding of the NHS mission and Aims
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Please would you clarify the steps of this procurement process? Are you simply looking for the shortlisting information responses and latest start date by the closing date for applications, or do you require additional material from prospective suppliers by that date? Bidders will be required to submit their shortlisting responses to the criteria listed in the requirements via the DOS portal prior to the closing date for applications. In the event we are unable to shortlist to 4 suppliers we will ask suppliers to provide up to 3 case studies within 5 working days (a template will be provided). The 4 suppliers that make the final sift will be required to submit a written proposal followed by a presentation.
2. Your requirements says that 5 bidders will be evaluated. But Question 1 says 4? How many suppliers will you evaluate? My error - it was a miskey. It should be 4. We will short-list and evaluate 4 bidders
3. Q: The service that has been taken to live – has this been built by an in-house team or by a supplier? Thanks The service that has been taken to Beta Live was built by a joint team of HEE staff and HEE's Digital Delivery Partner, Engine Partners LLP (Transform).
4. You have asked in some questions for evidence for "projects" but the DOS guidance says "You should only provide one example for each essential or nice-to-have requirement (unless the buyer specifies otherwise)." can you confirm you are looking for depth as well as specific evidence? We are interested in depth which is why we are considering three case studies as a further shortlisting stage. If we can't shortlist four bidders on the initial answers submitted via the DOS portal we will ask for the three case studies at the second stage. We agree 100 words makes it challenging to refer to multiple projects. So will accept a single project as evidence at the initial stage. If bidders wish to provide more than one they may do so - but we won't score a bidder down on the basis that they have given only one example.
5. Your requirements mention AngularJS, JavaScript, Bootstrap, Java 8, and Spring Boot. Are these actual technology requirements, or just examples of the sorts of technologies you were expecting to use? Will alternative technologies be considered? The aim is to work in alignment with the Government Service Design Manual and responses should describe how bidders will assure this over-riding requirement. HEE will need to support and further develop the core services internally. Therefore technology use must conform to our current TIS stack outlined.
6. You mention Azure. Is the system going to be deployed in the public cloud? Yes. Azure platform is already deployed.
7. Hi, please can you advise how many people you envisage requiring on this project and if possible can you break it down via job role? You mention a total of 4 bidders but there is no mention of how many individuals you potentially require? The number of team members offered and the breakdown of job rolea in your bid is up to you.
8. Could NHS Health Education England share the Discovery outputs? We will share the Discovery Outputs with the framework suppliers shortlisted for the evaluation stage.
9. Please can you advise what the total budget for this work will be? We have decided not to divulge our budget for this work.
10. With respect to AngularJS, are you considering Angular2 We are considering options with regard to Angular 2.x based on the need to support historical browsers across the NHS.
11. Could you tell us your interpretation of the term "Capped Time and Materials"? Some organisations have seen it as a cap to prevent costs spiralling out of control. Some have defined it as a cap to costs but still expect full delivery of a fixed scope project even if they have under-estimated the time required. This answer is based directly on information on the DOS portal. A capped time and materials approach is the same as a time and materials approach but there’s a limit on how much the client has to pay for the work. If the contract reaches the limit before the work is finished, the supplier has to complete the work at their own cost. If the supplier finishes the work before they said they would, you only pay them for the time they took to do the work.
12. Further to the information provided for the opportunity and the webinar, we anticipate that the team would consist of a Delivery Manager, Business Analyst, and Developers. Can you confirm that there is a team consisting of DevOps and Technical Architects in place who will be available to support the collaborative effort? Broadly we are happy to confirm but qualify this by emphasising that the successful bidder will be responsible for co-ordinating with the existing team using agile methodology and progressing from Alpha to Beta and Live in line with optimum GSDM assessment regime. We also agree that the bidder would provide BA expertise. Bidders must be clear on how they will deal with these issues, bring in (and release) contractor digital specialists at the appropriate time and take responsibility for optimum progress in an agile manner, working with the existing TIS Delivery Team.
13. Where can I see the Q and A Webinar? The link to the recording has been placed in Sharepoint link given with the Q and A details on the suppliers' portal.