top of page


Emergency service response systems are a critical component of any nation’s healthcare and security systems. 

Minutes or even seconds can mean the difference

between life or death.

S E C O N D S   M A K E   T H E   D I F F E R E N C E   
B E T W E E N   
L I F E   O R   D E A T H




UNITY EDMS™ is a software server suite that services the broad needs of Emergency Management and cooperation

type industries by providing a solid browser-based interface to manage and monitor all aspects related to the

documentation and real-time interfacing of Situational or Incident-Based environments.

Core Facilities include

  • Call Taking/Capturing

  • Resource Management and Dispatch

  • Google Maps incorporated into the native GUI with GEOJSON support

  • Easy interface for creating/changing markers and geo-fences.

  • Resource and Asset management (Vehicles, Staff, and Buildings)

  • Real-time Interactive Dashboards

  • Scalable Redundancy and backup features

  • Full Cloud/Local Cross-platform deployment

The software utilizes Connection Hive™ techniques to establish and maintain free-flowing links between various hardware modules, such as Data Servers, Mobile Data Terminals and all other Software endpoints that ties into the current infrastructure.

Access to the system is not limited to internet (TCP based) connections but can interface with local hardware to employ Least Cost Routing of information by means of Digital Radios, LoRa, GSM and WiFi, connecting at the core server and at devices such as MDTs (Mobile Data Terminals) and Cellphone Apps.


An API layer is included to allow access via different connection methods, like WebSockets, REST APIs, and Network Sockets to interrogate and influence the system.

The UNITY CORE module employs HTTPS protocols to encrypt data end to end when connected over WiFi, 3G, LTE and converts to using a proprietary key encryption/decryption protocol when low-level connections are active like LoRa and GSM.


UNITY EDMS™, developed alongside the Coltron Tornado MRCC™ Communications Switch (Multi-Role Communications Console) natively integrates the communication environment with Incident Management to ensure that capturing of ‘Caller ID’, ‘Login-Forward’, ‘Call Answering’ and all other basic radio functionality can be used within UNITY EDMS™.


Apart from the CORE that hosts and delivers the platform to the end-users, UNITY EDMS™ has the ability to seamlessly integrate additional modules in order to expand the system's capabilities and customization in accordance with end-users’ requirements.




The platform was developed on NodeJS and Lubuntu and leverages native modules in the browser environments to achieve fast and continuous communication.


The solution is serviced with a MySQL database to keep licensing requirements to an absolute minimum. This used as it is the basis of most internet servers and therefore suitable for the application.




CORE Server

The following services are included in the CORE Server Services -

  • File Serving (Media and Host Files)

  • Application Serving (Capture and Dispatch GUIs)

  • Net/WebSocket Communication

  • Serial / RS 232 Communications

  • Data event-based routing

  • Integration REST API

  • Robust module management functions and data routing

  • Inter-Server communication/duplication



CORE Browser Application Facilities –

Call Taking/Data Capturing

  • Resource Management and Dispatch

  • Active Incident Handling

  • Integrated Google Maps/OSM overlays System

  • Map and Overlay management

  • Staff and Asset Management

  • Manual Staff/Asset Rostering (Daily)

  • Real-time Current Open Incidents Wallboard

  • Real-time per incident timeline wallboard

  • Detailed and Summary "One-Click" reports

  • Automated Scheduled Reporting and Emailing



Modules included in the UNITY CORE Module


Incidents Management Module

Responsible for collecting data from the capture and dispatch interfaces and route data to any monitoring endpoint (Like Dashboards and Wall Displays)

The main ability of the module lies in the ability to notify the CORE and all or some of its connection endpoints about data updates virtually instantly.


Notifications Module

Enables the CORE system to send SMS and email notifications, receive messages via hardware routes. It also manages the notifications of pre-set groups of people and far-end devices like remote fire bells with their required protocols being programmable via the browser interface.


Logs Module

Built as a tool to enable diagnostics of the system and its various components. Keep real-time logs of system events and automatically identifies problems within all the code running. A preventative module to ease the mind of the end-users when trusting a system to always work.



Redundancy Module

