Integrated Project Planner

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Original Posting: ..." etc? That's metadata; maybe fold minor metadata into short

or drop it. The posting includes "Original Posting: 09/28/2026 - Until Filled" etc. That's minor metadata; we can drop or put in a short p. Probably drop. We need sections: About the role (purpose and scope). Responsibilities (Essential Responsibilities). Requirements (Minimum Position Knowledge, Skills, and Abilities Required). Qualifications (Preferred Qualifications). Skills maybe part of requirements but we can have Skills section if there is specific content. Benefits (Benefits Overview). Pay (Compensation Details). Schedule? Not provided; no schedule details. So we should not include Schedule section. We must not include sections with filler like "commensurate with experience" etc. For Pay, we have salary starts at $85K, final pay commensurate... That's specific enough? It says salary starts at $85K. That's specific. We can include Pay section with that info. Avoid filler like "commensurate with experience" but we can keep the statement as it's part of the content. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we cannot have a Pay section that only contains "commensurate with experience". But we have also "Salary starts at $85K." That's specific. So we can include that. Benefits: we have list. Good. Schedule: none. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from purpose and scope, responsibilities, minimum knowledge, preferred qualifications, work environment etc? The instruction: "Prefer a few substantive sections over many thin ones." But we must preserve all substantive info. We can combine some into sections like Requirements (includes minimum knowledge, work environment, physical demands etc). But we must not lose detail. We can include subpoints within

  etc. We need to decide sections: About the role (purpose and scope). Responsibilities (essential responsibilities). Requirements (minimum position knowledge, skills, abilities). Qualifications (preferred qualifications). Benefits. Pay. Possibly also Work Environment etc could be under Requirements or a separate section like Working Conditions. But we only have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Skills could be separate but we already have skills in requirements. Might combine. We need to avoid duplication. Let's extract content. Purpose and Scope paragraph: "On the Kennedy Propellants and Life Support Services (KPLSS II) program under general supervision, the Integrated Planner (IP) will develop plans and schedules, maintain the KPLSS Integrated Schedule to include work activities across all sites and facilities on Kennedy Space Center (KSC), Cape Canaveral Space Force Station (CCSFS) or other Government locations where KPLSS work is performed. The IP will integrate projects, task orders, maintenance, and operation plans and schedules, monitor progress, identify conflicts and variances, manage resource forecast plans, implement project controls and generate reports for critical path tracking. Ensure compliance with company scheduling standards and customer requirements. Support design and system maintenance engineering, project managers, business office, integrated operations and senior leadership, in addition to commercial customers requiring KPLSS services. Microsoft Project is the primary planning and scheduling software that is used. Excellent communication skills are needed to manage plans and schedules in a fast-paced, deadline driven environment. Skills and knowledge in production control, operations and maintenance planning, parts and material kitting, logistics inventory processes, technical task management, resource estimating, and component calibration and cleaning processes will be used daily." That's the About the role. Essential Responsibilities list: many bullet-like sentences. We need to turn each into
  • . Let's list them: - Ensures resources are forecasted to support maintenance, mission operations, task orders, projects and customer support requests. - Develops, reviews, maintains and presents work requirements in the KPLSS Integrated Schedule to ensure mission operations and maintenance milestones are met on time. - Determines resource availability, work authorization, critical milestones, and work breakdown structure during plan development. - Develop and plans project baseline and detailed critical path/workflow schedules by utilizing critical path scheduling techniques within the Microsoft Project application. - Analyzes requirements, ensuring that required resources are available or in process for availability so that established schedules dates are met on time. - Analyze schedule variance and tracking performance against the project baseline for assigned area. - Monitors estimated vs. actual performance to identify deviations to the forecasted maintenance activities. - Modifies schedules necessary to efficiently plan and report activities as required. - Ensures that all the necessary documentation is generated, input, reviewed, issued, and properly archived. - Interfaces directly with internal and external customers to validate support requirements and routinely coordinates plans with all stakeholders to ensure that plans and schedules are achievable; communicating in a manner fostering good relations with stakeholders. - Regular, timely verbal and written communication with the customer with the status of KPLSS work to ensure timely customer service. - Prepare schedule reports to reflect accurate status daily. - Works closely with functional managers to ensure that all schedules are effectively communicated and strategic solutions are developed as needed to meet required milestones. - Responsible for performing Open Work meetings with engineering to include operations and maintenance activities. - Must be able to lead planning and scheduling meetings in person and on Teams. - May lead or serve on committees, continuous improvement initiatives, and corrective action teams as required. - Daily use of Maximo to review work orders and support requests is required. - Coordinates with Amentum managers, supervisors, and employees to ensure commonality of purpose and direction. - Perform all other position related duties as assigned or requested. Minimum Position Knowledge, Skills, and Abilities Required: - Bachelor’s degree in related field, plus three years’ experience. - Possess moderate knowledge of Microsoft Office Programs, such as Outlook, Work, Excel, PowerPoint and Teams. - Possesses skilled knowledge in resource loading/leveling, logic linking activities by use of predecessor and successor, identifying dependencies, when building plans on MS Project, or other schedule software, such as Primavera; and Maximo (computerized maintenance/work management system software). - Exhibit concise communication skills daily, both orally and written. - Must be self-motivated, team player comfortable working in a dynamic environment. - Position may require the ability to pass and maintain a Security Clearance. - Must be able to successfully pass a National Agency Check with Inquiries (NACI). - US citizenship is required for restricted area access. - A driver's license is required to independently travel onto and around KSC property. Preferred Qualifications: - Local candidates. - No relocation allowance provided. - Practiced at leading planning/scheduling meetings. Work Environment, Physical Demands, and Mental Demands: - Most positions involve work typical of office environment with no unusual hazards, occasional lifting to 20 pounds, constant sitting with occasional use of computer terminal, constant use of sight abilities while reviewing documents, constant use of speech/hearing abilities for communication, constant mental alertness, must possess planning/organizing skills, and must be able to work under deadlines. Other Responsibilities: Safety, Quality, Procedure Compliance. These are generic boilerplate? Might be considered boilerplate but they are substantive? They are standard policies. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Safety, Quality, Procedure Compliance might be considered boilerplate but they are part of job description. However they are generic; but they are not EEO etc. Might keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Safety etc not listed. Could keep but maybe they are boilerplate. However they are not duplicated lines. I'd consider them part of "Other Responsibilities" but we don't have a heading for Other Responsibilities. Could include under Requirements or a separate section like "Other Responsibilities". But headings list does not include Other Responsibilities. We could fold into Requirements or maybe under a generic section like "Requirements". But we need to preserve all substantive info. If we drop them, we lose info. Safer to include them under a section like "Requirements" or maybe under a separate heading like "Other Responsibilities" but not in allowed headings. The instruction says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., implying those are examples but we can use others? It says "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should limit to those headings. So we should not add other headings. So we need to fit Safety, Quality, Procedure Compliance into one of those sections. Probably under Requirements or maybe under Responsibilities? They are more like general expectations. Could put under Requirements as additional bullet points. Compensation Details: Salary starts at $85K. Final pay will be commensurate with the candidate's experience, skills, and qualifications. The compensation range or hourly rate listed for this position is provided as a good-faith estimate of what the company intends to offer for this role at the time this posting was issued. Actual compensation may vary based on factors such as job responsibilities, education, experience, skills, internal equity, market data, applicable collective bargaining agreements, and relevant laws. We need to include Pay section with that info. However we must avoid filler like "commensurate with experience". The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we cannot have a Pay section that only contains that phrase. But we have also "Salary starts at $85K." That's specific. So we can include that sentence plus maybe the rest but we need to avoid the filler phrase? The phrase "commensurate with the candidate's experience, skills, and qualifications." is essentially filler. Might be considered filler. Safer to omit that sentence? But we must preserve ALL substantive information. The phrase is substantive? It's basically saying pay varies based on experience. That's somewhat generic but still info. However the instruction explicitly says not to emit a heading followed by filler/placeholder text like "commensurate with experience". So we should not include that phrase if it's the only substantive content. But we have also the specific salary start. So we can include the specific start and maybe omit the filler phrase. However we risk losing some info. But we could rephrase to keep the substantive: "Salary starts at $85K; final pay determined based on experience, skills, and qualifications." That still includes the phrase but maybe it's okay because it's not just filler; it's accompanied by specific number. The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. It doesn't say we cannot include that phrase at all; just that we shouldn't have a section that only contains filler. So including both is fine. Benefits: list. Schedule: none. Now we need to output HTML fragment only