Royal Navy, Ministry of Defence

Tactical Information Environment Applications

Incomplete applications

5
Incomplete applications
4 SME, 1 large

Completed applications

31
Completed applications
17 SME, 14 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Friday 12 July 2019
Deadline for asking questions Friday 19 July 2019 at 11:59pm GMT
Closing date for applications Friday 26 July 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work To deliver an agile Discovery for Royal Marines looking at intelligence gathering and exploitation, assist in determination of Alpha viability, and potentially to develop solution into Alpha and Beta.
Latest start date Monday 9 September 2019
Expected contract length 9 months
Location South East England
Organisation the work is for Royal Navy, Ministry of Defence
Budget range £416k (ex. VAT) initial limit. inclusive of travel and subsistence expenses

Potential for additional £416k (ex. VAT) uplift.

Total Limit of Liability £1m (inc. VAT)

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The Royal Marines 30 Commando Information Exploitation division aim to improve the way they exploit organic and external data to inform tactical and operational decision making.
Problem to be solved Data is gathered through a variety of means - both from sets of sensors in the field or outside, and from a wide range of other public and non-public sources. This information is used to inform decision making within tight timescales but the formats are highly varied and the volume is large. The Information Exploitation division requires a team to conduct a discovery to develop user needs for the tactical information environment and development team to progress users needs through to development.
Who the users are and what they need to do As an intelligence analyst, I need to be able to gather and understand a wide range of data from field operations and intelligence work, so that i can exploit it to inform field operations.
As a Royal Marine, I need to gather data during field operations so that I can get the best advice and instructions and make better and faster operational decisions.
Early market engagement
Any work that’s already been done A pre-discovery workshop with the target user groups has established high level project goals and context. It is currently envisaged that applications will leverage the NELSON Data Platform.
Existing team The pre-discovery workshop was conducted by the internal NELSON team. Outputs will be provided to the supplier's team.
Current phase Discovery

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place Semaphore Tower, Portsmouth Naval Base, Portsmouth, PO1 3LT
Working arrangements Project space to be based in Semaphore Tower, but with regular travel to Royal Marines bases/sites for user research and testing.
Security clearance SC clearance required at minimum from start. DV an advantage.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions The following DEFCONS (latest editions) shall apply:
DEFCON 76 - Contractor's Personnel at Government Establishments, DEFCON 658 - Cyber, DEFCON 659A - Security Measures, DEFCON 660 - OFFICIAL-SENSITIVE Security Requirements,

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
  • •Supplier has ability to develop digital services in both discovery and alpha.
  • •Supplier has capability to develop digital services using a range of Open Source Technologies (list available on application)
  • •Supplier has experience of delivering services in an agile user centred way in the public sector.
  • •Supplier has experience of delivering digital services according to best practise as defined by GDS in Digital Service Standard.
  • •Supplier is able to provide User Research, Design, Technical Architecture, Business Analyst, Data Engineer and Front End Development skills.
  • •Supplier is able to recruit roles within the above skillset to mobilise agile teams quickly and flexibly as required to meet project demands and funding opportunities.
  • •Demonstrable experience of User Research methodologies, and researching across a wide variety of contexts.
  • •Demonstrable experience of effective recording of discovery outputs, Alpha developments, and handovers of User Centred Design work across teams.
  • •Demonstrable experience of effective recording of discovery outputs, Alpha developments, and handovers of User Centred Design work across teams.
  • •Has ability to provide effective handover of alpha services to beta teams.
  • •Demonstrable experience of hitting project deadlines and delivering required quality.
Nice-to-have skills and experience
  • •Have experience of using data to enable the delivery of digital services and of creating data products and services.
  • •Experience of military environments.
  • •Experience of multi-supplier environments.
  • •Experience in communicating value of digital and technical projects to a non-technical audience.
  • •Experience in the following general toolsets: Linux, Atlassian, Google Suite, O365.
  • •Experience in following front end toolsets: React, Vue, Angular, Gatsby JS, Circle CI, SASS, GitHub, Linting.
  • •Experience of carrying out user centred design in classified environments.

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • •Evidence services that have been developed, the approaches adopted and the issues encountered/resolved.
  • •Evidence of working collaboratively in a multi-supplier environment or strategies that will be used
  • •Approach and methodology, including experience of the essential and nice to have skills and experience.
  • •Description of how you have been able to scale up development teams quickly to meet customer demand, with reference to previous work.
  • •How the supplier's approach or solution meets our goal.
  • •How the supplier has identified risks and dependencies and offered approaches to manage them.
  • •Team structure and resourcing models, including experience of working alongside clients in co-located, integrated teams.
  • •Ability to scale resources as requested.
  • •Value for money.
