Early integration planning helps align vendors, control systems, data architecture and commissioning strategy before schedules tighten.
Learning objectives
- Describe why early integration planning is critical in greenfield automation projects.
- Explain how greenfield projects differ from brownfield projects.
- Understand the benefits of bringing system integration expertise into vendor conversations early.
Integration insights
- Integration is one of the defining challenges of a greenfield project because it is the process of turning independent designs, vendor packages and stakeholder requirements into a facility that can operate as one system on day one.
- Successful greenfield integration begins early, with disciplined planning, documentation and cross-functional coordination that reduce risk long before commissioning and startup expose problems.
Greenfield projects offer a rare opportunity: the chance to build systems correctly from the start. They are also among the most complex efforts an engineer will encounter in industrial automation. Large greenfield projects bring together multiple engineering disciplines, equipment and technology vendors, client stakeholders, third-party specialists and engineering, procurement and construction (EPC) teams โ all working together to design and construct a facility from the ground up.
System integration is the process that makes sure all those elements work together. Automation systems, vendor packages, networking infrastructure, data architecture and operator interfaces must all function together when the plant starts for the first time.
On most greenfield projects, system integration is where problems become most visible, even if the problems originated earlier in the project. By the time a project reaches commissioning and startup, the process design is complete, equipment is installed, vendors have performed factory acceptance testing and the schedule has very little flexibility left. At that stage, the control system integrator must bring all systems together โ checking loops, proving interlocks, taking graphics live and beginning client training.
Integration is often the stage when earlier problems become apparent. If there were issues in communication six months earlier, they show up at this stage. If a design basis was loosely defined, it shows up in the integration stage. If a vendor package was purchased without fully considering how it would communicate with the distributed control system (DCS), it shows up during integration.
For engineers involved in a greenfield project, the implication is clear: integration planning cannot be treated as a late-stage activity. It must begin early, when process design and vendor selection are still evolving and system requirements are being defined. The opportunity to build systems correctly from the start of a greenfield project only pays off when integration planning receives the same early attention as process design, vendor coordination and startup preparation.
Why greenfield integration is different
In a brownfield expansion or retrofit, the design basis already exists in physical form. There is a running unit, and operators know how it behaves and understand an established control philosophy. Many decisions are one-for-one replacements with a defined list of improvements.
Greenfield integration is fundamentally different because that design foundation does not yet exist. Automation architecture, networking, safety systems, data structures and documentation standards must be defined while the process itself is still being developed.
Control narratives drafted early in the project may need revision, data visibility expectations may expand and cybersecurity requirements may be stricter than anticipated. Once the operations team begin thinking through startup scenarios, they may request changes to graphics or configuration to improve the operability of the system
If those conversations happen early, adjustments are manageable. If they occur during commissioning, when the schedule is compressed and resources are limited, the same changes become expensive and disruptive.
On a recent large-scale greenfield project where Hargrove Controls & Automation served as the system integrator for a novel process scaled beyond pilot operation, the design basis evolved continuously, which is normal for a first-of-its-kind or first-at-scale facility. Early assumptions changed as the team learned more about the process, equipment limitations and operational expectations. Because those discussions were happening early and were documented thoroughly, adjustments were incorporated before startup, allowing the operations team to meet schedule expectations set after the end of commissioning.
Integration is more than controls
When people hear โsystem integration,โ they often think about programmable logic controller (PLC) programming or DCS configuration. In practice, integration planning reaches much further.
Every modern facility is interconnected across multiple systems. These systems may vary depending on the facilityโs needs, but some of the most common include:
- Vendor skid packages and third-party PLCs
- DCS
- Safety instrumented systems
- Operational technology/information technology (OT/IT) network
- Data historians and analytics platforms
- Maintenance systems
Each of these elements involves design decisions that affect how the facility operates long term. These decisions ultimately shape how operators run the plant, how maintenance teams diagnose problems and how management evaluates performance.
Bringing system integration expertise into vendor conversations early, when specifications are written and bids are evaluated, allows for a smooth integration between vendor equipment and the plant control system. It reduces the risk of discovering during site commissioning that additional scope is required to meet client expectations. Integration planning protects the work already done by other disciplines.
Consider a vendor-supplied boiler package. The skid may be engineered well, its local human machine interface (HMI) may function properly and the control loops may be tuned and stable. From a package perspective, it performs as specified.
However, if its integration with the plant DCS is poorly defined, the end user may face operational limitations and unexpected integration work during startup. The system integration team should ask:
- Does the operator see the right alarms on the operator interface?
- Is the data captured in the historian in a format suitable for performance tracking?
- Can maintenance personnel trend runtime and fault history?
- Does the naming convention align with plant standards?
If those questions were not addressed during vendor specification and technical bid review, the integration team may be left solving those problems during startup.
Cybersecurity and data
Data architecture and cybersecurity are frequently overlooked systems. If digital strategy, data visibility and cybersecurity are treated as separate conversations rather than integral parts of integration planning, they will collide during commissioning. By that stage, architecture changes are far more difficult and expensive to implement.
Engineers should view automation strategy, data architecture and process design as interdependent from the outset. Every complex control strategy influences how data is structured and how it can be analyzed later. Decisions made on piping and instrumentation diagrams and in control narratives shape the long-term usefulness of the information the plant will generate.
One project where Hargrove was involved highlighted this clearly: expectations around moving data between the operations network and the business network differed significantly among stakeholders. Some team members assumed that exporting data to a spreadsheet and transferring it via USB drive would be acceptable. In modern OT cybersecurity practice, that approach creates significant vulnerability. Addressing the issue required rethinking how data would be securely accessed, how it would move between networks and how those networks would be segmented. The decision impacted historian configuration, network design and user access policies.
Communication breakdowns can delay integration projects
Integration alignment early in the project is a direct risk mitigation strategy. Large greenfield projects involve multiple engineering disciplines, EPC teams, vendors, client stakeholders and third-party specialists. Even with strong project management, communication gaps can develop. Within a small task group, alignment is usually straightforward, but across teams with different scopes and priorities, alignment requires deliberate effort.
When one group expects a standard that another group is not following, the discrepancy may go unnoticed until integrated testing begins. At that point, the schedule is tight, controls engineers are working against startup milestones and there is little room for extended design debates. If integration time has already been compressed due to earlier schedule delays, which is common, the pressure compounds.
Rework at that stage carries real cost. Controls engineers assigned to commissioning cannot easily be replaced or supplemented on short notice. Every hour spent redesigning or modifying configuration is an hour not spent progressing startup activities. The financial impact is not limited to engineering hours; delayed startup affects production schedules, revenue expectations and stakeholder confidence.
Documentation is operational memory
Documentation enables continuity and as the adage goes, โIf itโs not written, it doesnโt exist.โ Robust design specifications, control narratives, testing documents and acceptance criteria are important examples of operational memory.
Greenfield projects often take several years from design through startup and operational memory can be lost along the way. If decisions are made in meetings but not captured in updated documents, those decisions effectively disappear. Team members may rotate out, vendors may change personnel and engineers may move to other assignments. As project teams change over time, institutional memory can fade.
Clear and well-maintained documentation becomes especially important during commissioning, when teams need to understand how systems were designed to operate. When questions arise about why a system behaves a certain way, the answer should be traceable to the agreed-upon design basis. When testing is performed, it should reference documented acceptance criteria and when procedures are written, they should align with current control logic and graphics.
Projects that invest early and heavily in documentation often find that commissioning feels structured and manageable. Projects that defer documentation updates until late stages may experience confusion, redundant discussions and avoidable rework.
Involve commissioning early in integration
Another common oversight is waiting too long to involve commissioning and startup specialists in the design process. Procedure writers and startup experts should be brought in early; their experience operating and commissioning systems can identify issues that are difficult to see during early design reviews. Their input helps ensure that control narratives, procedures and operator interfaces will support efficient commissioning and startup.
These specialists think in terms of operability, providing perspective and expertise that can be lacking from other disciplines. This can lead to a design team working through issues well before they impact schedule or budget:
- How will this sequence be executed in the field?
- What will the operator see during an abnormal condition?
- Is the alarm strategy clear and actionable?
- Does the procedure align with the control narrative?
When commissioning expertise is introduced early, feedback can be incorporated into the design basis. That alignment reduces friction during startup and shortens the learning curve for operators.
If those voices are introduced too late, such as after systems are built, the team may discover that while the design is technically correct, it is cumbersome to operate or difficult to commission efficiently. Greenfield success depends on designing with startup in mind. Addressing these challenges requires focusing on a few key integration priorities early in a greenfield project.
Three early integration priorities for plant engineers
For engineers at the beginning of a greenfield project, three key integration priorities deserve early focus.
1. Establish structured, cross-discipline communication
Structure teams to encourage open communication. Define clear points of contact across process, electrical, instrumentation, automation, IT and vendor teams. Ensure that integration considerations are part of design reviews and technical bid evaluations. Encourage early identification of concerns, even if they seem minor. Problems identified early are usually manageable. When preventable integration issues surface during startup, they are much harder to resolve.
2. Protect team consistency and experience
Maintaining continuity on key integration roles helps preserve project knowledge. Experienced personnel who have worked with similar vendors or systems can recognize pitfalls quickly and prevent solutions that appear intuitive but create downstream challenges. When paired with strong documentation, minimizing turnover reduces integration risk.
3. Build the design basis and testing strategy from the beginning
Integration planning should start with a clear understanding of how the system will be tested, commissioned and operated. Compliance with specifications, change management procedures and testing requirements should be defined before configuration begins. Establishing templates for control strategies, graphics standards, naming conventions and documentation practices helps ensure the system is built consistently and can be validated efficiently.
Plan for factory acceptance testing, integrated testing, site acceptance, commissioning and pre-startup safety reviews as part of the initial strategy. When testing and documentation are integrated into the design process, startup becomes a matter of execution rather than troubleshooting.
Designing for Day One of operation
Ultimately, integration planning determines how well a new facility performs when it first comes online. During startup, operators depend on clear graphics, accurate alarm behavior, accessible data and well-defined procedures. Maintenance teams rely on meaningful trends and diagnostics, while management depends on reliable performance data.
When integration planning begins early, these needs can be addressed before on-site activities begin. When it is treated as a final technical task rather than part of the overall design process, teams are more likely to encounter avoidable rework during startup. Successful greenfield projects coordinate process design, automation strategy, data architecture and commissioning planning from the beginning. Doing so helps ensure that automation systems, vendor equipment and operational workflows function together as intended when the plant finally come
