HQ AIR FORCE MATERIAL COMMAND

AFMC Acquisition Strategy Process Guide

For

Acquisition Strategy Panel (ASP)

Published and maintained by the Air Force Materiel Command Product Center and Air Logistics Center Acquisition Centers of Excellence (ACE).

Process Owner: Product Center and Air Logistics Center ACEs

Date: 27 Jan 2011

1 Record of Changes.

Minor changes are annotated by changing the second digit, i.e., the first minor change after the basic document would be recorded as “1.1”.

Major changes are annotated by changing the first digit, i.e., the first major change after release of the basic document would be numbered as “2.0”.

Record of Changes Version Effective Date Summary 1.0 11 June 10 Basic document 1.1 6 July 10 Typo Corrections (2) 2.0 Jan 2011 Updated to reflect comments resulting from a review of the document by WR-ALC, OC- ALC, and OO-ALC. With the incorporation of the ALC comments the document title was renamed

2 Acquisition Strategy Panel Process

1.0 Process Definition

The Acquisition Strategy Panel (ASP) process is both an acquisition strategy development and approval process for both USAF and Foreign Military Sales (FMS) efforts. Ultimately, the ASP process helps acquisitions proceed to contract award to deliver systems, equipment or services that meet user needs within realistic cost and schedule parameters. See AFFARS 5307.104-90 Acquisition Strategy Panels (ASPs).

2.0 Purpose and Scope

The purpose of this process guide is to educate program managers and acquisition community stakeholders on the ASP process. The Air Force requires an ASP, unless waived by the ASP chairperson, for all ACAT programs, AFPEO/CM (services) acquisitions, and “Other Contracting” acquisitions requiring a written acquisition plan [AFFARS 5307.104-90(a)(1-3)]. Acquisition strategy planning and approval is required prior to formal solicitation release (See DoDI 5000.02, FAR Part 7, DFARS 207.1, AFFARS part 5307, and AFMC Mandatory Procedure (MP) 5307).

This process guide is to be applied across all three product centers (ASC/ESC/AAC) and Air Logistics Centers (OC, OO, WR) and includes ASPs chaired at all levels. Centers may supplement this guide with local implementation procedures. (Enclosure A is reserved for this use.)

3.0 Process Description

The ASP meeting is the culmination of the process to develop the acquisition strategy, which begins with the identification of the requirement and concludes with the approved acquisition strategy.

In this process, a series of deliberative meetings are held to evaluate proposed acquisition strategies addressing all technical, business, management, and other significant considerations (AFI 63-101). The final strategy recommendation is presented for Chair approval at the formal ASP (AFFARS 5307). The ASP Chair, with guidance from a standing cadre of senior advisors (standing ASP panel), approves the acquisition strategy. The PM is responsible for the ASP outputs, including the final ASP briefing charts and the official meeting minutes (approved by the ASP chair) to include action items.

3 The Acquisition Strategy Development process is notionally accomplished through the series of events depicted in the following Enclosure B process flowchart. An executive summary of this process is provided in Enclosure C.

3.1 Initial Acquisition Strategy Meeting with Acquisition Center of Excellence (ACE) office

A Program Manager (PM) typically begins the acquisition strategy process with approved requirements and appropriate authority. The strategy is initially developed within the IPT, considering the program office funding estimate, potential sources, level of technology maturity, level of manufacturing maturity, etc. The program manager then contacts the center ACE for assistance. The center ACE offers training on strategy development and the ASP process. The ACE facilitates the program team in developing a proposed strategy (with alternatives, if appropriate), and in identifying the ASP chair and potential delegations. The ACE provides the appropriate ASP template. Formal and informal meetings (such as risk assessment workshops, Early Strategy and Issue Session (ESIS), Quick PASS, Multi-functional Independent Review Team (MIRT), etc.) precede the ASP and help in development of a well thought out strategy. The ACE ASP secretariat (see 3.2.4.2) facilitates ASP planning and scheduling.

