HSBP1010R0074 Draft RFP

<HSBP1010R0074 (DRAFT)>

TABLE OF CONTENTS

4SECTION A.

SOLICITATION/CONTRACT FORM

5SECTION B.

SUPPLIES OR SERVICES & PRICES OR COSTS

5B.1.

SCHEDULE OF SUPPLIES/SERVICES

7B.2.

CLIN DESCRIPTIONS

14B.3.

TYPE OF CONTRACTContract

15SECTION C.

STATEMENT OF OBJECTIVES (SOO)

15C.1.

SCOPE

15C.2.

PURPOSE AND INTENT

16C.3.

BACKGROUND

16C.4.

PERFORMANCE OBJECTIVES

17C.5.

RISK MITIGATION

17C.6.

APPLICABLE DOCUMENTS

18SECTION D.

PACKAGING & MARKING

18D.1.

PACKAGING & MARKING

19SECTION E.

INSPECTION & ACCEPTANCE

19E.1.

FAR CLAUSES INCORPORATED BY REFERENCE

19E.2.

ULAD FIRST ARTICLE TEST (FAT)

20E.3.

ULAD Unit Acceptance Test (CDRL 0009)

21SECTION F.

DELIVERIES OR PERFORMANCE

21F.1.

21F.2.

CLAUSES IN FULL TEXT

23F.3.

PERIOD OF PERFORMANCE (MAR 2003)

23F.4.

PLACE OF PERFORMANCE/DELIVERIES

24F.5.

DELIVERYSCHEDULE

25SECTION G.

CONTRACT ADMINISTATION DATA

25G.1.

CONTRACTING OFFICER'S TECHNICAL REPRESENTATIVE (COTR)

25G.2.

CONTRACTING OFFICER (CO)

26G.3.

CONTRACTOR REPRESENTATIVE FOR PAST PERFORMANCE

26G.4.

SUBMISSION OF INVOICES

27SECTION H.

SPECIAL CONTRACT REQUIREMENTS

27H.1.

GOVERNMENT CONSENT OF PUBLICATION/ENDORSEMENT (MAR 2003)

27H.2.

SECURITY PROCEDURES (OCT 2009)

29H.3.

ORDERING PROCEDURES -- SUPPLIES (OCT 2007)

29H.4.

DISCLOSURE OF INFORMATION (MAR 2003)

30H.5.

NON-PERSONAL SERVICE (MAR 2003)

30H.6.

POST AWARD EVALUATION OF CONTRACTOR PERFORMANCE (JUL 2010)

31H.7.

ADDITIONAL CONTRACTOR PERSONNEL REQUIREMENTS (OCT 2007)

32H.8.

HOLIDAYS AND ADMINISTRATIVE LEAVE (MAR 2003)

32H.9.

TRAVEL COSTS (AUG 2008)

33SECTION I.

CONTRACT CLAUSES

33I.1.

35I.2.

FAR CLAUSES IN FULL TEXT

42I.3.

HSAR CLAUSES

48SECTION J.

LIST OF ATTACHMENTS

48J.1.

ULAD Capabilities Matrix, 3 pages

48J.2.

Enterprise Architecture Requirements, 7 pages

48J.3.

AMOC Sensor Data Format, 1 page

48J.4.

CBP Training Development Standards, 31 pages

48J.5.

Past Performance Questionnaire, 5 pages

48J.6.

Small Business Plan Outline, 6 pages

48J.7.

Acronym Listing

49SECTION K.

REPRESENTATIONS, CERTIFICATIONS, OTHER STATEMENTS OF OFFEROR

49K.1.

52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

49K.2.

52.203-2 CERTIFICATE OF INDEPENDENT PRICE DETERMINATION (APR 1985)

50K.3.

52.204-3 Taxpayer Identification (Oct 1998)

51K.4.

52.204-8 Annual Representations and Certifications (Feb 2009)

53K.5.

52.207-4 Economic Purchase Quantity—Supplies (Aug 1987)

54K.6.

52.209-5 Certification Regarding Responsibility Matters (Apr 2010)

55K.7.

52.209-7 INFORMATION REGARDING RESPONSIBILITY MATTERS (APR 2010)

56K.8.

52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS--COMMERCIAL ITEMS (AUG 2009) ALTERNATE II (OCT 2000)

66K.9.

52.215-6 Place of Performance (Oct 1997)

66K.10.

52.222-18 Certification Regarding Knowledge of Child Labor for Listed End Products (Feb 2001)

67K.11.

52.222-22 Previous Contracts and Compliance Reports (Feb 1999)

67K.12.

52.222-25 Affirmative Action Compliance (Apr 1984)

67K.13.

52.222-38 Compliance with Veterans’ Employment Reporting Requirements (Dec 2001)

67K.14.

52.223-4 Recovered Material Certification (May 2008)

67K.15.

52.223-13 Certification of Toxic Chemical Release Reporting (Aug 2003)

68K.16.

52.225-2 Buy American Act Certificate (Feb 2009)

69K.17.

52.225-4 Buy American Act—Free Trade Agreements—Israeli Trade Act Certificate (June 2009)

70K.18.

52.225-18 Place of Manufacture (Sept 2006)

71K.19.

52.227-15 Representation of Limited Rights Data and Restricted Computer Software (Dec 2007)

71K.20.

52.230-1 Cost Accounting Standards Notices and Certification (Oct 2008)

73K.21.

52.230-7 PROPOSAL DISCLOSURE-COST ACCOUNTING PRACTICE CHANGES (APR 2005)

74SECTION L.

INSTRUCTIONS, CONDITIONS, & NOTICES TO OFFERORS

74L.1.

52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998)

74L.2.

52.216-1 TYPE OF CONTRACT (APR 1984)

