This opportunity was cancelled

The buyer cancelled this opportunity, for example because they no longer have the budget. They may publish an updated version later.
Transformation Peer Group (Cabinet Office)

WP1339 Government Transformation Map

12 Incomplete applications

8 SME, 4 large

13 Completed applications

9 SME, 4 large

Important dates

Monday 13 March 2017
Deadline for asking questions
Monday 20 March 2017 at 11:59pm GMT
Closing date for applications
Monday 27 March 2017 at 11:59pm GMT


Summary of the work
Develop a dynamic mapping tool of government transformation strategy across government, highlighting dependancies and programme information.
Latest start date
28th April 2017
Expected contract length
2 Months (Until the beginning of July 2017)
Organisation the work is for
Transformation Peer Group (Cabinet Office)
Budget range

About the work

Why the work is being done
The Transformation Peer Group (TPG) has been commissioned to map transformation programmes across government. This will take the form of a digital tool that Civil Servants can access to see dependancies and other data about programmes. A public beta of the tool should be ready for early June 2017.
Problem to be solved
Departments cannot currently see how their programme relates to other programmes across government. This in turn leads to activities being duplicated across government.
Departments cannot see how other programmes depend upon them, leading to poor decisions for the whole of government being taken.
Ministers cannot see how their department has to work with other departments to achieve their priorities. This leads to resourcing being improperly allocated across the department. Treasury cannot plan cross government programmes as they cannot not see how these programmes fit into wider government transformation.
Who the users are and what they need to do
As someone involved in a programme, I need to see projects/programmes who we have a dependancy on, so that the collaboration can be managed.
As a SRO, I need to see where a programme's critical dependancies are, so that risks can be managed and prioritised.
As a Programme director, I need to see which programmes have similar outcomes to mine, so that I can see if we should be working together.
As a Senior Civil Servant, I need to see how my department is currently working with other departments, So that I understand how best to manage the relationship.
Early market engagement
Any work that’s already been done
A Proof of Concept has already been done and a screenshot of the work can be viewed here:
Existing team
The supplier will be expected to work with a Non Technical policy team for 3 civil servants.
Current phase

Work setup

Address where the work will take place
Westminster, London
Working arrangements
Working offsite 5 days a week (mon-fri) roughly 9am-5pm, with daily check in calls with the team, and face-to-face meetings at the request of the supplier (roughly 1 per week)
Security clearance
BPSS Security cleared

Additional information

Additional terms and conditions
Standard Cabinet Office terms and conditions will apply

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
  • Have experience designing over 5 services using data to extract value and insight with ease.
  • Have over 5 years professional experience delivering at pace with tight fixed deadlines.
  • Proven successful development of back-end technologies, databases, developing APIs, meeting data standards, and experience of GitHub.
  • Over 3 medium size projects (3-6 months each) worth of experience with front end data visualisation such as data mapping and/or dependancy mapping.
  • Have 4 years of experience developing open source products.
  • Demonstrate experience of delivering agile projects in sometimes non-agile environments for at least 2 projects.
  • 5 years of technical expertise of front-end, UI web development and responsive web design (HTML5/CSS/JS).
  • 5 years of experience of prototyping, testing and iterating with users and stakeholders.
  • 3 years proven experience in using robust metrics, analytics, search data and user feedback to audit and define key content and services.
Nice-to-have skills and experience
  • At least 1 project of experience of delivering services designed for internal government use.
  • At least 3 projects worth of experience of building a dependancy mapping project, programmes, organisations or services.
  • At least 3 projects worth of experience scrapping data from a variety of data sources, programmes and organisations.

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • Technical solution
  • Approach and methodology
  • How the approach or solution meets your organisation’s policy or goal
  • Estimated timeframes for the work
  • Value for money
Cultural fit criteria
  • Work as a team with our organisation and other stakeholders.
  • Transparent and collaborative when making decisions.
  • Have a no-blame culture and encourage people to learn from their mistakes.
  • Be able to deliver even with uncertainty surrounding the programme.
  • Can work with clients with low technical expertise.
  • How they’ve identified risks and dependencies and offered approaches to manage them.
  • Be transparent and collaborative when making decisions.
