Minor changes made so far this year focused on improving Risk functionality and enabling end to end use of ScCapture, ScCourier and ScResponse. We have additional development relating to the Hydrant functionality in ScCapture planned for 2017. This development will be focused on changes identified by Hydra users at the User Forum.
With most of our efforts focussed on core ScResponse and ScCourier functionality over the last twelve months its worth giving an update on where our development efforts will be targeted next.
ScResponse & ScCourier
The version 2.1 release will be available in July as mentioned earlier. For the remainder of 2016 we will be focussing on supporting the deployment of ScResponse & ScCourier and gathering feedback for the 2017 development plan. Based on demand we may begin development of an Incident Command Module for ScResponse so would be interested in your feedback on this (see below).
We are progressing with the development of ScGuide, our messaging component for the TomTom Bridge device. We expect the ScGuide application will be ready for deployment in October 2016.
Key features in ScGuide version 1:
- ScGateway login
- Mobilisation messaging
- Status messaging
- Initiate TomTom navigation
- Incident location display
- Incident details display
- Remove incident location
The ScGuide application will connect directly to ScGateway and will not require TomTom Webfleet. This Android application will provide us with better control over the message traffic and full control over the mobilisation workflow on the device.
We can, of course, continue to message TomToms via Webfleet or mobilise directly to officer radios through ScGateway should either options be required.
We are exploring the further development of ScResponse to provide enhanced Incident Command functionality. Below is a list of future functionality that is currently in the roadmap as candidates for future releases of the ScResponse product. The list is not definitive and the exact functionality and workflow may change as a result of working collaboratively with the ScResponse Incident Command Working Group:
- Place / Remove Cordon (Basic Hazmat);
- Place / Remove Cordon (Advanced Hazmat);
- Send Basic Cordon to others as a message;
- Send Hazmat Cordon to others as a message;
- Add Multiple Cordons;
- Send/Receive Redline layer as a message over ScGateway;
- Command Structure creation and automation;
- Display other vehicle\officer mobilised, in attendance and deployed;
- Display Crew Riding information;
- Mapping control use multi-touch for pan/zoom/select functionality;
- Text to speech so all crew can hear key text from on-screen;
- Positive Delivery Notification - allow user to set a flag against a message so the system actively reports progress on it;
- Peer to Peer messaging;
- Support cloud and local data sets;
- Collect incident information via pro-forma;
- Send incident information as a message (over ScGateway);
- Deliver incident information to third party system.
The Incident Command Module for ScResponse has been designed to be installed on all appliance MDTs, to enable the first responders to immediately start planning in reaction to an incident by knowing which other crews are on route, initial cordon planning, access to risk information, etc.
Once the Incident Commander arrives on site, they will immediately be able to see who has been allocated to the incident, their status and location and the actions taken and messages exchanged already, thus minimising the time required to “get up to speed”. At that time, plan ownership can be easily transferred to the Incident Commander.
Building on to ScResponse ensures Incident Command has access to the communications functionality provided by that product. All items added to the Incident plan, will be relayed to all mobilised ScResponse Incident Command enabled resources ensuring the plan data currency is near real-time and not time delayed. All data messages sent via ScGateway, between mobilised resources, will be available within SIC Message Log to give the Incident Commander a complete overview of the incident’s history and current position.
In summary, selecting Airbus Defence and Space and SAFEcommand for your Incident Command solution will ensure that you maximise your existing investment in the SAFEcommand suite of products by deploying a fully integrated solution that provides best value and minimises training and data migration, allowing for a seamless deployment.
For more information about the product roadmaps please do not hesitate to log a call with the service desk. Remember you can see our product roadmaps on the SAFEcommand Portal and if any particular feature that you would like to see is not listed you can submit via the appropriate form in that Roadmap section.