1. Acquisition Strategy Panel Mandatory Template
SYSTEM PROGRAM MANAGER:
PROGRAM MANAGER:
CONTRACTING OFFICER:
Updated July 2008
Please refer to the notes section for valuable guidance

2. Template
This template is designed to provide the key topics necessary to address for a successful Acquisition Strategy Panel (ASP).
The briefing should address every Template topic. For those topics that are not applicable indicate n/a with a brief explanation.
The basic goal is to provide the decision maker an understanding of a well thought out strategy that considered all the important issues
Those programs that have OSD involvement need to ensure the PM addresses all of the potential areas that the OSD decision makers and staff might want covered when discussing a particular program strategy
See the Defense Acquisition Guidebook, particularly Sect. 2.3
See LCMP Guide
Information is contained in the notes section to help you in preparation of the briefing. The SAF/ACE and local ACEs are available to assist (see Notes section).
Sample charts are provided at the end of the template and are optional.
If you have questions in preparing your briefing please contact your local Acquisition Center of Excellence (ACE) for guidance.
ASC/AE DSN:   /COMM:  (937)
ESC/AE DSN:   /COMM:  
AAC/ENQA DSN: /Comm:
WR-ALC/AE DSN:   /COMM:  
OO-ALC/AE DSN:   /COMM:  
OC-ALC/AE DSN:   /COMM:  
SSG/AQE DSN:   /COMM:  
SMC/AXD DSN:   /COMM:  
MSG/XPA DSN:   /COMM:  
311 HSW/AE DSN:   /COMM:  
AFRL/AE Commercial: 
AFFTC/AE DSN:   /COMM:  
AEDC/AE DSN:  340/COMM:  
SAF/ACE Commercial: (If you have recommendations to improve the ASP template pls call )

3. ASP Discussion Items Addressed? If not, why?/comments
Program overview/description
Identify Program Goals/Objectives 
Linkage to other programs 
Capabilities/KPPs/Key acq. Obj. 
Expectations Management Agreement 
Funding/POE 
Confidence level 
POE/CAIG Estimate 
Risk Assessment 
Technology Readiness/Transition N/A Production contract
Industrial Base Considerations 
Acquisition Strategy
Proposed 
Alternative Strategies Considered N/A only one viable strategy
Program Schedule
Road to ASP Schedule 
Major Program Schedule (Critical Path) 
12 month schedule 
Systems Engineering 
Open Technology (MOSA-OTD) 
Test and Evaluation 
Please annotate in the next three charts what is addressed in the brief. For topics not covered, state justification.
In several cases below the main topics area specific sub-topics that has been identified because it is of special concern to senior leaders.
In some cases a specific item that is addressed, such as Unique Identifiers or Integrated Digital Environment Mgt (IDEM) while important may not be a critical element of your strategy. In those cases it is still mandatory that this item be addressed, but can be included in the back-up portion of the briefing. 3

4. ASP Discussion Items Addressed? If not, why?/comments
Product Support (LCM) 
SORAP 
ATS 
Data & Data Rights 
Market Research 
International Cooperation 
Small Business 
Business/Contract Strategy 
Deviations, Waivers, Delegations N/A None requested
Source selection 
Evaluation Criteria (Sect L&M) 
Contract Type 
Special T&Cs 
Contract Incentives 
How will you control costs? 
Manpower/Personnel 
Org structure 
Resources 
Experience 
Manpower ramp up/down plan 
Please annotate what is addressed in the brief. For topics not covered, state justification.
In some cases a specific item that is addressed, such as Unique Identifiers or Integrated Digital Environment Mgt (IDEM) while important may not be a critical element of your strategy. In those cases it is still mandatory that this item be addressed, but can be included in the back-up portion of the briefing. 4

5. ASP Discussion Items Other topics Addressed? If not, why?/comments
Envir & Manuft/Quality Engineering 
Interoperability 
Information Assurance 
Information Technology 
Research/Technology Protection 
Protection-Critical Progr. Information 
Anti-Tamper 
Human Systems Integration 
Environment, Safety, Occupational Health 
Military Flight Operations QA n/a ground equipment
Spectrum Management/Supportability 
Integrated Digital Environment Mgt  in back-up
Gov’t Furnished Equipment/Property n/a none provided
Modeling and Simulation 
Clinger Cohen Act Certification (CCA) 
Corrosion Control 
Insensitive Munitions 
Unique Identifiers  in back-up
Trusted Foundry 
Please annotate what is addressed in the brief. For topics not covered, state justification.
In some cases a specific item that is addressed, such as Unique Identifiers or Integrated Digital Environment Mgt (IDEM) while important may not be a critical element of your strategy. In those cases it is still mandatory that this item be addressed, but can be included in the back-up portion of the briefing.

6. Outline Bottom Line Up Front (BLUF) Program Structure (Overview)
Factors shaping strategy
Capability Needs/EMA
Program Cost Est./Funding
Risk Management
Technology Transition
Industrial Base Considerations
Acquisition Strategy
Proposed
Alternative Strategies Considered
Program Schedule
Systems Engineering
Product Support Strategy
Test and Evaluation
Business Considerations
Market Research
Sole Source vs. Competition
Source Selection
Contract Parameters
Contract Incentives
Small Business
Schedule To Contract Award
Program Office
Additional Acquisition Topics
Status of MS Documentation
What worries me?
Recommendations
Chart Samples
Final Thoughts
A couple of thoughts to keep in mind when developing your strategy:
The Acquisition Strategy:
guides program execution across the entire program life-cycle
should cover development, testing, production, and life-cycle support
must be flexible enough to accommodate acquisition oversight decisions both on this program and on other programs that may affect this program
should address the availability of required capabilities to be provided by other programs
establishes the milestone decision points and acquisition phases planned for the program
should prescribe the accomplishments for each phase, and identify the critical events affecting program management
should identify the critical path and what events are outside of the program manager’s control
should include a summary of the Integrated Master Plan and Integrated Master Schedule.

7. Bottom Line Up Front (Decisions Requested & Key program information)
Decisions you are requesting
Approve Acquisition Strategy
Approve Applicable delegations
Major Issues
List “show stoppers”
What are your concerns
Losing Funding
The idea behind this chart is to identify ASP panel chair decisions and to set the stage for the panel to understand key issues that may impact the strategy.
Are you requesting or have been granted any delegations?
J&A delegation and status
AP approval authority
ASP chairman
SSA Source Selection Authority
Clearance Review and Approval Authorities
Don’t wait to the end to bring up the negatives!

8. Program Structure Overview
Top Level Background
Identify (See following quad chart as a potential sample)
Identify linkage to other programs
Explain unique organizational structures or relationships
Internal/External Stakeholders
Identify OSD involvement
MS Decision Points and Acquisition Phases
Identify Program Goals and Objectives
The next chart or series of charts sets the environment and provides a picture of the program.
Program Overview: Linkages to other programs –Is the development and/or operational use of this system dependent on the development of another system or systems? If other programs and discuss status of those programs and the nature of the dependency. Same type of comments would go for relationships with other program offices including external agencies like FAA, GIA, DISA, NSA, etc.

9. Program X (“Strategy on a page”) Requirements/Direction
Using Organization(s) -
Capabilities Document –
PMD
FMS
Moderate Technical Risk
Decision Authority
MDA –
PEO Program – AFPEO/XX
ACAT Level –
SSA –
Delegations: In work
- e.g.., SSA, ASP Chair, LCMP
Financial Data
Est. Contract Value (Pre-SDD) -
Est. Total Program (qty) - $
Fund Type (Pre-SDD) – e.g.., 3600
New Start (Congressional) –
Strategy
Competitive or sole source
Incremental
Contract Type –
Estimated Contract Award –
Schedule MS A –
MS B –
IOC –
A good initial chart is this quad chart. It provides the “strategy on a page” for the panel It can be a series of one-liners—some of the topics that could be included are:
What is being acquired (hardware, SW, etc.)
Is this satisfying a joint requirement?
Whether effort is a mod, foreign procurement, cooperative development, new US development, or foreign military sale (FMS)
ACAT level
Whether strategy is incremental or single step
Entry point (MS A, B,C)
Whether competitive or sole source
Whether there will be successive down selects or recompetitions
Overall technology assessment
Overall Risk level
Next major activity
Funding status
New development