3.2 Pre-Meetings to the ASP

The development and refinement of a viable acquisition strategy is a necessary step to a successful program. With leadership direction, the PM should consider conducting pre- meetings to the ASP. The purpose of these pre-meetings is to bring in various acquisition experts for informal sessions to brainstorm and build an acquisition strategy in preparation for an ASP. These activities are intended to allow the various experts to provide the PM with increasingly focused advice and lessons learned over time. These are informal meetings dedicated to the resolution of major problems prior to holding a formal ASP. The center-level ASP panel members or Organizational Senior Functionals (OSFs) may attend, depending on the type of meeting. Check with the local ACE ASP Secretariat for guidance.

3.2.1 Early Senior Level “Heading Check”, OSD Required Peer Reviews, or Center-Specific Briefings (e.g., ESIS, Sufficiency Reviews, and ESC Quick Preliminary Acquisition Strategy Session (PASS))

An important early action in developing an effective strategy is to get “senior leader” guidance, inputs and buy-in well ahead of the ASP. These early meetings may be mandatory or optional, depending on the program and magnitude of significant issues or as specified by center. Examples of issues include: sole source vs. competition, requirements concerns, technology maturity, alternative technologies, funding disconnects etc. Some of these early meetings have specific requirements such as the OSD Peer Review, required prior to ASPs for acquisition efforts over $1B. Refer to the local ACE ASP Secretariat for guidance.

3.2.2 Pre-ASP Multi-Functional Independent Review Team (MIRT) Review (AFFARS 5301.90)

4 MIRTs are used to provide independent, objective and periodic reviews in acquisition processes (generally not applicable to sole source acquisitions under $1B, or competitions under $50M) to enhance the AFFARS 5301.90 Clearance Process. The Pre-ASP MIRT meeting helps ensure the right acquisition strategy and business approaches are used. MIRT composition includes senior subject matter experts from legal, contracting and PM communities augmented by other functional subject matter experts (e.g., engineers, financial managers, test managers and logisticians) as required by the Clearance Approval Authority (CAA). The guidance and recommendations of this Pre-ASP MIRT meeting are used in the development of the program acquisition strategy and ASP briefing.

3.2.3 Pre-ASP Meetings

Depending upon the type of program (e.g., ACAT level), the next event is typically the Pre-ASP, which is conducted within a couple of months prior to the ASP and uses the ASP template. The program’s briefing charts are presented and discussions held which may lead to action items to resolve prior to the ASP. The goal is to provide the decision maker with the acquisition strategy, key program issues and a recommendation. Below are the major categories of the supply and services templates.

Supply ASP templates major topics include:  Program overview/Description  Capabilities/Key Performance Parameters/Key Acquisition Objective

 Funding/Program Office Estimate  Risk Assessment  Technology Readiness/Transition  Industrial Base Considerations  Acquisition Strategy  Program Schedule  Systems Engineering  Test and Evaluation  Product Support (Life Cycle Management)  Market Research  Business/Contract Strategy  Manpower/Personnel  Other topics as required (refer to template provided by center ACE)

Service ASP template major topics include:  Program Structure  Market Intelligence  Requirements Development and Management  Risk Management  Acquisition Planning  Solicitation and Contract Award

5  Contract Tracking and Oversight  Performance Evaluation

Other Contracting major topics may include:  Acquisition Background  Funding  Delivery or Performance Period  Risks  Market Research  Acquisition Approach  Competition  Contracting Considerations or Incentives  Government Furnished Property/Information  Surveillance  Milestones  Other Considerations

The AFPEO/DAO will conduct a pre-ASP when Milestone Decision Authority (MDA) is either at the AF or DoD level. The center-level ASP panel is invited to AFPEO/DAO-led meetings. When the AFPEO/DAO is the ASP Chair, a Pre-ASP should be held at the next lower level (ex: Directorate Deputy Director). The Pre-ASP chair will approve the PM to move forward with the briefing to the appropriate level (up to the AFPEO/DAO/Director, SAF/AQ or AFPEO/CM as applicable). During the meeting, it is recommended that the program office take minutes to document key issues raised as well as action items. The PM is responsible to ensure all action items are completed and closed.

