Staff Project Controls Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, EEO, etc. Must preserve all substantive info. We need to parse the posting. Job title: Staff Project Controls Specialist 12 month contract Albuquerque, NM or Kansas City, MO Description paragraph: "Candidates must have extensive experience scheduling in Primavera P6 and good knowledge of the electrical T&D industry projects (transmission lines, substations, and distribution lines). Candidate must have excellent communication skills, be able to work in fast-paced environment, ability to work on a team, and ability to host meetings, seek out information from stakeholders to update schedules, be proactive in reporting and issues identification for schedules impacts that may impact the projects, and be able to manage a large volume of project schedules simultaneously. The Staff Project Controls Specialist will be responsible for leading the project controls processes with the internal project management team to execute project deliverables within budget and schedule. Ensure project set-up in the Enterprise Planning & Controls software. Analyze data, review logs, and run reports in the Enterprise Planning & Controls software or other tools. Create Work Breakdown Structure (WBS). Develop, implement, and maintain effective scheduling reports, cost reports, cash flows and forecasts for multiple projects. Follow project execution plans. Responsible for engineering, procurement and construction planning, scheduling, logistics and cost control. Serves as a point of contact for technical questions from the project team. Approve Purchase Orders and/or Subcontracts for proper coding. Input and document changes to cost reports or forecasts. Interfaces with the Project Management Team and Accounting Department to review project costs and contingency costs and support external audits. Review upstream (prime contract) and downstream (purchase order & subcontract) change orders. Develop and present a cash flow report. Develop various levels of schedules. Apply and review the entry of logic ties within the schedules. Monitor resource loading of a schedule. Support Interactive Project Planning Meetings (IPPM). Create various schedule reports and determine appropriate reporting format. Develop, review, and analyze pre-programmed project scheduling reports and back-up documentation for accuracy. Consults with the project team on schedule progress. Analyzes and evaluates schedule management involving the critical path method of scheduling techniques, estimating, project cost management and forecasting. Perform schedule what-if scenarios. Develop and maintain an earned value management system. Input and validate progress measurement. Develop and maintain progress curves. Perform material takeoffs. Perform quality checks and inspections on project controls deliverables. Perform field audits to validate accuracy of reporting and processes. Capable of assisting with Project Forensic Analysis. Performs other duties as assigned" Then "Complies with all policies and standards" maybe part of responsibilities. Then "Requirements:" list: Bachelor Degree in engineering, construction management or related field. and 3 years of direct project controls experience. Required or Applicable experience may be substituted for the degree requirement. Required Experience with Oracle Primavera P6 preferred. Excellent written and verbal communication skills. Excellent interpersonal skills. Proficient with Microsoft Office. OSHA 10-hour safety certification Ability to obtain ESPO Corporation www.espocorp.com 630-789-2525 View all open jobs at www.espocorp.com/jobs Leaders in Technical Recruiting & Staffing since 1965 ESPO has a comprehensive benefits package which includes PTO, Group Health and Dental Insurance, and 401k after you have satisfied the necessary waiting periods. We are an Equal Opportunity Employer and value the benefits of diversity in our workforce. All qualified applicants will receive consideration for employment without regard to race, color, religion, gender, gender identity and expression, national origin, disability, protected Veteran status, or any other attribute or protected characteristic by law. If you need assistance applying, please get in touch with us directly. We need to remove boilerplate: EEO, legal, scam warning, application instructions, navigation, cookie, etc. Also remove "Ability to obtain ESPO Corporation www.espocorp.com 630-789-2525 View all open jobs at www.espocorp.com/jobs Leaders in Technical Recruiting & Staffing since 1965" maybe considered boilerplate? It's about the company; but we need to keep benefits info: "ESPO has a comprehensive benefits package which includes PTO, Group Health and Dental Insurance, and 401k after you have satisfied the necessary waiting periods." That's benefits. We should not include "Ability to obtain ESPO Corporation ..." as it's not substantive? It's basically a call to contact? Might be considered application instruction. Safer to drop that line. We need to keep: description (responsibilities), requirements (education, experience, skills), benefits (PTO, health, dental, 401k). Also maybe "Qualifications" could be same as requirements? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have description that includes responsibilities. Could treat first paragraph as "About the role" maybe summarizing role? But we must not invent placeholder text. We can create "About the role" with a short paragraph summarizing the role? But we must preserve ALL substantive information; we cannot summarize away detail. However we can keep the description as responsibilities. The "About the role" could be a brief overview but we risk losing detail if we don't include all details elsewhere. Better to put the detailed description under "Responsibilities". Then maybe "About the role" could be omitted if no specific content besides title? The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should not create About the role if we don't have a distinct summary separate from responsibilities. The posting didn't have an explicit "About the role" section; it started with description. So we can skip About the role. We have responsibilities: all the duties listed. We have requirements: education, experience, certifications. We have skills: maybe communication, interpersonal, MS Office, Primavera P6, etc. Could be under Skills. We have benefits: PTO, Group Health and Dental Insurance, 401k after waiting period. Pay: not specified; we must not create Pay section unless posting actually states them. No pay info, so omit. Schedule: not specified; omit. Qualifications: could be same as Requirements? Might be redundant. The instruction says we can have Qualifications section; but we need to avoid duplication. If we put Requirements, we could also put Qualifications but that would duplicate content. Better to either use Requirements or Qualifications, not both. Since we have explicit "Requirements:" heading in posting, we can use Requirements. Qualifications could be omitted. Skills: we could extract skills from requirements and responsibilities: excellent communication, interpersonal, MS Office, Primavera P6, OSHA 10-hour safety certification, ability to obtain... maybe not needed. But we can create Skills section with bullet list of skills: Excellent written and verbal communication skills, Excellent interpersonal skills, Proficient with Microsoft Office, Experience with Oracle Primavera P6 (preferred), OSHA 10-hour safety certification. However note that some of these are also in Requirements. To avoid duplication, we could keep Requirements as education/experience, and Skills as the skillset. That seems acceptable. We must preserve ALL substantive information; we cannot omit any. So we need to ensure that each piece of info appears somewhere in the output. Let's list all substantive info: From description: - Extensive experience scheduling in Primavera P6 - Good knowledge of electrical T&D industry projects (transmission lines, substations, distribution lines) - Excellent communication skills - Ability to work in fast-paced environment - Ability to work on a team - Ability to host meetings - Seek out information from stakeholders to update schedules - Proactive in reporting and issues identification for schedule impacts that may impact projects - Ability to manage a large volume of project schedules simultaneously - Lead project controls processes with internal project management team to execute deliverables within budget and schedule - Ensure project set-up in Enterprise Planning & Controls software - Analyze data, review logs, run reports in Enterprise Planning & Controls software or other tools - Create Work Breakdown Structure (WBS) - Develop, implement, maintain effective scheduling reports, cost reports, cash flows and forecasts for multiple projects - Follow project execution plans - Responsible for engineering, procurement and construction planning, scheduling, logistics and cost control - Serve as point of contact for technical questions from project team - Approve Purchase Orders and/or Subcontracts for proper coding - Input and document changes to cost reports or forecasts - Interface with Project Management Team and Accounting Department to review project costs and contingency costs and support external audits - Review upstream (prime contract) and downstream (purchase order & subcontract) change orders - Develop and present a cash flow report - Develop various levels of schedules - Apply and review entry of logic ties within schedules - Monitor resource loading of a schedule - Support Interactive Project Planning Meetings (IPPM) - Create various schedule reports and determine appropriate reporting format - Develop, review, analyze pre-programmed project scheduling reports and back-up documentation for accuracy - Consult with project team on schedule progress - Analyze and evaluate schedule management involving critical path method, estimating, project cost management and forecasting - Perform schedule what-if scenarios - Develop and maintain earned value management system - Input and validate progress measurement - Develop and maintain progress curves - Perform material takeoffs - Perform quality checks and inspections on project controls deliverables - Perform field audits to validate accuracy of reporting and processes - Capable of assisting with Project Forensic Analysis - Performs other duties as assigned - Complies with all policies and standards From Requirements: - Bachelor Degree in engineering, construction management or related field - 3 years of direct project controls experience - Required or Applicable experience may be substituted for the degree requirement - Required Experience with Oracle Primavera P6 preferred - Excellent written and verbal communication skills - Excellent interpersonal skills - Proficient with Microsoft Office - OSHA 10-hour safety certification From Benefits: - ESPO has a comprehensive benefits package which includes PTO, Group Health and Dental Insurance, and 401k after you have satisfied the necessary waiting periods. We also have company info but we can drop. Now we need to structure. We could have:

Responsibilities

• ... each duty as li

Requirements

• ... each requirement

Skills

• ... each skill

Benefits

• ... each benefit

We must not repeat info. Ensure each piece appears exactly once (or at least not omitted). Some items appear in both description and requirements (e.g., communication skills, interpersonal, MS Office, Primavera P6). To avoid duplication, we need to decide where to place them. Since they appear in both, we could place them under Skills (or Requirements) but ensure we still capture them. The requirement list includes "Excellent written and verbal communication skills", "Excellent interpersonal skills", "Proficient with Microsoft Office", "Required Experience with Oracle Primavera P6 preferred", "OSHA 10-hour safety certification". The description also mentions extensive experience scheduling in Primavera P6, excellent communication skills, ability to work in fast-paced environment, etc. So we can capture communication skills under Skills, and note Primavera P6 experience under Skills as well. The description's "extensive experience scheduling in Primavera P6" is more specific than "Required Experience with Oracle Primavera P6 preferred". We'll capture that under Skills as "Extensive experience scheduling in Oracle Primavera P6". The requirement's "Required Experience with Oracle Primavera P6 preferred" is similar; we can just note "Experience with Oracle Prim