10. Factors Shaping Strategy

11. Capability Needs To Be Briefed by the Warfighter!
Discuss the capability required.
Macro level – ICD, CDD, CPD signed/dated
Critical capability highlights -Mandatory Key Performance Parameters (KPPs) and Key System Attribute (KSAs)
Acquisition Approach (Evolutionary?)
Explain how you know that this is realistically achievable within the time and funding provided.
Have the requirements been scrubbed and are they evaluatable in a source selection? (to be briefed by the PM)
Discuss what collaboration has been accomplished in developing these capabilities.
How has industry been involved?
Identify requirements Industry has indicated they can’t meet
What are your plans for future capabilities?
ICD—CDD; CDD—CDD (next Increment); CDD-CPD
It is preferred for MS A/B that a senior “warfighter” brief this section.
Capability/Requirement: Do you clearly understand the requirement/capability needed? Is it realistic? Do you and the operator have the same understanding of the requirement? Was the Program Office a part of the requirements development process? Was an HPT involved? How will the PO & operator continue to work closely as the PO “translates” the requirement into contractual documents? As you translate the Capability Documents to System Specifications do you have a cross correlation matrix (may be addressed under SE)? Samples charts are provided at the back of the Template. Who is the customer?
AFMC/CC has been delegated authority from SECAF to support the SAE by monitoring and controlling weapon system requirements baselines from MS A to fielding, & attest to requirements feasibility prior to all MS decisions. The info requested from the PM is intended to come from existing program data.
If you have an ICD, how/when will the CDD be completed, likewise a CDD to a CPD or CDD to the next CDD if evolutionary in nature. For a MAIS program, address the applicability of a CPD when there is no "production"; address any agreement with the users regarding applicability of a CPD.
Other topics to address as appropriate
Jointness
Is AoA, CONOPS complete; other alternatives considered (DOTMLPF)
Does the document identify incremental requirements
Need dates per increment

12. Expectations Management Status of Agreement
Explain your signed Expectation Management Agreement (EMA)
EMD date
Demonstrate (money=content=schedule)
Include the “nice to haves”
What change process is in place?
Who authorizes changes?
Update w/ PMD 45 days after President’s Budget submission
Update out of cycle with major perturbations
If you do not have an EMA, explain your plan to get one including any potential obstacles
Program Management Agreement
Identify PM Tenure Dates (or in manpower section)
Expectation Management—a key element of our acquisition approach is to ensure that the “warfigher” and the acquirer are on the “same page.” The Expectation Management Agreement (EMA) approach is designed to ensure the acquisition community delivers on its promises--what can be delivered, when it can be delivered and the funding needed to accomplish it.
Does your understanding of the requirement meet the operator's expectations? Do you have an EMA in place?
Programs entering MS A should have a signed agreement, but programs entering MS B must have a signed agreement between the PEO and the MAJCOM/DR or XP or potentially the MAJCOM/CV. In rare cases the requirement for a signed agreement may be waived by the SAE; in these cases, a plan to attain the agreement must be presented. Demonstrate the fact that funds=content=schedule are in sync.

13. Program Cost Estimate/Funding
Identify your cost estimate
Identify the Confidence level of the estimate (50-90%)
Identify if this is a Program Office or Service Cost Estimate
Address any AFCAA/OSD CAIG issues that may exist
Specifically address funding shortfalls
Explain your budget plans
RDT&E plan for executing obligation and expenditure
Explain what MAJCOM commitment exists to cover shortfall as applicable (EMA)
Provide an overall funding chart
Required by FY/color
Actual by FY/color
The acquisition strategy shall address the estimated program cost and the planned program funding, including advanced procurement funding.
Cost Estimate
Identify type of cost estimate: Parametric, catalog, etc.
Identify if any data was contractor provided as in a response to an RFI
Address any funding issues/disconnects, to include phasing/types of funds.. Explain your work around plans to continue performance. How does this impact risk? What are MAJCOM commitments to supporting the program in the out-years( Linked to the affordability KPP and the EMA)?
OSD requires ACAT I programs to be fully funded.
If there is a funding mismatch, the PM should present a fully funded program at the “disconnect number.”
If an evolutionary approach is being used fully fund 1st increment of capability. Funding of subsequent increments should be discussed.
Is the program funding currently supported in the President’s Budget?
As part of the MS review, the MDA should approve specific exit criteria for advance procurement.These specific exit criteria must be satisfied before the PM releases any advance procurement funding. The PCO should initiate a separate contract action for advance procurement of long lead materiel.
If a new start highlight on the funding slide so chair knows all new start requirements have been met

14. Mandatory Program Office Estimate (POE) Mandatory by Air Force and OSD
Identify if this is a new start

15. Risk Management Risk Assessment with Mitigation
Identify the key Programmatic Risks—Cost, Funding, Schedule, Performance (Technology, Software, Manufacturing), Industrial Base, Manufacturing, Political?
What are they? Why do you think they are the only ones?
How are you going to address them?
In the following charts, plan to use various mitigation strategies to address them
What is the technical maturity level of your system? Is this the appropriate strategy given the technical maturity level?
Describe your top technical challenges
Who assessed the technology levels? Labs?
What are they, why do you think they are the only ones?
Provide Risk Matrix
See Section 4.2 of DoD Guidebook
The program manager should establish a risk management process to identify, track and mitigate and summarize the process in the Acquisition Strategy.
Programmatic/Technology/Technical Challenges:
Have you evaluated/identified:
Congressional/OSD oversight issues/concerns?
Relationship of technology to the capability needed? Is technology mature? Explain how you have assessed the TRL (who validated?). How has AFRL been involved? What is the back-up plan if the technology doesn’t come along at the required point in time.
What is your mitigation/management plan for insuring that technology is available for insertion when required?
Other technical challenges/risks. Have you determined the impacts/consequences of future changes? Does this capability impact other systems?
Any Clinger Cohen Act, Title 10 Testing requirements ?
Address all known certification requirements like Frequency Certification, DIACAP, Interoperability certifications, etc in terms of risk.

16. Program Risks Mandatory risk workshop completed –Date/By Whom Low Med
Risk Areas—Technical, Cost, Schedule, Logistics, Integration, etc
Mitigation Plan
Low
Med
High
Impact
Negligible Critical
100% 0%
Risk Areas (Increment 1)
Technology Issue
Mitigation Plan
Probability
Risk Areas (Increment II)
Mitigation Plan
Mitigation Plans should be realistic and descriptive.
The purpose of the mitigation plan is to describe how this particular risk will be handled – what, when, by who and how will it be done to avoid it or minimize consequences. A good risk management plan should contain a schedule for control implementation and responsible persons for those actions.
Examples of risk mitigation efforts include reducing software development risk by developing and delivering software incrementally, prototyping, simulation, alternative designs, additional resources (earlier engineering involvement, additional engineers), workarounds, etc.
risk workshop completed –Date/By Whom

17. Risk/Cost (Schedule, technical, or software)
Mandatory
Requirement: Develop/Procure xyz system
Risk Statement: Eg., Cost proposal exceeds budget
Impact: Address impact of risk
Probability: 4
Consequence: Serious
Risk Rating: High (Red)
Risk Management: Address mitigation approach
(Describe risk handling plan, milestones and risk closure criteria)
Post Risk Management Rating: Probability 1, Serious, Moderate (GREEN)
Higher "moderate" and "high" risks should be highlighted here. Pre-Mitigation assessment should be kept as back-up.
If previous chart doesn’t allow for full discussion of high risk issues you can use this chart to show more information and/or to supplement previous chart.
Risk Statement: An adverse event that impacts the ability to obtain the requirement. Worded as an event that might occur in the future.
Impact Statement: Worded in programmatic and/or operational terms.
Probability: Range of probability
Consequence: High, mod, low or red, yellow, green
Initial Risk Rating: High, mod, low or red, yellow, green
Risk Handling Plan: Describes what you’re going to do to try to avoid having the risk event occur (lower the probability) and/or reduce impact if the risk event occurs.
Post Risk Management/Mitigation Rating: The risk rating assigned after planned mitigation efforts (the anticipated risk assessment if the Risk Management Plan and Mitigation plans are effective as thought).
Any significant risk/issues and associated close-out plans should be addressed with the respective OPRs and home offices to ensure their respective SAT member concurs with the briefing.

