Project Controls Specialist III
EDG · Birmingham, AL · 1 mo ago
On-siteProject ManagementFull-time
We need to output HTML fragment with sections: About the role? The posting includes Job Summary and Job Duties And Responsibilities, Qualifications, Working Conditions, Physical Requirements, etc. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, drug free workplace, equal opportunity, etc. Also remove application instructions (Additional Application Requirement? That's about cover letter for relocation; might be considered application instruction; but it's a requirement? It says "Additional Application Requirement". Likely should be removed as application instruction. Also remove "Working Conditions" and "Physical Requirements"? Those are not in the allowed headings list but could be considered part of Responsibilities or Requirements? The instruction: "Use
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content accordingly.
We must not repeat job title as heading. No Job ID etc. Remove boilerplate: EEO, drug free workplace, equal opportunity, etc. Also remove application instructions (Additional Application Requirement? That's about cover letter for relocation; might be considered application instruction; but it's a requirement? It says "Additional Application Requirement". Likely should be removed as application instruction. Also remove "Working Conditions" and "Physical Requirements"? Those are not in the allowed headings list but could be considered part of Responsibilities or Requirements? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should only create those headings if there is real specific content. We can combine content into these categories.
We need to preserve all substantive information. So we need to extract details and place them under appropriate sections.
Let's parse content:
Job Summary: "The Project Controls Specialist performs all project controls functions including scheduling and cost control. The Sr. Project Controls Specialist will work with schedulers, cost analysts, project managers, and other key stakeholders to refine deliverables prior to stage gate reviews. This position will also be a key point of contact for upper management to discuss high-visibility projects and process development/improvement for the Project Controls team."
That's about the role. Could go under About the role.
Job Duties And Responsibilities: list of duties. We'll put under Responsibilities.
Qualifications (Knowledge, Skills And Abilities): includes Basic or Minimum Requirements and Preferred Qualifications. We'll put under Requirements and Qualifications? The headings list includes Requirements, Qualifications, Skills. We could split: Requirements (basic), Qualifications (preferred), Skills (maybe separate). But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But we have separate headings allowed. We could do: Requirements
for basic/minimum, Qualifications
for preferred, Skills
for skills like communication, writing, computer literacy, etc. However many of those are overlapping.
Better: Use Responsibilities for duties, Requirements for basic/minimum qualifications, Qualifications for preferred qualifications, Skills for specific skills (communication, writing, Primavera P6, Excel, etc.). But we need to ensure we don't create sections with filler like "not specified". All sections have content.
Also Benefits, Pay, Schedule: not present in posting, so we should NOT include those sections.
Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
Check if any content for Benefits, Pay, Schedule: none, so omit.
Now we need to format lists with - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information: include details like location, industry, department, employment type, etc. Those are metadata; we could fold into About the role paragraph or a short
. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, industry, department, employment type, etc. in a short paragraph under About the role or maybe a separate metadata paragraph. But we should not create a heading for them.
Thus About the role section could start with a paragraph summarizing role and include location, industry, department, employment type.
Let's craft:
About the role
Location: Birmingham, AL. Industry: Utilities. Department: Project Controls. Employment Type: Full‑time Regular. The Project Controls Specialist performs all project controls functions including scheduling and cost control. The Sr. Project Controls Specialist will work with schedulers, cost analysts, project managers, and other key stakeholders to refine deliverables prior to stage gate reviews. This position will also be a key point of contact for upper management to discuss high‑visibility projects and process development/improvement for the Project Controls team.
Now Responsibilities: list each duty as - . Need to capture all duties from Job Duties And Responsibilities.
Let's extract them:
- Assist project manager to develop project scope of work.
- Study and understand all relevant project documents pertaining to the preparation of plans and schedules.
- Work with all relevant project and discipline personnel to prepare plans and schedules.
- Convert scope of work document into logically linked resource-loaded project schedule.
- Prepare realistic, achievable schedules as logical networks and where necessary integrate engineering, procurement, and construction schedules.
- Monitor progress against project schedule and prepare progress reports.
- Gather accurate progress and expended cost information at relevant time intervals.
- Prepare, review, and ensure the timely issue of all relevant reports to stakeholders.
- Verbally and in writing advise project management and discipline personnel on impacts, contingencies and generally guide the scopes towards the earliest possible finish.
- Analyze progress and effects on schedule and advise necessary corrective actions.
- Mentor other Project Controls Specialist on the team.
- Develop and/or modify Project Controls processes and working procedures based on feedback from project stakeholders and upper management.
- Serve as a key point of contact for upper management to discuss high-visibility projects and issues.
- Lead/Assist in the development of Cost and Schedule QRAs (Quantitative Risk Assessment).
- Participate in schedule and project risk analysis as required.
- May assist as a Stage Gate Process Gate Reviewer by performing rigorous evaluations of project development and control deliverables, including business cases presented by project teams.
- Provide input into the budget forecasting process.
- Track actual costs and prepare cost forecasts.
- Manage cost discipline to ensure accurate and timely control and forecasting of man‑hour budgets and ensure that the impact of all change requests is properly assessed and included in the schedules.
We'll put each as
- .
Now Requirements (basic/minimum):
From Qualifications (Knowledge, Skills And Abilities) Basic or Minimum Requirements:
- High School Diploma or the equivalent.
- Requires five (5) years with less than (10) years of Project Controls related experience.
- Requires previous experience utilizing Primavera P6 to build schedules.
- Must be able to effectively communicate with project stakeholders and upper management.
- Requires a basic working knowledge of project management software, specifically Primavera P6 and Excel.
- Requires the ability to manage multiple projects and determine priorities.
- Must be a skilled writer.
- Must understand the basic principles of project management.
- Requires a general understanding of Cost Management, Estimating and Change Control.
- Candidate must reside within a reasonable commuting distance to work location.
- Candidates outside a reasonable commuting distance must provide a cover letter regarding intentions to relocate to be considered.
- Candidate must reside within commuting distance to New Orleans prior to starting employment.
- Must have a high degree of computer literacy.
Note: There's some contradictory: location Birmingham but also must reside within commuting distance to New Orleans prior to starting employment. We'll keep as is.
Now Preferred Qualifications:
- Bachelor’s degree preferred.
- Previous experience in the Utility industry preferred.
Now Skills: Could include communication, writing, Primavera P6, Excel, project management software, ability to manage multiple projects, etc. But many already in Requirements. To avoid duplication, we could treat Skills as a subset: maybe list specific technical skills: Primavera P6, Excel, project management software, cost management, estimating, change control, scheduling, risk analysis, etc. But we risk duplication. However instruction: preserve ALL substantive information; we can duplicate but better to avoid redundancy? Not prohibited. But we should aim for a few substantive sections over many thin ones. We already have Requirements and Qualifications; Skills could be thin. Maybe we can omit Skills section and incorporate skills into Requirements/Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But we have headings list; we could still use Requirements for both basic and preferred, and maybe not have Qualifications separate. However we need to include preferred qualifications somewhere. Could put them under Requirements as well, but label them as "Preferred". Or we could have Requirements (basic) and Qualifications (preferred). That's two sections, which is fine.
Skills section may be redundant; we could omit it. Let's see if we have any skill not covered: "Must be a skilled writer", "Must be able to effectively communicate", "Must have a high degree of computer literacy", "Must understand basic principles of project management", "General understanding of Cost Management, Estimating and Change Control". Those are already in Requirements. So we can skip Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
Now we need to ensure we don't include boilerplate: remove EEO, drug free workplace, etc. Also remove "Additional Application Requirement" (cover letter for relocation) - but that is actually a requirement for candidates outside commuting distance; it's already covered in Requirements (cover letter). We included that as a bullet under Requirements. So we can keep that. The "Additional Application Requirement" heading itself is application instruction; we can drop the heading but keep the content.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
Be careful to escape any special characters? Not needed.
We'll produce:
About the role
Location: Birmingham, AL. Industry: Utilities. Department: Project Controls. Employment Type: Full‑time Regular. The Project Controls Specialist performs all project controls functions including scheduling and cost control. The Sr. Project Controls Specialist will work with schedulers, cost analysts, project managers, and other key stakeholders to refine deliverables prior to stage gate reviews. This position will also be a key point of contact for upper management to discuss high‑visibility projects and process development/improvement for the Project Controls team.
Responsibilities
- Assist project manager to develop project scope of work.
- Study and understand all relevant project documents pertaining to the preparation of plans and schedules.
- Work with all relevant project and discipline personnel to prepare plans and schedules.
- Convert scope of work document into logically linked resource-loaded project schedule.
- Prepare realistic, achievable schedules as logical networks and where necessary integrate engineering, procurement, and construction schedules.
- Monitor progress against project schedule and prepare progress reports.
- Gather accurate progress and expended cost information at relevant time intervals.
- Prepare, review, and ensure the timely issue of all relevant reports to stakeholders.
- Verbally and in writing advise project management and discipline personnel on impacts, contingencies and generally guide the scopes towards the earliest possible finish.
- Analyze progress and effects on schedule and advise necessary corrective actions.
- Mentor other Project Controls Specialist on the team.
- Develop and/or modify Project Controls processes and working procedures based on feedback from project stakeholders and upper management.
- Serve as a key point of contact for upper management to discuss high‑visibility projects and issues.
- Lead/Assist in the development of Cost and Schedule QRAs (Quantitative Risk Assessment).
- Participate in schedule and project risk analysis as required.
- May assist as a Stage Gate Process Gate Reviewer by performing rigorous evaluations of project development and control deliverables, including business cases presented by project teams.
- Provide input into the budget forecasting process.
- Track actual costs and prepare cost forecasts.
- Manage cost discipline to ensure accurate and timely control and forecasting of man‑hour budgets and ensure that the impact of all change requests is properly assessed and included in the schedules.
Requirements
- High School Diploma or the equivalent.
- Five
Requirements
for basic/minimum,Qualifications
for preferred,Skills
for skills like communication, writing, computer literacy, etc. However many of those are overlapping. Better: Use Responsibilities for duties, Requirements for basic/minimum qualifications, Qualifications for preferred qualifications, Skills for specific skills (communication, writing, Primavera P6, Excel, etc.). But we need to ensure we don't create sections with filler like "not specified". All sections have content. Also Benefits, Pay, Schedule: not present in posting, so we should NOT include those sections. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Check if any content for Benefits, Pay, Schedule: none, so omit. Now we need to format lists with- for any list of duties/requirements/benefits. For prose, use
. We need to preserve all substantive information: include details like location, industry, department, employment type, etc. Those are metadata; we could fold into About the role paragraph or a short
. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include location, industry, department, employment type, etc. in a short paragraph under About the role or maybe a separate metadata paragraph. But we should not create a heading for them. Thus About the role section could start with a paragraph summarizing role and include location, industry, department, employment type. Let's craft:
About the role
Location: Birmingham, AL. Industry: Utilities. Department: Project Controls. Employment Type: Full‑time Regular. The Project Controls Specialist performs all project controls functions including scheduling and cost control. The Sr. Project Controls Specialist will work with schedulers, cost analysts, project managers, and other key stakeholders to refine deliverables prior to stage gate reviews. This position will also be a key point of contact for upper management to discuss high‑visibility projects and process development/improvement for the Project Controls team.
Now Responsibilities: list each duty as - . Need to capture all duties from Job Duties And Responsibilities. Let's extract them: - Assist project manager to develop project scope of work. - Study and understand all relevant project documents pertaining to the preparation of plans and schedules. - Work with all relevant project and discipline personnel to prepare plans and schedules. - Convert scope of work document into logically linked resource-loaded project schedule. - Prepare realistic, achievable schedules as logical networks and where necessary integrate engineering, procurement, and construction schedules. - Monitor progress against project schedule and prepare progress reports. - Gather accurate progress and expended cost information at relevant time intervals. - Prepare, review, and ensure the timely issue of all relevant reports to stakeholders. - Verbally and in writing advise project management and discipline personnel on impacts, contingencies and generally guide the scopes towards the earliest possible finish. - Analyze progress and effects on schedule and advise necessary corrective actions. - Mentor other Project Controls Specialist on the team. - Develop and/or modify Project Controls processes and working procedures based on feedback from project stakeholders and upper management. - Serve as a key point of contact for upper management to discuss high-visibility projects and issues. - Lead/Assist in the development of Cost and Schedule QRAs (Quantitative Risk Assessment). - Participate in schedule and project risk analysis as required. - May assist as a Stage Gate Process Gate Reviewer by performing rigorous evaluations of project development and control deliverables, including business cases presented by project teams. - Provide input into the budget forecasting process. - Track actual costs and prepare cost forecasts. - Manage cost discipline to ensure accurate and timely control and forecasting of man‑hour budgets and ensure that the impact of all change requests is properly assessed and included in the schedules. We'll put each as
- .
Now Requirements (basic/minimum):
From Qualifications (Knowledge, Skills And Abilities) Basic or Minimum Requirements:
- High School Diploma or the equivalent.
- Requires five (5) years with less than (10) years of Project Controls related experience.
- Requires previous experience utilizing Primavera P6 to build schedules.
- Must be able to effectively communicate with project stakeholders and upper management.
- Requires a basic working knowledge of project management software, specifically Primavera P6 and Excel.
- Requires the ability to manage multiple projects and determine priorities.
- Must be a skilled writer.
- Must understand the basic principles of project management.
- Requires a general understanding of Cost Management, Estimating and Change Control.
- Candidate must reside within a reasonable commuting distance to work location.
- Candidates outside a reasonable commuting distance must provide a cover letter regarding intentions to relocate to be considered.
- Candidate must reside within commuting distance to New Orleans prior to starting employment.
- Must have a high degree of computer literacy.
Note: There's some contradictory: location Birmingham but also must reside within commuting distance to New Orleans prior to starting employment. We'll keep as is.
Now Preferred Qualifications:
- Bachelor’s degree preferred.
- Previous experience in the Utility industry preferred.
Now Skills: Could include communication, writing, Primavera P6, Excel, project management software, ability to manage multiple projects, etc. But many already in Requirements. To avoid duplication, we could treat Skills as a subset: maybe list specific technical skills: Primavera P6, Excel, project management software, cost management, estimating, change control, scheduling, risk analysis, etc. But we risk duplication. However instruction: preserve ALL substantive information; we can duplicate but better to avoid redundancy? Not prohibited. But we should aim for a few substantive sections over many thin ones. We already have Requirements and Qualifications; Skills could be thin. Maybe we can omit Skills section and incorporate skills into Requirements/Qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine Requirements and Qualifications into one section? But we have headings list; we could still use Requirements for both basic and preferred, and maybe not have Qualifications separate. However we need to include preferred qualifications somewhere. Could put them under Requirements as well, but label them as "Preferred". Or we could have Requirements (basic) and Qualifications (preferred). That's two sections, which is fine.
Skills section may be redundant; we could omit it. Let's see if we have any skill not covered: "Must be a skilled writer", "Must be able to effectively communicate", "Must have a high degree of computer literacy", "Must understand basic principles of project management", "General understanding of Cost Management, Estimating and Change Control". Those are already in Requirements. So we can skip Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications.
Now we need to ensure we don't include boilerplate: remove EEO, drug free workplace, etc. Also remove "Additional Application Requirement" (cover letter for relocation) - but that is actually a requirement for candidates outside commuting distance; it's already covered in Requirements (cover letter). We included that as a bullet under Requirements. So we can keep that. The "Additional Application Requirement" heading itself is application instruction; we can drop the heading but keep the content.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft.
Be careful to escape any special characters? Not needed.
We'll produce:
About the role
Location: Birmingham, AL. Industry: Utilities. Department: Project Controls. Employment Type: Full‑time Regular. The Project Controls Specialist performs all project controls functions including scheduling and cost control. The Sr. Project Controls Specialist will work with schedulers, cost analysts, project managers, and other key stakeholders to refine deliverables prior to stage gate reviews. This position will also be a key point of contact for upper management to discuss high‑visibility projects and process development/improvement for the Project Controls team.
Responsibilities
- Assist project manager to develop project scope of work.
- Study and understand all relevant project documents pertaining to the preparation of plans and schedules.
- Work with all relevant project and discipline personnel to prepare plans and schedules.
- Convert scope of work document into logically linked resource-loaded project schedule.
- Prepare realistic, achievable schedules as logical networks and where necessary integrate engineering, procurement, and construction schedules.
- Monitor progress against project schedule and prepare progress reports.
- Gather accurate progress and expended cost information at relevant time intervals.
- Prepare, review, and ensure the timely issue of all relevant reports to stakeholders.
- Verbally and in writing advise project management and discipline personnel on impacts, contingencies and generally guide the scopes towards the earliest possible finish.
- Analyze progress and effects on schedule and advise necessary corrective actions.
- Mentor other Project Controls Specialist on the team.
- Develop and/or modify Project Controls processes and working procedures based on feedback from project stakeholders and upper management.
- Serve as a key point of contact for upper management to discuss high‑visibility projects and issues.
- Lead/Assist in the development of Cost and Schedule QRAs (Quantitative Risk Assessment).
- Participate in schedule and project risk analysis as required.
- May assist as a Stage Gate Process Gate Reviewer by performing rigorous evaluations of project development and control deliverables, including business cases presented by project teams.
- Provide input into the budget forecasting process.
- Track actual costs and prepare cost forecasts.
- Manage cost discipline to ensure accurate and timely control and forecasting of man‑hour budgets and ensure that the impact of all change requests is properly assessed and included in the schedules.
Requirements
- High School Diploma or the equivalent.
- Five