CHATBOT digital assistant for tactical military users

Tender description

Why the Work is Being Done To show how access to information and intelligence may be improved for military users who are operating via tactical radios (emulated here) though the use of a digital assistant (CHATBOT). The CHATBOT is to be located on the opposite end of the radio link to the military user at a location with good connectivity to military information/intelligence resources and services (but still no Internet access for security reasons). Problem to Be Solved Tactical users do not have internet connectivity and are restricted to low data-rate error-prone communications (tactical radios). They often need rapid access to information and intelligence in a succinct form that is relevant to their current situation to aid their survival and mission success. Task 1 will develop XMPP-based chat services accessing information in documents via a remote CHATBOT interfacing with (existing) federated search capabilities and (to be provided) Natural Language Processing (NLP) capabilities. Task 2 shall address the need to access remote intelligence data via a CHATBOT with suitable machine reasoning capabilities. Who Are the Users (Task 1) As a tactical user, via a radio link and using an existing Chat-application, I need to be able to search documents available at multiple remote locations, without knowing where they are, and be able to find information and intelligence that is relevant to my current situation without downloading whole documents, so that my mission success likelihood is improved. (Task 2) I need to be able to access intelligence products in the Single Intelligence Environment Demonstrator, and either download a compact product, or by dialogue retrieve facts/intelligence assessments about pertinent Objects of Interest (OOI). Early Market Engagement Not Applicable Work Already Done Prior research has produced a Federated Search capability, available openly at https://github.com/dstl/Open-Federated-Search (supplier may provide an alternative). The Single Intelligence Environment Demonstrator exists on a Dstl private cloud and must be used. Its capabilities and APIs are fully described in an Open Architecture document, which will be made available to those who are invited to submit a full proposal. It includes a Knowledge Base, which stores intelligence about Objects of Interest (OOI). GraphQL is used to access the Knowledge Base, returning a JSON-LD graph (an array of JSON objects, each providing some intelligence about an OOI). Existing Team The supplier team will work with User representatives (comprising Dstl, its Military Advisors and selected stakeholders) to ensure that the capabilities developed by the supplier are relevant to the military need. These User representatives shall also be invited to take part in a user-evaluation of the solution. No other contractors will be involved. Dstl will appoint a "Technical Partner" who will provide liaison with User representatives, provide technical advice to the supplier and to the Dstl Project Manager regarding technical choices proposed by the supplier, and technically review outputs for acceptance purposes. Current Phase Alpha Work Location Development anywhere in UK. Demonstration at either of the DSTL sites at Porton Down or Portsdown West. Working Arrangments Software development should be done offsite with unclassified data, including on public clouds. The solution should be transferred to Dstl's private Official-Sensitive Development Cloud (D-CLOUD) for system testing, evaluation and demonstration. This transfer should be via Docker containers. Dstl's D-CLOUD provides Windows 7 and Centos 7 VMs. Task 2 should start with a military requirements activity to agree what intelligence questions the tactical user may require to be answered, and what intelligence products and intelligence data can be generated by the supplier in the SIEC Knowledge Base to satisfy such needs. Fortnightly virtual Agile review meetings with Dstl. Security Clearance HMG Baseline Personnel Security Standard clearance is required for members of the team who need to access the Dstl Official-Sensitive cloud environment (which is where the demonstration and evaluation is required to take place towards the end of the project). Additional T&Cs These include: - DEFCON 76 (EDN 12/06), DEFCON 501 (EDN 05/17) – (Note only to be used when interpreting the DEFCONS), DEFCON 531 (EDN 11/14), DEFCON 608 (EDN 10/14), DEFCON 611 (EDN 02/16), DEFCON 649 (EDN 12/16), DEFCON 658 CYBER, DEFCON 659A (EDN 02/17), DEFCON 705 (EDN 11/02). Further additional T's&C's may be included in the ITT issued to shortlisted suppliers. Skills & Experience Experience of working with Chatbot frameworks .The supplier has provided evidence of working with one or more CHATBOT framework which one(s) were used and why. ( Weighting 35%) Experience of doing Natural Language Processing, Machine Reasoning/Machine Learning. The supplier has provided evidence including details of systems/services/methods used. (Weighting 35%) Experience of using XMPP. The supplier has experience of using XMPP and has provided evidence to support this. (Weighting 5%) Experience of software development, including working under a defined Agile development methodology and in a defined DevOps environment. The supplier has provided detailed evidence to support this. (Weighting 15%) Nice to Haves Experience of using communications link emulators. The supplier has provided evidence of their experience. (Weighting 5%) Experience of software development and delivery using Docker containers. The supplier has provided evidence of their experience. (Weighting 5%) No. of Suppliers to Evaluate 6 Proposal Criteria Understanding the requirements. Full details to be provided to shortlisted suppliers in the ITT The merits/limitations of the proposal. Full details to be provided to shortlisted suppliers in the ITT. Merits/limitations of proposed chat client/server applications. Full details to be provided to shortlisted suppliers in the ITT. Utility of proposed Natural Language Processing/Machine Reasoning capabilities to deliver Tasks 1&2. Full details to be provided to shortlisted suppliers in the ITT. Suitability of the proposed radio channel emulator and proposed channel characteristics to be emulated. Full details to be provided to shortlisted suppliers in the ITT. Suitability of the proposed industry supplier collaborative team. Full details to be provided to shortlisted suppliers in the ITT. Acceptability of plans for system test, evaluation, and demonstration. Full details to be provided to shortlisted suppliers in the ITT. Suitability/cost of proposed arrangements for future development by the Authority. Full details to be provided to shortlisted suppliers in the ITT. Presentation. Full details to be provided to shortlisted suppliers in the ITT. Cultural Fit Criteria Evidence of working collaboratively on research tasks in an Agile manner to maximise the useful capabilities of solutions whilst keeping costs to client(s) down. The Supplier has provided evidence. Supplier held proprietary capabilities utilised for the delivery of this task, should be offered to the Authority for research purposes (Under terms) both during and post-contract. The supplier has agreed. Provide evidence of your track record of rapid development of innovative software solutions, for research and demonstration purposes. The Supplier has provided evidence. Payment Approach Capped time and materials Assessment Method Written proposal Case study Work history Presentation Evaluation Weighting Technical competence 50% Cultural fit 20% Price 30% Questions from Suppliers Budget range the total available budget for tasks one and two is £700,000. the maximum available budget for each task is up to £350,000. a supplier must not exceed the maximum budget available per task(maximum £350k). task 1 : up to £350k task 2: up to £350k