Attachment 5 - CyOFTS III Section L 23Apr25.pdf

SECTION L

INSTRUCTIONS TO OFFERORS

Cyber Operations Formal Training Support (CyOFTS) III

1.0 Program Structure and Objective

1.1.1. The mission of 39th Information Operations Squadron (IOS) and its partners is to provide Initial Qualification Training (IQT), USCYBERCOM 2000-level work role training, and advanced training for Total Force (TF) Airmen to plan and execute tasks requiring Cyber Operations (CO) and Information Operations (IO) capabilities. The course offerings currently include disciplines that span CO, IO, and Instructor Training courses.

1.1.2. The Government plans to award a single Indefinite Delivery/Indefinite Quantity (ID/IQ) contract as a result of this competitive 8(a) solicitation. Award will be made to the offeror that provides the best value to the Government in accordance with (IAW) Section M, Evaluation Factors for Award.

1.1.3. Budget/Funding Information.

Funding to be cited on individual task orders for each ordering period.

1.1.4. Contractor Technical Proposal.

All or parts of the Contractor’s Technical Proposal may be added to the contract. Should there be any discrepancies between the Technical Proposal and the Performance Work Statement (PWS), the PWS will take precedence unless otherwise approved by the Procuring Activity.

2.0 General Instructions

2.1.1. This section of the Instructions to Offerors (ITO) provides general guidance for preparing proposals as well as specific instructions on the format and content of the proposal. The Offeror’s proposal must include all data and information requested by the ITO and must be submitted IAW these instructions. Any Offeror who submits an incomplete proposal may be considered ineligible for award. The proposal shall be compliant with the requirements as stated in the PWS and appendices, Contract Data Requirements List (CDRL), and Request for Proposal (RFP).

Non-conformance with the instructions provided in the ITO may result in an unfavorable proposal evaluation, and/or ineligibility for award.

2.1.2. The proposal shall be clear, concise, and 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 but rather shall provide convincing rationale to address how the Offeror intends to meet these requirements. Offerors shall assume that the Government has no prior knowledge of their facilities and experience and will base its evaluation on the information presented in the Offeror’s proposal.

2.1.3. Elaborate brochures or documentation, detailed artwork, or other embellishments are unnecessary and are not desired.

2.1.4. Acceptance Period.

The proposal acceptance period must be for a period of no fewer than 365 calendar days after receipt of proposal. The Offeror shall make a clear statement in Volume IV, Section A of the proposal documentation volume that the proposal is valid for this amount of time.

2.1.5. IAW FAR Subpart 4.8 (Government Contract Files), the Government will retain a copy of all unsuccessful proposals.

2.2 General Information

2.2.1. Point of Contact.

The contracting officers (CO) are the sole points of contact for this acquisition. Address any questions or concerns you may have to the COs. Written requests for clarification may be sent to melissa.mitchell.7@us.af.mil and melissa.blair.2@us.af.mil.

2.2.2. Debriefings.

The CO will promptly notify offerors of any decision to exclude them from the competitive range, whereupon they may request and receive a debriefing in accordance with FAR 15.505.

Offerors excluded from the competitive range may request a pre-award debriefing or they may choose to wait until after the source selection decision to request a post-award debriefing.

However, offerors excluded from the competitive range are entitled to no more than one debriefing for each proposal. The CO will notify unsuccessful offerors in accordance with FAR

15.503. Upon such notification, unsuccessful offerors may request and receive a debriefing.

Offerors must make their request for a debriefing in accordance with the requirements of FAR

15.505 and 15.506, as applicable.

2.2.3. Discrepancies.

If an Offeror believes that the requirements in these instructions contain an error, omission, or are otherwise unsound, the Offeror shall immediately notify the CO in writing with supporting rationale as well as the remedies the Offeror is asking the CO to consider as related to the omission or error. The Offeror is reminded that the Government reserves the right to award this effort based on the initial proposal, as received, without discussions. By this reservation, the Government also reserves the right to allow no additional or substitute pages to the initial proposal.

2.2.4. Electronic Reference Documents.

All referenced documents for this solicitation are available on the System for Award Management (SAM) website at https://sam.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

2.2.5. Amendments to Solicitation.

If this RFP is amended, all terms and conditions that are not amended remain unchanged and in full force and effect. Offerors shall acknowledge receipt of any amendment and provide confirmation upon submission of the Offeror’s proposal. Any unacknowledged amendments in the Offeror’s proposal will render the proposal ineligible for award.

2.2.6. Submission, Modification, Revision, and Withdrawal of Proposal.

Electronic proposals are due no later than 20 June 2025. Proposal packages shall be transmitted mailto:melissa.mitchell.7@us.af.mil mailto:melissa.blair.2@us.af.mil https://sam.gov/ to the solicitation CO via DoD SAFE (https://safe.apps.mil/). Physical delivery of proposal packages will not be accepted. See ITO sections 2.5 and 2.6.

2.2.7. Communications.

Exchanges of source selection information between Government and Offerors will be controlled by the CO. E-mail (encrypted when possible or with password protected attachments) may be used to transmit such information to Offerors and shall include “Source Selection Information – See FAR 2.101 & 3.104” in the subject line.

2.2.8. Questions.

