About this file

This is a request for information notice seeking input on draft request for proposal documents to maintain and sustain an existing management information system and develop new software applications for the Air Force Technical Applications Center. Services include maintaining reliability and security and keeping pace with technological advances. The proposed NAICS code is 541511. Responses are requested by November 6, 2020 and should identify the business, representative, CAGE code, and provide line-numbered comments on the draft documents. The work will take place at Patrick Air Force Base in Florida and the contractor's facility. An ombudsman contact is provided.

View the file

Other files

File Type Posted
Attachment 7 Rates_Hours_Indir.xlsx XLSX spreadsheet
Attachment 3 GFP.xlsx XLSX spreadsheet
Attachment 10 Total Evaluated Price.xlsx XLSX spreadsheet
Attachment 4 PPIS.docx DOCX document
Attachment 5 SubK_consent_letter.docx DOCX document
Attachment 11 MSS2 DD254 Draft.pdf PDF
Attachment 9 Other Direct Costs.xlsx XLSX spreadsheet
Attachment 8 Historical Labor Categories and Hours.png PNG image
Exhibit B - Scenario.docx DOCX document
Attachment 6 PP Questionnaire(1).docx DOCX document
Exhibit A - MSS2 CDRLs.pdf PDF
Attachment 2 GFE.docx DOCX document
DRAFT Solicitation FA702221R0001.pdf PDF
Show all 13

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Section L - Instructions, Conditions, and Notices to Offerors

L.1.0 Program Structure and Objectives

AFTAC provides national authorities with quality technical measurements to monitor nuclear treaty compliance and develops advanced proliferation monitoring technologies to preserve our nation’s security.

It is the sole organization in the federal government whose mission is to detect and report technical data from foreign nuclear explosions.

AFTAC uses automated information systems and software applications in the fulfillment of its mission.

Systems and software require maintenance and sustainment to ensure cybersecurity and reliability. In addition to maintenance and sustainment, software development is required to keep pace with newly identified areas of interest and technological advancements.

L.1.1 Budget/Funding Information

For consideration in developing proposals, the Mission System Support 2 (MSS2) acquisition strategy provides for award of a Cost-Plus-Fixed-Fee type contract with a base period of performance (twelve months) and four 12-month option periods. The Option to Extend Services under FAR 52.217-8 will also be included in any awarded contract.

Proposal Format

L.2.0 General Instructions

(a) The offeror's proposal must include all data and information requested by this ICNTO and must be submitted in accordance with these instructions. The offer shall be compliant with the requirements as stated in the Performance Work Statement (PWS), RFP Attachment 1, and the Contract Data Requirements Lists (CDRLs), Exhibit A. Non-conformance with the instructions provided in this ICNTO may result in an unfavorable proposal evaluation and may be grounds to eliminate the proposal from consideration for contract award. If a joint venture arrangement exists for this acquisition, the offeror shall provide a copy of the joint venture agreement that is signed and dated by all joint venture members as part of the proposal submission.

(b) Offerors shall submit only one proposal for the Mission Systems Support 2 effort as the Government will review only one proposal per offeror. Proposals must be received no later than the date and time specified in Block 9 on the face page of the RFP; however, offerors are requested to submit Volume III, Past Performance Information, so that it is received ten (10) calendar days prior to the required due date for proposals. Failure to submit Volume III by the earlier date will not result in offeror disqualification. See paragraph L.2.2.1. for submittal procedures.

(c) 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 but rather shall provide convincing rationale to address how the offeror intends to meet the stated 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.

Any reference to day(s) stated in the RFP, attachments and other contractual documents should be considered as calendar days unless specifically stated otherwise. Offerors are advised their proposals are presumed to represent their best efforts and most complete responses to this solicitation. Demonstration of capability and qualifications that clearly support the offeror’s claims are essential. The absence of such evidence will adversely influence evaluation of the proposal. Offers will be evaluated using the Factors and subfactors under Section M, Evaluation Factors for Award.

(d) Elaborate brochures or documentation, binding, detailed artwork, or other embellishments are unnecessary and are not desired.

(e) The proposal acceptance period is established at 360 days (see paragraph L.3.3.5.3). The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this period.

(f) In accordance with FAR Subpart 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.

(g) Questions regarding this solicitation are due by 18 December 2020. Questions and responses to questions will be posted to the beta.SAM.gov. Questions should be emailed to thomas.armstrong.11@us.af.mil.

L.2.1 General Information

L.2.1.1 Point of Contact. The Procuring Contracting Officer (PCO) is the sole point of contact for this acquisition. Address any questions or concerns you may have to the PCO. Written requests for clarification may be sent to the PCO at:

AMIC DET 2 OL/PKA (Patrick AFB FL) Attn: Mr. Thomas Armstrong Bldg 10989, 1020 South Patrick Drive Patrick Air Force Base, Florida 32925 Email: thomas.armstrong.11@us.af.mil Telephone: (321) 494-6537