Listens and catches all requests and responses between the currently active servers and redistributes the events to pre-defined hot-clone servers that are ready to take over at a moment’s notice. Service interruptions will seem invisible as the endpoint applications automatically switch to redundant servers.

This module also recovers data from redundancy points and notifies the endpoints to switch back once operation on the main server can resume.


These modules and the CORE server application is all that is required to set up a functional
and operating call taking and dispatch centre. Additional modules exist that expands the capabilities of the system.




Mobile Data Terminal Management Module

This module handles all communication between operators and MDT units. The module is responsible for collecting all data messages that pertain to connected devices and forwarding them to the incidents module for processing and event triggers within the software. In turn, it also collects all responses/messages/instructions from the operator endpoints and forwards it to the correct MDT unit. This module comes bundled with UNITY EDMS™ if our MDT units are used to interface with.


MDT Applications

The MDT itself is a dashboard mounting tablet unit that runs Android/Linux as the operating system.
The main interface is a browser-based GUI that runs on TCP/IP GSM but can be extended via hardware within the vehicle to employ least cost routing via existing infrastructure such as DMR radio networks and RAW GSM/GPS units by means of a hardware add-on.

Features of the MDT Application:

  • Login/Logout Automated Rostering

  • Instructions Receive and Respond

  • Incident information and to-center progress updates

  • MDT network text communication

  • LoRa Network Communication

  • UNITYChat (if the comms module is installed on the server)

  • GPS Tracking


GPS Tracking Module

Couples with the MDT Management module to report the locations of all GPS pings received from endpoint devices. This module can be installed separately and hosts its own API for external developers to use with their own systems.


ILP GRID™ (Informal Location Protocol Grid)

This module enables the administrator to generate and define a custom grid over an informal settlement on the map and give each block a short alpha-numeric address. This grid becomes available via mobile or desktop browser so that members of the public can view their own generated address based on GPS coordinates.


During emergencies, residents of informal settlements can give this ILP address and our maps will point to the exact block under that name.

The mobile interface allows for service staff to pinpoint the ILP address while out in the field too, for instance, mark homes with their corresponding ILP marker address.


HOIF – Hospital Interface Module

An interface module to allow existing Hospital systems to report the availability of:

Number of beds

Number of ICU bays

Number of trauma bays

Number of Operating Theatres

Number of ER Doctors on duty


JOC Management Module

The JOC Module is a set of GUI interfaces that enables a group of people spread apart geographically to collaborate on planning and deployment of resources using Map Environments, Geo-fencing Tools and Quick Resource creation to represent real-world resources being moved or actioned to the task.


The environments allow each user connected to use the map to send suggestions to the other JOC users about where vehicles should be moved to, what staff should be active in created fences and then using pre-defined structures enable authorization to members of the JOC to approve suggestions made by the various parties.


Should it be that no overriding authorization has been selected, all suggestions go to an interactive ‘Quick Vote Box’ that actions the suggestions with the most votes. Giving all members of the JOC equal say via a vote of the majority to action events.


All actioned events and instructions automatically get routed to MDT units and call centre operators as live updates to their map environments in front of them.


JOC Module feature shortlist


  • Incident Tracking and Reporting

  • Advanced mapping and tools environment

  • Collaboration between logged in members (Same Room, Same Network or

Over the internet)

  • Vote and Action Management System with overriding authority ability.

  • News Feeds

  • Weather Feeds

  • Video Streams (If Command Center Module is installed)

  • Social Media Streams (If Social Media Integration Module is installed)


Social Media Integration Module

Another set of functions that enables operators to accept SMS, WhatsApp, Facebook and Twitter messages as incoming incidents and pass it off to dispatch. The SMI module can host an unlimited amount of accounts to interact with.


Features of the SMI module:

Social Media/WhatsApp Message/SMS to Incident

Separate Filtering GUI to enable manual filtering of incoming messages

Social Media Tag/Search Algorithm tracking and display GUI

Social Media Interaction GUI to respond broadly to multiple accounts at once

Enabled to use Natural Language Processing to extract relevant data from messages


IoT Integration Module