The Offeror shall notify the CO in writing with any questions regarding the requirements provided within the solicitation or regarding any corresponding document. The Government reserves the right to publish all questions and answers to https://sam.gov. The Government reserves the right to establish a deadline for all solicitation questions.

2.3. Organization/Number of Copies/Page Limits

2.3.1. The Title Page of each volume shall contain the solicitation number, name, address, and telephone of the Offeror and electronic e-mail address if available.

2.3.2. A Team List of the Offeror’s primary points of contact shall be submitted in each volume.

2.3.3. The Offeror shall prepare the proposal as set forth in the Proposal Organization Table (Table 1 below). The titles and contents of the proposal volumes shall be as defined in this table, all of which shall be within the required page limits and with the number of copies as specified in Table 1.

TABLE 1 – PROPOSAL ORGANIZATION

VOLUME

ITO

Paragraph Number

VOLUME TITLE ELECTRONIC

COPY

PAGE

LIMIT

I TECHNICAL 1 25

2.3.1 Title Page (Not included in the 25

page limit) 1

2.3.2 Team List (See Attach 2.0) 5

2.3.8 Table of Contents Unlimited

2.3.9 List of Tables and Figures Unlimited

2.3.10 Glossary of Abbreviations and

Acronyms Unlimited

2.4.2 Tables, Charts, Graphs and Figures Unlimited

3.1.2.1

3.1.2.2

Subfactor 1 – Facility Security Clearance

Subfactor 2 - Management Plan/Staffing Plan

*Included in page limit https://sam.gov.t/

Paragraph Number

VOLUME TITLE ELECTRONIC

COPY

PAGE

LIMIT

II PRESENT/PAST

PERFORMANCE 1 Unlimited

2.3.1 Title Page 1

2.3.2 Team List (See Attachment 2.0) 5

2.3.8 Table of Contents Unlimited

2.3.9 List of Tables and Figures Unlimited

2.3.10 Glossary of Abbreviations and

Acronyms Unlimited

4.1.2 Consent Letter (See Attach 1.4) Unlimited

4.1.3 Client Authorization Letter (See

Attach 1.5) Unlimited

4.1.4 Commitment to Perform as

Proposed Letter (See Attach 1.6) Unlimited

4.3.1 Past Performance Information

Forms (PPIF) (See Attach 1.1)

Request each PPIF not exceed a target of 8 pages

4.3.2 Relevant Contract Narrative

Request each contract narrative not exceed a target of 5 pages

4.3.4 Organization Structure Change

History Unlimited

III

PRICE 1

Unlimited (See Para

5.0)

2.3.1 Title Page 1

2.3.2 Team List (See Attachment 2.0) 5

2.3.8 Table of Contents Unlimited

2.3.9 List of Tables and Figures Unlimited

2.3.10 Glossary of Abbreviations and

Acronyms Unlimited

5.1.1 Price Reasonableness Unlimited

5.1.2 Completeness Unlimited

5.1.3 Unbalanced Pricing Unlimited

5.1.4 Price Realism (Limited to the TEP

and specific LCATS only) Unlimited

Paragraph Number

VOLUME TITLE ELECTRONIC

COPY

PAGE

LIMIT

5.1.7 CyOFTS III Pricing Matrix (RFP Attachment 4)

Limited to the tabs within the matrix

IV

CONTRACT DOCUMENTATION 1

(See Para

6.0)

2.3.1 Title Page 1

2.3.2 Team List (See Attachment 2.0) 5

2.3.8 Table of Contents Unlimited

2.3.9 List of Tables and Figures Unlimited

2.3.10 Glossary of Abbreviations and

Acronyms Unlimited

6.1.1 Solicitation/Contract Form and

Amendments

5.1.7

6.1.2 CyOFTS III Pricing Matrix (RFP

Attachment 4)

Limited to the tabs within the matrix

6.1.3 Contract Clauses Unlimited

6.1.4 OCI Mitigation Plan Unlimited

6.1.5 Joint Venture Agreements Unlimited

6.1.6 Representations and Certifications Unlimited

6.1.7 Exceptions to Solicitation

Requirements Unlimited

6.2.1 Authorized Offeror Personnel Unlimited

6.2.2 Government Offices Unlimited

6.2.3 Company/Division Address, Identifying Codes, & Applicable Designations

6.2.4 Estimating, Purchasing, and

Accounting Systems Unlimited

2.3.4 Names.

Offerors shall submit volumes with the following file names: Volume I – Technical.doc or .docx, Volume II – Past Performance.doc or .docx, Volume III – Price.doc or .docx with PricingMatrix.xlsx, and Volume IV – Contract.doc or docx. Files provided in .pdf format are also acceptable if conversion is made from a Word document or equivalent Word processing software while maintaining searchable text.

2.3.5. Page Limitations.

Page limitations shall be treated as maximums. If exceeded, the excess pages will not be considered in the evaluation of the proposal. Page limitations may also be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the letters forwarding the ENs to the offerors. Each page shall be counted except the following:

blank pages, title pages, tables of contents, tabs, indexes and glossaries.

2.3.6. Pricing Information.

The price volume shall not include information beyond that required by this instruction unless the Offeror considers it essential to document or support Offeror’s price position. All information relating to the proposed price, including all required supporting documentation must be included in this part or assumptions of the proposal. Under no circumstances shall this information and documentation be included in the Technical or Past Performance volumes.