L.2.1.2 Debriefings. The PCO 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, Pre-award Debriefing of Offerors. 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 PCO will notify unsuccessful offerors in the competitive range of the source selection decision in accordance with FAR 15.506, Post-award Debriefing of Offerors. Upon such notification, unsuccessful offerors may request and receive a debriefing. Offerors desiring a debriefing must make their request in accordance with the requirements of FAR 15.505 or 15.506, as applicable.

L.2.1.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 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.

Questions from prospective offerors must be submitted no later than 18 December 2020. Offerors must clearly identify any exception to the solicitation terms and conditions and provide complete accompanying rationale. The offeror is reminded that the government reserves the right to award this effort based on the initial proposal, as received, without discussion. This reservation includes matters of omission, errors, additional or substitute pages of the initial proposal. All questions in reference to this solicitation shall be submitted to the following email address:

thomas.armstrong.11@us.af.mil mailto:thomas.armstrong.11@us.af.mil

L.2.1.4 Electronic Reference Documents. All unclassified referenced documents for this solicitation are available on the beta.SAM.gov Data Bank website at https://beta.sam.gov/reports/opp/ . Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation. Additionally, an electronic classified Technical Library will be made available to offerors by point of contact listed in Block 10 on page 1 of the RFP during the proposal preparation period. To ensure all offerors have the same access to the technical library, offerors with the appropriate security clearance will be sent a classified CD for use in proposal preparation. The CD must be immediately returned upon completion of the MSS2 acquisition. The classified CD must be properly secured, wrapped, marked, and shipped via registered mail in compliance with DOD 5200.1-R and AFI 31-401 security guidelines. In order for the government to send the CD to the offeror, the Government will need a point of contact, their Social Security Number for Joint Personnel Adjudication System (JPAS) verification, company cage code and the classified registered mailing address. Do not send Personally Identifiable Information (PII) via unencrypted email.

L.2.1.5 Communications. Exchanges of source selection information after submission of the initial proposal packages between the Government and offerors will be controlled by the Contracting Officer. 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. In order to facilitate the sending and receiving of encrypted emails, offerors may use the Trusted End Node Security (TENS) Encryption Wizard or the DoD SAFE file transfer site [NOTE: These sites are for UNCLASSIFIED documents only]. When using DoD SAFE, offerors must first send an unencrypted email to the Contracting Officer, indicated on the face page of the solicitation, to request a DoD SAFE drop-off. When submitting source selection information via email, file suppression utilities, to include but not limited to zip files, will not be accepted.

L.2.1.6. Notice to Offerors. Notice to Offeror(s)/Supplier(s): Funds are not presently available for this effort. No award will be made under this solicitation until funds are available. The government reserves the right to cancel this solicitation, either before or after the closing date. In the event the government cancels this solicitation, the government has no obligation to reimburse an offeror for any costs.

L.2.1.7. Offer Retention. In accordance with FAR Subpart 4.8 (Government Contract Files), the Government will retain one (1) copy of all unsuccessful proposals. Unless the offeror requests otherwise, the Government will destroy extra copies of such unsuccessful proposals.

L.2.2 Organization/Number of Copies/Page Limits

L.2.2.1. Submittal instructions. To ensure timely and equitable evaluation of proposals, offerors must follow the instructions provided. Offerors are required to submit all documentation/information detailed herein, including terms and conditions, representations and certifications, and technical requirements. Failure to submit all required documentation/information may result in a proposal being ineligible for award. In submitting a proposal, offerors are agreeing to the terms and conditions as written in this Request for Proposal (RFP), as amended (if applicable).

Offerors shall submit paper (hard copy) and electronic copies as indicated in Table 2.2: Proposal Organization, below. If there are any discrepancies between the paper copies and the electronic copies of the proposal, the paper (hard copy) will be used for evaluation.

a. The hard-copy volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary and mailed to the PCO using the address in paragraph L.2.1.1.

b. Electronic proposals shall be submitted via encrypted email using the Trusted End Node Security (TENS) encryption program or the DoD SAFE file transfer site (see paragraph L.2.1.5. for further guidance). All pages of the electronic version shall be submitted in Adobe .pdf format unless otherwise indicated in the instructions found below.

about:blank

c. Facsimile (FAX) proposals will not be considered.

d. NO disks/DVDs/thumb drives/other electronic storage media may be submitted.

e. See paragraph L.2.2.3. for submittal of classified material.

The RFP response shall consist of five (5) separate volumes submitted in accordance with Table 2.2:

Proposal Organization. The titles and contents of the volumes shall be as defined in this table. The contents of each proposal volume are described in the ICNTO paragraph as noted in the table below:

Table 2.2 - Proposal Organization

VOLUME ICNTO

Paragraph

Number

VOLUME TITLE COPIES PAGE LIMIT

