W56HZV15R0086-0003.pdf
PDF 46 KB Posted
- Attached to
- HAZARD-DETECTING INSTRUMENTS AND APPARATUS
- Solicitation number
- W56HZV15R0086
About this file
Conformed copy of RFP to include amendments up to 0003
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 17Mar17Update.pdf | ||
| W56HVZ15R0086conformed17Jan2017.pdf | ||
| Q&A_7_19January2017.pdf | ||
| W56HZV15R0086-0003.pdf | ||
| W56HZV15R0086-0001.pdf | ||
| Q&A__6__23_Dec.pdf | ||
| Q&A_5_23_Dec.pdf | ||
| Q&A_4_20_Dec.pdf | ||
| Q&A_3_16_Dec.pdf | ||
| Q&A__2_13Dec.pdf | ||
| MTRS_PPC_Attendee_List.pdf | ||
| Q A_1_23Nov2016.pdf | ||
| MTRS_Inc_II_Pre-Proposal_Conf.pdf | ||
| W56HZV15R0086.pdf | ||
| Distribution_A_Attachments.zip | ZIP file | |
| Exhibit_C_Tailored_DIDs.pdf |
Show all 16
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code Page Of
2. Amendment/Modification No.
3. Effective Date
4. Requisition/Purchase Req No.
5. Project No. (If applicable)
6. Issued By Code 7. Administered By (If other than Item 6) Code
8. Name And Address Of Contractor (No., Street, City, County, State and Zip Code)
9A. Amendment Of Solicitation No.
9B. Dated (See Item 11)
10A. Modification Of Contract/Order No.
10B. Dated (See Item 13) Code Facility Code
11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS
The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers is extended, is not extended.
Offers 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 ____________ copies of the amendments: (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 ONLY APPLIES TO MODIFICATIONS OF CONTRACTS/ORDERS
It Modifies The Contract/Order No. As Described In Item 14.
A. This Change Order is Issued Pursuant To: 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 data, 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.)
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)
16A. Name And Title Of Contracting Officer (Type or print)
15B. Contractor/Offeror 15C. Date Signed 16B. United States Of America 16C. Date Signed
By (Signature of person authorized to sign) (Signature of Contracting Officer)
NSN 7540-01-152-8070
PREVIOUS EDITIONS UNUSABLE
30-105-02 STANDARD FORM 30 (REV. 10-83)
Prescribed by GSA FAR (48 CFR) 53.243
SEE SCHEDULE
X
Firm Fixed Price
0003 2017JAN17
W56HZV
U.S. ARMY CONTRACTING COMMAND
WARREN, MICHIGAN 48397-5000
KAREN BLASKY
EMAIL: KAREN.E.BLASKY.CIV@MAIL.MIL
W56HZV-15-R-0086
2016NOV09
X
X
/SIGNED/
2 signed
SEE SECOND PAGE FOR DESCRIPTION
1 14
CONTINUATION SHEET
Reference No. of Document Being Continued Page of
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION A - SUPPLEMENTAL INFORMATION
Buyer Name: KAREN BLASKY
Buyer Office Symbol/Telephone Number: CCTA-HCP-D/(586)282-4011
Type of Contract 1: Firm Fixed Price
Kind of Contract: System Acquisition Contracts
*** End of Narrative A0000 ***
Amendment 0003
1. Please note that Amendment 0002 will not be utilized. The purpose of Amendment 0003 to solicitation W56HZV-15-R-0086 is to incorporate the following change:
SECTION L
L.2.2.3 Proposal Submission Instructions
Delete: The entire proposal shall be sent in a single AMRDEC transmission.
2. The solicitation closing date has NOT changed as a result of Amendment 0003. All other terms and conditions remain unchanged and in full force and effect.
*** END OF NARRATIVE A0003 ***
2 14
W56HZV-15-R-0086 0003
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
SECTION L - INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS
L.1 General Proposal Information
L.1.1 The proposal, subject to the Submission, Modification, Revision, and Withdrawal paragraph of Instructions to Offeror(s)
Competitive Acquisitions Federal Acquisition Regulation ((FAR) Provision 52.215-1, ALT I) contained in Section L of the solicitation, shall be submitted in the format and quantities set forth below. All information necessary for the review and evaluation of a proposal is to be contained in the proposal volumes set forth below. Section M of the solicitation sets forth the evaluation criteria and delineates the Factors to be evaluated and their relative order of importance. The offerors proposal, as required by this section, shall be evaluated as set forth in Section M of this solicitation. The Government will not assume the offeror possesses any capability, understanding, or commitment not specified in its proposal. It is an offerors responsibility to submit a well-written proposal, with adequately detailed information, which clearly demonstrates an understanding of and the ability to comply with the solicitation requirements to allow for a meaningful evaluation. The Government does not assume the duty to search for data to cure problems it finds in proposals. Each volume of the offerors proposal shall be consistent with the other proposal volumes and shall demonstrate the understanding and ability to perform according to the statement of work of the contract.
L.2 Proposal Content, Format and Instructions
L.2.1 Proposal Content
L.2.1.1 All proposals shall be in the English language (American Standard) and currency shall be in U.S. Dollars (USD). The proposal shall include all information specified and address all requirements outlined in Section L. The offeror shall submit six separate volumes as set forth below:
Volume
Number Title Quantity______ ______ ________
Volume I Performance Factor 1
Volume II Payload Integration Maturity Factor 1
Volume III Price Factor 1
Volume IV Past Performance Factor 1
Volume V Small Business Participation Factor 1
Volume VI Proposal Terms and Conditions 1
L.2.1.2 A Proposal Executive Summary or transmittal letter is optional. It will neither be considered as part of the volumes required, nor will it be evaluated. If a Proposal Executive Summary is submitted, it must be submitted as a separate volume from the six volumes set forth above and it should be no more than five pages in length and appropriately labeled.
L.2.1.3 Offerors shall not include citations for, or linkages to websites in the proposal.
L.2.2 Proposal Format and Instructions
L.2.2.1 RESERVED
L.2.2.1.1 RESERVED
L.2.2.1.1.1 No portion of the offeror's proposal shall contain classified information. Any Controlled Unclassified Information (CUI) contained in the proposal shall be handled in accordance with Attachment 0066, DD-254, specifically, the section titled, Additional
Guidelines for Controlled Unclassified Information.
L.2.2.1.2 Acceptable File Formats. All electronic information provided in response to the solicitation must be provided in Microsoft
(MS) Office 2013 or PDF compatible format or except as noted in instructions for individual volumes. For Modeling and Simulation Data the following formats are acceptable: CREO native, ISO 10303 STEP standards, or AutoCAD native (dwg/dxf), PDF and \formats.
L.2.2.1.3 Unless otherwise specified, it is recommended that proposal be formatted for 8.5 x 11 paper with a minimum font size of 10 pt.
and with a minimum of 0.5 margins. Schedules, drawings and other documents more appropriate to larger size shall be formatted for no larger than 11 x 17 dimensions. All spreadsheets must include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all Rows, Columns, Cells, and Worksheets must be visible. Zero height and zero width rows and columns in Worksheets are not acceptable. Worksheet cells formatted with the font color equal to the fill color are unacceptable. If Workbooks or Worksheets are password protected, then the passwords must be provided. Print image files, pictures, or files containing only values are not acceptable.
L.2.2.2 Submission Due Date
The offeror must ensure its proposal, in its entirety, reaches its intended destination before the date and time set for closing of the solicitation set forth in Block 9 on the SF 33, front page of the solicitation.
3 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
L.2.2.2.1 Lateness
The lateness rules for submitted proposals are outlined in FAR 52.215-1 "Instructions to Offerors-Competitive Acquisition," and are incorporated in to this solicitation.
L.2.2.3 Proposal Submission Instructions
Electronic submission is mandatory. Paper offers will not be accepted. Proposals shall be submitted electronically through the Aviation and Missile Research Development and Engineering Center (AMRDEC) Safe Access File Exchange (SAFE), which can be accessed at the following link: https://safe.amrdec.army.mil/SAFE.
When submitting a proposal to AMRDEC, the offerors shall specifically authorize access to their proposal to the following persons:
a. Contract Specialist Karen Blasky - mailto:Karen.e.blasky.civ@mail.mil
b. Procuring Contracting Officer: Keith Ahlstrom - mailto:keith.w.ahlstrom.civ@mail.mil
Once the proposal has been submitted to AMRDEC SAFE, the offeror shall send an electronic mail message to the same persons identified in
(a) and (b) above with the subject line: [Offeror Name], Proposal_W56HZV-15-R-0086. The offerors email shall include a screenshot of their submission to the AMRDEC SAFE site. Refer to Attachment 0036, AMRDEC SAFE Instructions for direction on how to upload files to the
AMRDEC SAFE site. AMRDEC SAFE is the initial point of entry to the Government infrastructure for determining lateness of a proposal pursuant to FAR 52.215-1(c)(3)(ii)(A).
L.2.2.3.1 Please pay close attention to the solicitation closing date and time as stated on the cover page of this solicitation, local time for the Army contracting Command - Warren, (DTA), Michigan. In accordance with FAR 15.208(a), offerors are responsible for submitting proposals, and any revisions, and modifications, so as to be received by the Government office designated in the solicitation by the time specified.
It is the responsibility of the Offeror to ensure the proposal/quote is received by the date and time specified on the cover page of this solicitation. In accordance with FAR 15.208, if the proposal/quote was not received at the initial point of entry to the
Government infrastructure (in this case, received through AMRDEC SAFE) by the exact date and time specified on the cover page of this solicitation, it will be determined late. Proposal/quote is defined to mean ALL volumes or parts required in the solicitation are included in the electronic submission.
Note: There is no "expected" or "target" length of time for proposal submission; size and content may be factors, therefore offerors are strongly cautioned when submitting proposals to allow adequate time for submission.
L.2.3 Single Proposal Submission
Offerors are limited to submitting one proposal with one approach to meeting the requirements of this solicitation. An offeror is defined as an entity competing independently that does not share a common parent, does not have a parent/subsidiary relationship with any other offeror, and is not affiliated with any other offeror.
L.2.4 Procedure for Submitting Classified Information:
The Government does not require classified information submitted as substantiating data however, if provided, classified information shall be submitted separately. The classified proposal information shall be either hand carried or submitted via US Mail. Do not submit any classified information with the UNCLASSIFIED volumes listed above. The classified information must be received by the time and date specified for receipt of proposals in block nine of the Standard Form (SF) 33, subject to the late proposal conditions in FAR Provision
52.215-1 ALT 1. When submitting classified information, follow the NISPOM Chapter 5 instructions and DD Form 254 (Attachment 0066) using the below mailing address:
Outer Envelope:
PEO Combat Support & Combat Services Support
AMSTA-CSS/MS 105
Attn: Mail Room_Proposal Related Stamp Time/Date
6501 E. Eleven Mile Road
Warren, MI 48397-5000
Inner Envelope:
AMSTA-CSS/MS 105 Source Selection Board
Attn: Security Manager (Matthew Curis)
6501 E. Eleven Mile Road
Warren, MI 48397-5000
Solicitation Number: W56HZV-15-R-0086
DATE & Time: Refer to Standard Form 33 (Pg. 1), Block 9
TO BE DELIVERED UNOPENED
(Offerors name)
This RFP includes classified information . In order to receive a copy of the classified RFP material, Offerors must provide proof of valid Industrial Facilities Security Clearance by sending an email to: matthew.g.curis.civ@mail.mil with the Company Name, address, CAGE
Code, Facility CAGE Code as per the National Industrial Security Program Operating Manual (NISPOM) DoD 5220.22-M, and basis of the need to know. The Government recommends all requests for the Classified Annexes specify whether the vendor requests a hard copy or an
4 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
electronic copy and that all requests be received within 10 calendar days of RFP release. Requests received greater than 10 calendar days after the RFP release date may not be processed with enough time for the Offeror to submit a proposal which meaningfully responds to the RFP. The Offeror shall provide the contact information for the Facility Security Officer (FSO) in the Offerors request.
L.3 Consistency
Each volume of the offerors proposal shall be consistent with the other proposal volumes and shall demonstrate the understanding and ability to perform according to the statement of work of the contract. The offeror should provide supporting documentation in sufficient detail to permit a complete evaluation of the proposal. The Government may conduct a crosswalk between the information provided in the offerors proposal volumes to assess whether the offeror submits consistent proposal information.
L.4 Evaluation Factors
Offeror proposals shall address the following five Factors:
a. Performance
b. Payload Integration Maturity
c. Price
d. Past Performance
e. Small Business Participation
L.4.1 Volume 1 Performance Factor
The Performance Factor consists of four Subfactors: Recognize Detected Person Low Light and Night, Manipulator Arm, Base Platform, and
Reliability.
A. Proposed Level of Performance
The offeror shall provide a completed copy of Attachment 0067 Performance Requirements Matrix to include the proposed level of performance for each identified requirement under each Performance Subfactor.
B. Substantiating Information
The offeror shall provide substantiating information for each requirement as outlined under each Performance Subfactor below. The substantiating information must support that the offered configuration meets the proposed performance levels identified in Attachment
0067. Substantiating information shall be complete, specific, and relevant to the specific performance levels proposed to be achieved by the offeror for each requirement identified in Attachment 0067. If the substantiating information for one requirement is the same as information cited for another requirement, then the offeror shall reference the previously provided data by volume and page number rather than providing duplicate data.
Where the offeror submits substantiating information for a design configuration that varies from the proposed design configuration or is from a system other than the proposed system, the offeror shall explain how the substantiating information is applicable to the proposed design or proposed system with supporting rationale. This explanation shall describe the extent of the variance and the impact such variances have on the credibility of the substantiating information.
This requirement regarding substantiating information applies to all performance subfactors and the Payload Integration factor.
L.4.1.1 Subfactor 1 Recognize Detected Person Low Light and Night (Reference: MTRS Inc II Performance Specification Section 3.5.4.1.3.1
Recognize Detected Person - Low Light and Night)
The offeror shall provide substantiating information to demonstrate the offered configuration will attain the proposed level of performance for this subfactor in Attachment 0067. Additionally, the offeror shall provide a written narrative consisting of no more than 15 pages detailing how the substantiating information provided demonstrates the offered configuration will meet the level of performance proposed in Attachment 0067.
Examples of substantiating information are as follows:
a. Test results (including pictures taken at the proposed performance level in low light and night conditions), calculations, simulations, and studies. Calculations and modeling and simulation (M&S) results which detail the approach including modeling software used, assumptions, and validation plan and validation status against test data.
b. Commercial literature (detailed technical specifications showing performance details and available field of view details) for each camera in the proposed night and low light vision system.
c. Models, drawings, and images or pictures depicting placement of each camera on the MTRS Inc II chassis.
L.4.1.2 Subfactor 2 Manipulator Arm (Reference: MTRS Inc II Performance Specification 3.5.2.1.1 and 3.5.2.6.1)
5 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
The offeror shall provide substantiating information to demonstrate the offered configuration will attain the proposed level of performance for this subfactor in Attachment 0067. Additionally, the offeror shall provide a written narrative consisting of no more than 15 pages detailing how the substantiating information provided demonstrates the offered configuration will meet the level of performance proposed in Attachment 0067.
Examples of substantiating information are as follows:
a. Test results, calculations, simulations, models, drawings, images, pictures, video of the arms demonstrating each of the degrees of freedom and studies.
b. Commercial literature (detailed technical specifications showing performance details) for the approach in the proposed Manipulator
Arm system.
c. Models, drawings, and images or pictures depicting placement of the manipulator arm on the MTRS Inc II chassis.
L.4.1.3 Subfactor 3 Base Platform (Reference: MTRS Inc II Performance Specification, Sections 3.5.1.1.9.2, Side Slope Traverse Forward;
3.5.1.3.3.1, Climb Stairs; and 3.5.5.1 Continuous Operations).
The offeror shall provide substantiating information to demonstrate the offered configuration will attain the proposed level of performance for this subfactor in Attachment 0067. Additionally, the offeror shall provide a written narrative consisting of no more than 15 pages detailing how the substantiating information provided demonstrates the offered configuration will meet the level of performance proposed in Attachment 0067.
Examples of substantiating information are as follows:
a. Test results, calculations, simulations, and studies.
b. Commercial literature (detailed technical specifications showing performance details) for the approach in the proposed Base Platform system.
c. Models, drawings, and images or pictures depicting placement of the manipulator arm on the MTRS Inc II chassis.
L.4.1.4 Subfactor 4 Reliability (Reference: MTRS Inc II Performance Specification 3.6.2.1.1, Mission Reliability, System Abort)
The offeror shall provide the following substantiating information to demonstrate that the offered configuration will meet the performance proposed in Attachment 0067.
a. A proposed Reliability Program Plan that identifies and describes the planned activities for implementation of the offerors
Reliability and Maintainability (R&M) program. The plan shall further identify and describe the following: (a) the quantitative and qualitative R&M and Built in Test (BIT) requirements associated with the offerors proposed design.; (b) a list of the required R&M and
BIT tasks; (c) the reliability growth planning curve; and (d) Failure Reporting Analysis and Corrective Action System process to be used as well as any other data collection requirements and procedures, including a sample of the failure analysis forms.
b. The offeror shall provide the Mission Reliability, System Abort prediction score calculated in accordance with Attachment 0028
MTRS Inc II Failure Definition and Scoring Criteria (FDSC). For proposal preparation purposes, the offeror shall use the Operational
Summary for RAM, Attachment 0019, in place of the OMS/MP and the Performance Specifications, Attachment 0001, in place of the
Capabilities Production Document (CPD).
c. Analyses to support the prediction score including any reliability test results conducted on the offerors MTRS Inc II prototype, if such testing was performed. Analyses of the MTRS Inc II, subsystems, and components that are not supported by test data shall be clear in the rationale for the prediction and shall provide sufficient information to support the prediction. The analysis shall include the applicable Operating Environment (defined in the MTRS Inc II Performance Specification, section 3.7.2.1.1). Test data, if submitted, shall include the following:
(1) Operating Environment (as defined in the MTRS Inc II Performance Specification, section 3.7.2.1.1) during test;
(2) The number of hours tested and Mission Profile utilized;
(3) A listing of all failures;
(4) Scoring of the failures shall be in accordance with the MTRS Inc II FDS
(5) Offerors root cause analysis of any failures;
(6) Proposed corrective actions to prevent failure recurrence or otherwise improve reliability; and
(7) Point estimate of the resulting Mission Reliability, System Abort and 80% lower confidence limit.
L.4.2. Volume II Payload Integration Maturity Factor
L.4.2.1 The offeror shall provide the following:
6 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
(a) A self-assessment of the proposed level of Payload Integration Maturity in relation to the maturity levels and characteristics described in Attachment 0030 Payload Integration Maturity. The offeror shall self-assess whether each characteristic under each level has been completed for the offerors proposed design by completing Attachment 0030.
(b) The self-assessment shall be accompanied by substantiating information supporting the offeror's asserted extent of maturity for
Payload Integration Maturity. The offeror shall provide substantiating information for each characteristic achieved, within each level identified in Attachment 0030. The resulting technical information, documentation, test data and rationale shall be complete, specific, and relevant to the specific characteristics of the offeror's self-assessment assertions. If the substantiating information applies to a design other than the proposed design solution, the offeror shall provide a narrative that details the extent of the variance and the impact such variance has on the credibility of the substantiating information as well as any additional information that supports the impact to the credibility. Additionally, the offeror shall complete Attachment 0031 (Matrix of Substantiating Data) to support Payload
Integration Maturity.
L.4.3 Volume III Price Factor
All proposed prices shall be in USD, including prices for any subcontractors.
As this is a competitive acquisition, the documentation requested is considered other than certified cost or pricing data. As such, a
Truth In Negotiations Act (TINA) certification is not required. The PCO reserves the right to obtain certified cost or pricing data pursuant to FAR 15.403-4.
In accordance with FAR 15.306, the Government reserves the right to request additional or more detailed information to support its determination of price reasonableness.
Electronic Submission: All spreadsheets must be in Microsoft 2007, 2010, or 2013 format and shall include all formulas, function, macros, computations, or equations used to compute the proposed amounts. For each workbook, all Rows, Columns, Cells, and Worksheets must be visible. Zero height and zero width rows and columns in Worksheets are not acceptable. Worksheet cells formatted with the font color equal to the fill color are unacceptable. If Workbooks or Worksheets are password protected, then the passwords must be provided.
Print image files or pictures or files containing only values are not acceptable. Supporting narratives shall be provided in Microsoft
Word format or PDF file format.
L.4.3.1 Price Attachment 0014. The offeror shall complete Attachment 0014, containing all of the offerors prices as indicated in the attachment. The offeror shall not enter any proposed prices in Section B.
For MTRS Inc II Contract Line Item Numbers (CLINs) (3002AA, 4001AA, 5001AA, 6001AA, 7001AA) the offeror shall propose Firm-Fixed-Price unit prices for each CLIN quantity range shown in Attachment 0014 and in accordance with 52.216-4216, Range Pricing. The offeror may propose the same unit prices for all ranges in each Ordering Year.
For storage CLINS (2004AA, 3003AA, 4002AA, 5002AA, 6001AB, 7001AB) the offeror shall propose storage prices based on one system per day.
L.4.3.2 Data Other Than Cost or Pricing Data. The offeror shall provide the basis used for establishing the proposed prices for all
CLINs, except for Not Separately Priced (NSP) CDRL Exhibit Line Item Numbers (ELINs). This information shall include the other supporting information IAW L.4.3.2.1 through L.4.3.2.11 below. The supporting information is not required for storage CLINs 2004AA, 3003AA, 4002AA, 5002AA, 6001AB, 7001AB.
L.4.3.2.1 For all priced CLINs (except Storage CLINs 2004AA, 3003AA, 4002AA, 5002AA, 6001AB, 7001AB), the offeror shall submit Excel spreadsheets, time-phased by ordering year and organized by cost element (i.e. Direct Labor, Subcontracts, Material, Other Direct Costs, Overhead/Indirect, Profit, etc) that support the proposed prices on a per unit basis (for each quantity range, if applicable).
L.4.3.2.2 Offerors shall provide an annual (by ordering year) time-phased breakout of the direct labor hours by labor category
(manufacturing, assembly, testing, engineering, design, quality assurance, packaging, etc.), including efficiency factors, if applicable. The offeror shall explain how the estimate was developed.
L.4.3.2.3 Offerors shall identify the proposed direct labor rates by year for each category of direct labor, and provide the basis for the proposed direct labor rates.
L.4.3.2.4 For all material and non-major subcontracts (those with a total proposed cost expected to be less than or equal to $20M), the
Offeror shall provide a narrative which explains the method used to develop proposed cost, including information about the extent to which the cost is based on vendor quotes, purchase order history, estimates, or any other information necessary to substantiate the proposal.
L.4.3.2.4.1 The offeror shall provide a priced BOM with the following information:
7 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
a. National Stock Number (NSN), as applicable
b. Part Number
c. Item Name and Description
d. Vendor e, Unit Cost (purchase price to offeror)
f. Quantity Used
g. Extended cost (unit cost multiplied by quantity used)
h. Basis for cost (engineering estimate, vendor quote, purchase history, etc.)
i. Indicate whether component is sole-source, competitive, or commercial
j. For material and non-major subcontract costs based on engineering estimates, please provide rationale and methodology for how the estimate was developed.
k. Indicate the next higher assembly
L.4.3.2.5 Detail of Other Direct Costs (ODCs), if applicable, such as Facilitization, Tooling, Setup, Testing, Travel, Packaging, Freight, etc. The offeror shall provide the basis of estimates (BOEs) for all proposed ODCs to include the description, amount, and how each amount was estimated.
L.4.3.2.6 Indirect Costs: The Offeror shall identify all applicable indirect costs, such as material overhead, labor overhead, general
& administrative overhead, etc. The offeror shall identify the direct and indirect rates by category and by offeror fiscal year, along with the proposal allocation base and calculation. If the award of this contract will have a significant impact upon the offerors business volume, the effects of those changes upon the pool and bases are to be identified and discussed.
L.4.3.2.6.1 The offeror shall state whether these rates represent a Forward Pricing Rate Proposal (FPRP) or Forward Pricing Rate
Agreement (FPRA).
L.4.3.2.6.2 For each proposed indirect rate, the offeror shall provide the actual incurred rate for the prior three fiscal years.
L.4.3.2.7 The offeror shall identify the amount proposed for profit.
L.4.3.2.8 The offeror shall identify the amount of and method of calculating Facilities Capital Cost of Money (FCCM), if applicable.
L.4.3.2.9 The offeror shall provide the basis and describe in narrative format any escalation proposed throughout the RFP period of performance. The offeror shall identify its assumptions for out-year escalation rates.
L.4.3.2.10 Major Subcontractors. If there are major subcontractor (those with a total proposed cost expected to be greater than $20M), provide a list identifying them, showing total amounts for each, brief descriptions of work, and method for determining prices reasonable.
L.4.3.2.11 Inter-Organizational Transfers. The offeror shall provide the same information as described in L.4.3.2.10 for inter-organizations transfers, regardless of dollar value, except the offeror need not provide its price reasonable analysis of the submission. Inter-organization transfers include transfers between divisions, subdivisions, subsidiaries, or affiliates of the offeror under common control.
L.4.3.3 RESERVED
L.4.3.4 RESERVED
L.4.3.5 Government Property Use. The offeror shall provide a list of all Government owned property the offeror proposes to use for this prospective contract. Any such proposed use will be subject to the rental equivalent evaluation factor specified in FAR 52.245-9.
L.4.3.5.1 For Government owned property in which rent-free use is proposed, the offeror shall provide the calculations in accordance with clause 52.245-4001. The final rental equivalent evaluation factor in accordance with 52.245-4001 shall be separately set forth by the offeror in cell K32 of the Contract Price Summary tab in Attachment 0014.
L.4.3.5.2 If the offeror does not proposed to use Government owned property on a rent-free basis, enter an amount of $0 in cell K32 of the Contract Price Summary tab in Attachment 0014.
L.4.3.6 The offeror shall provide the address, email, and telephone number of the cognizant DCAA Field Audit Office and the cognizant
Defense Contract Management Agency (DCMA) office.
L.4.3.7 The instructions above are not intended to be all-inclusive. Offerors may submit any other additional cost, price or financial information in addition to information required by L.4.3, considered to be helpful in the Governments evaluation of the price proposal.
L.4.4 Volume IV Past Performance Factor
8 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
L.4.4.1 For the Past Performance Factor, the offeror shall provide information for up to three recent and relevant contracts. These may include foreign, federal, state, local municipality, and private industry commercial contracts. The Government will not consider the past performance of subcontractors or any individuals or key personnel; only corporate past performance will be considered. Recent contracts are those performed within three years preceding the date of issuance of this RFP.
For the purposes of this volume, contract shall be defined as:
a. a single task or delivery order placed under a single-award or multiple-award IDIQ task order contract (FAR16.501-1) that does not contain multiple work directives or similar instruments which contain separate statements of work; or,
b. a single work directive or similar instrument which contains a separate statement of work issued under a broader contract; or,
c. a single order placed under a basic ordering agreement (BOA) (FAR 16.703); or,
d. a single task order placed under a federal supply schedule (FSS) (FAR 8.405-2); or
e. a single task order placed under a single-award or multiple-award blanket purchase agreement (BPA) (FAR 8.405-3 or FAR 13.303); or
f. a single Government or Commercial contract which does not include any of the types of instruments described in (a)-(e) above.
L.4.4.2 Relevant contracts are those that are comparable in scope, magnitude of effort, and complexity to the following requirements:
a. Development and delivery of software products for Unmanned Ground Vehicles (UGVs) to include executables, source code, documentation, and software updates and patches.
b. Performance and execution of the following: 1) a software requirements analysis and development process; 2) a software testing process to include software qualification and system level integration; and 3) a software configuration management process.
The offeror shall submit a completed Attachment 0032 Past Performance Relevance Matrix.
L.4.4.3 Contract Information: For each of the up to three recent and relevant contracts submitted, provide the following information:
a. Contract Number (and delivery order number if applicable);
b. Contract Type;
c. Total Value of the Contract (beginning & ending value);
d. Delivery or Performance Schedule;
e. Government or commercial contracting activity address, telephone number and email;
f. Procuring Contracting Officer (PCO) and Contract Specialists name or point of contact (for commercial customer), as well as their telephone number and email addresses;
g. Government (DCMA) or commercial administrative contracting officer (ACO) contracting officers representative (COR), performance certifier, and quality assurance representatives (QAR) names, as well as their telephone numbers and email addresses;
h. A description of scope of work requirements and a discussion of the similarities between the cited contract scope and the relevant standards identified above in L.4.4.2.
i. A description of work performed by the offeror;
j. Percentage of effort performed as a prime or subcontractor;
k. For each of the contracts listed, provide a brief self-assessment of contract performance.
l. Copies of Statements of Work from each of the submitted contracts to establish the relevance of the contract to the scope of work activities listed in L.4.4.2 above.
L.4.4.4 Performance Approach: To support the Past Performance assessment of the relevance of prior contracts to the MTRS Inc II
9 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
contract, offerors shall describe the similarities between their proposed performance approach and the contracts they are presenting.
a. For any contracts that did not or will not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the variance and any corrective action(s) taken, if any. 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 also provide a copy of any Cure Notices or Show Cause
Letters received on each contract listed and a description of any corrective action implemented by the offeror. The offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.
L.4.4.5 Past Performance Questionnaire. A Past Performance Questionnaire is provided in Attachment 0033. For each of the up to three recent and relevant contracts submitted by the offeror, the offeror shall send a copy of the past performance questionnaire directly to the appropriate PCO and, if applicable, COR or other appropriate technical and contracting individuals. The offeror shall request that these individuals complete the questionnaire and forward it electronically directly to the Contract Specialist listed on the front page of the SF33 block ten as soon as possible, but no later than the solicitation closing date (See Block nine of the SF33 cover page to this solicitation) with the subject heading PAST PERFORMANCE INFORMATION FOR [offeror name].
L.4.4.6 Corporate Entities. If any contract submitted as part of the Past Performance Factor Volume was performed by a corporate entity or division other than the corporate entity or division that would perform work under this solicitation, the offeror shall identify the entity, and explain how the resources of the other entity will be utilized in the performance of this effort.
L.4.4.7 Predecessor Companies. If the offeror only has recent and relevant performance history as part of a predecessor company, the
Government may consider that past performance in its evaluation of past performance. The offeror shall provide the information for those recent and relevant contracts of that predecessor company. Offerors shall also briefly document the history of the evolution of the offering company from the predecessor company.
L.4.4.8 Contacting References. The Government may contact any of the references the offeror provides, may contact other third parties for performance information, and the Government reserves the right to use any information received as part of its evaluation.
L.4.4.9 Past Performance Information. The Government does not assume the duty to search for data to cure problems it finds in proposals.
The burden of providing thorough and complete past performance information remains with the offeror. The offeror may also be evaluated based on other internal Government or private source information. In this regard, the Government may utilize the Contract Performance and Rating System (CPARS), the Past Performance Information Retrieval System (PPIRS) and any other available internal Government sources to search for recent and relevant offeror performance and ratings. While the Government may elect to consider data obtained from external sources other than the proposal, the burden of providing thorough and complete past performance information rests with the offeror. Failure to provide the information requested in L.4.4 may result in an assessment that the referenced past performance record lacks relevance or recency.
L.4.5 Volume V Small Business Participation Factor
L.4.5.1 Application. The Small Business Participation Factor Volume instructions apply to every offeror (U.S. and non-U.S.), regardless of size, socioeconomic status or location of working facilities or headquarters.
L.4.5.2 Definitions. _
a. Affiliate is defined in 13 CFR 121.103.
b. Alaskan Native Corporation is defined in FAR 19.701 as any Regional Corporation, Village Corporation, Urban Corporation, or
Group Corporation organized under the laws of the State of Alaska in accordance with the Alaska Native Claims Settlement Act, as amended
(43 U.S.C. 1601, et seq.) and which is considered a minority and economically disadvantaged concern under the criteria at 43 U.S.C.
1626(e)(1). This definition also includes ANC direct and indirect subsidiary corporations, joint ventures, and partnerships that meet the requirements of 43 U.S.C. 1626(e)(2).
c. Contractor Team Arrangement (CTA) is defined in FAR 9.601 and includes partnerships, joint ventures, and prime and subcontractor relationships.
d. Indian Tribe is defined in FAR 19.701 as any Indian tribe, band, group, pueblo, or community, including native villages and native groups (including corporations organized by Kenai, Juneau, Sitka, and Kodiak) as defined in the Alaska Native Claims Settlement
Act (43 U.S.C.A. 1601 et seq.), that is recognized by the Federal Government as eligible for services from the Bureau of Indian Affairs in accordance with 25 U.S.C. 1452(c). This definition also includes Indian-owned economic enterprises that meet the requirements of 25
U.S.C. 1452(e).
e. Other Than Small Business is any entity that is not a U.S. small business concern, including, but not limited to large businesses, educational institutions, non-profits, Government entities, and foreign firms.
f. "Small Business Subcontractor" is defined in 48 CFR 2/101 as a concern that does not exceed teh size standard for the North
10 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
American Industry Classification Systems (NAICS) code that the prime contractor determines best describes the product or service being acquired by the subcontract.
g. Small Business Teaming Arrangement (SBTA) is defined in 13 CFR 125.1 and 48 CFR 2.101 and includes joint ventures that qualify as a small business (small business joint venture) and prime and subcontractor relationships.
h. Subcontract is defined in FAR 19.701 as any agreement (other than one involving an employer-employee relationship) entered into by a Government prime contractor or subcontractor calling for supplies and/or services required for performance of the contract, contract modifications, or subcontract.
i. U.S. Small Business Concern is defined in FAR 19 and DFARS 19. U.S. small business concerns include small businesses (SBs), small disadvantaged businesses (SDBs), woman-owned small businesses (WOSBs), HUBZone small businesses (HUBZone SBs), veteran-owned small businesses (VOSBs), and service disabled veteran-owned small businesses (SDVOSBs).
L.4.5.3 Small Business Participation Factor Workbook (Attachment 0034) and Small Business Participation Factor Workbook Instructions
(Attachment 0035):
a. All offerors, including offerors who are themselves U.S. small business concerns for the NAICS code assigned to this requirement are required to complete the Small Business Participation Factor Workbook (Attachment 0034) using the detailed Small
Business Participation Factor Workbook Instructions (Attachment 0035).
b. An offeror shall fill out the Small Business Participation Factor Workbook (Attachment 0034) with goals for this solicitation specifically, even if it is an Other-Than-Small-Business (OTSB) submitting a Comprehensive Subcontracting Plan.
c. The Small Business Participation Factor Workbook (Attachment 0034) shall be submitted in the Microsoft Excel workbook format with all tabs, formulas, and functions that are built into the template in the solicitation. Print image files or pictures (for example, a picture of an Excel spreadsheet embedded in a Word document) or files containing only values are not acceptable. Offerors shall not add formulas or links to any cells that do not already contain them, nor shall the offeror remove or change any existing formulas or links.
d. Small Business Participation Factor Workbook (Attachment 0034) Fill-in Tabs (Prime $, Sub $, SB Prime List, and SB Sub
List). When filling in these tabs, the offeror shall include in the dollars for prime contractor participation and subcontractor participation the proposed amounts for all of the Basic CLINs and all of the Option CLINs.
e. Small Business Participation Factor Workbook (Attachment 0034) Automatic Tabs (Con and Rollup). These tabs are filled in automatically based on the information the offeror filled in on the other four tabs. During its evaluation of the proposal, the
Government will check for consistency. Therefore, the offeror shall use these tabs to check for consistency within the Small Business
Participation Factor Volume submittal, and between the Small Business Participation Factor Volume submittal and other parts of the proposal including the Subcontracting Plan and the offerors other factor volumes.
L.4.5.4 Registrations, Agreements, and Certifications: ______________________________________________
a. The Government may use the System for Award Management (SAM) to verify size, ownership, and any other information provided about the prime and subcontractors listed in the proposal. The Small Business Administration (SBA) Dynamic Small Business Search (DSBS)
Database is the official source for the SBA certified designations of 8(a), 8(a) Joint Venture, and HUBZone SB. The Government may use this system to verify any SBA certifications of the prime and subcontractors. Offerors should be aware of how U.S. SB concerns are defined in FAR Part 19, Defense Federal Acquisition Regulation Supplement (DFARS) Part 19, and 13 CFR 121, Small Business Size
Regulations. Offerors are advised to review 13 CFR 121.103, "How Does SBA Determine Affiliation." If applicable, the Government will consider 13 CFR 121.103(b)(9) In the case of a solicitation of offers for a bundled contract with a reserve (as defined in 125.1) and 13
CFR 121.103(h)(3) Exception to affiliation for certain joint ventures.
b. Failure to register in SAM for the corresponding NAICS code identified in Section K, FAR clause 52.204-8 prior to submitting a proposal for this solicitation may preclude an award being made to your company.
c. Joint Venture Registration and Agreement. If the offeror is a small business joint venture, the joint venture shall be registered in SAM under its own name. In addition, each member in a small business joint venture (as listed in the SB Prime List tab of the Small Business Participation Factor Workbook (Attachment 0034)) shall be registered in SAM for the type of work it does. To be recognized as a small business joint venture and be eligible for award of a contract, the membership arrangements of the joint venture shall be identified and the company relationships fully disclosed in the offerors proposal in accordance with FAR 9.603 and 13 CFR
125.1(u). A copy of the agreement establishing the joint venture shall contain the signatures of all of the members comprising the joint venture.
d. Affiliate Registration. If the offeror is a small business that has first tier affiliates that will be performing work on the proposed contract (as listed in the SB Prime List tab of the Small Business Participation Factor Workbook (Attachment 0034), each first tier affiliate shall be registered in SAM for the type of work it does.
11 14
Name of Offeror or Contractor:
PIIN/SIIN MOD/AMD
e. Subcontractor Registration or Certification. According to 13 CFR 121.411(b) the offeror cannot require subcontractors to be registered in SAM. For any small business subcontractor listed in the SB Sub List tab of the Small Business Participation Factor
Workbook (Attachment 0034) that is not registered in SAM, the offeror shall provide in accordance with 13 CFR 121.411(f), a
Certification of Small Business Size and Socioeconomic Status for Subcontractors Not Registered in the System for Award Management (SAM)
(Attachment 0037) from that subcontractor verifying its small business size and socioeconomic status. This certification shall contain, on the same page as the size and status claimed, the signature of the official authorized to sign for the subcontractor.
L.4.5.6 Subcontracting Reports: _______________________
a. The Offeror shall provide documentation of performance in complying with the requirements of FAR 52.219-9, DFARS 252.219-7003, and
DFARS 252.219-7004, as applicable, over the twelve months prior to solicitation release date if the offeror meets both of the following criteria:
(1) Offeror is other than a U.S. small business concern as defined by the NAICS code applicable to this solicitation.
(2) Offeror has had prior contracts requiring the submission of a Small Business Subcontracting Plan.
b. If over the twelve months preceding the date of solicitation release the Offeror has reported accomplishments against an
Individual Subcontracting Plan or Master Subcontracting Plan, the documentation shall include the latest Individual Subcontracting
Report (ISR/SF294) for the contracts listed below.
(1) Every Federal contract for which the Offeror was the prime contractor required to submit an ISR/SF294.
(2) Every contract for which the Offeror was a subcontractor required to submit an ISR/SF294.
c. The ISRs in paragraph b shall be for:
(1) The DUNs Number associated with the offerors own CAGE code.
(2) The DUNs Numbers associated with:
(a) A first tier affiliate that will be performing work on the proposed contract and will be subcontracting to small business (these subcontracts must be listed in the SB Sub List tab of the Small Business Participation Factor Workbook (Attachment
0034)). For purposes of the small business participation factor and the subcontracting plan, these first tier affiliates are considered part of the prime.
(b) A member of a joint venture offeror if the member will be subcontracting to small business (these subcontracts must be listed in the SB Sub List tab of the Small Business Participation Factor Workbook (Attachment 0034)). For purposes of the small business participation factor and the subcontracting plan, joint venture members are considered affiliates of the prime and therefore part of the prime, even if they are designated as subcontractors in the joint venture legal agreement.
d. If ISR reports for a contract were not submitted to eSRS, send signed copies of the SF294s that were submitted.
e. If over the twelve months preceding the date of solicitation release the Offeror has reported accomplishments against a Commercial or
Comprehensive Subcontracting Plan, or both, in lieu of or in addition to Individual or Master Plans, the documentation shall include:
(1) A copy of the Plan to document the goals.
(2) The latest Summary Subcontract Report (SSR/SF295) to document accomplishments.
f. If the Offeror has not performed a contract over the past 12 months that contained FAR 52.219-9, DFARS 252.219-7003, or DFARS 252.219-
7004, the Offeror shall so state.
g. If during evaluation, the Government finds additional reports from the twelve months prior to solicitation release date that were not submitted in the proposal, the…
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 .