2.3.7. Reserved.

2.3.8. Indexing.

Each volume shall contain a more detailed Table of Contents to delineate the subparagraphs within that volume. The tables of contents do not count against the page limitations for their respective volumes.

2.3.9. Tables and Figures.

Each volume shall contain a detailed list of tables and figures. The lists of tables and figures does not count against the page limitations for their respective volumes.

2.3.10. Glossary of Abbreviations and Acronyms.

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

2.4. Page Size and Format

2.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. Page line spacing shall be 1.5 lines. Except for the reproduced sections of the solicitation document, the text size shall be no less than 12 points Times New Roman, Courier, or Arial. 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. These page format restrictions shall apply to responses to evaluation notices (ENs).

2.4.2. Tables, Charts, Graphs and Figures

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 and shall not exceed 11 x 17 inches in size. When both sides of a sheet display printed material, it shall be counted as two pages. The following limitation only applies to the Technical Volume. Text intended for evaluation within all figures, charts, tables, and graphs, to include imbedded images, shall be no less than Arial 8 point. Any text within figures, charts, tables, and graphs which do not meet this requirement will not be considered in the evaluation.

2.5 Electronic Offers

2.5.1. All proposals shall be submitted using DoD SAFE, https://safe.apps.mil/. All interested Offerors must e-mail melissa.mitchell.7@us.af.mil and melissa.blair.2@us.af.mil in order to receive a request code to drop-off (upload) files in DoD SAFE. The government points of contact (GPOC) will send an e-mail to the Offeror acknowledging the request for a proposal drop-off code in DoD Safe. The GPOC e-mail acknowledging the request will not be sent to the Offeror after close of business hours, weekends, or on nationally observed holidays. If you do not receive an acknowledgement e-mail from the GPOC after 72 hours, you must send another e-mail. E-mails will not be returned after close of business hours, weekends, or on nationally observed holidays. After the e-mail request for a drop-off code has been sent from the Offeror and the Offeror has received the acknowledgment e-mail from either GPOC, the Offeror will then receive an e-mail from DoD SAFE to drop-off proposals and other requested documents. If the Offeror does not receive the e-mail from DoD SAFE, the Offeror will need to check SPAM and JUNK folders before requesting another drop-off code from the GPOC. The request for drop-off is only valid for 14 days. If the 14 days has expired and the RFP is still open, the Offeror may send another e-mail request for drop-off code to the GPOC e-mail addresses listed above.

2.5.2. Be advised that classified information is not allowed on DoD SAFE. Any files containing CUI/PII/PHI must be encrypted prior to uploading or by checking the “Encrypt every file” box.

The Offeror is allowed to drop-off one or more files (up to 8GB total). The Offeror may select the box ‘Send me an e-mail when each recipient picks up the files” for documentation purposes.

The GPOC will receive an automated e-mail containing the information the Offeror has entered and instructions for downloading the file(s). The GPOC will have 7 days to retrieve the files submitted in the drop-off. DoD SAFE does not guarantee delivery of documents within a specified time period under 4 hours.

2.5.3. All electronic documents and files submitted shall contain the volume number and title.

Use separate files to permit rapid location of all portions, including subfactors, required plans, exhibits, appendices, and attachments, if any. The Offeror shall submit volumes I through IV in electronic format. Each volume shall be submitted as a separate file. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office 365 Word, MS Office 365 Excel, MS Office 365 Power Point, and Adobe PDF Note: Files must be searchable and able to copy and paste. For amendment purposes to the proposal, the original proposal shall be clearly identified. Offerors are requested to provide pricing spreadsheets in Excel (.xlsx) format with no hidden formulas and not requiring a password, or with the password provided to the Government.

2.6. Distribution

2.6.1 Once the Offeror has uploaded the Offeror’s proposal in its entirety to DoD SAFE, the Offeror shall take a screen shot (Print Screen function) of the Offeror’s DoD SAFE upload confirmation screen showing all the uploaded files included in the proposal submission. The Offeror shall notify melissa.mitchell.7@us.af.mil and melissa.blair.2@us.af.mil by email that the files have been uploaded and provide a copy of the DoD SAFE completed upload confirmation screen shot. If the proposal files are uploaded in their entirety prior to the proposal closing date https://safe.apps.mil/ mailto:melissa.blair.2@us.af.mil mailto:melissa.blair.2@us.af.mil and time, and the Offeror has notified melissa.mitchell.7@us.af.mil and melissa.blair.2@us.af.mil the files have been uploaded (notification is to include the DoD SAFE upload confirmation screen shot has also been provided), the proposal will be considered timely, even if the files are not accessible to the CO in DoD SAFE until after the proposal closing date and time. If the Offeror does not notify melissa.mitchell.7@us.af.mil and melissa.blair.2@us.af.mil by email, the files will be considered timely if they are accessible in DoD SAFE prior to the closing date and time. However, they will be considered late proposals, if they are not accessible until after the proposal date and time if a notification email is not sent to the CO.

3.0 Factor 1, Technical, Volume I

3.1. General Instructions.