Cultural fit criteria
  • •Work as a team with our organisation and other suppliers.
  • •Value better use of data and user centred design best practises.
  • •Be transparent and collaborative when making decisions.
  • •Have a no-blame culture and encourage people to learn from their mistakes.
  • •Take responsibility for their work.
  • •Share knowledge and experience with other team members.
  • •Challenge the status quo & work constructively to improve it.
  • •Respond quickly to feedback.
Payment approach Capped time and materials
Assessment methods Written proposal
Evaluation weighting

Technical competence

50%

Cultural fit

10%

Price

40%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. There appears to be two identical questions in the Essential Skills.
'Demonstrable experience of effective recording of discovery outputs, Alpha developments, and handovers of User Centred Design work across teams'.
Can you please confirm that you are not looking for different answers to those two questions?
Our apologies, there is a clear duplication of the requirement 'Demonstrable experience of effective recording of discovery outputs, Alpha developments, and handovers of User Centred Design work across teams'.

Thankyou for bringing that to our attention. We would not expect you to answer the same question in two ways, please consider this as one requirement to meet in response.
2. Is it possible to request the list of "Open Source Technologies" at this stage? The project includes discovery, so it is unknown what technologies the contract winner will need to extract data from current systems for use in the development.
For backend interaction with the NELSON Data Platform requirements will be primarily focussed on Docker and GraphQL APIs, and Jenkins.
Previous front end and application development NELSON projects have used a selection of: HTML, Javascript (ES6), React JS, Graph QL, Apollo GraphQL Client and Server, Sangria, SASS, Redux/Fluc, BDD frameworks including Jest, Mocha, and Jasmine, Acceptance tests including Cucumber, Puppeteer, Codecept, and WebdriverIO, Node JS, Package Managers including NPM and YARN, Typescript, Vue/ Angular.”
3. When/how would the "Potential for additional £416k (ex. VAT) uplift" be available? Is this during the first 9 months, or as an extension? This is additional funding that may be incorporated as an extension, pending quality of output of work and desire from funding stakeholders to further development beyond the initial output.

This funding is not guaranteed within the first 9 months of activity (or at all).
4. Can you confirm the process following down selection please. The ITT suggests that it is just a written proposal. Will there be a requirement to present the proposal? In addition to the assessment method stated above (written proposal), we will also be assessing shortlisted suppliers by presentation. After shortlisting has concluded, suppliers being taken forward to the evaluation stage will be sent further details to prepare for the written proposal and presentation.
5. Would the authority consider an off site working approach, with initial sprint/sprints on site, and then frequent visits to site for sprint planning/reviews etc. as required? We would feel very comfortable with this approach. Most of the NELSON projects operate under this kind of model.
6. Please provide a list of the Open Source Technologies referenced The project includes discovery, so it is unknown what technologies the contract winner will need to extract data from current systems for use in the development.
For backend interaction with the NELSON Data Platform requirements will be primarily focussed on Docker and GraphQL APIs, and Jenkins.
Previous front end and application development NELSON projects have used a selection of: HTML, Javascript (ES6), React JS, Graph QL, Apollo GraphQL Client and Server, Sangria, SASS, Redux/Fluc, BDD frameworks including Jest, Mocha, and Jasmine, Acceptance tests including Cucumber, Puppeteer, Codecept, and WebdriverIO, Node JS, Package Managers including NPM and YARN, Typescript, Vue/ Angular.”
7. Are you able to share the output from the "pre-discovery workshop" please? The outputs of the full pre discovery workshop are not suitable for sharing on this forum due to both the format and the sensitivity of the content.