3.2.4 Participants - Pre-ASP and ASP

Participants to the Pre-ASP and ASP include the Chair, program office representatives, center-level ASP members (or panel subset), and stakeholders such as AFPEOs with interdependent programs, OSFs, user(s), Air Logistics Centers (ALC), Laboratory acquisition/technical professionals, other involved centers, consultants, higher headquarters (HHQ) as applicable, etc. Attendance of the panel at Pre-ASPs helps to resolve issues at the lower-level rather than at the ASP. Center level ASP member participation for Pre-ASP activities at the Air Logistics Centers will be on a case-by-case basis.

3.2.4.1 ASP Panel

ASP panels are used within the Product Centers, Air Logistics Centers (ALCs), SAF/AQ, and AFPEO/CM. Within each Product Center and ALC, there may be local variations in the use of the center-level panel. The AFPEO/DAO typically uses a standing center-level panel for all ACAT programs and related service/supply ASPs. This ASP panel has the ability to delegate within their respective functional areas/organization. The ASP panel is formed to provide consistent counsel on the acquisition strategy. It assists teams in formulating effective program

6 acquisition strategies and instills consistency across center programs by sharing knowledge, best practices and lessons learned. Scheduling early involvement of the panel members and their staff can be critical to the success of the program.

The Service Acquisition Executive (SAE)-level ASP panel is identified on the SAF/AQ PM&AE website. The SAE-level panel is comprised of general officers (GO) and Senior Executive Service (SES) members for ACAT I programs, non-delegated ACAT II, and special designated programs reviewed at the Headquarters level.

A staff of senior level advisors is also used by AFPEO/CM for counsel (services programs).

3.2.4.1.1 Center-Level Standing ASP Panel Membership

Center-level ASP panel membership includes senior advisor representatives (or representatives delegated by center staff functionals) from the disciplines of: Acquisition Excellence (AQ), Acquisition Security, Acquisition Intelligence, Test (applicable test personnel), Legal (JAN or AFMCLO), Engineering (EN), Contracting/Competition Advocate (PK), Logistics (AQ), Program Management (AQ), and Comptroller (FM). In addition to the core ASP panel, the following representatives may augment the panel: Defense Contract Management Agency (DCMA), Capabilities Integration (XR), Environmental, Plans and Programs (XP), Small Business (SB), Systems Safety (SE), other commands with program dependencies. The ASP chair may consider additional members, depending upon the type of acquisition, for advice and counsel. The Product Center Commander may authorize local variations in panel membership. For Air Logistics Centers: The Standing ASP Panel is comprised of Engineering (EN), Financial Management (FM), Legal (JA), Contracting (PK), Small Business (SB), Plans and Programs (XP), Program/Sustainment Management (GR), Logistics/Supply Management (GLSC), and ad hoc members as applicable to individual acquisitions. The Air Logistics Center Commander may authorize local variations in panel membership.

3.2.4.1.2 Center-Level ASP Panel Members Roles and Responsibilities

ASP Panel members are expected to attend ASP meetings and be knowledgeable of their ASP roles. Membership is recommended to be consistent for individual programs’ Pre-ASP and ASP, providing continuity in advice and limiting re-education. They are familiar with the requirements and acquisition to be examined, providing inputs to the ASP chair. Panel members evaluate strategies for realism, flexibility, risk, overall balance, responsiveness to the user, and executability. They research functional issues and provide consistent counsel in addition to fostering a cross flow of knowledge from program to program. Dissenting opinions from the ASP panel are appropriate, although they are expected to be discussed in pre- meetings.

3.2.4.2 ASP Secretariats

