Delivery of a User Interface for Sensor-derived Data

Description

Summary of the work Development of a user interface to represent sensor derived data used within the Social Housing Sector. Expected Contract Length 3-6 months initially Latest start date Monday 9 May 2022 Budget Range The development of a new user interface has a budget of up to £40,000. Why the Work is Being Done AHS is in a partnership project with The Highland Council (THC) and NHS Scotland (NHS). A major component of the project is a pilot to install sensors into selected homes. Data derived from the sensors (the data) can be used by professionals to inform judgements about the welfare of participating residents. Captured and stored data must be presented to the participants in the programme to test a number of hypothesis regarding the impact that the capture and use of user data can have on care and other services in the social housing sector. The project is part of the Highlands City region Deal, funded by the UK and Scottish Governments through the Highland Council The development of a pilot version of user interface should be in place for testing by the end of July 2022. Problem to Be Solved The user interface must be able to represent the data and analysis of that data for presentation back to a range of end users including residents, carers, the medical profession and other authorised groups. Who Are the Users As a Carer/GP need to be able to view the information provided from data collected in patients homes to be able to determine care decisions. Early Market Engagement A very basic interface is in place currently accessible through a secure web page but that does not meet the needs of a range of users. Work Already Done Sensors are collecting data. Data is being analysed using machine learning by Robert Gordon University and the output is being used by a range of interested stakeholders including tenants, careers and service providers. The current interface is not sufficient for the continued roll out of the programme. Existing Team The successful proponent will be required to report to the Head of Innovation and the Project Manager. In addition the successful proponent will work with representatives from the health care services, GP's , the prison service and other stakeholders to determine interface requirements. Current Phase Beta Skills & Experience • Experience of user interfaces across a range of end user environments • Have experience of presenting information to users with differing needs Nice to Haves Experience of the Health, care or Social Housing Sectors Work Location Albyn Housing Society is based in the Scottish Highlands but the work is expected to be carried out remotely with some incidental requirement to attend the local area from time to time. Working Arrangments Weekly progress review and ad hoc face to face local meetings where discovery of user needs is required although this may be able to be completed remotely from some stakeholders. Security Clearance Not applicable Additional T&Cs Not applicable No. of Suppliers to Evaluate 5 Proposal Criteria • Technical Solution • Approach and methodology • How the solution meets user needs • How the solution meets the project aims • Expected timeframes for delivery • Identification of risks and dependancies • Team structure and skills • Value for money Cultural Fit Criteria • Have demonstrable ability to work across teams • Take responsibility for the delivery of their work • Challenge the status quo • be an innovator seeking to solve problems through creativity Payment Approach Capped time and materials Assessment Method • Case study • Work history • Reference • Presentation Evaluation Weighting Technical competence 50% Cultural fit 20% Price 30% Questions from Suppliers 1. What are the expected deliverables for the initial 3 months? Is this just for a pilot phase and you’re looking to test a prototype or are you expecting a fully developed replacement for your current interface? During the first 3 months, we expect to have a pilot interface which has been developed based on input from user requirements and be available to user to capture feedback on the effectiveness of the pilot interface. 2. 1 – Could you provide more information about what visualisations are available in the current solution2 – Could you give an indication of what enhancements and additional visualisations are required for the updated visualisation tool 1 - The current visualisations are very basic, providing a indicator of movement within a tenanted home.2 - The visualisations required in the User interface need to be informed by the users of the interface. The work will involve discussing user requirements for the interface and representing those requirements in the test version of the interface. Users will include tenants, carers, GP's and other stakeholders. Albyn will facilitate all stakeholder discussions with the successful proponent. 3. Can you please share any more details on the technical solution, how it exposes it’s data, API’s, etc? Currently the data is stored in an InfluxDB database, which is a time series data base.Ideally we would create a secure REST API to expose the data to the interface.The current system, using the Grafana web display, has direct access to the data as it is running locally on the same server as the data base. 4. Could we know what end user devices need to be supported. End users will have access to devices capable of accessing a web or App based user interface. Proponents should work on the assumption that different end user will access the interface with either a windows based PC or an Android mobile device. 5. As this is a Beta phase, what is the plan post-beta? Is there any requirement for a follow-on project to take you through go-live? The project is funded through the City Region Deal. User evaluation and impact of the information will determine whether we move to further development of the interface. 6. Are there any IP restrictions around the use of licensed software in the project? Do you expect a custom application to be developed which you will own post-project or are you looking for something to be built on an existing software platform that you would license? We would expect the proponents to offer the most appropriate solution to whether the software solution is built on an existing platform or custom built for this application. Albyn Housing Society expect that it will retain and own the IP for any custom software developed specifically for the use of this project. 7. Could we please know if the technology stack to ingest and store the data is out of scope. If not, could we know what is the mechanism to ingest the data. For example is the sensor data collected via Kara or stream technologies. Ingesting the data is out of scope. 8. Do you have any preferred technology stacks? For example, do you have an existing AWS or Azure infrastructure? Or is this an on-premises solution hosted on physical servers? We do not have a preferred technology stack. 9. How many different views do you expect will be required (i.e. do you need a different view for different user types; does a single user need multiple ways to view and analyse the data)? To be discovered in meetings with the end users. We will limit the requirements to those views which can be delivered within an agreed set of sprints. 10. Is it a requirement of this project to create the REST APIs to expose the data from the existing database, or will this be completed outside of this project in collaboration with the application development? It is not part of this scope to create the REST APIs to expose the data from the existing database as this will be completed outside of this project. 11. Is a single technical solution expected to work on both web and app contexts? Are equivalent visualisations expected on desktop and mobile devices? We would expect a web application to be the first step, and possibly as far as is required. This would mean it could essentially be platform agnostic and function across the various devices likely to be used by the targeted audience. 12. Is there a requirement for the display of realtime data? Yes. Real time data, or at least data with a lag of maybe a minute or so maximum, is readily available from the database and forms the basis of the "quick glance" usability of the FITHomes system. 13. Will the visualisations be based on raw data or output from analysis/ML (what variety of source data formats are there)? The main visualisations will be based on raw data, with the more analysed results from batched data of the previous day being shown as well. There is potential for doing more up to date analysis for a comparison of previous activity levels with levels so far today, for example. 14. Are there any specific accessibility requirements for the visualisations beyond the usual WCAG guidelines? (provision of an alternative/textual formats for example) WCAG is a definite must. There may be a need for offering the ability to view in large text/zoomed format, but this can be reviewed/discussed through user testing. 15. Will Albyn Housing Society Ltd provide user testing and interview participants for this project? Yes. 16. Can you give an insight into the kinds of features / functionality or requirements that would be included in the pilot user interface by July? Examples of the information and data it will present? Or scenarios involved? The pilot UI should have visualisations for current sensor activations, i.e. movement around the home, door open/close, etc. Potentially an indication of the last sensor activity, with time of last activity.There is also potential for the post-processed activity levels from the previous day(s) to be displayed. 17. Can we assume that the user interface should comply to GDS standards? Yes, the principles of the GDS standards should be targeted. 18. Can we assume we will be working directly with InfluxDB API queries only for the scope of this project? This will be confirmed, but it is likely that the majority will be using influxDB API queries 19. Are the custom visualisations expected to integrate with any other IoT reporting or dashboard solutions? No, at this time there are no expectations of integration with other visualisation systems. 20. Is development of the end-user mobile (Android) app out of scope? We expect the development to be based around a web application to ensure it is platform agnostic, thus OS based applications would not be part of this scope. 21. What does success mean for the project? How do we measure success and what are your KPIs? What are the end goals of the project? The goal for this scope is to produce a user interface which is easy to use for the various types of targeted user, intuitive to navigate, displays the relevant information clearly and is secure. 22. How is the project team structured?Who are the key stakeholders for this project? Organisation structureWho are the main decision makers? Are they the same or different? Will we be working with the main decision makers on a daily basis or are decisions made by an executive board or similar The main decision maker will be the Head of Innovation, but the wider FITHomes and innovation team will be able to provide support and guide the development. Input from our wider partnership working on the City Region Deal project will also be provided to assist the successful proponent.