Single Processes Initiative

Overview.

Definition: The purpose of the Single Process Initiative (SPI) is to remove highly-tailored or customer-unique requirements from contracts and adopt instead, a single process proposed by the contractor. For example, if a contractor is allowed to use a single soldering standard (proposed by the contractor) for all work at its facility, costs to all affected customers should be reduced, while maintaining or even increasing quality.

Concerns: Because government agencies have their own unique set of requirements, a contractor can have several very similar systems or processes set up to accommodate each Agency. Maintaining many similar set-ups required by the government is inefficient and costly to the contractor and to the government.

Goal: Enable contractors to propose single processes that would meet the needs of multiple customers, and eliminate unique processes/systems that are imposed on contractors, unless they are essential to ensure mission safety and reliability. SPI is expected to improve process efficiencies, improve product quality, reduce the contractors' operating costs, and, reduce Government acquisition costs. The target time frame is 120 days from receipt of a concept paper to issuance of a contract modification.

Key Elements: All contractor systems and processes are candidates for this initiative if efficiencies can be gained. SPI would eliminate duplicative contractor systems and processes imposed by each customer's requirements.

NAVAIR TSD Process & Guidance For Review Of Single Process Initiative

1. Purpose:   This guidance is provided to assign roles and responsibilities to NAVAIR TSD competencies for the review and recommendation for approval or disapproval of Industry proposed Single Process Initiatives (SPI).

2. Background:   Under Secretary of Defense (Acquisition & Technology), Dr. Paul Kaminski's, Single Process Initiative, memorandum of 8 Dec. 1995 directed ACOs to

"...encouraged contractors to prepare and submit concept papers describing practices that will permit uniform, efficient facility wide management and manufacturing systems and a method for moving to such systems."

Administrative Contracting Officer's (ACO) will forward these concept papers to key Government customers doing business with these Companies for review and comment. If the consensus of the key Government customers is to approve the concept then the ACO, will modify all active contracts within that facility to adopt the new practice. The decision of the ACO is binding.

3. NAVAIR TSD Roles and Responsibilities:

    a.)  Competency 1.0A1

1. Designated as the NAVAIR TSD Point of Contact for all Single Process Initiative concept papers, and if necessary will represent NAVAIR TSD on SPI management councils, chaired by facilities ACOs to discuss and review the Contractors SPIs.
2. Will distribute copies of Contractor SPI concept papers to other NAVAIR TSD Competencies for technical review and comment.
3. Will review SPI concept papers for project management impacts to existing contracts, specifically identified within the SPI concept paper, and to future NAVAIR TSD contracts.
4. Is responsible for achieving consensus with the other Competencies if there is a disagreement on the acceptability of the SPI. If consensus between the NAVAIR TSD Competencies can not be reached the final decision to approve or disapprove the SPI rests with Competency 1.0A1.
5. Will coordinate and consolidate Competency comments and formulate the corporate NAVAIR TSD position.
6. Will respond back to the ACO in writing with NAVAIR TSDs concurrence or disagreement with the SPI within 15 working days of the SPI cover letter, and provide Competency Leads with a copy of the letter.
7. Will provide feedback to the Competencies regarding the ACOs final disposition on the SPI.
8. Will identify the process by which SPI are addressed within NAVAIR TSD and identify roles and responsibilities for addressing SPIs.
9. Will update and maintain SPI guidance as the need arises via the NAVAIR TSD "Acquisition Guide".
10. Will identify internet sites containing additional information on Single Process Initiatives for employee reference.
11. Will maintain a data file of SPIs processed through NAVAIR TSD and post the status of SPIs on the NAVAIR TSD Acquisition guide.

    b.)   Competency 2.5.3

1. Will review SPI concept paper for contractual and FAR impacts to existing contracts, specifically identified within the SPI concept paper, and to future NAVAIR TSD contracts.
2. Will provide, via eMail,a documented position agreeing or disagreeing with the Contractors SPI along with supporting technical rational to Competency 1.0A1.
3. When block changes havebeen initiated by the ACO, Competency 2.5.3 will notify all affected project teams and Competency Leads that an SPI has been adopted at a facility where NAVAIR TSD has active contracts.

    c.)   Competency 3.0