Payment approach
Fixed price
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Please advise what is the 'fixed price' of this project?
At this stage we would like to engage with the market in order to understand the range available.
2. Please advise what is the 'fixed price' of this project?
At this stage we would like to engage with the market in order to understand the range available.
3. Will tenders be accepted that include an existing solution that is capable of delivering the desired functionality?
We would welcome proposals from existing solutions. However in our initial research no solution met all of our needs.
4. This opportunity looks very similar to the Transformation Peer Group (Cabinet Office) WP1304 - Transformation Map Requirements opportunity posted last month. Are you able to provide a reason why the last procurement was unsuccessful?
WP1304 was withdrawn due to some internal milestones not being met and has been republished as WP1339.
5. Are you looking just for the services of a consultant to work on the existing mapping tool or the provision of an overall solution?
We would be looking for the development of a overall solution, which builds upon the early discovery and proof of concept work done already.
6. We have tried to access the Drive to review the screen shot and submitted a request for permission. Please grant us the access for the same asap.
The link should now allow everyone to see it.
7. Has a product based solution been considered?
We have conducted market research to try and find an off the shelf solution. So far we have not found one but would be interested if a supplier had one to offer or tailor to our needs
8. Has the PoC established any technology choices or approaches that have now become mandates for the project proper? For instance, visualisation libraries, JavaScript frameworks etc., that the supplier would need to incorporate into their own technical approach?
No technical architecture has been agreed, however an open source approach would be preferred so further development could be done later if required.
9. Is it only the front-end visualisation and service integration for the mapping tool that are in scope for delivery, or is the design and build of the various services that provide the data also part of the scope?
We are commissioning for both front end and back end elements. This means that the supplier will need to deliver the system to manage and edit the data as well as the front end visualisation and service integration. Gathering the data will be done by the team of civil servants and maintained via face to face meetings in the future.
10. Are any services that power the mapping tool already developed? If so, what form do these take? E.g. API endpoints, file consumption etc?
The proof of concept reads the existing data from a google spreadsheet and then visualises this.
11. Is the application for desktop only, or does it need to be mobile-first/responsive? If so, what are the browsers/devices/operating systems that the application needs to comply with?
The map will be primarily for laptop and desktop use. But should be able to be used on tablet. We feel a mobile would not be the best device to visualise this data, but are happy for a supplier to design an interface for this if they felt it added value.
12. Does the application need to conform to any accessibility guidelines?
Yes, we would expect it to meet the GOV.UK Service Manual Accessibility elements
13. Will the supplier be working within an established environmental topology? For instance, will the Cabinet Office provision development, QA, UAT environments etc? Will we be using your version control software? Do you already have an established continuous integration and deployment process?
No they will not, but we do expect the supplier to implement sufficient version control and environments to enable the us to review work done.
14. Will the supplier be working alongside, inheriting from or handing over to any other technical parties, including internal Cabinet Office teams? If so, what are the expected separation of concerns?
They will be inheriting some work done in discovery by an internal team. This includes some data, a proof of concept and a report for future development
15. What project methodology is preferred (e.g. Agile Scrum)?
Some form of agile methodology would be preferred.
16. Assume that the engagement needs to be delivered in an agile model who will perform the user acceptance testing and what would be the collaboration model?
The development team would be expected to conduct research with civil servants with a member of the client team supporting. Final user acceptance will be done with the client team at the end of the project. All collaboration with government departments will be done with the client team's involvement.
17. Can the results of the private beta service assessment be shared, if any?
We do not expect this tool to go through a full private beta service assessment.
18. Is there an overall roadmap for the solution envisaged in terms of adoption? What happens after this discovery phase and public beta?
We aim for civil servants to be able to use the tool from June/July 2017 with a effort during the summer of 2017 to ensure the data is as accurate as possible. Beyond that we will hold several events to build usage across government.
19. What is the expected number of users for the solution? and the number of projects / programmes for which the dependencies need to be mapped
We expect the number of nodes to be in the region of 200-300 (estimate and is expected to rise). This consists of 53 major transformation programmes and their dependancies.
20. Are the parameters in the image enclosed an exhaustive set or could there be more parameters linking projects?
We expect the number of parameters to expand beyond the current list with more research and development.
21. Is there a pre-defined User Interface template - w.r.t fonts/ designs etc. that needs to be adhered to?
We would like to tool to follow the GOV.UK Design style with regards to fonts and designs.