The Technical Volume should be specific and complete. Legibility, clarity, and coherence are very important. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions provided below, provide as specifically as possible the actual methodology you would use for accomplishing/satisfying these subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your firm will perform all the requirements specified in the solicitation. It is neither necessary nor desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

In the Technical Volume, address your proposed approach to meeting the minimum performance or capability requirements of each technical subfactor.

3.1.1. Volume Organization

The Technical Volume shall be organized according to Table 1.

3.1.2. Technical

The Offeror shall provide its proposed approach to meeting the performance or capability requirements of the technical subfactor that demonstrates an understanding and capability for executing the program. As a minimum, the approach shall provide the essential elements, as follows:

3.1.2.1. Subfactor 1 – Facility Security Clearance – Submit evidence of facility clearance for the Prime, Teaming Partners, or Joint Venture.

a) Top Secret (TS) /Sensitive Compartmentalized Information (SCI) and Special Access Program (SAP) Access Facility Clearance (FCL) is required. An Offeror without the requisite FCL will not be permitted as the prime contractor due to the required security classification. Offerors shall possess or acquire a FCL equal to the requirement on the DD Form 254, Contract Security Classification Specification (RFP Attachment 2) without additional authorization (i.e. National Interest Determination (NID) by the proposal due date. The Sensitive Compartmentalized Information (SCI) work will take place at a government facility. If an Offeror does not have the required FCL at the time of proposal submission, the proposal will not be further evaluated and is not eligible for award. However, if an offeror is a Joint Venture (JV), a Top Secret FCL is not required mailto:melissa.blair.2@us.af.mil mailto:melissa.blair.2@us.af.mil for the JV itself if the Offeror is an unpopulated JV and all members of the JV possess a Top Secret FCL. A JV without its own FCL will not have access to classified information and all access will solely be through the cleared JV members. Therefore, a JV without its own FCL is required to submit, as part of its proposal, a Security Plan/Standard Operating Procedure which, at a minimum, includes the following:

i. Identification of the JV member that will be responsible for implementing and managing all security program requirements;

ii. A description of the JV and JV members’ roles and responsibilities to ensure compliance with 32 CFR Part 117, NISPOM;

iii. A copy of the JV agreement(s) relating to the establishment of the JV and any subcontracts awarded to the individual JV members as they relate to this solicitation and all security responsibilities;

iv. A completed Standard Form 328, "Certificate Pertaining to Foreign Interests" for the JV;

v. Execute a formal exclusion resolution stating that the JV will not require and will not have access to classified information.

vi. The JV members and all subcontractors shall execute similar resolutions excluding the JV from access to classified information.

In addition to the above requirements, the Offeror shall also provide:

1) A self-certifying statement that the Offeror possesses at time of proposal submission the TS/(SCI) and SAP Access FCL as required for this acquisition. The self-certifying statement shall also include the Offeror’s name and applicable cage code.

2) A screenshot of the Offeror’s TS/(SCI) and SAP Access FCL from the National Industrial Security System (NISS), which is the system used by the Defense Counterintelligence and Security Agency (DCSA) to manage facility clearance information. The screenshot must be current and valid at the time of proposal submission.

NOTE 1: In the instance a proposing JV itself is an unpopulated JV, all proposing JV members will be required to possess the required facility clearance for this requirement in order for the proposing JV to meet prerequisite acceptability requirements for Subfactor 1. See Note 2 for additional details.

NOTE 2: Subfactor 1 is a prerequisite for the remainder of the Government’s evaluation to include Subfactor 2, Factor 2, Factor 3 and Contract Documentation. Offeror’s who fail to meet requirements for Subfactor 1 will not receive further evaluation of Subfactor 2, Factor 2, Factor 3 and Contract Documentation. See Section M paragraph 2.1.3 for full Evaluation Methodology details. The Government will not sponsor offerors for facility clearances.

3.1.2.2. Subfactor 2 - Management Plan/Staffing Plan

a. The offeror shall provide a Management Plan/Staffing Plan that explains how it will meet the requirements in the PWS and appendices. The approach shall meet the following criteria (do not include employee names or resumes):

i. An acceptable organizational structure to include a completed CyOFTS III Labor Matrix that provides certified personnel resources, including any subcontracting and teaming arrangements. The organizational structure shall adequately demonstrate the labor categories, position descriptions, security clearances, number of fully qualified positions available on day one and minimum acceptable qualifications necessary to meet the requirements identified in the PWS Table C.1.

ii. An acceptable methodology for recruiting, training, accession and retention of certified personnel, training, obtaining/maintaining personnel clearances, and certifications. Methodology adequately addresses continuity of service during personnel absences due to sickness, leave and vacancies, surge and emergencies such that the 39 IOS mission is not impacted. PWS 2.5.12, 7.5.1.7, 7.5.3.

iii. A transition phase-in approach that ensures continuity of services and a smooth effective transition has the ability to be fully staffed and ready to begin performance on the first day of the period of performance after the transition period is complete. PWS 2.12.2, 2.12.3 and 2.12.4.

4.0 Factor 2 – Past Performance, Volume II

4.1. General Information.