1. Will review SPI concept papers for logistics and life cycle considerations to existing contracts, specifically identified within the SPI concept paper, and to future NAVAIR TSD contracts at that facility.
2. Will provide, via EMail, a documented position agreeing or disagreeing with the Contractors SPI along with supporting technical rational to Competency 1.0A1.

    d.)   Competency 4.6

1. Will review SPI concept papers for engineering and technical impacts to existing contracts, specifically identified within the SPI concept paper, and to future NAVAIR TSD contracts at that facility.
2. Will provide, via eMail, a documented position agreeing or disagreeing with the Contractors SPI along with supporting technical rational to Competency 1.0A1.

    e.)   Legal Counsel

1. Will review SPI concept papers and provide, via eMail, a documented legal position to Competency 1.0A1.

SPI Review and Approval Process.

NAVAIR TSD List.   List of SPIs reviewed by NAVAIR TSD.

211.273 Substitutions for military or Federal specifications and standards.

211.273-1 Definition. "SPI process," as used in this section, is defined in the clause at 252.211-7005, Substitutions for Military or Federal Specifications and Standards.

211.273-2 Policy.

1. Under the Single Process Initiative (SPI), DoD accepts SPI processes in lieu of specific military or Federal specifications or standards that specify a management or manufacturing process.
   
   
2. DoD acceptance of an SPI process follows the decision of a Management Council, which includes representatives from the Defense Contract Management Command, the Defense Contract Audit Agency, and the military departments.
   
   
3. In procurements of previously developed items, SPI processes that previously were accepted by the Management Council shall be considered valid replacements for military or Federal specifications or standards, absent a specific determination to the contrary (see 211.273-3(c)).

211.273-3 Procedures.

1. Solicitations for previously developed items shall encourage offerors to identify SPI processes for use in lieu of military or Federal specifications and standards cited in the solicitation. The solicitation shall require an offeror proposing to use an SPI process to include, in its response to the solicitation, documentation of the Government acceptance of the process.
   
2. Contracting officers shall ensure that--
   1. Concurrence of the requiring activity has been or will be obtained for any proposed substitutions prior to contract award; and
      
   2. Any necessary additional information regarding the SPI process identified in the proposal is obtained from the cognizant administrative contracting officer.
3. Any determination that an SPI process is not acceptable for a specific procurement shall be made at the head of the contracting activity or program executive officer level. This authority may not be delegated.

211.273-4 Contract clause. Use the clause at 252.211-7005, Substitutions for Military or Federal Specifications and Standards, in solicitations and contracts exceeding the micro-purchase threshold, when procuring previously developed items.

DFARS 252.211-7005 Substitutions for Military or Federal Specifications and Standards. As prescribed in 211.273-4, use the following clause:

SUBSTITUTIONS FOR MILITARY OR FEDERAL SPECIFICATIONS AND STANDARDS (AUG 1997)

1. Definition. "SPI process," as used in this clause, means a management or manufacturing process that has been accepted previously by the Department of Defense under the Single Process Initiative (SPI) for use in lieu of a specific military or Federal specification or standard. Under SPI, these processes are reviewed and accepted by a Management Council, which includes representatives from the Defense Contract Management Command, the Defense Contract Audit Agency, and the military departments.
   
   
2. Offerors are encouraged to propose SPI processes in lieu of military or Federal specifications and standards cited in the solicitation.
   
   
3. An offeror proposing to use an SPI process shall-
   
   1. Identify the specific military or Federal specification or standard for which the SPI process has been accepted, and the specific paragraph or other location in the solicitation where the military or Federal specification or standard is required;
      
      
   2. Provide a copy of the Department of Defense acceptance of the SPI process;
      
      
   3. Identify each facility at which the offeror proposes to use the specific SPI process; and
      
      
   4. Unless provided in response to paragraph (c)(2) of this clause, provide the name and telephone number of the cognizant Administrative Contracting Officer for each facility where the SPI process is proposed for use.
   
   
4. Absent a determination at the head of the contracting activity or program executive officer level that an SPI process is not acceptable for this procurement, the Contractor shall use the following SPI processes in lieu of military or Federal specifications and standards:

	Training Systems Division	Last Update: 26 June 2003