ISC_2_L_Intro and Factor 1 - v2.0.docx

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1.0. GENERAL

1.1. The Government intends to award a single-award Indefinite Delivery Indefinite Quantity (IDIQ) contract for the Integration Support Contract (ISC) 2.0 in Fiscal Year 2021 for an 18 year period. The Government intends to award five individual task orders at the onset of this contract, as referenced in Table #, with performance requirements detailed in each task order Performance Work Statement (PWS). The main function of the ISC 2.0 is to support effective and responsive integration throughout the lifecycles of Intercontinental Ballistic Missile (ICBM) weapon systems by providing knowledge, experience, and resources across a broad range of diverse professional disciplines and functional capabilities.

1.2. The following Instructions to Offerors (ITO) cover the preparation and submittal of the offeror’s proposal for this solicitation. Offerors must follow the instructions contained herein. The offeror's proposal must include all data and information requested by this ITO and must be submitted in accordance with (IAW) these instructions.

1.3. Offerors are required to meet all solicitation requirements, including terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or Subfactors. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined to be unacceptable and therefore not considered eligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale.

1.4. The Government intends to award without discussions, therefore, each initial offer should contain the offeror’s best terms from a price and technical standpoint. However, the Government reserves the right to conduct discussions if it determines them necessary.

1.5. Point of Contact:

1.5.1. The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. The offeror shall address any questions, concerns or requests for clarification to Mr. Chris Thomas at afnwc.pzbc.isc2@us.af.mil (preferred) or:

Attention: Mr. Chris Thomas 6008 Wardleigh Rd Bldg 1580 Hill Air Force Base, UT 84056

1.6. Communications

1.6.1. Exchanges of source selection information between Government and Offerors will be controlled by the PCO. All inquiries must be submitted via e-mail or mail to the PCO. Questions, if appropriate as determined by the Government, will be answered as quickly as possible, during the proposal preparation period. When appropriate, answers to questions and concerns will be made available to all Offerors.

1.6.2. Email may be used to transmit such information only if the email can be sent encrypted, and must include “Source Selection Information – See FAR 2.101 and 3.104” in the subject line of the email. When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted. In order to facilitate the sending and receiving of encrypted emails, Offerors must use Microsoft (MS) Outlook email configured to support encryption or a different email product that is S/MIME compatible and configured to support encryption. If the Offeror intends to submit source selection information via encrypted email, contact the Buyer/Contracting Officer indicated on the face page of the solicitation prior to the first submittal in order to exchange certificates used for encryption.

1.6.3. If encrypted email is not available/feasible, source selection information will be transmitted via direct mail.

1.6.4. Initial proposals may not be submitted by email; the offeror may mail or hand deliver their submission to the PCO.

1.7. Discrepancies

If an offeror believes the requirements in these instructions contain an error, omission, or are otherwise unsound, the offeror shall immediately notify the PCO in writing with supporting rationale, as well as the remedies the offeror is asking the PCO to consider as related to the omission or error. When appropriate, Government responses will be provided to all Offerors.

1.8. Electronic Reference Documents

All referenced documents for this solicitation are available on the beta.sam.gov website. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

1.9. Amendments to Solicitation

If this RFP is amended, all terms and conditions that are not amended remain unchanged. If the RFP is amended prior to proposal delivery, Offerors shall acknowledge each amendment by signing and returning the front page of each amendment with the proposal submission. If the RFP is amended after proposal submission, Offerors shall respond by the date and time specified in the amendment to include a signed front page of the amended RFP.

1.10. Alternate Proposals

Offerors shall submit only one proposal for the ISC 2.0 as the Government will review only one proposal per offeror. Alternate proposals will not be considered.

1.11. Oral Presentations

Oral presentations will not be allowed.

1.12. Debriefings

1.12.1. Pre-Award - The PCO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing IAW FAR 15.505, Pre- Award Debriefing of Offerors. Offerors excluded from the competitive range may request a pre-award debriefing or, at the offeror’s request, this debriefing may be delayed until after award. However, offerors excluded from the competitive range are entitled to no more than one debriefing.