I L.3.0 Administrative Paper: Original and 1 copy Electronic: 1

Unlimited

II L.4.0 Technical/Technical Risk

Paper: Original and 2 copies Electronic: 1

30 pages

III L.5.0 Past Performance Paper: Original and 1 copy Electronic: 1 (Requested 10 days prior to proposal due date)

No more than 3 pages per reference

IV L.6.0 Cost/Price Paper: Original and 1 copy Electronic: 1

Unlimited

V L.7.0 Small Business Paper: Original and 1 copy Electronic: 1

Unlimited

L.2.2.1 Page Limitation. All material must be contained within the page limit identified for each volume or appendix. The page limitations specified in Table 2.2 above shall be treated as maximum limits to assist in the evaluation of each proposal. Total page count will be based on the printed proposal submission. Each page shall be counted toward the above page limits except for cover pages; tables of contents; tabs; resumes;

glossaries; list of key terms; appendices to technical volume such as tables, charts, graphs, and figures;

consent letters; and client authorization letters; company financial statements; and model contract. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Page limitations may be placed on responses to Evaluation Notices (ENs). The specified page limits for EN responses will be identified in the correspondence forwarding the ENs to the offerors.

L.2.2.1.1 Page Size and Format. These instructions shall apply to both electronic and paper copy proposals.

(a) Page size shall be 8.5 x 11 inches, not including foldouts. Tracking, kerning, and leading values shall not be changed from the default values of the word processing or page layout software. Use at least one-inch margins on the top, bottom and side margins. Pages shall be numbered sequentially by volume. These page format restrictions shall also apply to responses to ENs and Final Proposal Revisions (FPRs), if required.

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

(c) Double-sided printing is acceptable, but will count as two pages. Each printed side of foldout pages shall count as two pages each. The background color of each page of the proposal submission shall be white or ivory paper only. These page format restrictions apply to responses to ENs and FPRs.

(d) Text type shall be Times New Roman or Arial. Except for the reproduced sections of the solicitation document, the text size shall be no smaller than 12 point. Text lines will be no less than single-spaced. For tables, charts, graphs and figures, the text shall be no smaller than 10 point.

These limitations apply to both electronic and hard copy proposals.

(e) Each page should contain the following legend at the bottom of each sheet:

SOURCE SELECTION INFORMATION--SEE FAR 2.101 and 3.104 FOR OFFICIAL USE ONLY

L.2.2.2 Cost/Price Related Data. The contracting officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers if, in the contracting officer's opinion, adequate price competition exists, no additional data will be requested and certification under FAR 15.406-2 will not be required. If, at any time during this competition, the contracting officer determines that adequate price competition no longer exists, offerors may be required to submit cost/price data to the extent necessary for the contracting officer to determine the fairness, reasonableness and realism of the cost/price. The offeror may be required to provide a Certificate of Current Cost or Pricing Data in accordance with FAR 15.403-4 and 15.403-5 and submit a revised cost/price proposal which complies with FAR 15.408 Table 15-2.

L.2.2.3 Classified Information. Where classified information is required in your response, it shall be provided in hard copy only (no electronic copies) as a classified supplement and bound in a single classified addendum to the appropriate proposal volume. If a classified supplement is used, each entry in the classified addendum shall be referenced to the proposal volume, page number, and paragraph number to which it applies. Similarly, a reference shall be placed in the unclassified volume where the classified insert applies, giving the page and paragraph numbers within the addendum where it can be found. Binding shall conform to the same directions as those given in this ICNTO for unclassified portions. The classified addendum shall be separately bound with an applicable security designation color cover, conforming to DoDM 5200.01-V2, Pages in a classified addendum will be included in the page count for the applicable volume.

The classified addendum shall be submitted according with DOD 5220.22-M National Industrial Security Program Operating Manual, also the company must provide CAGE Code which can be verified using the Industrial Security Facilities Database (ISFD). Classified information will be clearly marked and shipped in accordance with DOD 5220.22-M and AFI 31-401 to this address:

“Outer Address”

DEPARTMENT OF THE AIR FORCE

AFTAC/SO

Bldg. 10989 1020 South Patrick Drive Patrick AFB, FL 32925-3002

“Inner Address”

DEPARTMENT OF THE AIR FORCE

AMIC Det 2 OL/PKA ATTN: Mr. Thomas Armstrong Bldg 10989 1020 South Patrick Drive Patrick AFB, FL 32925-3002

L.2.2.4 Cross-Referencing. To the greatest extent possible, each volume shall be written on a stand-alone basis so that its contents may be evaluated with a minimum of cross-referencing to other volumes of the proposal. Information required for proposal evaluation, which is not found in its designated volume, will be assumed to have been omitted from the proposal. Cross-referencing within a proposal volume is permitted where its use would conserve space and/or improve clarity.

L.2.2.5 Indexing. Each volume shall contain a detailed table of contents to delineate the subparagraphs within that volume. Paper copies shall use tab indexing to identify sections. Neither the table nor tabs will count towards the page count.

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