The Past Performance Volume shall be organized according to Table 1. Each Offeror shall submit a past performance volume with its proposal, containing past performance information in accordance with the format contained in Attachment 1.1 of the ITO. The Past Performance Volume shall include a team list, which includes the prime contractor, all significant subcontractors, teaming partners, and/or joint venture partners proposed to perform the work outlined in the solicitation. The Offeror shall describe the portion of effort each team member is proposed to perform in relation to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude and Complexity. The government Past Performance Evaluation Team (PPET) evaluates each member of the Offeror’s team for relevancy and performance quality, based on their proposed portion of effort. Therefore, it is important for the Offeror to provide a detailed portion of effort description, in order for the PPET to conduct an accurate assessment. Offerors shall also provide approximate percentages for portion of effort for each team member. For the Past Performance evaluation, the Government will use data provided by the Offeror in the Past Performance Volume, as well as data obtained from other sources.

4.1.2. Attachment 1.4 Consent Letter. This letter shall be executed and signed by each subcontractor, teaming partner, and/or joint venture partner. The letter authorizes the release of adverse past performance information to the Offeror so the Offeror can respond to such information.

4.1.3. Attachment 1.5 Client Authorization Letter. For each identified effort for a commercial customer, the Offeror shall submit a client authorization letter (Attachment 1.5) authorizing recipients to release information about the Offeror’s performance to the Government.

4.1.4. Attachment 1.6 Commitment to Perform as Proposed Letter. This letter shall be executed and signed by the prime contractor and each subcontractor. The letter states that, in the event a contract is awarded to the prime contractor, the prime contractor and subcontractor (to include teaming partners, and/or joint venture partners) commit to joint contract performance as described in the proposal. A separate letter shall be completed for each subcontractor separately.

If the signed commitment is not fully executed by both parties and provided with the Past Performance Volume, the subcontractor references will not be evaluated or considered.

4.2. Early Proposal Information

4.2.1 Each offeror is requested to submit the Past Performance Volume fifteen (15) calendar days prior to the solicitation closing date. The Past Performance Volume early proposal information is a request, and not a requirement. Failure to submit early proposal information will not result in offeror disqualification, nor will offerors be penalized.

4.2.2. As soon as practicable, offerors shall complete Section 1 of the attached Past Performance Questionnaire (Attachment 1.2) and e-mail it and the Performance Questionnaire Letter (Attachment 1.3) to all points of contacts (POCs) the Offeror has listed in the Past Performance Information Form (Attachment 1.1). The POCs will complete the questionnaires and forward them directly to the CO (Attn: Melissa Mitchell and Melissa Blair). E-mail addresses for questionnaires are melissa.mitchell.7@us.af.mil and melissa.blair.2@us.af.mil. RESPONDENTS

TO THE QUESTIONNAIRES SHALL NOT SEND THE COMPLETED INFORMATION

SHEETS BACK TO THE OFFEROR. Offerors shall not follow-up with respondents to ensure they have completed the questionnaires. The PPET will conduct such follow-up with any POC as necessary.

4.3. Relevant Contracts

4.3.1. The Offeror shall provide Past Performance Information (PPI) on current or previous contracts (or efforts). The PPI shall be completed in accordance with Section L ITO, Attachment 1.1, Past Performance Information Form (identified in this document as “PPIF”). The Offeror shall submit PPIFs for contracts which include all or some performance within the past three years, as defined in Section M, para 2.3.2.1 Recency Assessment. Request each offeror submit up to five (5) PPIFs for the prime contractor, and up to three (3) PPIFs for each significant subcontractor/teaming partner. Significant subcontractor is defined as a contractor who is proposed to perform over 5% of the total effort, or a contractor who is proposed to perform less than 5% of the total effort, but is determined to be performing a critical function. NOTE: The requested number of PPIFs for the prime and subcontractors are preferences and not requirements. Offerors may submit more than the preferred number if the Offeror believes the extra contracts are needed to fully describe their relevancy. Offerors who submit fewer than the preferred number of PPIFs are not automatically assigned a “Neutral Confidence” rating. Fewer numbers may be acceptable, if the Government determines there is sufficient information to determine a confidence rating. Request each PPIF not exceed a target of eight (8) pages, although more or fewer may be submitted, if necessary and relevant to the CyOFTS III Program.

4.3.2. PPI Relevant Contract Narrative

For each PPIF, the Offeror shall also provide a narrative explaining what aspects of the contract mailto:melissa.mitchell.7@us.af.mil are deemed relevant to the proposed effort, and to what aspects of the proposed effort they relate.

Specifically, the narrative should focus on similarities to the Factor 1 Technical subfactors, Factor 3 Price, and Scope, Magnitude, and Complexity, as defined in Section M, paragraph 2.3.2.2, and should be tailored to the proposed portion of effort. Categorize the relevant information into the specific technical subfactors and price assessment used to evaluate the proposal. The narrative may include a discussion of efforts accomplished by the Offeror to resolve problems encountered on prior contracts as well as past efforts to identify and manage program risk. Merely having problems does not automatically equate to a Limited or No Confidence rating, since the problems encountered may have been on a more complex program, or an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The Offeror shall clearly demonstrate management actions employed in overcoming problems and the effects of those actions, in terms of improvements achieved or problems rectified. This may allow the Offeror to be considered a higher confidence candidate.

