Application Platform Services in HM Revenue and Customs' Chief Digital & Information Officer Group

Professional Services for the Multi-channel Digital Tax Platform

Incomplete applications

40
Incomplete applications
32 SME, 8 large

Completed applications

41
Completed applications
30 SME, 11 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Tuesday 1 October 2019
Deadline for asking questions Tuesday 8 October 2019 at 11:59pm GMT
Closing date for applications Tuesday 15 October 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work Building and operating a Continuous Integration-Continuous Delivery (CI-CD) capability in public cloud, currently AWS, using open source technologies.
Latest start date Wednesday 1 January 2020
Expected contract length 2 years maximum
Location South West England
Organisation the work is for Application Platform Services in HM Revenue and Customs' Chief Digital & Information Officer Group
Budget range The anticipated budget is £6m per annum split between 1 – 2 suppliers depending on the result of this DOS exercise.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done We are looking for up to two partners with expertise in building and operating a Continuous Integration-Continuous Delivery (CI-CD) capability in public cloud. MDTP is a Platform-as-a-Service (PaaS) currently hosted in AWS (London Region) and all of HMRC's modern, customer-facing digital services accessed via Gov.uk reside on this platform. MDTP also provides services and dashboards to many thousands of internal staff.

MDTP went live in February 2014 and is always evolving to meet changing user needs. The platform vision and roadmap set out the future direction, centred on continually improving MDTP's usability, operability, security and simplifying the path to Production.
Problem to be solved Maintaining and enhancing MDTP's ability to serve up online content to HMRC's customers, as well as services to internal staff, while ensuring an optimal user experience. Without a performant, secure and highly available platform, HMRC's customers will not be able to access MDTP's constituent services or may suffer a degraded user experience. The successful supplier may be asked to conduct work on various areas of the project simultaneously.
Who the users are and what they need to do As a user of services on tax.service.gov.uk,
I need to interact with HMRC/perform my duties as a HMRC staff member,
So that I can, e.g. file my tax return/monitor any attempted repayment fraud
Early market engagement Bristol supplier day 12th July 2019.
Suppliers may also request a copy of the presentation slides and the Q&A document that followed by emailing andrew.cullenaine@hmrc.gov.uk.
Please note:
1. The Classic Services have been removed
2. Transaction Monitoring is being procured as a separate DOS exercise
Any work that’s already been done MDTP went live in February 2014 and is now in its third major iteration:
2014 - 1 x SME cloud provider
2016 - 2 x SME cloud providers (active-active)
2017 - 1 x hyperscale cloud provider
The platform roadmap envisages MDTP's continued evolution as a cutting edge PaaS, so there is plenty of transformative feature work in addition to the live running aspects.
Existing team HMRC expect the Service Providers to work alongside other suppliers and internal staff, including apprentices, as part of blended teams.
There are six platform teams, typically comprising the following roles:
- infrastructure engineer
- software developer
- QA/tester
- Delivery Lead
- Product Owner
- Business Analyst
Current phase Live

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Bristol - 3 Glass Wharf, BS2 0PS
Secondary location (occasional travel only and only up until the site's planned closure in November 2020): London, Canary Wharf, E14 4PU
Working arrangements The supplier will be required to co-locate with the existing platform teams, mixed teams comprising both internal staff and other contractors, 5 days per week.

Occasional travel may be required to other HMRC Delivery Centres. Expenses will be paid as per agreed contract rates.

We expect the successful supplier to provide upskilling to permanent staff to increase internal capability.
Security clearance Baseline Personnel Security Standard (BPSS) clearance will be needed for all supplier contractors.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions All personnel engaged in the provision of this service must have a minimum of three years experience in their designated role/skill specialism, with an expectation of five years minimum experience for lead roles.

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
  • Provide additional and/or value added activities when acting in the role of a partner supplier to an organisation
  • Translate business problems and user needs into technical designs
  • Proficient at writing code (Scala, Python, Ruby) to solve problems, automating wherever it adds value and incorporating security best practices at all times
  • Hands on experience of various AWS services like Cloudformation, S3, ECS, EC2, RDS, Lambda, SQS, SNS, Stacks and IAM
  • Proponents of test-driven development (TDD) practices, writing top quality unit tests and code
  • Devising and implementing unit/component, integration, system and acceptance tests to meet functional and non-functional requirements
  • Deep understanding of distributed Source Control, preferably git/GitHub
  • Deep understanding of application deployment strategies and Continuous Integration
  • Deep understanding of inter-application communication protocols
  • Deep understanding of navigating and troubleshooting Linux servers
  • Experience of developing, using Terraform, Kubernetes, ELK, Sensu, Clickhouse, MongoDB
Nice-to-have skills and experience Evidence significant, similar contract with a public sector body

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 4
Proposal criteria
  • Earliest start date
  • Providing the relevant skills, roles and resources across a variety of open source technologies
  • Collaborative working with other suppliers and a client's in-house teams, including coaching, mentoring and knowledge sharing
  • Providing additional and/or value added activities when acting in the role of a partner supplier to an organisation
  • Translating business problems and user needs into technical designs
  • Proficient at writing code (e.g. Scala, Python, Ruby) to solve problems, automating wherever it adds value and incorporating security best practices at all times
  • Hands on experience of various AWS services like Cloudformation, S3, ECS, EC2, RDS, Lambda, SQS, SNS, Stacks and IAM
  • Proponents of test-driven development (TDD) practices, writing top quality unit tests and code
  • Devising and implementing unit/component, integration, system and acceptance tests to meet functional and non-functional requirements
  • Practising pair programming and understanding the value of peer review as part of maintaining focus on quality
  • Deep understanding of distributed Source Control, preferably git/GitHub
  • Deep understanding of application deployment strategies and Continuous Integration
  • Deep understanding of inter-application communication protocols
  • Working knowledge of navigating and troubleshooting Linux servers
  • Working knowledge of Terraform, Kubernetes, ELK, Sensu, Clickhouse, MongoDB
  • Working in agile delivery teams within a product-centric environment, and particularly comfortable with kanban
  • Good communicator, having the soft skills to talk to the business as well as techs
  • Teams will have demonstrable DevOps experience, showing ability to release at least every sprint and ideally much more frequently
  • Experience of delivering to Government Digital Standards
  • Significant, similar contract with a public sector body (Desirable)
Cultural fit criteria
  • Operates a no-blame culture, encouraging people to learn from their mistakes
  • Able to start work immediately
  • Have excellent communication skills with staff at all levels of the organisation
  • Will take responsibility for their work while also pairing/peer reviewing by default
  • Willing to collaborate and partner, including with other suppliers and HMRC staff at all levels
  • Proactively share knowledge and experiences with members of team, especially with HMRC staff
  • Be innovative and promote ideas and suggestions as applicable
  • Focus on achieving value for money in all activities
Payment approach Time and materials
Additional assessment methods Presentation
Evaluation weighting

Technical competence

50%

Cultural fit

10%

Price

40%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Who are the current incumbent suppliers? This is not relevant to the DOS requirement and therefore not to be disclosed at this stage.
2. How many supplier staff do you envision having on-site simultaneously? There are no defined numbers at this stage, however it is estimated that awarded suppliers would provide in the region of approximately 20 individuals. The number of individuals will be dependent on the solution proposed by suppliers to deliver individual Statements of Work”.
3. Can you please provide details of any particular roles required immediately . As this is a service contract we do not want to be prescriptive on the roles required. However, it is expected that the types of roles will include Infrastructure Engineer, Delivery Lead, Software Developer, QA/Tester.
4. Is there a current or preferred incumbent for this programme of works please? HMRC currently have other suppliers engaged in ths activity but incumbents receive no preferential treatment or consideration. The successful supplier will be required to work within and alongside teams made up of HMRC and/or other suppliers, dependent upon the proposed solution to the problem.
5. RE your answer to q1, this is extremely relevant as if there is a current incumbent it would tend to make it untenable for further bids to be made as they will, understandably, be preferred? HMRC currently have supplier(s) engaged in this activity, who these suppliers are has no relevance. Any supplier who is registered on the DOS4 framework and with the capability to fulfil the requirement will be able to apply for this opportunity. Shortlisted suppliers will be assessed fairly to find the supplier that best meets our needs.
6. You mention you're looking at '1-2 suppliers' and then go on to mention 'partners' later on. Does that mean you're looking at a joint partnership bid or are you looking at awarding it to the top 2 suppliers at the end of the DOS exercise? Please note we are asking for what your structure / approach to awarding the contract is, so we can consider internally whether to partner up or put in an individual bid. HMRC require a single proposal to deliver all aspects of the requirement. We are not prescriptive, as per the terms of the framework this proposal could come from a consortium of suppliers who come together to deliver (with one lead supplier or a newly formed company, jointly owned by the members of the consortium) or by a single supplier supported by one or more subcontractors. We also welcome bids from suppliers who intend to fulfil 100% of the service through their own capability. Any consortium or subcontractor arrangements must be made clear in the bid information.
7. Does the scope of the work include front end development and UX? MDTP has a very small UI team, maybe two developers, so this would be negligible.
8. What regulations/governance does the current platform fall under? No specific regulation and mostly self-governed. The platform is architected and engineered according to industry and security best practice and all strategic decisions are taken at the local level, unless additional funding is required for something specific. We are only subject to the corporate change management process if we're implementing a major platform change, such as migration from one cloud provider to another (and this is very rare).
9. We would like to understand how many integrations are involved, with what technology and how old that technology is? MDTP connects to legacy back end through a single MDTP egress point in the form of a proxy server with traffic going via a legacy integration/API layer (around 200 APIs) currently using WSO2. This is in the early stages of being replaced by an AWS VPC connecting to MDTP via peering. MDTP is integrated with a modern API Platform serving 3rd party software developers’ needs. There’s a single integration with HMPO through to their DVA service across the PSN and we're reliant upon Government Gateway which MDTP ingrates with in line with all other Government Departments across the public internet.
10. What are the key integration points in the existing estate? We would like to understand how many integrations are involved, with what technology and how old that technology is? As above. It's not possible to give a precise number of integrations but they all exist in the layers described above.
11. Do you have a roadmap for the multichannel digital platform? Can you share this with us? Each team on MDTP will have a backlog of work which is prioritised by the Product Owner of that team. We do take a high level picture of this and combine it with cross-platform priorities to create a roadmap. We do have a snapshot of this roadmap but it can, and will, change considerably with time. We may decide to share the roadmap snapshot at stage 2 if we feel it is relevant.
12. Do you consider this engagement to fall within IR35? This engagement will be operated on a fully contracted out service basis. Therefore, HMRC consider that this contract will be outside of the IR35 legislation.
13. If we have delivered consultants to the public sector but haven't got specific Outcomes based experience with the public sector, will this significantly affect our scoring? Not necessarily if sufficient evidence is provided against the essential criteria. Any supplier who is registered on the DOS4 framework, and with the capability to fulfil the requirement, will be able to apply for this opportunity. Shortlisted suppliers will be assessed fairly to find the supplier that best meets our needs.
14. What are the technical/other internal standards that must be met? MDTP is built and operated according to industry/security best practice. MDTP also goes through an AWS Well Architected review at regular intervals for additional quality control assurance.
15. What is the requirement for support -24x7? There is an out of hours rota with one engineer on at any one time. From experience it takes around six months for someone new to the platform to be ready to do on call.
16. Are there SLA’s that must be met – if so what are they? There are no specific SLAs for MDTP.
17. How many statements of work are envisaged for the total delivery? SoWs run for six weeks at a time but there is no limit, as MDTP is constantly supported and iterated.
18. What are the payment terms? HMRC will pay the supplier within 30 days of receipt of a valid invoice submitted in accordance with the Call-Off Contract.
19. Would you consider a start-up consultancy that, as a business, has no history but that the team (our people) have relevant experience and success across all key areas? Yes, but you will need to provide sufficient evidence against the essential criteria to enable HMRC to evaluate the skills and experience.
20. What are the non-functional requirements and to what degree are these tested and proven? This is too broad a question, other than to say MDTP is a highly available, performant and secure cloud platform, with availability consistently around 99.9+%.
21. What is the performance of the current service? This is too broad a question, other than to say MDTP is a highly available, performant and secure cloud platform, with availability consistently around 99.9+%.
22. Regarding the working arrangements, would HMRC be open to consider support of onsite resources from offshore. The resources onsite will be fully compliant and would own the deliverable, but our question is could onsite resources be supported from offshore. No.
23. Would you be interested in examples from more than one client in the answer to a single question? E.g. We used tool x to do a thing in client a and another thing in client b. Yes.
24. Please share a high level architecture of MDTP platform. We will include a high level architecture diagram for those suppliers shortlisted to provide a written proposal.
25. Please describe your CI-CD pipeline blueprint. Our platform provides a CI-CD pipeline for all service teams. Platform teams will have their own CI-CD pipelines which will differ. For service teams, code changes committed on GitHub.com triggers a build on Jenkins and the resultant compiled code is stored on Artifactory. When deploying, teams can use a pipeline in Jenkins to push the code through all pre-production environments. Deployments to Production are an additional manual step.
26. What technologies do you use for your CI-CD implementation? GitHub.com + Jenkins + Artifactory
27. What are key activities in your MDTP platform 2020 improvement roadmap? Each team on MDTP will have a backlog of work which is prioritised by the Product Owner of that team. We do take a high level picture of this and combine it with cross-platform priorities to create a roadmap. We do have a snapshot of this roadmap but it can, and will, change considerably with time. We may decide to share the roadmap snapshot at stage 2 of this procurement if we feel it is relevant.
28. What are HRMC key applications technology stacks ? On MDTP all microservices are written in Scala + Play, except a small number in Java + Spring.
29. Are your Devops team responsible for AWS Infrastructure management ? Yes, wholly responsible.
30. Do you expect any out of the business hours activities (for example on-call support) ? There is an out of hours rota with one engineer on at any one time. From experience it takes around six months for someone new to the platform to be ready to do on call.
31. The Existing Team section describes 6 existing teams of 6 people each with roles similar to those that we understand are being procured. Are some of those teams the ones to be replaced by the new supplier? The working arrangements implies not, as it requests the supplier to co-locate with existing teams. All teams are blended, so no single team is being replaced in its entirety.
32. For the Nice-to-have evidence there is only a single request. Is that limited to 100-words as usual at stage 1? Yes.
33. The majority of the stage 2 proposal criteria repeat all of the Essential evidence skills. Does this mean that shortlisted suppliers will have to provide further detail on those same topics, or will you only be looking for a proposal around the additional points at stage 2? HMRC will be seeking to test the evidence given against the essential criteria by means of a scenrio based written proposal. Shortlisted suppliers will be required to provide detail on the essetial criteria and the additional proposal criteria in their written proposal.
34. Please can you confirm how you will evaluate the price element at Stage 2? Your response 2 in Q&A indicates that pricing will be based on future individual SOWs. Will the Stage 2 evaluation therefore be based only upon rate-card, as that is unlikely to give a fair comparison of specific outcomes? Or, given that you are looking for specific approaches, will you be proposing various scenarios for suppliers to price up for evaluation? Costing will be evaluated based on the pricing of the solution to the scenario in the written proposal. Suppliers will be asked to detail how they would go about delivering the solution, and details of the roles in the team that they would use making up the total price. A rate card will be issued to suppliers to populate and used to assess the breakdown of costs in the pricing solution.
35. You are asking for no evidental queries around suppliers’ experience of talking over services from existing supplier(s). We assume the incumbent(s) will not be exiting on 1st Jan 2020 (the latest start date). Please can you confirm how long will they remain on-site to permit handover to the new supplier(s) – we assume that some form of handover will form the basis of the initial SOWs that you issue under this framework. Is that correct? Two of the three suppliers in the exisiting ecosystem are not affected by this procurement, as they are on different contracts, so any handover will not be wholesale.
36. Your response to Q&A 4 indicates that you will choose a supplier “dependent upon the proposed solution to the problem”. The usual Digital Market Place stage 2 proposal criteria would ask suppliers to describe such an approach in their proposal but this request appears to be missing. Please can you clarify where suppliers should be outlining their proposed solution at stage 2? Suppliers at Stage 2 will be provided with details of a scenario on a possible piece of work the successful supplier(s) might be asked to complete as a statement of work under the contract as part of the written proposal. This is where they will be asked to propose a solution.
37. Please elaborate on typical activities involved in Linux troubleshooting process, does it include system programming or debugging or anything related to kernel debugging or troubleshooting ,performance optimization, job monitoring etc ? What Linux distribution / version are currently been used. Our infrastructure in AWS primarily consists of AMIs which are built with a mixture of Ubuntu 16.04 and Ubuntu 18.04. Problems can and do occur in any part of the stack down to the OS. We have support from AWS to assist with any problems with their infrastructure. In truth kernel debugging or any system programming would be rare. More common would be troubleshooting problems within the linux environment, rather than with it.
38. Do you have any configuration management tool to manage patches or upgrades or other tasks on the Linux ? Is there a cluster involved in the infrastructure, if so, can you please quantify in terms of how many servers, master, child nodes etc MDTP infrastructure is built immutably, patches and configuration changes are provisioned, via CI/ CD pipelines on a regular basis.

Due to the subjective nature of the term "cluster" it is difficult to accurately answer this part of the question. Each MDTP environment can comprise of up to several hundred compute hosts.
39. Is your current landscape is 100% cloud or on-premise or hybrid set up ? In case of hybrid, can you pl. elaborate what is placed on on-premise and what is deployed on cloud ? All public cloud, with API integrations to the back end.
40. We would like to know how does RDS data is been consumed and where does it used. E.g. is it been pushed to any BI or reporting tool. We would also like to know what are data sources feed to RDS and MongoDB. Metrics on the performance of RDS are monitored, and visualised in Grafana. Our largest use of RDS is related to the Government Gateway teams with data concerning enrollments of users to services.
Any microservice can make use of MongoDB - the actual usecase is largely irrelevent to the platform itself.
41. Can you elaborate where is Scala, Python and Ruby employed in your current system landscape, e.g. Lambda code in python etc. We want to understand if you are you looking for developers with proficiencies in these languages or engineers with expertise in developing optimized build pipelines for projects developed using these languages. All tenant services on our platform are written in Scala (with the exception of a small number of Java monolith services). This is necessary when working on Platform Operations who work most closely with service teams.
Python is the language used most commonly across the platform, in Lambdas and many other places. In the Telemetry Team there is some Ruby used in configuring Sensu, although this may change with a migration to SensuGo.
We are looking for a smaller number of developers with expertise in Scala and a much larger number of engineers with experience with Python, Terraform etc.
42. Terraform – We understand you are completely on AWS currently and you use cloud formation. What is Terraform being used for today or is it a future requirement for any multi cloud initiatives/cloud agnostics solution you may have on the road map? Although we are using CloudFormation, the majority of infrastructure is provisioned with Terraform and we are not anticipating that changing in the medium term.
We are not currently investigating any multi-cloud initives and see significant disadvantages with such an approach.

Terraform is currently used to manage Infrastructure across the various MDTP environments.
43. Is there any code deployment tool involved in your landscape to deploy git code ? is there a CICD in place, if so, can you pl. provide details on tools involved ? Our platform provides a CI-CD pipeline for all service teams. Platform teams will have their own CI-CD pipelines which will differ. For service teams, code changes committed on GitHub.com triggers a build on Jenkins and the resultant compiled code is stored on Artifactory. When deploying, teams can use a pipeline in Jenkins to push the code through all pre-production environments. Deployments to Production are an additional manual step.
44. Can you pl. provide what project implementation methodologies do you currently use ? and do you desire to alter that or open for recommendations ? e.g. Agile, waterfall etc All agile practices, which won't be changing, and currently all kanban.
45. For the security standpoint, we would like to know what protocols and controls are currently been employed for the inter app communication. E.g https ; SSL/TLS, encryption algorithm etc. forward proxy, reverse proxy, IDS etc MDTP incorporates TLS 1.2 everywhere, with encryption at rest enabled throughout the persistence layer. All connections to MongoDB also require authentication, using credentials generated and stored in Vault.
There are not currently any specific controls for inter-microservice communication, except between our different Public and Protected Zones. This is something we are likely to change in the future.
46. We would like to get some idea on scale and size of the infrastructure. Can you pl. let us know how many users are currently using your application, how many web applications, mobile application, number of API services, IAM roles, number of databases are currently being employed in your existing infrastructure There are around 1,200 people working in HRMC Digital developing services to run on MDTP. There are currently >900 microservices deployed in production, comprising >160 public facing services.
47. Is HMRC using Single or Multiple AWS accounts? MDTP has a single root account with multiple sub-accounts for the various environments and tech stacks.
48. Are you already using StackSet in Cloud formation to Provision Resources Across AWS Envirnoment ( Primary & DR )? StackSets are in use, but are not used for the provisioning or manipulation of platform Infrastructure.

MDTP does not implement a primary and DR architecture. It is built to be resilient rather than robust so runs in an active-active configuration across multiple distinct locations.
49. Is Cloud formation used in all other envirnoments like DEV, QA & PROD or only for PROD? Can you please share some details related to amount of current deployment manual /Automation? For MDTP, Terraform is the main tool used for provisioning AWS infrastructure and services. CloudFormation is also used for more the provisioning of certain dynamic resources, which are required on an on-demand basis. This is for all environments, however all other infrastructure is provisioned with Terraform and we've no plans to move away from this.
50. We are assuming CFT's are already used & that need to be uplifted & maintained ? Can you share some use cases of templates? Yes, CloudFormation templates are used. See previous answer for use case.
51. Are you using Cloudformation artefacts for the Code Pipelines or using it for IaaS deployments only ? Not currently.
52. Any Safety controls Considered with respect to CFT on the Project ? Yes, all pretty standard stuff: Observing the principle of least privilege, locking down IAM roles and policies to an absolute required minimum etc, not exposing arbitrary functionality through CFT parameters etc.
53. Any other Major AWS services with respect to IaaS, CICD & analytics which are currently used ? The major AWS services being used include ECS, EC2, CloudWatch, S3, Lambda.
54. Please share the Number of VPC's, Peering Connectivity details and approximate Instances currently being used? A brief about the Architecture would help? The number of VPCs is ~50, but most of these would only be used by each team for their own development, in Labs accounts which are spun up as required.
We may decide to share an infrastructure diagram at stage 2 if we feel it is relevant.
55. Please share some details related to the capacity of Storage S3 Used in the Project, In single region /multiple regions /multiple accounts? S3 is used in a single region, but across multiple AWS accounts. It is used for artefact storage and the archive of logs as well as storage of Database snapshots.
There is limited use of S3 by tenant services, but we are working to make this easier to provision.
56. Any S3 services used for Data Archiving, Large Data Store Analytics or Long term retention Backup & Restore? Yes, the archiving of logs - these are stored in Glacier.
57. Is S3 also Extended for CI /CD Pipe line or any logs – Percentage of utilizing S3 service in Continuous delivery? Artifactory is used for CI/CD and this uses S3 for storage.
58. Are Docker Services /Docker images are used in ECS? Yes.
59. Is ECS used mainly for Batch /Micro services functionality? ECS will shortly be used for running our tenant microservices. It could be used for other requirements as appropriate.
60. Please share some details related to the Database Engine usedin AWS RDS – Mongo DB or any DB Engine? All tenant microservices have access to provision their own MongoDB as they require. Certain tenant services also use RDS Postgres.
Other use of RDS includes MySQL for Grafana and RDS Oracle for migration of on-premise databases to the public cloud.
61. Is the RDS service is deployed in Multi-AZ deployment? Yes.
62. DB Capacity – Approximate Size of Database? There are many different databases, spread across multiple environments.
63. Is there any domain controller in place – Using for IAM integration? Assuming by "domain controller", the question refers to an Active Directory Domain Controller? In which case, no - the platform is not based on a Windows/ Microsoft architecture.
64. Please share number of instances running with proposition of Operating systems ( Majority Windows /Linux – Versions ) ? All instances are running Ubutu 16.04 or 18.04 LTS.
65. Is Lambda extensively used for regular backups & updates and also in CI/CD deployments as well? Yes. Lambda is used for the safe recyling of instances, deployments to ECS and taking MongoDB snapshots.
66. Is there any integration of AWS lambda with other services like SQS etc.? Yes, as part of step functions that, for example, automate the regular recycling of servers.
67. Please share some details of SQS /SES integrations with KMS, Lambda etc., if already implemented? KMS is used in conjunction with CMKs to encrypt secrets when stored in SSM (Parameter Store).
KMS is used across various other AWS services (e.g. for encryption of S3 storage).
68. Please share details of SNS utilization with CI/CD? Is there any usage of API's for integration? There is no particular integration of SNS with CI/CD. It is not clear what "for integration" means in this context so we are unable to comment on this.
69. What is HMRC’s policy on travel expenses? Travel to and from the Primary Location will be met from the day rate.
Expenses are payable where travel to other locations is required as part of the assignment. Where an overnight stay is required HMRC will pay for actual bed and breakfast costs within the current maximum limits. Any other subsistence or incidental expenses are not payable. Receipts must be provided.
All other expenses will be payable at the discretion of HMRC. The supplier shall not incur such expenses without the prior approval of HMRC. Any expense incurred by the supplier without prior approval shall not be reimbursed.