ATCH_10_Section_L.pdf

Attachment 10

FA702219RA007

Section L - Instructions, Conditions, and Notices to Offerors (ICNTO)

L.1.0 Program Structure and Objectives

The 24th Analysis Squadron Nuclear Sciences Flight (24ANN), part of the Air Force Technical Application Center (AFTAC) 709th Surveillance and Analysis Group (709SAG), contracts with multiple laboratories to perform analysis of samples and uses the results to create reports.

During previous contracts, mostly recently Nuclear Data Evaluation Services, NDES, a suite of software and hardware systems were developed to manage sample logistics and analytical information. The systems developed under previous NDES contract include the Trackman application, Data Acquisition System Lab Extraction (DASSLE), and Workflow.

L.1.1 Budget/Funding Information

For consideration in developing proposals, the NDES III acquisition strategy provides for award of an Indefinite Delivery Indefinite Quantity (IDIQ) type contract with a five (5) year ordering period. The contract ceiling is $3.7M which includes services (O&M), Firm-Fixed-Price (FFP), cost reimbursable for other direct costs and travel (CR no-fee), data deliverables (NSP), and Phase-In . The government’s intent is to fund the contract at the task order-level. Issued task orders may contain both cost (no fee) and firm-fixed price CLINs.

The contract ceiling identified above, and at clause 52.216-19 Order Limitations (Oct 1995), is established based on known/unknown mission requirements.

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 List (CDRL), RFP Exhibits A and B. 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.

(b) 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 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. 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 (RFP Attachment 11).

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

(d) The proposal acceptance period is established at 180 days (see paragraph L.3.3.4.3).

The offeror shall make a clear statement in Section A of the proposal documentation volume that the proposal is valid through this period.

(e) 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.

(f) Questions regarding this solicitation are due by 2 Apr 2019. Questions and responses to questions will be posted to the FBO site. Questions should be emailed to kim.pattan@us.af.mil and cynthia.turner.1@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: Ms. Kim M. Pattan Bldg 10989 1020 South Patrick Drive Patrick Air Force Base, Florida 32925 Email: kim.pattan@us.af.mil Telephone: (321) 494-5452

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, Preaward 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, Postaward 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. The offeror is reminded that the government mailto:kim.pattan@us.af.mil mailto:cynthia.turner.1@us.af.mil 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.

L.2.1.4 Electronic Reference Documents. All unclassified referenced documents for this solicitation are available on the Federal Business Opportunities (FedBizOpps) website at http://www.fedbizopps.gov. Potential offerors are encouraged to subscribe for real-time e-mail notifications when information has been posted to the website for this solicitation.

L.2.1.5 Communications. Exchanges of source selection information between government and offerors will be controlled by the PCO. Email may be used to transmit such information to offerors; email can be sent and received and shall include “Source Selection Information – See FAR 2.101 & 3.104” in the Subject line. Source selection information may be transmitted via mail.

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.2 Organization/Number of Copies/Page Limits

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

The Administrative Volume should not be used to expand information that should be included in other volumes. The volumes identified in the table shall be separately bound in three-ring, loose-leaf binders, as necessary. 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 3.0 Administrative Paper: Original and 1 copy Electronic: 1

Unlimited

II 4.0 Technical/Technical Risk

Paper: Original and 3 copies Electronic: 1

40 pages

III 5.0 Past Performance Paper: Original and 1 copy Electronic: 1

1-3 pages per reference

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

Unlimited

V 7.0 Task Order 0001 (Technical)

Paper: Original and 1 copies Electronic: 1

10 pages

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 ENs. The specified page limits for EN responses will be identified in the letters 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 shall also 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 shall apply to both electronic and hard copy proposals.

L.2.2.2 Pricing Related Data. Submit an electronically encoded price model in support of the proposed price. All pricing data shall be addressed ONLY in the Price Proposal and Section B of the Model Contract. Price trade-off information, work hour estimates, and material kinds and quantities may be used in other volumes only as appropriate for presenting rationale for alternatives or design and trade-off decisions. Any price model submitted must be consistent with your approved estimating system and must duplicate the logic and mathematical formulas reflected in the paper copy of your proposal. All cells in the Excel document shall be unprotected and show all formulas used. Price models submitted must comply with the following format requirements:

(a) Data file should be submitted on a CD.

(b) Data file should be MS-Excel 2016 file format or compatible format.

(c) Viewing Environment. The government anticipates viewing the electronic submittals with the following computer software and hardware: 1) HP-compatible systems, 128 MB of RAM, nominal 17 inch color monitors, and standard CD ROM readers, 2) Windows 10 operating system, 3) Adobe Reader, Microsoft Office 2016, and Internet Explorer 11.