3.2.4.2.1 SAF/AQ Level ASP Secretariat (SAF/AQ-PM & AE) Responsibilities

7  Schedule ASPs  Keep a list of standing ASP members  Archive minutes  Collect and disseminate lessons learned through updates to the ASP template as well as by providing feedback to program offices in the preparation of their briefing  Provide recommendations and trend analysis based upon lessons learned  Provide templates, guidance, and assistance to center-level ASP secretariats, as appropriate

3.2.4.2.2 Center-Level ASP Secretariat (ACE) Responsibilities

 Assist in scheduling ASP and Pre-ASP meetings and notifying panel members and other invitees  Keep a list of standing ASP panel members  Meet with teams in advance of ASPs to discuss the process and ACE support  Assist with identification of ASP chair and delegations  Provide briefing templates and room preparation (name tents, sign-in sheet)  Ensure center standing ASP panel and other attendees (to include SAF/AQ personnel) are invited as appropriate to ASPs  Collect and disseminate lessons learned through updates to the ASP template as well as by providing feedback to program offices in the preparation of their briefing  Attend the ASP, tracking attendance and may assist with meeting minute inputs  May assist in meeting minutes review & coordination, with action items  Coordinate with teams on SAE- and AFPEO/CM-chaired ASPs (ex: executive summary, scheduling timeframes, etc.)

3.2.5 Acquisition Strategy Panels (ASPs)

ASP meetings will be scheduled with enough time to allow for full vetting of the issues. The ASP chair should ensure all pertinent aspects of the strategy have been discussed as appropriate. The team should brief the ASP, as a minimum, on the basis for establishing explicit program cost, schedule, and performance objectives using the topics identified in the template provided by the Center ASP secretariat. The goal of the briefing is to provide the chair with an understanding of the key issues, so the chair can approve an acceptable acquisition strategy.

3.2.5.1 ASP Chair and Delegation

For non-space related ACAT I/IA and non-delegated ACAT II programs, the Service Acquisition Executive (SAE), SAF/AQ, is the ASP chairperson. Typically, the AFPEO/DAO is the ASP Chair for all delegated ACAT II and ACAT III portfolio programs. For AFPEO/CM acquisition ASP chair and delegations, refer to the AFMC MP 5307 matrix. Refer to AFFARS 5307 and AFMC MP 5307 for Center “Other Contracting” actions (See AFFARS 5302.101 for definition).

8 Delegations of the decision authority (e.g., ASP chair) are usually on a case-by-case basis and include whether the ability to re-delegate is permitted. The coordination of delegation requests should go through the requiring organization's chain to the prescribed ASP chair. Notify the ACE ASP Secretariat of the intent, who will provide samples and guidance (see Enclosure D). Requests for delegation of ASP authority can be combined with other delegations such as Source Selection Authority (SSA), Justification and Approval (J&A) and Life Cycle Management Plan (LCMP)/Acquisition Plan (AP) approval when appropriate. The document approving the delegation then becomes a part of the official contract file.

3.2.5.2 ASP Waiver

In very rare cases, a waiver to an ASP (AFFARS 5307.104-90(a)) may be requested when a decision is made not to hold an ASP. Waiver approval is by the ASP chair authority. The approval documentation must be retained in the official contract file.

3.2.5.3 Categories of ASPs

3.2.5.3.1 Service Acquisition Executive (SAE)-level ASP

The SAE-level ASP is chaired by SAF/AQ or designee. The SAF/AQ ASP template and guidelines for conducting Headquarters Air Force ASPs are available at the AF PM&AE website. The current policy requires ASP briefings to be scheduled at least 45 days in advance to allow adequate time for the Panel members to review the executive summary contents, and schedule their calendars for participation. Additionally, briefing charts must be received by the AF PM&AE at least six days ahead of the scheduled briefing or the briefing will be cancelled and rescheduled. Changes may be made to the charts only in response to questions raised or approved ahead of the briefing by the ASP chairperson and transmitted by the ASP secretariat. ASPs chaired by SAF/AQ should be supported by the AFPEO and panel members.

