Who Owns Each Electrical Design Deliverable? A Responsibility Matrix for FDI Factories

An electrical design responsibility matrix should assign a named producer, a competent technical checker, an authorised decision-maker and an acceptance record to each deliverable. “EPC designs everything” is not an adequate interface definition when an international factory project combines owner standards, a Vietnamese delivery team, imported production equipment and separate civil or mechanical contractors. As a result, a missing input can remain invisible until cable procurement, foundation construction or machine commissioning.

Prepared for QuangAnhcons · Editorial focus: M&E design interfaces for FDI factories · Sources checked: 5 October 2026.

This guide addresses the factory-side design process, from the agreed incoming electrical interface to the production-machine terminals. It does not duplicate the utility-application process, replace project-specific engineering or prescribe Vietnam’s statutory approval duties. The matrices below are procurement recommendations to be adapted to the signed contracts, appointment of competent designers and applicable local requirements.

1. Freeze the design baseline before allocating responsibility

A responsibility matrix built on undefined inputs creates false certainty. Start with the owner’s operating decisions: production phases, critical loads, maintenance philosophy, redundancy expectations and expansion boundaries. Then, the designer develops the technical response. A designer should not silently choose the production downtime that the owner is willing to accept.

In addition, for an FDI project, the owner’s international standards and the local execution requirements also need an explicit reconciliation route. An overseas specification is not automatically the local legal requirement. Conversely, a local drawing approval does not establish compliance with every owner performance requirement. Record the applicable documents, editions, contractual hierarchy and the person authorised to resolve a conflict. Do not resolve a conflict merely by selecting the cheaper requirement.

A baseline register every bidder can use

Control the revision and the missing inputs

ISO 19650-1:2018 describes concepts and principles for managing building information, including exchange, recording and versioning. Its public catalogue scope supports the need for controlled information; it does not allocate the legal or commercial obligations of an EPC contract. The catalogue identifies the 2018 edition as current while a replacement is under development. ISO source and edition status.

For example, if a machine vendor cannot confirm its final terminal location, mark that input provisional. Identify the cable, tray, opening and panel decisions affected, and put a hold point on the irreversible work. An assumption is manageable only when someone owns its closure.

2. Assign responsibility to deliverables, not just organisations

In an electrical design responsibility matrix, use a row for an identifiable output rather than a broad discipline label. “Electrical design” can include load estimation, cable sizing, protection coordination, panel manufacture, controls, equipment connections and field changes. As a result, these outputs may belong to different parties.

To make those boundaries explicit, in the starting matrix below, P means produce; T means technically check within the appointed competence and scope; D means decide or accept at the contractual hold point; and I means supply an input. However, a decision by the owner is not a substitute for a competent technical check. Where the contract separates designer and EPC contractor, split that column rather than leaving a combined accountability ambiguous.

Electrical design responsibility matrix: a deliverable-based example

Keep technical checking separate from owner acceptance

The matrix should state where the designer’s responsibility continues after the owner comments on a drawing. Avoid an unqualified “approved” stamp that could be read as transferring design liability to the investor. Define the review purpose, permissible issue status and remaining obligations in the actual contract.

Therefore, allocate one decision owner for each hold point. Several reviewers can contribute; however, competing acceptance instructions need one escalation route. A meeting attended by four organisations is not evidence that all four accepted the same drawing revision.

3. Close both the physical boundary and the information handoff

To keep the electrical design responsibility matrix usable, every interface needs two descriptions: where the physical work ends, and what information must cross that point. For example, a cable ending at a machine panel can be physically clear while its controls, earthing terminal, gland space or isolation arrangement remains undefined.

Questions at the package boundary

Track an issue to its engineering closure

For model-based coordination, buildingSMART’s BCF standard provides a way to exchange model-linked issues between applications. It can carry a view and references to model elements. That makes an issue easier to locate, but a BCF topic alone does not approve the engineering solution or vary the contract. Assign an issue owner, affected revision, due date and closure evidence whether the project uses BIM or a spreadsheet. buildingSMART BCF introduction.

However, a common failure is to close a query with “refer to vendor drawing” while the vendor drawing does not identify the factory-side terminal. In that case, the interface is still open. Close it with a shared marked-up boundary drawing or an accepted schedule, not with a document reference that moves the question elsewhere.

4. Control changes before cable, panel or civil-work release

The design team must assess a late equipment change across the affected system, not only at the machine nameplate. The response may involve demand, protective devices, cables, panel space, heat, controls, support loads and commissioning. Therefore, the appropriate checks depend on the actual change and the equipment information; this guide does not supply universal design margins.

