Principal Project Controls – Scheduler

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. The posting includes: Pay: $72.00/hr - $82.00/hr; Contract: 12 months, extensions likely, conversion possible; Type: W-2, cannot support C2C or provide visa sponsorship; Hybrid: Field-based position with mobilization to project site in Anderson, SC. So we have Pay, Contract length, Type, Hybrid (maybe schedule?). The schedule is not given; we have location and field-based. There's no explicit schedule (like full-time, hours). So we should not create Schedule section unless specific content. Benefits not mentioned. So we can have sections: About the role (summary), Responsibilities, Requirements (maybe combine Basic/Required Qualifications and Desired Qualifications?), Qualifications (maybe separate?), Skills (maybe list of skills like Primavera P6, Acumen Fuse, etc). But we must not repeat job title as heading. Use

for each section heading. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate (EEO, etc). Also remove duplicated lines. We need to decide how to structure. Potential sections: - About the role (summary paragraph) - Responsibilities (list) - Requirements (basic/required qualifications) - Qualifications (desired qualifications) - Skills (maybe list of tools/expertise) - Pay (section) - Contract (maybe under Pay? But we have separate heading for Contract? Not in list but we could include under Pay? The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include Pay and maybe Contract as part of Pay? But better to include Contract under a separate heading? Not listed but we could still include if content exists? The instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they say "Prefer a few substantive sections over many thin ones." So we could combine Contract and Type into Pay section or maybe a "Details" section. But we have headings list includes Pay and Schedule; we could add a "Contract" heading if we want, but it's not in the examples. Safer to stick to the given headings. So we can put Pay info under Pay heading. Contract length and type maybe also under Pay? Or we could add a "Details" heading but not in list; risk of being considered extra. Better to incorporate contract info into Pay section as a paragraph. Schedule: we have no explicit schedule; we have field-based location. Could we put location under Schedule? Not really. Maybe we can omit Schedule section because no specific schedule info. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we should not create Schedule section because no schedule info. So we will have Pay section only. Benefits: none, so omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Now we need to extract content. About the role: The summary paragraphs: "Primary Talent Partners has a 12 month contract opening for a Principal Project Controls - Scheduler & Primavera Subject Matter Expert to join a national energy and utilities company for a field-based position operating out of Anderson, SC." Then "SummaryThe Principal Project Controls Specialist is a critical lead position responsible for scheduling and project controls integration on major power generation construction projects. This position supports Project Managers and Project Directors on projects of varying size and complexity, leading the setup, maintenance, and analysis of project schedules including baseline management, critical path analysis, and schedule-cost integration." Also "This is a field-based position supporting the Anderson Combined Cycle construction project. Power plant construction experience (Combined Cycle, Simple Cycle, Solar, or Battery) and mobilization to the field site is required." We'll combine into a paragraph. Responsibilities: list from "Key Responsibilities:" with sub-bullets. We'll extract each bullet as

. Responsibilities bullets: - Schedule Management & Development: - Lead development and maintenance of site integrated schedules in Primavera P6 - Establish and maintain project schedule baselines with critical path analysis - Incorporate implementation details into schedules upon contract award and integrate with site activities - Perform schedule variance analysis, adherence reporting, and trend analysis - Develop recovery plans and schedule mitigation strategies as necessary - Track project resources and quantities using Primavera and other scheduling tools - Project Controls Integration: - Provide schedule-cost integration analysis to support project forecasting - Review and assess change orders for schedule and time impacts - Support project funding submittals with detailed schedule analysis - Coordinate with vendors to gather and verify schedule updates through submittals, field walkdowns, and direct communication - Implement and maintain Work Breakdown Structures (WBS) aligned with project scope - Analysis & Reporting: - Perform schedule analysis using Acumen Fuse and other analytical tools - Conduct risk management analysis including Monte Carlo simulations - Generate monthly reports and site-specific documentation for PM/PD teams - Lead project controls reviews and status presentations - Support field observations of project progress and tracking of performance metrics - Leadership & Collaboration: - Serve as Primavera P6 subject matter expert and mentor to project controls team members - Lead implementation of scheduling methodologies and best practices - May supervise junior project controls staff as assigned - Coordinate benchmarking and self-assessment initiatives for continuous improvement - Support multiple projects simultaneously as required We need to keep the subheadings? The instruction: Use

• for any list of duties/requirements/benefits. So we could just list all responsibilities as flat list, but we could also keep subheadings as plain text? Probably better to keep as list items; subheadings could be strong text inside li? But we should not invent headings inside list. Could we keep the category headings as plain text before a nested list? That would be extra structure not requested. Simpler: flatten all bullet points into a single list. However we risk losing the grouping but still preserve all info. The instruction: "Use
  • for any list of duties/requirements/benefits". It doesn't forbid having headings inside list items. We could include the category as part of the li text, e.g., "
  • Schedule Management & Development: Lead development ..." That preserves info. Let's do that. Similarly for Requirements: Basic/Required Qualifications list. Requirements bullets: - Bachelor's degree in Engineering, Project Management, Finance, or Business Administration AND 10 years of related work experience, OR High School diploma/equivalent AND 14 years of related work experience - Demonstrated lead-level experience with complex EPC projects in power generation (Combined Cycle, Simple Cycle, Solar, or Battery construction) - Expert proficiency in Primavera P6 scheduling and critical path methodology on large-scale construction projects - Field experience observing project progress and tracking performance via schedule updates and field walkdowns - Proficiency in schedule analysis software such as Deltek Acumen Fuse - Willingness to mobilize to field site in Anderson, SC - Valid driver's license Qualifications: Desired Qualifications list. - Experience with MS Project, MS Office Suite, Business Objects, Passport, Powerplant, Emax, PeopleSoft - Risk management tools and Monte Carlo analysis experience - Experience evaluating vendor change orders and time impact analysis - Master's degree in Project Management, Engineering, or Business Administration - Professional certifications: PMI-SP (PMI Scheduling Professional), AACE-PSP (Planning & Scheduling Professional), or PMP (Project Management Professional) - Additional certifications: AACE-EVP, AACE-CCC, CAPM - Strong collaborative team member with proven ability to work across functional groups - Employee development and mentoring experience Skills: Could list specific tools and expertise: Primavera P6, Acumen Fuse, critical path methodology, schedule-cost integration, WBS, etc. But we already have many in responsibilities/qualifications. Might be redundant. Perhaps we can omit Skills section to avoid thin sections. But we need to include only when posting has real specific content. The posting does mention skills implicitly; but we could create a Skills section listing: Primavera P6, Acumen Fuse, MS Project, MS Office Suite, Business Objects, Passport, Powerplant, Emax, PeopleSoft, risk management tools, Monte Carlo analysis, change order evaluation, etc. However that may duplicate content. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we combine Skills into Responsibilities or Qualifications. But we need to follow the instruction to use headings for sections like Skills if we include. If we think it's thin, better to omit. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Now Pay section: include pay rate, contract length, type, hybrid/location. We need to preserve all substantive information: Pay: $72.00/hr - $82.00/hr; Contract: 12 months, extensions likely, conversion possible; Type: W-2, cannot support C2C or provide visa sponsorship; Hybrid: Field-based position with mobilization to project site in Anderson, SC. We'll put in a paragraph. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    ...

    Qualifications

    ...

    Pay

    ...

    Make sure not to include any boilerplate. Now write the content precisely. About the role paragraph: Combine: "Primary Talent Partners has a 12‑month contract opening for a Principal Project Controls – Scheduler & Primavera Subject Matter Expert to join a national energy and utilities company for a field‑based position operating out of Anderson, SC. The Principal Project Controls Specialist is a critical lead position responsible for scheduling and project controls integration on major power generation construction projects. This role supports Project Managers and Project Directors on projects of varying size and complexity, leading the setup, maintenance, and analysis of project schedules including baseline management, critical path analysis, and schedule‑cost integration. It is a field‑based position supporting the Anderson Combined Cycle construction project, requiring power plant construction experience (Combined Cycle, Simple Cycle, Solar, or Battery) and mobilization to the field site." Make sure to not repeat job title as heading; we already have heading About the role. Now Responsibilities list items: We'll embed headings inside maybe. Let's craft each li:
  • Schedule Management & Development: Lead development and maintenance of site integrated schedules in Primavera P6
  • Schedule Management & Development: Establish and maintain project schedule baselines with critical path analysis
  ... etc. But repeating the strong heading each time may be redundant but okay. Alternatively we could have one li with multiple sentences; but we need to preserve all details. Could combine into one li per category with semicolons. But better to keep each bullet as separate duty. We'll do:
  • Schedule Management & Development: Lead development and maintenance of site integrated schedules in Primavera P6
  • Schedule Management & Development: Establish and maintain project schedule baselines with critical path analysis
  • Schedule Management & Development: Incorporate implementation details into schedules upon contract award and integrate with site activities
  • Schedule Management & Development: Perform schedule variance analysis, adherence reporting