Owner Furnished Equipment Coordinator

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are", "Overview", "Key Responsibilities", "Software & Technical Proficiency", "Who You Are" (which includes Required Skills & Experience, Preferred Qualifications, Soft Skills Required, Hard Skills Required). We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. The posting does not have Benefits, Pay, Schedule. So we should not create those sections. We need to map content to appropriate headings: maybe "About the role" corresponds to Overview? "Responsibilities" corresponds to Key Responsibilities. "Requirements" maybe combine Required Skills & Experience? "Qualifications" maybe Preferred Qualifications? "Skills" maybe Software & Technical Proficiency? Also "Who You Are" includes both required and preferred and soft/hard skills. We need to decide. We must not repeat job title as heading. The page already shows it (not given). So we just output sections. We need to preserve all substantive information, no boilerplate (EEO etc). Remove duplicated lines. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to include sections only when posting has real specific content. Thus we can have:

  About the role

  with overview paragraph.

  Responsibilities

  with list of responsibilities (maybe grouped under subheadings? But we can just list items). The responsibilities are many bullet-like sentences. We'll create
  • for each.

    Requirements

    for Required Skills & Experience (maybe also hard skills?). Could combine required skills and hard skills? But we can separate: maybe "Required Skills & Experience" as Requirements, and "Preferred Qualifications" as Qualifications, and "Skills" for Software & Technical Proficiency. We need to ensure we don't create empty sections. Let's extract content. Who We Are: description of VEC. Could be part of About the role? Might be considered company overview. Could be placed under About the role? The instruction: "About the role" heading for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can put company description under About the role? Or maybe Overview. But we can treat "Overview" as About the role. Thus About the role: include "Who We Are" paragraph and "Overview" paragraph. Responsibilities: all bullet points under Key Responsibilities (including sub-sections). We'll list each responsibility as
  • . Requirements: Required Skills & Experience (5-7 years experience etc). Also maybe Hard Skills Required? But Hard Skills Required is similar to required skills. Could combine. Qualifications: Preferred Qualifications. Skills: Software & Technical Proficiency (list of tools). Also maybe Soft Skills Required? Could be under Skills? But Soft Skills are not technical. Could be part of Requirements? Might be better to have a separate section for Skills (technical) and maybe include soft skills under Requirements? However the instruction says use headings like Skills for skills section. We'll put technical skills under Skills. Soft skills maybe under Requirements? But we can also include them under Requirements as part of required skills? Might be okay. We need to avoid filler like "commensurate with experience". Not present. We must not include EEO boilerplate at end. Let's craft HTML. We'll start with

    About the role

    ... combined paragraphs.

    Then

    Responsibilities

    ...
    Then

    Requirements

    ...
    (maybe include required skills, hard skills, soft skills? We'll list each as li.) Then

    Qualifications

    ...
    (preferred qualifications) Then

    Skills

    ...
    (software & technical proficiency) We need to ensure we don't duplicate content. Let's extract text. Who We Are: "VEC is a leading construction technology services provider that is at the forefront of innovation in the construction industry, delivering cutting-edge technology solutions that revolutionize the way construction projects are designed and built. Our Mission is to challenge the status quo and reshape the way we plan, design, and construct the built world so Humanity can thrive sustainably. We partner with contractors, engineers, and developers/owners across the US and deploy our team of construction and technology professionals to improve project delivery. We support large projects across many sectors of the industry: Data Centers, Healthcare, Life Sciences, Tech, Education, Transportation, Aviation, Commercial Office Space, and Public Works. We love what we do, our VECommunity, and helping the best build better." Overview: "The Owner Furnished Equipment Coordinator (OFE-C) owns all Owner Furnished Equipment (also called Owner Furnished, Contractor Installed, or OFCI) across the project lifecycle, from early identification and planning through procurement tracking, design coordination, delivery, and closeout. The role reports to the Digital Delivery Program Manager and is assigned to a single site or campus. The OFE-C is the single-threaded owner of the OFE pipeline from design through operations handover, and the primary point of coordination between the owner, vendors, design team, GC, trade partners, BIM/VDC team, commissioning team, and operations stakeholders. Owner furnished scope fails when it gets deferred to another party. The OFE-C holds it instead: identifying gaps early, asking the technical questions, tracking decisions, escalating risk, and acting with authority on the owner's behalf so every item moves from concept to operational readiness without disrupting the project. The OFE-C does not purchase or install equipment. The role governs the work through a master OFE log kept as the single source of truth, a RASCI matrix that settles who furnishes, installs, and accepts each item, and asset metadata validated against the project's Asset Information Requirements (AIR) schema. This is a mission-critical coordination role, roughly 60% cross-party coordination and communication and 40% technical judgment." Now Responsibilities: list each bullet. Key Responsibilities sections: Master OFE Log & Tracking: - Create, own, and maintain the master OFE log as the single source of truth for end-to-end equipment tracking, including equipment IDs, locations, vendor information, procurement status, installation responsibility, utility requirements, delivery dates, and closeout status. - Keep all tracking logs current and usable by every party working from them. - Enforce model metadata compliance against the Asset Information Requirements (AIR) schema using automated validation tools. - Maintain the CDE for the OFE register and supporting documentation, and reduce data fragmentation across single-site and multi-site environments. Responsibility Boundaries & Scope Interfaces: - Define who furnishes, purchases, delivers, installs, connects, tests, commissions, warrants, and accepts each OFE item. - Identify and resolve scope gaps between owner, vendor, GC, trade contractors, design team, and operations through a RASCI matrix. - Hold owner-furnished scope rather than deferring it, and make the call when responsibility is unclear. Technical & Installation-Interface Coordination: - Collect and track vendor cut sheets, installation manuals, utility requirements, clearance requirements, structural support needs, data/IT needs, and maintenance access requirements. - Coordinate OFE requirements across architectural, structural, MEP, low-voltage, BIM/VDC, and field teams. - Inform BIM/VDC of OFE design changes ahead of time so clash resolution stays on schedule for sign-off. Procurement, Delivery & Schedule Risk: - Monitor equipment selections, purchase orders, lead times, submittals, fabrication, shipping, delivery, storage, and installation windows. - Escalate late decisions, missing vendor information, changed equipment requirements, delivery conflicts, and schedule impacts to the responsible parties in time to act on them. - Use visual planning and 4D sequencing tools such as Synchro and Navisworks to review equipment development and protect schedule-critical-path access. Commissioning, Turnover & Operational Readiness: - Track delivery confirmation, installation verification, commissioning, warranties, O&M manuals, serial numbers, asset tags, and final acceptance. - Validate asset metadata against the AIR schema before operational sign-off and handoff to the owner. - Deliver the asset data and closeout documentation package, and support digital handoff. Stakeholder Coordination: - Owner and client team for equipment decisions, standards, approvals, and acceptance requirements. - Owner procurement for purchasing status, vendor contracts, lead times, and delivery commitments. - Equipment vendors for cut sheets, installation requirements, manuals, startup support, and warranty information. - Design team for layout, code, clearance, structural, MEP, low-voltage, and infrastructure coordination. - BIM/VDC team for equipment modeling, clash detection, clearance zones, and coordinated installation planning. - GC project management and field teams for schedule integration, subcontractor coordination, site readiness, logistics, and issue escalation. - Trade contractors for rough-ins, supports, final connections, testing support, and field installation requirements. - Commissioning and facilities teams for startup, testing, training, asset data, maintainability, and turnover acceptance. Now Required Skills & Experience: "5 to 7 years of direct experience in equipment procurement, project management, owner's representation, procurement coordination, mission-critical equipment planning, or a related field. Strong understanding of construction sequencing, design coordination, submittals, RFIs, procurement, logistics, and closeout. Familiarity with MEP, structural, low-voltage, and architectural coordination issues related to equipment installation. Ability to build and manage equipment logs, and to read and interpret drawings, specifications, equipment cut sheets, installation manuals, and coordination documents. Experience working across owner, vendor, design, GC, trade, commissioning, and operations stakeholders on a live project." Preferred Qualifications: "Direct OFE, OFCI, or FF&E coordination experience for data center owners. Experience on hyperscale or multi-building campus programs. Familiarity with Asset Information Requirements (AIR) schemas and digital handover to facilities and operations teams. Owner's representative or owner-side project experience." Soft Skills Required: "Takes ownership of scope that has no obvious home, and escalates rather than waiting for direction. Strong written communication, particularly in tracking decisions and confirming commitments in writing. Comfortable asking technical questions of vendors, designers, and trades until the answer is clear. Organized and persistent on follow-through across many parties and long lead times." Hard Skills Required: "Working knowledge of construction documents, submittals, and equipment coordination workflows. Ability to maintain structured data at scale, including equipment registers, metadata, and asset records. Understanding of construction schedules and the ability to read installation windows and critical-path impacts. Working proficiency across Procore, Autodesk Construction Cloud, Bluebeam, Smartsheet, Excel, and 4D review tools such as Synchro or Navisworks (see Software & Technical Proficiency above)." Software & Technical Proficiency: "Procore and Autodesk Construction Cloud, or comparable project management and document control platforms. Smartsheet and Excel for log management, tracking, and reporting. Bluebeam for drawing review and markup. Synchro and Navisworks for 4D sequencing and model review, or comparable visual planning tools." Now we need to map to sections. We could put Required Skills & Experience + Hard Skills Required + Soft Skills Required under Requirements? But we have separate headings for Skills (technical). Perhaps: - Requirements: Required Skills & Experience (maybe also Hard Skills Required? but Hard Skills includes technical proficiency which we already have under Skills). To avoid duplication, we could put Hard Skills Required under Skills as well? But Hard Skills includes ability to maintain structured data etc, which is more general. Could be under Requirements. Better: Requirements: Required Skills & Experience + Hard Skills Required (since both are required). Qualifications: Preferred Qualifications. Skills: Software & Technical Proficiency (technical tools). Soft skills maybe could be included under Requirements as well, but we