1.12.2. Post-Award - After award, the PCO will notify unsuccessful offerors in the competitive range of the source selection decision IAW FAR 15.506, Post-Award Debriefing of Offerors. Upon such notification, successful/unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request IAW the requirements of FAR 15.505 or 15.506, as applicable.

1.13. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission.

2.0. PROPOSAL SUBMISSION

2.1. Proposals (both paper and electronic copies) must be received by the PCO at the address in paragraph 1.5.1 of this document, no later than the date and time specified in Block 9, Section A of the SF 1447 Solicitation. Proposals received after the due date and time specified in the solicitation shall be handled IAW FAR 15.208, Submission, Modification, Revision, and Withdrawal of Proposals.

2.2. Submission of the initial proposal packages via electronic mail will not be accepted. Initial proposal packages shall either be mailed or hand-delivered. Delivery of initial proposals shall be coordinated at least 24 hours in advance of the due date/time with the PCO.

2.2.1. Offerors are cautioned that Hill Air Force Base has visitor control procedures requiring individuals not affiliated with the installation to obtain a visitor pass prior to entrance. Some delay should be anticipated when hand-delivering proposal packages. Offerors should allow for sufficient time to obtain a visitor pass and arrive at the specified office PRIOR to the time specified for receipt of proposals.

2.2.2. Offerors are responsible for ensuring their delivery is on time. Base closure due to exercises or police activity will not result in a waiver or delay of the proposal acceptance period.

2.3. The sealed package used to submit the proposal package must show the time and date specified for receipt. Acceptable evidence to establish the time of receipt at the specified location in paragraph 1.5.1 includes the time/date stamp of that installation on the proposal wrapper, other documentary evidence of receipt maintained by the installation, or oral testimony or statements of Government personnel.

2.4. The proposal acceptance period is specified in Section A of the solicitation. The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid for a minimum of 365 days from solicitation closing.

2.5. IAW FAR 4.8, Government Contract Files, the Government will retain one copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals

2.6. Proposals may be withdrawn by written notice received at any time before award. Proposals may also be withdrawn in person by an Offeror or an authorized representative, if the identity of the person requesting the withdrawal is established and the person signs a receipt for the proposal before award.

3.0. PROPOSAL PREPARATION INSTRUCTIONS

3.1. General Instructions

3.1.1. Proposals shall be in the English language and all monies shall be proposed in United States dollars.

3.1.2. The proposal must be complete, self-sufficient, and respond directly to the requirements of this solicitation. The proposal shall be clear, concise, and shall include sufficient detail for effective evaluation and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements.

3.1.3. The offeror’s proposal shall address how the offeror intends to meet the Government’s requirements and evidence of the effectiveness and ability to execute the proposed methodology. The proposed approach must clearly demonstrate the full capability and experience the offeror possesses for performing activities to meet contract requirements. Where supporting evidence of capabilities is based on systems other than Minuteman III (MMIII), the offeror shall clearly demonstrate how the capabilities will apply to MMIII and Ground Based Strategic Deterrent (GBSD).

3.1.4. Offerors shall assume that the Government has no prior knowledge of the offeror’s facilities and experience and will base its evaluation solely on the information presented in the offeror's proposal.

3.1.5. Elaborate brochures or documentation, binding, detailed art work, or other embellishments are unnecessary and are not desired.

3.2. Volume Organization

3.2.1. The response shall consist of 3 separate volumes:

Volume I - Factor 1: Management Approach Volume II - Factor 2: Cost/Price Proposal Volume III - Contract Documentation

3.2.2. The offeror shall prepare the proposal as set forth in the Proposal Organization Table below. The titles and contents of the volumes shall be as defined in this Table. Each volume shall be marked with the RFP number and the offeror’s name and address, and the number of the Volume.

3.2.3. All volumes shall be within the required page limits and with the number of copies as specified in the Table.

· Does not include Labor Matrix or Compensation Plan

· Subfactor 2: Program Management Approach - 40 pages

· Does not include Copies of Associated Contractor Agreements

· Subfactor 3: Sample Task - not included in overall page limit for Volume I

· Page limit for responses will be in the instructions accompanying the task

· Subfactor 4: Transition Approach - 5 pages

· Does not include GRIDS

· Labor Rate Matrix

