Sustainment IPS 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. Must preserve all substantive info, remove boilerplate, navigation, legal, EEO, etc. Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes "Basic Compensation: $105,000-$117,000 in Colorado Springs". So Pay section is present. Benefits: "KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule." So Benefits section present. Schedule: Not explicitly stated; there is "Working Hours: Standard". That's a schedule mention. It says "Working Hours: Standard". That's schedule info. Should we include Schedule section? It says "Standard". That's not placeholder? It's a specific statement: Standard working hours. It's not "varies" or "TBD". It's a concrete statement. So we can include Schedule section with that info. Now sections: About the role: we have introductory paragraphs describing role, mission, etc. Should we put that under About the role? Likely yes. Responsibilities: list of duties under "Duties And Responsibilities Include, But Are Not Limited To". So we can extract bullet points. Requirements: maybe separate from Qualifications? The posting has "Qualifications Required:" and then list. Also "Preferred" qualifications. We could combine Required and Preferred under Qualifications? But we have separate headings: Requirements, Qualifications, Skills. We need to decide mapping. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what content goes where. We have: - About the role: description of role, mission, location, etc. - Responsibilities: bullet list of duties. - Requirements: maybe the mandatory qualifications (Active DoW SECRET clearance, Bachelor's degree, 8+ years experience, etc.) - Qualifications: maybe the preferred qualifications (Active TS/SCI, Master's, etc.) Or we could treat Qualifications as both required and preferred? But we have both headings; we need to allocate content without duplication. - Skills: maybe list of skills like proficiency in MS Office, SharePoint, communication, analysis, organizational skills, etc. Could be under Skills. We need to avoid filler. Ensure we preserve all substantive info. Let's parse the posting: Title line etc. First paragraph: "Sustainment IPS Specialist Belong. Connect. Grow. with KBR! KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security. KBR is the prime contractor on the Military Satellite Communications (MILSATCOM) Systems Engineering, Integration and Test (MSEIT) contract. KBR is seeking a highly-skilled, motivated and proactive teammate to support Mission Delta 8 (MD8), 8th Sustainment Squadron (8STS) located at Peterson Space Force Base (PSFB), CO. We conduct operations and sustainment (O&S) activities for state-of-the-art Military and Commercial Satellite Communications (SATCOM) and Nuclear Command, Control and Communications (NC3) systems, providing global secure, survivable and protected communications for our Nation’s warfighters. We are looking for an experienced, dynamic and effective Sustainment IPS Specialist for a front-facing role within the Government System Program Office to effectively execute IPS activities supporting legacy and transitioning strategic and tactical space-based telecommunication capabilities, specifically with the Air Force/Army Antijam Modem (A3M). Future opportunities supporting Protected Band and Wideband MILSATCOM systems which include Advanced Extremely High Frequency (AEHF), Enhanced Polar System (EPS), Global Broadcast Service (GBS), and Protected Tactical Enterprise Service (PTES) as part of the MSEIT contract are possible. This position will be joining our high-functioning, high-performing MSEIT Sustainment IPT and be an important part of directly and positively affecting warfighter readiness as they employ US Space Force (USSF) systems worldwide in support of full spectrum military operations." That's about the role. Then "Why Join Us?" with bullet-like sentences: Innovative Projects..., Collaborative Environment..., Impactful Work:. Could be part of About the role or separate? Probably part of About the role (company culture). We'll include in About the role. Then "Work Environment Location: On-Site Peterson Space Force Base, Product Support Facility (PSF), Bldg. 2025. 1050 E. Stewart Ave., Colorado Springs, CO 80914 Travel Requirements: less than 20% Working Hours: Standard". This could go under About the role or maybe Schedule? We'll put location and travel under About the role, and Working Hours under Schedule. Then "Duties And Responsibilities Include, But Are Not Limited To" followed by bullet points (actually sentences separated by line breaks). We'll extract each as