74L.3.

52.232-31 INVITATION TO PROPOSE FINANCING TERMS (OCT 1995)

75L.4.

52.233-2 SERVICE OF PROTEST (SEP 2006)

75L.5.

52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

75L.6.

SMALL BUSINESS SUBCONTRACTING PLAN

76L.7.

GENERAL INSTRUCTIONS FOR THE PREPARATION OF PROPOSALS

77L.8.

PREPARATION OF VOLUME 1 – TECHNICAL PROPOSAL

79L.9.

PREPARATION OF VOLUME 2 – Cost/Price Proposal

81SECTION M.

EVALUATION FACTORS FOR AWARD

81M.1.

GENERAL

SECTION A. SOLICITATION/CONTRACT FORM

SECTION B. SUPPLIES OR SERVICES & PRICES OR COSTS

B.1. <SCHEDULE OF SUPPLIES/SERVICES>

Purchase or Option

Base Period

Option Period 1

Option Period 2

Option Period 3

Option Period 4

B.2. CLIN DESCRIPTIONS

The example CLIN structure presented in Section B is to assist the vendor in identifying the requirements the Government anticipates it needs to evaluate the vendor‘s proposal. The vendor is free to propose an alternate CLIN structure to meet this requirement providing proposed CLIN solution will meet the Government’s requirement.

B.2.1. Base (1st) Year Contract Line Item Numbers (CLINs)

B.2.1.1. CLIN 0001 – ULAD First Article Test (FAT) (CDRL U-0001) B.2.1.1.1. The purpose of CLIN 0001 is to procure one unit for First Article Testing in an operational environment to ensure the unit satisfies all of the requirements in the capabilities matrix and performs as advertised by the Vendor.

B.2.1.1.2. In accordance with FAR 16.504, this First Article Test Unit satisfies the minimum requirement of the IDIQ contract. The maximum dollar value of this contract is $100,000,000.00.

B.2.1.1.3. A unit is defined as a being composed of a sensor component and remote component (see ULAD Concept in Attachment 8).

B.2.1.1.4. The system will not be tested to destruction and it is expected it will be utilized as an operational unit, with a warranty.

B.2.1.1.5. The vendor will provide an operations and maintenance manual for FAT Test Unit.

B.2.1.1.6. The Government cannot determine at this time the number of awards that will be made. Therefore the following two cases apply:

B.2.1.1.6.1. In the event of a single award, the Contractor shall deliver one (1) system of Lot/Item Number One (1) within one hundred twenty (120) calendar days from the date of this contract to the Customs and Border Protection Tucson Sector, <<2430 Swan Road>, <Tucson>, <Arizona> <85711>> for first article test.

B.2.1.1.6.1.1. If additional time is needed by the Contractor for delivery of the first article test unit, the Contractor is free to propose additional time needed and submit the rationale for extra time needed.

B.2.1.1.6.1.2. The shipping documentation shall contain this contract number and the Lot/Item identification.

B.2.1.1.6.1.3. The characteristics and testing requirements the first article test unit must meet are specified in the ULAD Performance Objectives as stated in ULAD SOO.

B.2.1.1.6.2. In the event of multiple awards, the Government will establish a delivery schedule for first article test units approximately at the time of award.

B.2.1.1.7. Refer to the Federal Acquisition Regulation (FAR) Subpart 52.209-4 – First Article(s) Approval – Government Testing for additional instructions.

B.2.1.2. Vendor shall provide operators and train up to four CBP personnel to perform the FAT for a two week period.

B.2.1.2.1. It is anticipated that operator training, operator familiarization, First Article Acceptance Testing, and Border Patrol field operation will utilize First Article Test System (s) on a 24/7 basis from delivery until system acceptance is completed.

B.2.1.2.2. The vendor shall provide a government approved First Article Test Plan (CDRL U-0001) 120 days after contract award, or vendor will propose a due date subject to Government approval prior to FAT Unit delivery.

B.2.2. CLIN 0002 – Sensor Unit B.2.2.1. The purpose of CLIN 0002 is to price an individual ULAD Sensor unit after successful FAT completion. Any repairs or modifications recommended as a result of the ULAD FAT must be completed at the factory before delivery of the production unit and include warranty provisions.

B.2.3. CLIN 0003 through 0006 are applicable to Sensor Volume Discount Units should the Government elect to purchase more than one unit.

B.2.3.1. The purpose of CLINs 0003 through 0006 is to procure additional ULAD units after successful FAT completion based on any volume discounts the vendor may offer as cited in the vendor’s proposal for deployment along the U.S. Southwestern border.

B.2.3.2. The goal of is to leverage cost savings normally inherent in volume discounting so that the Government procures ULAD units in an economical fashion.

B.2.3.3. Any repairs or modifications recommended as a result of the ULAD FAT must be completed at the factory before delivery of the production units and include warranty provisions.

B.2.3.4. The Contractor shall deliver to the Government ULAD units based on volume discounts selected by the Government subject to the availability of funding as indicated in the Contractor’s proposal.

B.2.3.5. Included in the price of the unit shall be the Contractor’s warranty which must comply with FAR Subpart 52.246-18 (Warranty of Supplies of a Complex Nature) and any additional costs to maintain the system during the warranty period.

B.2.3.6. As a minimum, the term “any additional costs” include spares, labor, equipment, facilities, and TDY travel costs.

B.2.4. CLIN 0007 Remote Power Component B.2.4.1. The purpose of this CLIN is to purchase Remote Power Components.

B.2.5. CLIN 0008 through CLIN 0011 are applicable to Remote Power Components should the Government elect to purchase more than one Remote Power Component.

B.2.6. CLIN 0012 Communication Component B.2.6.1. The purpose of this CLIN is to purchase Communication Component.