The Program Element Monitor (PEM) and Program Manager are responsible for taking notes and preparing the final draft minutes to include meeting action items. The PM is responsible to ensure all action items have been completed and cleared through the AF PM&AE ASP Secretariat. The PEM will then staff the package through SAF/AQ staff, concluding in a SAF/AQ signature approval. In addition, the PEM will ensure that AF PM&AE is “coordination functional” on the staff package. Completion of the staff package is required five duty days after the meeting occurs.

3.2.5.3.2 AFPEO/DAO-Level ASP

The AFPEO/DAO will chair ASPs for programs where the AFPEO/DAO has authority (see AFFARS 5307, AFMC MP 5307 & AFI 63-101). The ASP template provided by the Center ASP Secretariat is used for the briefing. The briefing reflects updates from any Pre-ASP meeting held. The Center-level ASP panel will be used (see 3.2.4.1.1). Within each Product Center and

9 Air Logistics Center, the Center Commander may authorize local variations in the use of the center-level panel.

3.2.5.3.3 Below and/or Delegated AFPEO/DAO/ALC Commander Level ASP

Based on the AFFARS and AFMC MP ASP chair authority levels, ASPs can be held at or below the product center directorate or ALC center level. The ACE ASP Secretariat is the point of contact for assistance in providing an ASP template, lessons learned and guidance, and in the meeting invitation and documentation. Any programs that have been delegated should include the appropriate members of the center functional staffs at the ASPs (to include OSF level ASP panelists).

3.2.5.3.4 AFPEO/DAO Services Acquisitions ASP

For services acquisitions, a determination is made on whether the service falls under the AFPEO/CM or a weapons system AFPEO/DAO portfolio. To determine ASP chair, refer to the FARS and AFMC MP 5307. If within a weapon system portfolio, see ASP categories listed in paragraphs 3.2.5.3.1 – 3.2.5.3.3.

An ESIS will be held in advance of each AFPEO/CM ASP. After Pre-ASPs, the ASPs will include the appropriate detail to ensure the AFPEO/CM-level panel members can thoroughly discuss and assess the viability of a proposed strategy. AFPEO/CM chaired-ASPs typically include the appropriate AFPEO/DAO/ALC Commander from the center, as well as the center ASP panelists as needed. ASPs chaired at lower levels will typically use the center-level panel (see 3.2.4.1.1).

Guidelines for how AFPEO/CM ASPs will be conducted are available at the AF Portal website for AFPEO/CM. Please also see the URL from their webpage for their CoP. The website includes the ASP template specific to services ASPs.

3.2.5.3.5 Other Contracting Acquisition ASP

For other contracting actions, please refer to the appropriate section of AFFARS 5307 and AFMC MP 5307. The ASP secretariat can assist with identification of the chair, possible chair delegations, suggested panel composition, suggested ASP template. The ASP secretariat can also work with the team in preparation of the final ASP briefing charts, as well as the ASP products (See 3.2.5.4 below).

3.2.5.4 ASP Documentation - Minutes, Action Items and Final charts

The program manager is responsible for documenting the ASP proceedings and discussion in formal meeting minutes (with briefing charts attached) with action items that are approved by the ASP Chair before proceeding with the acquisition. The documents should be appropriately marked if restricted access is needed (e.g., For Official Use Only/Source Selection

10 Sensitive/etc). Normally, the approved minutes become part of the official contract file. See Enclosure E for a sample. The team must track and ensure resolution of all action items as directed by the ASP Chair.

3.2.6 Acquisition Strategy Inputs to Acquisition Strategy Report (ASR), AP, LCMP, etc.