For example, submittal of quality performance indicators or other management indicators that clearly support that an offeror has overcome past problems is required. The Offeror is requested to limit the narrative to a maximum of five (5) pages. However, the Offeror may exceed the requested page limit, if determined necessary to fully describe relevancy.

4.3.3. If subcontractor experience is submitted for consideration as part of the proposal, the offeror shall include a commitment signed by offeror and subcontractor certifying that if a contract is awarded resulting from the proposal, the parties commit to joint performance as proposed IAW Section L paragraph 4.1.4. If the signed commitment is not fully executed by both parties and provided with the Past Performance Volume, subcontractor references will not be evaluated or considered.

Affiliate companies, sister companies, teaming arrangements, joint venture agreement, etc., will be considered, provided that sufficient documentation is included in the proposal. The prime contractor must demonstrate that the affiliate will perform significant and critical aspects of the contract if awarded. Proposal documentation should include a copy of the signed arrangement such as documented affiliation, a copy of the teaming agreement, a copy of the joint venture agreement, etc. If the required information is not included in the proposal, the proposed affiliate companies, sister companies, joint venture companies, etc. shall not be evaluated or considered.

4.3.4. Organizational Structure Change History

Many companies have acquired, been acquired by, or otherwise merged with other companies and/or reorganized their divisions, business groups, subsidiary companies, etc. In many cases, these changes have taken place during the time of performance of relevant past efforts or between the conclusion of recent past efforts and this source selection. As a result, it is sometimes difficult to determine what past performance is relevant to this acquisition. To facilitate this relevancy determination, offeror’s shall include a "roadmap" describing all such changes in the organization of the offeror’s company. A pamphlet or other commercial document describing such reorganizations may suffice. As part of this explanation, show how these changes impact the relevance of any efforts you identify for past performance evaluation/performance confidence assessment. Since the Government intends to consider past performance information provided by other sources as well as that provided by the Offeror(s), the "roadmap" should be both specifically applicable to the efforts identified, yet general enough to apply to efforts on which the Government receives information from other sources.

5.0 Volume III – Price, Volume III

The Pricing Volume shall be organized according to Table 1.

Price or Pricing Related Data. The source selection will be conducted with the expectation of adequate price competition per FAR 15.403-1(c)(1)(i); therefore, certified cost and pricing data is not required. However, the offeror may be required to submit data other than certified cost or pricing data to the extent necessary for the CO to determine price reasonableness IAW one or more of the proposal analysis techniques described in FAR 15.404. If adequate competition is not achieved, an Offeror will be required to submit certified cost and pricing data IAW FAR 15.403-4 and 15.403-5 and submit a revised price proposal which complies with FAR 15.408 Table 15-2.

This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the Price Reasonableness, Completeness, Unbalanced Pricing, and Price Realism limited to the TEP and specific LCATs (identified in 5.1.4.1) of the Offeror’s proposed Price Volume. To aid in the Government’s understanding of the Offeror’s proposal, Offerors shall describe in a narrative format the methodology and basis used to support how the Offeror’s proposed price is reasonable, complete, balanced and realistic for the work to be performed IAW with the requirements stated in the RFP and PWS. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. The burden of proof rests solely on the offeror.

5.1 General Instructions.

5.1.1. Price Reasonableness: The Government will evaluate proposals for reasonableness.

Normally, price reasonableness is established through adequate price competition but may be determined through analysis techniques as described in FAR 15.404-1. The burden of proof for credibility of proposed costs/prices rests with the Offeror. The Offeror shall provide sufficient rationale describing how prices were developed (such as assumptions, historical data, projections, expertise, management decisions, etc.). A price is reasonable if, in its nature and amount, it does not exceed that which would be incurred by a prudent person in the conduct of competitive business. A determination of an unreasonably high Total Evaluated Price (TEP) may be grounds for eliminating a proposal from the competition. Analysis of proposals will be performed using one or more of the techniques defined in FAR 15.404-1 in order to determine reasonableness.

5.1.2. Completeness: The Government will evaluate proposals for completeness. A proposal is complete when all pricing data required under this solicitation, including any attachments, is provided in the format prescribed and the Offeror has complied with all pricing requirements of the solicitation. Noncompliance with the solicitation, unauthorized manipulation of the workbook, and exceptions/assumptions in the price volume may result in the proposed price being determined incomplete and ineligible for award. Offerors shall provide rationale if any proposed unit price or rate is entered as zero in the Pricing Matrix.

5.1.3. Unbalanced Pricing: The Government will evaluate proposals for unbalanced pricing.

Unbalanced pricing may increase performance risk and could result in payment of unreasonably high prices. Unbalanced pricing exists when, despite an acceptable total evaluated price, the price of one or more line-items is significantly over or understated as indicated by the application of price analysis techniques. The Government may also consider an offer unbalanced if there is a significant difference between proposed prices from year to year, including option years, such that they are above or below what would be considered a reasonable adjustment for inflation, or if the frontloading of costs is present. Refer to FAR 15.404-1(g) for risks associated with unbalanced pricing. An offer may be rejected if the CO determines that the lack of balanced pricing poses an unacceptable risk to the Government.