B.2.7. CLIN 0013 through CLIN 0017 is applicable to Communication Component should the Government elect to purchase more than one Communication Component.

B.2.8. CLIN 0018 – Train-the-Trainer (T3) Course (CDRL U-0002) B.2.8.1. The purpose of CLIN 0018 is to procure a T3 Course for development of a cadre group (Master Trainers) within CBP.

B.2.8.1.1. These Master Trainers will be responsible for training ULAD Operators on the use, deployment, and preventative maintenances checks and services (PMCS) of the ULAD system.

B.2.8.1.2. The goal of the course is to give CBP the ability to train as many U LAD Operators as needed based on CBP’s equipment density and operational needs.

B.2.8.1.3. The vendor shall deliver a Train-the-Trainer (T3) operator class to a total of eight (8) personnel as identified by CBP, at the Government’s location in <<Tucson>, <AZ.>> B.2.8.1.4. The course should begin after successful completion of ULAD First Article(s) Test (FAT) and last approximately two (2) weeks.

B.2.8.1.5. The T3 Course shall be classroom based training with hands-on portions taking place under field locations within the Tucson Sector Area of Operations.

B.2.8.1.6. Training should emphasize different operational scenarios and must emphasize both day and night operational conditions.

B.2.8.2. In addition, the CBP intends to procure T3 Course Documentation that complies with Department of Homeland Security (DHS) standards.

B.2.8.2.1. The goal is to ensure that all DHS standards for course development are satisfied upon receipt of the deliverable and well in advance of course delivery.

B.2.8.2.2. The vendor shall use the CBP Training Development Standards October 2008 for development of the T3 Course.

B.2.8.2.3. It is the intent of the Government to develop its own web-based training modules using organic assets.

B.2.8.2.4. The vendor shall not propose development of a web-based training module.

B.2.8.2.5. If this direction changes, the ULAD Contracting Officer will negotiate a contract modification to the ULAD Contract to address the change.

B.2.8.3. When the T3 Course (CLIN 0004) is delivered, the vendor shall be responsible for providing T3 training materials (training manuals, workbooks, CD/DVD, etc.) for each student.

B.2.8.3.1. In addition to this, the vendor shall provide a master electronic copy that contains all of the training materials for use and reprinting by the Government (i.e. Golden Disks).

B.2.9. CLIN 0019 – ULAD Operations and Maintenance (O&M) Manuals (CDRL U-0003)

B.2.9.1. The purpose of CLIN 0019 is to ensure the ULAD Operator has all of the information necessary to effectively deploy the system, place the system in operation (set-up and operate), trouble-shoot the system at the operator level, perform PMCS, stow (make ready for transport), and redeploy the system to another location based on the operational needs of the Border Patrol.

B.2.9.2. The goal of procuring ULAD Operations and Maintenance manuals is to ensure the ULAD Operator has all the information necessary to effectively deploy, operate, and redeploy the ULAD system.

B.2.9.3. The ULAD Operations and Maintenance manual must satisfy the above purpose and address all Levels (Organizational) of maintenance requirements of the system. Distribution shall as be follows:

B.2.9.3.1. One (1) manual per ULAD system – hardcopy

B.2.9.3.2. One (1) manual – ULAD Contracting Officer– hardcopy

B.2.9.3.3. Two (2) CDs/DVDs for reproduction of materials (MS Word 97-2003 or Adobe Acrobat Reader V7.0) for use by the Government.

B.2.10. CLIN 0020 – Product Drawing Package (CDRL U-0004) B.2.10.1. The purpose of CLIN 0020 is to ensure that, in addition to having maintenance manuals that provide instruction on how to perform maintenance and services above the ULAD Operator level, the Government obtains product drawings necessary to provide adequate system level logistical support.

B.2.10.2. The goal is to ensure the Government has the information it needs, in addition to the O&M manuals, Vendor Maintenance manuals, and ILSP, to adequately perform Level 2 (Intermediate) ULAD sustainment support.

B.2.10.3. A Product Drawing Package is a collection of product engineering data related to the design and manufacture of an item or system.

B.2.10.3.1. Product drawings contain all of the descriptive documentation needed to ensure the competitive procurement of spare parts or items.

B.2.10.3.2. The Government intends to use the Product Drawing Package to maintain proper configuration control, support quality assurance functions, provide technical data for competitive procurement of spares (not the system level end item), and as the major source of technical information for logistics support throughout the ULAD system life cycle.

B.2.10.3.3. The vendor shall provide a Product Drawing Package for maintenance and repair of the system by Government engineers, technicians, or support contractors.

B.2.10.3.4. Distribution shall as be follows:

B.2.10.3.4.1. Seven (7) copies of the Product Drawing Package for the Government Maintenance Supervisor – hardcopy

B.2.10.3.4.2. One (1) copy of the Product Drawing Package for the ULAD Contracting Officer

B.2.10.3.4.3. Two (2) soft copies (CDs/DVDs) (MS Word 97-2003 or Adobe Acrobat Reader V7.0) for reproduction and use by the Government.

B.2.11. CLIN 0021 – Vendor Integrated Logistics Support Plan (ILSP) (CDRL U-0005)

B.2.11.1. This CLIN addresses only the preparation, delivery, and update of the vendor’s ILSP.

B.2.11.2. The purpose of CLIN 0021 is to ensure the Government has an end-to-end plan, from the vendor, that adequately explains what has to be done to adequately sustain the ULAD system.

B.2.11.3. It must be emphasized the ILSP is intended to be a “what” document; the O&M and ULAD Intermediate (Level 2) Maintenance manuals are expected to be “how” documents.

B.2.11.4. The goal of this CLIN is to ensure a single-source document exists that describes the end-to-end maintenance strategy for the ULAD system.

