Digital Delivery · Industrial Automation & Control
From an optimised process to reliable operational control.
Somos-Co combines process expertise, Dynamic Modeling, software engineering and OT/IT integration. We design and deliver automation and control solutions, integrate them into existing system landscapes and support the journey from simulation and commissioning into operation.
Three connected areas of accountability: Management Consulting defines and validates the target, Digital Delivery implements software, integration and control, and Operations and Hosting sustain operation and improvement.
Management Consulting
Digital Delivery
Operations & Hosting
Connecting consulting and engineering
Automation does not begin with control technology – it begins with understanding the entire system.
A local automation measure does not automatically improve the overall outcome. Somos-Co connects business objectives, process dependencies, equipment behaviour and technical architecture. This allows us to validate where automation creates real value before implementing control logic, software and integration.
A clear distinction
Two forms of automation – one connected target system.
Business automation and industrial control can share data and interfaces, but they solve different problems. This capability focuses on production and equipment processes.
Complementary capability
Business & Workflow Automation
Design digital, rules-based, document-driven and data-driven business processes through applications and integrations.
- Digital business processes
- Workflow automation
- Rules-based flows
- Interfaces and system integration
- Document-driven and data-driven processes
Focus of this capability
Industrial Automation & Control
Develop and integrate production and equipment processes through control, operational visualisation, simulation and explicit OT/IT boundaries.
- Machine and process control
- OT/IT integration
- HMI, SCADA and MES connectivity
- Sensing, operational data and edge systems
- Virtual commissioning and simulation
Capability portfolio
From the control concept to controlled improvement.
The capabilities form one connected delivery path. The specific scope follows the process, equipment, system landscape and accountability model.
01
Automation and control concepts
Connect business objectives, process requirements, equipment behaviour and technical constraints in an implementable automation and control concept.
02
Process and equipment simulation
Analyse production flow, capacity, control strategies, buffers, disruptions and alternative operating modes before implementation.
03
Control and software engineering
Develop, test and document control logic, operational applications and technical components in a structured delivery process.
04
OT/IT integration
Connect machines, control systems, supervisory systems, production platforms and enterprise IT through clearly defined interfaces.
05
HMI, SCADA and operational transparency
Make equipment states, process values, alarms and operational decisions understandable to the people responsible for them.
06
Testing and virtual commissioning
Validate control logic, interfaces and operating scenarios against simulated or controlled system states as early as possible.
07
Commissioning and handover
Transition the technical solution into production in a controlled manner and hand over responsibilities, documentation and support paths transparently.
08
Operations and continuous improvement
Use operational data, incidents and performance indicators to continuously improve automation, availability and process performance.
End-to-end delivery flow
Each phase creates a testable basis for the next.
The management decision, model, control architecture and operation are not treated as separate projects. Outcomes and accountability boundaries remain visible throughout the flow.
Six connected phases: understand the process, simulate behaviour, develop the control concept, implement software and integration, test and commission, then monitor and improve.
Understand the process
Simulate behaviour
Develop the control concept
Implement software and integration
Test and commission
Monitor and improve
Reference architecture
Separate control, operational systems and platform responsibilities clearly.
The layers show a vendor-neutral target picture. The specific architecture follows equipment behaviour, real-time needs, safety requirements and the existing system landscape.
Five stacked layers connect field equipment and control to operational systems, integration, and enterprise and platform services.
Layer 5
Enterprise & Platform
Layer 4
Integration
Layer 3
Supervisory & Operations
Layer 2
Control
Layer 1
Field & Equipment
Operating boundary
Time-critical machine control is not a generic cloud workload.
Time-critical control remains where process and safety requirements need it. Data, integration, monitoring and management components run in the most appropriate edge, on-premises or cloud model.
- Central data and integration platforms
- Monitoring
- Historian and analytics components
- Management and reporting applications
Application areas
Typical questions across production and operations.
These examples are illustrative application patterns, not claims about a specific client engagement, installation or achieved result.
- 01
Production flow and equipment capacity
Illustrative
- 02
Automated material and order control
Illustrative
- 03
Tank, buffer and inventory control
Illustrative
- 04
Machine and line integration
Illustrative
- 05
Condition-based monitoring
Illustrative
- 06
Quality and yield optimisation
Illustrative
- 07
Energy and resource efficiency
Illustrative
- 08
Alarm and event management
Illustrative
- 09
Virtual commissioning
Illustrative
- 10
Operational decision support
Illustrative
Evidence and claim boundaries
What is documented today – and what remains a target picture.
Somos-Co separates documented first-party experience, anonymised modelling work and illustrative architecture. This makes the basis of every statement visible.
- DocumentedFirst-party
Solar Tracker: control, telemetry, a digital twin and operations
The owned venture documents physical tracking prototypes, control logic and firmware, sensing and IoT telemetry, a user application, a digital twin, plus deployment, monitoring and backups. Simulation and measurement are reported separately.
- ModelledAnonymised project experience
Compare production flow and system effects before implementation
The Dynamic Modeling portfolio documents anonymised questions involving capacity, throughput, lead time, WIP, cost and bottlenecks. It shows model outputs and KPI types, not promised client results.
- Illustrative
Vendor-neutral OT/IT reference architecture
The layered diagram on this page shows one possible integration flow from Field & Equipment through Control and Operations to Enterprise & Platform. It does not depict a real client installation.
Not presented as existing evidence
Vendor, safety and performance claims remain project-specific.
The published evidence does not establish general capability for specific PLC, DCS, SCADA or MES products, nor any formal safety or industry certification. Those statements require their own project documentation or certificates.
- No vendor certifications or product-specific capability commitments
- No functional-safety certification or IEC 62443 compliance commitment
- No blanket 24/7 operation or guaranteed availability
- No regulatory validation or specific industry approval
- No unsupported installation counts or performance improvements
Next step
Plan automation from the perspective of the entire system.
Discuss the process objective, equipment behaviour, existing OT/IT landscape and the decision that must become defensible before engineering begins.