L.2.2.7 Binding and Labeling. Each hard-copy volume of the proposal should be separately bound in a three-ring, loose leaf binder permitting the volume to lie flat when open. Staples shall not be used. A cover sheet should be bound in each book, clearly marked as to volume number, title, copy number, solicitation identification, and the offeror's name. The same identifying data should be placed on the spine of each binder. Elaborate format and binding are neither necessary nor desirable. All unclassified document binders shall have a color other than red or other applicable security designation colors. Be sure to apply all appropriate markings including those prescribed in accordance with 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 on both the paper and electronic copies.

L.2.3 Reserved.

L.2.4 Distribution.

L.2.4.1 Submit your proposal to arrive no later than time and date stated on the first page of the solicitation.

The "original" proposal shall be identified. Proposals shall be addressed to the PCO and mailed or hand-carried to (for classified portions use paragraph L.2.2.3 for mailing.):

DEPARTMENT OF THE AIR FORCE

AMIC Det 2 OL/PKA ATTN: Mr. Thomas Armstrong Bldg. 10989 1020 South Patrick Drive Patrick AFB, FL 32925-3002

L.2.4.2 All proposals delivered in response to this solicitation shall reflect the following information on the address label:

(a) Solicitation Number: FA702221R0001

(b) Legend, “TO BE DELIVERED UNOPENED TO THE PROCURING CONTRACTING

OFFICER”

(c) Volume and copy numbers contained in each box.

IMPORTANT NOTICE: PAGES OR SECTIONS, WHICH DO NOT MEET THE FORMAT

REQUIREMENTS TO INCLUDE FONT SIZE, MAY NOT BE EVALUATED.

PROPOSAL CONTENT

L.3.0 Volume I – Administrative

L.3.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 offer, reflecting the most recent amendment (if amended) and Sections A through K. The "original" copy should be clearly marked under separate cover and should be provided without any punched holes. Offerors shall ensure that all clauses and provisions that require “fill in” information are appropriately completed, including the proposed prices associated with the contract line items in the Schedule (Section B) of the RFP. This includes:

L.3.1.1 Section A – Solicitation/Contract Form (as amended, if applicable). Complete blocks 13 through 18 of the SF 33. In doing so, the offeror accedes to the contract terms and conditions as written in the RFP Sections A through K, which constitute the model contract. Note: An official having the authority to bind the offeror contractually must sign the SF 33. One copy of the SF 33 must bear an original signature.

L.3.1.2 Section B – Schedule of Supplies or Service and Prices. Complete pricing information in Section B of the model contract. Use the government-provided dollar values for CLINs X004 and X005 (ODCs):

CLIN X006, Data Deliverables will be Not-Separately-Priced (NSP).

L.3.1.3 Section F – Deliveries or Performance. Acknowledge content of Section F.

L.3.1.4 Section G - Contract Administrative Data. Provide any ‘fill-in’ information required in Contractor’s Contract Administration, in Section G. If not applicable, state so.

L.3.1.5 Section H – Special Contract Requirements. Acknowledge and address content of Section H as applicable.

L.3.1.6 Section I – Contract Clauses. Complete ‘fill-ins’ as applicable.

L.3.1.7 Section K - Representations, Certifications, and other Statements of Offerors.

Complete representations, certifications, acknowledgments, and statements. (Note: Offerors must also comply with the System for Award Management (SAM) requirements of FAR 52.204-8)

L.3.2 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. Offerors are cautioned that any noncompliance with the terms and conditions of the RFP may cause their proposal to be determined not eligible 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 a solicitation 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, price, and specific requirements of the solicitation. This information shall be provided in the format and content of Table 3.2 below:

Table 3.2 - Solicitation Exceptions

Solicitation Document

Page/ Paragraph

Requirement/ Portion Rationale

SOO, SOW, SPEC,

Model Contract, ICNTO, etc.

Applicable Page and Paragraph Numbers

Identify the requirement or portion to which exception is taken

Describe why the requirement can/will not be met

L.3.3 Other Information Required

L.3.3.1 Company/Division Address, Identifying Codes, and Applicable Designations.

Provide company/division's street address, county, state and facility code; CAGE code; DUNS number;

TIN; size of business (large or small); and labor surplus area designation. 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.

L.3.3.2 Subcontractors/Partners.

Provide company/division's street address, county, state and facility code; CAGE code; DUNS number;

TIN; size of business (large or small); and labor surplus area designation for joint venture partners and intended major subcontractors. Major subcontractors are those proposed to perform 10 percent or more of the effort based on the total proposed price OR perform aspects of the effort the offeror considers critical to overall successful performance. Provide copies (redacted as necessary) of any firm agreements or contracts between business entities.

L.3.3.3 Authorized Offeror Personnel.

