Why This Role ExistsEvery project starts before the project starts — with a scope definition, a vendor interface assessment, and a proposal that accurately describes what we will deliver, what we will not, and where the integration boundaries are. This role exists because P&C scope definition across eight manufacturer platforms requires an engineer who can read specifications and translate them into actionable scope. You define the technical scope, clarifications, and exclusions that become the contract. When you identify a gap between a prime contractor's specification and the actual integration requirements, that gap gets documented before it becomes a change order.What You OwnTechnical scope definition for P&C subcontract bids — protection, controls, commissioning boundariesClarifications and exclusions documentation — what is in scope, what is not, and where interfaces liveMulti‑vendor integration scope assessment: which engineering activities apply to each of eight manufacturer platformsVendor interface matrices: protocol compatibility, boundary definitions, integration risk identificationQuotation development with engineering hour estimates and equipment listsLegacy‑to‑modern equipment mapping and migration scope definitionSystems You'll TouchVendor PlatformsSELWoodwardABBEatonCAT (Caterpillar)Software ToolsETAPStandardsIEC 61850ProtocolsDNP3Modbus TCPWhat Success Looks LikeFirst 90 DaysReviewed 2+ prime contractor RFP/specification packages and produced scope clarification documentsDeveloped a vendor interface matrix for a multi‑vendor P&C scopeContributed to a proposal package — engineering narrative, equipment list, or scope boundary definitionFirst 180 DaysIndependently defining P&C scope from prime contractor specifications — clarifications, exclusions, integration boundariesProduced at least one complete proposal package accepted by the principal engineerIdentified scope gaps or integration risks that were incorporated into contract termsRequired Background5+ years protection & controls engineering or applications engineering for medium‑voltage power systemsFamiliarity with data center or critical facility power architecture — generators, ATS, switchgear, UPS, PDUExperience reading and interpreting prime contractor specifications, one‑line diagrams, and bid documentsScope definition and proposal writing — translating technical requirements into deliverable boundariesMulti‑vendor awareness: SEL, Woodward, ABB, Eaton, or equivalent OEM protection/controls platformsPreferred BackgroundSubcontractor proposal experience — scope narratives, clarifications/exclusions, engineering hour estimatesModernization/migration scope assessment — legacy system evaluation and upgrade planningETAP or SKM modeling for preliminary study scope sizingCommissioning scope estimation and resource planningWhat to Expect in the FieldTravel 10–15 % for site visits, constructability walks, and pre‑bid assessmentsSite hours standard office hours for scope development; occasional half‑day site visits for as‑built assessmentCustomer‑Facing direct interface with prime contractor procurement and project managers during bid/proposal phase; vendor technical support for scope clarificationDocumentation moderate — scope definitions, clarifications/exclusions, quotation packages, vendor interface matrices, equipment listsField safety minimal field exposure; NFPA 70E awareness for site assessment visitsWhy ZigguratYour scope definitions become the contract — you shape what the project looks like before engineering startsWork across all eight vendor platforms — scope assessment requires understanding every integration boundaryDirect feedback from project execution: see how your scope boundaries hold up during delivery and commissioningSmall firm means proposals move from your desk to the principal engineer's review, not through bureaucracy#J-18808-Ljbffr