18. Technology Transition (As Applicable)
Explain how you have assessed the technology available in development to ensure rapid insertion
Technology Readiness Level: entire technology aspect
Status of Technology Readiness Assessment
Fold in to the program—dovetail with contractor efforts
Explain what plans you have for keeping track of new developments within the laboratories/battle labs etc.
Address areas of technology the program is going to support and any MOAs or informal agreements that you have with Laboratories (i.e., AFRL, NRL, LLNL, etc)
Reminder that the MDA at MS (KDP) B must certify (Sec 2366a, Title 10), that the critical Technology has been “demonstrated in relevant environment”, which equates to at least a TRL 6.
Given this edict, Technical Transition strategies can reduce the time and expense associated with inserting new and improved technology into systems. SAF/AQ and AFRL emphasize collaboration in developing, assessing and inserting technology advancement. Explain what technology is required for your system, what research and collaboration you have accomplished to assess the availability and applicability of new advances. Identify why you think your technology is mature enough to enter the particular milestone. Technical maturity includes the manufacturing aspects as well as the science. Identify any specific agreements you have established to support or monitor technology development from the laboratory environment.
Address when discussing the status of technology who besides the program office has validated the state of the technology needed for the program—eg., laboratories, etc.

19. Technology Readiness Levels (TRL)
Mandatory
Technology
 TRL
Incr 1
Incr 2 9 X 6 8 7 5
Technology Readiness Levels (TRL)
9. Actual system “flight proven” through successful mission operations
8. Actual system completed and “flight qualified” through test and demo
7. System prototype demonstration in a operational environment
6. System/subsystem model or prototype demonstration in a relevant environment
5. Component and/or breadboard validation in relevant environment
4. Component and/or breadboard validation in laboratory environment
3. Analytical and experimental critical function and/or characteristic proof-of-concept
2. Technology concept and/or application formulated
1. Basic principles observed and reported
The category of Technology identifies the key technologies necessary for this program. Column 2 the technology level and the next two columns in this sample (showing two increments) provides the increment in which the technology will be delivered.
This sample generally applies to hardware

20. Industrial Base Capability
Industrial Capability
Address industry’s capability to design, develop, produce, support (product technology obsolescence, replacement of limited-life items, regeneration options for unique manufacturing processes, and conversion to performance specifications at the subsystems, component, and spares levels) , and, if appropriate, restart an acquisition program.  (see notes section)
Address the effort performed as part of your analysis to determine the need for government action necessary to ensure a robust US Industrial and Technical base
Are new industrial base capabilities required?
US or off-shore manufacturing?
Diminishing Manufacturing Sources (DMS)
Address the possibility for cooperative research and development opportunities
10 U.S. C. Sec Technology and Industrial Base Plans
The SecDef shall…require consideration of the national technology and industrial base in the development and implementation of acquisition plans for each MDAP
DoD 5000 Guidebook--excerpts
Industrial Capability In many cases, commercial demand now sustains the national and international technology and industrial base.  The following should be considered:
Need for new defense-unique industrial capabilities.
Availability of Foreign sources/international cooperative development
Address security considerations of foreign sources
Industrial surge capability.
Analysis of industrial base capability to design, develop, produce, support, and…restart a program. 
Considerations for the analysis include the following:
Investments needed to create or enhance certain industrial capabilities
Risk of industry ‘s ability to provide program design or mfg capabilities
If analysis indicates that industrial capabilities are in danger of being lost the strategy needs to consider what government action is required
Analysis should address obsolescence, replacement parts, unique mfg processes…spares levels.
US Code SEC requires that at MS(KDP)A that cooperative opportunities be considered and a Cooperative Opportunities Document be prepared

21. Acquisition Strategy
The Acquisition Strategy defines the approach the program will use to achieve full capability: either evolutionary or single step; it should include a brief rationale to justify the choice. (See notes for additional information)
Prototyping and Competition (See 19 Sep 07 USD AT&L) and notes below
Present the proposed strategy and viable alternative strategies considered; the pros and cons of each; justification of why the proposed strategy was selected, This allows the ASP Chair to have an understanding that the strategy he/she is approving is not only a good one but that it is the best one of several considered. Without this dialogue, the ASP Chair has no way of knowing (other than gut feel) that the proposed strategy is the best strategy.
Will you develop the system using an evolutionary acquisition strategy? If so, discuss your incremental development approach. Why does this approach mitigate risk? How is technology going to be developed to meet your evolutionary approach?
Demonstrate you understand the inherent challenges that spiral development provides: concurrency, retrofit, and configuration control issues.
On 19 Sep 07 USD (AT&L) issued a policy letter mandating the consideration of prototyping and competition. “To implement this approach, the Military Services…will formulate all pending and future programs with acquisition strategies and funding that provide for two or more competing teams producing prototypes thorough Milestone (MS) B.”

22. Proposed Acquisition Strategy
As many charts/backups to explain/justify the proposed strategy (basically the initial part of the briefing builds to this point while the rest of the briefing supports this chart.)

23. Alternative Strategies Considered
Can be in the form of pro/cons, or +/- against a set of listed parameters that were considered as the PM decided on the proposed strategy. Parameters could include cost, schedule, technology, infrastructure, risks, GIG connectivity, etc. See sample charts at end of briefing.

24. Program Schedule MS Decisions and Key Program Events
Event driven milestone chart
Include major milestones (Decision Points/Acquisition Phases)
See sample charts
Major events required to make an award
OIPT or ITAB/DAB
Key documents needing approval
Provide the following schedule charts:
How we got here
Long term program Schedule
Critical Path chart
12 Month schedule chart
Provide an event driven milestone charts. Indicate the impact of failure to meet key events. Clearly articulate how your program impacts others. While slipping one program milestone by a few months may not appear serious, if it causes perturbations to other capabilities more serious mitigation plans may be appropriate.
Include a schedule that is comprehensive schedule that shows the critical path--identifies the events/documents and documents associated with an upcoming milestone. If an event such as a MS or SDR has slipped indicate original MS date and new date. Include the AOA as well as the ISP if these are applicable to your program. Include the Capabilities Document, the Cost Assessment Requirements Document and Independent Cost Estimate depending on whether your program is an MDAP or MAIS. If the TEMP is not signed, identify it. Overall, these documents play a major role in gaining Clinger Cohen Act certification necessary for successful completion of a major milestone. Therefore, lay out a critical path that demonstrates that you understand the crucial issues required to be addressed.
Also include MDA decision points.

25. Program X Schedule How we got to this point!
Mandatory
FY:
2006
2007
2008
2009
2010
2011
2012
Milestones:
MS A
MS B
Concept
Decision
Capabilities
Documents
ICD
CDD
Strategy
Development
Effort
LEGEND
Program Milestone
Gov’t Milestone
Market Research
ESIS
Risk
Workshop
Wing
Review
PEO
ASP
SAE
ASP
Minimum events to include—market research (could include industry days), ESIS, Risk Management, Wing Reviews, PEO ASP. The program office should include other events as appropriate—e.g., requirements timeline, etc.
Today