L.2.2.3 Classified Information. The government desires that classified information not be included as part of your proposal. If it is absolutely necessary to provide classified information in your response, it shall be provided 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 the DD Form 254 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: Ms. Kim Pattan 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 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 copy and the CD.

L.2.3 Electronic Offers.

The content and page size of electronic copies must be identical to the hard copies. The offeror shall submit all volumes in electronic format, using recordable CDs. For electronic copies, indicate on each CD the volume number and title, using separate folders or files to permit rapid location of all portions, including subfactors, exhibits, annexes, and attachments, if any. Each volume shall be in a different directory on a CD. If files are compressed, the necessary decompression program must be included. The electronic copies of the proposal shall be submitted in a format readable by Microsoft (MS) Office Word 2016, MS Office Excel 2016, MS Office Project 2010, and MS Office Power Point 2016, as applicable. The offeror shall not embed sound or video files into the proposal files. Minimize the use of scanned images and keep embedded graphics as simple as possible. In the event that paper copies and electronic copies of a proposal are submitted and if there are any discrepancies between the paper copies and the electronic copies of the proposal, the hard paper will be used for evaluation. It is the offeror’s responsibility to ensure media is free of viruses and malware.

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 (If the proposal is classified, use paragraph L.2.2.3 for mailing.):

DEPARTMENT OF THE AIR FORCE

AMIC Det 2 OL/PKA ATTN: Ms. Kim M. Pattan 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: FA7022-19-R-A007.

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

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. 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 – Supplies or Service and Prices. Complete pricing information in Section B of the model contract. Use the government-provided dollar value for CLIN 0002 (ODCs) and CLIN 0003, 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 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, 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 Authorized Offeror Personnel.

Provide the name, title, 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.2 Government Offices.

Provide the mailing address, telephone; fax number, e-mail address (if known), and facility codes for the cognizant Contract Administration Office (ACO), DCMA, DCAA, and government paying office for the prime contractor and major subcontractors (including teaming partners who are proposed to perform 15 percent or more of the proposed effort based on the total proposed price or perform aspects of the effort the offeror considers critical to overall successful performance). If offeror elects to subcontract a portion of this effort, provide a copy of your analysis as required by FAR 15.404-3(b) (2).

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

Provide company/division's street address, county and facility code; CAGE code; DUNS number; 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). Provide the same information for your major subcontractors as defined in paragraph L.3.3.2. 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.4 Attachments to the Model Contract. The offeror shall provide the following as attachments to the model contract:

L.3.3.4.1 GFP and/or Base Support Requirements.

The need for GFP and base support requirements is anticipated. The offeror shall complete the GFP List (Attachment 12), Non-Serially Managed Items tab only. Required fields are marked with an asterisk (*). The offeror shall also provide the written authorization from the cognizant ACO, as applicable.

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

L.3.3.4.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 180 days from the date of receipt of proposal.

L.3.3.4.4 Clearances. Documentation of current DSS-approved facility clearance and key personnel clearances in place. Joint ventures (populated/unpopulated) must have a DSS-approved facility clearance specific to the joint venture entity.

L.3.3.4.5 Organizational Financial Information. Submit copies of your 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 you are proposing a joint venture, describe how you will handle financial matters.

L.4.0 Volume II – Technical/Technical Risk Volume (Factor 1)

L.4.1 General

L.4.1.1 The Technical Volume must 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 (RFP Attachment 11). Using the instructions provided below, provide as specifically as possible, the actual methodology/approach you will use for accomplishing/satisfying these 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 Technical.

In the technical volume, provide your technical solution for meeting or exceeding the government’s minimum performance or capability requirements of each technical subfactor. 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). Your proposal must describe the capability of your organization to successfully perform the requirements to include discussion of program management, ability to provide personnel with the requisite knowledge, experience, skill sets and clearances; and discussion of teaming or subcontracting arrangements. 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.1.1 Technical Risk.

Address technical risk associated with those aspects of your proposed technical approach you consider to have the potential for disruption of schedule, increased costs, degradation of performance, the need for increased government oversight, or the likelihood of unsuccessful contract performance. Classify each risk in accordance with the DOD Source Selection Procedures, dated 31 Mar 2016, Table 2B Technical Risk Rating (included in RFP Attachment 11). Provide the rationale for each risk and its rating, including quantitative estimates of the impact on cost, schedule, and performance. Describe the impact of each identified risk in terms of its potential to interfere with or prevent successful accomplishment of other contract requirements (for example: PWS requirements), whether or not those requirements are identified as subfactors. Propose realistic “work-arounds” or risk mitigators for identified risks that will eliminate or reduce risk to an acceptable level. Identify and classify any new risks introduced by such mitigation.

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(s) of Tables/Drawings/Matrices

(2) Glossary of key words and acronyms

(3) Short introduction and summary

(4) Subfactor 1

(5) Subfactor 2