The internet of things has become a part of everyday operations and gives us valuable insight into our surroundings.


This module can interface with various types of IoT networks to deliver dashboards that can monitor anything from the fuel levels at depots to the weather conditions in specific areas.


The module allows the user to drag and drop sensor monitors of sensors that have been connected to the system via some or other network connection.


‘Things’ like Dam water levels, Water Tank levels and other related environmental ‘Things’ can give vital information to the Emergency Controllers to know if certain solutions are available to them during the span of an incident.


IT Network Monitoring Module

This module does not necessarily fall into the same category as the other modules connecting to the CORE but performs various functions to enable IT or Ground staff about Network and Device health with real-time audible alerts and notifications via SMS, Email and other methods.


It tracks and reports Server, Computer and Router outages with programmable labels to know exactly where the ‘disconnect’ has happened.


The module hosts its own GUI and has a special user type available to restrict IT workers from affecting or view other parts of the system.


Work Order Management Module

  • Enables long term management of low-risk incidents and also enables a separate MDT user interface for service workers on the ground.

  • Operators can assign for instance a clean-up task to a service crew that could take days.

  • Manages and reports any changes and tasks completed.

  • Integrates natively with the notification module of the core to notify all parties involved of work orders being issued and when their status changes.


Chained Redundancy and Backup Module

This module pushes data to a chain of redundancy “Clone” Servers which ports all events and records in real-time.


In the event that the main server loses connection for any reason, the various modules connected to the core will automatically fall back to the next server in the chain.


Once the main server recovers connection, it will first update itself with all new data and notify the other modules that it can be used as a primary server.


This differs from the normal embedded redundancy measures by enabling automatic hot-switching between machines spread apart geographically.


RTC Comms Module

This module enables Text, Audio and Video Chat across all GUIs and MDT’s.

It establishes connections either over the Internet or via a Local Intranet.

All online users are able to use the facility to coordinate and layout tasks needed to manage an incident as this module employs IO Signal Pooling™ to establish peer-to-peer communications.


The module can be deployed on a separate server for conferencing via the COMMS module.


Block-Chain Storage Module

Block-chain methods ensure that records can be verified for years after they were created.


The module collects all records and events in real-time and adds it to a secure block-chain file that can be backed up and verified using the module tools.


The major benefit of this module is its ability to port the block-chain and any new additions to other connected systems using decentralized connections.


With the Client App-enabled, all records generated across all connected systems/sites are consolidated and spread among its peers.


Deployment Options

The system can be deployed as a cloud or a localized solution. The CORE and modules may reside on the same hardware platform or can be split up into different regions of a network/VPN to accommodate redundancy rules as defined by the end-user.


The free-form installation allows the system to chain CORE servers to alternate installations in order to duplicate all events and messages sent on the main system in real-time.


In the event of hardware failure, the endpoints will automatically switch to the next server in line and use that to continue operations with virtually a seamless switch over.


Security Protocols Used

All communications between modules, endpoints, and operators are encrypted by HTTPS certificates as default.


Information can be transmitted on various network topologies without concern of espionage or sabotage of information with confidence.


POPI Compliance

The system can be programmed to adhere to the POPI laws by destroying data older than a certain time frame automatically, but can also be switched off manually for sites that require long term or indefinite record keeping.


No data captured by the system phones home and stays within the operating network. It does not get parsed or captured for speculative or marketing purposes and actively guards personal information stored on the system with watchdog scripts that detect intrusion and manipulation attempts.


Self-protecting mechanisms will report any unwarranted actions taken or introduced throughout the system and the hardware connected to it.



In order to service the need to accept instructions and data from any external system, a multi-tier API is exposed to enable other developers to interface with the data on the system.


The Unity system exposes a native Socket Server, a WebSocket server and an HTTPS POST/GET server as methods to interface with the data. This enables most languages and script engines to access and affect data.


The API is protected by manually issued ID tokens, to ensure that validated software can interface at that level.


Encryption on native sockets is disabled at this level, due to the range of communication methods and the need to simplify integration.


Alterations to the Protocol can be effected to accommodate any vendor requiring to encrypt data between their application and the Unity servers.


bottom of page