B.2.11.5. The vendor shall develop an ILSP for review and approval by the Government.

B.2.11.6. The ILSP should be delivered no later than forty-five (45) calendar days after receipt of ULAD Contractor notification that FAT has been successfully completed.

B.2.11.7. As a minimum, the plan must address the data below:

B.2.11.7.1. General repair and service of the system.

B.2.11.7.1.1. Level 1

B.2.11.7.1.1.1. Organizational ULAD Operator Preventative Maintenance Checks and Services (PMCS) B.2.11.7.1.2. Level 2 B.2.11.7.1.2.1. Intermediate; maintenance services above the ULAD Operator level and below depot level B.2.11.7.1.3. Level 3

B.2.11.7.1.3.1. Depot; complex maintenance services not expected to be performed by the servicing organization such as major component refit and/or repair (i.e. IR camera or radar B.2.11.7.2. Training B.2.11.7.3. Provisioning (Spares) Parts List

B.2.11.7.4. Engineering Data for Provisioning

B.2.11.7.5. Long-lead Items List

B.2.11.7.6. Standard Operating Procedures (SOP) for service and repair of low-density equipment

B.2.11.7.7. Environmental considerations

B.2.11.7.8. Fault diagnostics and determinations

B.2.11.7.9. Removal and replacement of components-level items

B.2.11.7.10. Shipment of removed components for Depot (Level 3) level repair or replacement

B.2.11.7.11. Monthly updates: status reports, trend, and analysis data (i.e. FRACAS (Failure Reporting Analysis and Corrective Action System), Pareto Charts, return to service data, etc.)

B.2.11.7.12. Spares Provisioning Analysis and Technical Documentation, as follows.

B.2.11.7.12.1. Provisioning Parts List (PPL): identify both standard and long lead items

B.2.11.7.12.2. Tools and Test Equipment List (TTEL)

B.2.11.7.12.3. Common Bulk Items List (CBIL)

B.2.11.7.12.4. Repairable Items List (RIL)

B.2.11.7.12.5. Calculated inventory requirements for the above line items based on recognized Integrated Logistics Support (ILS) calculations.

B.2.11.7.12.6. Offeror to supply calculations and conduct a provisioning conference/meeting with Government participation.

B.2.11.7.12.7. Supplier to report on these items in the monthly updates.

B.2.11.7.12.8. List of expendable items.

B.2.11.8. Distribution of the ILSP shall be as follows:

B.2.11.8.1. One (1) copy for the ULAD Contracting Officer

B.2.11.8.2. Two (2) soft copies (CDs/DVDs) (MS Word 97-2003 or Adobe Acrobat Reader V7.0) for reproduction and use by the Government.

B.2.12. CLIN 0022 – Maintenance and Repair Service

B.2.12.1. This CLIN is required for the base year and optional for the second year of the contract. Beginning the second or the third year of the contract, the Government will assume responsibility for ULAD sustainment. The purpose of this CLIN is to address maintenance and “non-warranty” repair of the system above the operator level (Levels 2 and 3). It is defined as maintenance and repair service performed to Supplier-proposed standards for MTTR and MaxTTR. This CLIN is necessary for two (2) reasons:

B.2.12.2. The Government has to have a way to address maintenance service and repairs, not covered by the warranty, during the warranty period; and

B.2.12.3. The Government must have a way to ensure adequate sustainment of the ULAD system after the warranty has expired and until the Government assumes responsibility for sustainment of the system.

B.2.12.4. The goal of this CLIN is to address the above challenges.

B.2.12.5. The vendor shall price base year, non-warranty maintenance repair and price optional maintenance under this CLIN.

B.2.12.6. The Supplier shall propose first-year maintenance and repair service, for a 12-month period, beginning at Government system acceptance (FAT Acceptance for the first article(s) and Government acceptance for all other systems; the vendor shall price the following cases under CLIN 00228 as follows:

B.2.12.6.1. CASE A:

B.2.12.6.1.1. 12-months (to co-inside with the vendor’s 12-month warranty); Minimum Ao => 75%; MTTR=As proposed by Vendor; MaxTTR=As proposed by Vendor:

B.2.12.6.1.2. A 12-month period; Ao => 75%; MTTR and MaxTTR as proposed by the vendor. System level warranty that applies to the ULAD as a system.

B.2.12.6.1.3. 12-month service period begins at Government system acceptance; optional period begins when the option is exercised after the first year.

B.2.12.6.1.4. Supplier to report on warranty actions and status in the monthly updates.

B.2.12.6.2. CASE B:

B.2.12.6.2.1. 12-months (to co-inside with the vendor’s 12-month warranty); Minimum Ao => 95%; MTTR=72 hrs; MaxTTR=288 hrs:

B.2.12.6.2.2. A 12-month period; Ao => 95%; MTTR=72 hrs; MaxTTR=288 hrs.

B.2.12.6.2.3. System level warranty that applies to the ULAD as a system.

B.2.12.6.2.4. 12-month service period begins at Government system acceptance; optional period begins when the option is exercised after the first year.

B.2.12.6.2.5. Supplier to report on warranty actions and status in the monthly updates.

B.2.12.7. Definitions

B.2.12.7.1. Ao = Operational Availability = Uptime/Total Time. Where “Uptime” is the time during which the system was capable of performing all required functions in a given calendar interval; and “Total Time” is the total time during which the system was supposed to be up during a given calendar interval (Total Time = Uptime + Downtime).

B.2.12.7.2. Source: Paragraph 3.2.4.3, DOD Guide for Achieving Reliability, Availability, and Maintainability, August 3, 2005 B.2.12.7.3. http://www.acq.osd.mil/sse/docs/RAM_Guide_080305.pdf B.2.12.7.4. Mean Time to Repair (MTTR):

B.2.12.7.5. The average time consumed performing Level 1, 2, and 3 repair and maintenance averaged for an interval of time specified as a calendar month.

B.2.12.7.6. For Level 2 and 3 repair and maintenance, Start Time is when unit arrives at the Level 2 maintenance location and is made available to Supplier and Supplier notified, whether or not Supplier personnel are present.

B.2.12.7.7. For Level 2 and 3 repair and maintenance, End Time is when Supplier notifies CBP and releases the fully repaired and tested unit to CBP at the Level 2 maintenance location, whether or not CBP personnel are present.

B.2.12.7.8. Note: Based on these definitions, Level 3 maintenance time does intentionally include transportation time from the Level 2 maintenance location to the Level 3 maintenance location, as well as return transportation time back to the Level 2 maintenance location, as well as any wait times involved in transportation.

B.2.12.7.9. Maximum Time to Repair (MaxTTR):

B.2.12.7.10. The maximum time consumed performing Level 1, 2, and 3 repair and maintenance averaged for an interval of time specified as a calendar month.

B.2.12.7.11. Start and End Times have the same definition as MTTR.

B.2.12.7.12. Level 1 (Organizational or ULAD Operator) Maintenance is routine maintenance at a novice skill level performed by CBP personnel or support contractors including routine oil and filter changes (on a generator, for example).

B.2.12.7.13. Specific Level 1 Maintenance Tasks and schedules are to be defined by the Supplier in the ILSP document.

B.2.12.7.14. Level 2 (Intermediate) Maintenance is non-routine maintenance and also any routine maintenance requiring special skills above the novice level.

B.2.12.7.15. Specific Level 2 Maintenance Tasks and schedules are to be defined by the Supplier in the ILSP document.

B.2.12.7.16. Level 3 (Depot) Maintenance is non-routine maintenance performed at the Supplier’s facilities (perhaps at the factory). Specific Level 3 Maintenance Tasks and schedules are to be defined by the Supplier in the ILSP document. CBP expects most maintenance to be performed at Level 1 or Level 2. CBP anticipates that Level 3 maintenance will be rare.

B.2.12.8. Warranty and Maintenance Assumptions B.2.12.8.1. Level 1 Maintenance Locations and Facilities:

B.2.12.8.1.1. Level 1 maintenance will be performed by CBP personnel or support contractors in the field at the surveillance site.

B.2.12.8.1.2. The locations will typically be remote, unimproved, and far from paved roads.

B.2.12.8.1.3. No facilities such as electrical power or water will be provided at the Level 1 site.

B.2.12.8.1.4. Any special tools required for Level 1 maintenance shall be supplied with and attached to the ULAD system (via robust enclosures or restraints) so that the tools are readily available.

B.2.12.8.2. Level 2 Maintenance Locations and Facilities:

B.2.12.8.2.1. Level 2 maintenance will be performed at a Border Patrol Station, Border Patrol Sector Headquarters, or leased maintenance facility.

B.2.12.8.2.2. The maintainer must supply onsite all necessary labor, instrumentation, spare parts, consumable items, expendable items, lifts, jacks, winches, electricity, and water.

B.2.12.8.3. Level 3 Maintenance Locations and Facilities:

B.2.12.8.3.1. Level 3 maintenance is performed at the Supplier’s facilities (such as at the factory).

B.2.12.8.3.2. Location and Facilities are at the Supplier’s discretion, but note that MTTR and MaxTTR are defined in such a way as to include transit time (as detailed above).

B.2.12.9. Additional instructions:

B.2.12.9.1. Supplier to report on maintenance actions and status as stated in the monthly updates.

B.2.12.9.2. The Level 2 maintenance location will be either the Offeror’s facility or at a Border Patrol sector facility.

B.2.13. CLIN 0023 – Vendor Technical Support

B.2.13.1. The purpose of CLIN 0023 is to allow the Vendor to propose an hourly rate for labor to provide subject matter expertise associated with repair and service of the system.

B.2.13.2. The goal is to give the Government access to subject matter expertise needed from the Vendor, particularly for Unit Acceptance Test (UAT) support and when responsibility for ULAD sustainment transfers from the Vendor to the Government.

B.2.13.3. Since there is no way for the Government to know exactly where, when, and how many hours will be needed, the intent is only for the Vendor to propose a rate which would be charged under this CLIN if exercised.

B.2.13.4. For the purpose of consistent pricing, the Vendor shall use <<Tucson>, <AZ>> as the location.

B.2.13.5. The Supplier shall propose hourly rate for Technical Services by Subject Matter Expert(s) (SME) capable of guiding CBP in diagnosis, operation, maintenance (Levels 1, 2, and 3), troubleshooting, and repair of the system and its subsystems and components.

B.2.13.6. This may involve telephone support by the SME(s).

B.2.13.7. This may also involve travel by the SME(s) to various CBP Station locations (to help the vendor conceptualize the scope of the mission, several locations along the U.S. Southwestern Border are listed below).

B.2.13.7.1. Customs and Border Protection, <<Del Rio>> Sector Headquarters, <<2401 Dodson Avenue>, <Del Rio>, <Texas> <78840>> B.2.13.7.2. Customs and Border Protection, El Centro Sector Headquarters, <<221 West Aten Road>, <Imperial>, <CA> <92251>> B.2.13.7.3. Customs and Border Protection, El Paso Sector Headquarters, <<8901 Montana Avenue>, <El Paso>, <Texas> <79925>> B.2.13.7.4. Customs and Border Protection, <<Yuma>> Sector Headquarters, 4035 S. Ave. A, <<Yuma> <AZ> <85365>> B.2.13.7.5. Customs and Border Protection, <<Tucson>> Sector Headquarters, <<2430 S. Swan Road>, <Tucson>, <AZ> <85711>> B.2.13.7.6. Customs and Border Protection, San Diego Sector Headquarters, <<2411 Boswell Road>, <Chula Vista>, <California> <91914>> B.2.13.7.7. Customs and Border Protection, Rio Grande Sector Headquarters, 4400 South Expressway 281, <<Edinburg>, <Texas> <78542>> B.2.13.7.8. Customs and Border Protection, Marfa Sector Headquarters, <<300 East Madrid Street>, <Marfa>, <Texas> <79843>> B.2.13.7.9. Customs and Border Protection, <<Laredo>> Sector Headquarters, <<207 W. Del Mar Blvd.>, <Laredo>, <Texas> <78041>> B.2.14. CLIN 0024 Data Transfer into AMOC (CDRL U-0006) B.2.14.1. The purpose of CLIN 0024 is to ensure sensor data is continuously transmitted to the Air and Marine Operations center (AMOC) in Riverside, California B.2.14.1.1. This can be accomplished either through existing power and communications infrastructure or, when deployed in remote locations, via the power and communications unit Sensor data shall be transmitted in one of the formulas specified in the applicable documents in the SOO.

B.2.14.2. The AMOC shall have remote control capability for the sensor component.

B.2.14.2.1. Remote control capability means the operator at the AMOC has the same level of control as the field operator on site with the sensor package.

B.2.14.2.2. This capability has to be established either through existing power communications infrastructure or, when deployed in remote locations via the power and communications units.

B.2.14.2.3. The vendor shall grant to the Government rights consistent with FAR 52.227-14.

B.2.15. CLIN 0025 Vendor Travel (Reimburseable CLIN)

B.2.15.1. This CLIN supports all approved allowable Vendor Travel associated with the base year of this contract.

B.2.15.2. The offeror is to propose this CLIN as an NTE amount.

B.3. TYPE OF CONTRACTContract

B.3.1. This is a multiple award indefinite delivery, indefinte quantity (IDIQ) contract with a cost reimbursable line item for travel.

B.3.2. Supplies and Services may be ordered from this contract.

B.3.3. Delivery Orders or Task Orders in accordance with FAR 16-501-1 will be issued against this contract

B.3.3.1. If a combination of Supplies and Services are ordered on the same document, the term Delivery Order may be used interchangeably with Task Order.

SECTION C. STATEMENT OF OBJECTIVES (SOO)

C.1. SCOPE

C.1.1. The scope of this SOO includes all necessary work for deployment of the system, training, maintenance, system delivery to the end-users, and full Government acceptance of system products and services.

C.2. PURPOSE AND INTENT

C.2.1. This Statement of Objectives (SOO) is for the procurement of a capability to provide for the persistent detection and tracking of aircraft that fly across <<United States>> borders that are slow moving, fly at low altitudes, and have a low radar cross section.

C.2.2. This is an immediate high priority threat. The intent of this SOO is to acquire a system that is able to use existing sensor technology to detect and track these aircraft.The approach will focus on existing systems that meet requirements rather than developmental systems which are not ready for immediate deployment.

C.2.3. Vendors should use this SOO to develop their Performance Work Statements (PWS) to be submitted as part of their proposal.

C.2.4. The terms Contractor, Offeror, Supplier, and Vendor are used interchangeably throughout this document and refer to the company or team of companies who are responding to the RFP.

C.2.5. The system will transmit real time sensor data to the Air and Marine Operations Center (AMOC) in Riverside, CA, either through its external power and communications infrastructure or, when deployed in remote locations, via its own internal power and communications package.

C.2.5.1. Data must integrate into the AMOC.

C.2.5.2. Acceptable AMOC data protocol is provided in Attachment 3.

C.2.5.3. In addition, the AMOC desires remote control capability for the system.

C.2.5.4. Remote control capability means the AMOC has the same level of control as the operator who is on-site with the system.

C.2.6. Training is required for a limited number of personnel.

C.2.6.1. Training shall include equipment setup, operations, disassembly, packaging for transport and field level maintenance.

C.2.6.2. Operator and user maintenance manuals should be provided in contractor format that provide the minimum essential information to operate and maintain the system.

C.2.6.3. Vendor shall develop an operations and maintenance training curriculum and conduct a training course for a limited number of CBP personnel upon acceptance of the system to permit the Government to operate and deploy the system.

C.2.6.4. The goal is to provide operations and maintenance training to adequately prepare all personnel who will be involved in operating and maintaining the system.

C.2.6.5. Training will include but is not limited to corrective and preventative maintenance.

C.2.7. The deployment concept includes two scenarios.

C.2.7.1. In the first scenario, the sensor technology will be deployed at existing CBP facilities where existing electrical power and communications infrastructure may be utilized.

C.2.7.2. In the second scenario, the sensor technology will be remotely deployed where there is no available electrical power or communications infrastructure.

C.2.7.3. In this second scenario the desired system is intended to be self contained, able to operate without external power or CBP communications infrastructure.

C.2.8. The system must be transportable, capable of being deployed along the Borders of the <<United States>> and be rugged enough to support a wide range of deployed operations in all types of weather and terrain conditions.

C.2.8.1. It will also optimize system sustainability and maintainability.

C.2.8.2. The system will provide the capability to detect and track aircraft with low radar cross sectional areas, with the goal of facilitating a CBP response and resolution.

C.3. BACKGROUND

C.3.1. The Secure Border Initiative (SBI) within CBP is a comprehensive multi-year plan to secure <<America>>’s borders and reduce illegal migration.

C.3.2. SBInet is the component of SBI using the technology and tactical infrastructure solution for border control.

C.3.3. The SBInet Systems Program Office (SPO) is charged with developing, acquiring, fielding, testing and sustaining an integrated system to achieve border control.

C.3.4. Our customers are the operational forces of CBP – the Office of Border Patrol (OBP), Office of Field Operations (OFO), and the Office of Air and Marine (OAM).

C.3.5. OBP requested assistance from SBI in defining the requirements and funding a project to respond to the high priority threat presented by small, low flying aircraft transiting across <<United States>> borders.

C.3.6. SBInet is tasked with addressing this threat.

C.4. PERFORMANCE OBJECTIVES

C.4.1.1. 4.1 System should accurately, detect and track aircraft with a RCS of 0.5 m2 from 33 feet Above Ground Level (AGL) to 15,000 feet above Mean Sea Level (MSL), in various types of terrain (i.e. flat and mountainous) and a wide range of ambient temperatures.

C.4.1.2. 4.2 System should be able to detect and track targets that are in line-of-sight from the system. The minimum desired detection range is 1 kilometer and the desired maximum range is equal to or greater than 20 kilometers.

C.4.1.3. 4.3 System should be able to detect and track at least twenty-five (25) targets of interest (TOIs) at the same time.

C.4.1.4. 4.4 System should be easily transportable for set-up in remote locations with an objective of a maximum three (3) hour pack/un-pack time (includes setup of communications link).

C.4.1.5. 4.5 When deployed to remote areas without grid power and without CBP communications, operation of the system for ninety-six (96) continuous hours or more is desired with the understanding the system may off-line for short periods of time for refueling the power component.

C.4.1.6. 4.6 When deployed to CBP facilities with grid power and communications infrastructure, the system should be capable of sustained and persistent operations for a minimum period of two weeks. Continuous operations greater than two weeks are desired.

C.4.1.7. 4.7 System should be capable of operations in extreme weather environments (-40o to 125 o F and 0 to 100% humidity) without performance degradation.

C.4.1.8. 4.8 System should be capable of detecting and tracking TOIs at a minimum airspeed of 24 knots up to at least 55 knots. Detecting and tracking at higher airspeeds up to 150 knots is desired.

C.4.1.9. 4.9 System capable of being transported by multiple means and able to withstand transport over rugged terrain.

C.4.1.10. 4.10 First article testing will be performed in a controlled, operationally relevant environment to determine how well the system meets requirements.

C.5. RISK MITIGATION

C.5.1. The Government perceives risk in this type of technology.

C.5.2. The Contractor shall provide metrics by which high risk or critical performance parameters may be monitored.

C.5.3. The Contractor shall present an integrated summary of all risks, mitigation strategies, and the effects of the mitigation strategies on their respective systems.

C.5.4. Risk management as a shared or centralized activity must accomplish the following tasks:

C.5.4.1. Identity concerns.

C.5.4.2. Identify risks & risk owners. 1 C.5.4.3. Evaluate the risks as to likelihood and consequences.

C.5.4.4. Assess the options for accommodating the risks

C.5.4.5. Prioritize the risk management efforts.

C.5.4.6. Develop risk management plans.

C.5.4.7. Authorize the implementation of the risk management plans

C.5.4.8. Track the risk management efforts and manage accordingly.

C.6. APPLICABLE DOCUMENTS

C.6.1.1. Ultra Light Aircraft Detection (ULAD) Capabilities Matrix (J.1 – Attachment 1) C.6.1.2. DHS and CBP <<Enterprise>> Architecture Document (J.2 - Attachment 2) C.6.1.3. AMOC Sensor Data Format (J.3 - Attachment 3) C.6.1.4. CBP Training Development Standards (J.4 - Attachment 4)

SECTION D. PACKAGING & MARKING

D.1. <PACKAGING & MARKING>

D.1.1. <Material shall be packaged, packed and marked for shipment in such a manner that will insure acceptance by common carriers and safe delivery at destination.

D.1.2. Packages shall be clearly identified on the outer wrapping with the contract number and delivery/task order number.

D.1.3. Any pertinant Packageing and Marking applicable to an indivdual delivery/task order will be specified in the delivery/task order.

SECTION E. INSPECTION & ACCEPTANCE

E.1. <<FAR CLAUSES INCORPORATED BY REFERENCE

E.1.1. 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)>

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): <www.acquisition.gov>

