Rank, Name Office Symbol Date of Briefing Version

slide1. Rank, Name
Office Symbol
Date of Briefing
Version #
Updated: April 18 This template is for guidance
and is not mandatory. If tailoring, please ensure to include statutory items at minimum. Acquisition Strategy Panel (ASP) Template Please refer to the notes section for valuable guidance 1 This document includes AFLCMC/AQ-AZ and Digital Campaign recommended additional guidance for ASP preparation. Last Updated Feb 2021.<br>
slide2. Outline Bottom Line Up Front (BLUF)
Program Structure
Program Schedule
Factors shaping strategy
Capability Needs
Affordability
Program Cost Est./Funding
Program Risks
Technology Transition
Acquisition Strategy
Framing Assumptions
Proposed Acquisition Strategy
Business Considerations
Business Strategy Contract Considerations
Competition Strategy/Market Research
Contract Parameters
Data Rights
Small Business
System Engineering
Digital Engineering/MBSE
Cybersecurity
Product Support Strategy
Test and Evaluation
What Worries me
Recommendations HQ AF ASPs will be scheduled for 1 ½ hour
Program office goal should be to present no more than ~30-35 charts 2<br>
slide3. “Bottom Line Up Front (BLUF)” (Decisions Requested & Key program information) Decisions you are requesting
Approve Acquisition Strategy (see notes)
Approve Applicable delegations/waivers (e.g., Source Selection Authority)
Major Issues
List “show stoppers”
What are your concerns?
Losing Funding Don’t wait to the end to bring up the negatives! 3<br>
slide4. Decision Authority Strategy
Competitive or sole source
Incremental
Contract Type –
Estimated Contract Award –
Schedule MS A –
MS B –
IOC – Program X Structure
(“Strategy on a page”) Financial Data
Est. Contract Value (Pre-EMD) -
Est. Total Program (qty) - $
Fund Type (Pre-EMD) – e.g.., 3600
New Start (Congressional) – Requirements/Direction
Using Organization(s) -
Capabilities Document – ICD, CDD, CPD
Joint requirement
FMS
Technical Risk
ADM 4<br>
slide5. Program X Schedule MS C Development MS B FY: PRODUCTION EMD IOC
(6/6) CT&E FRP DT&E IOT&E LRIP # of items # of Items FRP 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 ICD CDD CPD Capabilities
Documents 2026 Tech
Demo Milestones: Concept
Decision MS A CDR RFP Rel DSOR Logistics PDR IBR ED Guidance Depot
Activation Major Contract
Events CA Development RFP
Review Time Now Identify Critical Path SAMPLE 5<br>
slide6. Schedule to Contract Award MARKET RESEARCH / RFI SYNOPSIS DATES
ACQUISITION STRATEGY PANEL
J&A/ACQUISITION PLAN or LCMP (or ASR) APPROVAL
DRAFT RFP RELEASE
FEDBIZOPS [or other system used] SYNOPSIS OF FORMAL RFP
PRESOLICITATION CONFERENCE (if Competitive)
PEER REVIEW
RFP RELEASE
PREPROPOSAL CONFERENCE (if Comp)
PROPOSALS RECEIVED
FACT FINDING/DISCUSSIONS
COMPETITIVE RANGE BRIEF (if Competitive)
FINAL PROPOSAL REVISIONS/DISCUSSIONS
MILESTONES
CONGRESSIONAL NOTIFICATION
CONTRACT AWARD
DEBRIEFINGS (if Competitive and requested) 6 See Notes Page<br>
slide7. Factors Shaping Strategy Capability Needs Discuss the capability required (AS Template Para 2)
Effect of Capability and gap it will mitigate
CONOPS, OV-1
Key Performance Parameters (KPPs) and Key System Attribute (KSAs)
Discuss Reliability, Maintainability, Availability, and Supportability requirements
Acquisition Approach (Evolutionary) as it relates to meeting need
Address length of the Increments (see footnotes on length)
Discuss what collaboration has been accomplished in developing these capabilities.
How has industry been involved? How have they influenced requirements?
Identify requirements Industry has indicated they can’t meet either in the capability document or the affordability goal See Notes Page 7<br>
slide8. Factors Shaping Strategy  Affordability Requirement Discuss your affordability goals (AS Template Para 8.2.1)
Do you have enough information to develop an affordability goal?
Using both the average unit acquisition cost and average annual operating and support cost per unit what will you be able to present at MS A/B?
Discuss strategy for achieving this “KPP” like topic
Identify specific contract provisions (e.g., goals and Incentives in RFP)
Identify changes to quantities that are necessary to achieve target
Identify schedule changes necessary to achieve goal
Identify the Digital Acquisition (both business & technical) strategy being used to optimize total system performance & total ownership cost
Impact of procurement rate (EOQ) and schedule on the affordability goal
What is the source of the Affordability Requirement? 8<br>
slide9. Factors Shaping StrategyProgram Cost Estimate/Funding Identify your cost estimate and methodology (AS Template Para 8)
Identify the Confidence level (55-80%)*
Include LCC estimate (product support %)
Identify if it is a Program Office Estimate/Service Cost Position
Address any AFCAA/OSD CAPE 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
Provide an overall funding chart (see next chart) Proffer a fully funded Acquisition Strategy See Notes Page 9<br>
slide10. MANDATORY SLIDE 10<br>
slide11. SEE NOTES PAGE
and BACKUP SLIDES Program Risks (AS Template Para 6) SAMPLE 11<br>
slide12. Technology Readiness (AS Template Para 6.3) See Notes Page SAMPLE 12<br>
slide13. Expectations Implications Framing Assumption Purpose-built will be competitive with existing designs Basic aircraft and training system designs will be complete through vendor-conducted CDRs Enter at MS B Limited EMD of “deltas” to meet spec PDR and competitive prototype waivers applicable Best-value source selection must consider risk Contractor flight data to validate performance Single step to full capability Single award for EMD, Prod and ICS RAA in 2023
FOC in 2031 See Notes Page for more examples of framing assumptions Acquisition Strategy Framing Assumptions #1 SAMPLE 13<br>
slide14. Expectations Implications Framing Assumption APT
requirements only Mature technologies and systems available Single step, limited EMD, waivers etc. AETC sole customer Separate PPBE
process for
other T-38 owners Separate Planning Programming Budgeting and Execution (PPBE) process for APT derivative use capabilities IOC 2023 Acquisition Strategy Framing Assumptions #2 SAMPLE 14<br>
slide15. Acquisition Strategy Framing Assumptions See Notes Page ALTERNATE SAMPLE 15<br>
slide16. Proposed 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. (AS Template Para 3)
If evolutionary acquisition approach, summarize the cost, schedule, and performance drivers for the increment under consideration, and the plan to transition from the initial increment to later increments.
Specify any unique program circumstances
Are you replacing an existing system (modification or new capability)
New Start
Is this a joint program?
Identify Service(s)/DoD Components; Service-specific technical and operational differences; roles and responsibilities; and program funding
If MS B or C total planned production and LRIP quantities. If LRIP quantity exceeds 10% provide justification.
Address and regulatory tailoring necessary for program efficiency SEE BACK UP for sample charts on alternatives considered and rationale
for the strategy selected 16<br>
slide17. Discuss the program’s business strategy for the contractor/government ownership of the architecture, labs and knowledge-based tools
E.g. Own the Technical Baseline (OTB), and/or Modeling Strategy objectives:
Government Organic & Controlled / Model Centric
Hybrid Government & Contractor Collaborative / Model Collaborative
Government Influenced & Contractor Supported / Model Supported
Discuss the contractor/government collaboration approach over the program lifecycle for knowledge sharing concepts including
Digital Ecosystem / Integrated Digital Environment (IDE)
Product Lifecycle Management (PLM)
Authoritative Source of Truth (ASOT)
Discuss the Digital Engineering & Management and Open Systems business strategies being utilized by the program
Discuss the software development approach (Agile, DevSecOps, DevStarOps, etc) and how it supports the acquisition strategy Business Strategy 17 See Notes Page<br>
slide18. Competition Strategy/Market Research Competition Strategy (AS Template Para 7.1)
Explain how a competitive environment will be sought, promoted, and sustained throughout all program phases.
Summarize the competition strategy for the upcoming phase
Where head-to-head competition is not possible, explain how dissimilar competition or other competitive approaches will be used
Include Digital Acquisition in Competition Strategy (Digital fly-offs, Simulations, etc.)
Market Research (AS Template Para 7.2)
Summarize research conducted and results. Indicate the specific impact of those results on the various elements of the program.
Plans for continuing market research to support the program throughout development and production.
Plans for getting industry insights on potential requirements and cost trade space to support AF’s cost capability analysis
Sole Source Authority(AS Template Para 7.5..1.5)
Identify legal authority and basis
Planned Action to obtain future competition (e.g., buying tech data package & associated intellectual property rights 18<br>
slide19. Competition Strategy/Market ResearchSource Selection Approach List the known sources (AS Template Para 7.5.5)
Source Selection Procedures/Organization (AS Template Para 7.5.4)
Address the Source Selection experience of the team (see notes)
Best Value approach (e.g., Trade-off/Lowest Price Technically Acceptable)
Only use LPTA when able to clearly define Technical Acceptability
Evaluation Criteria with Weighting
Tied to Risks and Significant Discriminators
Evaluation Criteria—Section L&M criteria
Factor/subfactor weightings
Identify the criteria that will be used to select the winning bidder. Indicate how those criteria reflect the key government goals for the program.
How will data and data rights acquisition be evaluated
Be prepared to Discuss in detail
Will the program’s Digital Acquisition objectives over the life cycle be leveraged in source selection?
Discuss the robustness of the Gov’t Digital Reference Library & bidders library based on program’s Digital Strategy See notes section for OSD guidance 19<br>
slide20. Contract Parameters Contract Type (AS Template Para 7.5)
Need to discuss the rationale for your contract type
What measures are in place to control contract costs?
Describe type & number of contracts expected & why you chose that approach—will this reduce program risk?
Have you considered breakout of subsystems?
Contract Structure (Length, Options, CLINs)
Special Terms and Conditions
E.g., Organizational Conflict of Interest (OCI), Pricing Matrix, Warranty of Data (DFARS 252.246-7001), warranties, Advance procurement
If an Undefinitized Contract Action (UCA) is planned discuss rationale and what led to this situation as well as get well plan
Subcontractor Management
Make or Buy considerations
Discuss usage of model-based contract language based on programs Digital Strategy/Modeling Objectives 20<br>
slide21. Contract Parameters& Incentives Discuss planned Incentives (AS Template Para 7.5.2)
What are the key program risks and how can incentives help to mitigate risks and improve probability of success?
What Objective Incentives were considered and why?
Award Fee
How is award fees linked to the acquisition outcomes—cost, schedule and performance?
How is award fee tied to specific challenges, commitments & delivered capability versus just “effort”
Are there negative incentives for overrun or poor performance?
If more than one incentive is planned explain how the incentives complement each other and do not conflict.
Why will the incentive motivate the contractor?
What incentives do the contractors intrinsically have and/or what incentives is the government providing to meet program office Digital Acquisition objectives? 21<br>
slide22. Intellectual Property (IP) Strategy What do you need? (AS Template Para 7.6)
What technical data rights & deliverables will be needed throughout the system’s life cycle?
What is needed to support the sustainment plan (OEM maintained or organically sustained)?
How is a Modular Open Systems Architecture (MOSA) business strategy being used in harmony with the IP Strategy to ensure competition at both prime & subcontract level throughout life-cycle (including system/subsystem upgrades & maintenance (CLS/ Depot)?
How does your Government Reference Architecture (GRA) and open standards impact IP needs?
Who is paying for development (govt or contractor) and what rights have been previously procured?
How will you buy it?
Discuss strategy for technical data/software data rights procurement, data access & data delivery.
For a competitive procurement, describe evaluation factors that will be used to assess the price and adequacy of the technical data during source selection. Discuss use of options for delivery of technical data and obtaining additional rights in the technical data.
Assess merits of including a priced contract option for future (or deferred) delivery of technical data and intellectual property rights. (See DOD 5010.12-M Chapter 5 for pricing data.)
Discuss strategy for acquiring software (source code, documentation, and development artifacts)
 How will you manage it?
What approach will be used to ensure delivery and adequacy of data?
How will program office verify contractor’s assertion of restricted use & release of data?
What considerations are being made for digital product design data requirements?
What is the Product Lifecycle Management (PLM) strategy/process to ensure Data Rights are managed & protected when required? See Notes Page 22<br>
slide23. Small Business What does your Industrial Base Survey indicate is the small business (SB) Capability? (AS Template Para 7.5.7)
Identify NAICS ($’s or employee size standard) and Product Service Code (PSC) used based on market intelligence
Is this acquisition appropriate for a SB set -aside?
If so, what are your recommendations? Breakout opportunities?
Are there any bundling or consolidation decisions?
If no prime opportunities, describe your plan for SB participation
Identify planned contract incentives to encourage aggressive SB subcontracting
Identify percentage requirements for SB subcontracting
How will small business be evaluated in source selection?
Discuss your plan for post award monitoring 23<br>
slide24. Systems Engineering (SE) Outline the open systems architecture approach, combined with the Product Support and IP strategy, which the government will pursue in order to ensure a lifetime consideration of competition (AS Template various)
Address the program’s Government Reference Architecture (GRA) with open key interfaces & open/common standards identified for your domain of operation for systems & subsystems (including software & hardware)
Systems Engineering Tradeoff analysis
Show your approach to determining how cost varies as the major design parameters and time to complete are traded off against each other
Discuss key requirements impacting Acquisition Strategy
Discuss requirements maturity and stability
Discuss how the SysML-compliant Government Reference Architecture (GRA) is being used & leveraged for requirements traceability and maturity
Address how GRA model (or leverage/modify existing GRA models) supports implementing the program Digital Eng/Mgmt & Open Architecture objectives
Discuss how Reliability, Maintainability and Availability are addressed in the SRD (AS Template Para 7.5.10) 24<br>
slide25. Systems Engineering (Continued) 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?
Plans for addressing manufacturability and maturity
Describe key SE components of the RFP and contract
Identify SE RFP requirements and selection criteria (or address in source selection part of brief)
Identify SE contractual provisions to ensure contractor implements proposed approach
Address Digital Acquisition/Engineering requirements that will be implemented
Address Digital model artifacts/analysis and any Digital Thread / Digital Twin requirements traceability for manufacturing
Is a configuration management plan required and, if so has one been developed?
Have defense exportability features been considered in the initial designs (AS Template Para 10.3) 25<br>
slide26. Digital Engineering/MBSE Strategy Define how the DE/MBSE strategy was derived-from and maps-to the business strategy
Define the expected benefits of DE/MBSE and its injection points in the acquisition schedule
Define the acquisition
Modeling objectives
Model-based Capabilities Assessment results to ensure the government team is ready for modeling and contractor modeling results
Model element and data needs that are necessary to meet the modeling objectives and result in RFP/model contract data requirements
Modeling plan as part of the SEP, TEMP, LCMP, etc
Define the software strategy
Address your Agile Software DevSecOps and/or Dev*Ops strategy. Tailor your program objectives/requirements for “baked” in security (DevSecOps) methods to enforce cybersecurity, and where applicable additional “baked” in factors like safety and certification requirements (Dev*Ops where the “*” represents the additional factors) 26<br>
slide27. Cybersecurity & Resiliency Acquisition Strategy Panel Chart 27<br>
slide28. Product Support Strategy Metrics Data * Test or fielding event data derived from _______ Notes: Sustainment Schedule O&S Data MS B MS C IOC FRP FOC Sustainment BCA LCSP CLS Start Depot Standup LRIP Contract Award Blended Partnership Startup PBL Recompete Avionics PBL PBL Recompete Sustainment Approach
Current (initial CLS covering total system)
Future (sub-system based PBL contracts)
Issues
Shortfall in O&M funding in FYDP
Reliability and availability estimates are below goals
LCSP requires update before DAB
Resolution
POM request for O&M restoration submitted
Reliability improvement plan with clear RAM goals up for final signature
LCSP in draft BCA BCA BCA Cost based on average annual cost per squadron Today See Notes Page (AS Template Para 7.4) MANDATORY SLIDE 28 Product Support<br>
slide29. Product Support StrategyDigital Engineering Summarize the product support strategy for meeting sustainment requirements necessary to satisfy the model-based acquisition strategy requirements (Technical Data Strategy/Intellectual Property Strategy)
Address the approach to managing the data & IP during acquisition & sustainment (e.g., access, method of delivery, format, and storage) and how it complies with the AF Data Strategy for Visible, Authoritative, Understandable, Linked & Trusted (VAULT) Data.
Define the program's approach to managing the data during both acquisition and sustainment (e.g., access, method of delivery, format, and storage) within a model-based environment
Address implementation of Product Lifecycle Mgmt (PLM) and other Logistic Capability initiatives for Technical & Logistics baseline data to plan, buy, and fix the right stuff. Include leveraging the Integrated Logistic Data Model/Logistic Reference Architecture to connect Integrated Product Support (IPS) elements to the GRA to ensure design driven sustainment planning, include coverage of IPS elements for the program’s Authoritative Source of Truth (ASOT) to establish/maintain the Digital Thread and validated Digital Twin(s) to support sustainment for the programs life cycle.
Operations & Sustainment Data
Consideration for network compatibility issues and mitigation steps for operating in the model-based environment
Document logistics data enterprise architecture generated which identifies electronic data repositories, information exchange requirements, and/or usage
Identification of preliminary engineering/products support data needed
Considerations for process by which Tech Orders (TOs) will transfer from Acquisition to Sustainment 29<br>
slide30. Test and Evaluation (T&E) Summarize the T&E Strategy; how does it support the acquisition strategy, and provide info for major decision points
Identify LDTO, OTO, major test facilities to be used. Is ITT formed/active?
Is the program on OSD Test oversight? (DOT&E and/or DD,DT&E)
Is test strategy fully developed & synced w/ contract?
Identify any risks or issues regarding availability of test articles, test facilities or support assets, test personnel, etc.
Describe any capability shortfalls of the test ranges to support.
Does program plan have adequate schedule, budget, & resources for T&E?
Describe how T&E strategy supports “Digital Acquisition”
How are models/MBSE used for test planning, predicting test results, and complementing physical testing? Any Gov’t-provided reference models?
What digital access do testers require to contractor models & data?
How will a program Integrated Digital Environment be used by test team? How is test data shared between stakeholders? See notes as limited room on this slide. Overflow goes to backup unless MDA decision is needed on test strategy. 30<br>
slide31. “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 PM (examples might be)
OSD Oversight issues
Funding instability
Technical transition issues
Congressional Interest
Requirements stability 31<br>
slide32. Recommendation Approve Acquisition Strategy Concept
Allow program to draft Acquisition Strategy
Approve applicable delegations
Approve waivers and deviations
Way ahead to AFRB and OSD DAB
Staff reviews/OIPT (PEO reviews) 32<br>
slide33. Back-Up See Footnotes for additional information 33<br>
slide34. Back-ups Program Office
Industrial Base Capability and International Cooperation
Software Development
Risk
Additional Acquisition Topics
Samples
Affordability
Should Cost
Source Selection
Acquisition Strategy
Lessons Learned/FAR Part 2 34<br>
slide35. Program OfficeOrganization, Experience and Manpower Provide Organizational Structure (Org Chart) (AS Template Para 9.1)
Resources
Address Critical manpower positions / program office manning & facilities
Program Office Staffing & Support Contractor Resources Available to PM
Identify Deputy PM, chief program engineer, lead program system engineer, lead cost analyst, product support manager and engineering data management officer (EDMO), contracting officer, financial manager, T&E
Identify any shortage of personnel
Identify current DAWIA (APDP) certification levels for all key government personnel (SPMs, PMs, etc)
Address the technical level of the team and the alignment w/ the program’s Own the Tech Baseline & Model Strategy/Objectives (Govt Controlled, Gov/Ktr Hybrid, Ktr controlled)?
Define your Digital Acquisition resources and IT needs
Integrated Product Teams (IPTs)
PMA tenure agreement 35<br>
slide36. Program Org Chart OSD/AT&L SAF/AQ PEO
Lt Gen JP Jones PM
Col John Smith Program
Control
Maj D. MacArthur Contracts
Ms. Jane Smith Sys Eng
Maj Kelly Johnson Test
Maj C. Yeager Test IPT
2 Captains
1 GS-12
5 Contractors PC IPT
2 Captains
1 GS-12
5 Contractors Contracts IPT
2 Captains
1 GS-12 Sys Eng IPT
2 Captains
1 GS-12
5 Contractors ACC/A5XX
Col B Martin OO-ALC/XYZ
Col Al Griggs User Depot PSM
Lt. Col T. Jones Support IPT
1 Captain
1 GS-12
4 Contractors SAMPLE 36 Does the technical level of the team align with the program’s Own the Tech Baseline & Model Strategy (Govt Controlled, Gov/Ktr Hybrid, Ktr controlled)?<br>
slide37. Industrial Base Capability and International Cooperation 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 a program. 
Address 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)
Do you have sufficient data and data rights for DMS?
International Cooperation/Foreign Military Sales
Defense Exportability considered in the design of the system? See Notes section to address these topics 37<br>
slide38. Software Development Address the DevSecOps (or DevStarOps) maturity growth over lifecycle
Address the program implementation of the DevSecOps Design Pillars
Show DevSecOps pipeline and discuss how key elements of software development are being met
Modern SW dev practices, human centered design, active & committed user engagement, enterprise services/platforms, rapid & interative releases, gov’t/industry software teams, automated tools 38 DoD Enterprise DevSecOps Reference Design<br>
slide39. Additional Acquisition Topics(if not addressed elsewhere) Program Protection Planning
Anti-Tamper
Protection of Critical Program Information
Information Assurance
Trusted Foundry
Clinger Cohen Act Certification progress (CCA)
Environmental & Manufacturing/Quality Engineering
Interdependencies/Interoperability
Information Technology
Human Systems Integration
Environment, Safety, Occupational Health
Spectrum Management/Supportability
Integrated Digital Environment Management (may address in the data rights section)
Government Furnished Equipment/Property
Modeling and Simulation
Corrosion Control
Intelligence Mission Data (IMD)
General Equipment Valuation (MS C)
Multi-year procurement 39<br>
slide40. All High and Moderate Risks should be identified. Recommend Program Office prepare a Risk Mitigation chart and provide in back-up Risk Mitigation SAMPLE 40<br>
slide41. Planned
FY16-FY18: $70.292M; EMD Phase 2 (Contract Award) Source Selection Savings
FY 17: $24.500M; Flight Body-2
FY18: $26.000M; EMD Phase 2 Test Activities Realized
FY13: $ 1.400M; EMD Phase 1 Aircraft Integration
FY13: $11.000M; EMD Phase 1 Test Activities Should Cost Summary Ensure all Should Cost Initiatives are PEO-Approved in CCaRS and values are consistent. Use Back-up slides to elaborate on each initiative. See Notes Page 41<br>
slide42. Top Risks Mitigation OPS Architecture Robust Systems Engineering System Performance Section M Section L System Engineering Integrated Process Architecture Specialty Engineering Program Monitoring Management Fielding study Operator Terminal Control System Data Management AEHF Launch ACTS Availability Software Development DMSMS Ops Terminal
Control Functions SCA Compliance Software Engineering Source Selection
Evaluation Criteria Selection SAMPLE 42<br>
slide43. Source Selection Identify criteria weighting SAMPLE 43<br>
slide44. Basis for Selecting Proposed Strategy The Challenge—Program Needs
Strategy…
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 44 SAMPLE<br>
slide45. Solution Trade Space RED = No YELLOW = Partially GREEN = Yes 45 SAMPLE<br>
slide46. Some Items to Consider in Preparing Briefing – Feedback from Other Reviews Incentives
Did not Focus on highest risk areas
Could not explain rationale for share ratios and ceiling
Inadequate to control cost
Schedule
Briefer unable to explain schedule flow and margins for potential slips
SORAP did 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
Source selection criteria did not relate to program technical risks
Source selection factor weightings were out of sync with program priorities
Funding
Did 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 FYB can mean loss of FYA funding
Be mindful that management reserve not used in the year of execution likely taken 46<br>
slide47. FAR Part 2What constitutes Source Selection information “Source selection information” means any of the following information that is prepared for use by an agency for the purpose of evaluating a bid or proposal to enter into an agency procurement contract, if that information has not been previously made available to the public or disclosed publicly:
(1) Bid prices submitted in response to an agency invitation for bids, or lists of those bid prices before bid opening.
(2) Proposed costs or prices submitted in response to an agency solicitation, or lists of those proposed costs or prices.
(3) Source selection plans.
(4) Technical evaluation plans.
(5) Technical evaluations or proposals.
(6) Cost or price evaluations of proposals.
(7) Competitive range determinations that identify proposals that have a reasonable chance of being selected for award of a contract.
(8) Rankings of bids, proposals, or competitors.
(9) Reports and evaluations of source selection panels, boards, or advisory councils.
(10) Other information marked as “Source Selection Information – See FAR 2.101 and 3.104” based on a case-by-case determination by the head of the agency or the contracting officer, that its disclosure would jeopardize the integrity or successful completion of the Federal agency procurement to which the information relates. For Information Purposes Only 47<br>
slide48. Cost Driver /
Operational Requirements Trade space See Notes Page 48<br>
slide49. Useful Links to Digital References 49 Link to AF Digital Guide: https://usaf.dps.mil/teams/afmcde<br>