Requirements and information flows
We define users, activities and information needs, identifying the sources and handovers that the software should support.
We develop software for industrial processes, connecting data acquisition, information management and operational control. We start with the decisions the system needs to support.
How we can helpIn an industrial setting, information may be spread across machines, applications and manual records. We first establish which data exists, how it is produced and what it needs to support. We define the relationships between sources, users and activities, distinguishing useful information from data that adds complexity without helping people do their work.
We design software around the process and the integrations that are feasible. The interface is only part of the system: every indicator needs consistent acquisition, organisation and interpretation behind it. We coordinate these elements with automation and investment planning, considering requirements, existing infrastructure constraints and funding opportunities relevant to the project.
We define users, activities and information needs, identifying the sources and handovers that the software should support.
We assess available connections, interfaces and protocols to link process data with other systems, within the capabilities of the installation.
We structure information and its relationship with databases, defining how it will be stored, accessed and used by the specified functions.
We develop operational screens and visualisations that make statuses, measurements and relevant information clear for the people using them.
We test the agreed flows and behaviours, including relevant error conditions and the consistency of the information displayed to users.
We define the deliverables around the agreed scope and objectives.
We examine users’ work and the available sources to define functions, priorities and the constraints on integration.
We build the agreed functions and connections, progressively checking how data moves through the system and appears in its interfaces.
We compare the software’s behaviour with the agreed scenarios and identify where further refinement may be needed.
We assess integration by examining interfaces, data access and technical constraints. Machines and applications vary in what they support, so the scope is defined after this review.
The choice depends on the context, existing systems and required functions. We select technologies during the analysis, rather than imposing a platform before the requirements are understood.
The appropriate update rate depends on the application and its sources. Availability, acquisition times and display requirements are assessed for the specific use case before the expected behaviour is defined.
Have a challenge to work through?