· Awardable Task Order (ATO) 1 – ICBM Systems Directorate

· ATO 2 – MMIII Sustainment

· ATO 3 – MMIII Acquisition

· ATO 4 – MMIII Integration

· ATO 5 – GBSD Enterprise

1.0.

2.0.

3.0.

3.1. asdf

3.2. sdf

3.3. Page Limitations

3.3.1. Individual page limitations shall be treated as maximums. If exceeded, the excess pages will not be read nor considered in the evaluation of the proposal and (for paper copies) will be shredded. The above limitations apply to both electronic and paper copies of the proposal.

3.3.2. Each page shall be counted except for the sections specified in the table and the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, tabs, and glossaries.

3.3.3. If Evaluation Notices (ENs) are issued, page limitations may be placed on responses. The specified page limits for EN responses will be identified in the letters forwarded with the ENs to the Offerors.

3.4. Page Size and Format

3.4.1. A page is defined as each face of a sheet of paper containing information. When both sides of a sheet display printed material, it shall be counted as two pages. Page size shall be 8.5 x 11 inches, not including foldouts. Except for the reproduced sections of the solicitation document, the text shall be Times New Roman, 12 point font. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least 1-inch margins on the top and bottom and ¾-inch side margins. Pages shall be numbered sequentially by volume.

3.4.2. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size. Foldout pages shall fold entirely within the volume, and count as a single page. Foldout pages may only be used for large tables, charts, graphs, diagrams, and schematics, not for pages of text.

3.4.3. For charts, graphs, and figures, text shall be searchable in MS Word and/or PDF formats to the maximum extent practical. Ensure all tables, foldouts, graphics, and figures in the electronic version of the proposal are pasted into the proposal in a format that allows a word search by the host program (do not paste as pictures) to the maximum extent practical.

3.4.4. These limitations and restrictions shall apply to both electronic and hard copy proposals, and responses to ENs.

3.5. Cost or Pricing Related Data

3.5.1. The PCO has determined there is a high probability of adequate price competition for this acquisition. Upon examination of the offers, the PCO will review this determination and if, in the PCO's opinion, adequate price competition exists, no additional data will be requested and certification under FAR 15.406-2, Certificate of Current Cost or Pricing Data, will not be required. However, if at any time during this competition the PCO determines that adequate price competition no longer exists, offerors may be required to submit cost data to the extent necessary for the PCO to determine the reasonableness and affordability of the price.

3.5.2. All cost or pricing data shall be addressed only in the Cost/Price Proposal and Contract Documentation Volumes. Cost tradeoff information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or tradeoff decisions.

3.5.3. All cost data requested in Section 3.0 should be readable and searchable in .XLSX file format (MS-Excel 2016 or later) compatible format. All electronic cost/pricing data submission should be IAW paragraph #.

3.6. Classified Information

Classified information must not be submitted as part of the proposal. A DD Form 254, Contract Security Classification Specification, Department of Defense is required for the performance of this contract.

3.7. Cross-Referencing

3.7.1. Each volume shall be written on a stand-alone basis so that its contents may be evaluated without cross-referencing to other volumes of the proposal. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

3.7.2. Cross-referencing within a proposal volume is permitted where its use would conserve space without impairing clarity, but must be hyperlinked IAW paragraph #.

3.7.3. The offeror shall fill out Section J, Attachment #, Cross Reference Matrix, indicating relations between the ITO, proposal paragraph, PWSs, Contract Line Item Numbers (CLINs), and Contract Data Requirements Lists (CDRLs). The Cross Reference Matrix does not count towards the volume page limit.

3.8. Indexing

Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume. Tab indexing shall be used to identify sections. Tabs and tables of contents do not count against the page limits for the respective volumes.

3.9. Glossary of Abbreviations and Acronyms

Each volume shall contain a glossary of all abbreviations and acronyms used, and an explanation for each. Glossaries do not count against the page limitations for the respective volumes.

3.10. Binding and Labeling

3.10.1. Each volume of the proposal should be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open. Staples shall not be used. The outside of each binder shall include a cover sheet, clearly marked, identifying volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. The original proposal shall be identified “Original.”

3.10.2. Apply all appropriate markings, including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data, and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