The 2 day workshop involved visioning exercises to narrow the scope of work within the space, stakeholder and user mapping and prioritisation, user journey exploration of some common processes, and data type and source identification and mapping. An illustrated sketchnote was produced from the workshop. The outputs informed the creation of this requirement.
8. What is NELSON? NELSON is a digital centre of excellence for the Navy as part of its wider transformation. NELSON is building a data platform to make data accessible, acting as an in-house consultancy to help staff in the Navy understand what can be done with their data and how to get at it, and addressing cultural, behavioural and process issues that come with digital transformation.
9. Who is the customer? 30CDO IX Group is the main community for this project. It is part of 3 Commando Brigade (RM 30CDO), which is largely dedicated to the ‘find’ task. This experimentation should partly inform how a commando force should operate in the future. The army is interested in the impact this may have on the land domain, though as a marines-led project, we focus on tidal and littoral domains.
10. What prior work has been done on this project? Thus far, for initial engagement, NELSON has conducted a 2-day workshop with 30CDO to understand their problem, their community and their current data sources. Currently the project vision is not quite clear, and stakeholders may have mixed views. The purpose of discovery work is to lead this unit to be an intelligent customer and be aware of what is possible if they think differently with data – within 6-9 months and an alpha/beta stage.
11. Who from the Navy will support this project? This project will have a dedicated product owner and an engaged community. This comes from the planning officer of 30CDO and the 2nd in command of 3CDO brigade, and the technical advisor for infrastructure that is available, including links to agile C2 programmes.
The technical advisor for the user community is from MarWorks – a partner organisation of NELSON set up 3 years ago for tech acceleration. Where NELSON is interested in information warfare and data, MarWorks is interested in infrastructure and architecture that will enable a future commando force. MarWorks is based in Stonehouse, Plymouth along with 3CDO brigade.
12. How did this project come about? UOR capability procured for Operation Herrick introduced the user to capabilities such as TiGR. It took data fed in by marines from patrol reports. However, it was not taken into the core. The DACOS (Dev.) in Navy IW asked if something of this ilk could be made with data going in and knowledge coming out in various formats. The veracity and velocity of data will change daily, but we want to get more out.
13. Why are you using this specific approach? This project has tactical, operational and strategic implications. At the tactical level, data may mean something to the individual doing a reconnaissance operation, but over time that information could be consolidated and mean something else at operational or strategic levels. The work starts in the tactical space but there is an overarching effort called COLLAR.

NELSON is encouraging 30CDO to not specify something then buy it because we’ve seen it somewhere else. Focused warfighters don’t necessarily always understand the data and possibilities available. Instead we want to go in open-minded, learn by doing and experimentation, and build a holistic solution.
14. What’s your process from today in terms of making the decisions? a. The bid submission opportunity will end on July 26th. Bids will be shortlisted according to the process outlined here https://www.gov.uk/guidance/how-to-shortlist-digital-outcomes-and-specialists-suppliers. 3 suppliers will be shortlisted within 10 days. The 3 shortlisted suppliers will be given 2 weeks to prepare a presentation which will be used to evaluate a winning tender. The contract award will be handled via our commercial team and we expect a start date of no later than 9th September. (We’re aware this is a compressed timescale. We’re attempting to make use of in-year spend by maximising project time).
15. How are you going to down select from 3 to 1? The selection criteria are on the advert on the Digital Marketplace website under the ‘How Suppliers will be evaluated’ section. A presentation to a panel will be used as the assessment after shortlisting. Members of the panel will aggregate scores from the various categories and, pending a review of scoring by Navy Commercial, will determine the winner according to the highest score. Technical scoring will be carried out by NELSON, cultural scoring will be carried out by 30CDO and Navy Commercial will score on price.
16. Will there be 3 supplier presentations or just one from the winner? No, the shortlisted 3 will be asked to give presentations, not just the winner.
17. Will the Discovery be technical in terms of an output in some kind of thing or is it going to be more around the discovery of what the business needs are and getting them articulated in a way someone can take the info that’s being collected into a product that will be developed into beta or alpha? Discovery will clarify what the user needs are and establish a prioritised roadmap. It should also do a deeper dive into the data and the data needs; the current infrastructure; the understanding of programmes in flight already that could be used for support; and getting right stakeholders involved. There is an important user research element to it, but it does include data science and architecture too.
18. What data is likely to be available? 1/3 We don’t have buckets of data sat there as often we haven’t routinely kept some of the operational data. For example, Operation Baltic Protector, a recent deployment, did not routinely keep records. The only records we will have are from Taskforce Helmand from Operation HERRICK which isn’t representative of all environments. As part of discovery, we’ll want to explore what data is there, where to start, what types are available and useful, what can we give out, and how can we ensure that data we want or need is captured in future operations.
19. What data is likely to be available? – 2/3 30CDO is looking to make a generational leap in capability. For example, does a ‘patrol report’ need to be done in person? Could an operational report be filled with remote sensors entirely or partly? There’s a new way of thinking and working that is meant to augment the human or take them away from the threat that needs to be thought of conceptually, and for the winning delivery partner to encourage, right from the tactical element of how data is collected on operations to the strategic distribution through company HQ.
20. What data is likely to be available? 3/3 This means the users aren’t completely cold and there could be opportunity to plug into something bigger. The team selected should be one that can blend from user research heavy in discovery phase with a bit of data science and technical architecture, and to then blend or fuse more into the kind of development team you’d expect for an alpha or beta, without a contractual gap. A roadmap with technical documentation is the least we’d expect at the end of alpha with guidance, so we can secure additional funding to continue the process.
21. What would be your ideal at the end of 6-10 months? An ambitious and mature beta, integrated with the NELSON data platform, which fuses data sources together. We have gained buy in from 3 Commando Brigade to start changing culturally and start collecting and sorting data sources.