FEDERAL ACQUISITION REGULATION (48 CHAPTER 1) CLAUSES>

E.2. <ULAD FIRST ARTICLE TEST (FAT)>

E.2.1. The Vendor shall price FAT support labor under CLIN 0001 and Travel under CLIN 0011.

E.2.2. Vendor support costs for subject matter expertise shall be billed under CLIN 0009 (Vendor Technical Support) if requested by the government.

E.2.3. Prior to Government acceptance, the system is owned by the Vendor, therefore, if repairs are necessary, the cost will be borne by the Vendor.

E.2.4. For the purpose of Vendor planning, the Vendor will assume FAT will take place in <<Tucson>, <AZ.>> E.2.5. The test shall be executed by the Government and be supported by the vendor.

E.2.6. In support of FAT, the vendor shall prepare FAT Plan and Procedures for review and approval by the Government.

E.2.7. For the purpose of consistency, the Vendor shall submit FAT Plan at least two (2) weeks in advance of ULAD FAT.

E.2.8. Price travel to and from <<Tucson>, <AZ>>; the number of people (labor hours) proposed is decided by the Vendor.

E.2.9. Upon completion of FAT, the Government shall prepare a FAT Report, with vendor support as required.

E.3. ULAD Unit Acceptance Test (CDRL 0009)