3.10.3. Each page containing proprietary information should be so marked. Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

3.11. Electronic Offers

3.11.1. The content and page size of electronic copies must be identical to the hard copies. In the event there is a discrepancy between the hard copy and the electronic copy, the electronic copy will take precedence and will be used for evaluation.

3.11.2. The offeror shall submit all electronic copies using virus-free CD-/DVD-R. In no cases shall the offeror use CD-/DVD-RW. Each volume shall be on a separate disc. Each disk shall be properly labeled to indicate the volume number, title, solicitation identification, and the Offeror’s name. Apply all appropriate markings, including those prescribed IAW FAR 52.215-1(e), Restriction on Disclosure and Use of Data and FAR 3.104-4, Disclosure, Protection, and Marking of Contractor Bid or Proposal Information and Source Selection Information.

3.11.3. Use separate files to permit rapid location of all portions, including Subfactors, exhibits, annexes, and attachments, if any. When naming files, use titles to describe the content of the file rather than using numbers alone to more easily navigate and identify specific data. The file naming convention shall specify the appropriate volume. If files are compressed, the necessary decompression program must be included.

3.11.4. The electronic copies of the proposal shall be submitted in a format readable and searchable by MS Office Suite (2016 or later) and Adobe Acrobat, as applicable. Ensure all formulas used are included and accessible in Excel Spreadsheets.

3.11.5. Hyperlinks: Tables of Contents of all proposal volumes shall be hyperlinked to the corresponding material within each proposal volume such that clicking the mouse on an item in the Table of Contents will take the reader to the corresponding section within the body of the proposal volume. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above. Also, any reference within the body of the proposal volume that refers the reader to another location within the document shall be hyperlinked in the manner described above.

4.0. VOLUME I - FACTOR 1: MANAGEMENT APPROACH

The Management Approach Factor focuses on the Offeror’s approach to effectively and efficiently accomplish the requirements of this contract, thereby demonstrating understanding of those requirements, and the risk of the proposed approach. Factor 1 consists of 4 Subfactors:

Subfactor One: Personnel Management Approach Subfactor Two: Program Management Approach Subfactor Three: Sample Scenario Subfactor Four: Transition Approach

4.1. Subfactor 1: Personnel Management Approach

The Offeror shall fully describe the approach to provide a qualified, stable workforce who satisfy contract requirements. At a minimum, the approach shall address the following elements:

4.1.1. Labor Matrix

