# DLAD PGI

- SUBPART 17.93 Surge and Sustainment ( S&S) [F25]

- 17.9300.
- 17.9301. S&S Implementation Procedures, Guidance, and Instructions for Contracting Officers.
- 17.9303(c)(1)
- 17.9303(c)(2)
- 17.9303(c)(3)
- 17.9303(c)(4)
- 17.9393(c)(5)
- 17.9303(c)(6)
- 17.9303(c)(7)
- 17.9303(c)(8)
- 17.9303(c)(9)

SUBPART 17.93 Surge and Sustainment ( S&S) [F25]

17.9300.

This DLAD PGI subpart prescribes the mandatory procedures, guidance, and instructions for obtaining Surge and Sustainment (S&S) coverage through acquisition planning and long-term contracting. Refer to the Industrial Capabilities Surge and Sustainment One Book for a more detailed process, if necessary.

17.9301. S&S Implementation Procedures, Guidance, and Instructions for Contracting Officers.

The procedures, guidance, and instructions help Contracting Officers implement S&S in the acquisition process. The supporting Industrial Specialist (IS) shall assist the Contracting Officer with implementation to ensure appropriate S&S coverage is obtained.

Steps | Tasks | Sources
PRE-SOLICITATION
1 | (a) CO conducts market research (e.g., historical surge plan and performance, collaboration with industrial specialist) to determine the appropriate strategy to obtain S&S coverage. (i) If market research clearly shows that surge quantities and delivery schedule can be met through the LTC contract maximum and required delivery, and can satisfy both peacetime and wartime requirements, CO shall consult the IS to determine if surge-specific provisions can be excluded, in part or as a whole, from the solicitation. (ii) CO shall only exclude surge-specific provisions after receiving approval from the Industrial Base (IB) Chief through the waiver process below, and will clearly document the market research result, surge coverage decision, and approval in the acquisition plan. (b) Except as stated below, Contracting officer (CO)/Buyer conducts surge check using the Industrial Base Management System (IBMS): (i) Go to https://www.dla.mil/wicap Refer to Exhibit 1 for IBMS Surge Check procedures. (ii) Copy and paste NSN or NIIN (LTC population) in IBMS. (iii) IBMS provides surge requirements expressed as monthly wartime rate (MWR) to include estimated PLT. (iv) Export surge results from IBMS to Excel. (v) Save Excel sheet to preferred drive or desktop. Use RFP number and Project Name to title surge requirements in IBMS. (vi) Edit Excel sheet to meet required CLIN format - add columns for 9900 CLINS (9961, 9962, 9963, & 9964), UI, and for pricing MWR. Estimated PLT is provided to buyer as information only and should not be included in the solicitation. Refer to Exhibit 2A for the CLIN sample and 4.7103-2(a)(90). (c) For Medical, Buyers consults the DSCP Medical Contingency Contracting Office to validate surge requirements on LTC item candidates and surge coverage recommendation. DSCP Medical uses Readiness Management Application (RMA) as the Industrial Base (IB) tool to identify S&S requirements. (d) For Subsistence and C&T, Buyers consult IB Chief to validate surge requirements on LTC item candidates and surge coverage recommendation. DSCP Subsistence and C&T use SPIDERS or IBMS to identify S&S requirements. (i) For Subsistence, Buyers include surge quantity option in percent or exact number to identify surge requirements. Surge quantity option is calculated using historical demand data or other appropriate data. (ii) Buyers identify surge quantity option using a regular CLIN and include 9900 CLINS (9961, 9962, 9963, & 9964). Refer to Exhibit 2C for the surge quantity option CLIN sample and 4.7103-1(a)(90). (iii) For C&T, Buyers include D1-D6 schedule to identify surge requirements. Surge requirements are obtained from SPIDERS or IBMS. (iv) Buyers identify D1-D6 schedule using regular CLINS and include 9900 CLINS (9961, 9962, 9963, & 9964). Refer to Exhibit 2B for D1-D6 CLIN sample and 4.7103-1(a)(90). (e) Contracting Officers shall obtain surge coverage for items identified as the Services “go-to-war” items during the acquisition process for all long-term contracts, except IDPO, in accordance with DLAD 17.9303(c). (f) The CO documents S&S coverage strategy in the acquisition plan. | 17.9303(c)(1) Exhibit 1 Exhibit 2A Exhibit 2C Exhibit 2B
SOLICITATION
2 | (a) When surge requirements apply, CO includes the following in the solicitation: (i) S&S clauses IAW DLAD 17.9304; and (ii) S&S CLINS 9960, 9961, 9962, & 9963, IAW 4.7103-(a)(90); and (iii) Include MWR or D1-D6 using regular CLINS (i.e., 0001, 0002, etc.) to identify surge requirements. Refer to Exhibit 2A or 2B for CLIN structure sample. (b) For Prime Vendor arrangements for commercial, market ready items, non-NSN, or part numbered items, CO includes the following in the solicitation: (i) S&S Alternate Clauses IAW DLAD 17.9304; (ii) S&S CLINS 9960, 9961, 9962, & 9963. Refer to Exhibit 2C for CLIN structure sample. (iii) Include surge quantity option expressed as a percent or an exact number using a regular CLIN. Refer to Exhibit 2C for CLIN structure example. (c) CO determines and identifies the appropriate technical evaluation criteria in the solicitation: (i) For best value/source selection, Buyer in collaboration with the IS determine the appropriate S&S evaluation criteria in the solicitation; or (ii) For LPTA and/or ABVS, Buyer in collaboration with the IS determine appropriate or additional evaluation criteria if necessary to evaluate the CAP for technical acceptability (go or no go). (d) CO notifies the IS immediately via email when the solicitation is issued and/or available in the ECF. (e) IS will obtain copy of solicitation from ECF to update the appropriate IB tool. | 17.9303(c)(2) Exhibit 2A Exhibit 2C
3 | (a) Solicitation Amendment, Changes, Closing: (i) CO collaborates with IS before making changes to surge coverage in the RFP after issuance (i.e., increase, decrease, or deletion). (ii) IS assesses the impact of the proposed change to surge requirements and will advise the CO. (iii) CO proceeds with the amendment or change after receiving IS feedback. (iv) Buyer notifies the IS when the amendment is posted in the ECF. (v) IS obtains a copy of the amendment and updates the appropriate IB tool. |
| (b) Supplier is required to submit the following with the proposal upon solicitation closing: (i) Prices for MWR or D1-D6, either in $ or %; (ii) When surge pricing exceeds peacetime prices, vendor provides sufficient explanation by submitting information other than cost or pricing, or, if applicable, certified cost or pricing data to determine price reasonableness or cost realism IAW Clause 52.217-9009; (iii) Submits capability assessment plan (CAP) using applicable IB Tool (i.e, WICAP/eCAP or SPIDERS) as specified in Clause 52.217-9007 or the Alternate Clause; (iv) Submits hard copy of the CAP or questionnaire with the proposal. |
EVALUATION |  |
4 | (a) Buyer submits the Capability Assessment Plan (CAP) or Questionnaire to IS for evaluation and recommendation: (i) Buyer submits an electronic copy of the CAP or questionnaire to the IS via email; (ii) IS reviews and advises the Buyer; (iii) IS determines the application of Warstopper (WS) or Government investment; (iv) If Warstopper or Government investment applies, Buyer notifies all vendors competing in the acquisition during negotiations or issues a modification to include the investment; and IS assists the Buyer with processing the investment; (v) Buyer documents the IS recommendation and negotiation plan in the PBM. (b) When evaluating MWR or D1-D6 prices, (i) Buyer evaluates the surge prices to determine price reasonableness and cost realism IAW FAR 15.404-1, 15.403, 2.101, and DFARS 217.7505(b)(2); (ii) Total surge price is not added in the overall comparative price evaluation to determine awardee due to varying factors affecting surge pricing; (iii) Buyer documents surge price objectives in the PBM. | 17.9303(c)(3)
NEGOTIATION/DISCUSSION
5 | (a) CO negotiates if necessary to obtain surge coverage. Delivery for S&S items will be 30 days or less. (b) CO makes every attempt to obtain surge coverage to include the following: (i) Negotiate surge prices if necessary; (ii) Use the exit strategy (e.g., surge asset buy-back for high demand items, surge asset ramp down) as leverage or negotiating tool to obtain surge coverage; (iii) Consider alternate packaging or guaranteed minimum for surge items if appropriate and/or applicable; (iv) Engage the IS and/or IB Chief during negotiations to determine alternate surge strategy to obtain coverage; (v) Collaborate with IB Chief to determine if Government investment can be applied to obtain surge coverage. NOTE: When negotiating/discussing surge, make every attempt to obtain surge coverage and consider vendor’s proposed alternatives to support the Services’ go-to-war items IAW DLAD 17.9303(a). (c) If vendor’s CAP excludes the exit strategy, obtain one during negotiation/discussion. Vendor is required to include an exit strategy IAW Clause 52.217-9006. CO ensures that the proposed exit strategy is in the Government’s best interest. (d) Consider the following exit strategies when WS or Government investment does not apply: (i) Surge asset ramp-down before contract expiration date (i.e., 6-12 months); (ii) Asset buy-back for highly demanded or backordered items based on historical stock position, or to have inventory on- hand until follow-on contract can be established; (iii) Apply asset buy-back guaranteed minimum in percent, dollar amount, or quantity based on historical demand patterns and/or items with long lead times; (iv) Shift assets to other contracts if applicable. (e) Consider the following exit strategies or other alternate strategy that is in the Government’s best interest when Warstopper investment applies: (i) Transfer investment to the next contract; (ii) Put investments into production to produce finished goods and offset price for Government furnished property, material, or equipment; (iii) Salvage investment to be used for other government projects; or (iv) Return funds to US Treasury through the WS Program Manager at HQ DLA J-74. (f) For other Government investment application: (i) Supplier may request for Government investment during negotiation/discussion; (ii) CO consults the IS to determine if Government investment can be applied and IS advises the CO; (iii) CO exercises prudence and limit or conserve use of Government investment when obtaining S&S coverage. Only authorize or allow Government investment to overcome S&S shortfall and/or to obtain coverage. Refer to 52.217-9006(c)(3) to (7) for shortfall conditions; (iv) CO and IS approve request for Government investment only when it is absolutely in the Government’s best interest to do so; (v) CO ensures an exit strategy is included when Government investment applies. Refer to exit strategy alternatives under (e) above. (g) For Warstopper (WS) investment application: (i) WS application is determined and approved by the DLA HQ J-7 WS Program Manager(PM). (ii) When WS investment applies, CO notifies the vendor(s) of Government investment during negotiations or discussions. Refer to 52.217-9010 for Limitation on Use of S&S Government Investment. (iii) CO exercises great prudence when negotiating surge coverage with WS investment and only include when approved by DLA HQ J-7 WS PM. (h) When DLA HQ J-7 WS PM approves use of WS investment, the CO consults the IS to process the investment: (i) IS processes the request and advises the CO of WS funding approval; (ii) Upon receiving funding approval, the CO: (A) Includes the WS CLIN 9965 and not-to-exceed amount in the contract; (B) Incorporate appropriate exit strategy as listed under (e) above; (i) If WS or Government funding is approved before contract award, CO notifies all vendors competing in the acquisition of the approved investment amount and includes explicit written language describing use and limitation of Government investment. (j) If WS or Government funding approval occurred after contract award, CO notifies and advises the supplier of approval by issuing a contract modification with the approved dollar amount using CLIN 9965 and includes explicit written language describing use and limitation of Government investment. (k) For a successful negotiation, (i) Proceed with awarding surge coverage; (ii) Include appropriate surge CLINS, MWR/D1-D6 prices, exit strategy, WS investment (if applicable) in the contract; (iii) Include explicit language in the contract on use and limitation of WS or Government investment; (iv) Document the PNM of surge negotiation results. (l) When negotiation is unsuccessful, (i) After making every attempt to obtain surge coverage, and vendor refuses to support surge, and/or negotiation becomes extended, and/or surge prices are unreasonable, Buyer elevates to the CO for a waiver request decision and describe attempts made to obtain surge coverage; (ii) CO consults IB Chief for alternate solutions or recommends to exclude surge requirement, in part or as whole, via a waiver request; (iii) IB Chief recommends alternate solution if any or approve waiver request; (m) Surge Waiver Process (i) CO sends a waiver request to the IB Chief via email that includes the following information: (A) Describe every attempts made to obtain surge coverage; (B) Inform IB Chief whether the contract maximum (quantity or dollar value) can sustain potential increase in demands in the event of future contingency or emergency; (C) Incorporate CO’s decision/concurrence to exclude surge, in part or as a whole, in the email; (D) Attach surge coverage or item(s) being excluded from LTC; (ii) IB Chief may recommend other alternatives if any or approves the waiver request via email and forwards a copy to HQ DLA J-74; (iii) Buyer excludes surge coverage or item(s) as a requirement after receiving approval from the IB Chief; (iv) CO ensures the contract maximum (quantity or dollar value) can cover potential surge in demands in the event of future contingencies to prevent untimely contract expiration; (v) Buyer documents the PNM and includes the waiver approval in the contract file; (vi) IS coordinates with SMSG or IST Lead for alternate surge support strategy for the excluded surge coverage or item(s). (n) IS in collaboration with the SMSG or IST Lead considers the following alternatives: (i) Corporate Exigency Contracts (CEC); (ii) Minimum Sustaining Rate (MSR) contracts (this type of contract may generate protected inventory that can be used to meet contingency demands as free issue); (iii) Industrial Base Maintenance Contracts (IBMC); (iv) Vendor Managed Inventory; and/or (v) Agreements common in some industries (e.g. subsistence), such as memorandum of understanding/agreement or blanket purchase agreement. (o) If using alternate support strategies listed under (n) above, DLAD 17.93 does not apply. Terms, conditions, and provisions for these alternatives will be developed and established by the Contracting Officer and IS based upon specific contingency support needs of the customer(s). (p) When the alternative methods to obtain S&S coverage also fail, the IS notifies the IB Chief and HQ DLA J-74 that Unsupported Item Issue (UII) exists. IS takes the appropriate action to notify the Service(s) and document UII in the appropriate IB tool (i.e., IBMS, SPIDERS, RMA). IS relays the information to the SMSG/IST Lead for future acquisition planning and strategy. (q) CO documents the contract file of the UII for future use. | 17.9303(c)(4)
AWARD
6 | (a) CO incorporates approved CAP in the contract. (b) If WS or Government investment applies, CO incorporates CLIN 9965, approved dollar amount, and explicit written language in the contract regarding limited use of investment. (c) Provides final surge items awarded and notifies the IS when the contract is available in ECF. (d) IS obtains a copy of the contract from ECF to update the appropriate IB tool (i.e., IBMS, SPIDERS). (e) CO uploads surge CLINS in SAP Outline Agreement (OA). Refer to Job Aid “Establishing a Surge Outline Agreement” in EBS Online Help for instructions. | 17.9393(c)(5) Job Aid – EBS OLH
POST AWARD
7 | (a) Deleting Surge Items (i.e., Obsolete items, item no longer needed, etc.) – IAW Add/Delete Clause (i) CO notifies the IS via email before deleting surge coverage or item(s) from the LTC; (ii) CO follows the surge waiver process under Section 5(m) above when excluding or deleting surge coverage or item(s) from the LTC; (iii) IS assesses and determines impact to surge support and WS investment (if applicable, and advises the CO; (iv) CO proceeds with deleting surge coverage or item (s) from the LTC via a modification after receiving approval from the IB Chief. Modification (mod) will include disposition and instructions for WS or Government investment, if applicable); (v) CO documents the contract file by including waiver request, IB Chief approval and a copy of the mod; (vi) CO updates the OA in SAP by removing the surge coverage or item(s) from LTC; (vii) CO notifies the IS via email when mod becomes available in the ECF; (viii) IS obtains a copy of the mod from ECF and updates the appropriate IB tool; (ix) IS advises the Services. (b) Adding Items (Phased Pricing) IAW Add/Delete Clause (i) CO conducts surge check using the appropriate IB tool or by consulting IS. Refer to Section 1 for the surge check procedure. If surge requirement applies, CO obtains surge pricing and CAP from the vendor: (ii) CO evaluates surge Pricing, and IS reviews the CAP and advises the CO. Refer to Section 4 above for procedures on CAP and surge price evaluation; (iii) CO negotiates if necessary to obtain surge coverage for the added items. Refer to Section 5 above for negotiation or discussion procedures; (iv) CO incorporates surge coverage via a mod. Follow the procedure under Section 6 when adding surge coverage or item(s) on LTC; (v) CO notifies the IS when mod is available in the ECF and provides the awarded surge items; (vi) IS obtains a copy of the mod from the ECF and updates the appropriate IB tool. | 17.9303(c)(6)
| (c) Decreasing or Increasing MWR (i) If CO intends to decrease/increase the surge coverage, notify the IS before making any changes; (ii) IS reviews and determines the impact to the customer, surge support, and WS investment (if applicable); (iii) IS collaborates with the Services if necessary and advises the CO via email; (iv) CO proceeds with decreasing or increasing surge coverage after receiving IS recommendation; (A) If increasing MWR or D1-D6, negotiate with vendor if necessary to lower surge prices and update the CAP; (B) CO issues the mod reflecting the change and include instruction for WS investment adjustment (if applicable); (v) CO documents the contract file by incorporating all related email transactions in the ECF; (vi) CO updates the surge coverage in SAP OA when changes are made and notifies the IS when mod is available in ECF; (vii) IS updates the appropriate IB tool. | `
| (d) Exercising Option Periods (i) CO notifies the IS before making any changes to the surge coverage i.e., add/delete items or increase/decrease); (ii) Follows the procedures under (a), (b), (c) above when adding, deleting, increasing, or decreasing surge coverage; (iii) Remember to update the OA and document the contract file when changes are made to surge coverage; (iv) CO notifies the IS when the option mod is available in the ECF to update appropriate IB tool. |
S&S EXECUTION
8 | (a) CO invokes/executes surge IAW 17.9306, when: (i) Supporting project coded requisition(s) for: (A) Wartime or contingency operations; (B) Reconstitution of contingency resources following wartime or major exercise; (C) NMCS, MICAP, unusual and compelling requirements; or (ii) Directed by senior leaders to support anticipated increase demands in preparation for national emergency; or (iii) Supporting peacetime issue to resolve backorder situation affecting customer readiness (Requires J7 approval); or (iv) To support testing, validation, or maintenance of S&S capability. (b) Prior to invoking/executing surge, the CO considers the following: (i) Buyer validates the item(s) for surge coverage in the LTC, verify MWR, D1-D6 or surge quantity option, and ramp-up time requirement; and (ii) Determine if requirement meets criteria under (a) above; and (iii) Determine if it’s in Government’s best interest to invoke/execute surge in lieu of other support that may be more cost effective (e.g., expedited delivery, spot buys, diversion, redistribution orders, etc.), and consider delivery, customer readiness, and vendor performance record. (c) Surge trigger or input to invoke/execute may come from the following: (i) Internal input (A) Manual – CO, Buyer, Supply Planner (SP), Customer Account Specialist (CAS), Industrial Specialist, Seniors Leaders, HQ DLA J-74; (B)Automated – Industrial Base Management System, SAP. (ii) External input – Customers or Services. (d) Invoking/executing surge for DLA Direct: (i) Supply Planner (A) Validates backorder, due-in, stock-out situation, and criteria listed under 8(a) above prior to generating a Surge PR for manual sourcing; (B) Identifies the PR as a “Surge PR”. (C) Notifies the CO of the Surge PR via email for immediate processing. Refer to the Job Aid “Creating a Surge Purchase Requisition” in EBS Online Help for instructions; (ii) Contracting Officer (A) Retrieves Surge PR sent by the SP; (B) Validates the Surge PR against the email sent by the SP; (C) Prior to invoking or executing surge, CO follow steps under (b) above and ensures that it’s in the Government best interest to invoke or execute surge to support the requirement in lieu of other support; (D) Sources surge PR against the appropriate Surge CLIN(S) in the OA and includes a remark stating “This is a Surge Order”; (E) CO notifies the vendor and IS immediately by emailing a PDF copy of the order with subject title “Surge Order – Read Immediately”; Includes the PIIN, Order Number, and other information deemed necessary to bring immediate attention to the order for processing. (iii) IS tracks and reports surge execution. (e) Invoking/executing surge for Customer Direct: (i) Customer Account Specialist (A) Uses Surge CLIN(S) to source CD requisitions that meet the criteria under 8(a) above; (B) Project coded requisition can be sourced automatically in SAP by loading the appropriate Surge CLIN(S) in the OA and inclusions and/or exclusions. (C) CAS consults the CO to validate surge coverage in LTC and to load the surge CLINS in SAP OA (if not already loaded). (D) CO notifies the vendor and IS immediately by emailing a PDF copy of the order with subject title “Surge Order – Read Immediately”; Includes the PIIN, Order Number, and other information deemed necessary to bring immediate attention to the order for processing. (E) IS tracks and reports surge execution. (ii) CO is responsible for loading surge CLIN(S) in SAP OA. | 17.9303(c)(7) Job Aid – EBS OLH
SUPPLIER CHANGE IN S&S CAPABILITY
9 | (a) In the event of supplier change request to the CAP due to unexpected supply chain interruption (i.e., extreme market conditions, natural disaster, labor dispute, etc.), the following applies: (i) CO instructs the supplier to update the CAP using the appropriate IB tool. CO notifies and consults the IS; (ii) IS reviews and assesses the impact to the customer and WS investment (if applicable), and advises the CO with the next step; (iii) CO takes action based upon the IS recommendation; negotiates if necessary to keep the surge coverage if possible; documents the contract file; and updates the surge coverage in the OA; (iv) Refer to Section 7 above if making changes to surge coverage (i.e., decreasing, increasing, deleting). (b) If vendor can no longer support surge coverage (e.g., bankruptcy, etc.) and contract is being terminated untimely or before contract maturity: (i) CO notifies the IS as soon as possible; (ii) IS assists the CO with recouping the WS investment (if applicable); (iii) CO will exercise exit strategy to recoup/recover WS investment and issues a mod with instructions on investment disposition; (iv) CO notifies IS when mod becomes available in ECF and document contract file; (v) IS retrieves mod from ECF and updates the appropriate IB tool; (vi) IS works with SMSG or IST Lead to determine alternate or follow-on surge support strategy. | 17.9303(c)(8)
CONTRACT EXPIRATION/TERMINATION
10 | (a) Exercise the appropriate exit strategy before contract termination or expiration: (i) If contract includes WS investment (A) CO consults the IS for assistance if needed when exercising the exit strategy involving WS investment; (B) CO ensures all investments (i.e., funds, raw materials, finished good, etc.) are recouped and recovered to the maximum extent possible; (C) CO exercises S&S exit strategy as stated in the contract and recoup/recover all Government investment. If Government investment cannot be recouped or recovered due to unforeseen circumstance (e.g., bankruptcy) and the existing exit strategy cannot be applied, CO can exercise an alternate exit strategy that is in the best interest of the Government. Consults IS for assistance and elevates to HQ DLA J-74 if necessary for alternatives. (ii) If contract does not include Government investment, (A) CO exercises the exit strategy IAW the contract; (B) CO considers Government’s stock position and the lead time for establishing follow-on contract when exercising the exit strategy. Consider backorder, stock-out, customer support gap, and acquisition timeline when determining disposition of surge coverage. (b)If terminating the contract, CO notifies the IS immediately to determine alternate surge support strategy. (c) CO documents the result of the exit strategy in the contract file for future use as lessons learned. | 17.9303(c)(9)