26. Program X Schedule Single Increment
Mandatory for
single Increment
FY:
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
Milestones:
MS A
MS B
CDR
MS C
Concept
Decision
FRP
IOC
(6/6)
Capabilities
Documents
ICD
CDD
CPD
Tech
Demo
LEGEND
Program Milestone
Gov’t Milestone
As a reminder this schedule is generic and as an example it depicts testing to show the goal of a integrated DT and OT testing. Normally IOT&E testing is accomplished normally using LRIP items. IOT&E cannot be done using a prototype unless the OT&E (DOT&E with MDAP) approves. An alternate schedule might show the integrated goal as using DT&E/OA (operational Assessment) than a short IOT&E.
RFP Rel
Sys Design/Integration
S D D
System Demonstration
CT&E
DT&E IOT&E
Logistics
SORAP
LRIP
# of items
PRODUCTION
# of Items
FRP

27. Program X Schedule Multiple Increments
Mandatory for
Multiple Increments
FY:
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
Milestones:
MS A
MS B
MS C
Concept
Decision
FRP
IOC
(6/6)
Inc 2 MS B
Inc 2 MS C
Capabilities
Documents
Inc 2
CDD
ICD
CDD
CPD
Tech
Demo
LEGEND
Program Milestone
Gov’t Milestone
Sys Design/Integration
Increment 1
As a reminder this schedule is generic and as an example it depicts testing to show the goal of a integrated DT and OT testing. Normally IOT&E testing is accomplished normally using LRIP items. IOT&E cannot be done using a prototype unless the OT&E (DOT&E with MDAP) approves. An alternate schedule might show the integrated goal as using DT&E/OA (operational Assessment) than a short IOT&E.
System Demonstration
RFP Rel
DT&E IOT&E
S D D
CDR
Increment 2
Sys Design/Integration
System Demonstration
RFP Rel
CDR
DT&E IOT&E
Increment 1
LRIP Fab
# of items
PRODUCTION
Increment 1
FRP
# of Items

28. Sample Critical Path Schedule
In back-up charts

29. Milestone Schedule (12 Month)
Mandatory
Milestone Schedule (12 Month)
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
JAN
FEB
Milestones
AFRB
DAB
Source Selection
Contract Award
SS Debrief
SAE ASP
OSD Review
AS Approval
RFP Release
Proposal Receipt
Contracting
FPR
Program
Management
Program Startup Conference
Show short term schedule driving towards the milestone. 12 month version offered as starting points to tailor.
TODAY

30. Systems Engineering (SE)
Describe how your overall SE approach drives and supports the acquisition strategy across the acquisition life cycle
Show linkage to acquisition life cycle activities such as:
Requirements planning
Technology development/maturation and transition
Risk management
Integration into/with other systems in SoS or FoS environment
Technical baseline management
Technical reviews (including Gov’t Peer Reviews)
Describe key components of the RFP and contract
Identify key RFP requirements and selection criteria to evaluate bidder’s approach to SE and a robust design (or address in the source selection part of brief)
Identify key contractual provisions to ensure contractor implements proposed approach
Show how SE approach will yield a robust system or capability and describe the technical management of the program across the acquisition life cycle.
Pre-Milestone A: Show how requirements planning evolves into technology development. What are the critical system parameters? How are program risk and technology transition addressed? Explain SoS/FoS considerations/ implications. Identify key trades in characterization of concept/systems architecture. What are the supportability and maintenance concepts and technologies? Provide status on technical reviews (ITR/ASR) and the entry-exit criteria for technical reviews in the next phase (SRR, IBR, PDR, TRA)?
Pre-Milestone B:
How is technology maturation assessed? Discuss S&T involvement.
How does the integrated T&E/V&V strategy support the acquisition strategy?
What strategies support the supportability & affordability of the system including use of common interface standards, open systems architectures, and commercial components.
Describe interfaces with prime contractor/vendors to manage technical aspects of the program. Provide status on key technical reviews conducted (SRR, PDR)-- identify reviews planned for the next phase (e.g., CDR, TRR, PRR) and entry/exit criteria. What metrics will track contractor progress? What data will you need to manage and access & what data rights have been secured? What contractual provisions have you included to ensure the bidder will implement his proposed technical management plan and ensure establishment and maintenance of a quality team?
How will you interact with other systems and programs to ensure unintended consequences are identified early and mitigation plans are effected? What certifications are required & how are they factored into the technical management plan?
See notes – use multiple slides as needed

31. Systems Engineering (SE)
Open Technology Development Considerations
Modular Open Systems Approach / Open Architecture
Modular system and design disclosure: Have you identified key interfaces, data elements and sub-systems (incl. S/W) which should be open / common / standard?
Is there a reference implementation architecture and set of default standards for your domain of operation? Applicable?
Open Source Software Methods / Software Reuse
Contracting approach for S/W licensing and Intellectual Property (IP) rights
Application Programming Interface (API) disclosure / delivery
OTD encompasses MOSA principles as well as strategies for software reuse; for OTD definitions and discussion, see:
Your Center EN and/or XR organization can guide you through an OTD assessment to determine the extent to which you should apply OTD principles. As such this slide can also be a summary based on an independent (EN or XR) assessment of your approach to OTD.
Key Interface / Component Designation, consider: Diminishing Manufacturing Sources (DMS), desire to reduce barriers to 3rd party innovation, interfaces driving program cost / performance / supportability, components that change frequently, requirements to be interoperable/net-centric
Reference architecture and default standards: consult your EN and/or XR organization to discuss whether there is a default implementation architecture and corresponding set of default open standards to guide your acquisition. If applicable, consider how this guidance could be used in your solicitation to drive openness in key components and interfaces.
IP Rights Considerations, as applicable:
1. Approach for key components: Gov’t Purpose Rights, Unrestricted Rights, Restricted Rights?
2. Open Source Software licenses: e.g. GPL, L-GPL, BSD – consider applicability of OSS to fulfill technical requirements…OSS is by DFARS definition a Commercial Item / COTS
For more information about addressing this topic in your ASP / AFRB, contact Ms. Monique Pryce in SAF/AQII, DSN ,
See notes – use multiple slides as needed

32. Systems Engineering Cont…
Describe your approach to translating Capability documents to systems specification. If available provide a capability cross correlation matrix that indicates the KPPs, KSAs, the translation of those requirements into the systems specification (sample in backup charts).
Discuss status of initial manufacturing concepts and their implementation (pre-MS B/C)? What is the status of LRIP manufacturing capabilities and ability to ramp up to full rate production?
Status of Production Readiness Review
What are the critical manufacturing elements?
Pre-Milestone C: What are key activities required to achieve IOC and FOC? Provide status on key technical reviews conducted: SRR, PDR/CDR, TRR, PCA/FCA, PRR, etc. How has technical management planning activities changed (organizational and processes)?
Pre-FRP: What is the status of LRIP manufacturing capabilities and ability to ramp up to full rate production? What are key activities required to achieve IOC and FOC? Provide status on technical reviews conducted (PCA/FCA). How has technical management planning activities changed (organizational and processes)? Has a Manufacturing Readiness Assessment been performed?

33. Product Support Strategy
Source Of Repair Decision (See footnotes)
Status of your Source of Repair Assignment Process
Organic and Contractor Capability/Capacity
50/50 Assessment
Source of Repair Assignment Process (SORAP) Completion Date (see notes)
Partnership Opportunities for Repair
Core vs non-core impacts to strategy
Source of Supply Decision
Diminishing Manufacturing Sources (DMS) Considerations
Reliability, Maintainability, Availability (if not addressed elsewhere)
Evolutionary Acquisition effects on Supportability
Berry Amendment implementation in sustainment
DO NOT ASSUME CONTRACTOR LOGISTICS SUPPORT FOR LIFE OF THE SYSTEM.
Explain how you have planned to insure that the delivered system is going to be supported.
Have you considered your Source of Repair Assignment Process?
What impact does this have on the depot repair management allocation?
Have you coordinated with AFMC and/or AF/IL?
An initial Depot Source of Repair (DSOR) assignment will be made prior to MS B.
Address the life cycle supportability approach and the challenges the program may face such as reliability, parts obsolesce, and bare-basing in remote areas.
What are the considerations for transition to sustainment?
Has support been incorporated into your EMA? Explain why the EMA does not include support commitments, as applicable to your program.
Discuss whether the program is based on an open standard consistent with MOSA & OTD guidance and what impact compliance or non-compliance impacts robustness in design and ultimately the support strategy including sources of repair and DMS considerations, etc.
What is the configuration management plan for future modifications?

