How to choose an industrial automation system integrator in Indonesia

An industrial automation system integrator is a company that designs, installs, programs, tests and maintains equipment and software from several vendors so that they work together as one system. Choosing one is safest when you base it on evidence of similar projects, the ability to support the system after handover and the way the company documents its work.

A plant may buy PLCs from one vendor, instruments from another and a SCADA package from a third. The integrator is the party that makes them talk, answers for the result and gets the call when the plant stops at night. In Indonesia the label covers small panel workshops and large engineering firms, so the name alone tells you little. This guide gives a checklist you can apply to any bidder.

A disclosure: Citia is itself an automation integrator, so the checklist applies to us too. We appear in one section as an example, with links to real project pages you can check.

Many suppliers do two or three of these jobs, so the label matters less than the answer to one question: who signs for the integration? That party writes the functional specification, tests the interfaces between vendors and answers when two systems disagree.

A distributor may also commission. An engineering, procurement and construction (EPC) contractor may hire an integrator as a subcontractor. A vendor’s own engineers commission their own products very well, but they answer only for those products.

Single-vendor and independent models both work. A single vendor gives you one party for one product family and limits finger-pointing inside it. An independent integrator can mix brands to suit the plant, which matters when the site already runs equipment from several vendors, but you must check how deep its skills go in each brand.

The best evidence is a finished project that resembles yours. Resemblance means the same process, the same control platform or protocol, a site of similar size and the same kind of operating constraints.

Ask for three things per reference: what was delivered, who on the integrator’s team did the work and whether that person still works there, and a contact on the client side who ran the system afterwards. Then call that contact. Ask what went wrong during commissioning and how it was handled. Every project has such a moment, and the answer shows more than the success story.

A site visit beats a call. A control room with tidy cabinets, labelled wiring and a current backup shows what the integrator’s work looks like three years on. Be wary of reference lists made only of logos. A logo shows a relationship, not a scope, so ask what share of the system the integrator delivered.

A proposal is written by sales and delivered by engineers, so read the proposed team as closely as the price. Ask who the project manager and the lead engineer will be, how many projects each already carries, and what happens to your schedule if one of them leaves.

Ask what the integrator will subcontract, and to whom. Panel building, cable installation and civil work are often subcontracted, and that is normal. What matters is that the integrator names the subcontractors, stays accountable for them and holds them to its HSE rules on your site. Programming and commissioning of the control system are different. If those are subcontracted, you are really hiring the subcontractor, so evaluate it too.

Distance matters for response. An integrator with engineers near the site can reach a fault in hours, while one that must fly a team in cannot. Ask where the people who would support you are based, and whether documents and training will be in Indonesian, English or both. Operators read manuals at night and under stress, and a manual in a language they read fast is a safety feature.

A control system runs for years after the project team has left, so the support behind it matters as much as the build. Ask how a fault call is handled: who answers outside office hours, how fast, with what access to the system and which spares.

Citia’s long-term service agreement (LTSA) pages show two models. At LPG Panjang, one standby technician works office hours, and support after hours is on call. At Padalarang, the team makes a monthly visit for routine maintenance and coordination and takes a database backup each time.

Both pages also record a common problem. Faults in equipment outside the contract scope can still affect the system, and responsibility blurs. Write the scope boundary and the fault-handling steps into the service agreement, so the first night call does not start with an argument.

A good integrator also tells you when equipment is going out of production. The Redeco ATG assessment separated devices that could be kept, repaired or replaced, and drew up a plan to migrate discontinued units to supported technology. For the wider question, see the guides on migrating obsolete PLC and SCADA systems and assessing PLC and SCADA reliability.

Score the checklist first and price second. This avoids the cheapest bid with the widest gaps.

When you compare proposals, read the exclusions before the price. Two quotes for the same system often differ mainly in what they leave out: commissioning days, third-party interfaces, documentation and training. An open scope tends to return as variation orders. For a plant that already runs, consider a paid assessment before the tender, so the scope rests on what is really installed.