Attachment 23 - Section L (Updated 28-Dec-2020).pdf

ISC 2.0 Section L Amended 22 December 2020

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS OR RESPONDENTS

1.0. GENERAL

1.1. The Government intends to award an 18-year, single-award Indefinite Delivery Indefinite

Quantity (IDIQ) Integration Support Contract (ISC 2.0) to provide Systems Engineering and Integration (SE&I) services to the Intercontinental Ballistic Missile (ICBM) organizations at Hill Air Force Base (AFB). It is anticipated that five (5) individual Awardable Task Orders (ATOs) will be awarded with the basic contract. Performance requirements will be detailed in each ATO’s Performance Work Statement (PWS).

1.2. The main function of the ISC 2.0 is to support effective and responsive integration throughout the lifecycles of ICBM Weapon Systems (WSs) by providing knowledge, experience, and resources across a broad range of diverse professional disciplines and functional capabilities.

1.3. 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. The Government reserves the right to award this effort based on the initial proposal, as received, without discussion. Therefore, the Offeror’s initial proposal submission should contain the Offeror’s best terms from a price and technical standpoint.

1.4. Offerors are reminded that they 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 (SFs). Offerors are cautioned that any noncompliance with the terms and conditions of the Request for Proposal (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.

Offerors are further reminded that any outstanding/unmitigated OCI(s) (as defined in Basic PWS Para 4.13 and H-clause 001 [H-001]) at time of proposal submission may render proposals ineligible for award, and that outstanding/unmitigated OCI(s) at contract award will render proposals ineligible for award. OCI restrictions apply to all team members (Primes, Subcontractors, Joint Venture Members, etc.). See paragraph 7.5.11.1 of this document for further instructions.

1.5. Point of Contact:

The Procuring Contracting Officer (PCO) is the sole Point of Contact (POC) for this acquisition.

The Offeror shall address any questions, concerns or requests for clarification to Mr. Kyle Chase at afnwc.pzbc.isc2@us.af.mil (preferred) or:

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

1.6. Communications

1.6.1. Exchanges of Source Selection (SS) information between Government and Offerors will be controlled by the PCO. All inquiries must be submitted electronically or by 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 SS information via email, file suppression utilities (e.g. zip files, etc.) 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 SS Information (SSI) via encrypted email, contact the Buyer/PCO 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, SSI 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

Solicitation documents 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.

A Bidder’s Library is available on the DoD SAFE website (safe.apps.mil). Contact the PCO for access.

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 Federal Acquisition Regulation (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.

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 of this document, No Later Than (NLT) the date and time specified in Block 9, Section A of the SF 33 Solicitation.

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.3. Offerors are responsible for ensuring their delivery is on time. 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. Base closure due to exercises or police activity will not result in a waiver or delay of the proposal acceptance period. 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.4. 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 includes a hand receipt from the PCO or, if mailed, the delivery receipt from the carrier.

2.5. 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.6. 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.7. 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. The Offeror shall demonstrate how the capabilities will apply to ICBM WSs.

3.1.4. Offerors shall assume that the Government has no prior knowledge of the Offeror’s facilities and experience. The Government 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.1.6. For purposes of this proposal, “team” includes all partners, teammates, Joint Venture members, Subcontractors, universities, technical institutions, and any other similar entities, unless otherwise specified.

3.2. Volume Organization

3.2.1. The response shall consist of four (4) volumes:

Volume I - Factor 1: Technical Capability Volume II - Factor 2: Mission Capability Volume III - Factor 3: Cost/Price Volume IV - Contract Documentation

3.2.2. The Offeror shall prepare the proposal as set forth in Table 1, Proposal Organization, below. The titles and contents of the volumes shall be as defined in the table.

3.2.3. Each volume shall be marked with the RFP number, the Offeror’s name and address, and the number of the volume.

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

3.3. Page Limitations

3.3.1. All volumes shall be within the required page limits specified in Table 1.

3.3.2. 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.

3.3.3. Each page shall be counted except for the sections specified in Table 1 and the following: blank pages, title pages, tables of contents, lists of tables and drawings, cross-reference matrices, tabs, listing of abbreviations and acronyms, and glossaries.

3.3.4. 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.

Table 1: Proposal Organization

Volume Volume Title Page Limit

Paper Copies

Electronic Copies Description

I Factor 1: Technical Capability

65 2 (1 Original

1 Copy)

2 • Subfactor 1: Test Anomaly Root Cause o 20 pages max

• Subfactor 2: Systems Engineering o 20 pages max

• Subfactor 3: Digital Engineering o 25 pages max

II Factor 2: Mission Capability

70 2 (1 Original

1 Copy)

2 • Subfactor 1: Workforce Management o 20 pages max

(*Note: PECP will not apply against page count)

• Subfactor 2: Operational Capability o 20 pages max

• Subfactor 3: Transition Approach o 25 pages max

• Subfactor 4: Small Business Participation o 5 pages max

III Factor 3: Cost/Price N/A 0 3 *The cost volume shall be submitted in electronic format (CD/R-DVD/R) only.

IV Contract Documentation

N/A 1 2 • Executive Summary

• Request for Proposal

• Representations and Certifications

• Cross Reference Matrix

• GRIDS

• Other Information

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.

3.4.2. Page size shall be 8.5 x 11 inches, not including foldouts (see paragraph 3.4.7.).

3.4.3. Text shall be Times New Roman, 12 point font (text in tables shall be no smaller than 10 point font).

3.4.3.1. For charts, graphs, and figures, alternate fonts will be accepted, however text shall be legible and no smaller than 8-point.

3.4.4. Pages of text shall use the following formatting values:

3.4.4.1. Tracking and kerning values shall not be changed from the default values of the word processing or page layout software.

3.4.4.2. Line spacing shall be “Multiple”, set at 1.15 (default value of MS Word 2016)

3.4.4.3. Leading value (space between paragraphs) shall be 6 pt.

3.4.5. Use at least 1-inch margins on the top and bottom and ¾-inch side margins.

3.4.6. Pages shall be numbered within each volume.

3.4.7. “Foldout” pages

3.4.7.1. Legible tables, charts, graphs and figures shall be used wherever practical to depict organizations, systems and layout, implementation schedules, plans, etc.

3.4.7.2. These displays shall be uncomplicated, legible, and shall not exceed 11 by 17 inches in size.

3.4.7.3. Foldout pages shall fold entirely within the volume, and count as a single page.

3.4.7.4. Foldout pages may only be used for large tables, charts, graphs, figures diagrams, and schematics, not for pages of text.

3.4.8. Ensure all tables, foldouts, graphics, and figures in the electronic version of the proposal are searchable in the host program to the maximum extent practical.

3.4.9. These limitations and restrictions apply to electronic and hard copy proposals, and responses to ENs.

3.5. Cross-Referencing

3.5.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.

3.5.2. Information required for proposal evaluation which is not found in its designated volume will be assumed to have been omitted from the proposal.

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

3.10 below.

3.6. Indexing

3.6.1. Each volume shall contain a more detailed table of contents to delineate the subparagraphs within that volume.

3.6.2. Tab indexing shall be used to identify sections.

3.6.3. Tabs and tables of contents do not count against the page limits for the respective volumes.

3.7. Glossary of Abbreviations and Acronyms

3.7.1. Each volume shall contain a glossary of all abbreviations and acronyms used, and an explanation for each.

3.7.2. Glossaries do not count against the page limitations for the respective volumes.

3.8. Binding and Labeling

3.8.1. Each volume of the proposal shall be separately bound in a three-ring, loose-leaf binder permitting the volume to lie flat when open.

3.8.2. Staples shall not be used.

3.8.3. 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.

3.8.4. The same identifying data should be placed on the spine of each binder.

3.8.5. The original proposal shall be identified “Original”.

3.8.6. 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.8.7. Each page containing proprietary information shall be marked accordingly in the margin.

3.8.8. Each page shall contain the following legend in the margin at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104

FOR OFFICIAL USE ONLY

3.9. Electronic Offers

3.9.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.9.2. The Offeror shall submit all electronic copies using virus-free CD-/DVD-R. In no cases shall the Offeror use CD-/DVD-RW.

3.9.3. Each volume shall be on a separate disc. Each disc shall be properly labeled to indicate the volume number, title, solicitation identification, and the Offeror’s name.

3.9.4. 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.9.5. Use separate files to permit rapid location of all portions, including Subfactors, exhibits, annexes, and attachments, if any.

3.9.5.1. 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.

3.9.5.2. The file naming convention shall specify the appropriate volume.

3.9.5.3. If files are compressed, the necessary decompression program must be included.

3.9.6. The electronic copies of the proposal shall be submitted in Adobe Acrobat or MS

Excel (2016 or later), as applicable. Ensure all formulas used are included and accessible in Excel Spreadsheets.

3.10. Hyperlinks:

3.10.1. 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.

3.10.2. Any heading or sub-heading appearing in the Table of Contents shall be hyperlinked as described above.

3.10.3. Also, any reference within the body of the proposal volume that refers the reader to another location within the referring document shall be hyperlinked in the manner described above.

3.10.4. Hyperlinking references between different filenames is not necessary.

3.11. Cost or Pricing Related Data

3.11.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.11.2. All cost or pricing data shall be addressed only in the Cost/Price and Contract Documentation Volumes.

3.11.3. All cost data shall be readable and searchable in .XLSX format (MS-Excel 2016 or later) compatible format. Electronic cost/pricing submission shall be IAW section 6.0.

3.12. Classified Information

3.12.1. Classified information shall not be submitted as part of the proposal.

NOTE: A DD Form 254, Contract Security Classification Specification, Department of Defense is required for the performance of this contract.

4.0. VOLUME I - FACTOR 1: TECHNICAL CAPABILITY

The Technical Capability Factor focuses on the Offeror’s familiarity, corporate experience, and technical expertise in understanding and successfully performing selected services required by the ISC 2.0 Basic and ATO PWSs.

Factor 1 consists of three (3) Subfactors:

Subfactor One: Test Anomaly Root Cause Subfactor Two: Systems Engineering Subfactor Three: Digital Engineering

The offerors shall describe their proposed technical capability and approach, including their solutions and processes, to the situations and requirements given in the subfactors. The proposal shall provide enough detail to demonstrate the Offeror’s technical capability, experience or expertise, and understanding of ISC 2.0 requirements. The Technical Capability Volume shall be organized according to the following general outline:

Section Title Table of Contents 1 Subfactor One: Test Anomaly Root Cause 2 Subfactor Two: Systems Engineering 3 Subfactor Three: Digital Engineering Listing of Abbreviations and Acronyms (used within Technical Capability Volume)

4.1. Subfactor 1: Test Anomaly Root Cause

The Offeror shall describe the approach to determine the root cause of a test anomaly. (ATO1 PWS 9.5.13. and 9.5.14.)

Assume the following information: During a recent test launch, telemetry data for the Rocket Engine residual fuel post-mission was significantly lower than the model predicted, and the score for the reentry vehicle was outside acceptable limits. As integration support to the anomaly investigation, the ISC Contractor is tasked to determine the probable root cause for the anomaly.

The approach shall address:

4.1.1. Engineering analysis processes outlining the approach used for root cause determination (e.g. root cause analysis, data mining, information integration, describing Work Breakdown Structure interrelationships, etc.)

4.1.2. Digital engineering data processing and analysis tools used in the approach, and anticipated data deliverables

4.1.3. Management processes and resources required to support the system-of-systems root cause determination process, with accompanying rationale (e.g. estimated number and types of personnel, team structure, communications, stakeholder engagement etc.)

4.2. Subfactor 2: Systems Engineering (SE)

The Offeror shall describe the SE approach for defining technical requirements for an acquisition program. (Basic PWS 2.1.2; ATO4 PWS 3.3.1.1) Assume the following information: A new acquisition program has been initiated to replace the MMIII guidance computer. The ISC Contractor is tasked with defining the technical requirements for the acquisition.

The approach shall address:

4.2.1. SE processes used for technical requirements determination, definition, allocation, and traceability

4.2.2. Processes to ensure requirements are comprehensive (e.g. accuracy, Nuclear Hardness and Survivability [NH&S], reliability, availability, interface control, Nuclear Surety Certification, Configuration Management, Risk Management, training, technical data, testing, etc.)

4.2.3. Management processes and resources required to support SE processes for requirements definition, with accompanying rationale (e.g. estimated number and types of personnel, team structure, communications, stakeholder engagement etc.)

4.3. Subfactor 3: Digital Engineering

The Offeror shall describe a Digital Engineering approach that addresses use of digital engineering tools and processes to support a Government acquisition program. (ATO5 PWS 4.3.

and 4.6.) The intent of this Subfactor is to assess the Offeror’s Digital Engineering capability (e.g. processes, innovations, experience level, etc.).

The approach shall address:

4.3.1. Product Lifecycle Management of weapon system functional, allocated, and product baselines within an integrated Digital Engineering environment utilizing Siemens Teamcenter.

4.3.2. The development, support and use of Model-Based Systems Engineering (MBSE) architectures for both system design analysis and requirements traceability with allocation to the engineering baselines.

4.3.3. The use of Agile methodologies and Development, Security, and Operations (DevSecOps) processes (see “DoD Enterprise DevSecOps Reference Design Version 1.0”) to develop any capabilities or updates to the Digital Engineering environment, including but not limited to: updates to existing software applications and middleware and the creation of custom scripts and applications.

5.0. VOLUME II - FACTOR 2: MISSION CAPABILITY

The Mission Capability Factor focuses on the Offeror’s approach to effectively and efficiently accomplish the requirements of the contract, thereby demonstrating understanding of those requirements, and the risk of the proposed approach. Factor 2 consists of four (4) Subfactors:

Subfactor One: Workforce Management Subfactor Two: Operational Capability Subfactor Three: Transition Approach Subfactor Four: Small Business Participation

The Technical Volume shall be organized according to the following general outline:

Section Title Table of Contents 1 Subfactor One: Workforce Management 2 Subfactor Two: Operational Capability 3 Subfactor Three: Transition Approach 4 Subfactor Four: Small Business Participation Listing of Abbreviations and Acronyms (used within Mission Capability Volume) Attachment: Professional Employee Compensation Plan

5.1. Subfactor 1: Workforce Management

The Offeror shall describe the approach to provide and manage a qualified, stable workforce.

(Basic PWS 4.0) At a minimum, the approach shall address the following elements: Recruiting and Hiring

5.1.1.1. “High Demand/Low Density (HD/LD)” Labor Categories and Specialties HD/LD labor categories and specialties (as identified in Attachment 4) have limited labor pools, which makes recruiting and hiring fully qualified personnel challenging.

5.1.1.1.1. Explain the approach to successfully recruit and hire the mandatory quantities (contingent on funding availability) of HD/LD personnel IAW contractual timelines (see Basic PWS

4.7.4 and 5.0).

5.1.1.1.2. Explain the approach to ensure HD/LD personnel have the appropriate specialized skills/qualifications IAW Attachment 4, Labor Categories and Qualifications, and the Integration ATO PWS, prior to beginning work for the Government.

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

5.1.1.3. Explain the approach to efficiently on-board personnel (e.g. network access, background checks, clearances, badging, etc.).

5.1.2. 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.

5.1.2.1. Describe the approach for personnel growth/development, advancement/ promotion, and retention.

5.1.2.2. Describe the method to maintain technical performance and retain knowledge when employee turnover does occur.

5.1.2.3. The Offeror shall submit a Professional Employee Compensation Plan (PECP) meeting the requirements of FAR 52.222-46, Evaluation of Compensation for Professional Employees. The PECP shall be submitted as an attachment to Volume II Mission Capability.

5.1.2.3.1. The compensation plan shall include how compensation remains competitive when compared nationally and regionally, as well as other forms of compensation/ motivation that will be used to recruit and retain high quality employees.

5.1.2.3.2. The plan shall address proposed benefits, such as leave, health insurance, education, and other competitive benefits. It is required that salaries and fringe benefits be included in the labor rates provided in Volume III, Cost/Price. Rates/cost information shall not be included in the Mission Capability Volume.

The compensation plan pertains to the Offeror only. However, if a populated joint venture is formed (a joint venture in which the employees are employed by the joint venture itself and not by any individual joint venture partner), the joint venture must submit the employee compensation plan for the joint venture. If an unpopulated joint venture is formed, each individual joint venture partner must submit its own professional employee compensation plan.

5.1.3. Experience

5.1.3.1. The Offeror shall provide evidence of experience using the approach proposed for this Subfactor.

5.1.3.2. Evidence shall be from the team member proposed to fulfill the role/perform the process on ISC 2.0

5.1.3.3. Explain how the proposed approach led to successful accomplishment of requirements, and ensured a high level of quality and customer satisfaction.

5.1.3.4. Explain how the experience provides benefit to the Government for the ISC 2.0 effort.

5.2. Subfactor 2: Operational Capability

The Offeror shall describe the operational approach for providing the services and products delineated in the PWSs, through the following elements:

5.2.1. Corporate Structure (Basic PWS 2.0, 4.2, 6.3, 2.4.)

The Offeror shall describe the corporate structure of the organization/team proposed to provide sufficient management and governance to support Government requirements in the Basic and ATO PWSs.

The description shall include:

5.2.1.1. Corporate governance over this contract.

5.2.1.2. Connections/associations with corporations, division organizations, teammates, subcontractors, etc.

5.2.1.3. Internal and external lines of authority

5.2.1.4. How management and control policies will be implemented

5.2.1.5. Rationale for selecting each team member (i.e. how that firm adds value to the team)

5.2.1.6. Roles, responsibilities, and accountability of each team member

5.2.1.7. Level of local autonomy and authority, and the resulting impact on performance of the ISC. Address the following:

5.2.1.7.1. Autonomy and authority as it relates to day-to-day operations and processes (e.g. negotiation and signing of contract modifications, reassignment of work in response to varying workloads and priorities, recruitment and hiring of required personnel, managing labor relations interfaces, etc.)

5.2.1.7.2. Any decisions or approvals that will be made outside the local organization

5.2.1.8. How the proposed corporate structure will facilitate successful accomplishment of Government requirements in the Basic and ATO PWSs.

5.2.2. Operational Strategy (Basic PWS 3.2, 3.4, 4.2, 6.3, 6.4.)

The Offeror shall provide the strategy (e.g. concepts, plans, practices, internal procedures, tools, existing infrastructure, innovations, etc.) for conducting operations on ISC 2.0 efficiently and effectively.

The strategy shall address the following, at a minimum:

5.2.2.1. Approach for internal management reviews/status

5.2.2.2. Approach for communicating status to the Government and methods of providing Government visibility into the work

5.2.2.3. Approach to enhance customer satisfaction and service delivery

5.2.2.4. Approach for implementing continuous improvement

5.2.2.5. Approach to ensure timely delivery of high quality services and products

5.2.2.6. Approach for an integrated, effective, and efficient work process (e.g.

how work will be planned, directed, controlled, reported, reviewed, delivered, etc.)

5.2.2.6.1. Address when and how approvals to proceed are needed and from whom

5.2.2.6.2. Describe internal work/task flow

5.2.2.6.3. Explain the approach for technical oversight

5.2.2.7. Approach for handling issues (e.g. concerns, conflicts, priorities, dissenting opinions, etc.), both internally and in collaboration with the Government, including:

5.2.2.7.1. Early recognition of potential problems/problem areas

5.2.2.7.2. Proactive problem avoidance and solutions

5.2.2.8. How the proposed operational strategy will facilitate successful accomplishment of Government requirements in the Basic and ATO PWSs.

5.2.3. The Offeror shall explain how the corporate structure and operational strategy will complement each other and work together to ensure a high level of quality and customer satisfaction.

5.2.4. For any proposed innovations, the Offeror shall explain the efficiencies gained and the associated benefit to the Government.

5.2.5. Experience

5.2.5.1. The Offeror shall provide evidence of experience using the approach proposed for this Subfactor.

5.2.5.2. Evidence shall be from the team member proposed to fulfill the role/perform the process on ISC 2.0

5.2.5.3. Explain how the proposed approach led to successful accomplishment of requirements, and ensured a high level of quality and customer satisfaction.

5.2.5.4. Explain how the experience provides benefit to the Government for the ISC 2.0 effort.

5.3. Subfactor 3: Transition Approach (Basic PWS 5.0.)

The Offeror shall describe the approach (e.g. concepts, plans, practices, internal procedures, innovations, etc.) to seamlessly transition workload from ISC 1.0 with minimal impact and disruption, ensuring complete requirements coverage throughout the transition. (NOTE: A detailed Transition Plan [CDRL A132], will be delivered after contract award, IAW the instructions on the DD1423 and Basic PWS 5.1.3.)

For purposes of this contract, the following definitions apply:

The “Transition Period” consists of two (2) phases:

• The “Transition Preparation Phase” begins at completion of the Contract Kick-Off Meeting (see Basic PWS 6.2.) and ends at Government approval of the Transition Plan (see Basic PWS 5.1.3.).

• The “Transition Execution Phase” begins at Government approval of the Transition Plan and ends when the exit criteria are met.

The duration and exit criteria for the Transition Execution Phase from the Contractor’s proposal will be incorporated into the contract upon award.

At a minimum, the approach shall include:

5.3.1. Duration required for Transition Execution (not to exceed 90 calendar days from Government approval of CDRL A132, Transition Plan)

5.3.2. Exit Criteria for the Transition Execution Phase

5.3.3. Timeline of activities (e.g. hiring, anticipated fill-dates, facility provisioning and certification, clearances, infrastructure establishment events, etc.) leading to assumption of full responsibility by the proposed end of the Transition Execution Phase.

5.3.4. Identify what positions will be in place at the start of the contract, including their roles and alignment to the ATOs.

5.3.4.1. Identify what capabilities will be provided by the initial staff

5.3.4.2. Identify Security Clearance statuses of initial staff

5.3.5. Strategy for obtaining and certifying (if applicable) required facilities IAW the location and security requirements in the LQW and PWSs.

5.3.6. Processes for transition/transfer of knowledge (transitioning on-going work while ensuring continuity of operations) and data (including tools and models).

5.3.7. For any proposed innovations, the Offeror shall explain the efficiencies gained and the associated benefit to the Government.

5.3.8. Experience

5.3.8.1. The Offeror shall provide evidence of experience using the approach proposed for this Subfactor.

5.3.8.2. Evidence shall be from the team member proposed to fulfill the role/perform the process on ISC 2.0.

5.3.8.3. Explain how the proposed approach led to a timely, successful contract transition.

5.3.8.4. Explain how the experience provides benefit to the Government for the

ISC 2.0 effort.

5.4. Subfactor 4: Small Business (SB) Participation

The Small Business participation submission is not to be confused with the “Small Business Subcontracting Plan” required in the Contract Documentation Volume (see paragraph 7.5.10.

below)

5.4.1. The Offeror shall describe the SB participation approach to address the goals within H002, Small Business Participation.

5.4.2. Offerors shall discuss the rationale for any goal proposed that is less than the PCO’s recommended goal in any category.

5.4.3. The SB participation approach shall also include the extent to which such firms are specifically identified in proposals and the extent of commitment to use such firms.

6.0. VOLUME III – FACTOR 3: COST/PRICE

The purpose of this volume is to assist the Offeror in submitting other than certified cost or pricing data that is required to evaluate the reasonableness, balance, and realism as defined below (where identified). Compliance with these requirements is mandatory and failure to comply may result in rejection of the Offeror’s proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject the Offeror’s proposal.

Offers should be sufficiently detailed to demonstrate reasonableness. The burden of proof for credibility of proposed costs/prices rests with the Offeror.

The Cost/Price Volume shall be organized according to the following general outline:

Section Title Table of Contents 1 Labor Rate Matrix 2 Basis of Estimate 3 Subcontractor Costs 4 Estimating Methodology Listing of Abbreviations and Acronyms (used within the Cost/Price Volume)

6.1. General

6.1.1. Cost/Price Data: Data beyond that required by this instruction shall not be submitted, unless the Offeror considers it essential to document or support its cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

6.1.2. Cost or Pricing Data Requirements: IAW FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided IAW FAR 15.403-5, Instructions for Submission of Certified Cost or Pricing Data and Data other than Certified Cost or Pricing Data. If, after receipt of proposals, the PCO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1, Prohibition on Obtaining Certified Cost or Pricing Data (10 U.S.C. 2306a and 41 U.S.C. 254b) apply, the Offeror shall be required to submit additional cost or pricing data.

6.1.3. “Full Time”: For calculations, Offerors shall use 1,880 hours as the number of hours considered as full-time per year.

6.1.4. Rounding: All dollar amounts provided shall be rounded to the nearest dollar, except all loaded labor rates shall be rounded to the nearest penny.

6.1.5. Not Separately Priced

6.1.5.1. Facility costs will not be priced separately. Offerors shall account for facility costs in the rate structure.

6.1.5.2. Data deliverables/Contract Data Requirements Lists (CDRLs) will not be separately priced. Cost required to produce each CDRL shall be included in the Offeror’s proposed labor rate structure.

6.2. Labor Rate Matrix (LRM), Section J, Attachment 8:

6.2.1. Offerors shall appropriately populate the indicated pricing and cost cells specified in the LRM worksheets, IAW the instructions below and in the worksheets themselves.

6.2.2. The Offeror shall bid all ATOs, as if they were post-award tasks.

6.2.3. Total Evaluated Price (TEP) Worksheet

No Offeror input. The “TEP” worksheet will auto-populate from the Offeror’s inputs into the other worksheets. The TEP will be computed for evaluation purposes only and will not become part of the resulting contract.

TEP Formula:

[ATO 1: Period 1 + (ATO 1: Period 2) x (multiplier 1)] + [ATO 2: Period 1 + (ATO 2: Period 2) x (multiplier 2)] + [ATO 3: Period 1 + (ATO 3: Period 2) x (multiplier 3)] + [ATO 4: Period 1 + (ATO 4: Period 2) x (multiplier 4)] + [ATO 5: Period 1 + (ATO 5: Period 2) x (multiplier 5)] = TEP

Period 1 = Calendar Year (CY) 2021 through CY2022 $Dollars Period 2 = CY2023 through CY2026 $Dollars

(CY=Calendar Year)

6.2.4. Cost Element Summary

No Offeror input. The “CostElementSmy” worksheet will auto-populate from the ATO and Cost Elements worksheets.

6.2.5. ATO Summary

No Offeror input. The “ATOs-Smy” worksheet will auto-populate from the “ATO*” worksheets.

6.2.6. ATO Travel and Other Direct Costs (ODC)

No Offeror input. The Government will complete the “ATO-TravelODC” worksheet.

6.2.7. ATO Worksheets

No Offeror input. The “ATO *” worksheets will auto-populate from the “LRM- BaseRates”, LRM-AFPoolRates”, and Government-input ATO hours.

6.2.8. “LRM-FFPRates” Worksheet

6.2.8.1. The Offeror shall populate the “LRM-FFPRates” worksheet by providing the Prime’s fully burdened Labor Rates (to include all associated direct and indirect costs, and Profit) for all contract periods.

6.2.8.2. The Offeror shall submit one rate per labor category.

6.2.8.3. All Labor Categories on the worksheet shall be populated.

The rates on this worksheet will be incorporated into the resulting contract. The Government will use the rates on this worksheet to price FFP CLINs on future contractual modifications/awards.

6.2.9. “LRM-BaseRate” Worksheet No Offeror input. The “LRM-BaseRate” worksheet will auto-populate from the Cost Elements Worksheets (CEWs).

The rates on this worksheet will be incorporated into the resulting contract. The Government will use the rates on this worksheet as the base rates to price all contract types other than FFP CLINs on future contractual modifications/awards. Applicable incentives will be added to the base rate in this worksheet for cost incentive CLINs.

6.2.10. “LRM-AFPoolRates” Worksheet No Offeror input. The “LRM-AFPoolRates” worksheet will auto-populate from the CEWs and the Offeror’s Award Fee percentage input on the “Award Fee and Indirect Rates” worksheet. The Award Fee Pool is based on the fee-bearing elements (less Cost of Money (COM)) in the CEWs and the Award Fee percent.

The rates on this worksheet will be incorporated into the resulting contract. The Government will use the rates on the “LRM-AFPoolRates” worksheet to price all CPAF CLINs, both on the initial ATOs and on future contractual modifications/awards.

6.2.11. CEWs

6.2.11.1. Offerors shall populate the cells indicated on each of the CEWs:

• “Cost Elements-GFS” (Government Furnished Site)

• “Cost Elements-KFS-OnB” (Contractor Furnished Site - On Base)

• “Cost Elements-KFS-OffB” (Contractor Furnished Site - Off Base)

6.2.11.2. The Offeror shall provide the Prime’s fully burdened Labor Rates (to include all associated direct and indirect costs, except Profit/fee) for all contract periods.

6.2.11.3. The Offeror shall submit one rate per labor category.

6.2.11.4. All Labor Categories on each worksheet shall be populated.

6.2.12. “Award Fee and Indirect Rates” Worksheet

6.2.12.1. The Offeror shall populate the cells indicated on the “Award Fee and Indirect Rates” worksheet

6.2.12.2. The Offeror shall provide percentages for the indirect cost categories.

6.2.12.3. The Offeror shall propose an Award Fee pool percentage for use on all

Award Fee CLINs.

6.2.12.4. The Offeror shall not propose a base fee.

6.3. Labor Category Mapping Workbook

6.3.1. The Offeror shall populate the following data entry tables of the Excel Workbook within Attachment 9, Labor Category Mapping, with Contract labor categories mapped to proposed labor categories and number of CMEs and FTEs for the ATOs for each year:

• Offeror Labor Categories Entry

• Form Data Mapping Entry

6.4. Basis of Estimate (BOE)

6.4.1. The Offeror shall provide the basis of proposed direct and indirect labor rates, e.g.

actuals/current individual salaries, Forward Pricing Rate Agreement (FPRA), Forward Pricing Rate Proposal/Submission (FPRP/S), labor survey, etc.

6.4.2. The Offeror shall show base labor rate for each labor category, a breakout of all indirect rates applied, and fee. Explain how the rates factor into the build-up of the loaded labor rate. This shall be in accordance with your disclosure statement and accounting system. The offeror shall provide a basis for the indirect rates proposed .e.g. actuals, FPRA, FPRP/S, etc.

If an FRPA/FPRP/S was used, provide a copy of the applicable agreement/submission. If actuals were used, provide the previous three years of data. The offeror shall also provide audit agency contact information, to include telephone number(s). For the ordering periods that extend beyond the applicable agreed/proposed rates, utilize the final yearly rates of the agreed/proposed rates for the remaining periods of the contract.

6.5. Costs Associated with Transition

6.5.1. All costs associated with transition shall not be a separately priced CLIN, shall not be priced outside the calendar years 2021 and 2022 pricing, and are not included in the LQW. Offerors shall account for transition costs in the calendar years 2021 and 2022 rate structures.

6.6. Other Pricing Types

6.6.1. Cost Reimbursable No Fee (CRNF) CLINs (Travel/ODC) will not be included in the TEP but will be provided to the awardee and included in the ATOs after evaluations but prior to awarding any ATO.

6.6.2. Share ratios/ceilings/minimum-maximum and other incentive fee type arrangements for Fixed-Price Incentive Firm Target (FPIF) and Cost-Plus Incentive Fee (CPIF) arrangements will be negotiated at the time they are utilized after award.

6.7. Subcontractor Costs

6.7.1. The Offeror shall submit a list of the proposed subcontractors and interdivisional transfers showing (a) the supplier, (b) description of effort, (c) type of contract, (d) price and hours proposed by each, (e) price and hours included in prime’s proposal to the Government, (f) subcontract rates are sole-source or competitively proposed, and (g) commercial item / service determination support, if applicable. The Offeror shall conduct cost or price analyses of subcontracting costs in accordance with FAR 15.404-3 and include those results in the cost/price volume.

6.7.2. For purposes of the Cost/Price Volume only, a major subcontractor is defined as a subcontractor, other than the Offeror itself, that will perform ten (10) percent or more of contract scope based on labor hours or total labor cost.

6.7.3. In the event a subcontractor’s contract type is Cost, the subcontractor shall submit cost data at the same level of detail as required of the Offeror. The Government will review all major subcontractors and reserves the right to review and request additional data for any subcontractor.

If a subcontractor refuses to identify rates, costs, etc. to the prime contractor, then the subcontractor must provide under separate cover to the Government a detailed cost proposal in the same format and level of detail as prescribed for the prime Offeror.

6.7.4. The Offeror shall also submit one Section J, Attachment 9, Labor Category Mapping, for each major Subcontractor.

6.8. Estimating Methodology

6.8.1. Estimating System. The Offeror shall provide a summary description of its standard estimating system or methods. The summary description shall cover separately each major cost element. The Offeror shall identify any deviations from standard estimating procedures in preparing this proposal volume.

6.8.2. Accounting System. The Offeror shall identify any deviations from its standard accounting procedures in preparing this proposal.

6.8.3. Explanation of Estimating Methods Used. The Offeror shall explain the methodology used to estimate each cost element. The Offeror shall provide a description detailing each major cost element (e.g., Fringe, Overhead (O/H), General and Administrative (G&A), Material Handling, Facilities Capital Cost of Money (FCCOM), Labor, Other Direct Costs (ODC)) separately and the basis for each major cost element. The Offeror shall provide the basis of estimate for each expense used to compute the indirect rate buildup (Fringe, O/H, G&A, Material Handling, FCCOM). If a current forward pricing rate proposal, forward pricing rate recommendation, or forward pricing rate agreement exists, the Offeror shall provide a copy.

7.0. VOLUME IV - CONTRACT DOCUMENTATION

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file.

7.1. Executive Summary

The Executive Summary is not evaluated, scored, or used to clarify other discrepant information in other volumes. Do not include cost information in the Executive Summary. Any summary material presented here shall not be considered as meeting the requirements for any portions of other volumes of the proposal.

In the Executive Summary, the Offeror shall provide the following information:

7.1.1. Table of Contents - Include a master table of contents of the entire proposal.

7.1.2. Narrative Summary - The narrative summary of the entire proposal should be concise and highlight any key or unique features, excluding cost/price. The salient features should tie in with evaluation Factors/Subfactors.

7.2. Request for Proposal (RFP) contract/Representations and Certifications The Offeror's proposal shall include a signed copy of the RFP contract, and Sections A through K of the SF 33. This includes delivery of all applicable documents.

7.2.1. Section A - Solicitation/Contract Form

Complete Blocks 13 and 15, then sign and date Block 27 of the Standard Form (SF) 33, Solicitation/Contract. Signature by the Offeror on the SF 33 constitutes an offer, which the Government may accept. The "original" copy shall be clearly marked under separate cover and shall be provided without any punched holes.

7.2.2. Section B - Supplies or Services and Costs/Prices

No Offeror input required.

7.2.3. Section F - Deliveries or Performance

Proposed Performance Schedule: The Offeror shall not propose the performance schedule in Section F of the RFP contract. This information has been provided by the Government in the solicitation.

7.2.4. Section G - Contract Administrative Data

Section G of the RFP contract will include all fund sites and dollar amounts for the contract. The contractor is not required to fill in this information.

7.2.5. Section H - Special Contract Requirements

The Offeror shall comply with all special provisions/clauses shown under Section H of the RFP Basic contract. Basic contract terms and conditions apply to all task orders.

7.2.6. Section I - Contract Clauses

The Offeror shall comply with the clauses specified within Section I of the RFP contract.

Furthermore, any…