E.3.1. Subsequent ULAD Units (i.e., after the first FAT unit) will be subjected to an ULAD Acceptance Test consisting of system check-out and an initial six hour operating period.

E.3.2. The vendor shall support the Government’s ULAD Unit Acceptance Test efforts as needed.

E.3.3. After the ULAD Unit/Units reaches the deployment site (Border Patrol Station or Sector Headquarters), the Government shall conduct system check-out to ensure the ULAD Unit is free of readily apparent defects.

E.3.4. After the ULAD Unit successfully completes system check-out, the Government will then conduct a six hour operating period where each unit will be operated under field conditions.

E.3.5. In support of the six hour operating period, the vendor shall prepare an Operating Period Performance Test Plan and Procedures for review and approval by the Government.

E.3.6. The purpose is to ensure the production articles work as advertised in the operational environment of intended use.

E.3.7. Upon completion of UAT, the Government shall prepare a UAT Report, with vendor support as required.

E.3.8. ULAD Unit/Units will be accepted by the Government upon successful completion of Unit Acceptance Test and procedures to TBD after contract award between Government and vendor.

SECTION F. DELIVERIES OR PERFORMANCE

F.1. <FAR CLAUSES INCORPORATED BY REFERENCE

F.1.1. 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)>

<This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): <www.acquisition.gov>