(6) Subfactor 3

L.4.2.3 Evaluation 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. A proposal that merely reiterates, paraphrases, or promises to accomplish the requirements of the PWS will be considered unacceptable.

(1) Subfactor One (1): Program Management and Staffing Plan

1) The offeror’s Program Management approach

2) A Staffing Plan which demonstrates the offeror’s ability to provide qualified personnel (see Attachment 3). The offeror shall provide the resumes for the all labor categories

3) Transition plan to describe how you propose to mobilize, train, observe, and otherwise prepare to become fully operational and assume complete contract responsibility

*Offerors shall submit a Letter of Intent with the resume for any person not presently in the employ of the prime offeror or an intended subcontractor. Letters of Intent will not count toward the volume page total.

(2) Subfactor Two (2): Technical Approach and Ability

1) How performance will be accomplished in each of the areas of process, procedures, and planning as required to implement, maintain and support the requirements of the PWS. The offeror must provide specific and detailed examples, prior experience, and evidence to support their claims

2) Demonstrate ability to provide technical expertise to meet Department of Defense Information Assurance requirements in accordance with Security Technical Implementation Guides (STIGs) (https://iase.disa.mil/)

(3) Subfactor Three (3): Task Order 0001

1) Provide a proposal to fulfill the requirements outlined in the Task Order 0001 PWS

(Attachment 4). The proposal shall include a staffing plan and technical proposal.

The price proposal related to Subfactor 3 shall be submitted as part of Volume IV - Price.

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

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 5 of the RFP. 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, teaming partner, and/or joint venture partner (if applicable), authorizing release of adverse past performance information to the offeror so the offeror can respond to such information. If no joint venture/teaming partners’ 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 desirable. The questionnaire, see Attachment 6 of the RFP, 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, by 1 Apr 2019. Failure to submit early proposal information will not result in offeror disqualification.

L.5.3 Relevant Contracts

Submit information in accordance with Attachment 5 of the RFP: Past Performance Information on a maximum of three (3) recent contracts that you consider most relevant in demonstrating your ability to perform the proposed effort. Also include information on two (2) recent contracts performed by each of your teaming partners and significant subcontractors that you consider most relevant in demonstrating their ability to perform the proposed effort. 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 Attachment 11, Section M002, paragraph c. (Past Performance Factor)). To be a ‘significant subcontractor’ the prime anticipates the subcontractor will perform 15% or more of the total effort, based on ceiling price, or will perform effort critical to overall success.

L.5.3.1 Specific Content.

Offerors are required to explain what aspects of the 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 more complex program, or 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. 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. Categorize the relevant information into the specific Technical subfactors and Price factor used to evaluate the proposal.

L.5.3.2 Questionnaires.

The government requests the offeror send out past and present performance questionnaires (see Attachment 6 of the RFP) to each of the points of contact (POCs) identified in the past performance volume. Offerors are recommended to encourage agencies/clients to complete the questionnaire and return it directly to the PCO 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 cover letter for transmitting the questionnaire to each POC is included in Attachment 6 of the RFP. You may include your own cover letter requesting completion of the questionnaire in addition to the cover letter provided.

Provide a list of questionnaire recipients to include two (2) current POCs and phone numbers for each contract reference provided. The offeror is solely responsible for the accuracy of the contact information provided.

The completed past and present performance questionnaire may be emailed to kim.pattan@us.af.mil and cynthia.turner.1@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: Ms. Kim M. Pattan Bldg 10989 1020 South Patrick Drive Patrick Air Force Base, Florida 32925

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 3)

L.6.1 General Instructions

L.6.1.1 This section is to assist you in submitting data other than certified cost or pricing data that is required to evaluate the reasonableness, and balance of your proposed cost/price.

Compliance with these requirements is mandatory and failure to comply may result in rejection of your proposal. Additionally, unbalanced pricing poses an unacceptable risk to the Government and may be a reason to reject an offeror’s proposal. Offers should be sufficiently detailed to demonstrate their reasonableness, and balance. The burden of proof for credibility of proposed costs/prices rests with the offeror.

In accordance with FAR 15.403-1(b) and 15.403-3(a), data other than certified cost or pricing data may be required to support a determination of price reasonableness. Data shall be provided in accordance with FAR 15.403-5. If, after receipt of proposals, the CO determines that there is insufficient data available to determine price reasonableness and none of the exceptions in FAR 15.403-1 apply, the offeror shall be required to submit additional cost or pricing data. Data beyond that required by this instruction shall not be submitted, unless you consider it essential to document or support your cost/price position. All data relating to the proposed price, including all required supporting documentation, must be included in the section of the proposal designated as the Cost/Price Volume. Under no circumstances shall this data and documentation be included elsewhere in the proposal.

All dollar amounts provided shall be rounded to the nearest dollar.

