Inspections Roadmap highlights and priorities
When an organization has multiple questionnaires, they often share identical sections. Components library allows to quickly reuse and manage these sections, which can consist of questions, groups of questions and corresponding logic.
The information collected by field teams can be reviewed and evaluated with our web-based analytics tools. We aim to provide a clear-cut overview of the collected data for a specific questionnaire and show statistics and insights for the entire set of available data. Moreover, with a help of machine learning engines, we want to help you identify the patterns in your collected data and make better-informed decisions.
Flowcharts and decision trees
As our Questionnaire Designer is used predominantly by business users, it is necessary to find a balance between the flexibility it provides and general ease of use. We believe that focusing our efforts on more visual questionnaire modelling, where the relationship between questions and the overall flow of the questionnaire is visible at the first sight, will improve the experience with the creation of any template.
All features and details
When a company utilizes a higher number of questionnaire templates, the Designer landing page might become somewhat crowded. To resolve this, on top of a search bar and status filters, one will be able to organize their templates within different folders. A functionality well known from any other software programs or tools, where users can create simple or hierarchically structured folders, and move and import items within them.
Every inspection process has a different scenario. Not all questionnaires have to be completed and then have a report run from them necessarily in this order – that’s why the users designing the questionnaires need a range of options in what actions the questionnaires should result. To define the commands and their execution, it will be possible to use a Command editor directly in the questionnaire template.
The process of designing a questionnaire can result in complex inspection questionnaires, with multiple different paths and complex logic. The ability to immediately test the questionnaire as a preview – as the user would see it in the mobile application – will make the design process significantly more effective. The preview will be part of the browser experience, directly launched from the Designer.
There are many different scenarios where the inspector’s hands are not free and many of them would benefit from displaying information in the user’s field of vision. Augmented Reality devices, such as Microsoft HoloLens and others, could prove useful. An application UI/UX optimized for this type of devices will be developed. Users will be able to visualize inspection questions one by one (question after question) and theit head movement will indicate an answer (yes/no) or launch voice recognition.
Additional question types
Different organizations have different requirements. To capture the different types of data these organizations need, we’ll provide additional question types such as:
- Rating to be able to rate a product or a service in a visual way (e.g. 1-5 stars)
- Table to be able to select multiple options from a database table (e.g. select all products the customer is interested in)
- Progress bar within the questionnaire to show how much is still left to be answered
- Augmented reality item (e.g. location-based annotations)
- Map item question for selecting and recording a location on a map
- Numeric range question with custom values in a fully configurable slider
Images represent a valuable data set, especially when combined with advances in the field of artificial intelligence. An existing database of pictures of products, assets, or machines can be used in conjunction with image recognition to identify the object captured in a photo. This can be then used in lookup questions to select the corresponding record (product, asset, etc.) by taking a picture and/or to start the entire process by it. Utilizing Azure Machine Learning (Azure Custom Vision) should provide a convenient technological basis to build this feature.
Components library – Composite components
Snippets streamline the process of reusing portions of a questionnaire, but they lose connection to the original snippet the moment they are pasted. This means that modifying the original and thus making a change to all occurrences of a snippet pasted into multiple questionnaires is not possible.
Composite components resolve this issue. They remain connected to the original component, so all future updates to the component are reflected in all questionnaires, where this component is used. A composite component is a ‘black box’ which has inputs and outputs. Once inserted into a Questionnaire it remains non-modifiable, so future changes to the component are possible only in the Component library.
Localization (Language support)
In an environment where an organization operates in multiple countries, or in a country with multiple official languages, it is usually required to manage the same questionnaire, but in different languages. This means having the same questions and the same logic, but the texts – question labels, descriptions and answer options, etc. should be available in multiple language variations.
Our goal is to incorporate this localization directly into the Designer, so different text versions can be handled there. Also, an export/import function will be available for efficient translation setup.
Pages and decision tree
Many questionnaires are structured as process dialogs or wizards. They take the inspector through the process step by step, displaying one or more questions at each step and each answer possibly affecting which step in the process will follow.
In Resco Inspections, we will simplify the modelling of this approach with Pages. At any given moment, only one page is displayed. Each page can display one or more questions and question groups. Based on a precisely defined decision tree, a set of answers on one page might lead to a certain page being displayed next. If the answers are different, a different page will be displayed next.
The decision tree driving the process is a key element and will be displayed in a specific interface allowing visual representation and editing – so the relationships between pages are immediately apparent.
Building on top of voice control, we plan to incorporate conversational interfaces for filling out a questionnaire. Like the standard voice control, a conversational interface allows the user to provide answers into the questionnaire. The main difference is that instead of using keywords, the user interacts with the questionnaire using standard phrases (such as “I’m opening the machine.”). The conversational engine detects intent in the phrase which corresponds to a question or a step (“Open the machine”) and automatically fills in the answer (“Done”). Additionally, the engine can continue the interaction, outlining answer options or next questions (“Is the machine operational?”), similarly to chatbots.
The importance of document version control stems from the fact that most documents go through a lot of revisions and editing, especially digital documents in which revisions are difficult to track. And this is not different for the questionnaire templates in Resco either.
Versioning allows the administrators in charge of questionnaire design to keep track of questionnaire edits, and various versions that have been in use over the time. It will be possible to go back and use one of the archived versions, in case a change needs to be reverted. All other functionalities, such as for example reporting and analytics, will be adapted to the new versioning structure, if necessary.
Reuse answers from previous questionnaires
When re-visiting an inspection site, some inspectors would like to see the answers from previously filled out questionnaires to be able to either use the answers as a benchmark or reuse them if there is a little chance of having to modify the answers again. By implementing this feature, we would allow the admins to easily set up a fetch that would pre-fill the answers from their previously filled out questionnaire in the app or select the answers from any other questionnaire based on the exact use case.
Wearables offer a quick way to improve the efficiency of inspections. A smart watch can be used to quickly check in or check out of a job. Integration with voice control will allow answering simple types of questions that don’t require complex inputs.
Resco’s Roadmap might be subject to change. The outlined features may be modified or updated before commercial release. Resco makes no warranties with respect to the information provided.
The work on this feature has already started. The expected delivery date in next release (usually March, June, September or December), but if the feature is more complex it might require two release cycles to be completed.
The feature has been implemented and will be released in Resco’s forthcoming release (next: December 2019).
This feature is on Resco’s roadmap and is waiting to be picked up by the development pipeline to get implemented.
The feature has been released in last Resco’s release (Version 12.2 – September 2019).