5.1.4. Price Realism: The Government will evaluate the proposed TEPs and direct labor base rates for specifically identified LCATs (see 5.1.4.1 below) of technically acceptable proposals for price realism to determine whether proposed prices are based on an adequate understanding of contract requirements and to ensure the proposed price does not pose an unacceptable risk to performance. No other labor category or price element will be evaluated for price realism other than those identified. The Offeror shall provide sufficient rationale describing how prices were developed. Examples of supporting data include national/regional compensation surveys, studies of professional, public, and private organizations, or another recognized compensation market data source (e.g., Watson & Wyatt, Economic Research Institute, Bureau of Labor Statistics, Salary.com, etc.) used to support the proposed compensation. The Offeror should also describe any judgmental factors applied, the mathematical or other methods used to estimate, and the nature and amount of any contingencies included in the proposed price and identified rates. All proposed prices shall be sufficient and adequately proposed to ensure performance is not at an unacceptable risk with prices proposed too low. For the purposes of comparability within this evaluation, the direct labor base rates proposed by all offerors should be the annual salary divided by 1872 hours.

Offeror’s will submit its TEP and the specified direct labor base rates according to the instructions in the Pricing Matrix (RFP Attachment 4). It is the Offeror’s responsibility to ensure the accuracy of calculations and formulas in the proposal.

5.1.4.1 LCAT Listing for Limited Realism Evaluation

The Government will perform a limited realism evaluation on the proposed direct labor base rates for the following LCATs:

DCO Cyber Instructor/Developer - Senior DCO Cyber Instructor/Developer - SME DCO Cyber Instructor/Developer (TS/SAP) – Senior OCO Cyber Instructor/Developer – Senior OCO Cyber Instructor/Developer - SME Tool Dev Cyber Instructor/Developer - Senior Tool Dev Cyber Instructor/Developer - SME DODIN Ops Cyber Instructor/Developer - Senior DODIN Ops Cyber Instructor/Developer – SME XCOMM Ops Cyber Instructor/Developer - Senior

XCOMM Ops Cyber Instructor/Developer - SME IO-Intel Instructor/Developer - Senior IO-Intel Instructor/Developer – SME Data Analytics Instructor/Developer - Senior Data Analytics Instructor/Developer - SME

For all other LCATs that are not included in the list depicted in paragraph 5.1.4.1, the Government will not perform any price realism evaluations.

5.1.5. Price Data: Information beyond that required by this instruction shall not be submitted unless you consider it essential to document or support your proposed price. All information relating to the proposed price, including all required supporting documentation shall be included in the section of the proposal designated as the Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal. Offerors should not assume that the Government will view price data in other volumes that should have been submitted in the Price Volume.

5.1.6. Solicitation Total Evaluated Price (TEP): The TEP will be calculated as described in Section M, paragraph 2.4.6 utilizing the Offeror’s completed CyOFTS III Pricing Matrix (Attachment 4.)

Offerors must ensure all required proposed pricing is provided. This effort includes 60-day transition period, a ten-month base period, four one-year ordering periods and a six-month extension period. The input spreadsheet in the Pricing Matrix automatically applies the order period 4 unit prices to the six-month extension unit prices. Pricing shall be provided for all periods of performance by CLIN. The Pricing Matrix will be used for all pricing. The TEP is for evaluation purposes only. The quantities provided in the Pricing Matrix do not obligate the Government to exercise options or guarantee such quantities during the contract period of performance.

For purposes of monthly invoicing and obligation tracking, the yearly totals for labor must be divisible by 12 and rounded to whole dollar totals. The burden of providing a mathematically accurate and complete pricing proposal using the format provided rests with each Offeror. At the sole discretion of the CO, mathematical errors identified may be corrected with the corrected pricing applied for evaluation purposes only. In cases where a proposed yearly total is not evenly divisible to months, the total will be downward adjusted to the nearest whole dollar amount that is divisible by 12. Proposals with corrected errors may be returned through an exchange for Offeror’s concurrence of the required revision.

5.1.7. CyOFTS III Pricing Matrix

5.1.7.1. The Government has developed a CyOFTS III Pricing Matrix (Attachment 4). The CyOFTS III Pricing Matrix shall be completed in accordance with Tab 1 Instructions of the Pricing Matrix. Offerors shall fill in all necessary information in the matrix as instructed.

The CyOFTS III Pricing Matrix shall be in Excel format and the spreadsheet shall be unlocked.

Offerors shall not alter any formulas in the CyOFTS III Pricing Matrix. If there is an error in any formula, please notify the CO immediately.

5.1.7.2. The Government may order additional FTEs and or surge FTEs, as needed. These will be funded at a task order level utilizing the same labor rates as the core FTEs for that ordering period when needed.

5.1.7.3. The Government has populated estimated prices for Travel, Contractor Acquired Property (CAP) and Other Direct Costs (ODC), based on historical market research and anticipated level of effort. Travel, CAP and ODCs will be established as Cost Reimbursable (CR) CLINs, with not to exceed ceilings, and therefore does not require evaluation. Travel, CAP and ODCs cells are locked and shall not be altered. Note: Profit is not allowable for Travel and ODCs.

5.1.7.4. For evaluation purposes only, the six-month, FAR 52.217-8, Extension of Services shall utilize Ordering Period 4 pricing based upon half the proposed total annual CLIN prices from Ordering Period 4. However, should the Government elect to exercise any part or all of the six-month Extension of Services during full performance, it will be calculated at the price in effect of the affected year.

