Expertise
A sequence that will not let an incompatible state through.
PLC, HMI, SCADA, supervision and integration.
Design the logic, not just wire the controller.
An automation function is judged as much by what it prevents as by what it allows. We write the specification, program the controller, develop the operator interface, design the communication architecture, then run the testing and commissioning through to start-up.
What we do
From specification to start-up, on a new installation as well as an existing one.
- write or review functional specifications, and carry out basic design studies
- program the controllers, and take over or modify an existing program
- develop the operator interfaces
- design the communication architecture between equipment and systems
- turn an expected operation into states, sequences, conditions and time delays that stay coherent with one another
- run the testing, commissioning and start-up assistance
- contribute to the qualification and validation activities planned for the project
Taking over an existing program is a capability in its own right. An installation in service is rarely modified from a blank sheet.
In which situations
The starting point is an operation to guarantee, not a controller to program.
- several access points or units must operate under coordinated rules
- a sequence must prevent an action incompatible with the current state of the system
- an opening must depend on a time delay or on differential pressure control
- an automation function must be added to an installation in service
- system states must feed an existing BMS or EMS
- teams must be able to change a threshold or a delay without calling us back
These are entry points, not an exhaustive list.
With what
Documented technical building blocks, assembled to the need.
- door-to-door cascade logic, time delays, differential pressure thresholds and configurable opening and closing delays
- state inputs: door position sensors, pressure control
- interfaces to the existing estate: access badge systems, fire alarm panels
- a web interface secured by login and password, on a protected URL, with no additional software
- a data feed over Modbus TCP or Profinet to a BMS or EMS
- the platforms we work with: TIA Portal and WinCC, Siemens, B&R, Allen-Bradley, and Kepware for data exchange
These names describe a context of experience. They imply no partnership, no certification and no exclusivity: the choice of platform belongs to the project and to what is already on site.
What it produces
A system that holds, and that can be operated.
- an operation that rules out incompatible state combinations, without relying on operator vigilance
- a written functional specification the testing can be anchored to
- an operator interface designed for the people who live with it
- a configuration your teams can change, locally as well as remotely
- state histories that can be used for qualification activities
- integration with the rest of the site rather than one more technical island
A data feed and a history are not a supervisory interface.
Can you take over an existing PLC program?
Yes. Taking over or modifying an existing program is a capability in its own right: an installation in operation is rarely modified from a blank page. We review the specification, analyse the program in place, add or correct the expected function, then run the tests and the commissioning. The platforms we work with include TIA Portal, WinCC, B&R and Allen-Bradley; the choice belongs to the project and to what is already on site.
Does a sequence have to guarantee an operation, not just automate it?
Describe the access points or units involved, the states to coordinate and the conditions to respect. An initial discussion will identify the logic to design and the interfaces to check.