Controls engineering from functional definition to commissioning.
TBC can deliver a complete controls package or a clearly defined part of one, with the interfaces, deliverables and acceptance criteria agreed at the outset.
PLC engineering
PLC software is developed from the operating philosophy and I/O, not improvised around individual devices. TBC structures modes, sequences, interlocks, permissives, alarms, diagnostics and communications so the code can be tested, understood and changed.
- Software architecture and standards
- Sequences, interlocks and permissives
- Communications and package interfaces
- Simulation, fault finding and controlled backups
Issued with agreed naming, revision history and test evidence.
SCADA & HMI
An operator should be able to see what the plant is doing, why it stopped and what action is required. TBC develops clear HMI and SCADA applications with consistent navigation, alarm handling, trends, data and diagnostics.
- Screen hierarchy and navigation
- Alarm and event presentation
- Trends, reports and data logging
- User access and operator workflows
Navigation, alarm priorities, tags, users and data functions documented for testing and handover.
Control-panel design
Electrical drawings should be complete enough to manufacture, test and modify without relying on assumptions. TBC produces control schematics, layouts and schedules that stay aligned with the functional design and software.
- Control schematics and layouts
- I/O, terminal and cable schedules
- Power supplies, protection and segregation
- BOMs, interfaces and manufacturing support
Schematics, layouts, I/O, terminals, cables and BOM information issued under revision control.
Power-management systems
Power-management projects depend on clear authority between mains, generators, switchgear, PV, BESS and third-party controllers. TBC defines and implements the sequences, permissives, load priorities and interfaces needed for safe, resilient operation.
- Generator and mains control
- ATS and synchronising arrangements
- Load shedding and restoration
- PV, BESS and third-party coordination
Control authority, breaker actions, load priorities and failure responses defined before testing.
Functional design
Good software starts with a testable description of what the system must do. TBC develops control philosophies, FDS documents, cause-and-effect and I/O/interface schedules that resolve ambiguity before hardware and code are committed.
- Control philosophies and FDS documents
- Cause-and-effect schedules
- I/O and interface schedules
- Testable acceptance criteria
Requirements written so each function, interface and failure response can be traced into FAT and SAT.
FAT, SAT & commissioning
Testing should prove the system against the agreed operating and failure scenarios, not just demonstrate that individual signals change state. TBC prepares and executes FAT/SAT, supports commissioning, records defects and closes changes into the final handover.
- FAT and SAT procedures
- I/O and communications testing
- Failure-mode and sequence testing
- Snag management and handover records
Requirements, outcomes, defects, retests and final software or drawing revisions kept traceable.
Have a defined package, an unresolved interface or a site problem?
Share the information you have and TBC can set out the engineering required, the likely deliverables and the next practical step.