Awarded to Cogworx

Start date: Monday 3 February 2020
Value: £1,036,000
Company size: SME
UK Export Finance

Digital Trade Finance Service - Node.js Developer team

18 Incomplete applications

17 SME, 1 large

19 Completed applications

16 SME, 3 large

Important dates

Monday 2 December 2019
Deadline for asking questions
Monday 9 December 2019 at 11:59pm GMT
Closing date for applications
Monday 16 December 2019 at 11:59pm GMT


Summary of the work
A team of node.js Developers to transition the DTFS platform to nodejs from PHP/Drupal and help transform the wider service in an agile project.
Latest start date
Monday 27 January 2020
Expected contract length
2 years with option to extend 6 months
Organisation the work is for
UK Export Finance
Budget range
£800,000 to £1,000,000

About the work

Why the work is being done
UKEF offers a digital service to five partner banks; the Digital Trade Finance Service (DTFS).
A recent third paty audit of DTFS established that the current service does not meet user needs or comply to GDS service standards. To help bring the service into line with service standards and meet accessibility needs we are undertaking a code transformation from the original PHP/Drupal code into node.js. After this the Development team will work as part of a project team to extend and re-architect the wider platform to meet GDS service standards.
Problem to be solved
DTFS is not currently meeting the government’s 14-point Service Standard and will fail any future GDS service assessment.
We need to transfer the current platform from PHP/Drupel to node.js in a continuous manner in order to allow us to take advantage of the GDS design patterns and system and therefore better meet accessibility requirements
Building on this we will also commence a discovery into the wider platform to potentially redesign the service to meet user needs and GDS service standards. This will then lead to Alpha, Beta and a new Live service that has passed the relevant service assessments.
We require a team of developers comprised of a senior developer/Technical architect and 3 node.js developers to undertake both of these projects
Who the users are and what they need to do
Pre-discovery work so far has identified the following users...
Maker (Bank) - Provides export finance to the bank’s customer (exporter) and requests additional cover from UKEF.
Checker (Bank) - Reviews finance deals raised by the maker and approves applications to UKEF.
Underwriter (UKEF) - Reviews a deal request and approves cover.
Inputter (UKEF) - Inputs deal information to internal systems.
Approver (UKEF) - Ensures input data matches the deal.
Post-issue management (UKEF) - point of contact for the banks after the point of issue. Deals with any amendments needed, as well as any general queries.
Risk team member (UKEF) - Makes risk-based decisions on trade finance.
Early market engagement
Any work that’s already been done
We have commissioned research into accessibility and content design of the existing portal.
We commissioned an agency to review DTFS and recommend an approach to take DTFS forward.
Existing team
UKEF have a small existing team of developers and testers. The new development team will work with this team to transition the service to node.js and then maintain the service in an ongoing basis.
A wider project team is being established to start the Discovery of DTFS in the new year, the development team will form part of the multi-disciplined project team working with Service designer, user researchers to build prototypes and code solutions.
Current phase
Not started

Work setup

Address where the work will take place
UK Export Finance. 1 Horse Guards Rd, Westminster, London SW1A 2HQ
Working arrangements
The supplier will work as part of a multi-disciplined matrix team in agile sprints, predominately in our London office
Security clearance
All staff should have minimum CTC level security clearance in place before work is started or be prepared to undergo security clearance process.

Additional information

Additional terms and conditions
Pricing will be based on capped time & materials but the Buyer will reserve the right in the contract to use alternative payment mechanisms e.g. T&M or Fixed Price for future SoWs.

Suppliers will be required to participate in a code test/review as part of the presentation in the 2nd round of the procurement.

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
  • Demonstrate significant experience building, operating and monitoring NodeJS systems in production
  • Demonstrate experience of developing or maintaining services in PHP/Drupel
  • Demonstrate your ability to mentor and train developers in modern JavaScript programming idioms and patterns, and NodeJS good practices
  • As a lead TA Demonstrate your ability to work with business and technology stakeholders to translate business problems into technical designs
  • Demonstrate your experience working as the development team in a a multi-disciplined project team through Discovery, Alpha, Beta and live.
  • Demonstrate your willingness to participate in in-hours support and out-of hours on call rota
Nice-to-have skills and experience
  • Demonstrate experience with HTML/CSS and web accessibility practices
  • Demonstrate experience of Microsoft Azure
  • Demonstrate experience of the GDS design system and patterns
  • Demonstrate experience of working with open source tools and concepts (e.g. github, common government services etc).
  • Demonstrate experience of transforming a service from one coding language to another.
  • Demonstrate experience of test driven design and development

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

How many suppliers to evaluate
Proposal criteria
  • Detail your approach to producing, checking and releasing code to a production environment.
  • Demonstrate your understanding of agile environments, collaboration and DevOps culture, and continuous learning
  • Demonstrate where you have taken the lead in secure web software design and coding practices
  • Explain your approach to translating technical concepts between software engineering, delivery management and service management so they are understood by all.
  • Demonstrate experience with building a CI/CD pipeline
Cultural fit criteria
  • Demonstrate your ability to deliver in an open, collaborate, agile way according to the principles outlined in the Government Service Design Manual
  • Demonstrate how you will build capability within the existing service team
  • Demonstrate your ability to adapt your approach when dealing with blockers
  • Demonstrate your experience collaborating with other suppliers on a project
Payment approach
Capped time and materials
Additional assessment methods
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. In the event of the 6 month optional extension should the potential costs incurred by the supplier be included in the initial costing, or would that be an extra cost of T&M?
In event of an extra 6 months we would expect to negotiate an extended contract with the supplier as extra cost.
2. How many developers does the organisation feel are required for this programme of work please?
4, a lead developer/Technical Architect and 3 other developers
3. We understand this requirement is for a team of node.js Developers to transition the DTFS platform to nodejs from PHP/Drupal and help transform the wider service in an agile project. Could you please let us know if there is an incumbent supplier in place or if this is for a new piece of work?
We have a team of staff developers managing the current DTFS to be replaced by the new team of developers. This is a new piece of work
4. Is there any flexibility on the budget or the timescale for this outcome? The listed budget, start and end dates will restrict the quality of specialists available for this project
We expect the resource profile to change throughout the project lifecycle. It is up to the supplier to propose required resources for each phase.
5. Will remote working patterns be available to the suppliers node.js consultants, for example can they work from the suppliers premises or from home on occasion?
We very much would like the development team to work on-site at UKEF as part of a multi-disciplined agile team.
6. Are the existing team of developers, internal staff or have they been sourced externally?
A mix of internal staff and contractors.
7. What is the timeline on procurement (1st/2nd/Decision phase)?
Publish requirements on the Digital Marketplace 2nd December 2019
Deadline for Round 1 responses 16th December
Request for Proposals sent to shortlisted providers 20th December
Deadline for proposal submissions 10th January 2020
Supplier presentations 14th January
SOW / Contract Meeting 20th January
Contract finalisation and signature 20th – 24th January
Proposed start date 27th January 2020
Please note these dates are indicative and subject to change