MRO Current State.pdf
PDF 361 KB Posted
- Solicitation number
- FA8770-24-MRO_MRO-S_SS-RFI
About this file
This document is a Request for Information (RFI) related to a federal contract opportunity for Maintenance, Repair, and Overhaul (MRO) and Maintenance, Repair, Overhaul and Supply (MRO-S) integration and implementation support. The Air Force Materiel Command (AFMC), Air Force Life Cycle Management Center (AFLCMC) is conducting market research to assess vendor interest in this effort. The RFI provides background on the MRO program, which aims to establish a foundational baseline to satisfy complex depot maintenance requirements and expand Enterprise Resource Planning (ERP) capabilities across logistics and other business domains. The MRO-S effort will build upon the MRO baseline to provide a holistic solution for integrated depot maintenance, Air Force Working Capital Fund (AFWCF) financials, and wholesale and depot retail supply. The attached Statement of Objectives (SOO) provides a high-level system description, but the exact requirements will be included in a future official Request for Proposal (RFP). This RFI is for planning purposes only and does not constitute a solicitation or obligation on the part of the government.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Industry Questions and Responses.pdf | ||
| MRO and MRO-S RFI Rev 2.pdf | ||
| MRO and MRO-S RFI Rev 1.pdf | ||
| MRO and MRO-S SOO.pdf | ||
| MRO and MRO-S RFI.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
MRO Integrated Program Office (IPO) Leads
Functional Leads
AFSC/LZTC AFMC/FMF
AFSC/FZR
MRO Chief Engineer
AFLCMC/GBM
MRO Deputy PM
AFLCMC/GBM
(Lt Col)
System Implementer Accenture Federal Services
(AFS)
Functional(s)Technical / InfrastructureAcquisition Implementation
IPO Lead AFSC/LG
(SES)
AFMC/FM
(SES)
MRO Program Manager
AFLCMC/GBM
(NH-04)
Product System Manager
AFLCMC/GB
IPOs with Working Groups
Functional Management Offices (FMOs)
Program Management Office (PMO)
System Implementer (SI)
Scrum Teams*
*Personnel from each of these offices participate in the SCRUM teams
Integrated Test Team
AFSC/FM
(SES)
MRO Chief Developmental Tester
AFLCMC/GBM
MRO Milestone Decision Authority
PEO BES, AFLCMC/GB
(SES)
Scrum Teams
CAO: 5 Feb 24
ERP-CS
PM:
EN:
Enterprise Resource Planning- Common Service PMO (ERP-CS)
UNCLASSIFIED
MROi Agile Governance
Plan High-Level (PI Planning), Evolve Details Incrementally (Sprints)
Features/Stories Iteratively Prioritized by Stakeholders
Decentralized Decision- Making – Reviews at Demos
Objective, Fact-based Measures and Milestones (Velocity and Burndown)
MROi Governance Approaches
• Governance requires a retrospective
• MROi Program Review Board (LG, FM, PMO) was implemented over a year ago
• MROi Team updated charter for lessons learned and adjustment to agile ceremonies/artifacts
• MROi PRB is part of a larger 3-tiered Enterprise governance process; need to leverage lessons learned from
A4PB retrospective
Briefer: (AFSC/LZTC)
Ready
Entered into
ALM
(Program B/L)
Entered into JIRA
(SPRINT
B/L)
SCRUM
Stories
PRB
Approval
Feature Refinement
GV: 4 Feb 2022
N
Y
FMO Product Managers – Responsible for Functional Features o FMO “PMs” do not work at the team level but establish and maintain the strategic Solution/MVP Roadmap used to direct the overall team functional feature work priorities and timings on the Program.
o FMO PMs works closely with the team Product Owners to refine feature requirements making scope trade-off decisions for the MRO Program Backlog.
o FMO PMs work directly with end users through workshops to understand and capture specific needs.
PMO Product Manger – Responsible for Technical/Enabler Features o The PMO “PM” does not work at the team level but ultimately represents the customer’s needs with any Technical/Enabler Features. Enabler Features represent foundational architecture or “spike” work needed to support Functional work.
o PMO PMs work with the teams to make high-level design decisions and provide Enabler priorities and timing in the Solution/MVP Roadmap.
Release Train Engineer (RTE) o Chief Scrum Master for the Agile Release Train (ART). Executing the program increment and facilitating all PI Planning and Inspect & Adapt events.
o Works with Scrum Teams to identify, track, and elevate team risks, dependencies, and impediments through resolution.
o Coaches the Scrum Teams on Agile best practices and drives continuous improvement on the ART.
FMO Product Owners (POs) – Responsible for functional features o FMO representative to the team.
o Participates in and aligns to upstream Roadmap activities with Product Managers (Solution/MVP Roadmap).
o Functional PO responsible for upstream feature refinement for Team (Program Backlog Refinement feature-functional).
o Responsible for pulling in other experts to assist with Team backlog refinement readiness and approvals.
o Manages and prioritizes Team Backlog aligning with larger Product vision and goals.
o Responsible for approving functional user story and feature work acceptance; moves items to Done in Jira (user stories) and Octane (features).
PMO Engineer – Responsible for Technical/Enabler Features o PMO technical representative to the team o Acts as Team Product Owner for Enabler Features and Enabler Stories o Participates in upstream Roadmap activities with Product Managers (MVP Roadmap). PMO focus on enablers.
o Responsible for upstream feature refinement for Team (Program Backlog Refinement feature-enablers).
o Responsible for pulling in other experts to assist with Team backlog refinement readiness and approvals.
o Manages and prioritizes Team backlog aligning with larger Product vision and goals.
o Responsible for approving user enabler story and feature work acceptance; moves items to Done in Jira (user stories) and Octane (features).
FMO SME (Functional Subject Matter Expert) o Air Force end user functional subject matter expert.
o Peer reviews Team documentation as needed and attends demos confirming they meet story/feature Acceptance Criteria intent.
o FMO SMEs are government support and may not be available full time.
o Serves Team as functional interface Trading Partner (TP) liaison for Team and coordinating functional interface design and test sessions.
PMO Program Manager (PM) o Works closely with Scrum Masters to create and manage Team risks, dependencies, and impediments to resolution.
o Assists Scrum Master in resolving agile delivery process issue and offers alternatives.
o Should not be mistaken as a Product Managers. PMO Program Managers work directly with their individual Teams.
PMO Ops o Serves Team as interface Trading Partner (TP) liaison and network representative for Team establishing initial live connection and coordinating technical interface design/development/test sessions.
o Assists Team PMO PO in Enabler feature and user story refinement and approval.
MRO SCRUM TEAM ROLES AND RESPONSIBILITIES
Scrum Master (SM) o Facilitates Scrum Team events; represents Team in ART events including Scrum of Scrums.
o Coaches Team on agile planning and delivery processes & tools.
o Enforces and facilitates improvements to MRO agile delivery processes and standards.
o Assures that current PI/Iteration Plan risks, cross-Team dependencies, and impediments have been surfaced and accounted for in plans.
o Tracks, removes, and resolves dependencies and impediments for Team w/support from the Team and the impediment owner.
o Supports POs assuring features and stories are created and understood by Team.
SI Developer (Dev) o Develops configuration managed (CM) quality code/configurations using MRO and Oracle/industry coding best practices, standards, and guides.
o Open Oracle SR tickets, SD tickets, MTSD tickets, etc. as needed.
o Reviews the static Fortify and dynamic web inspect security scans and resolves findings.
o Completes user stories and features according to acceptance criteria.
o Responsible for moving code thru the code migration process for all instances.
o Completes code peer reviews for each user story containing code/configuration work.
o Identifies, estimates, and maintains Jira user story and subtask work items.
o Lead Dev: Supports code review approvals and developer mentoring to ensure quality code.
SI Tester (QA) o Ensures high quality code/configuration user story and feature deliveries that meets acceptance criteria intent.
o Identifies test scenarios/scripts/data and demonstrates user stories and features according to acceptance criteria.
o Captures all test scenarios/scripts and runs within test management tool (Octane).
o Perform exploratory and manual regression testing on critical areas of the system and/or areas which receive frequent updates.
o Maintains access to all test instances relevant to required test activities.
o Responsible for preparing and participating in Demos.
o Identifies, estimates, and maintains aligned Jira user story and subtask work items.
SI Training or System Tester o Plans aligned tactical issues to track work as needed.
o Completes aligned stories that meet acceptance criteria intent.
o Identifies, estimates, and maintains aligned Jira user story and subtask work items.
SI Business Architect (BA) o Supports the Team directly (including Product Owner) as a Oracle E-business Suite (EBS) process subject matter expert.
o Participates in upstream Roadmap activities with Product Management (Solution/MVP Roadmap) o Participates in upstream feature refinement with PO (Program Backlog Refinement) including feature acceptance criteria scope details, recommendations, and estimates; conducts Blueprinting and Conference Room Pilots (CRPs) as needed.
o Supports PO assuring features and stories are well written and understood by Team.
o Supports the Team with test scenario and data identification and execution.
LDTO Tester o Review and contribute to functional and system test data and scenario creation.
o Responsible for the acceptance (closing) of the System test tactical issues.
MRO SCRUM TEAM ROLES AND RESPONSIBILITES CONTINUED
Program Level Key Metrics
Program Level Key Metrics
| MRO Integrated Program Office (IPO) Leads |
| MROi Agile Governance |
| Slide Number 3 |
| Slide Number 4 |
| Slide Number 5 |
| Slide Number 6 |
| Slide Number 7 |
| Slide Number 8 |
| Slide Number 9 |
| Slide Number 10 |
| Slide Number 11 |
File details come from the government source that posted it. Updated .