The ASR and AP/LCMP are typically drafted at the beginning of the process, close to completion when the ASP is held, and finalized after the ASP. The approved acquisition strategy will be documented in either the AP or LCMP and used both for contract award and program execution. ACAT ID & IA programs shall prepare an Acquisition Strategy Report (ASR) document for OSD, per DoDI 5000.02. For sustainment services and non-ACAT acquisitions, an AP may be more appropriate. For ACAT programs, an LCMP will be written and submitted for approval in accordance with AFI 63-101. At the conclusion of this step, a coherent, integrated program acquisition strategy should be documented and complete. Once the ASP is approved, the Acquisition Strategy/Life Cycle Management Plan (AS/LCMP) is submitted to the MDA for approval. Until approved, the program office does not have the authority to continue the acquisition through RFP release. The MDA can authorize RFP release prior to LCMP/AP approval per AFFARS 5307.

3.2.7 Preserving Currency of this Standard ASP Process (reference the Record of Changes)

This Acquisition Strategy Process Guide is a joint product of ASC, ESC AAC, OC-ALC, OO- ALC, and WR-ALC. Suggested revisions may be provided to any of the product center or Air Logistics Center ASP Secretariats. The product center and Air Logistics Center ASP Secretariats will meet periodically to assess the suggestions and the effectiveness of this process. Updated documents (tracking the update via Record of Changes) will be published with each center’s librarian.

11 ENCLOSURE A – ASC Specific Implementation Instructions

1. This ASC supplement provides further Center-specific guidance to the Cross- Center ASC/ESC/AAC Process Guide for Acquisition Strategy Panel (ASP).

2. The ASP Panel described in the Process Guide is identified at ASC as the Senior Acquisition Team (SAT). The ASC SAT was established to provide consistent, cross-Center counsel to the ASP chair and program teams on their acquisition strategy. The ASC SAT membership consists of Acquisition Excellence (AQ), Capabilities Integration (XR), Comptroller (FM), Contracting/Competition Advocate (PK), Engineering (EN), Legal (AFMCLO/CL or JAN), Logistics (AQY), Test (AQT), Acquisition Security (88 ABW/IPA), Environmental Management (ENV), DCMA, Small Business (SB), and System Safety (SE).

3. If the AFPEO, Directorate Deputy Director, or ASC/CA chairs an ASP for an ACAT II, ACAT III, or services program, the ASC SAT members are invited. If the ASP Chair is delegated below the Director or Deputy Director level, Organizational Senior Functionals (OSFs) may serve as a substitute for the ASC SAT members at the ASP with the following caveat. If a corresponding representative is not available, request the ASC SAT Secretariat to invite the respective ASC SAT member and a partial SAT, which includes ASC/AQ, ASC/AQT, ASC/BC, ASC/PK, and HQ AFMCLO/CL or JAN representatives.

4. The program office must invite at least one senior-level individual (LtCol/GS14 or above) from the user or requirements community to serve as a member of the ASP.

5. The program manager is responsible for scheduling all pre-ASP and ASP briefings. Plan two hours on the Chair’s calendar. Notify the ASC SAT Secretariat, as soon as an ASP or pre-ASP is scheduled to ensure ASC SAT participation. The ASC SAT Secretariat will send the invitations to the ASC Center-level SAT members.

6. FMS programs at ASC will implement the same acquisition process used in the execution of USAF programs. Special considerations may be acknowledged for FMS unique protocols. See ASC Reorganization Concept of Operations (CONOPS) Section 4.2.7 on FMS and ASC/CC Memo “Supplemental Guidance on Foreign Military Sales (FMS) Programs at ASC”.

7. Direct questions regarding this supplement to the ASC SAT Secretariat, Ms. Paula Trimbach, ASC/AQH, (937) 255-5538, or alternate Secretariat, Mr. Timothy Zwiebel, ASC/AQH, (937) 656-5951, ASC SAT [email protected].

Note: Updates to this enclosure do not require coordination with centers outside of ASC.

12 13 Enclosure B: Flowchart

