Project Control Specialist I
Akima · Fort Sill, OK · 1 mo ago
On-siteInformation TechnologyFull-time
We need to output HTML fragment with sections for headings: 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. No Job ID headings. Remove boilerplate.
We need to parse the posting.
Content:
- Intro: "Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project. Apply today to join our team of outstanding professionals!" This is maybe a brief description; could be placed under About the role? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section with that intro.
- Responsibilities: many bullet points. We need to list them as
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section with that intro.
- Responsibilities: many bullet points. We need to list them as - . The posting includes many responsibilities grouped under headings: General Responsibilities, Month End Close, Budgeting and Financial Analysis, Project Accounts Receivable / Accounts Payable, Project Team Support, Contracts. We need to combine all responsibilities into a list (or possibly separate subsections? The instruction says use
- for any list of duties/requirements/benefits. It doesn't forbid subheadings inside responsibilities? But we only have allowed headings list; we could still include subheadings as plain text? Probably better to just have one Responsibilities section with a big list.
- Qualifications: The posting includes "Qualifications" heading with bullet list: US Citizenship with the ability to pass a thorough background check; Strong analytical and problem‑solving skills with a high level of attention to detail.; Excellent communication skills.; 0-2 years of experience with government contracts.; Excel proficiency, including VLOOKUP, SUMIF, and PivotTables.; Desired Qualifications: Experience using Costpoint and Cognos.; Basic understanding of EACs, ETCs, unbilled analysis, and core project financial concepts.
We need to separate Requirements vs Qualifications vs Skills? The allowed headings include Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements: mandatory qualifications. Qualifications: desired? Skills: specific skills like Excel, Costpoint, etc. We'll interpret:
- Requirements: US Citizenship with ability to pass background check; Strong analytical and problem‑solving skills; Excellent communication skills; 0-2 years experience with government contracts.
- Qualifications: Desired Qualifications: Experience using Costpoint and Cognos; Basic understanding of EACs, ETCs, unbilled analysis, core project financial concepts.
- Skills: Excel proficiency, including VLOOKUP, SUMIF, PivotTables.
But we could also combine Qualifications and Skills. However we need to only include sections that have real specific content. We'll include all three if they have content.
- Benefits, Pay, Schedule: The posting mentions "You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options." That's a statement about benefits and pay but not specific details. It says "comprehensive benefits and competitive pay". That's vague but still mentions benefits and pay. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits and pay, albeit generic. Should we include? It says "comprehensive benefits and competitive pay". That's not specific like "health insurance, 401k". But it's still stating benefits and pay exist. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit generic. So we could include Benefits and Pay sections with that sentence. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "comprehensive benefits and competitive pay" is not filler; it's a statement. So we can include.
Schedule: Not mentioned. So no Schedule section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay.
Now we need to preserve all substantive information; do not invent or summarize away detail. We must keep all details from responsibilities etc. We must not drop any responsibility bullet. We need to capture each bullet as an
- . Ensure we don't lose any.
Let's extract responsibilities bullet by bullet.
From posting:
General Responsibilities:
- Provide support to Project Control Analyst (PCA) in driving project financial performance through effective planning, tracking, and reporting.
- Assists PCA with consolidating, analyzing, and presenting monthly and quarterly financial forecasts.
- Assists PCA with reviewing labor utilization across the organization.
- Serve as back-up point of contact for data requests, financial analyses, and issue resolution.
Month End Close:
- Assists PCA with completing month‑end accounting tasks, including cost, revenue, and accrual reconciliations.
- Assists PCA with analyzing monthly financial results and deliver clear, timely reports that highlight budget impacts and contract performance.
- Assists PCA with identifying potential over/under variances in revenue and margin recognition.
- Assists PCA with interpreting drivers behind revenue and gross margin variances against forecast.
- Assists PCA with presenting project financial performance during corporate reviews.
- Assists PCA in collaborating with program teams to validate cost inputs, schedule updates, and performance metrics affecting financial outcomes.
Budgeting and Financial Analysis:
- Assists PCA with developing baseline, working budgets, and EACs (Estimate At Complete) in partnership with program leadership.
- Assists PCA with monitoring project actuals, identify variances, communicate issues, and drive resolution.
- Assists PCA with tracking outstanding project commitments to maintain financial accuracy.
- Assists PCA with producing monthly financial forecasts and execute detailed variance analysis.
- Assists PCA with analyzing project reports, identifying trends or issues, and finding recommend corrective actions.
- Assists PCA with initiating and overseeing project setup activities within financial management systems (Costpoint).
Project Accounts Receivable / Accounts Payable:
- Ensure timely and accurate processing of subcontractor and vendor payments.
- Prepare customer‑specific invoice backup documentation as needed.
- Monitor the billing and payment status of customer invoices and support collection efforts.
- Identify and address incorrect charges, ensuring proper holds and corrections.
- Perform unbilled revenue and accrual calculations.
- Assists PCA with tracking contractual obligations and deliverables to maintain compliance.
- Review purchase request documentation to ensure accuracy and adherence to requirements.
Project Team Support:
- Assist in identifying and analyzing project risks.
- Support preparation and execution of internal and external project reviews.
- Contribute to schedule updates, analysis, contract deliverables and reporting.
- Initiate and track Purchase Orders.
- Generate, analyze, and interpret project financial reports.
- Communicate timecard and expense policies to project personnel.
- Proactively monitor project timesheets, identify errors, and ensure timely resolution.
- Review project‑related expenses for accuracy and timely processing.
- Assists PCA with providing earned value calculations and analysis when required.
- Project closeout activities.
Contracts:
- Assists PCA with reviewing and interpreting contracts, subcontracts, and agreements to ensure accurate project setup and compliance with reporting requirements.
- Assists PCA with with pricing extensions and bid development for new opportunities.
- Assists PCA with preparing funding notifications (including 75% letters) in accordance with contract requirements.
- Assists PCA with conducting variance analysis and identify risks to schedule, cost, and performance baselines.
Note there is a duplicate "Assists PCA with" in some lines; we keep as is.
Now Qualifications (mandatory):
- US Citizenship with the ability to pass a thorough background check
- Strong analytical and problem‑solving skills with a high level of attention to detail.
- Excellent communication skills.
- 0-2 years of experience with government contracts.
Desired Qualifications (maybe under Qualifications):
- Experience using Costpoint and Cognos.
- Basic understanding of EACs, ETCs, unbilled analysis, and core project financial concepts.
Skills:
- Excel proficiency, including VLOOKUP, SUMIF, and PivotTables.
Benefits/Pay statement: "You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options."
We could split: Benefits: comprehensive benefits, growth opportunities, excellent retirement options. Pay: competitive pay. But the instruction says we should not create sections unless posting actually states them. It states both benefits and pay. We could make Benefits section with "comprehensive benefits, growth opportunities, and excellent retirement options." Pay section with "competitive pay." However we must not invent detail; we can just put the sentence as is in each? Better to keep the sentence whole under Benefits and maybe Pay separate? But splitting may be considered inventing? The original sentence lumps them together. If we split, we are interpreting. Safer to keep a single Benefits section that includes both benefits and pay? But we have separate headings Benefits and Pay. Could we put the same sentence under both? That would be duplicative. Better to have Benefits section with the phrase about benefits and retirement options, and Pay section with competitive pay. However the original sentence includes both; we are extracting parts. That could be considered summarizing but not inventing. It's okay to extract.
Alternatively, we could have only Benefits section and not Pay, because the posting mentions both but we could treat the whole as Benefits. But the instruction says we can include Pay if posting states it. It does state "competitive pay". So we should include Pay.
Thus:
Benefits: comprehensive benefits, growth opportunities, excellent retirement options.
Pay: competitive pay.
Now About the role: The intro sentence: "Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project. Apply today to join our team of outstanding professionals!" We should not include "Apply today" maybe that's application instruction; we should remove application instructions. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So "Apply today to join our team of outstanding professionals!" is an application instruction; we should remove it. So About the role should just be: "Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project." That's substantive.
Now we need to output HTML fragment with
headings and - for lists,
for prose.
We'll structure:
About the role
Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project.
Responsibilities
- ...
...
Requirements
- US Citizenship with the ability to pass a thorough background check
- Strong analytical and problem‑solving skills with a high level of attention to detail.
- Excellent communication skills.
- 0-2 years of experience with government contracts.
Qualifications
- Experience using Costpoint and Cognos.
- Basic understanding of EACs, ETCs, unbilled analysis, and core project financial concepts.
Skills
- Excel proficiency, including VLOOKUP, SUMIF, and PivotTables.
Benefits
Comprehensive benefits, growth opportunities, and excellent retirement options.
Pay
Competitive pay.
Check for any duplicated lines: we removed duplicates.
Check that we didn't miss any responsibility bullet: Let's list all we captured.
General Responsibilities:
1. Provide support to Project Control Analyst (PCA) in driving project financial performance through effective planning, tracking, and reporting.
2. Assists PCA with consolidating, analyzing, and presenting monthly and quarterly financial forecasts.
3. Assists PCA with reviewing labor utilization across the organization.
4. Serve as back-up point of contact for data requests, financial analyses, and issue resolution.
Month End Close:
5. Assists PCA with completing month‑end accounting tasks,
- for any list of duties/requirements/benefits. It doesn't forbid subheadings inside responsibilities? But we only have allowed headings list; we could still include subheadings as plain text? Probably better to just have one Responsibilities section with a big list. - Qualifications: The posting includes "Qualifications" heading with bullet list: US Citizenship with the ability to pass a thorough background check; Strong analytical and problem‑solving skills with a high level of attention to detail.; Excellent communication skills.; 0-2 years of experience with government contracts.; Excel proficiency, including VLOOKUP, SUMIF, and PivotTables.; Desired Qualifications: Experience using Costpoint and Cognos.; Basic understanding of EACs, ETCs, unbilled analysis, and core project financial concepts. We need to separate Requirements vs Qualifications vs Skills? The allowed headings include Requirements, Qualifications, Skills. We need to decide what goes where. Typically Requirements: mandatory qualifications. Qualifications: desired? Skills: specific skills like Excel, Costpoint, etc. We'll interpret: - Requirements: US Citizenship with ability to pass background check; Strong analytical and problem‑solving skills; Excellent communication skills; 0-2 years experience with government contracts. - Qualifications: Desired Qualifications: Experience using Costpoint and Cognos; Basic understanding of EACs, ETCs, unbilled analysis, core project financial concepts. - Skills: Excel proficiency, including VLOOKUP, SUMIF, PivotTables. But we could also combine Qualifications and Skills. However we need to only include sections that have real specific content. We'll include all three if they have content. - Benefits, Pay, Schedule: The posting mentions "You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options." That's a statement about benefits and pay but not specific details. It says "comprehensive benefits and competitive pay". That's vague but still mentions benefits and pay. However the instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits and pay, albeit generic. Should we include? It says "comprehensive benefits and competitive pay". That's not specific like "health insurance, 401k". But it's still stating benefits and pay exist. The instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, albeit generic. So we could include Benefits and Pay sections with that sentence. However we must avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The phrase "comprehensive benefits and competitive pay" is not filler; it's a statement. So we can include. Schedule: Not mentioned. So no Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. Now we need to preserve all substantive information; do not invent or summarize away detail. We must keep all details from responsibilities etc. We must not drop any responsibility bullet. We need to capture each bullet as an
- . Ensure we don't lose any.
Let's extract responsibilities bullet by bullet.
From posting:
General Responsibilities:
- Provide support to Project Control Analyst (PCA) in driving project financial performance through effective planning, tracking, and reporting.
- Assists PCA with consolidating, analyzing, and presenting monthly and quarterly financial forecasts.
- Assists PCA with reviewing labor utilization across the organization.
- Serve as back-up point of contact for data requests, financial analyses, and issue resolution.
Month End Close:
- Assists PCA with completing month‑end accounting tasks, including cost, revenue, and accrual reconciliations.
- Assists PCA with analyzing monthly financial results and deliver clear, timely reports that highlight budget impacts and contract performance.
- Assists PCA with identifying potential over/under variances in revenue and margin recognition.
- Assists PCA with interpreting drivers behind revenue and gross margin variances against forecast.
- Assists PCA with presenting project financial performance during corporate reviews.
- Assists PCA in collaborating with program teams to validate cost inputs, schedule updates, and performance metrics affecting financial outcomes.
Budgeting and Financial Analysis:
- Assists PCA with developing baseline, working budgets, and EACs (Estimate At Complete) in partnership with program leadership.
- Assists PCA with monitoring project actuals, identify variances, communicate issues, and drive resolution.
- Assists PCA with tracking outstanding project commitments to maintain financial accuracy.
- Assists PCA with producing monthly financial forecasts and execute detailed variance analysis.
- Assists PCA with analyzing project reports, identifying trends or issues, and finding recommend corrective actions.
- Assists PCA with initiating and overseeing project setup activities within financial management systems (Costpoint).
Project Accounts Receivable / Accounts Payable:
- Ensure timely and accurate processing of subcontractor and vendor payments.
- Prepare customer‑specific invoice backup documentation as needed.
- Monitor the billing and payment status of customer invoices and support collection efforts.
- Identify and address incorrect charges, ensuring proper holds and corrections.
- Perform unbilled revenue and accrual calculations.
- Assists PCA with tracking contractual obligations and deliverables to maintain compliance.
- Review purchase request documentation to ensure accuracy and adherence to requirements.
Project Team Support:
- Assist in identifying and analyzing project risks.
- Support preparation and execution of internal and external project reviews.
- Contribute to schedule updates, analysis, contract deliverables and reporting.
- Initiate and track Purchase Orders.
- Generate, analyze, and interpret project financial reports.
- Communicate timecard and expense policies to project personnel.
- Proactively monitor project timesheets, identify errors, and ensure timely resolution.
- Review project‑related expenses for accuracy and timely processing.
- Assists PCA with providing earned value calculations and analysis when required.
- Project closeout activities.
Contracts:
- Assists PCA with reviewing and interpreting contracts, subcontracts, and agreements to ensure accurate project setup and compliance with reporting requirements.
- Assists PCA with with pricing extensions and bid development for new opportunities.
- Assists PCA with preparing funding notifications (including 75% letters) in accordance with contract requirements.
- Assists PCA with conducting variance analysis and identify risks to schedule, cost, and performance baselines.
Note there is a duplicate "Assists PCA with" in some lines; we keep as is.
Now Qualifications (mandatory):
- US Citizenship with the ability to pass a thorough background check
- Strong analytical and problem‑solving skills with a high level of attention to detail.
- Excellent communication skills.
- 0-2 years of experience with government contracts.
Desired Qualifications (maybe under Qualifications):
- Experience using Costpoint and Cognos.
- Basic understanding of EACs, ETCs, unbilled analysis, and core project financial concepts.
Skills:
- Excel proficiency, including VLOOKUP, SUMIF, and PivotTables.
Benefits/Pay statement: "You will also have access to our comprehensive benefits and competitive pay in addition to growth opportunities and excellent retirement options."
We could split: Benefits: comprehensive benefits, growth opportunities, excellent retirement options. Pay: competitive pay. But the instruction says we should not create sections unless posting actually states them. It states both benefits and pay. We could make Benefits section with "comprehensive benefits, growth opportunities, and excellent retirement options." Pay section with "competitive pay." However we must not invent detail; we can just put the sentence as is in each? Better to keep the sentence whole under Benefits and maybe Pay separate? But splitting may be considered inventing? The original sentence lumps them together. If we split, we are interpreting. Safer to keep a single Benefits section that includes both benefits and pay? But we have separate headings Benefits and Pay. Could we put the same sentence under both? That would be duplicative. Better to have Benefits section with the phrase about benefits and retirement options, and Pay section with competitive pay. However the original sentence includes both; we are extracting parts. That could be considered summarizing but not inventing. It's okay to extract.
Alternatively, we could have only Benefits section and not Pay, because the posting mentions both but we could treat the whole as Benefits. But the instruction says we can include Pay if posting states it. It does state "competitive pay". So we should include Pay.
Thus:
Benefits: comprehensive benefits, growth opportunities, excellent retirement options.
Pay: competitive pay.
Now About the role: The intro sentence: "Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project. Apply today to join our team of outstanding professionals!" We should not include "Apply today" maybe that's application instruction; we should remove application instructions. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So "Apply today to join our team of outstanding professionals!" is an application instruction; we should remove it. So About the role should just be: "Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project." That's substantive.
Now we need to output HTML fragment with
headings and
- for lists,
for prose. We'll structure:
About the role
Akima Facility Operations is looking for a Project Control Specialist to support the EAGLE Fort Sill project.
Responsibilities
- ... ...
Requirements
- US Citizenship with the ability to pass a thorough background check
- Strong analytical and problem‑solving skills with a high level of attention to detail.
- Excellent communication skills.
- 0-2 years of experience with government contracts.
Qualifications
- Experience using Costpoint and Cognos.
- Basic understanding of EACs, ETCs, unbilled analysis, and core project financial concepts.
Skills
- Excel proficiency, including VLOOKUP, SUMIF, and PivotTables.
Benefits
Comprehensive benefits, growth opportunities, and excellent retirement options.
Pay
Competitive pay.
Check for any duplicated lines: we removed duplicates. Check that we didn't miss any responsibility bullet: Let's list all we captured. General Responsibilities: 1. Provide support to Project Control Analyst (PCA) in driving project financial performance through effective planning, tracking, and reporting. 2. Assists PCA with consolidating, analyzing, and presenting monthly and quarterly financial forecasts. 3. Assists PCA with reviewing labor utilization across the organization. 4. Serve as back-up point of contact for data requests, financial analyses, and issue resolution. Month End Close: 5. Assists PCA with completing month‑end accounting tasks,
- for lists,