Provide the name, title, email address and telephone number of the company/division point of contact 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.

L.3.3.4 Government Offices.

Provide the mailing address, telephone; fax number, e-mail address, and facility codes for the cognizant Contract Administration Office (ACO), DCMA, DCAA, and government paying office for the prime contractor and major subcontractors. A joint venture is considered the same as a prime contractor.

L.3.3.5 Attachments to the Model Contract. The offeror shall provide the following as attachments to the model contract:

L.3.3.5.1 Government Furnished Equipment (GFE), Government Furnished Property (GFP) and/or Base Support Requirements.

The need for GFE is anticipated. A list of planned GFE is provided as Attachment 2.

Offeror GFP and/or base support requirements are to be listed in Attachment 3. Required fields are marked with an asterisk (*). The offeror shall also provide the written authorization from the cognizant ACO, as applicable.

L.3.3.5.2 Associated Contractor Agreements (ACAs). Include Associated Contractor Agreements, if applicable.

L.3.3.5.3 Proposal Validity. Block 12 of the SF33 is hereby superseded with the following proposal Acceptance terms: Offeror's proposal is valid for a period not less than 360 days from the date of receipt of proposal.

L.3.3.5.4 Clearances. Provide documentation of current DIA-approved facility clearance and key personnel clearances in place. Joint ventures must have a DIA-approved facility clearance specific to the joint venture entity.

L.3.3.5.5 Organizational Financial Information. Submit copies of the latest available financial statement covering the organization(s) which will perform the contract. Include any information, which may have a bearing on your ability to handle the financial management of the contract. If proposing as a joint venture, provide financial statements for each joint venture partner.

L.4.0 Volume II – Technical (Factors 1 and 2)

L.4.1 General

L.4.1.1 The Technical Volume must be specific and complete. Legibility, clarity, and coherence are very important. The Technical Proposal Volume (Volume II) shall not make reference to cost or price information. Your responses will be evaluated against the Technical subfactors defined in Section M, Evaluation Factors for Award. Using the instructions below and in Section M provide, as specifically as possible, the actual methodology/approach you will use for accomplishing/satisfying these factors and subfactors. All the requirements specified in the solicitation are mandatory. By your proposal submission, you are representing that your company will perform all the requirements specified in the solicitation. It is not necessary or desirable for you to tell us so in your proposal. Do not merely reiterate the objectives or reformulate the requirements specified in the solicitation.

L.4.2 Format and Specific Content

L.4.2.1 The following information shall be provided in the written technical proposal and will be evaluated to assess the proposed technical approach and associated technical risk in accordance with Section M001 a., Evaluation Basis for Award. The information provided should be in sufficient detail to allow the government to assess the offeror’s understanding of, and capability to perform, the work required by the PWS (RFP Attachment 1). 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.

It is your responsibility to ensure the completeness of your proposal. The government evaluation team has been instructed to evaluate on the basis of the information provided in the proposal. The government shall not assume that an offeror possesses any capability unless specified in the proposal.

L.4.2.2 Volume Organization.

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

(1) Table of contents to include list of Tables/Drawings/Matrices

(2) Glossary of key words and acronyms

(3) Short introduction and summary

(4) Response to factors and subfactors

L.4.2.3 Evaluation Factors and Subfactors.

The purpose of the technical approach is to furnish sufficient technical detail to allow the Government to assess the offeror's capabilities to perform the work required by the applicable PWS paragraphs and identify and mitigate risks to successful performance. A proposal that merely reiterates, paraphrases, or promises to accomplish the requirements of the PWS will be considered unacceptable. The offeror shall submit responses to the following factors and subfactors:

Factor 1: Access to Defense Intelligence Agency (DIA)-approved Sensitive Compartmented Information Facility (SCIF) approved at the Top Secret/Sensitive Compartmented Information (TS/SCI)-level

Factor 2: Technical Approach

Subfactor 1: Software Development Scenario (Exhibit B)

Subfactor 2: Program Management approach

L.5.0 Volume III – Past Performance (Factor 3)

L.5.1 General

Each offeror shall submit a Past Performance Volume with its proposal, containing past performance information in accordance with the format contained in Attachment 4. See paragraph L.5.3 for specific guidance on the number of past performance examples requested. Offerors with no past performance shall provide a statement to that effect. Offerors are cautioned that the government will use data provided by each offeror in this volume and data obtained from other sources in the evaluation of past performance.

Along with the information required in this paragraph, the offeror shall submit a consent letter executed by each subcontractor for whom past performance documentation is provided. A sample letter is provided as Attachment 5. The purpose of the consent letter is to authorize release of adverse past performance information to the offeror so the offeror can respond to such information. If no subcontractor past performance inputs are submitted as part of Volume 3, no consent letter is required. For each identified effort for a commercial customer, the offeror shall also submit a client authorization letter, authorizing release to the government of requested information on the offeror's performance.

L.5.2 Early Proposal Information