F.2. CLAUSES IN FULL TEXT>

F.2.1. 52.211-9 Desired and Required Time of Delivery (June 1997)

The Government desires delivery to be made according to the following schedule:

Desired Delivery Schedule

[Contracting Officer insert specific details]

If the offeror is unable to meet the desired delivery schedule, it may, without prejudicing evaluation of its offer, propose a delivery schedule below. However, the offeror’s proposed delivery schedule must not extend the delivery period beyond the time for delivery in the Government’s required delivery schedule as follows:

Required Delivery Schedule

[Contracting Officer insert specific details]

Offers that propose delivery of a quantity under such terms or conditions that delivery will not clearly fall within the applicable required delivery period specified above, will be considered non-responsive and rejected. If the offeror proposes no other delivery schedule, the desired delivery schedule above will apply.

Offeror’s Proposed Delivery Schedule

[Contracting Officer insert specific details]

(b) Attention is directed to the Contract Award provision of the solicitation that provides that a written award or acceptance of offer mailed or otherwise furnished to the successful offeror results in a binding contract. The Government will mail or otherwise furnish to the offeror an award or notice of award not later than the day the award is dated. Therefore, the offeror shall compute the time available for performance beginning with the actual date of award, rather than the date the written notice of award is received from the Contracting Officer through the ordinary mails. However, the Government will evaluate an offer that proposes delivery based on the Contractor’s date of receipt of the contract or notice of award by adding (1) five calendar days for delivery of the award through the ordinary mails, or (2) one working day if the solicitation states that the contract or notice of award will be transmitted electronically. (The term “working day” excludes weekends and U.S. Federal holidays.) If, as so computed, the offered delivery date is later than the required delivery date, the offer will be considered nonresponsive and rejected.