. Then "Qualifications Required:" list. Then "Preferred" list. Then "Basic Compensation: $105,000-$117,000 in Colorado Springs The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity." Then "Ready to Make a Difference?" paragraph (call to action) - we should remove application instructions? It's not exactly instructions but encouraging to apply. Might be considered boilerplate? The instruction says remove application instructions. This is a call to apply; maybe we should remove it as it's application instruction. Safer to remove. Then "KBR Benefits KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development." Then "Belong, Connect and Grow at KBR ..." that's EEO/boilerplate? It's about culture but maybe not boilerplate; but it's similar to earlier "Why Join Us?" Might be considered fluff but still substantive? It's about company values. Could be included under About the role or maybe omitted as it's repetitive. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines. This section is about Belong, Connect and Grow, which is a tagline but also appears earlier. It's somewhat duplicated. Might be considered boilerplate. Safer to omit. Then "KBR is an equal opportunity employer..." that's EEO boilerplate, remove. Then "R2130316" job ID, remove. Thus final sections: About the role: include description, Why Join Us? (Innovative Projects, Collaborative Environment, Impactful Work), Work Environment Location, Travel Requirements. Responsibilities: bullet list of duties. Requirements: mandatory qualifications (Active DoW SECRET clearance, Bachelor's degree, 8+ years experience, etc.) Qualifications: preferred qualifications (Active TS/SCI, Master's, etc.) Skills: maybe list of skills like proficiency in MS Office tools, SharePoint, communication, analysis, organizational skills, familiarity with USAF logistics systems, etc. However many of those appear in qualifications. Could split: Required qualifications include some skills; Preferred include others. But we have separate Skills heading; we could put the generic skills like "Strong communication, analysis, and organizational skills Proficiency with standard MS Office tools (Word, Excel, PowerPoint, Teams, etc.) and SharePoint" under Skills. Also "Familiarity with USAF logistics systems (D035, DO43, SMART, REMIS, GCSS, etc.)" maybe under Skills. But those also appear in qualifications. To avoid duplication, we need to decide. Better: Use Requirements for mandatory qualifications (clearance, degree, years experience). Use Qualifications for both required and preferred? But we have Skills heading; we could put the skill-based items under Skills. Let's extract: From Qualifications Required: - Active DoW SECRET clearance with the ability to obtain a TS/SCI - Bachelor's degree in Logistics, Supply Chain, Business or equivalent related degree from an accredited university - 8+ years’ experience executing logistics in a Government Program Office or industry for a government program. - Experience planning, leading, and executing a depot activation (hardware, software, COMSEC) - Experience authoring logistics products to include an LCSP - Experience with Government programs in Acquisition transitioning to Sustainment - Proficiency in multiple DoW 12 Product Support Elements - Familiarity with USAF logistics systems (D035, DO43, SMART, REMIS, GCSS, etc.) - Familiarity with developing and maintaining technical orders - Familiarity with provisioning, cataloging, Logistics Supportability (GEIA-STD-0007), and sparing analysis - Strong communication, analysis, and organizational skills - Proficiency with standard MS Office tools (Word, Excel, PowerPoint, Teams, etc.) and SharePoint From Preferred: - Active TS/SCI security clearance - Master's degree in Logistics, Supply Chain, Business or equivalent related degree from an accredited university - 8+ years’ experience DoD SATCOM ACAT I/II acquisition and sustainment life cycle management - DAWIA Certification in Life Cycle Logistics (Advanced or Level III) - Experience performing Reliability, Availability, Maintainability, and Life Cycle Cost analysis - Experience conducting Logistics Supportability Analysis (GEIA-STD-0007) - Experience with Product Support Analysis (SAE TA-STD-0017) - Experience performing item/material management in USAF logistics systems (D035, DO43, SMART, REMIS, GCSS, etc.) - Experience with Weapon System Sustainment funding and Logistics Requirements Determination Process - Experience developing BOE’s and performing technical evaluations of contract proposals - Experience developing contract related documents (PWS/SOW/SOO, CDRLs, QASP, etc.) - Experience with JIRA and Confluence Now Skills: maybe we can pull out the generic skills: Strong communication, analysis, organizational skills; Proficiency with MS Office tools and SharePoint; Familiarity with USAF logistics systems; Familiarity with developing and maintaining technical orders; Familiarity with provisioning, cataloging, Logistics Supportability, sparing analysis. But many of those are also in qualifications. To avoid duplication, maybe we treat Skills as the subset of "Strong communication, analysis, and organizational skills; Proficiency with standard MS Office tools; Familiarity with USAF logistics systems; Familiarity with developing and maintaining technical orders; Familiarity with provisioning, cataloging, Logistics Supportability, sparing analysis". However that duplicates with qualifications. But the instruction says preserve ALL substantive information; we can duplicate? It didn't forbid duplication, but we should avoid unnecessary duplication. However we need to follow the headings: we have Requirements, Qualifications, Skills. If we put all qualification items under Requirements and Qualifications, we might leave Skills empty or with minimal content. Better to distribute: Requirements = mandatory qualifications (clearance, degree, years experience). Qualifications = preferred qualifications (master's, certifications, specific experience). Skills = the skill-based items (communication, MS Office, USAF logistics systems, technical orders, provisioning, etc.) That seems logical. Let's assign: Requirements (mandatory): - Active DoW SECRET clearance with ability to obtain TS/SCI - Bachelor's degree in Logistics, Supply Chain, Business or equivalent