Title: The RAT Pack Presentation to USAF T
1The RAT PackPresentation toUSAF T E Days
2Overview
- RAT Pack update (MGen Catton, ACC/A8)
- 53rd Wings initiatives to advance seamless DT/OT
(Col Wilsbach, 53rd Wing/CC) - AFOTECs perspective on OT construct (Mr.
Kitchen, AFOTEC/CA)
3Whats different?
- Broader threat--Asymmetric to peer competitor
- Were engaged in a long war
- Limited resources, tighter budgets
- Improved modeling simulation capabilities and
manufacturing processes - Combined DT/OT becoming the norm
Todays environment promotes concurrency, but we
must continue to validate capability through test
before we buy. Bottom line is. . . The
warfighter needs the biggest capability bang
for every buck...TODAY!
4RAT PackWho We Are and What Were Doing
- The RAT Pack consists of Air Force 2-Stars
across Requirements, Acquisition, Test
Evaluation, Fielding, Modernization Sustainment
organizations who decided we could do better for
ALL concerned if we approach what we do as a
team, committed to establishing a constant,
recurring, trust-based Enterprise that will
consult with each other to more efficiently
deliver capability to the warfighter
Its never over until its over, and its never
over
5RAT Pack Objectives Goals
- Our Requirements, Acquisition, Test Evaluation,
Fielding, Modernization Sustainment Enterprise
must do better at delivering what the warfighter
needs, when he needs it - We will continue the effort to regain enterprise
efficiency and credibility inside outside the
Air Force
- Our goals are three-fold
- ID points of friction in our processes
- Figure out how to fix them
- Promote the Enterprise vision
Its never over until its over, and its never
over
6RAT Pack Guiding Principles
- Requirements will change to meet evolving threats
and take full advantage of new technology how we
handle the change is the key - We will field the A-Model then evolve
capabilities using spirals / block upgrades - There will always be a lot of good ideas, but a
measured, disciplined approach to spiral
development is an absolute requirement - Success depends upon helping senior leadership
maintain a disciplined requirements process - Must inform leadership on the far reaching impact
of programmatic decisions due to political and
fiscal pressure - Weapon system story must remain consistent
program stable
7RAT Pack Guiding Principles
- Must meet warfighter needs from lust to dust
- Life cycle considerations like sustainability and
reliability must be built in from the beginning - Involvement must continue throughout system life
span - Requirements generation and documentation must be
a collaborative effort -- full enterprise
involvement - Acquisition community will translate warfighter
requirements into specs that produce
capabilities - Test community will ensure threshold requirements
are testable and verifiable
8RAT Pack Guiding Principles
- Strive to get the biggest capability bang for
every buck - Wont chase frills technology
- Optimize capability for cost
- Test is not an obstacle, it is a path to fielding
capability - Verifies spec compliance
- Improves system capability in development
- Defines and reduces risk
- Evaluates overall military utility
- Delivers validated warfighting capability
9Friction Points
- At the first Rat Pack summit we addressed the
following four friction points - Requirement to contract specification
- Test evaluation environment
- Seamless DT/OT throughout the RATF enterprise
- Spiral development vs. requirements creep
Todays focus on T E environment and seamless
DT/OT
10Test Evaluation Environment
- Threat crystal ball not always bore-sighted
correctly - Threat evolves differently than expected between
requirements definition and OT - May test against environment the requirements did
not address - OSD / DOTE focuses on effectiveness
suitability - Warfighter wants to know what system can do
- Is it significantly better than the current
capability? If so, buy it. - What is the best way to use the system as it
exists? - What are the risks and how can we best mitigate
them? - What do we need to improve through spiral
development?
OT based on evolving environment system designed
against predicted environment
11Way Forward
- Clarify and mutually understand AF and OSD
DOTEtest expectations - Establish credibility open communications
- Embrace AFOTEC improved TE reporting methodology
- Leverage test environment to develop TTPs and
future spiral development - Test early and often
- Change culture that ties negative test results
with program failure, to one that uses test
results (good bad) to inform program decision
making
Committed to delivering the capability the
Warfighter needs
12Integrated DT/OT Throughout the RATFM Enterprise
- AFIs direct early tester involvement, but
implementation is often vague - inconsistent
execution - Involvement is at discretion of SPO and is seldom
standardized - No program office prior to MS B limits early
development of meaningful test plan - Late standup of ITT and identification of
testability and verification issues - Absent a coherent ITT plan, benefits of
coordinated DT and OT efforts are not fully
realized - Need to do testing in such a way that the data
obtained is sufficient for everyone to use to
avoid regression testing - Too much sequential vice parallel TE activity
without full warfighter, test, and acquisition
collaboration
Enterprise leadership needs to foster TE
participation earlier in development and
throughout
13Way Forward
- RATFM should coordinate to ensure appropriate
representation at specific touch points for each
major program and make efficient use of existing
venues - General Officer Steering Groups
- Executive AFROCC sessions
- Establish specific guidance to stand up ITT
earlier (pre MS A) - Provide necessary resources to actively
participate - Leadership hold Enterprise accountable to
disciplined execution of AFIs - Enterprise needs to continue to encourage CTFs
and combined DT/OT
1453rd Wings Initiatives to Advance Seamless DT/OT
- F-15 OFP CTF
- H-60 CTF
- F-22 DT/OT Cooperation
- UAV
15Open Q A