Attachment_(L-15)_Vol_3_CE-2_ACE.xlsx
XLSX spreadsheet 18 KB Posted
- Attached to
- Close Range Unmanned Aircraft Systems (UAS), Intelligence, Surveillance and Reconnaissance (ISR) Services
- Solicitation number
- N00019-16-R-0063
About this file
Attachment (L-15) Vol 3 CE-2 ACE
View the file
Other files
Show all 50
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
Instructions **NOTE: This tab contains instructions for completing Table CE-2: Applicable Contracts For Each Corporate Experience Element
Note: Only contract references designated in Table ES-2 (Relevant Contract Summary) shall be used in completing this Volume and all contract references shall be numbered the same throughout all of the Offeror’s proposal volumes (i.e. the contracts identified as P1, T1, C1 etc. in Table ES-2 shall be the same P1,T1, C1 etc. contracts identified in Table CE-1.
Use a seperate worksheet for each contract reference. Label each worksheet with the entity name and contract reference. For example, if the Prime is Example Corp and has submitted five contract references for evaluation, there should be five worksheets labeled as follows: Example - P1, Example - P2, Example - P3, Example - P4 and Example - P5.
Item 1 (Offeror Name) In Column C, fill in the Prime Offeror submitting a response to this solicitation.
Item 2 (Entity Name) In Column C, the Offeror shall enter the name of the principle entity for the contract reference.
Note: The term “entity” is defined in Part A General Instructions, Section 1.0 General.
Item 3 (Contract Reference) In Column C, enter the contract reference number.
Note: The contract reference should reference the same contract identified in Table ES-2 and PP-1.
Item 4 (Title of Contract) In Column C, fill in the contract title.
Item 5 (Contract / TO / DO / Subcontract Number) In Column C, identify any associated TO / DO / or subcontract number.
Item 6 (Applicable PWS / SOW Section / Paragraph from Contract Reference Applicable to (Evaluation Element)) The Offeror shall identify the relevant portions (sections and paragraphs) of the contract reference’s SOW/PWS or other supporting solicitation/contract documentation to clearly identify how corporate experience performing past tasks are similar to evaluation areas 4.1.1 through 4.1.n If the Offeror performed as a subcontractor for a contact reference, additionally include relevant portions (sections and paragraphs) of the work agreement with the Prime.
Note: A single contract reference may demonstrate experience in multiple elements.
CE-2 Template
| Table CE-2 Applicable Contracts for CE Elements | ||
| 1 | Offeror Name | |
| 2 | Entity Name | |
| 3 | Contract Reference | |
| 4 | Title of Contract | |
| 5 | Contract/TO/DO/Subcontract Number | |
| 6 | 3.2.1 OCONUS COCO Hardware System Deployment | Provide applicable PWS/SOW Section/Paragraph and/or other substantiating information/explanation that demonstrates performance of the effort. Where not applicable to the contract/T.O. write “N/A” |
| a. OCONUS COCO Hardware System Deployment |
b. Import/Export Licensing to support military operations – Also identify the countries involved
c. Supply chain management – Also identify the number of sites and the frequency of the shipments
d. Defense Transport Regulations Compliance activity. Also identify the following:
(1) Personnel CONUS Training & Deployment; Number of CONUS personnel trained for deployment per quarter
| (2) Attainment of Official Host Country Approval (VISAs, etc); and identified the associated countries | ||
| 7 | 3.2.2 UAS Operations | Provide applicable PWS/SOW Section/Paragraph and/or other substantiating information/explanation that demonstrates performance of the effort. Where not applicable to the contract/T.O. write “N/A”. |
| a. Sea-Based UAS/UAV Operations – Also identify the number of ships, the number of flight hours per day flown and the number of personnel deployed to each ship. | ||
| b. Land-Based UAS/UAV Operations - Also identify the number of sites, the number of flight hours per day flown and the number of personnel deployed to each site. | ||
| c. FOB UAV Operations | ||
| d. OCONUS Air Space Coordination – Also identify Cognizant Airspace Authority which the coordination was conducted and the associated country. | ||
| 3.2.3 Intelligence, Surveillance, and Reconnaissance Services | Provide applicable PWS/SOW Section/Paragraph and/or other substantiating information/explanation that demonstrates performance of the effort. Where not applicable to the contract/T.O. write “N/A”. | |
| a. Intelligence, Surveillance, and Reconnaissance Services | ||
| b. Military Liaison Coordination for data collection | ||
| c. Information Assurance Accreditation activity | ||
| d. ISR Data Classification & Regulations Compliance activity | ||
| 8 | 3.2.4 Prime Contractor and Management Experience as the Prime (Only past contracts/T.O.s where the proposed principle entity was the Prime applies to this element.) | Provide applicable PWS/SOW Section/Paragraph and/or other substantiating information/explanation that demonstrates performance of the effort. Where not applicable to the contract/T.O. write “N/A”. |
| a. Number of subcontractors managed | ||
| b. Ramp Up efforts, managing turn-around time from Award to Deployment. Also identity time from award to deployment and describe the level of effort. | ||
| c. Deployed Personnel – number of sites or ship | ||
| d. Deployed Personnel – number of personnel at each site or ship | ||
| e. Location, identify as a minimum OCONUS and/or CONUS |
N00019-16-R-0063 Attachment (L-15)
File details come from the government source that posted it. Updated .