(End of clause)

F.2.2. 52.247-60 GUARANTEED SHIPPING CHARACTERISTICS (DEC 1989)

<(a) The offeror is requested to complete paragraph (a)(1) of this clause, for each part or component which is packed or packaged separately. This information will be used to determine transportation costs for evaluation purposes. If the offeror does not furnish sufficient data in paragraph (a)(1) of this clause, to permit determination by the Government of the item shipping costs, evaluation will be based on the shipping characteristics submitted by the offeror whose offer produces the highest transportation costs or in the absence thereof, by the Contracting Officer's best estimate of the actual transportation costs. If the item shipping costs, based on the actual shipping characteristics, exceed the item shipping costs used for evaluation purposes, the Contractor agrees that the contract price shall be reduced by an amount equal to the difference between the transportation costs actually incurred, and the costs which would have been incurred if the evaluated shipping characteristics had been accurate.

(1) To be completed by the offeror:

(i) Type of container: Wood Box [__], Fiber Box [__], Barrel [__], Reel [__], Drum [__], Other (Specify) ________;

(ii) Shipping configuration: Knocked-down [__], Set-up [__], Nested [__], Other (specify) _____________;

(iii) Size of container: ____ (Length), [__] ___ (Width), [__] ___ (Height) = ___ Cubic Ft;

(iv) Number of items per container ________ each;

(v) Gross weight of container and contents ____ Lbs;

(vi) Palletized/skidded [__] Yes [__] No;

(vii) Number of containers per pallet/skid ______;

(viii) Weight of empty pallet bottom/skid and sides _______ Lbs;

(ix) Size of pallet/skid and contents _______ Lbs Cube ________;

(x) Number of containers or pallets/skids per railcar __________ *

(A) Size of railcar _____________

(B) Type of railcar _____________

(xi) Number of containers or pallets/skids per trailer ________*

(A) Size of trailer _________ Ft

(B) Type of trailer _________

* Number of complete units (contract line item) to be shipped in carrier's equipment.

(2) To be completed by the Government after evaluation but before contract award:

(i) Rate used in evaluation __________;

(ii) Tender/Tariff __________;

(iii) Item _________.

(b) The guaranteed shipping characteristics requested in paragraph (a)(1) of this clause do not establish actual transportation requirements, which are specified elsewhere in this solicitation. The guaranteed shipping characteristics will be used only for the purpose of evaluating offers and establishing any liability of the successful offeror for increased transportation costs resulting from actual shipping characteristics which differ from those used for evaluation in accordance with paragraph (a) of this clause.

(End of clause)

F.2.3. 52.247-62 SPECIFIC QUANTITIES UNKNOWN (APR 1984)>

<(a) For the purpose of evaluating "f.o.b. destination" offers, the Government estimates that the quantity specified will be shipped to the destinations indicated:

(b) If the quantity shipped to each destination varies from the quantity estimated, and if the variation results in a change in the transportation…