B-1 Readiness and Sustainment Subject Matter Expert
ASI Government · Oklahoma City, OK · 1 mo ago
On-siteOTHRFull-time
We need to output HTML fragment with sections: headings using
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. Remove boilerplate, etc. We need to parse the posting. First part: "ASI Government provides government leaders..." is about the company. Could be "About the role"? Actually "About the role" is typical heading for description of role. The posting includes a description: "Do you thrive on creating unique and impactful value for Federal clients? ..." That's more like introductory. Could be considered "About the role". We'll include that as a
under
About the role
. Then "Job Description ASI Government is seeking a senior B-1 Readiness and Sustainment Subject Matter Expert to support the Air Force B-1 System Program Office at Tinker Air Force Base. The initial 16-week effort will improve how the SPO manages fleet readiness by establishing a current-state baseline, assessing the data and integration landscape, prioritizing and designing a minimum viable product, and developing an implementation roadmap. You will bring the weapon-system and sustainment context that allows the team to distinguish how readiness decisions are actually made from how a process appears on paper. You will work with System Program Office (SPO) leaders, logisticians, engineers, program managers, depot and production personnel, supply-chain stakeholders, and an integrated consulting and digital team. Ideal candidates understand the B-1 sustainment ecosystem and can turn incomplete data, cross-organizational dependencies, and ambiguous operational problems into practical decisions, clear requirements, and executable plans." That's description; could be part of About the role or Responsibilities. We'll treat as About the role. Then "Key Responsibilities" heading. We'll outputResponsibilities
with- each bullet.
List items from "Key Responsibilities":
- Serve as the team's senior B-1 readiness and sustainment advisor, providing practical context on fleet management, maintenance, engineering, logistics, supply, depot production, and field operations.
- Lead interviews and working sessions that document current readiness processes, decision rights, information flows, constraints, and pain points across the sustainment ecosystem.
- Help define the future-state readiness management approach, including decision forums, roles, key performance indicators, business rules, escalation paths, and recurring management routines.
- Translate operational needs into functional use cases, analytic requirements, data definitions, and acceptance criteria for a prioritized minimum viable product.
- Guide the assessment of readiness data sources, mappings, normalization needs, data quality, system interfaces, and integration constraints in partnership with data engineers and architects.
- Conduct or advise root-cause analyses of readiness drivers, including maintenance, supply, MICAP, production, engineering, and reliability issues, using FMEA or comparable methods when appropriate.
- Develop decision-ready briefings, process maps, requirements, risk and action trackers, and an implementation roadmap that can be incorporated into the SPO's routine operations.
- Engage B-1 stakeholders, including depot, wing and squadron, supply-chain, DLA, and other enterprise partners, to validate findings and remove barriers.
Then "Required" heading: list of requirements. We'll treat as Requirements.
List:
- Bachelor's degree and eight or more years of relevant Department of Defense experience in aviation readiness, weapon-system sustainment, logistics, maintenance, supply chain, engineering, product support, or program management.
- Direct experience supporting the B-1, another Air Force bomber, or a comparably complex Air Force weapon system in a program office, depot, operational unit, supply-chain organization, or sustainment command.
- Working knowledge of the relationships among program management, product support, depot maintenance, field maintenance, engineering, supply support, and operational readiness.
- Experience assessing current processes and converting findings into a future-state operating approach, prioritized improvements, and specific implementation actions.
- Ability to define and interpret readiness measures, identify underlying drivers, and connect metrics to authoritative data sources and management decisions.
- Strong facilitation and executive communication skills, including the ability to lead discussions with senior leaders and technical specialists and produce clear written decision products.
- Ability to work on site at Tinker Air Force Base and meet customer security, installation access, and suitability requirements.
Then "Preferred" heading: we could treat as Qualifications or Skills? The spec says we can have Qualifications, Skills sections. Preferred items could go under Qualifications or Skills. We'll decide to put under Qualifications (since they are preferred qualifications). Or we could split: Qualifications for required, Skills for preferred? But we already used Requirements for required. We'll put Preferred under Qualifications.
List:
- Current or prior B-1 experience within the System Program Office, Air Force Life Cycle Management Center, Air Force Sustainment Center, Oklahoma City Air Logistics Complex, Air Force Global Strike Command, the 448th Supply Chain Management Wing, DLA, or a B-1 operational or maintenance unit.
- Experience as a Product Support Manager, logistician, maintenance or production leader, systems engineer, equipment specialist, program manager, or readiness analyst.
- Experience with readiness dashboards, digital-product or minimum-viable-product development, data integration, data governance, or the improvement of weapon-system management information.
- Experience performing MICAP, FMEA, reliability, availability, supply-chain, or other structured root-cause analysis for aviation readiness.
- Active Department of Defense Secret clearance or higher.
Then "Why Join ASI Government?" heading: could be Benefits? Actually it's more like "Why Join". Could be Benefits? But we have a Benefits section later. The "Why Join ASI Government?" bullet points: Help B-1 leaders identify readiness risks earlier and make better-supported fleet decisions. Shape a usable readiness-management capability that will be designed for integration into the SPO's recurring processes. Work across the program office, depot, supply chain, operational units, and enterprise support organizations rather than within a single functional silo. Competitive compensation and comprehensive benefits package available on our careers site.
These are more like benefits/value proposition. Could be placed under Benefits. However there is also a separate "BENEFITS:" section later: "ASI Government offers a comprehensive benefit package to our employees. Benefits can be viewed on our careers site." That's vague; we should not create a Benefits section if content is just "comprehensive benefit package ... viewable on careers site" which is not specific. The rule: never create Benefits section unless posting actually states them. The "Why Join" section has specific points: help B-1 leaders..., shape..., work across..., competitive compensation and comprehensive benefits package available on our careers site. The last is vague but the first three are specific. So we can include a Benefits section with those three bullet points (maybe also mention competitive compensation). However the rule: "Prefer a few substantive sections over many thin ones." We could incorporate those points into a Benefits section.
We also have "Competitive compensation and comprehensive benefits package available on our careers site." That's somewhat generic but still mentions compensation and benefits. Might be okay to include as a bullet.
We also have separate "PAY TRANSPARENCY..." etc which is boilerplate to remove.
We also have "EQUAL OPPORTUNITY EMPLOYER:" etc boilerplate to remove.
We also have "REASONABLE ACCOMMODATIONS:" etc boilerplate.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications (preferred), Benefits (why join). Possibly also Schedule? No schedule info. Pay? Not specific beyond "competitive compensation". The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state "competitive compensation and comprehensive benefits package". That's a statement about compensation and benefits, but not specific numbers. Is that enough? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them, albeit generic. I'd say we can include a Benefits section (covers compensation and benefits). We'll not create a separate Pay section.
Thus we will output:
About the role
... (the introductory paragraph and job description)
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
- ...
maybe two paragraphs. It's okay to have multiple
under the heading. We'll just put them as separate
elements. Now list items: ensure we preserve all details. Let's craft HTML. Be careful to escape any HTML special characters? Not needed as plain text. We'll output:
About the role
ASI Government provides government leaders with the expertise they need to navigate acquisition and organizational challenges so they can make an impact and achieve their goals. For over 30 years, ASI has transformed the way government does business, impacting over 70 government agencies across the civilian, defense, and intelligence communities.
Do you thrive on creating unique and impactful value for Federal clients? Are you passionate about partnering with clients and collaborating to create solutions? Do you enjoy the opportunity to drive change that impacts our nation? We are looking for smart, curious, driven individuals to join us in partnering with our client to help them solve some of the nation’s most challenging problems. ASI Government serves as a trusted adviser to government leaders seeking improved performance, enhanced organization effectiveness, and strategic change.
ASI Government is seeking a senior B-1 Readiness and Sustainment Subject Matter Expert to support the Air Force B-1 System Program Office at Tinker Air Force Base. The initial 16-week effort will improve how the SPO manages fleet readiness by establishing a current-state baseline, assessing the data and integration landscape, prioritizing and designing a minimum viable product, and developing an implementation roadmap. You will bring the weapon-system and sustainment context that allows the team to distinguish how readiness decisions are actually made from how a process appears on paper. You will work with System Program Office (SPO) leaders, logisticians, engineers, program managers, depot and production personnel, supply-chain stakeholders, and an integrated consulting and digital team. Ideal candidates understand the B-1 sustainment ecosystem and can