The controller governs starting, stopping, monitoring, alarms and coordination, but a brand name alone does not prove fit. Define single-set, AMF, transfer, paralleling, remote communications and service boundaries before selecting a series and firmware.
Select the functional level from the control architecture and I/O list, then compare specific DSE, ComAp and SmartGen models, engineering tools, local capability and spares. Screen size is not a selection method.
1. Understand what this decision changes
The controller must match the power-system architecture
Manual, auto-start, AMF, transfer, multi-set and utility-parallel systems require different measurement, synchronization, load sharing and protection.
A communication port is not a delivered data system
Modbus, CAN, Ethernet and cellular links still need point maps, gateways, cybersecurity and an alarm-response workflow.
Local configuration and spares determine recovery time
Correct software, configuration files, permissions, firmware compatibility and replacement models matter during a failure.
2. Inputs to confirm before procurement
Start with the full control point list and operating scenarios.
- Single-set, AMF, ATS, multi-set or utility-parallel architecture
- Engine ECU, sensors, breakers and auxiliary I/O
- Required events, trends, alarms and operating data
- Modbus, CAN, Ethernet, cloud or SCADA interface
- Local engineers, software access, spares and remote support
3. How the main options compare
| Option or parameter | Where it fits | What must be verified |
|---|---|---|
| A specific DSE series | Projects ranging from auto-start sets to engineered paralleling. | Exact model functions, expansion, software and local support. |
| A specific ComAp series | Power-plant control, paralleling, communications and engineered configuration. | Architecture, licensed functions, tools and integration capability. |
| A specific SmartGen series | Projects balancing function, cost, local supply and common control duties. | Model boundaries, point map, firmware and service capability. |
4. The most common decision errors
Common mistakes
- Comparing brand names instead of exact model functions
- Using the controller as a substitute for independent protection or breaker logic
- Failing to hand over final configuration files
- Connecting remote monitoring without defining alarm ownership
Each brand spans several functional levels; compare equivalent models against the same system duty.
5. What the technical specification must state
The specification should state at least
- Control architecture, modes, start-stop and transfer logic
- Analog, digital, relay and expansion I/O schedule
- Measurement, protection, alarms, events and trends
- Protocols, register maps, network interfaces and time sync
- Configuration files, software, access, training and spare delivery
Accept the controller as part of the complete plant control system, not by checking that the display powers up.
6. How to verify and make the final decision
Verification and acceptance
- Simulate utility failure, return and failed starts
- Test sensors, emergency stop, breaker feedback and interlocks
- Review alarm text, timestamps and event sequence
- Verify remote data, communication loss and recovery
- Back up configuration and prove controlled replacement
A model that local teams can configure, diagnose and replace is often more valuable than unused advanced functions.
Paralleling and critical facilities require joint review by controls, protection and distribution engineers.