To permit the Past Performance evaluation team to conduct its assessment more efficiently, early submission of the past performance volume before the required submission date for the rest of the proposal is desired. The questionnaire, Attachment 6, should be sent directly to the government PCO identified in paragraph L.2.1.1, not the offeror. Each offeror is requested to submit Volume III, Past Performance, 10 days prior to proposal due date (see RFP page 1, Block 9). Failure to submit early proposal information will not result in offeror disqualification.

L.5.3 Relevant Contracts

Submit information in accordance with paragraph L.2.2. Prime offerors shall submit Past Performance Information on a maximum of three (3) recent contracts that they consider most relevant in demonstrating ability to perform the proposed effort and a total of two (2) recent contracts performed by major subcontractors (or a maximum of five (5) from prime offeror if no major subcontractors). Recent contracts, for the purposes of this solicitation, are defined as those where at least six months of work was performed during the five (5) years preceding the proposal due date. Include rationale supporting your assertion of relevance. For a description of the characteristics or aspects the government will consider in determining recency and relevance see RFP Section M002, paragraph d.(2).

To be a ‘major subcontractor’ the prime anticipates the subcontractor will perform 10 percent or more of the total effort, based on total proposed price/cost, or will perform effort critical to overall success such as serving in a ‘Principal’, ‘Lead’, ‘Senior’ or managerial designated role.

L.5.3.1 Specific Content.

Offerors are required to explain what aspects of the past performance example contracts are deemed relevant to the proposed effort and to what aspects of the proposed effort they relate. This 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 complex program and an offeror may have subsequently demonstrated the ability to overcome the problems encountered. The offeror is required to clearly demonstrate management actions employed in overcoming problems and the effects of those actions in terms of improvements achieved or problems rectified.

On the (up to) five (5) contracts submitted in Volume III, Past Performance, include relevant information concerning the offeror’s/joint venture member’s and major subcontractor’s compliance with the requirements of FAR 52.219-8, Utilization of Small Business Concerns or FAR 52.219-9, Small Business Subcontracting Plan, if these clauses were included in the past performance example contract. Copies of contractual reports may be submitted to validate compliance with requirements of FAR 52.219-8/52.219-9.

Explanation of efforts where minimum quantitative requirements and/or goals were not met should be provided. (Please note that FAR 52.219-8 does apply to ALL businesses, whereas FAR 52.219-9 only applies to large businesses.)

L.5.3.2 Questionnaires.

The government requests the offeror send out past and present performance questionnaires (see Attachment 6). Questionnaires shall be sent by the offeror to each past performance point of contact (POC) identified in the past performance references (Attachment 4). Offerors are recommended to encourage agencies/clients to complete the questionnaires and return them directly to the PCO 10 days prior to the solicitation due date but NO LATER THAN THE SOLICITATION DUE DATE. Once the past and present performance questionnaires are completed by the POCs, the information contained therein shall be considered sensitive and shall not be released to you, the offeror. A sample cover letter for transmitting the questionnaire to each POC is included in Attachment 6.

Provide a list of questionnaire recipient’s names and phone numbers for each contract reference provided to the Contracting Officer. The completed past and present performance questionnaire may be emailed to thomas.armstrong.11@us.af.mil. Mailing the questionnaire(s) to the address listed below is an acceptable alternative method of transmission. If mailing (through contracted courier providers), the outside envelope must be marked as follows:

NOTE: TO BE OPENED BY ADDRESSEE ONLY

AMIC DET 2 OL/PKA

Attn: Mr. Thomas Armstrong Bldg 10989 1020 South Patrick Drive Patrick Air Force Base, Florida 32925

The completed questionnaires should be contained in a second envelope marked with the mailing address and the following legend:

SOURCE SELECTION INFORMATION - See FAR 2.101 and 3.104 FOR OFFICIAL USE ONLY

L.5.3.3 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 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, include in this proposal volume a "roadmap" describing all such changes in the organization of your 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), your "roadmap" should be both specifically applicable to the efforts you identify and general enough to apply to efforts on which the government receives information from other sources.

L.6.0 Volume IV – Cost/Price (Factor 4)

L.6.1 General Instructions

L.6.1.1 Cost/Price Reasonableness, Realism and Balance. This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness of your proposed cost/price. Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Note that unrealistically low, or unreasonably high, proposed costs or prices, initially or subsequently, may be grounds for eliminating a proposal from competition either on the basis that the offeror does not understand the requirement or has submitted an unrealistic proposal. Costs or rates which are unbalanced, i.e. overstated or understated, may also be grounds for eliminating a proposal from competition. Offers should be sufficiently detailed to demonstrate their reasonableness. The burden of proof for credibility of proposed costs/price rests with the offeror.

L.6.1.2 Cost/Price Data. Information beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All information relating to the proposed cost/price, including all required supporting documentation shall be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this information and documentation be included elsewhere in the proposal.