Complete the Labor Matrix in accordance with (IAW) the instructions provided (see Section J, Attachment #).

4.1.2. Recruiting and Hiring

4.1.2.1. Explain the approach to be used for timely recruiting and provisioning of required High Demand/Low Density (HD/LD) personnel to perform contract requirements.

4.1.2.2. Include processes the Offeror intends to perform to ensure successful, timely recruiting and hiring of qualified personnel.

4.1.3. Flexibility and Surge Support

4.1.3.1. Explain the approach to provide the workforce flexibility necessary to accommodate short- and long-term increases and decreases in the required level of support. For proposal purposes, assume sudden workforce change to be +/- 30% of each Task Order’s (TO’s) workforce.

4.1.3.2. The approach shall include:

4.1.3.2.1. Process/method for accommodating rapid increase or decrease in contract workforce due to start or cancellation of new program.

4.1.3.2.2. Process/method for meeting surge requirements.

4.1.3.2.3. Process/method for “pivoting” as priorities are adjusted within the ICBM System Directorate (ICBMSD).

4.1.3.2.4. Anticipated effects on management, subcontractor continuity, quality of services, and other factors resulting from changes in staffing levels.

4.1.4. Retention

Due to the length of this contract, the Offeror’s ability to maintain a workforce with the necessary technical expertise is imperative to the Government.

4.1.4.1. Describe policies/processes intended to attract and retain professional employees.

4.1.4.2. Describe how personnel, including Subject Matter Experts (SMEs), are grown, promoted and retained within the company.

4.1.4.3. Describe how expertise will be retained within the company as workforce knowledge is lost due retirement or general attrition.

4.1.4.4. Describe the method to maintain technical performance when employee turnover does occur.

4.1.5. Employee Compensation

Submit a Professional Employee Compensation Plan meeting the requirements of FAR 52.222-46, Evaluation of Compensation for Professional Employees.

4.1.6. Experience

4.1.6.1. Provide an example of experience demonstrating successful use of the proposed approaches/processes.

4.1.6.2. Explain any issues that occurred during the processes, how those issues were resolved, the impact to the program, and any resulting improvements/adjustments to the processes.

4.1.7. Risk Assessment

4.1.7.1. Provide an assessment of risks inherent in the proposed approach for Subfactor 1.

4.1.7.2. The risk assessment shall include clearly stated risks, explanation of why they are considered risks, mitigation plan(s), and techniques to eliminate or reduce the probability of occurrence and/or severity of consequences.

4.2. Subfactor 2: Program Management Approach

The Offeror shall fully describe the concepts, plans, practices, internal procedures, innovations, etc., to efficiently and proactively manage performance of this contract. At a minimum, the approach shall address the following elements:

4.2.1. Quality

4.2.1.1. Explain the approach to ensure services and products provided are fully compliant, timely, and responsive to requirements.

4.2.1.2. Explain the approach for aligning/realigning with ICBMSD priorities.

4.2.1.3. Explain the approach for enhancing customer satisfaction and delivery.

4.2.1.4. Explain the approach for implementing continuous improvement.

4.2.1.5. Explain the approach for technical oversight.

4.2.2. Organizational Structure

For purposes of this proposal, “team” includes all partners, teammates, subs, universities, technical institutions, and any other similar entities, unless otherwise specified.

4.2.2.1. Describe the proposed organizational/team structure. Description shall include:

4.2.2.1.1. Connections/associations with corporations, division orgs, teammates, major subs, etc.

4.2.2.1.2. Roles, responsibilities, and accountability of team members.

4.2.2.1.3. Estimated percentage of total work to be performed by each teammate.

4.2.2.1.4. Corporate governance over this contract.

4.2.2.1.5. Degree of local autonomy and authority.

4.2.2.2. Explain how the proposed structure facilitates the Offeror’s proposed general management approach for accomplishing requirements.

4.2.2.3. Provide a copy of all signed Associated Contractor Agreements (ACAs) or other agreements obtained from team members/ partners for this contract to show commitment to the program at a minimum for the base contract period.

4.2.2.4. Provide information on any informal agreements and a timeline for formalization.

4.2.3. Communication

4.2.3.1. Describe methods and processes for communications in relation to this contract, both internal and with the Government.

4.2.3.2. Explain the approach for management reviews/status updates.

4.2.3.3. Describe methods for providing the Government with visibility into contract work.

4.2.3.4. Describe internal and external lines of authority.

4.2.4. Issue Handling

4.2.4.1. Explain the approach for identifying, tracking, and resolving concerns, conflicts, priorities, and skill/workforce availability issues that arise during contract performance.

4.2.4.2. Describe the method for early recognition of potential problems/problem areas.

4.2.4.3. Describe the method for proactive problem solving and avoidance.

4.2.5. Work Processing

4.2.5.1. Explain the approach for integrated, effective, and efficient work processing, covering all phases from request through closure (e.g. receiving requirements/tasks, planning, developing, cost estimating, scheduling, processing, approving, implementing, tracking, controlling, directing, reporting, and timely closure).

4.2.5.2. Work processing shall use an electronic work processing system.

4.2.5.2.1. Provide a plan for ensuring the electronic system is ready and available at contract start.

4.2.5.2.2. Describe the content and delivery of any guides and training to be provided to Government users.

4.2.5.2.3. Explain how the system integrates with the steps of the work planning process.

4.2.5.2.4. Explain how the system integrates with the Offeror’s financial system(s).

4.2.5.2.5. Explain any security issues with the work planning system and provide proposed resolutions.

4.2.6. Cost Control

Provide the current status of the Prime’s, each teammate’s, and each major subcontractor’s business systems (accounting, estimating, compensation, property, timekeeping, and purchasing) indicating Government approval status, the date approval was given, the approval document (i.e. DCAA Audit or Letter No.), and the address of the responsible Government agency for each major subcontractor.

4.2.7. Experience

4.2.7.1. Provide an example of experience demonstrating successful use of the proposed approaches/processes.

4.2.7.2. Explain any issues that occurred during the processes, how those issues were resolved, the impact to the program, and any resulting improvements/adjustments to the processes.

4.2.8. Risk Assessment

4.2.8.1. Provide an assessment of risks inherent in the proposed approach for Subfactor 2.

4.2.8.2. The risk assessment shall include clearly stated risks, explanation of why they are considered risks, mitigation plan(s), and techniques to eliminate or reduce the probability of occurrence and/or severity of consequences.

4.3. Subfactor 3: Sample Scenario

The intent of the sample scenario is for the Offerors to demonstrate processes in a real-world scenario to aid the Government in determining the Offeror’s level of understanding of contract requirements.

4.3.1. The Offeror shall complete the sample scenario IAW Sample Scenario Instructions.

4.3.2. The scenario will include 2 stages and a separate response will be required for each. The first stage of the sample scenario will be released within # days after the Initial proposals are due to the Government. The time frame for release of the second stage of the sample scenario will be included in the instructions for the first stage.

4.3.3. The release of each stage of the sample scenario will include specific instructions and due dates for each response. Format, page count, and delivery method will be IAW paragraph # of this document. The 2 stages of the scenario will be evaluated IAW paragraph 4.0 of Section M.

4.4. Subfactor 4: Transition

4.4.1. Phase-in

The Offeror shall provide a transition approach that demonstrates the ability to seamlessly transition the workload from ISC 1.0 with minimal impact and disruption, ensuring complete requirements coverage throughout the transition. The approach shall include:

4.4.1.1. Time required (not to exceed # calendar days).

4.4.1.2. Comprehensive schedule of transition activities leading to assumption of full responsibility by the proposed completion date.

4.4.1.3. Description of Initial Operational Capability:

4.4.1.3.1. Identify the staffing structure proposed to be in place for each Task Order at the start of contract performance.

4.4.1.3.2. Demonstrate how the proposed structure will provide operational capability.

4.4.1.3.3. Provide the proposed incumbent capture rate for each skill type.

4.4.1.3.4. Provide a timeline demonstrating how the recruiting and hiring approach will facilitate the proposed initial staffing structure, with emphasis on those labor categories identified as HD/LD.

4.4.1.3.5. Identify ALL personnel vacancies anticipated at the start of contract performance and the anticipated fill date of such vacancies.

4.4.1.3.6. Identify impacts of HD/LD positions not filled timely and proposed mitigation plan.

4.4.1.4. Provide transition strategies for:

4.4.1.4.1. Networks.

4.4.1.4.2. Facilities.

4.4.1.4.3. Knowledge transfer (transitioning on-going work while ensuring continuity of operations).

4.4.1.4.4. Security Clearances.

4.4.1.4.5. Data.

4.4.1.4.6. Innovative approach(es) to streamline transition and minimize costs.

4.4.2. Transition/Phase-in Experience

4.4.2.1. Provide an example of experience demonstrating successful use of the proposed approaches/processes.

4.4.2.2. Explain any issues that occurred during the processes, how those issues were resolved, the impact to the program, and any resulting improvements/adjustments to the processes.

4.4.3. Enabling of Future Requirements

4.4.3.1. The Offeror shall provide a strategy enabling the Government to maintain full and open competition on future contracting actions, minimize life-cycle costs, and perform sustainment and acquisition for ICBMs.

4.4.3.2. To this end, the Offeror shall ensure that tables # through # of the Government Rights in Data and Software (GRIDS) for each awardable task order (Section J, Attachments #-#), are filled out completely and correctly IAW the instructions in the GRIDS document and IAW DFARS clauses 252.227-7013, Rights in Technical Data--Noncommercial Items, 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, 252.227-7015, Technical Data--Commercial Items, and 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions.

4.4.4. Risk Assessment

4.4.4.1. Provide an assessment of risks inherent in the proposed approach for Subfactor 4.

4.4.4.2. The risk assessment shall include clearly stated risks, explanation of why they are considered risks, mitigation plan(s), and techniques to eliminate or reduce the probability of occurrence and/or severity of consequences.