The CO of 30CDO wants to enable end-to-end info exploitation. He wants to be able to find, fix, move, process and access data anywhere, in support of 3 Cdo Bde. That is big and needs scoping. From our exploration workshop we realised we don’t know all the data types. We need help deciding what to focus on, get data accessible, and develop our roadmap.
22. In the 2-day workshop, did you look at what data types the marines were particularly interested in? In superficial terms, there was a mapping of current data but no diving into whether they are machine-readable.
23. What was the data you looked at in the 2-day workshop? Did you explore data types and attributes they thought they had or what was held within NELSON? No, it was data that we have or would like but is not accessible or integrated to the NELSON platform at the moment. We talked about data we’d like, and of sensitive data that is hard to use because of classification boundaries on certain networks. We want to create a more fused environment.
24. What is the balance between digital and technology in the tactical environment? At the tactical edge, we aren’t very digital. There will be a bit of recorded voice (possibly digitised) or FMV, but a lot is analogue like tactical reports. We know the future is digital (likely autonomous/unmanned) so we’re trying to digitise and test tech with front line users, but it’s chicken and egg. The types of data they want will rise, but as we experiment along the journey under Agile C2 and Future Commando Force, the digitisation in the tactical space will increase and in turn increase data demands/opportunities.
25. We’d like to get a beta out ASAP – do you have infrastructure available to do this (e.g. Azure credits or AWS credits?) We have UKCloud credits using Openstack, we have hardware and infrastructure in place via MarWorks. MarWorks will be embedded in the process from the start and begin concurrent activity to provide the infrastructure needed to support an alpha and a beta.
26. With 40% weighted on cost, ideally we’d like to start concept demonstration asap to interact with stakeholders and demonstrate as the product evolves. We had a look at the contract figures and not sure if that’s possible in the budget. We could do a low-cost proposal to meet the 40% figure but would have to do more discovery up front and delay delivery of software. Where do you see the balance between discovery learning and delivered software? Our view is long-term – more discovery and more holistic and deeper understanding to mature the thinking the better. However, at the end of 9 months, we need to deliver something functional as that is the thing that will change the culture of the brigade to whet their appetite for going further. Your bid needs to consider that. We need to deliver something sufficiently impressive within the timescale, whilst leaving time to deliver a Beta.
27. Is the ask here to conduct a discovery phase that produces software which will demonstrate a capability to fuse data from X number of data sources and present that to a brigade user in a way that makes sense to them? 1/4 NELSON models itself on Government Digital Service’s Service Manual, in which a Discovery phase does not normally produce a software output. The requirement as described in the brief is to conduct a discovery phase, and then develop a solution to alpha and beta. These phases are not concurrent. The outcome of discovery will be to lead users from a broad problem set to determining the viability of one (or more) Alpha routes. As NELSON has a requirement to deliver, one route at least is achievable within timescales (balancing quick win vs. value) should be taken to develop some software.
28. Is the ask here to conduct a discovery phase that produces software which will demonstrate a capability to fuse data from X number of data sources and present that to a brigade user in a way that makes sense to them? 2/4 - To clarify - the discovery phase needs to include some sort of alpha product that can demonstrate capability to fuse data from x number of data sources and present that to brigade user in a way that makes sense to them – is that correct? NELSON's strategy, just like the Government Digital service's strategy, is delivering things. If we commit, we must deliver. Yes, we will focus on discovery, but we also need to deliver.
29. Is the ask here to conduct a discovery phase that produces software which will demonstrate a capability to fuse data from X number of data sources and present that to a brigade user in a way that makes sense to them? 3/4 - More than discovery – software development to? Yes. We need to quickly lead these users from a broad base and problem set into a line of delivery focusing on something achievable in timescales. We will achieve the sweet spot of quick win vs value.
30. Is the ask here to conduct a discovery phase that produces software which will demonstrate a capability to fuse data from X number of data sources and present that to a brigade user in a way that makes sense to them? 4/4 - Discovery and development phase – will they be separate or can developer start at back of discovery? 2 separate teams or no? NELSON is modelled on the Government Digital service standards, which are available online. Discovery is normally prior. We don’t want to charge on at end of discovery if there is nothing worth doing. However, if we are confident we can deliver a service then we will carry on into Alpha. We don’t know at the moment, so some work is needed to determine that.
31. Security aspects for discovery phase – what classification are you working to? Will keep to official – but discussions will go up. Team needs to be SC cleared to take on the work, but the discovery phase shouldn’t include above secret data sources in its scope.
32. Is there any problem with working remotely and providing regular onsite updates? No. We often work remotely in Programme NELSON. There will be office space in Portsmouth with the rest of NELSON to use and some occasional presence may be required there. Users will be located elsewhere and travel to those places may well be required as part of discovery. There is no requirement for a team to spend 100% (or even most) of its time in the NELSON office and remote working can be facilitated.
33. If we develop a backlog through discovery, where would that backlog be kept? Are you going to provide the tooling for agile processes? One thing covered in specification is demonstrable ability to handover Discovery and Alpha products. We will expect handover of your outputs at the end of a discovery period and the end of an alpha. How this happens will depend on how you work (i.e. paper-based user research, recordings etc). It is up to you to decide how you want to handover to us and to provide evidence that your handover process will enable us to properly absorb learnings from discovery and/or continue development work if applicable.
34. Currently the bid has a 40% weighing on cost. Do we have an opportunity of proposing a method of conducting the discovery and producing a beta that will describe what we get for the cost? Yes, this would be welcome. You can describe what we might be able to achieve within the cost boundaries and the resourcing that you are likely to be able to provide within the cost limits.
35. What format would you want the cost information in? Would that be prior to next Friday or after down selecting? If you can do this before the initial shortlist, that would be good. Otherwise we will expect to explore that within the next stage of selection.
36. Can you confirm that TIE will be required to develop a methodology to create a data flow from resources into a single resource (i.e. query data, extract from sources and place elsewhere)? Yes. There are not currently pipelines from these data sources into NELSON. There are many data sources in Defence that are not integrated. Part of the point of discovery in this project will be to identify which sources to prioritise in the project.
37. The data that the 3CDO team might be looking for are out there somewhere or are in a database. Does that data need to be brought into NELSON first or can a future application use the data before it gets to NELSON, or even in parallel? Data needs to come into NELSON at some point. Whether it's sequential or parallel depends on timescales and the complexity involved in the challenge revealed in the Discovery phase.
38. Could you elaborate on the likeliness of need to process data or transfer it within the tactical environment? As a starting point, the tactical space is challenged by connectivity– there’s no 3G or 4G. One possibility is interrogating information in a way that can be federated back into NELSON and vice versa, but some data processing should be local. If reachback is needed every time for knowledge, the system won’t be robust– both for marines or for the wider navy. Users are likely to be using one of many devices, and when they get an uplink or downlink to a cloud wherever they are, we want to augment that.
39. Moving forward into the future, will there also be a new style of IT deployed, and will this marine application be deployed on it? It might not be hosted on a new style of IT – it may be something completely different. NSOIT might be able to host it but we can't confirm yet. For our future evolution and alignment with other wider projects (e.g. COLLAR), one of the decisions to make is whether we utilise NSOIT or create something separate and go it alone for this app. This is unknown right now. Note there is also potential to influence the wider NSOIT programmes, for instance by communicating an expectation for hardware capabilities to support certain graphics in applications.
40. To clarify, at a minimum you want to use a private cloud infrastructure that you have access to on UKCloud for the moment , the assumption being that this is analogous to what guys have in theatre. However, this needs to reflect the data exploitation of whatever sources were identified from discovery phase and at some point, will that data move into NELSON? That is correct.
41. When do we get sight of the high-level project goal and context? We will be informed by the discovery phase to inform the future commando force of how it’s going to operate. The thinking is being done, this work is being informed by it and will inform back too.
42. In terms of intent of the app to exploit and analyse data from whatever source is deemed most achievable within the timeframe, is that something that you will tell us about? Will you build it on this NELSON platform expecting unlimited licenses or is it a case of ‘we understand what NELSON is but we think this is a different answer’? I.e. do we need to replicate a mini version of NELSON for this? NELSON as a digital platform is the answer but maybe there should be a 3 Commando enclave within it. Replication isn’t necessary. NELSON has a deployable version and a core data environment. Whether we deploy NELSON to other HQs (that’s what MarWorks does) or not, we expect the final output to be ingested by NELSON. We have a core platform team dealing with data ingests and when we identify the sources of data that are valuable, we will want the contracted team to support our platform team with however much resource is needed to integrate their work.
43. What skilled resources, capabilities, experience and software are you expecting to be deployed from the supplier site? We don’t know this yet fully. It will be determined by the discovery phase. Part of the requirement here is for you to identify what resource is appropriate from discovery then to supply it (reach out to market to get this if it's not within your company already). There is additionally another question listed asking for a list of open source technologies in NELSON which is worth referring to, though note it’s not exclusive of other technologies (bearing in mind there are some standards for developing NELSON applications – particularly around the use of front-end components).
44. Have you thought about or lined up any user research training exercises that can be exploited in the project? A few opportunities have been discussed – namely Commando Training courses, an upcoming deployment exercise, and weekly commando unit reports. The challenge will be in how quickly we want the data – Command training courses will be quicker than Norway exercise. Some weeklong commando warrior exercises are upcoming, but they won’t represent the constant data flow we deal with. The discovery phase will involve discussing with the user community and identifying the best routes to take for further UR and data examination. The NELSON community will be able to support in these decisions, as will the Marines’ product owner.
45. On the Digital Marketplace, there are only 100 words in the box to supply evidence, so can we provide links? No, this isn’t permitted by the Digital Marketplace guidance laid out here on ‘writing evidence’: https://www.gov.uk/guidance/how-to-sell-your-digital-outcomes-and-specialists-services#writing-evidence.
46. On the application form on the DOS3 website, there is one question repeated:

Demonstrable experience of User Research methodologies, and researching across a wide variety of contexts

Could you please advise on how to address?
The Essential Skills and experience criteria - "Demonstrable experience of effective recording of discovery outputs, Alpha developments, and handovers of User Centred Design work across teams." - has been repeated in error. Please copy the same answer into both response boxes, or leave one as N/A. Only one box will be scored.
47. Do you know Lieutenant Commander Paul Santry? Yes we do – the person who asked this question had a conversation with him a few weeks ago.
48. Given that this is very much an agile development, a fixed price quote will not be appropriate. How will you be evaluating price? Can we assume it will be based on day rates for various skill sets? In the DOS advert we stated that our payment approach would be Capped Time & Materials. This means that suppliers should submit a pricing matrix with a breakdown of roles, day rates and amount of days that they think is needed to meet the requirement. The total price should be within the budget stated in the advert (£416k ex VAT for the initial period. The optional additional funding should not be considered at this stage). The total prices submitted will be compared and scored by Navy Commercial in line with the weightings specified in the advert.
49. Can you confirm what security clearances, if any, the user research team will need? If required, will the Royal Navy be willing to sponsor the process? The discovery and development team will all need SC clearances. Programme NELSON is willing to sponsor these. It is worth noting, however, the tight contract timescales, and the essential skills and experience requirement “supplier is able to recruit roles within the above skillset to mobilise agile teams quickly…“. In the proposal criteria, suppliers should demonstrate “how the supplier has identified risks and dependencies and offered approaches to manage them” and “team structure and resourcing models…”. Acknowledging the length of time required for acquiring SC clearances, we would expect to see the risk of clearance delays addressed and mitigated.