ISC 2.0 Strategy Updates 9-Sept-20.pptx
PPTX presentation 368 KB Posted
- Attached to
- Integration Support Contract (ISC) 2. 0 Federal contract opportunity
- Solicitation number
- FA8207-20-ISC-2
About this file
This document provides an overview of strategy updates for the Integration Support Contract (ISC) 2.0 opportunity. The Air Force Nuclear Weapons Center is splitting the ICBM Systems Directorate into two new directorates, the MMIII Directorate and the GBSD Directorate. Task orders will support the sustainment, integration, and acquisition functions of the MMIII Directorate as well as the enterprise functions of the GBSD, MK21A, and Fuze programs. The document outlines the new structure of the directorates and divisions. It also describes changes to the task order structure, performance work statements, labor categories, and data deliverables. Transition activities will be split into two phases with an initial preparation phase and subsequent execution phase not to exceed 90 days. Organizational conflicts of interest will be addressed during the transition period for the prime contractor only. Updates to the source selection factors and criteria include new subfactors for technical capability based on technical processes to be defined later. Labor quantities in the new labor quantity workbooks will now be requirements rather than estimates.
View the file
Other files for this federal contract opportunity
Show all 50
Integration Support Contract (ISC) 2. 0 has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Integration Support Contract (ISC) 2.0 Information and Strategy Updates for Industry
8 Sept 2020 All information contained herein is subject to change
Never Doubted, Always Feared
AIR FORCE NUCLEAR WEAPONS CENTER
UNCLASSIFIED//FOUO
ICBM Organization at Hill AFB
– Directorate Split The ICBM Systems Directorate (NI) has officially split into two directorates:
MMIII Directorate (NM) GBSD Directorate (NX) Both Directorates report directly to AFNWC Both Directorates still located at Hill AFB
MMIII Directorate Operations Division (NMO)
Propulsion Branch (NMSP) Guidance Branch (NMSG) Ground Mechanical Branch (NMSM) Field Support Branch (NMSF)
Data Management Branch (NMED) Specialty Engineering Branch (NMES) Test and Assessment Branch (NMET)
ACAT-I & II Branch (NMAA) ACAT-III Branch (NMAB) Services Branch (NMAC)
FE Warren AFB OL (NMD) Technical Engineering Operating Locations Minot AFB OL (NMI) Vandenberg AFB OL (NMJ) Malmstrom AFB OL (NMM)
Information Technology Branch (NMOT) Security Branch (NMOS) Finance Branch (NMOF) Program Integration Branch (NMOP)
OPERATIONS DIVISION (NMO)
ICBM Infrastructure DIVISION (NMH)
SUSTAINMENT DIVISION (NMS)
ACQUISITION DIVISION (NMA)
Ground Electrical Branch (NMSE)
MMIII-to-GBSD Transition Program Mechanical Branch (NMHM) Electrical Branch (NMHE)
INTEGRATION DIVISION (NME)
Deputy SPM Chief Engineer Chief Financial Officer (CFO) Product Support Manager (PSM) Deputy Director Alternate Lead Dev Test Org (Alt-LDTO) Director/SPM Military Deputy Lead Project Office (LPO) (NMW) Contracting (PZB) Seven IPTs
PZB reports through AFNWC Chief of Contracting
RS/RV
Branch (NMSR)
AFLCMC SS
GBSD Directorate AVE Division (NXA) Guidance Branch (NXAG) Booster Branch (NXAB) Reentry System Branch (NXAR) Post Boost Branch (NXAP) Command and Launch Division (NXC) Launch Equipment Branch (NXCE) Physical Security Systems Branch (NXCP) SLP-A Branch (NXCS) Launch & Guidance Control Branch (NXCC) Infrastructure and Deployment Division (NXD) SE&I Division (NXE) Finance Division (NXF) Product Support Division (NXL) Deployment Branch (NXLD) Sustainment Branch (NXLS) Logistics Support Branch (NXLL) Material Support Branch (NXLP) Program Operations Division (NXO)
CAG (NXOD)
Security Branch (NXOS) Enterprise Services Branch (NXOH) Workforce Dev Branch (NXOW)
Program Execution Division (NXP) Program Integration Branch (NXPI) TMRR/EMD Execution Branch (NXPE) Ops Contract Manaement Branch (NXPO) Support Systems Division (NXS) Program & Test Facilities Branch (NXSP) Weapon Systems Facilities Branch (NXSW) Training Systems Branch (NXST) Support Equipment Branch (NXSE) Enterprise Combined Test Division (NXT) Software Division (NXW) Futures Division (NXX) MK21A Branch (NXXM) Fuze Branch (NXXF) Advanced Development Branch (NXXR) Capabilities Branch (NXXP) IT/Cyber Division (NXZ)
Task Order/PWS Structure
TO 2 – MMIII
Sustainment TO 5 – GBSD Enterprise
(GBSD, MK21A, FUZE)
Scheduling Alt-LDTO Specialty Engineering Test & Assessment TO 4 – MMIII Integration Engineering/ Technical Program Appendices Programmatic Data Management Ground Electrical Ground Mechanical ICBM Infrastructure and Equipment (IIE)
RS/RV
Field Support Guidance Propulsion TO 1 – MMIII Directorate Support Portfolio Management Transition IT/Cybersecurity Finance Engineering TO 3 – MMIII Acquisition (ACATs I-III) IT/Cyber Support Engineering/ Technical Support Security Support Acquisition/Pgm Mgmt Support Force Development Evaluation (FDE) Subject to change Lead Project Office
DEMIL
Pertinent areas from TO 1 added to support GBSD Directorate
PWSs and Attachments
EACH TASK ORDER PWS
Specific requirements/tasks TO-Specific List of Labor Categories (Additional, program/function-specific labor qualifications needed for the requirements in each TO are embedded into each TO’s PWS) TO-Specific Labor Quantity Workbook Labor categories and quantities required for the TO Location requirements Security Clearance requirements
BASIC PWS
Contract scope and overarching requirements Master GRIDS Contract Labor Matrix Contractual labor rates for each Labor Category Master list of CDRLs Master list of Labor Categories Definitions Qualifications Knowledge, Skills, and Abilities (KSAs) Examples of job duties TO-Specific List of CDRLs (See next slide for updated data deliverable strategy) TO-Specific GRIDS (See next slide for updated data deliverable strategy) Attachments:
Attachments:
Data Deliverables Basic PWS, new paragraph 3.12 “A master list of potential DoD Form 1423s (DD 1423s), Contract Data Requirements List, is provided as [Attachment #] of this document.
Due to the quantity and diversity of the programs in the ICBM Organization, the type and magnitude of required support is different for each program. Each program will employ the tasks in the PWSs to the extent needed by that program. This also means that data deliverable needs will vary based on the program. To this end, CDRLs are not referenced in the PWSs after every paragraph in which they may be required.
CDRLs specifically referenced in the PWSs are to be delivered every time the task required by the referenced paragraph is performed (e.g. monthly status reports, training materials, specialty engineering documentation, etc.).
If a program determines that a formal data deliverable is needed for a paragraph without a CDRL reference (e.g. advice, recommendations, analysis reports, etc.), the Government representative will select the appropriate CDRL from the master list and specify the delivery date/address and any other necessary instructions on the DD 1423. Any additional tailoring will also be documented on the DD 1423 at that time. The CDRL will then be incorporated into the associated task assignment (see paragraph 4.9 of this document).”
Rights for all data deliverables will be IAW the contract master GRIDS document
Transition Basic PWS, new paragraph 5.0:
“The ‘Transition Period’ will be split into two (2) phases.
The ‘Transition Preparation Phase’ begins at completion of the Contract Kick-Off Meeting (see paragraph 6.2 below) and ends at Government approval of the Transition Plan (see paragraph 5.1.3. and 5.1.4. below).
The ‘Transition Execution Phase’ begins at Government approval of the Transition Plan and ends when the agreed upon exit criteria are met. The date and exit criteria for the Transition Execution Phase from the Contractor’s proposal will be incorporated into the contract upon award.”
The NTE 90 day limitation applies to the Transition Execution Phase
The opportunity to resolve OCIs during the transition period applies to the Prime only. Any Subcontractor with an outstanding OCI (as defined in the H-clause) at time of proposal submission will render the associated Prime’s proposal ineligible for award.
Org Conflict of Interest (OCI)
Source Selection Factors
| Last Released (April 2020) | Updated Criteria | |
| Factor 1 | Technical Approach/Technical Risk | Technical Capability |
| Subfactor 1 | Program Management Approach | TBA |
| Subfactor 2 | Technical Expertise | TBA |
| Subfactor 3 | Transition | TBA |
| Subfactor 4 | Small Business | |
| Subfactor 5 | Sample Scenario | |
| Factor 2 | Cost/Price | Mission Capability |
| Subfactor 1 | Workforce Management | |
| Subfactor 2 | Operational Capability | |
| Subfactor 3 | Transition | |
| Subfactor 4 | Small Business | |
| Factor 3 | Cost/Price |
Order of importance Factors are listed in descending order of importance Per FAR 15.304(e), all evaluation factors other than Cost/Price, when combined, are significantly more important than Cost/Price.
Labor Quantity Workbook (LQW) (was “Suggested Labor Matrix Workbook”) Types and quantities of personnel in the LQW for each TO are now requirements, not estimates Offerors shall meet these requirements, i.e. provide the quantities of personnel listed in the LQWs (contingent on funding availability) Offerors will not propose alternate quantities Technical capability will be evaluated under the new Factor 1 There will be three Subfactors Subfactors will be based on technical processes The specific processes will be announced at a later date
Source Selection Technical Criteria image2.png image1.png image4.png
File details come from the government source that posted it. Updated .