14 ENCLOSURE C – Executive Summary of Acquisition Strategy Panels (ASPs) Process

PURPOSE  Develop proposed acquisition strategy by deliberative forums using senior advisors culminating in the Acquisition Strategy Panel (ASP) meeting, seeking decision maker approval of an acquisition strategy

DISCUSSION  Background o AFFARS 5307 and AFMC MP 5307 require ASPs o SAF/AQ policy establishes SAE-level ASPs with PM&AE as ASP Secretariat o Center ACE office has the ASP Secretariat for scheduling and facilitating ASPs for all PEO/DAOs  ASP Levels & Expectations: o ASP chair levels are determined by ACAT and/or dollar level o Pre-ASP meetings are held typically one level lower than the ASPs . A PEO/DAO Pre-ASP is held prior to an SAE-level ASP . A lower level Pre-ASP is held prior to a PEO/DAO-level ASP o PEO/DAO is expected to attend SAE-level ASP or a AFPEO/CM level ASP o PEO/DAO ASP chairs are expected to coordinate with PEO/DAO of interdependent efforts on strategy development/schedules/etc. that may impact the other programs o Center Commanders may authorize local variations in the use of the center-level panel o Center-level ASP Panel is standard but tailorable for each ASP . Panel attends pre-ASP meetings and provides counsel to the ASP Chair . Panel attends all PEO/DAO-level ASPs . Panel should have already evaluated proposed strategy prior to ASP . Panel dissenting opinions are solicited by Chair for deliberation and direction; ensure all pertinent aspects of the strategy are discussed  Process methodology: o Delegations/Waivers: ASP chairs may delegate authority or waive ASPs (PEO/DAO to Dep Dir) . Delegations below PEO/DAO may require a partial center ASP panel o ASPs are held after the pre-ASP MIRT; and prior to Acq Plan/LCMP approval and RFP release o ASP Attendees include stakeholders such as PEO/DAO with ancillary portfolios, the Center-level ASP panel, senior level user(s), Air Logistics Centers (ALC), Laboratory acquisition/technical professionals, other involved centers, consultants, senior directorate functionals, etc.  Content: o Formal ASP templates provided by the ACE are specific to effort type (services or supply) o Topics typically cover: Program Description/Requirement; Risk Assessment and Mitigation Strategies; Proposed Acquisition Strategy; Systems Engineering; Financial/Cost; Schedule and other topics as applicable (e.g., Test Program) o Typically an ASP is about two hours in duration  Formal Outputs: o Minutes of PEO/DAO-level ASPs should be fully coordinated by 10 business days o PEO/DAOs approve meeting minutes & receive PM’s action item status for PEO/DAO-level ASPs o PEO/DAOs review minutes/action items as they are elevated for SAE-level ASPs

SUMMARY . ASP approval with the Acq Plan or LCMP/AP approval allow RFP release

15 . Center ASP Secretariat is available to provide specific training

ENCLOSURE D Sample Request for Delegation of Chairperson Authority (Staff Summary Sheet with Tab 1 Delegation Letter)

STAFF SUMMARY SHEET SIGNATURE SIGNATURE (Surname), TO ACTION TO ACTION (Surname), GRADE GRADE AND DATE AND DATE xx/xx(within [revise coord per command front Center/CA (or) 1 Coord 6 Sign directorate) office direction, as needed] AFPEO/DAO/xx 2 Insert others Coord 7

3 xxx/CCX Coord 8

4 xxx/CS Coord 9 XXXX 5 xxx/CV Coord 10 Coord Secy SUSPENSE SURNAME OF ACTION OFFICER AND GRADE SYMBOL PHONE TYPIST’S INITIALS DATE John Doe, GS-13 XXXXX XXXXX xx xxx xx XXX SUBJECT DATE (NAME OF PROGRAM) Acquisition Strategy Panel (ASP) Chair Delegation xx xxx xx SUMMARY 1. PURPOSE. Obtain AFPEO/DAO/xx approval of the (NAME OF PROGRAM) ASP Chair delegation (Tab 1).