A scheduling example with an explicit hold point

Hypothetical scheduling example: suppose the approved machine interface is required on day 20, technical checking takes 3 working days, and coordinated closure takes another 2. With sequential activities and no overlap, the input must arrive by day 15: 20 − 3 − 2 = 15. By contrast, if it arrives on day 18, the earliest closure is day 23, creating a 3-working-day conflict with release. The reverse check is 15 + 3 + 2 = 20. These are invented planning durations, not a commitment for any project.

As a result, the owner has choices: move the release, obtain a formally agreed review acceleration, split a demonstrably independent package, or accept a documented provisional release. Each choice carries risk. Splitting a package is sensible only if the unaffected work really is independent; changing a panel incomer can make that assumption false.

A change record the site team can act on

• Record the initiating change and the baseline revision.
• Identify every affected drawing, calculation, purchase order and field package.
• Complete the competent technical review before commercial acceptance.
• State the cost, programme and operational consequence.
• Approve the change through the named authority and withdraw superseded issues.
• Notify vendors and site teams, then verify that the new revision reached them.

In particular, do not allow an email marked “noted” to serve as both technical approval and commercial variation. Separate those decisions. For broad tender-scope allocation, see electrical EPC tender boundaries in Vietnam; for the external supply boundary, see utility connection responsibilities.

5. Put the electrical design responsibility matrix into the RFQ

A useful request for quotation makes bidders return the same deliverable schedule. It should expose missing inputs before the owner compares prices. For example, the cheapest offer may exclude studies, vendor coordination or revised drawings that another offer includes.

Twelve items to return with the priced offer

Require the following alongside the priced offer:

1. A design scope divided into calculations, drawings, vendor interfaces, review support and as-builts.
2. A deliverable matrix naming producer, technical checker, decision-maker and input providers.
3. A dated owner/vendor input schedule and the treatment of late inputs.
4. A document register with language, format, revision and issue-status definitions.
5. A design-review calendar, comment closure method and escalation path.
6. A list of assumed supply conditions and the route to confirmation.
7. A coordinated interface schedule for machine terminals, foundations, penetrations, earthing and controls.
8. A deviation and substitution procedure with technical, commercial and operational review.
9. Hold points for long-lead purchase, panel manufacture, civil works and installation release.
10. A commissioning evidence plan linking tests to design requirements and equipment.
11. Named exclusions and provisional items, rather than “by others” without an owner.
12. A handover acceptance checklist covering field changes, settings, vendor information and operator use.

Define what counts as acceptance

For each item, ask for an identifiable output and an acceptance criterion. “Coordinate as required” has no measurable finish. “Close the listed machine power and controls interfaces before release of panel revision C” can be checked, provided the actual project defines that revision and list.

Finally, use clarification meetings to reconcile differences, then incorporate the agreed scope into the contract. Meeting notes that never enter the controlled contract package can leave the commercial allocation unresolved.

6. Carry design decisions into commissioning and handover

Design coordination does not end when the team issues drawings. Commissioning should verify the installed arrangement against the accepted design basis, the actual machine information and the applicable test plan. However, a passed equipment test is not necessarily proof that an interlock, alarm destination or maintenance isolation interface works as intended.

Reconcile the field condition and the final documents

Before handover, reconcile the final single-line diagram, cable schedules, protection settings, control lists and vendor documents with the field condition. Assign ownership for unresolved defects and provisional information. Do not label an unverified drawing “as-built” simply because construction has ended.

Consequently, the owner’s operations team should receive information it can use: asset tags matching the plant, accessible isolation and maintenance references, an accepted settings register, change history and contact routes for vendor questions. The design matrix can then become a handover matrix: every obligation is either accepted with evidence or remains a named open item.

Supporting video: QuangAnhcons factory substation energisation on YouTube. This construction-service illustration does not prove that a particular design matrix was used. The player is hosted by YouTube, not by this website.

Sources and method

Sources checked on 5 October 2026: ISO 19650-1:2018 public catalogue for information-management scope and edition status; buildingSMART BCF introduction for model-linked issue exchange. No paywalled clauses or statutory approval duties are asserted. The matrices, RFQ checklist and scheduling scenario are editorial recommendations, not a published standard or an actual project record.

Request a design-interface scope review

Send QuangAnhcons the factory location, latest load and machine schedules, proposed single-line diagram, owner standards, discipline boundaries and target operating date. These inputs support a focused review of the electrical design responsibility matrix, missing deliverables and unresolved interfaces before procurement release.

Discuss your factory electrical design interfaces.

[contact-form-7 id="7239967" title="Contact form 1"]