Cost or Pricing Data Requirements. The contracting officer has determined there is a high probability of adequate price competition in this acquisition. Upon examination of the initial offers if, in the contracting officer's opinion, adequate price competition exists, certification under FAR 15.406-2 will not be required.

If, at any time during this competition, the contracting officer determines that adequate price competition no longer exists, an offeror may be required to submit cost/price data to the extent necessary for the contracting officer to determine the fairness, reasonableness and realism of the cost/price. An offeror may be required to provide a Certificate of Current Cost or Pricing Data in accordance with FAR 15.403- 4 and 15.403-5 and submit a revised cost/price proposal which complies with FAR 15.408 Table 15-2.

L.6.1.3 Contract Line Item Number (CLIN) Structure Contract CLIN 0001, Transition-In, will be firm-fixed-price and is a one-time charge for costs associated with phase-in operations. CLIN X002, O&M Labor and CLIN X003, R&D Labor, will be Cost-Plus-Fixed- Fee; CLIN X004, Travel and Other Direct Costs (O&M) and CLIN X005, Travel and Other Direct Costs (R&D), will be reimbursed on a cost-only (no fee) basis; and CLIN X006, Data Deliverables, will be Not Separately Priced.

‘X’ is used to represent the period of performance (ex., Base period is ‘0’; option period 2 is ‘2’, etc.)

L.6.2 Volume Organization. The Cost/Price volume shall consist of the following sections:

L.6.2.1 SECTION 1 - Table of Contents; summary descriptions of estimating, purchasing, and accounting systems; changes to estimating, accounting practices, or Cost Accounting Standards (CAS) Disclosure

Statement. Small Businesses shall provide either CAS Disclosure Statements or evidence of an acceptable accounting system as described in DFARS 252.242-7006(a)(1) and System Criteria described in 252.242- 7006(c).

(a) Provide any supporting Forward Pricing Rate Recommendations (FPRR)/Forward Pricing Rate Agreements (FPRA) issued by DCMA or supporting audits issued by DCAA.

i. If the proposed direct hourly rate for one or more labor categories does not match the applicable FPRR/FPRA with the cognizant DCMA or if an FPRR/FPRA is not available, then the offeror must provide an explanation of the methodology used to develop both the direct labor rates and indirect rates proposed.

(b) If applicable, provide calculations showing the development of composite and/or average rates from contractor fiscal year to government fiscal year.

(c) If applicable, provide supporting documentation (DD Form 1861 and CASB-CMF) for proposed Facilities Capital Cost of Money.

(d) Provide any other pricing data believed prudent and necessary to justify the cost/price proposal.

(e) Estimating System. Provide a summary description of your standard estimating system or methods. The summary description shall cover separately each major cost element (e.g., Direct Material, Engineering Labor, Manufacturing Labor, Indirect Costs, Other Direct Costs, Overhead, G&A). Also, identify any deviations from your standard estimating procedures in preparing this proposal volume. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

(f) Purchasing System: Provide a summary description of your purchasing system or methods (e.g., how material requirements are determined, how sources are selected, when firm quotes are obtained, what provision is made to ensure quantity and other discounts). Also, identify any deviations from your standard procedures in preparing this proposal. Indicate whether you have Government approval of your system and if so, provide evidence of such approval.

(g) Accounting System: Indicate whether you have Government approval of your accounting system and if so, provide evidence of such approval. Also, identify any deviations from your standard procedures in preparing this proposal.

L.6.2.2 SECTION 2 – Data other than certified cost or pricing data, to include estimating methodology.

(a) Total Cost Summary: Submit cost/price schedules which display the estimating methods of the proposed Section B costs/prices for each priced CLIN. Include a cost roll-up summary by base and option periods (to include Option to Extend Services, FAR 52.217-8) and total contract cost/price.

(b) Labor Rates. Offerors shall provide the labor rates that will be used during the contract performance and for billing purposes. The proposed rates shall show an unburdened rate (base year) and fully burdened rates (all years) which includes allocable and allowable costs (e.g., labor, fringe, overhead, G&A) required to perform the requirements as stated in the PWS. Offerors shall provide a detailed schedule which shows the development of each labor rate on the base year and escalated rates for each option year on Attachment 7 Rate_Hours_Indir.xlsx provided for proposal submission (or similar form). Offerors shall also provide a narrative that describes the offeror’s rationale used to develop each labor rate (e.g., labor categories, estimated hours, fringe, escalation factors and other allowable indirect expenses). Provide all other considerations and assumptions made in developing the rates.

(c) Labor hours and categories. Offerors shall also complete the Labor Cost Summary tab in Attachment 7. The historical workload by labor category, is provided as Attachment 8 and is for informational purposes only. Offerors may propose an alternative workload schema (hours and labor categories). In the event an offeror uses different titles for labor categories other than shown in Attachment 8, proposals shall map the proposed labor category to those identified by the Government. Labor categories proposed that are different than those provided in Attachment 8 shall include a clear and concise description including experience, duties, certifications and education.

