Soliciation Amendment 0003.pdf
PDF 247 KB Posted
- Attached to
- Cooperative Biological Engagement Support (CBES) Federal contract opportunity
- Solicitation number
- W911SR20RBESC
About this file
This is a solicitation for cooperative biological engagement support services. The Combat Capabilities Development Command Chemical Biological Center seeks a contractor to provide support by addressing global health security threats through working with partner nations to improve biosafety, biosecurity, and disease surveillance. The contractor will foster expertise to help mitigate pathogens at their source by supporting the creation and development of Threat Reduction Networks, researching and documenting policy guidance, gathering partner country data, and aiding CCDC CBC. The effort involves traditional select agents and emerging disease pathogens of international concern. This requirement will be set aside for certified HUBZone small businesses. The solicitation includes the document and attachments with proposal submission instructions, evaluation criteria, and contract terms.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Questions Responses FINAL.xlsx | XLSX spreadsheet | |
| Amendment 0002.pdf | ||
| Amendment 0001 SolicitationW911SR-20-R-BESC.pdf | ||
| Amendment 0001 SolicitationW911SR-20-R-CBES.pdf | ||
| A07 - Solicitation Questions Template.XLSX | XLSX spreadsheet | |
| A03 - DD254 25 March 2020.pdf | ||
| Solicitation W911SR-20-R-BESC.pdf | ||
| A03 - QASP 2020.doc | DOC document | |
| Cost Template - CBES 20-R-BESC.xlsx | XLSX spreadsheet | |
| A02 - FINAL CDRLs 27 July.docx | DOCX document | |
| Performance Assessment Questionnaire.docx | DOCX document |
Show all 11
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND TITLE OF SIGNER (Type or print)
30-105-04EXCEPTION TO SF 30
APPROVED BY OIRM 11-84
STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA
FAR (48 CFR) 53.243
The purpose of this amendment is to execute the follow ing:
1. Revise the proposal submission language in paragraph L.1.3.3. to state " Each volume of an Offeror's proposal shall be submitted electronically to the Contracting Officer at nicholas.granata.civ@mail.mil and Contract Specialist at Sheila.l.ramos2.civ@mail.mil . Each volume shall be clearly labeled w ith its Title and a copy number (e.g.copy 1 of 5).
2. To add paragraph L.1.3.3.1 to provide the Acquisition Source Selection Interactive Support Tool (ASSIST) information.
3. To revise the language in paragraph L.6.6. to state "Offerors can contact the ASSIST2Industry helpdesk at 1-866-335-2769 (ARMY), #Option 7 for any technical assistance that may be needed".
4. To revise the language in table M-2 "Combined Technical/Risk Rating Technical/Program Management to reflect the Department of Defense Source Selection Procedures dated 31 March 2016,
1. CONTRACT ID CODE PAGE OF PAGES
J 1 19
16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)
16C. DATE SIGNED
BY 10-Sep-2020
16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR
(Signature of Contracting Officer)(Signature of person authorized to sign)
8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W911SR20RBESC
X 9B. DATED (SEE ITEM 11)
04-Aug-2020
10B. DATED (SEE ITEM 13)
9A. AMENDMENT OF SOLICITATION NO.
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNTING AND APPROPRIATION DATA (If required)
13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE
CONTRACT ORDER NO. IN ITEM 10A.
B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).
C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
D. OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)
10A. MOD. OF CONTRACT/ORDER NO.
2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)
6. ISSUED BY
3. EFFECTIVE DATE
10-Sep-2020
CODE
USA CONTRACTING CMD-APG. - W911SR
EDGEWOOD CONTRACTING DIVISION
8456 BRIGADE STREET
BLDG E4215
ABERDEEN PROVING GROUND MD 21010-5401
W911SR 7. ADMINISTERED BY (If other than item 6)
4. REQUISITION/PURCHASE REQ. NO.
CODE
See Item 6
FACILITY CODECODE
EMAIL:TEL:
W911SR20RBESC
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
INSTRUCTIONS TO OFFERORS
Section L - Instructions, Conditions and Notices to Bidders
L.1 PROPOSAL SUBMISSION INSTRUCTIONS.
L.1.1 In order for proposals to receive full consideration for award, the Offeror shall ensure that the information furnished in support of the proposal is factual, accurate, complete and defensible. Failure to provide the information requested by the RFP may render the Offeror’s proposal incomplete and ineligible for further consideration for award. Files shall not contain classified data or material. No portion of the proposal shall contain classified information. The use of hyperlinks in proposals is prohibited.
L.1.2 . The solicitation will be issued electronically, as well as any amendments subsequently issued thereto. It will therefore be the sole responsibility of all interested parties to periodically access the www.beta.sam.gov website described below in order to obtain any amendments which may be issued. Failure of an Offeror to obtain any said amendments and to respond to them prior to the date and time set for receipt of proposals is at the sole risk of the Offeror, and may result in proposals (or any portion thereof) being declared non-responsive, which can result in the rejection of proposal submissions.
L.1.3 All submissions shall strictly comply with all filing requirements and content as specifically set forth in the solicitation. Failure to fully comply with all filing requirements shall result in rejection of a proposal submission as non-responsive.
L.1.3.1 Offerors must be registered in the System for Award Management (SAM) at www.sam.gov and have a Data Universal Numbering System (DUNS number) and Commercial and Government Entity (CAGE) Code.
L.1.3.2 The solicitation is found by searching on www.beta.sam.gov.
L.1.3.3 Each volume of an Offeror's proposal shall be submitted electronically to the Contracting Officer at nicholas.granata.civ@mail.mil and Contract Specialist at Sheila.l.ramos2.civ@mail.mil . Each volume shall be clearly labeled with its Title and a copy number (e.g.copy 1 of 5).
L.1.3.3.1 During the conduct of this acquisition, the Acquisition Source Selection Interactive Support Tool (ASSIST) will be used by the Government to support the proposal evaluation and source selection process. A separate tool, the ASSIST2Industry, will be used in conjunction with ASSIST to accomplish all exchanges with Offerors after receipt of proposals pursuant to Federal Acquisition Regulation (FAR) 15.306. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, all Evaluation Notices (ENs) in a secure online environment.
PLEASE REFER TO PARAGRAPH L.6 FOR FURTHER INSTRUCTIONS ON SET UP AND USE OF
THE ASSIST SYSTEM.
L.1.3.4 Files shall not contain classified data. All information which the Offeror wishes to have considered must be submitted with the initial proposal and shall be confined to the appropriate volume. The Government will not consider any information that is not included in the appropriate volume as required, or any information that exceeds the number of pages allowed. The use of hyperlinks in proposals is prohibited.
L.1.3.5 Offerors are cautioned that “parroting” of the Technical requirements or the PWS with a statement of intent to perform does not reflect an understanding of the requirement or capability to perform. Offerors are responsible for including sufficient details to permit a complete and accurate evaluation of each proposal.
Proprietary information shall be clearly marked.
L.1.3.7 The Offeror bears the responsibility to ensure timely transmission of its offer, that the offer is responsive to all requirements set forth in the solicitation, and to ensure the availability of an open transmission line and to take into consideration the length of time required to complete an upload transaction prior to the solicitation closing date/time stated in the solicitation. In no circumstances shall the tender of any proposal or other required document that is filed beyond any filing deadline be considered. Late filing shall result in a proposal being rejected in its entirety.
L.2 PROPOSAL PREPARATION INSTRUCTIONS.
L.2.1 Format: The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date, and Request for Proposal (RFP) number in the header and/or footer. A Table of Contents should be created and files shall use the following page setup parameters:
Margins – Top, Bottom, Left, Right – 1 inch Gutter – 0 inch From Edge – Header, Footer 0.5 inch Page Size, Width – 8.5 inch Page Size, Height – 11 inch
L.2.2 File Packaging. Files shall be in read-only format, using PDF files. All price breakdown information to aide in the cost or price evaluation shall be submitted in Microsoft Excel Read/Write format and viewable in Microsoft Excel 2013.
L.2.3 Content Requirements. The Offeror’s Technical Approach, Program Management Approach, Past Performance and Cost or Price shall be submitted in separate volumes as set forth in Table L-1 below. The Offeror shall confine submissions to essential matters, sufficient to define the proposal in a concise manner to permit a complete and accurate evaluation of each proposal. Each file of the proposal shall consist of a Table of Contents, Summary Section, and the Narrative Discussion. The Summary Section shall contain a brief abstract of the file. Proprietary information shall be clearly marked. All information the Offeror wishes to have considered must be submitted with the initial proposal and shall be confined to the appropriate volume and page limit. The Government will not consider any information that is not included in the appropriate volume as required, or information that exceeds the number of pages allowed.
Table L-1 Format for Submission
Volume
Title
Page Limit
I Technical Approach Fifty (50) pages II Program Management Approach Fifty (50) pages
III Past Performance Ten (10) pages, in addition Five (5) pages for every subcontractor, if applicable
IV Cost or Price Unlimited V Solicitation, Offer and Award Documents and
Certifications/Representations Unlimited
NOTE: Pages that exceed the required page limitations will not be evaluated. Additional pages over the maximum allowed will be removed or not read and will not be evaluated by the Government.
L.2.4 The title page for each volume shall include: volume number, volume subject, company name, and a proposal identification number.
L.2.5 Indices to the proposal and cross-references between the proposal and the solicitation are used for ensuring that all pertinent sections of the proposal are fully understood. The use of an effective and organized Table of Contents and/or List of Tables/Figures along with tabs to easily locate sections of the proposal also facilitates thorough evaluation.
L.2.6 Each volume shall be as brief as possible, yet consistent with a complete submission. Pages shall not exceed
8.5 inches in width and 11 inches in length; however, pages, as appropriate, not exceeding 11 x 17 inches, depicting such items as charts, matrices, or schedules may be used and will count as a single page. The Offeror shall number all pages within each volume.
L.2.7 The Offeror's proposal shall not exceed the above page limitations and must be printed using 12 point font (foldout pages or electronic spreadsheets - 10 point font) with one-inch margins (top, bottom, left and right).
The cover letters, title page, table of contents, resumes limited to two pages, supporting data, and cross-reference matrices do not count against page count limitations.
L.2.7.1 Technical Approach. Refer to paragraph L.3.2.1 below. The supporting data shall be limited to 50 pages.
This supporting data does not count against the page limitations for the Technical Approach – Volume I.
L.2.7.2 Program Management Approach. Refer to paragraph L.3.2.2 below. The supporting data, shall be limited to 50 pages. This supporting data does not count against the page limitations for the Program Management Approach – Volume II.
L.2.8 The Offeror shall provide an explanation, in a clearly reliable format, such as a matrix, of any difference between the format in which the proposal has been requested and the format in which it is actually submitted.
L.2.9 The Offeror is expected to provide sufficient detail in a clear and concise manner to completely and logically address every aspect the Government intends to evaluate. The Government does not desire excess verbiage, unnecessary and elaborate brochures, or lengthy, repetitious, disorganized presentations beyond that sufficient to present a complete and clear offer. Such presentations are not desired and may be construed as an indication of the Offeror’s inefficiencies and lack of cost consciousness in proposal preparation. All Offerors are reminded that unsupported promises to comply with the contractual requirements will not be sufficient.
Proposals must not merely repeat the contractual requirements, but rather must provide convincing documentary evidence in support of any statements relating to the promised performance.
L.3 SPECIFIC INSTRUCTION BY VOLUME.
L.3.1 The Offeror’s proposal shall be segregated into six (5) volumes as follows:
L.3.1.1 Volume I -Technical Approach
L.3.1.2 Volume II – Program Management Approach
L.3.1.3 Volume III – Past Performance
L.3.1.4 Volume IV – Cost or Price
L.3.1.5 Volume V – Certifications and Representations
L.3.2 Specific Instructions.
L.3.2.1 Volume I – Technical Approach.
L.3.2.1.1 The Offeror’s technical volume shall address the following, and shall be organized into the following sections:
L.3.2.1.2 The Offeror shall provide a detailed discussion of the technical approach in terms of executing each of the tasks outlined in the PWS. This shall include identifying how they will comply with all regulations, policies and process in accordance with the PWS.
L.3.2.1.3 The Offeror shall describe its approach to working with agencies similar or equal to the U.S. State Department, Defense Health Agency (DHA), and the World Health Organization (WHO), describe their processes of complying with regulations in the following partner countries: Cambodia, Indonesia, Laos, Malaysia, Thailand, Vietnam, Kenya, and Switzerland and Status of Forces Agreements (SOFA) requirements and how these processes will be implemented in order to formulate a strategy for executing critical collaborative international engagements in meeting the requirements stated within the PWS.
L.3.2.1.4 The Offeror shall describe the established previous and current international relationships, detail their approach to maintaining these relationships, provide a list of critical key points of contacts (POC’s) in each partner country mentioned above and processes of migrating contractor personnel in/out within those countries.
L.3.2.1.5 The Offeror shall discuss its approach to providing and executing support to the following Threat Reduction Networks (TRN’s)/pathogens: Bat / One Health Research Network (BOHRN), Rickettsial Pathogens, and Melioidosis in accordance with the requirements of paragraph 3.2 and 3.3 of the PWS. The Offeror shall discuss how the Government Program Manager will be supported in each partner country in accordance with these TRN’s within specific areas, to include interim support, logistics of its engagement activities and in-country TRN’s, mitigation plans, emergent country engagements, coordination with interagency partner and partner countries and strategic planning and rapid emergency response support and how these methods will be implemented. The Offeror shall provide specific experience within each partner county utilizing the related pathogen and their approach to exercise and training facilitation, design, science communication, rapid emergency planning solutions, and frameworks for enabling information exchange as it relates to events such as large conferences, workshop trainings, and working group meetings.
L.3.2.1.6 Travel: Offerors shall include a travel and subsistence schedule, indicating the number of trips contemplated, the purpose of each trip, the number of people involved, duration, and itinerary for each trip in accordance with the PWS.
L.3.2.2 Volume II – Program Management Approach
L.3.2.2.1 Management. The Offeror shall clearly describe the work to be performed by both them as a prime contractor and subcontractor, if applicable, in accordance with the PWS and include a detailed discussion as to how this work will be managed and implemented with appropriate oversight.
L.3.2.2.2 Performance Risk Management. The Offeror shall identify risks and provide mitigation strategies and contingencies to address the identified risks in relation to the work in accordance to the requirements of the
PWS.
L.3.2.2.3 Schedule Risk Management. The Offeror shall include a discussion of the potential high-risk features of the work that may adversely impact the schedule and the Offeror's plan to mitigate those high-risk features.
The Offeror shall discuss its scheduling capabilities and procedures to be used for tasks under this contract, which shall include availability of resources, schedule updates, incorporating modifications into the schedule and other steps to be taken to maintain the schedule. In addition, the Offeror shall discuss method(s) of managing workload fluctuation periods, including anticipated Government surge and emergency requirements, in accordance with paragraph 3.5 of the PWS, and the identification and management of critical resources. The Offeror shall cite specific examples of previously satisfactorily completed work to demonstrate relevant experience.
L.3.2.3 Volume III – Past Performance
L.3.2.3.1 The Offeror is responsible for including sufficient details to permit a complete and accurate evaluation of the Offeror’s probability of meeting the RFP requirements.
L.3.2.3.2 Format: Information contained in this section of the proposal will be used for a Past Performance Evaluation.
L.3.2.3.3 Content: The Past Performance Volume shall contain the following:
L.3.2.3.4 This volume shall demonstrate past performance information regarding similar contracts. This volume shall not exceed ten pages plus five pages for each major subcontractor, excluding Past Performance Questionnaire Forms. Offerors shall submit all relevant Government and/or commercial contracts for the prime Offeror and each major subcontractor in performance or awarded during the past three years from the issue date of this RFP. Relevant efforts are defined as efforts that are the same or similar to the effort as compared to the North American Industry Classification Code (NAICS) code 541715 required by the RFP.
L.3.2.3.5 Offeror shall use formatting guidelines as referenced in Section L.2.1 and L.2.3. The Offeror may provide information regarding any awards received for work done on any of the projects described by the Offeror.
L.3.2.3.6 Data concerning the Offeror shall be provided first, followed by each proposed major subcontractor, in alphabetical order. The Offeror shall submit the written consent of its major subcontractors to allow the disclosure of its subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors for their past performance to be considered.
L.3.2.3.7 This volume shall be organized into the following sections:
L.3.2.3.7.1 Section One – Contract Descriptions: This section shall include the following information in the following format:
L.3.2.3.7.1.1 Contractor/Subcontractor place of performance, CAGE Code and DUNS Number. If the work was performed as a subcontractor; provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization, name, current address, E-mail address, and telephone and fax numbers.
L.3.2.3.7.1.2 Government contracting activity, current address, Procuring Contracting Officer’s (PCO’s) name, e-mail address, and telephone and fax numbers.
L.3.2.3.7.1.3 Government’s technical representative/Contracting Officer’s Representative (COR), current e-mail address, and telephone and fax number.
L.3.2.3.7.1.4 Government contract administration activity, Administrative Contracting Officer’s (ACO) name, current e-mail address, and telephone and fax number.
L.3.2.3.7.1.5 Government contract administration activity’s Pre-award Monitor’s name, current e-mail address, and telephone and fax number.
L.3.2.3.7.1.6 Contract Number and, in the case of Indefinite Delivery Indefinite Quantity (IDIQ) type contracts, General Services Administrative (GSA) contracts, and Blanket Purchase Agreements (BPA’s), Delivery/Task Order numbers.
L.3.2.3.7.1.7 Contract Type, such as Firm Fixed Price (FFP), Cost Reimbursement (CR), Time and Material (T&M), etc. In the case of Indefinite Delivery Indefinite Quantity (IDIQ) contracts, please indicate the specific type, such as a Requirements, Definite Quantity, and Indefinite Quantity, and Delivery Order/Task Order contract type, to include FFP, CR, T&M, etc.
L.3.2.3.7.1.8 Awarded price/cost.
L.3.2.3.7.1.9 Final or projected final price/cost.
L.3.2.3.7.1.10 Original delivery schedule, to include dates of start and completion of work.
L.3.2.3.7.1.11 Final or projected final, delivery schedule, to include dates of start and completion of work.
L.3.2.3.7.2 Performance. Offerors shall provide a specific narrative explanation of each contract listed in Section One, Contract Description, describing the objectives achieved and detailing how the effort is relevant to the requirement of this RFP.
L.3.2.3.7.2.1 For any contracts that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcomings and any corrective action(s) taken to avoid recurrence. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. All requests for Deviation and Requests for Waiver shall be addressed with respect to causes and corrective actions. The Offerors shall provide copies of any Cure Notices or Show Cause Letters received on each contract listed and a description of any corrective action implemented by the Offeror or proposed subcontractor. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.
L.3.2.3.7.3 Subcontracts. Offerors shall provide an outline of how the effort required by the RFP will be assigned for performance within the Offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, DUNS Number and type of work to be performed by citing the applicable Government PWS subparagraph number. This includes all subcontractors who will be providing critical hardware/services or whose subcontract is for more than 25% of the total proposed cost/price. This section will further include written consent of major subcontractors to allow the disclosure of their subcontractor’s past performance information to the Offeror. In addition, letters of commitment shall be included for all major subcontractors.
L.3.2.3.7.4 New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above. Letters of Commitment shall be included in the proposal for these employees in order to be considered.
L.3.2.3.7.5 Past Performance Questionnaire. For all contracts identified in Section one, Contract Descriptions, a Past Performance Questionnaire must be completed and submitted. The Offeror shall complete Part I of the Past Performance Questionnaire and e-mail the questionnaire to both the Government contracting activity and technical representative responsible for the past/current contract. The Offeror shall instruct the POCs to electronically complete Part II of the questionnaire and e-mail the entire questionnaire to the Contracting Office no later than the proposal due date, to Contract Specialist, Sheila.l.ramos2.civ@mail.mil and Contracting Officer, Nicholas.granata.civ@mail.mil. The Offeror shall e-mail to the Contracting Office a list of all the POC’s who were sent a questionnaire. The Government must receive this list no later than the proposal due date. The POC List shall be submitted in Word for Windows Table Format to include the following fields:
Solicitation Number; Company Name; Contract Number; Government Agency; POC Last Name, First Name;
POC Title; POC Telephone Number; POC E-mail Address; and Date E- Mailed to POC (month/day). Blank past performance questionnaires can be found in Section J as Appendix A.
L.3.2.3.7.6 Submissions. Offerors are discouraged from providing points of contact with another Contractors’ facility, i.e., in case an Offeror (or one of his/her team members) is in a subcontract with another Contractor who has submitted a proposal on the same requirement. Offerors shall provide and submit the prime contract number and all Governmental agency points of contact (POC) in lieu of subcontract numbers or prime contract POCs in situations as described above.
L.3.2.4 Volume IV – Cost or Price
L.3.2.4.1 General Instructions. In accordance with FAR 15.402 and FAR 15.403-1, certified cost or pricing data are not required based on the fact that adequate competition is expected for this procurement. Information other than certified cost or pricing data may be provided in contractor format providing that sufficient information is made available. Information submitted shall be prepared in accordance with the instruction in FAR 15.403-5 (b)(2). If after receipt of proposals the Contracting Officer determines that there is insufficient information available to determine price reasonableness and none of the exceptions at FAR 15.403-1 apply, the Offeror shall be required to submit cost or pricing data. In the event that adequate competition is not obtained, the Contracting Officer may incorporate FAR 52.215-20 titled “Requirements for Cost or Pricing Data or Information Other Than Cost of Pricing Data’, into the solicitation and request a Certificate of Current Cost or Pricing Data. No Page limitations exist for this volume. Proposal information included in this volume which is not directly related to Cost or Price will be disregarded.
L.3.2.4.1.1 The Offeror's proposal shall contain a "Cost Narrative (Word or PDF) and a "Cost Proposal” (Excel).
L.3.2.4.1.2 The Offeror shall provide a breakout of resources (labor categories, hours, materials, etc.) that are proposed for each priced CLIN from 0001,0002, 1001 and 1002 excluding "Accounting for Contract Services" and “Data Deliverables” CLINS. On CLINs that will be evaluated for cost realism (0001 and 1001) the Offeror shall ensure that proposed resources presented in the Cost or Price Volume match those proposed in the Uncosted Volume. This volume shall be void of all pricing data.
L.3.2.4.2 Subcontracts: Resources that will be provided via subcontracts greater than $100,000 shall also be broken out to be considered as part of the Offeror's technical approach by Government evaluators.
L.3.2.4.3 At minimum, Offeror's breakouts of proposed resources shall include:
L.3.2.4.4 Detailed breakouts of equipment and materials, as appropriate, identifying specific equipment and showing specific materials that will be required. Estimated quantities for materials and equipment shall also be included. The Offeror shall include information clearly identifying any/all spare and repair parts.
L.3.2.4.5 Labor matrices structured by effort identifying all the personnel to be used during the effort, the hours each person will be assigned, the individual's labor category, typical experience level, and individuals’ responsibilities. The requirement for individual’s responsibility shall be provided for CLINs 0001, 0002, 1001 and 1002 only.
L.3.2.4.6 Cost Narrative [doc(x)/pdf]: The primary purpose of this document is to provide factual documentation that supports the accuracy of proposed rates in the Excel Cost Proposal. Offerors are discouraged from duplicating tables shown in the Excel “Cost Proposal” workbook.
L.3.2.4.6.1 Cost Narrative Contents: This file shall contain the following sections:
L.3.2.4.6.2 Table of Contents: Identifies the location of required Cost Narrative sections.
L.3.2.4.6.3 Identifying Information: The name and address of the Offeror; solicitation number; name, email address, and phone number of the point of contact and alternate; and a list containing either DUNS number or CAGE code for the prime contractor and each subcontractor.
L.3.2.4.6.4 Cost Accounting Business System: The successful Offeror is required by FAR 16.301-3 to have an adequate accounting system. The adequacy of a contractor’s accounting system is determined in a review performed by the cognizant Defense Contract Audit Agency (DCAA). The Offeror shall state Offeror if the submitted proposal is consistent with established estimating and accounting principles and procedures and FAR Part 31 (Contract Cost Principles and Procedures), explaining any identified inconsistencies. If the Offeror lacks a DCAA approved Cost Accounting Business System, the Offeror shall identify their timeline to obtain approval for this business system subject to receipt of award.
L.3.2.4.6.5 Direct Labor: Proposed labor categories shall be specific to a job function (e.g. “Chemist”, “Electrical Engineer”, “Budget Analyst”; not “Scientist”, “Engineer”, “Analyst”). For each labor category provide 1) typical education and years of experience, 2) a brief (one sentence will suffice) description of job duties, 3) if proposed labor will be composed of mostly current employees or new hires, and 4) how proposed labor rates were estimated (e.g. category average of current employees, pay rate of current employee, letter of intent, labor statistics such as http://data.bls.gov/oes/, etc.). See the following as an example:
Software Applications Developer, mid (4 year degree, 4+ years of experience): Develop, create, and modify general computer applications software or specialized utility programs.
Employee Makeup: Current Workforce. Basis of Estimate: Payroll Data.
L.3.2.4.6.6 Escalation: Provide the rationale behind proposed escalation for Direct Labor Rates.
L.3.2.4.6.7 Indirect Expense Rates: Provisional Billing Rates will not be accepted as a basis for proposed indirect rates. Proposed indirect expense rates shall be supported by one of the following:
a) A copy of a Forward Pricing Rate Agreement;
b) A copy of a Forward Pricing Rate Recommendation;
c) A copy of a DCAA audit or DCMA review of indirect rates incurred during a period within the past two years from the RFP due date;
d) Claimed/actual indirect expense pool, allocation base, and rate data for the past two fiscal years; or
e) An agreement to cap reimbursable indirect expense rates at proposed amounts in accordance with FAR 42.707.
If proposed indirect rates are significantly different than would be supported by one of the above required methods, Offerors shall provide supporting documentation of any proposed rate inconsistencies and provide substantiation of calculations.
L.3.2.4.6.8 Cost Reimbursable Subcontracts, if applicable: Provide a quote for each subcontract greater than $100,00 that supports how the Offeror arrived at the subcontractor’s proposed price and quantities of uncosted elements (e.g. labor hours, material quantities, etc.) presented in the Excel Cost Proposal A Cost Narrative and Cost Proposal shall be provided to the Government for subcontracts greater than $100,000 with the same level of detail as is required of the Prime Offeror (may be provided by either the Prime or Subcontractor). In accordance with FAR 15.404-3, the Offerors shall perform a cost or price analysis of all the proposed subcontractor prices.
L.3.2.4.6.9 Travel: Proposed travel costs do not need to be addressed in the Cost Narrative. Travel and associated indirect costs will be paid by the Government under a Cost (no fee) CLIN.
L.3.2.4.6.10 Equipment, Materials, and ODCs: The Offeror shall fully describe how it arrived at proposed equipment, material, and other direct costs; and provide data used to arrive at the specific dollar value proposed.
Any analogous or parametric estimate used must be supplemented by data and calculations used to arrive at proposed rates and/or dollar values. All equipment, materials, and ODCs that contribute more than $10,000 in proposed costs shall be supported by vendor/supplier quotes, catalog pricing, or historical pricing documentation.
L.3.2.4.6.11 Fixed Fee. Any fixed fee dollar amount may be proposed up to an amount equating to 15% of estimated costs (FCCOM is not included in estimated costs, as it is based on the six month treasury rate, not actual expenses). In accordance with FAR 15.404-4(c)(4)(i)(A) and based on 10 USC 2306(d) and 41USC3905, Contracting Officers are prohibited from awarding more than this amount, which could cause Offerors with a fixed fee amount exceeding 15% of estimated costs to not be considered for award unless the Government voluntarily enters into discussions to allow revisions. The effective fixed fee percentage proposed will be incorporated into any resulting contract for CPFF CLINs.
L.3.2.4.7 Cost Proposal [xls(x)]: This workbook should use formulas to the maximum extent practical to ensure costs accurately roll up to the overall proposed evaluated price. Offerors shall neither lock cells nor make cell references to outside files.
L.3.2.4.7.1 The cost proposal shall accurately arrive at proposed costs (e.g. ensuring proper allocation bases are used for indirect expenses, adding feeder tabs to make proposal preparation easier, showing calculations for weighted average rates if needed, adding/deleting rows, etc.). Spreadsheets shall be sent in an unlocked workbook that includes all formulas, macro, and format information. No links to external worksheets or workbooks are acceptable. Hard keyed data/numbers entered into spreadsheets are discouraged. Any cell with a hard keyed data/number must be referenced to source documentation contained within the cost proposal. Print image is not acceptable. Offerors have discretion to edit the template as needed, so long as a similar level of detail and conciseness is provided. Each subcontractor, if applicable, shall have its proposed cost broken out on a separate tab: Cost reimbursable subcontracts under $100,000 need only fully loaded rates and quantities of uncosted elements (e.g. labor categories, materials, etc.); while cost reimbursable subcontracts over $100,000 shall have costs broken out with the same level of detail required of the prime and may be submitted by the subcontractor directly to the Government.
L.3.2.4.7.2 Standard Form 33 [doc(x)/pdf]: Provide a completed copy of Standard Form 33 and continuation sheets (if applicable) to include acknowledgement of all amendments to the RFP and a completed Section B.
L.3.2.4.7.3 Excel Cost Proposal Contents: This workbook shall contain the following:
L.3.2.4.7.4 Summary Tab: This tab shall show a summary level rollup of proposed prices for each CLIN.
L.3.2.4.7.5 CPFF Tabs: For each CPFF CLINs (CLINs 0001 & 1001) The Offeror shall breakout the proposed CPFF by cost element (direct labor, applicable indirect expenses, materials, travel, fixed fee, etc.), broken out either by fiscal or calendar year.
L.3.2.4.7.6 Travel Tab: This tab will show a breakout of travel costs proposed for CLINs 0002 and 1002.
L3.2.4.7.7 Cost reimbursable type subcontracts (e.g., CPFF, etc.): Provide the same level of detail required of the prime Offeror. If the prime Offeror is unable to provide this level of detail due to the subcontractor deeming this level of detail to be proprietary, then the Offeror shall at minimum provide uncosted elements and fully loaded rates that the subcontractor is proposing AND the subcontractor shall provide the required level of detail directly to the Government by the date and time that proposals must be delivered.
L.3.2.4.8 Notices to Prospective Offerors:
L.3.2.4.8.1 Pricing Validity Duration: Prices that Offerors propose in response to this solicitation shall remain valid for at least ninety (90) days after the date that proposals are due or, if applicable, the date that any proposal revisions are due by, whichever date is later.
L.3.2.4.8.2 Restricting Pricing Data to Cost/Price Volume: The Offeror shall include cost information ONLY in Volume IV—Cost or Price. Inclusion of cost data in Volumes I through III and Volume V will not be considered and the pages with the cost data in these volumes will be removed from the proposal prior to evaluation.
L.3.2.5 Volume V – Solicitations, Offer, and Award Documents, and Certifications and Representations.
L.3.2.5.1 Certifications and Representations – Each Offeror shall complete (fill-in and signatures) the solicitation sections indicated below using the file (without modification to the file) provided with the RFP.
An authorized official of the firm shall sign the SF 33 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission.
L.3.2.5.1.2 Section A – Standard Form 33 (SF33), Solicitation, Offer and Award
L.3.2.5.1.3 Section G – Contract Administration Data
L.3.2.5.1.4 Section K – Representations, Certifications and Other statement of Offerors
L.3.2.5.2 Solicitations, Offer, and Award Documentation and Certifications/Representations shall not be addressed separately from that submitted in Volume V.
L. 4 CONFIDENTIAL INFORMATION
L.4.1 The Freedom of Information Act (FOIA) and its amendments have resulted in an increasing number of requests from outside the Government for copies of contract qualifications and proposals submitted to federal agencies. If an Offeror’s submission contains information that it believes should be withheld from such requestors under FOIA on the grounds that they contain trade secrets and commercial or financial information [5 USC§552(b)(4)], the Offeror should mark its submissions in the following manner:
L.4.1.1 The following notice should be placed on the title page: “Some parts of this document, as identified on individual pages, are considered by the submitter to be privileged or confidential trade secrets or commercial or financial information not subject to mandatory disclosure under the Freedom of Information Act. Material considered privileged or confidential on such grounds is contained on page(s) .”
L.4.1.2 Each individual item considered privileged or confidential under FOIA should be marked with the following notice: “This data or information is considered confidential or privileged, and is not subject to mandatory disclosure under the Freedom of Information Act.”
L.4.2 Restriction of Disclosure/Proprietary Information. If the Offeror wishes to restrict the disclosure or use of its proposal, the legend permitted by FAR 52.215-1(e) shall be used.
L.5 Security Clearance
L.5.1 In the event that the Offeror does not hold a security clearance, in accordance with the DD Form 254 attachment 15 in Section J, the CCDC CBC Security office will be able to sponsor the Offeror. The Offeror shall complete with the following requirements for sponsorship during the pre-award phase:
L.5.2 Complete Facility Clearance (FCL) Request Form on Company letterhead (Section J of the solicitation) and submit the request form to contracting specialist, sheila.l.ramos2.civ@mail.mil and the contract officer, Nicholas Granata Jr at Nicholas.granata.civ@mail.mil .The Government will submit the FCL request letter and a copy of the DD254 to the Defense Security Service (DSS) Facility Clearance Branch (FCB) for processing.
L.5.3 The FCL requirements are set forth in the National Industrial Security Program (NISP) and the specifics are spelled out in the National Industrial Security Program Operating Manual (NISPOM).
L5.4 The Offeror shall possess, or acquire prior to award of the contract, a facility clearance equal to the highest classification stated on the Contract Security Classification Specification (DD Form 245) attached to this solicitation.
L.6 Acquisition Source Selection Interactive Support Tool (ASSIST)
L.6.1 During the conduct of this acquisition, the ASSIST will be used by the Government to support the proposal evaluation and source selection process. A separate tool, the ASSIST2Industry, will be used in conjunction with ASSIST to accomplish all exchanges with Offerors after receipt of proposals pursuant to Federal Acquisition Regulation (FAR) 15.306. ASSIST2Industry provides the ability for the Government to issue, and the Offerors to receive and respond to, all Evaluation Notices (ENs) in a secure online environment.
L.6.2 In order to initiate the use of ASSIST2Industry, the Offeror shall provide the names, company titles, telephone numbers, and email addresses of two (2) individuals that the Offeror has designated as responsible for exchanges and for receiving and responding to Government ENs, if applicable through ASSIST2Industry. The designation of two (2) individuals is for the purpose of insuring availability of one individual if the other individual is not available. The required information regarding these two (2) individuals must be submitted with the Offeror’s proposal and included in the cover letter.
L.6.3 After the solicitation’s closing date, the Government will establish an account in ASSIST2Industry for each individual identified by the Offeror that has submitted a proposal in response to this solicitation. The two individuals named by the Offeror will be authorized access to that account. Two (2) separate system generated emails will be sent to each individual. One of the emails will contain the individual’s ASSIST2Industry username. The other email will contain the individual’s temporary password. Using the provided username and temporary password, each individual can then go to https://ASSIST2Industry.army.mil to access the account.
NOTE: The first time a user logs in, the user will be required to change the temporary password before the user can proceed to use the site.
L.6.4 Whenever the Government issues ENs to the Offeror through ASSIST2Industry, the Government’s Contracting Officer will notify the Offeror through a medium independent of ASSIST2Industry ( e.g., e-mail) that the Offeror has ENs in ASSIST2Industry waiting for a response. There will be no ENs in ASSIST2Industry until such notice is issued by the Contracting Officer.
L.6.5 Offerors are cautioned that the system generated emails referred to above are intended for administrative purposes only. Receipt of these emails does not constitute the commencement of any type of exchange with the Offeror in accordance with far 15.306(a), (b), or (d) (i.e., clarifications, communications, or discussions). Also, receipt of these emails does not signify that a competitive range determination in accordance with far 15.306(c) has been made or that the Offeror’s proposal will be included in the competitive range when that determination is made. All notifications that any type of exchange with the Offeror has commenced and the Offeror has evaluation notices (ENs) available to respond to, or any notification that the Offeror’s proposal has been included in or excluded from the competitive range, will be sent to the Offeror by the contracting officer independently of the Assist2industry
L.6.6 Both Prime Contractors and Sub Contractors are instructed to review the ASSIST2Industry User’s Guide, located under the “Getting Started” tab on the website. The guide has been updated and provides step by step instructions on how to perform functions and navigate the website. Offerors can contact the ASSIST2Industry helpdesk at 1-866-335-2769 (ARMY), #Option 7 for any technical assistance that may be needed".
SECTION M - EVALUATION FACTORS FOR AWARD
The following have been modified:
EVALUATION CRITERIA
Section M - Evaluation Factors for Award
M.1 Evaluation Process
M.1.1 All proposals received pursuant to the Request for Proposal (RFP) will be fully evaluated in a careful and impartial manner. All factors against which proposals will be evaluated are described in this section. The proposal will be evaluated to determine the extent to which the proposed approach is practical and the end results achievable. The proposal will be evaluated to determine whether the Offeror’s methods and approach provide the Government with a high level of confidence of successful completion.
M.1.2 Basis for Contract Award
M.1.2.1. Award will be made to the Offeror(s) whose proposal(s) represents the best value to the Government by applying the tradeoff process described in FAR 15.101-1. Accordingly, the Government may award a resulting contract to other than the lowest evaluated priced Offeror, or to other than an Offeror with the highest technical rating. The basis for award of a contract will be the results of the proposal evaluations of all of the factors set forth herein, giving due consideration to the relative order of importance indicated herein. Ultimately, the source selection decision will take into account the Offeror’s capability to meet the requirements of this RFP at a reasonable cost as determined by the best value selection process.
M.1.3 Competitive Range
M.1.3.1 The PCO will make the determination as to which proposals are in the Competitive Range. Pursuant to FAR 15.306, the PCO shall establish a competitive range comprised of all of the most highly rated proposals based on the ratings of each proposal against the evaluation criteria. The initial number of proposals considered as being within the competitive range may be reduced when, as a result of written or oral discussions, a proposal is determined to no longer have a reasonable chance of being selected for award. The number of most highly rated proposals that might otherwise be included in the competitive range may be limited to the greatest number that will permit an efficient competition among the most highly rated proposals and in accordance with Paragraph M.1.2.1 above.
M.1.4 Final Evaluation of Proposals
M.1.4.1 The contracting officer will allow proposal revisions as the result of discussions. At the conclusion of discussions, each Offeror still in the competitive range shall be given an opportunity to submit a final proposal revision. The PCO will establish a common cut-off date only for receipt of final proposal revisions.
Requests for final proposal revisions will advise Offerors that the final proposal revisions shall be in writing and that the Government intends to make award without obtaining further revisions.
M.2 Evaluation Approach
M.2.1 All proposals will be evaluated to determine the Offeror’s ability to successfully complete the RFP requirements within the required schedule. The evaluation team will use the Department of Defense Source Selection Procedures document, the Army Source Selection Supplement (AS3) to the Department of Defense Source Selection Procedures, along with advice and guidance from the PCO to conduct the evaluation. All factors against which proposals will be evaluated are described below, and generally parallel the proposal instructions in Section L. All proposals will be evaluated by a team of individuals using the following evaluation approach:
M.2.1.1 Technical Approach Factor. Technical Approach factor will receive an adjectival combined technical/risk rating along with narrative evaluation.
M.2.1.2 Program Management Factor. The Program Management approach factor will receive an adjectival combined technical/risk rating along with a narrative evaluation.
M.2.1.3 Past Performance Factor. Each Offeror's past performance will be reviewed by the Government to determine recency, relevancy and receive a rating of “acceptable” or “unacceptable”, along with the narrative evaluation.
M.2.1.4 Cost or Price Factor. The Cost or Price Factor will not receive an adjectival rating but will be evaluated with a narrative for realism, reasonableness, and completeness. The uncosted information will be used as part of the cost realism analysis to determine cost realism. The results of the cost realism analysis will determine the probable cost of performance. Probable cost will be used in the final evaluation to determine best value.
M.3 Evaluation Factors and Relative Order of Importance
M.3.1 Evaluation Factors. Each Offeror’s proposal will be evaluated on the extent to which it demonstrates responsiveness to each of the evaluation factors. The evaluation factors are as shown in Table M-1.The relative order of importance is set forth in M.3.2.
Table M-1: Evaluation
Factors
Factor Description Technical Approach
Program Management Approach
Past Performance Cost or Price Certification and Representations
M.3.2 Relative Order of Importance. The Technical Approach and Program Management approach are of equal importance and when combined, are significantly more important than the than the Past Performance Factor, which is substantially more important than the cost or price factor. All evaluation factors other than Cost or Price, when combined, are significantly more important to the Cost/Price factor in accordance with FAR 15.304(e) (2).
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 .