L.6.1.2 CLIN Structure for pricing.

The labor for CLIN 0001 firm-fixed-price; Other Direct Costs, to include Travel, under CLIN 0002 will be strictly cost reimbursement (no fee), and will be provided by the government as a not-to-exceed (NTE) amount; CLIN 0003, Data Deliverables, is expected to be not-separately-priced (NSP); CLIN 0004, Phase-In, will be firm-fixed-price and is a one-time charge for costs associated with phase-in operations.

As there is no expectation for sustained performance at a government work-site offerors should develop cost/price for labor assuming work will be performed at the offeror’s work-site(s) only.

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

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.

(a) Provide any supporting Forward Pricing Rate Recommendations (FPRR)/Forward Pricing Rate Agreements (FPRA) issued by DCMA or supporting audits issued by DCAA. 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.

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

(a) Solicitation Attachment 7, Labor Rates. Offerors shall fill in and return Attachment 7 (or a similar spreadsheet generated by the offeror). Offerors may add additional labor categories deemed necessary to successfully perform the requirements detailed in the PWS. Any added labor categories shall include a clear and concise description including experience, duties, and education. Added labor categories shall be highlighted or made recognizable for government evaluation.

Although the intended contract will reflect a single 5-year ordering period, Attachment 7 allows for the escalation of labor rates throughout the government fiscal years. Offerors shall state the basis for labor rate escalation (if applicable). Individual task orders will be costed/priced using the rates applicable to the fiscal year in which the task order is awarded. Offerors are cautioned that Attachment 7 will be incorporated, as negotiated, in any resulting contract and utilized for the life of the contract.

Indirect Rates: Offerors shall provide detail analysis to justify the proposed indirect expenses for the FFP CLIN 0001. Offerors shall provide one of the following:

(1) 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 expenses. Provide a breakout between all other considerations and assumptions made in developing the proposed indirect rates.

OR

(2) Provide Government approved rates (e.g. DCAA, DCMA approved rates).

(b) Solicitation Attachment 8 provides the government’s estimate of the hours anticipated under the proposed contract. Offerors shall fill in and return Attachment 8 (or similar spreadsheet generated by the offeror). The labor hours provided by the Government in Attachment 8 are estimated and included to assist the offeror by providing a point of reference. Offerors may propose alternative labor hours that differ from the Government’s estimated workload. Proposed changes to workload data shall be highlighted for government evaluation. Offerors shall apply the labor rates documented in Attachment 7 and verify all totals. Any labor categories added to Attachment 7 shall be added to Attachment 8 with an estimated number of FFP hours.

(c) Solicitation Attachment 9, Total Proposal Price. Offerors shall fill in and return Attachment 9 (or a similar spreadsheet generated by the offeror). There should be a linear relationship among Attachments 7, 8 and 9.

Offerors shall ensure the CLIN values submitted in Section B of the Model Contract/RFP comport with the totals provided in Attachment 9.

(d) Offerors shall identify any indirect expenses to be applied to CLIN 0002 (ODCs to include travel). Offerors shall use the government-provided CLIN 0002 value of $25,000 in Section B of the model contract.

(e) Subcontracts (if applicable):

(1) Provide a summary listing of all anticipated subcontractors and consultants which identifies subcontractor labor categories, description of effort, and anticipated hours.

(2) Under FAR 15.404-3, provide the results of the prime’s cost/price analysis on each subcontract anticipated to exceed $250,000 over the life of the contract.

(4) 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) Acceptable Accounting System: 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).

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.

SECTION 4 – Cost/Price Proposal for Task Order 0001. Offerors shall provide a separate cost/price proposal for Task Order 0001. The price proposal should be aligned with the technical proposal, labor categories/hours listing and proposed schedule provided to satisfy Technical Factor 1, Subfactor 3. The price proposal shall include direct labor broken down by labor category, direct labor rates and direct labor subtotal; and identify other direct costs (ODCs), if applicable. Offerors shall provide a summary of total labor price, total ODCs (if applicable), and total proposal price with all dollar amounts rounded to the nearest whole dollar. Offerors shall also provide a Task Order Section B which indicates the cost/price of each appropriate Task Order CLIN, similar to Section B of the model contract/RFP.

If awarded, the negotiated cost/price proposal will be used for issuance of Task Order 0001 (subject to FAR 52.232-18 – Availability of Funds).

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

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.

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.

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.

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.

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.

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

L.6.4 Other Information:

Service Contract Labor Standards Act (SCLSA). Labor under this effort is exempt from the

SCLSA.

The 24th Analysis Squadron Nuclear Sciences Flight (24ANN), part of the Air Force Technical Application Center (AFTAC) 709th Surveillance and Analysis Group (709SAG), contracts with multiple laboratories to perform analysis of samples and uses the res...