(d) Indirect Rates: Offerors shall identify all indirect expenses applied to fully-burdened labor rates and CR CLINs on the Indirect Rates tab in Attachment 7. Offerors shall provide detailed analysis to justify the proposed indirect expenses for the CLINs shown in Section B of the solicitation. Provide one of the following and a total indirect rate roll-up summary:

• Identify the allocation base for each rate. Provide detailed breakout of indirect expense pools and associated basis used to develop the rates. Provide calculations showing the development of composite and/or average rates from contractor fiscal year to contract fiscal year. Also provide narrative that describes the offeror’s rationale used to develop each indirect expense.

Provide a breakout between all other considerations and assumptions made in developing the proposed indirect rates; OR

• Provide Government-verified rates (e.g. DCAA, DCMA rates).

(e) Subcontracts. Offerors shall:

o Provide a summary listing of all anticipated subcontractors.

o Under FAR 15.404-3, provide the prime offeror’s cost/price evaluations and negotiations on each subcontract exceeding 10 percent of the total proposed price, if the percentage is above the TINA threshold. Describe the evaluation and rationale, including all relevant facts and data which led to the subcontract amount incorporated in the cost proposal. Identify all adjustments made to the subcontractor’s proposed costs. Prime contractors with an approved purchasing system shall submit this data in addition to and in accordance with their approved purchasing plan.

Subcontractors may submit subcontract proposals directly to the Contracting Officer if the cost information is considered proprietary data. All required data shall be received by the same date/time as the prime’s proposal.

(f) Travel and ODC: Travel and ODC CLINs shall be Cost-Reimbursement (COST) Non-Fee bearing CLINs, which include provision for the cost of all travel ODCs and associated burdens (indirect expenses). Offerors shall identify any indirect expenses to be applied to CLIN X004, Travel and ODCs (O&M) and CLIN X005, Travel and ODCs (R&D). Offerors shall use the government-provided values stated for CLINs X004 and X005 in Attachment 9.

(g) Solicitation Total Proposal Price. Offerors shall fill in and return Attachment 10 (or a similar spreadsheet generated by the offeror). There should be a linear relationship between Attachments 7 and 10. Offerors shall ensure the CLIN values submitted in Section B of the Model Contract/RFP comport with the totals provided in Attachment 10.

Note: In the event only one awardable offer is received, the offeror may be required to provide a Certificate of Current Cost or Pricing Data in accordance with FAR 15.403-4 and 15.403-5 and submit a revised cost/price proposal which complies with FAR 15.408 Table 15-2. In that instance, FAR 15.404-3(b)(3) also applies.

L.6.2.3 SECTION 3 (IF APPLICABLE) - Other information such as Government Furnished Property/Government Furnished Equipment (GFP/GFE), base support, long lead costs, termination costs, development/production schedule, inflation rate summary and explanation, life cycle cost, and special tooling/test equipment. List each exception to the ground rules and assumptions provided in the solicitation and each qualification of the Cost/Price volume, if any. Provide complete rationale for any exceptions. If an offeror proposes to absorb a portion of costs or provides other benefits to the Government which affects cost/price, the offeror shall explain the impact on cost/price. Include any information which may have a bearing on your financial capability to perform the contract. If you are proposing a joint venture, describe how you will handle financial matters.

L.6.3 Estimating Techniques and Methods: When responding to the Cost/Price Volume requirements in the solicitation, the offeror and associated subcontractors may use any generally accepted estimating technique, including contemporary estimating methods (such as Cost-to-Cost and Cost-to-Non-Cost Estimating Relationships [CERs], commercially available parametric cost models, in-house developed parametric cost models, etc.), to develop their estimates. If necessary, reasonable and supportable allocation techniques may be used to spread hours and/or costs to lower levels of the work breakdown structure (WBS).

L.6.3.1 Explanation of Estimating Methods Used. Explain the methodology used to estimate each cost element. As a minimum, provide the following information for each cost element. If a portion of the required information is not applicable for a particular cost element, so state.

(a) Past Experience-Based Estimates. Where cost estimates are based upon past experience, identify the past experience, explain how the past experience relates to the current effort, including similarities and differences, and how cost data available from the past experiences was adapted to the current effort.

(b) Learning Curve Estimates. Where cost estimates are based upon learning/improvement curve applications, identify the specific area subject to learning, the curve hypothesis (unit or cumulative) and the slope of the curve as a percent. Also, identify the data used to develop the first unit cost and slope and explain how this data related to the current effort and how entry on the learning curve was attained (i.e., how the first unit cost was derived).

(c) Labor Hours. If labor hours have been estimated based upon other than past experience; provide detailed rationale on how they have been estimated.

(d) Labor Hour Skill Mix. Explain how the proposed labor hour…

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .