PPRO/004/009/040 - Renewable Transport Fuel Obligation (RTFO) System Development

Tender description

Why the Work is Being Done The Renewable Transport Fuel Obligation (RTFO) Operating System (ROS) needs amendment to implement required legislative changes, both to the existing RTFO (due by September, via the RTFO Order) and also to introduce a new greenhouse gas (GHG) mechanism (by January 2018, via the GHG Emissions Reporting Regulations). Problem to Be Solved The current system, which runs the RTFO scheme, (ROS) needs amendment to incorporate changes to the RTFO to introduce new categories of certificates issued, traded and used for compliance, as well as targets and limits on their use. Additionally a new GHG scheme needs implementing (new system build), to issue credits that can be traded and used for compliance. Issuance will primarily be based upon ROS data, though some GHG credit types will use data entered directly. The supplier should indicate how they plan to implement a cost-effective, timely, Agile development (ROS currently has no continuous integration or automated tests). Who Are the Users The users are members of the RTFO Unit at DfT, who use the system to check applications from suppliers and grant certificates if fuel meets the necessary criteria, as well as fuel suppliers who enter data and verifiers who upload assurance reports, which provide evidence for DfT to check applications, and traders who transfer certificates to other users. DfT users need to check suppliers’ compliance with new legislative requirements, targets and limits, and issue certificates and GHG credits where compliant. Current and new non-DfT users need to enter and upload required data and reports, and transfer certificates and credits. Early Market Engagement N/A Work Already Done A Discovery Phase has been carried out to understand user needs and scope options for development. Full details of the output from Discovery will be made available to the successful supplier. Existing Team There is an existing core team of three individuals, comprising a delivery lead (20% of time), a delivery manager (75% of time) and a product owner/ business representative (25% of time). N.B As part of their submission the supplier will need to provide an additional business analyst to oversee the development, reporting directly to the DfT business team and acting as an interface with the development team to communicate user / business needs and prioritise work. Current Phase Alpha Work Location The development needs to take place in bidder’s offices using their IT infrastructure for development and test. The production environment will be DfT hosting / cloud based. However, as part of the development / deployment, the supplier may need to spend some time working in DfT’s office (Great Minster House, 33 Horseferry Road, London SW1P 4DR). Working Arrangments The project needs to be developed to required timescales, the supplier should propose how to resource the project to best meet these milestones. DfT staff work normal office hours, it is expected that the supplier will fit in with these hours with regard to interactions they need to have with the staff. The team for Alpha delivery will need to work 5 days a week for 6-8 weeks. Any expenses incurred will need to be evidenced and paid in accordance with DfT rates. Security Clearance As a minimum, suppliers will have BPSS clearance in place for each team member identified in their proposal. Suppliers will be required to evidence this as part of their submission. Additional T&Cs Skills & Experience Demonstrable experience of Microsoft stack (Windows 7 and 10) Demonstrable experience of Windows server / SQL server 2012 Demonstrable experience of Internet Information Services (IIS) Demonstrable experience of .Net version 4 Demonstrable experience of Crystal reports version 11 Proven experience of Agile project delivery Demonstrable evidence of meeting Government security requirements, i.e. Cyber Security standards Nice to Haves Demonstrable experience of utilising Open source technologies to affect change. Demonstrable experience in utilising Cloud technologies Proven experience of delivering upgrade of complex IT systems Proven experience of delivering new systems development Demonstrable evidence of a robust Risk management process, including risk identification, mitigations and governance No. of Suppliers to Evaluate 6 Proposal Criteria Technical solution Approach and Testing methodology / strategy How the approach or solution meets Government Digital Service requirements Estimated timeframes for the work How they’ve identified risks and dependencies and offered approaches to manage them Team structure Value for money Cultural Fit Criteria Experience of working as a team with our organisation and other suppliers, adjusting their approach to meet the needs of the organisation Experience of transparent and collaborative decision making Experience of taking responsibility for their work and resolving problems effectively Experience of sharing knowledge and skills with other team members at both local and Departmental level Payment Approach Capped time and materials Assessment Method Written proposal Case study Reference Presentation Evaluation Weighting Technical competence 60% Cultural fit 20% Price 20% Questions from Suppliers Budget range £250,000-£450,000 for alpha delivery and ros system enhancements. the supplier shall provide a combined overall price for all phases of delivery through alpha, beta and into live, noting that alpha is capped at £450,000.£250,000-£450,000 for alpha delivery and ros system enhancements. the supplier shall provide a combined overall price for all phases of delivery through alpha, beta and into live, noting that alpha is capped at £450,000.