2. BACKGROUND. The (NAME OF PROGRAM) will acquire XXXXXXXX capability. The estimated value of this acquisition is $XXXXXXX. An ASP is planned for (MM YY/ Summer 20xx/ etc). Planned Pre-ASP activities include (ESIS, Pre-ASP meeting XXXXX date, etc). Anticipated RFP release date is XXXXX and projected contract award date is XX XXX XX. The major risks associated with this acquisition are XXXXXX XXXXXXX. Other issues include XXXXXXX.

3. DISCUSSION. The AFFARS 5307 allows for delegation to the XXXX level with/without the ability to re-delegate. Due to the (lack of major acquisition issues / acquisition schedule / include any appropriate justification) request that (name of person and office symbol) be delegated the authority to Chair the ASP with the additional authority to re-delegate, if needed.

4. VIEWS OF OTHERS. [None or: xx office has a dissenting opinion (& explain why) (if applicable)]

5. RECOMMENDATION. AFPEO/DAO approve and sign the proposed delegation authority at Tab 1.

[signature block] 1 Tab Delegation Letter

SAMPLE BODY OF ASP CHAIR DELEGATION LETTER FOR SSS TAB 1 ------Tab 1 Memo: MEMORANDUM FOR [office of new ASP chair] FROM: AFPEO/DAO/XX (or office of current ASP chair) SUBJECT: Delegation of Acquisition Strategy Panel (ASP) Chair Approval for the [acronym] Contract I delegate the ASP authority for the basic [name] Contract to the [name & directorate]. Further re-delegation is prohibited. [Signature block]

16 ENCLOSURE E - SAMPLE ASP MINUTES

MEMORANDUM FOR (Program Manager) FROM: (Position of ASP Chair) SUBJECT: Program name; Acquisition Strategy Panel Minutes and Acquisition Strategy Approval

Ref: Acquisition Strategy Panel (ASP), (Date)

1. On (Date), the (Organization) recommended an acquisition strategy approval for the (Program) to the (Position of ASP Chair) and the ASP Panel. Participants are listed in Attachment 1. (Briefer’s name and organization) presented the acquisition strategy. This memo constitutes the minutes of the ASP IAW AFFARS 5307.104-90(d).

2. Objective(s): The objectives of this ASP were to obtain: a. Approval of the (program name) acquisition strategy as briefed. b. (List other specific objectives such as delegation of Source Selection Authority, approval of extended contract period of performance, etc.).

3. The following is a brief summary of the issues and actions discussed during the briefing with resulting action items and decisions as relevant. Topic Discussion: Recommendation, conclusion, or advice Disposition: Action, directive, or decision (include completion date and OPR)

4. As the designated ASP Chair, I approve the ASP minutes for the ______Program as presented in the ASP slides (Attachment 2).

5. ______The acquisition strategy is approved and upon approval of the LCMP/AP you will be authorized to proceed with release of the Request for Proposal (RFP).

______The acquisition strategy is approved but you are NOT authorized to proceed with release of the Request for Proposal (RFP) until the LCMP/AP is approved and all action items identified in the ASP minutes are completed and the ASP Chair’s approval for closure is obtained. Route summary of completed action items through the Program Execution Group (PEG) for ASP Chair approval.

6. This memo and the slides at Attachment 2 represent an acquisition strategy framework and constitute a contract between the undersigned ASP Chair and the program manager. As such, you shall ensure that the RFP, Life Cycle Management Plan/Acquisition Plan, and resulting contract are accomplished in accordance with the acquisition strategy described in the attached briefing slides. Any changes to the acquisition strategy, including those arising from contract clearance, must be approved by the ASP Chair prior to contract award.

(Signature/Title) ASP Chair Attachments: 1. ASP Attendance List 2. (Date) Briefing Slides

17