6.0 Volume IV – Contract Documentation

6.1. Model Contract/Representations and Certifications

The purpose of this volume is to provide information to the Government for preparing the contract document and supporting file. The Offeror's proposal shall include a signed copy of the Model Contract.

6.1.1. Solicitation/Contract Form and Amendments

Completion of blocks 12, 17 and signature and date for blocks 30a, 30b and 30c of the SF33 Signature by the Offeror on the SF33 constitutes an offer, which the Government may accept.

The Offeror shall also provide a signed copy of all amendments issued by the Government IAW paragraph Section L paragraph 2.2.5 as part of the Contract Volume submission.

6.1.2. Supplies or Services and Cost/Prices

The Offeror shall provide a completed copy of the CyOFTS III Pricing Matrix utilized in the Pricing Volume within the Contracting Volume. The pricing provided in the CyOFTS III Pricing Matrix for the Contracting Volume copy must match those proposed in the Offeror’s CyOFTS III Pricing Matrix for the Price Volume.

6.1.3. Contract Clauses

The Offeror shall provide required information to complete clauses fill-ins as required.

6.1.4. Organizational Conflict of Interest (OCI) Mitigation Plan The Offeror shall submit an OCI Mitigation Plan, if an OCI issue is identified. The Offeror shall include, in Volume IV, the OCI Mitigation Plan IAW DAFFARS 5352.209-9000 and DAFFARS

5352.209-9001 which will become part of the contract upon award. The proposed OCI mitigation plan shall: 1) Describe in detail any actual or potential OCI of which the Offeror is aware of with the performance with its division, affiliates, and/or subcontractors under any contract the Offeror or any of its divisions/affiliates/subcontractors has been or may be awarded by any federal agency or any other entity whose performance may create an OCI if awarded this contract; 2) Describe in detail the methodology the Offeror used to identify those potential or actual OCIs described in paragraph 1); and 3) Describe in detail the specific techniques the Offeror intends to use to mitigate each identified potential or actual OCI.

6.1.5. Joint Venture Agreements

Per the Small Business Administration (SBA), Joint Ventures are allowable on small business set-asides. IAW 13 CFR 125.8 (d), “Prior to the performance of any contract set aside or reserved for small business by a joint venture between a protégé small business and a mentor authorized by § 125.9, the small business partner to the joint venture must submit a written certification to the contracting officer and SBA, signed by an authorized official of each partner to the joint venture." A copy of the Joint Venture agreement should be submitted within Volume

IV.

6.1.6. Representations, Certifications, and other Statements of Offerors.

The Offeror has completed the annual representations and certification electronically via the System for Award Management (SAM) website at https://www.sam.gov. The Offeror shall be eligible for award under the specified NAICS code, 611420 and as an 8(a) small business at the time of its proposal submission. After reviewing the SAM database information, the Offeror verifies by submission of this offer that the representation and certifications currently posted electronically are correct.

6.1.7. Exceptions to Solicitation Requirements.

Offerors are required to meet all solicitation requirements, such as terms and conditions, representations and certifications, and technical requirements, in addition to those identified as evaluation factors or subfactors. Failure to meet a requirement may result in an offer being ineligible for award. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. Each exception shall be specifically related to each paragraph and/or specific part of the solicitation to which the exception is taken.

Provide rationale in support of the exception and fully explain its impact, if any, on the performance, schedule, cost, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 3. Offerors are cautioned the Government could determine any identified exceptions to be unacceptable, which would make the proposal ineligible for award.

TABLE 3 – RFP EXCEPTIONS

RFP DOCUMENT PAGE/PARAGRAPH REQUIREMENT RATIONALE

PWS, ITO,

Evaluation Factor, etc.

Applicable Page and Paragraph Numbers

Identify the requirement to which exception is taken

Describe why the requirement can/will not be met

6.2. Other Information Required

6.2.1. Authorized Offeror Personnel.

Provide the name, title, and telephone number of the company/division POC regarding decisions made with respect to your proposal and who can obligate your company contractually. Also, identify those individuals authorized to negotiate with the Government.

6.2.2. Government Offices. Provide the mailing address, telephone and fax numbers and facility codes for the cognizant Contract Administration Office, DCAA, and Government Paying Office.

Also, provide the name and telephone and fax number for the Administrative Contracting Officer

(ACO).

6.2.3. Company/Division Address, Identifying Codes, and Applicable Designations. Provide company/division's street address, county and facility code; CAGE code; DUNS code; TIN; size of business (large or small); and labor surplus area designation. This same information must be provided if the work for this contract will be performed at any other location(s). List all locations where work is to be performed and indicate whether such facility is a division, affiliate, or subcontractor, and the percentage of work to be performed at each location.

6.2.4. Estimating, Purchasing, and Accounting Systems

Provide a summary description of your standard estimating, purchasing, and accounting systems. Identify any deviations from your standard estimating, purchasing, and accounting systems procedures in preparing this proposal volume. If no deviations have been made, then state accordingly. Indicate whether you have government approval of your estimating, purchasing, and accounting systems and if so, provide evidence of such approval.

ITO ATTACHMENTS

PAST PERFORMANCE PACKAGE ATTACHMENT

ITO…