“5.1. The Authority requires a Video Solution which can be used by the various DWP directorates and the different business units within each directorate (DWP Lines of Business), in parallel to the continued use of Telephony, Chat or face-to-face customer engagement channels. The initiative intends to provide an alternative channel of communication with the individual. A major advantage of this initiative is that the individual won’t have to travel to have a face-to-face meeting or assessment. … 5.4. Additionally, the Authority needs a Video Solution that Customers and DWP employees will be able to use only via their web browsers and the solution must support two models of Video engagement: a) First model is the more traditional and common approach where the Video Solution creates unique URLs per Video meeting so that Customers and DWP employees can use them to directly join the Video meeting. b) Second model is where the solution provides waiting rooms functionality. Customers using the URL corresponding to each waiting room will be landing to a page where they’ll be filling in some information (e.g. first name, surname) and will then be waiting in the waiting room until a DWP Host admits them to the actual Video meeting. 5.4.1. For the first model, the solution shall provide the ability for DWP to create and manage the Video meeting URLs programmatically via APIs. 5.4.2. For both models of engagement, the solution must follow GOV.UK styles and the DWP customers must consume the service from within GOV.Uk web pages without being aware that they are using a third-party Video product.”
“Please provide a description of how the overall proposed solution will meet the GOV.UK related requirements, detailed in Attachment 1 – Specification.”
“User Interface and GOV.UK styles” classified as a “MUST” and stated: “10. The proposed solution supports the standard GOV.UK styles …. so that the Customer interface of the Video Solution is integrated and provided from within DWP web pages that adhere to the design standard. 11. The proposed solution supports that no branding is visible to the Customer interface of the Video solution when they are using the service, i.e. DWP customers will consume the service from within GOV.UK web pages without being aware that they are using a third-party Video product. 12. The proposed solution must be presented via GOV.UK and alternative DWP websites e.g. the Universal Credit portal, Citizen View/Colleague View when they are available.”
“The Authority requires a Video Solution that provides a Customer Interface which is consistent with the rest of the GOV.UK pages, it looks and feels like GOV.UK page and complies to GOV.UK structure and style requirements set out in the Specification. Your response should include, as a minimum: 1. A description of how the solution will ensure that the Customer Interface is integrated and provided from within DWP web pages that adhere to the standard GOV.UK styles as described in https://www.gov.uk/service-toolkit and https://design-system.service.gov.uk/". 2. Describe how the solution will be architected to ensure that DWP Customers will be consuming the Video service from within GOV.UK web pages, without being aware that they are using a third-party Video product.”
“5. A minimum score of 4 is required for each of the Technical Merit questions (“Technical Merit Minimum Threshold”) 6. Where the Tender is evaluated and does not meet the Technical Merit Minimum Threshold set for a question within the Technical Envelope, the entirety of their Tender will be deemed as non-compliant and the Potential Supplier will be excluded.”
“Where information or documentation submitted by Potential Suppliers is or appears to be incomplete or erroneous, or where specific documents are missing, the Authority may request a Potential Supplier to submit, supplement, clarify or complete relevant information within a specified time limit provided that the Authority is satisfied that such requests are made in full compliance with the principles of equal treatment and transparency. In those instances, the Authority will send any questions using the Portal to the named representative of the Potential Supplier. They will also be notified by email from the Portal. This will be sent to the person who is registered on the Portal, who must arrange for a reply via the Portal by the stipulated clarification response deadline.”
“21.1. The Authority shall evaluate all compliant Call-Off Tender responses to the Further Competition respectively. The purpose of evaluation as described in this section is to identify the “Most Economically Advantageous Tender” (‘MEAT’). 21.2. The Authority will only evaluate information provided by Potential Suppliers in their Call-Off Tender response.”
“Can you elaborate on the requirement to integrate into GOV.UK? are you expecting customers to access the solution ‘embedded’ into existing GOV.UK. pages or can the solution be deployed into GOV.UK (eg subdomain).”
“A Customer is provided with a GOV.UK.URL. The Customer uses this URL in their web browser and they land to a GOV.UK web page which is styled with the standard GOV.UK styles. From within that GOV.UK page, the Customer consumes the Video service without being redirected to a page in a non GOV.UK domain, so that the Customer is not aware that they are using a third-party Video product.”
“SQOD has been designed and built with the ability to provide full customisation to customers using the product. This allows for design elements to be changed including logos, colour schemes and text elements. As part of the development of SQOD for GOV.UK use, a full suite of customisation has already been developed and included using the GOV.UK design toolkit. All components used within the GOV.UK template have been developed using elements taken directly from https://www.gov.uk/service-toolkit and https://design-system.service.gov.uk/. … The SQOD platform supports integration into a customer website. The GOV.UK instance will be pre-designed using the GOV.UK template so any Waiting Rooms or Scheduled video calls will automatically have the design applied. Involve will work with DWP as part of the implementation to deliver a masked URL where applicable utilising DNS records to allow the SQOD platform to appear as part of the DWP web portfolio. The SQOD user interface will be presented within the flow of a DWP Business unit. The template used for the GOV.UK site will be maintained and updated based on the future development of the GOV.UK design toolkit. … All customers using the SQOD platform will be presented with a user interface using the GOV.UK design toolkit. This will provide the confidence that the solution they are using is provided and delivered by DWP. All elements of the user interface will use GOV.UK components, colours and fonts and provide a familiar user experience as provided on any other GOV.UK web site. SQOD has been designed to be third-party product and branding neutral, ensuring that there are no third-party video components or branding visible. This is possible by embedding the video window and controls within the SQOD GOV.UK styled web pages.”
“Customer Interface - Mat and Chelsea considered that the Potential Supplier had responded to guidance item one to an excellent level of detail, particularly how the web pages will adhere to the standard GOV.UK styles. The response provides evidence of previous development where these standards have been adhered to, as well as a number of relevant supporting screen shots. Furthermore, the response explicitly references relevant accessibility standards and flags the process if something isn't compliant with WCAG 2.2. Ioannis agreed that the response does provide excellent detail on the compliance with GOV.UK styles element of the question, however, focussed on the 'integrated and provided from within DWP web pages' element. The Potential Supplier's response refers to use of a masked URL so platform appears to be a part of the DWP web portfolio. Ioannis considered that this does not meet the requirement as a masked URL that looks like a DWP web page is not the same as the web page actually being integrated from within DWP web pages. Following a lengthy discussion, Mat and Chelsea did not agree that URL masking did not meet the requirement, Ioannis agreed that if the URL masking was acceptable then it should be considered that the guidance item was addressed to an excellent level of detail. GOV.UK Web Pages - The same rationale for Ioannis' score applied to guidance item 2 in that he did not consider URL masking to address how the solution will be consumed from within GOV.UK web pages. However, in line with the discussion on guidance item 1, it was agreed that if this did meet the requirement, the response explained how the solution would be architected to an excellent level of detail. Although, the response only confirmed that customers will not be aware that they are using a third-party product, it did not describe how this will be achieved. Overall – Ioannis initially scored a 1 due to URL masking not meeting the requirement for the solution to be integrated and provided from within DWP/GOV.UK web pages, therefore the only part of the requirements that were considered to be addressed was the GOV.UK styles. Following Mat and Chelsea’s view that the URL masking did meet the requirements, it was agreed that how this process would be architected was done to an excellent level of detail and therefore Ioannis agreed to raise to a 7. In summary the response was considered to have addressed most of the requirements to an excellent level of detail, further information on how the customer won’t be aware that they are using a third-party video product could have been provided. The screenshots were relevant and demonstrated that the Potential Supplier had a thorough understanding of the Authority’s requirement for a solution that adheres to standard GOV.UK styles.”
“In the process of writing up the moderation notes for Question 6.4, I do not believe we have sufficiently addressed the issue with Involve and around if a masked URL can be considered to meet the requirement that the Customer Interface is integrated and provided from within DWP web pages and a more thorough justification is needed for the final score. On that basis, Corinne will be sending out an invite for a follow up moderation meeting next week to discuss further.”
“… I don’t think I can actually add anything on the issue with the masked URL as from my perspective it is more of a tech question of whether this can be done seamlessly – as far as I’m aware it can be so any constraints are tech not GOV.UK design. I certainly wouldn’t feel comfortable failing any of the suppliers based on this.”
“SQOD is a third party hosted platform requiring DNS entries that will need to be investigated further. The response states that there is customisation to customer requirements, with initial pre-design using GOV.UK templates. Overall, this again is a disappointing example of a response. There is very little detail of how the solution will be seamless and transparent to the end user, or how it will fit within the DWP architecture.”
“Question says the customer interface is provided from within DWP webpages, the UI is not embedded within DWP webpages instead the URL is masked and you will be consuming the service from Involve’s URL – does not meet the requirement. Mimic embedding of pages, whilst they are hosted somewhere else within Involve’s space. • Mat – do mention DNS redirect – standard approach to make it appear as if it is the same thing • IF – user journey, start in gov.uk page then when click to go to new solution, will leave gov.uk space and land in supplier’s site • MM – do that in any of the supplier’s web UIs • No innovation or added value to score a 10. Key argument on point 1 is ‘from DWP web pages’ and what this means. Currently health customers go to a gov.uk url, select a supplier and are taken to that supplier’s webpage, when start a video call, re-directed to a video platform which is a non-gov.uk page. Have no control to change content of page. UC – create video and send gov.uk link. Customer lands in a DWP webpage with gov.uk URL. Lacking how the solution will be integrated. Evidence on adhering to styles (2nd part of point 1). How the solution will be architected is lacking. Discuss how they won’t be aware. Short response, screenshots take up a lot of the word count.”
“Showed what was required- platform page has to show that it is a DWP page but Involve can’t do this. Matt- This may change my view. But the problem may be in the way on the exact wording of the questions. But based on what Ioannis has shown- in practice it is not viable. But is the score a 1- based on what constitutes a 1 if it doesn’t meet requirements. I am prepared to come down – I am onboard with what Ioannis- it meets the look of the question but doesn’t meet the integration. Part 1 does not meet the requirements. They have not met the description of how it would be integrated. They have explained how they will adhere to the standards. Ioannis- Provided some evidence about adherence to the styles. They have provided evidence to show that the customer wouldn’t know that it was being masked. Matt- In reality the masking wouldn’t work. Philip- They said they are confident they can do it, but not confirmed that they can. Matt- Happy to go to a 4- it is clear that now it is not a 7. Phillip and Ioannis- Are happy to come up to a 4. Jess went through question again for an understanding. Confident Architecture consumed from within - not met. Philip- We are saying technically that it is not compliant. Matt- Phil you mentioned the supplier said ‘We are confident that we can do X, Y, Z’ can we revisit this wording- to look at if they have said if they can do what we have asked or are they just confident? Phil shared the response. Mathew- now rereading this I am leaning towards a 1. Philip – from rereading this I am not confident that anything they put in there would work. Mathew- 4 parts to the question and 25% of them are good. Jess- If we go through each section one by one to understand. Part 1 – Customer interface from within - Mathew- This is a fail- they have used a non-viable method. They have proposed to use masking- not viable- so show as they have not understood the requirement. Ioannis- URL masking could put masking in place- but to put this in place is not an integration- don’t want to state this is not viable. It does not meet requirement. Masking not equivalent to not be integrated. Adherence to gov.uk styles – ok Consumed from Within- As above Not aware using a third-party- Mathew- no explanation of how. Ioannis- If I can add- URL masking- can you tell if you are technical enough it is masked? So there is technically a way for a user to know they are being direct. Mathew- End point. Depending on where you are in the world and which part of the country your DSS records can lag and are not in real time. If the provided had an outage and switched to secondary data centre- would point to prior IP range and could get outages as a result. Could be a concern. Overall scoring relooked at again- if only hitting one out of four is not meeting it and also have misunderstood what we mean by integrated. Score agreed - 1.”
“Each guidance item was reviewed and discussed, in turn alongside the moderation comments, with all three evaluators. It was felt that the original moderation comments were no longer applicable. Customer Interface - In the initial moderation there was a substantial discussion around the meaning of 'integrated and provided from within DWP web pages'. Chelsea and Mat had originally considered that URL masking met this requirement and this again was discussed during the re-moderation. Ioannis presented the current Customer journeys, demonstrating the difference between pages that are integrated from within DWP web pages that have a GOV.UK URL, versus use of Supplier webpages. Following this demonstration, Mat revised his view and agreed that URL masking is not equivalent to the Customer Interface being integrated and provided from within DWP web pages. Phil also agreed that the proposed approach did not meet the requirement. As a result, the extent to which the Potential Supplier had addressed guidance item one was considered, it was agreed that the response addressed the GOV.UK styles element to an excellent level of detail, however, did not address the integration point on the basis that the information provided did not meet the requirement. Therefore, the response only partially addressed guidance item one. Furthermore, the provision of a solution that does not meet the requirement suggests a lack of understanding of the Authority's requirements. GOV.UK Web Pages - For the same reasons as above, Mat revised his view that the proposed architecture of the solution addressed the requirement within guidance item two that the solution will be consumed from within GOV.UK web pages. The response details the Customer consuming the video service from something that appears to be a GOV.UK web page but is actually the Potential Supplier's SQOD platform. As had already been highlighted in the initial moderation, and as Phil picked up on in his evaluation comments, the response provides very little detail on how the solution will be seamless and transparent to the end user. The response relies on a statement that 'we can confirm that DWP customers consuming the video service from within GOV.UK web pages will not be aware that they are accessing a third-party video product' rather than providing sufficient detail on how this will be achieved. It was therefore agreed by all evaluators that the requirements of guidance item two were only minimally addressed with the confirmation statement described above. Similarly, there was minimal evidence that the Authority's requirements had been understood, given that the proposed architecture did not meet the requirements of the question. Overall - Following the above discussions, it was then deliberated whether the response partially addressed the requirements or minimally addressed the requirements. It was agreed that the response only minimally addressed the requirements; GOV.UK styles were well addressed, Customer's not being aware that they were using a third-party product was minimally addressed, and the integration and provision of the Customer Interface and consuming the solution from within DWP / GOV.UK web pages was not addressed in a way that complied with the requirements of the question. Furthermore, the proposal to use URL masking rather than to integrate from within DWP / GOV.UK web pages provided evidence that the requirements had not been understood. All evaluators agreed to a score of 1 and Mat confirmed he was content to move from a score of 7 to a score of 1.”
“(1) Contracting authorities shall treat economic operators equally and without discrimination and shall act in a transparent and proportionate manner.”
“[41] … the principle of equal treatment implies an obligation of transparency in order to enable compliance with it to be verified … [42] More specifically, this means that the award criteria must be formulated, in the contract documents or the contract notice, in such a way as to allow all reasonably well-informed and normally diligent tenderers to interpret them in the same way. [43] This obligation of transparency also means that the adjudicating authority must interpret the award criteria in the same way throughout the entire procedure … [44] Finally, when tenders are being assessed, the award criteria must be applied objectively and uniformly to all tenderers ...”
“[8] … [In the Mayo case] the Court explained what the legal principle of transparency meant in the context of invitations to tender for public contracts: the award criteria must be formulated in such a way as to allow all RWIND tenderers to interpret them in the same way. That requirement set a legal standard: the question was not whether it had been proved that all actual or potential tenderers had in fact interpreted the criteria in the same way, but whether the court considered that the criteria were sufficiently clear to permit of uniform interpretation by all RWIND tenderers. … [12] … the yardstick of the RWIND tenderer is an objective standard applied by the court. … [14] The rationale of the standard of the RWIND tenderer is thus to determine whether the invitation to tender is sufficiently clear to enable tenderers to interpret it in the same way, so ensuring equality of treatment. The application of the standard involves the making of a factual assessment by the national court, taking account of all the circumstances of the particular case. [27] … The court has to be able to put itself into the position of the RWIND tenderer, and evidence may be necessary for that purpose: for example, so as to understand any technical terms, and the context in which the document has to be construed. But the question cannot be determined by evidence, as it depends on the application of a legal test, rather than being a purely empirical enquiry. Although, as counsel for the appellants emphasised, the question is not one of contractual interpretation – the issue is not what the invitation to tender meant, but whether its meaning would be clear to any RWIND tenderer – it is equally suitable for objective determination.”
“if a criterion was going to be fatal at the outset to the whole tender, then it ‘was one in respect of which the principles of clarity, fairness and equality of treatment demanded particular clarity and transparency’.”
“The principles of equal treatment, non-discrimination and transparency require a contracting authority that has adopted a decision-making procedure for assessing bids to comply with it once it has begun to do so. A different way of expressing the same principle is to state that a contracting authority that has set rules for that procedure must follow them, applying those rules in the same way to the different bidders. Changing the decision-making procedure during the process of assessment risks arbitrariness and favouritism, a risk that it is the purpose of such requirements to avoid ...”
“… the Court should always resist the temptation simply to substitute its view for that of a contracting authority and should only intervene where sufficiently material breaches of obligation are shown… There is, however, no judicial remedy for subjective dissatisfaction at losing a procurement competition.”
“like taking the existing “Attend Anywhere” solution, adding a GOV.UK style ‘skin’ to that and then asking DWP to use it, which would not in my view have been acceptable to Domain Architecture.”
“In my initial evaluation and at the initial moderation meeting, I thought that Involve’s answer to question 6.4 … should be scored with a 7 and that it met the requirements. In the wider world of IT solution architecture, URL masking can be used to appear as part of a wider solution relatively transparently. With hindsight, I believe that I misread part of the requirements and that some of what Involve was saying did not meet the intent of question 6.4. The portion of Involve’s response specifically referencing URL masking did not meet the requirement of hosting the solution within what I would describe as the boundary of GOV.UK (“provided from within DWP web pages”).”
“the solution must follow GOV.UK styles and the DWP customers must consume the service from within GOV.Uk web pages without being aware that they are using a third-party Video product.”
“User Interface and GOV.UK styles”: “10. The proposed solution supports the standard GOV.UK styles …. so that the Customer interface of the Video Solution is integrated and provided from within DWP web pages that adhere to the design standard. 11. The proposed solution supports that no branding is visible to the Customer interface of the Video solution when they are using the service, i.e. DWP customers will consume the service from within GOV.UK web pages without being aware that they are using a third-party Video product. 12. The proposed solution must be presented via GOV.UK and alternative DWP websites e.g. the Universal Credit portal, Citizen View/Colleague View when they are available.”
“The Authority requires a Video Solution that provides a Customer Interface which is consistent with the rest of the GOV.UK pages, it looks and feels like GOV.UK page and complies to GOV.UK structure and style requirements set out in the Specification. Your response should include, as a minimum: 1. A description of how the solution will ensure that the Customer Interface is integrated and provided from within DWP web pages that adhere to the standard GOV.UK styles as described in https://www.gov.uk/service-toolkit and https://design-system.service.gov.uk/. 2. Describe how the solution will be architected to ensure that DWP Customers will be consuming the Video service from within GOV.UK web pages, without being aware that they are using a third-party Video product.”
“A Customer is provided with a GOV.UK.URL. The Customer uses this URL in their web browser and they land to a GOV.UK web page which is styled with the standard GOV.UK styles. From within that GOV.UK page, the Customer consumes the Video service without being redirected to a page in a non GOV.UK domain, so that the Customer is not aware that they are using a third-party Video product.”
“20.1. Each Potential Supplier must notify the Authority of any actual or potential conflict of interest that may be relevant to this Further Competition and/or the submission or evaluation of its Call-Off Tender as soon as reasonably practicable after it becomes aware of such a conflict. 20.2. Failure to declare such conflicts and/or failure to address such conflicts to the reasonable satisfaction of the Authority may result in the Potential Supplier and/or members of the Potential Supplier's Team being excluded from further participation in the Further Competition. 20.3. Potential Suppliers should remain alert to the possibility of conflicts of interest arising at all stages of the Further Competition and should update the Authority if any new circumstances or information arises, or there are any changes to information already provided to the Authority. 20.4. Failure to comply with this Section, and/or to manage any conflicts of interest properly, may result in a Call-Off Tender being rejected.”
“We have no potential, actual or perceived conflicts of interest relevant to this requirement.”
“We confirm that there is no actual, potential or perceived conflict of interest as the incumbent, as defined by the regulations. As the incumbent, we acknowledge that there will always be a perception of conflict of interest in the wider sense of having an unfair advantage. Furthermore, we are an SME without the resources to ensure total separation at executive level of oversight of the bid. Prior to the issue of the tender, the Authority raised the question of actual and perceived conflicts of interest with us as the incumbent. After extensive discussion, we agreed with the Authority a mitigation approach which is set out in the attached note in order to address an unfair advantage perception (which could, in the widest sense, be interpreted by some as a conflict of interest). This has been implemented as described. The bid team, in its response to question 3.1 of attachment 2, had no knowledge of our previous discussions and responded within their knowledge without recourse to senior executives. Furthermore, as the response was completed in the portal, Involve’s executive team did not have governance oversight of this and so were not in a position to and did not inform the bid team of this agreed position. Therefore, whilst we acknowledge the existence of a perception of conflict of interest (in its widest sense) as the incumbent, we are confident that the steps implemented with the Authority’s approval ahead of this exercise mitigate any potential conflict. Furthermore, in response to a clarification request from another tenderer, you have confirmed the extent to which steps have been taken to ensure equal access to information, fairness and transparency in the process and we fully support your response. As we state above, the steps agreed have been implemented and we are confident that these will help to demonstrate the transparency of the Authority’s tender process.”
“As the incumbent provider to DWP, Involve believes that there could arise a perception of a potential conflict of interest if Other Bidders believe that Involve (or its Representatives taking part in the ITT Process), because of its relationship with DWP under the existing contract, has or has had access to information which could provide Involve and/or its Representatives with an advantage and render unfair an otherwise genuine and open competitive ITT Process. … The conclusions reached by Involve in undertaking such considerations are that it would be possible, with the resources available to Involve, to separate ongoing management of the existing contract from the new ITT Process and ensure that there is no information flow between the delivery team working on the current contract and the bid team for the new ITT Process. Therefore, in order to eliminate a conflict arising, Involve has proposed taking the following steps and seeks DWP’s approval to these steps for the purpose of the EWA, so that Involve can participate in the new tender process with those measures in place. The steps being implemented by Involve are as follows: The current senior executives overseeing delivery and performance of the current contract (commercial lead (Mick Roach) and Technical Lead (Dan Loomes) will withdraw from their roles with immediate effect and have no further engagement with the current contract (and no line management roles in relation to that contract). They will be replaced by Mark Rea (commercial) and James Tongue (technical) [who will report to other managers within the Involve hierarchy]. Following issue by DWP of the specification for the new ITT Process, a bid team will be assembled by Involve which will not include any of the current delivery team. Mick Roach and Dan Loomes will have oversight/review roles (relating to commercial and technical aspects of the bid) for the bid as senior managers but will not participate in the detailed bid assembly. As an SME it is not possible to completely remove Mick/Dan from the process without it having a disproportionate negative impact on the quality of any potential bid from Involve. These steps will eliminate potential conflicts of interest arising as the timeframes involved in the ITT Process should mean that any short-term information to which either Mick or Dan may have access will quickly become out of date and irrelevant for the new bid, which will be appraised internally on its merits…”
“The content of the technical questions in the ITT effectively rendered the agreed mitigation unnecessary since there could be no incumbency advantage (by reason of having relevant information not available to other bidders) because of the entirely different requirements of the new contract compared with the existing contract.”