34. Product Support Strategy
Automatic Test Systems
Discuss approach and schedule
Will waiver be necessary?
Performance Based Logistics
How has performance based logistics been factored into your overall strategy?
Have you accomplished a cost benefit analysis incorporating OSD policy?
Address types of measure used for PBL (e.g, Flying hours, MC rates, availability, etc.)
Address impact on user’s flexibility to fund PBL
Discuss approach to acquiring engineering data and data rights (See notes from the FY07 NDAA)
Are you using the Acquisition Sustainment toolkit? See footnote for link
The ATS discussion needs to include new/replacement, Organizational, Intermediate and Depot (See AQ/A4/IL & AFMC policy letter 26Nov07
The Air Force ATS focal point:
ATS Leadership Office, 742 CBSG, WR-ALC, Ga: Phone , DSN
Address either here or in the source selection section how the acquisition of engineering data and data rights will be addressed to ensure the government’s long term interests are protected.
PMs for MDAPs and subsystems of major weapon systems need to
Assess the long term tech data needs
Address Acquisition Strategy to sustain system over life cycle
Strategies may include in-DoD maintenance capabilities
Competition for contracts for sustainment
Address merits of priced options for future delivery
Address the potential for changes in sustainment plan over life cycle
URL for Acquisition Sustainment Toolkit:

35. Test and Evaluation
Describe the T&E Strategy and how it supports the acquisition and requirements strategies (See notes).
Identify issues regarding availability of production representative test articles, test facilities, Systems Integration Labs, Collaborative Development Environments
Also describe capability shortfalls of the test ranges.
Have you developed your TEMP?
Do you have the time, budget, and assets required for test
Are the Critical Operational Issues (COIs) linked to Critical Technical Parameters (CTP) and Measures of Effectiveness (MOE)?
Is DOT&E involved? If so, what is their position regarding integrated testing economies
What specific challenges are addressed through your test strategy?
How have you incorporated Modeling and Simulation into your strategy and what challenge does this address
T&E is more than just DT and OT (we have contractor testing, IA testing, interoperability, etc, all of which must be integrated). The T&E strategy, acquisition strategy, and requirements need to be in sync with each other. A T&E Strategy must be prepared for a MS A decision
Discuss your approach (pros/cons) for reducing test time and redundancies. Specifically explain how this is going to reduce testing cost and schedule as applicable and emphasize what specific buy-in you have from key stakeholders: AFOTEC, DOT&E, the PM and/or AF/TE.
Has an Integrated Test Team (ITT) been formed and a charter signed?
Has the TEMP been fully coordinated? What are the open issues, if any? When will it be completed?
Have you assessed the Critical Operational Issues, Critical Technical Parameters, and Measures of Effectiveness? Are they linked and achievable based on the schedule/funding estimates? Are there any high-risk areas that lower the probability of success, and if so, are they included in your EMA?.
Identify the Responsible Test Organization (RTO) and the operational test organization (i.e., AFOTEC or MAJCOM) according to AFI
In describing capability shortfalls of the test ranges keep in mind that some new technologies require test resources that do not yet exist or do not exist in a form appropriate for final DT/OT (e.g. directed energy). Have you had input from the test community (or an experienced tester?)
How will M&S be used in your tests? Does it replace or supplement. Also what challenge does it create? Are the M&S tools validated? How will the data to support the models be generated?

36. Business Considerations

37. Market Research Sources Sought Synopsis Results Industry Days Held
Industry Feedback on requirements, contract type, incentives, etc
Prospective Sources
Qualified SB Sources?
Consideration of SB program set-asides or partial set asides; i.e., SB, 8a, SDVOSB, HUBZone.   
Consolidation/Bundling Issues?
Potential for International Cooperation Program
Potential for FMS
ITAR issues
Explain how your approach supports the socio-economic (Small Business/Small Disadvantaged Business) responsibilities of the Air Force.
Potential ITAR issues (technology, technology sharing, source code issues, etc. Information Assurance issues associated with offshore development of SW code and/or use of COTS components developed offshore. IA is one of the certification hoops that programs need to jump through.
Should also address unusual contract provisions that impacts the prime and all vendors. This can also be addressed in the contract parameters chart.

38. Sole Source vs. Competitive
Sole Source Topics
Authority
Future Competition
Competitive Topics
Source Selection Procedures
Source Selection Organization
Address the Source Selection experience of the team
Evaluation Criteria with Weighting
Tied to Risks and Significant Discriminators
See Sample Matrix chart to be included with Briefing
Be prepared to Discuss in detail
Selection criteria to address Section 801 certification requirements for MDAP programs at MS B (See notes)
Describe your contracting approach. Will it be sole source or competitive? How will you maintain competition in the future or does it make sense?
If this will be a source selection it is Mandatory to describe the source selection approach-structure, SSA, Criteria—key section L&M criteria
USC Title 10, Section 2366a, levied a new requirement for the Milestone Decision Authority (MDA) to certify, at MS (KDP) B, that the technology in a Major Defense Acquisition Program has been demonstrated in a relevant environment. Address Sections L&M approach to ensuring that offerors demonstrate in their proposal they are proposing technology that has achieved at least Technology Level 6 (See Technology Readiness Assessment Guidebook for definition)
Describe the type and number of contracts you expect and why you chose that approach.
Address any inter-organization relationships that might be applicable.
Note: FOR OFFICIAL USE ONLY once Section L&M information provided

39. This or the next chart is Mandatory
Source Selection
The purpose of this chart is to demonstrate the flow of Risk elements and discriminators in source selection. Specifically, how do you plan to measure the contractor’s performance? How will you incentivize the contractor (Can address on a later chart).
Ties into earlier risk charts
This chart could be expanded after receipt of contractor’s proposal to help in tracking your management of risk.
This or the next chart is Mandatory
How do you plan to measure and incentivize contractor’s performance?

40. Evaluation Criteria Selection Mandatory
Source Selection
Evaluation Criteria Selection
Mandatory
Top Risks
ACTS Availability
Ops Terminal
Control Functions
Software Development
AEHF Launch
SCA Compliance
DMSMS
Robust Systems Engineering
Mitigation
OPS Architecture
Section M
System Performance
System Engineering Integrated Process
The purpose of this chart is to demonstrate the flow of Risk elements and discriminators in source selection. Specifically, how do you plan to measure the contractor’s performance? How will you incentivize the contractor (Can address on a later chart).
Ties into earlier risk charts
This chart could be expanded after receipt of contractor’s proposal to help in tracking your management of risk.
Architecture
Fielding study
Management
Program Monitoring
Section L
System Data Management
Operator Terminal Control
Specialty Engineering
Software Engineering
Address Incentives used to alleviate risk areas
This or the previous chart is Mandatory

41. Contract Parameters Commercial vs. Noncommercial
Rationale – Commercial Item Determination (CID)
Industrial base and foreign competitors (if not addressed somewhere else)
Contract Type (See footnote for development programs)
Need to discuss the rationale for your contract type
What measures are in place to control contract costs?
Contract Structure
Performance Based
Special Terms and Conditions
E.g.s, Organizational Conflict of Interest (OCI), Pricing Matrix
Berry Amendment
Subcontractor Management
Make or Buy considerations
Restriction on using only Cost type contract for development has been revised to favor use of Fixed price type contracts for Development.
Now At MS (or KDP)-B the MDA must
Select contract type consistent with program risk
Document basis for contract type & explain level of program risk
If MDA determines program risk is high
Document the steps that have been taken to reduce risk and reasons for proceeding with MS B approval despite the high level of program risk
Congress has directed that the preferred type of contract for development is a Fixed Price contract. However, for Development the MDA may authorize cost-type contract upon written determination that
Program is so complex & technically challenging that it would not be practicable to reduce risk to level of fixed-price contract
Complexity & technical challenge is not result of failure to meet Milestone B Technology certification requirements
Describe the geometry of the contract type, e.g. target cost, target fee, min/max fees, share ratios, ceiling prices as applicable for the contract type—may be discussed as part of the Incentive discussion

42. Contract Incentives Discuss why an Incentive is needed
What are the key program risks and how can incentives help to mitigate risks and improve probability of success? (See notes below)
What Objective Incentives were considered and why (See FAR Subpart Incentive Contracts)
Will an Incentive Fee be used?
What type (Is there adequate funding to cover it?)
How will incentive control costs?
Award Fee
How is award fees linked to the acquisition outcomes—cost, schedule and performance?
How is award fee tied to specific challenges & delivered capability versus just “effort”
What are the specific areas you want to incentivize?
Objective/Subjective criteria
How do these track to risk areas?
How do you know this incentive is adequate to drive behavior?
The right incentives can reduce challenges by focusing the contractor toward those areas you identify as critical.
Describe the incentives structure
Cost Incentives (e.g. CPFF, CPIF, FPIF, FFP—describe geometry of incentive, e.g. target cost, target fee, min/max fees, share ratios, ceiling prices as applicable for the contract type;
Performance Incentives (Objective performance incentives for products or services);
Schedule performance
You must explain why you chose the incentives, how you determined they actually provide the right motivation, and what challenge(s) they address. How do incentives relate to your critical problem areas identified in earlier charts?
Examples follow (tailor to your program):
Maximize system performance (objective performance incentive)
Reward cost control (Cost incentive)
Reward schedule performance (objective performance incentive)
Incentive for establishing and implementing processes (e.g. subjective incentive for system engineering, program management etc.)
Reward services, customer support, quality etc. for services
Reminder –no award fee can be paid for performance not meeting contract requirements

43. Contract Incentives Award Fee Cont…
How will the contractor’s performance be judged?
How will award fee periods be structured?
Will there be a base fee?
Will award fee be back loaded (to ensure enough money at end of contract in case schedule slips)?
Do you plan to use rollover? Why? What specifically do you plan to use rollover for?
Who is the Fee Determining Official (FDO)?
Is that the appropriate level?
Are there negative incentives for overrun or poor performance?
Award fees need to be focused toward actual delivered capability and not just on effort. Clearly identify the expected percentages and dollars that you anticipate awarding for an acceptable ("OK") job as well as an exceptional one along with consequences for poor performance. Ensure you have enough incentive at the end of contract to motivate contractor. If milestones are included, successful completion of the critical entrance criteria and eventual exit are more important than having a meeting.
Rollover should be used as the exception rather than the rule.
Reminder—award fee must be earned--Scoring starts at zero

44. Small Business
For companies who are not in the Comprehensive Subcontracting Plan Test Program
Describe your approach for incorporating SB/SDB business subcontracting goals into your overall acquisition strategy
Remember the Air Force’s objective to maximize subcontract awards to small business
Discuss how you determined the appropriate SB/SDB subcontracting goals
Use factual data from your market research
Include a review of potential offerors’ subcontracting performance at the business unit sector – explain the results
Explain how your analysis enabled you to set the optimum subcontracting range
Identify the SB/SDB subcontracting goals
Express the goals as a % of total contract value, not % of subcontracted amt.
Don’t rely on government specified % goals – use maximum practical % based on your market research and your acquisition
Describe how SB/SDB subcontracting plans will be evaluated
Discuss how you determined this evaluation approach to be appropriate
Subcontracting performance at the business unit sector
Explain how this evaluation will be addressed (Section L and M)
Comprehensive Subcontracting Plan Test Program approved by Congress
Submittals from contractors participating in this program will be evaluated against their corporate commitment (see Notes)
Include performance on subcontracting plan as part of past performance evaluation IAW FAR (a)(2)(v) and DFARS
Comprehensive Subcontracting Plan Test Program—Source Selection
If a contractor is not part of the test program then require the normal submittal of subcontracting plans.
When contractor is part of the Test program only require submittal of information on the contractor’s goal as well as information on its success in meeting its goals.
Evaluate the submittal in the source selection measured against how they are doing against their individual contract plans or how well they are doing against their corporate plan/goal.

45. SB Cont…
Identify planned contract incentives to encourage aggressive S/B subcontracting (except for those contractors involved in the Comprehensive Subcontracting Plan Test Program)
FAR clause , “Incentive Contracting Program”
Award fee
Assess whether contractor achieves goals (e.g..)
Satisfactory: meets goals
Above satisfactory: exceeds goals
Discuss your plan for post-award monitoring, such as
Contracting Officer review of SF 294 reports/DCMA Forms 640
Actions that might be taken if contractor not meeting goals in Plan
Measuring performance and documenting same in Contract Performance Assessment Reports
Consider requiring CDRL for Small Business participation
Consider Liquidated Damages

46. Schedule to Contract Award
MARKET RESEARCH / RFI SYNOPSIS
ACQUISITION STRATEGY PANEL
J&A/ACQUISITION PLAN or LCMP (or ASR) APPROVAL
DRAFT RFP RELEASE
FEDBIZOPS SYNOPSIS OF FORMAL RFP
PRESOLICITATION CONFERENCE (if Comp)
RFP RELEASE
PREPROPOSAL CONFERENCE (if Comp)
PROPOSALS RECEIVED
FACT FINDING/DISCUSSIONS
COMPETITIVE RANGE BRIEF (if Comp)
FINAL PROPOSAL REVISIONS/DISCUSSIONS
CONGRESSIONAL NOTIFICATION
CONTRACT AWARD (see footnote)
DEBRIEFINGS (if Comp/if requested)
There are milestones related to the activities leading to contract award like RFP review, approval for release, source selection period, etc.
Contract Award – Allow adequate time during source selection for a MS decision.

47. Program Office Organization, Experience and Manpower
Provide Organizational Structure (Org Chart)
Resources
Address Critical manpower positions / program office manning & facilities
Program Office Staffing and Support Contractor Resources Available to PM
Identify technical authority/chief engineer
Identify any shortage of personnel
Identify current DAWIA (APDP) certification levels for all key government personnel (SPMs, PMs, etc)
Integrated Product Teams (IPTs)
PMA tenure agreement (on in EMA section)

48. Mandatory Program Org Chart OSD/AT&L ACC/A5XX SAF/AQ Wing CC PEO
User
ACC/A5XX
Col Ron Smith
SAF/AQ
Wing CC
BGen K. Boockholdt
PEO
Lt Gen JP Jones
Depot
OO-ALC/XYZ
Col Al Griggs
Group CC
Col Ayn Curious
SPD/PM
Col John Smith
PM1
Maj D. MacArthur
Contracts
Ms. Jane Smith
Sys Eng
Maj Kelly Johnson
Test
Maj C. Yeager
Use existing program org charts so long as they show from MDA through PM and major IPTs within the program office.
In no case shall there be more than two levels of review between the Program Manager and the Milestone Decision Authority in accordance with DODD , DODI , NSS 03-01, and AFPD 63/ Wing CC and Group CC should not be in the “acquisition chain” but may be shown on the side in an organize/train/equip role.
PM1 IPT
2 Captains
1 GS-12
5 Contractors
Contracts IPT
2 Captains
1 GS-12
5 Contractors
Sys Eng IPT
2 Captains
1 GS-12
5 Contractors
Test IPT
2 Captains
1 GS-12
5 Contractors

49. Program Office Acquisition Certifications
SPD/PM: Col John Smith (Total Acq Exp = XX mos / x mos as PM)
Level III: Program Management
Level II: Test, SPRDE
PM1: Maj D MacArthur
Level II: Program Management
Level I: SPRDE
PCO: Ms. Jane Smith
Level III: Contracting
Level I: Program Management
SPO Personnel
Military: 20
Civilians: 10
Contractors: 20
Critical shortage of Systems Engineering and Test
Mandatory
Identify DAWIA (APDP) Certification of the major personnel below PEO.
Identify number of SPO personnel and any critical shortages.
Break out by Mil/Civ/Contractor, Rank/Grade, and/or Functionality (PM, Sys Eng, Test).

50. Mandatory Program Office Experience Level
Progam Manager: Col John Smith
Total Acq Exp = 280 mos / 24 mos as PM
 # Assigned (Avg Months of Total Acq Experience/Avg Months of Experience on Program)
Govt Engineers
Govt Program Management
Other Govt (Finance, Contracts, Admin, etc.)
Support Contractors
Totals = 350 (92 (wt avg)/13 (wt avg)

51. Manpower ramp up & down
Current and Future Manpower level

52. Additional Acquisition Topics (if not addressed elsewhere)
Clinger Cohen Act Certification progress (CCA)
Envir & Manuft/Quality Engineering
Interoperability
Information Assurance
Information Technology
Research/Technology Protection
Protection of Critical Program Information
Anti-Tamper
Human Systems Integration
Environment, Safety, Occupational Health
Military Flight Operations QA
Spectrum Management/Supportability
Integrated Digital Environment Mgt
Gov’t Furnished Equipment/Property
Modeling and Simulation
Corrosion Control
Insensitive Munitions
Unique Identifiers
Trusted Foundry
What are the Clinger Cohen Act certification issues associated with your program? If the strategy is being developed to release an RFP prior to a milestone, you should still explain the plan for meeting your certification requirements. Teaming early with the AF-CIO precludes surprises and stumbling blocks as your program nears a significant milestone event.
Explain how you have assessed intelligence supportability
Describe the process used and personnel involved in assessing intelligence supportability
Summarize the types of intelligence products and services required to support the program across the life-cycle
Summarize intelligence shortfalls
Summarize cost, schedule and/or performance risk associated with intelligence shortfalls
Describe plan to mitigate intelligence shortfalls
Explain how threat data is being used and managed
Describe threat data sources and application
Describe plan to manage the threat baseline throughout the acquisition life-cycle
Describe plan to ensure testing is accomplished against a realistic threat environment (test to threat baseline, developmental scenario=operational test scenario)
If you expect to have ASIC (application specific integrated circuits) then go to :Trusted Foundry:

53. Status of Documents for MS Review
If you have to go to a MS Review
Show specific steps documents that need to be completed and reviewed and approved at HQs AF and at OSD. (I.e, documents, test events, etc)—
(See Sample section for Matrix examples)
AoA
Capabilities Document
ISP
CARD/ICE—EA w/ ROI
TEMP
CCA compliance/certification
Systems Engineering documents (SEP, TRA, MRA)
Section 801 Certification (ACAT ID &IC programs)
Technology Development Strategy
Section 801 Certification: There are 10 different items the MDA (either the DAE or SAE) will have to certify to comply with Section. Address any issues/difficulties (providing satisfactory proof) for the DAE/SAE in signing the certifications. The 7 are:
`(a) Certification- An MDAP may not receive MS B approval, or Key Decision Point B approval in the case of a space program, until MDA certifies that--
`(1) technology has been demonstrated in a relevant environment;
`(2) the program demonstrates a high likelihood of accomplishing its intended mission;
`(3) the program is affordable when considering the per unit cost and the total acquisition cost in the context of the total resources available during the period covered by the FYDP submitted during the fiscal year in which the certification is made;
`(4) the DoD has completed an AOA with respect to the program;
`(5) the program is affordable when considering the ability of the DoD to accomplish the program's mission using alternative systems;
`(6) the JROCl has accomplished its duties with respect to the program pursuant to section 181(b) of this title, including an analysis of the operational requirements for the program; and
`(7) the program complies with all relevant policies, regulations, and directives of the Department of Defense.
Add other appropriate to the list—should total 10

54. “What Worries Me”
This is an opportunity to communicate internal concerns to the SAE
Discuss any issues that are of a particular concern to the PEO and SPM (examples might be)
OSD Oversight issues
Funding instability
Technical transition issues
Explain how you intend to track these areas specifically and report to the SAE any problems
"What worries me"? The PM/SPD/PEO is encouraged to identify issues that provide the most concern. It is an open opportunity to identify: "what worries me most”. What "keeps me up at night"? These may include oversight issues, funding instability, congressional interest, or other issues such as slow transition of technology. This is an opportunity for the PM/PEO to notify the SAE of potential issues either not addressed previously, or reiterate some of those addressed earlier. Identifying these issues is the first step; but have a plan to address them. Also, identify how the SAE might help. An example might be asking the SAE to break a logjam disagreement with the OSD staff. Another might be a problem getting coordination through another Air Force Directorate (GC, TE, IL etc).

55. Recommendation Approve Acquisition Strategy
Approve applicable delegations
Approve Waivers and Deviations
Way ahead to AFRB/ARB and OSD DAB
Staff reviews/OIPT (PEO reviews)

56. Final Thoughts in Preparing your Briefing

57. Some Items to Consider in Preparing Briefing – Feedback from Other Reviews
Contracts
Incentives
Evenly provide the fee versus being back-loaded
Inadequate to control cost
Did not Focus on highest risk areas
Schedule
Insufficient detail; no critical path identified or briefer does not know
Briefer unable to explain schedule flow and margins for potential slips
Manpower ramp up & down does not match program schedule
SORAP does not align with program schedule…ensure AFMC involved early for sustainment funding
Risk
Failure to adequately identify risk, or address mitigation plan once identified
PMs overly optimistic
Risk Mitigation inadequately addressed just indicating the SPO would work harder
“Working harder” is not a risk mitigation strategy
Funding does not align with requirements or schedule
Need to present a fully funded program
Need to clearly identify costs by increment & map to budget documents
Small slip in contract award from end of FY A to beginning of FY B can mean loss of FY A funding
Be mindful that management reserve not used in the year of execution likely to be taken

58. SAMPLE CHARTS

59. Required Capabilities Requirements Traceability
CDD
Capability
Sys Spec
Testing
KPP 1
Config Item 1
Config Item 2
KPP 2
Net Ready
Materiel Availability
Materiel Reliability KSA
Ownership Costs KSA
Force Protection
Survivability
Training
Energy Efficiency
KSA 1
KSA 2
Separate out the lines by “Program KPPs (including associated KSAs), Mandatory “KPPs” and “non-KPP KSAs”
Sample
Use Multiple slides as required

60. Alternative strategies considered

61. Alternative Acquisition Strategies Considered
SAMPLE
The Challenge—Program Needs
Develop a program plan that…
Meets need date
Migrates to ……architecture
Satisfies the Net Ready KPP
Utilizes existing equipment
Maximizes insulation from other program risks
Manages internal program constraints/dependencies
Other upgrades, computer processors, resources (labs & people)
Best fits in a fiscally constrained environment
Seven Key Items Used to Develop Strategy

62. Fits Fiscal Constraints
Strategy 1
SAMPLE
Strategy 1
Meets Need Date
Does not migrate
Does not fulfill Net Ready KPP
Uses existing equipment
No dependency on other programs
Manages constraints
No additional funding in near years
Maintains
Strategic
Connectivity G
Migrates R
Satisfies Net Ready R
Utilizes
FAB-T R
Insulation from other G
Manage Constraints G
Fits Fiscal Constraints G
RED = No
YELLOW = Partially
GREEN = Yes

63. Fits Fiscal Constraints Insulation from others
Solution Trade Space
SAMPLE
Fits Fiscal Constraints
Manage Constraints
Insulation from others
Utilizes
Equipment
Satisfies Net Ready
Migrates
Maintains
Strategic
Connectivity G R Y
Strategy 1
Strategy 2
Strategy 3
Strategy 4
Strategy 5
RED = No
YELLOW = Partially
GREEN = Yes

64. Fits Fiscal Constraints Insulation from others Alternate EHF terminal
Solution Trade Space
SAMPLE
Fits Fiscal Constraints
Manage Constraints
Insulation from others
Utilizes
equipment
Satisfies Net Ready
Migrates
Maintains
Strategic
Connectivity G R Y
VLF terminal
non-integrated
Alternate EHF terminal
FAB-T
Integrated
FAB-T Integrated

65. Acquisition Strategy Selected
SAMPLE
Bridge Solution
Meets Need Date
Migrates
Fulfills Net Ready KPP
Uses existing equipment
Minimal dependency on other programs
Manages constraints by…
No additional funding in near years
Maintains
Strategic
Connectivity G
Migrates B-2 to EHF G
Satisfies Net Ready G
Utilizes
FAB-T G
Insulation from AEHF Y
Manage B-2 Constraints G
Fits Fiscal Constraints G
RED = No
YELLOW = Partially
GREEN = Yes

66. Documentation Samples

67. E.g.., MS B Document and Actions Status
Sample 1
Est Start
Est Comp Date
Preparing Org
Program Documentation
OPR
Approved By
Date (AF)
AF Status
(AF)
Remarks
Program
Acquisition Decision Memo (ADM)
MDA
Management
Acquisition Program Baseline (APB)
MDA
Acquisition Strategy Panel (ASP)
SAF/AQ
Completed
Acquisition Strategy Report (ASR)
MDA
Expectation Management Agreement
In coordination
(EMA)
Information Assurance Strategy
SAF/XC
Life Cycle Management Plan (LCMP)
Draft in work
Market Research Report
MDA
Milestone B Exit Criteria
MDA
Mission-critical and Mission-essential
This is a sample chart to lay the state of your documentation to provide the decision maker a status. It is important that if there are any major issues that impact your preparing MS documents should be presented early in presentation.
Information Systems Registration
(MCESR)
Statement of Objectives (SOO)
Systems
Engineering
Systems Engineering Plan (SEP)
MDA
In work
Tech Development Strategy (TDS)
Tech Readiness Assessment (TRA)
Security
Program Protection Plan (PPP)
MDA
In work
Security Classification Guide (SCG)
= Prior to Start
= Being Drafted
= In Coord.
= Approved

68. MS C Documents and Actions Statutory
Sample 2
Status
Program Documentation
OPR
Approval Authority
Start
Complete
Actions G
Consideration of Technology Issues
Programmatic Environment, Safety and Health Evaluation (PESHE)
Industrial Capabilities
Independent Cost Estimate & Manpower Estimate
Core Logistics Analysis & SORAP
Technology Development Strategy
MDA
Acquisition Program Baseline
Cooperative Opportunities
Tailorable: Tailor to fit each acquisition program consistent w/ technical risk, design maturity and sound business practices.
Deliberate leadership oversight
Approved On track--no issues
Issues but recoverable Significant issues, jeopardy

69. MS C Documents and Actions Regulatory
Sample 2
Status
Program Documentation
OPR
Approval Authority
Start
Complete
Actions G
Systems Engineering Plan (SEP)
System Threat Assessment Report (STAR)
Information Support Plan (ISP)
MDA
Exit Criteria
Cost Analysis Requirements Document (CARD)
Capabilities Production Document (CPD)
Affordability Assessment
Test and Evaluation Master Plan (TEMP)
Program Protection Plan (PPP)
Acquisition Strategy/LCMP
Operational Test Agency Report
Acquisition Decision Memorandum (ADM)
Technology Readiness Assessment (TRA)
Earned Value Management System (EVMS)
Unique Identification (UID)
Tailorable: Tailor to fit each acquisition program consistent w/ technical risk, design maturity and sound business practices.
Deliberate leadership oversight

70. MS C Documents and Actions Beltway Buttons
Sample 2
Status
Program Documentation
OPR
Approval Authority
Start
Complete
Actions G
Expectations Management Agreement (EMA)
Modular Open Systems Architecture (MOSA)
Tailorable: Tailor to fit each acquisition program consistent w/ technical risk, design maturity and sound business practices.
Deliberate leadership oversight
Approved On track--no issues
Issues but recoverable Significant issues, jeopardy

71. Other Samples

72. SAMPLE Road to Milestone C FY08 FY09 Apr May Jun Jul Aug Sep Oct Nov
Dec
TFN Resolution
TFN Qual Final Report
Critical Path
Qual Test
Complete
Qual Final Report
Technical
Verification Compliance Review (MS 1)
VCR 1 Complete
Readiness
Production Readiness Review
PRR Complete
Safety Pause
MS 1 Flight Test
MS 2 Flight Test
IOT&E
MS 2 Flight Test
OA Report
MS 1 Complete
PEO Cert
Budget,
POE Update
POE Complete
POE, and
SCP
SCP Complete
SCP
FY10 POM
FY10 POM
Input
Update
ABIDES Locks
Proposal and
Fact Finding / Alpha / Negotiations
Clear / Cert
Contract
Proposal Development
Award
ATP
Update
Final Submittal
FFP Decision
FPI Update or FFP Submit
Milestone Documentation
Docs Complete
Milestone C
Pre-Briefs
Activities
MS C Briefing
ADM

73. SAMPLE Program Schedule FY06 FY07 FY08 FY09 FY10 FY11 FY12 FY13
Restructure Approved
Re-plan Approved
Re-plan/Restructure
LDR
IBR
Delta PDR
CDR
1st LDR EDM
Delivery date with margin
Baseline delivery date
LDR Development
Development
ΔSRR
PDR
CDR
XDR
1st XDR EDM
XDR/Command Element Dev
IPR
DAE Review
KDP-C
LDR
Factory/Qual/RGT DT OA
Flt Test
Test
XDR
Factory/Qual
Flt Test
DTOT
LDR
EDMs
LRIP Decision
XDR
EDMs
FRP Decision
Production
EDMs / LRIP/Install / FRP/install
EHF ops 73 73

74. Human System Integration (HSI) & Environment, Safety, and Occupational Health (ESOH) Template *
Sample Chart
Systems Eng. Focus Areas
Compliance/Risk
Rationale/Comments
Manpower **
Personnel **
Training **
Human Factors Engineering**
Habitability**
Survivability**
Environment***
Safety***
Occupational Health***
Use “HSI Issues / Questions Material” to complete matrix from AFRB/ASP website or ed from SAF/ACE AFRB/ASP Secretariat ( / 5662)
Template & backup material provided by AF/SGR ( )
Address red areas in main brief and have yellow areas in back-up
Legend:
* SAF/AQ Interest Item
** Use AF/SGR HSI Assessment Material
*** Use MIL-STD-882D
As Of: 30 Aug 06

75. SAMPLE Probability of Program Success Summary PEO: PM: PM’s Name
LEGENDS
Colors:
G: On Track, No/Minor Issues
Y: On Track, Significant Issues
R: Off Track, Major Issues
Gray/Hashed: Not Related/Not Applicable
Asterisk carried on metric to indicate rebaselined
Trends:
Up Arrow: Situation Improving
(number): Risk Score
(based on 100 possible)
Down Arrow: Situation Deteriorating
Probability of Program Success Summary
PEO:
PM: PM’s Name
Program Planning
Date of Review: Date
Rebaselines: (X)
Last Rebaseline: DATE
Program Life Cycle Phase: XXXXXXX
Warfighter (1 or 1.5)
Congress (0.5)
OSD (0.5)
Joint Staff (0.5)
HQ Air Force (0.5)
Industry (0.5)
International (0.5 or 0)
Air Force Vision (0.5)
DoD Vision (0.5)
Acquisition (10)
Program Risk
Assessment (13)
Sustainability Risk
Assessment (2)
Testing Risk (2)
Technical Maturity (13))
Budget (20)
Manning (5)
Industry
Resources (5)
Program Parameter
Status (15)
Program Scope
Evolution (10)
Program “Fit”
Capability Vision (xx/1)
Program
Advocacy (xx/4)
Planning (xx/40)
Resources (xx/30)
Requirements (xx/25)
Program Name ACAT XX
Software (Not used for
Pre-Ms B Evaluations)
Contractor/Developer
Performance )
Fixed Price
Performance
SAMPLE