On paper, two customers may appear to need the same technology. Once you look at how they operate, the requirements can vary widely.
That is why Sentiv starts with the working environment and the problem that needs to be solved. That means starting with use cases rather than individual products. Communications, IoT, security, and operational intelligence may use common building blocks, but their roles change depending on the environment in which they are deployed.
“The starting point has to be the operating environment,” says Louis Du Toit, CEO at Sentiv. “We need to understand the risk the customer is managing, how people work around it and what needs to happen when something changes. The technology follows from there.”
The operating environment comes first
Mining sites are difficult places to design communications around because conditions can change quickly from one area to the next. A system that works above ground may not be enough underground or at a remote section of the operation. Sentiv’s role is to understand those gaps and build around them, using the mix of communications, connectivity and monitoring the site actually needs.
A private security operation faces a different set of demands. The control room may need to know whether a patrol took place, where an officer is when an alert is raised and what happened during the response. Communications, location services, dispatch and digital evidence therefore need to support the same workflow.
The architecture has to reflect how the operation actually functions. Coverage, workforce structure, existing systems, and reporting requirements all influence the design.
Integration has to follow the workflow
Sentiv’s solutions cover mission-critical communications, workforce safety, command and control, digital evidence, connected operations and IoT, security, and resilient connectivity. The real benefit comes when those capabilities support the same operational process.
An alert is more useful when the recipient has enough context to act on it. A sensor reading has greater value when it feeds a process that can recognise an abnormal condition, reach the right team and retain a reliable record of what followed.
Sentiv’s industry approach also allows for the technology customers already have. In mining, for example, the company can manage a broader technology stack or interoperate with systems already on site. That flexibility is important because an industry solution has to work with the customer’s operating reality, not an imagined clean slate.
“Customers should not have to stitch together separate technologies and hope they behave like one operation. Our role is to understand the use case and bring together the capabilities needed to support it in a way the customer can operate and manage,” says Du Toit.
Industry knowledge changes the design
South African and African operating environments add another consideration. Connectivity can vary sharply between an urban site and a remote operation, while older infrastructure may still perform an important role. Budgets and regulatory requirements also differ across sectors.
That makes industry knowledge an important part of the technology decision. A solution designed around ideal conditions can quickly become difficult to support when it reaches actual site conditions and the people who have to use it.
For Sentiv, the aim is to build around how the organisation works. That may involve one focused solution or a broader managed environment, depending on the problem being solved.
It is therefore important to determine whether the technology helps people understand what is happening and act with enough information when pressure increases. Industry solutions succeed when the technology fits that operating reality and supports the response the organisation needs.
