ULAD Solicitation Amendment 0001.pdf
PDF 507 KB Posted
- Attached to
- Ultra Light Aircraft Detection (ULAD)
- Solicitation number
- HSBP1010R0074
About this file
ULAD Solicitation Amendment 0001
View the file
Other files
Show all 41
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 PAGES
1 I 13
2. AMENDMENT/MODIFICAITON NO.
Amendment # 0001
3. EFFECTIVE DATE
03/25/11
4. REQUISITION/PURCHASE REQ. NO.
20062528
5. PROJECT NO. (If applicblel
6. ISSUED BY CODE 7014 7. ADMINISTERED BY (If other than Item 6) CODE
DHS - Customs and Border Protection Enterprise Contracting Office 1901 South Bell Street, 8th Floor Arlington, VA 22202-3292
DHS - Customs and Border Protection Enterprise Contracting Office 1901 South Bell Street, 8th Floor Arlington, VA 22202-3292
8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X) AMENDMENT OF SOLICIATION NO.
HSBP1010R0074
DATED (SEE ITEM 11)
03/25/11
MODIFICATION OF CONTRACT/ORDER NO.
DATED (SEE ITEM 11)
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 MI is extended, q 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 0 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your 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 APPROPIRATION DATA (If required)
13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.
IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.
CHECK ONE THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER
NO. IN ITEM 10A.
K THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).
THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:
OTHER (Specify type of modification and authority)
E. IMPORTANT: Contractor is not, q 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.)
1. The purpose of this Amendment is to:
Responses to vendors questions submitted prior to 3/15/2011(See continuation pages SF 30).
Amend the solicitation (See continuation pages SF 1449).
2. All other terms and conditions remain unchanged and in full effect.
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 1 OA, 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)
Jud h A. Simpsonh/Contracting Officer
15B. CONTRACTOR/OFFEROR 15C. DATE SIGNED
16B. UN D STATE'. OF KMERIC ,
'4111 -4166.44AAILL/&
16C. DATE SIGNED
3/07 Z1/1(Signature of person authorized to sign) (Signature of I .ntracting Officer)
NSN 7540-01-152-8070
STANDARD FORM 30 (REV. 10-83)
Previous edition unusable Prescribed by GSA FAR (48 CFR) 53.243
HSBP1010R0074
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION SF 30 — BLOCK 14 CONTINUATION PAGE
The following have been added by full text:
RESPONSE TO VENDOR'S QUESTIONS
Questions submitted in response to ULAD Solicitation # HSBP1010R0074 Answers to Questions received by closing date March 15, 2011.
Number Question/Comments Answer 1 Which volume is contractual information
(e.g., SECTION K. REPRESENTATIONS, CERTIFICATIONS, OTHER
STATEMENTS OF OFFEROR) suppose to go in? Normally, when there are only 2 volumes, it should be in Volume II. Please clarify.
Submit in Volume I, Representations and certifications will not count against 50 page limit
2 If the proposed prime is a small business, then the Small Business Subcontracting Plan required, per solicitation Section L.5, is not required, per FAR Subpart 19.7, 19.702 Statutory requirements, paragraph (b)(1)?
Please confirm.
Small Business Subcontracting Plan is not required of Small Businesses per FAR Subpart 19.7, 19.702
3 If we put the contractual information in Volume I, which is limited to 50 pages, will the contractual information be excluded from the page count?
Yes
4 Section C 3.1.3 states: "The ULAD System shall be IEC 61000 compliant."
In Attachment 9, Environment Document, there is no reference to IEC 61000, but it directly references FCC Title 47, CFR 15 and
MIL-STD-461.
Recommend removing reference to IEC 61000.
C.3.1.3 Amended (See solicitation amendment).
C.3.3.5 Added (See solicitation amendment).
5 Section 3.3.3 states: "The ULAD system should be able to operate continuously off its own power for 96 hours without operator intervention."
Is refueling of a generator considered during the 96 hours of continuous operation?
Refueling is considered operator intervention.
6 Section C.5.1.1 states: "The vendor should develop their support plan and pricing based on maintaining the initial 16 ULADs for a period of one year at the Tucson location."
CLINS 0001, 0002, 0003, 0004, 0009, 0010,
0011, 0012, as well the option years require pricing for stepped ladder pricing for up to 50 systems. Section C.5.1.1 specifies pricing for only the initial 16 ULADs for a period of one year at Tuscon, Blaine, El Paso, and Yuma.
We assume we are pricing to Attachment J-16 for CLINS 0009, 0010, 0011, and 0012, however the range quantities and the evaluated quantities in J-16 conflict with Section C5.1.1. Please correct pricing spreadsheet.
C.5.1.1 Amended. See amendment to solicitation.
See Attachment J 16 (Pricing Instructions) Revised (Page 3 — CLIN 0001, 0002, 0003, 0004)
7 Section C.4.1. states: "The vendor will be required to demonstrate to the government that the vendor's proposed solution meets the performance requirements of the contract.
This demonstration will be performed on the first system delivered to the government, will be considered an acceptance inspection (FAR 12.204.b), and shall be conducted in a representative operational environment for the southwest border."
Attachment 11 for CDRL A001 indicates that the "initial delivery order" needs to be tested.
The RFP defines the "initial delivery order" as 1-3 (or more) systems. Please clarify if one
(1) system, or up to three (3) systems will undergo an acceptance inspection.
One system will be demonstrated for acceptance inspection.
In an effort to fully respond to support 75%
vs. 95% Availability, we need to understand the complete mission profile of the ULAD system, how many ULAD Systems will be operating at fixed locations as opposed to remote locations? How often will they operate? What is the operational tempo?
Government will not divulge operational information as it pertains to locations.
Systems will be required to operate on a 24/7 basis for 365 days.
How many ULAD systems will be deployed remotely per week per Border Patrol Sector?
Required information to support 75% vs. 95% Availability.
Government will not divulge operational information.
Will the generator be transported with the ULAD system when the radar is returned to the vendor depot for repair? May impact transport options impacting Ao.
The vendor will determine whether individual sub-systems are to be returned for repair and if any other components need to be transported with them.
Will Border Patrol Agents supply failure information by ULAD system serial number and operational times? What frequency?
This data is required to in support of the CMLS services monthly report to demonstrate "operational availability of all ULAD systems".
When required, CBP will send specified information to the vendor.
12 What is the CBP definition of a failure? Is a degraded state considered a failure? This is required information to support 75% vs. 95% availability plus reporting monthly availability per ULAD system.
Failure is any event impacting the ULAD system in a way that degrades system capability below threshold as stated in the
RFP.
Can the proposal be hand delivered?
Yes L.6.2.3 will be Amended.
Can the submission via CD be >5MB?
Yes
15 Section L.6.10.6 states that the Executive Summary, Past Performance, title pages, table of contents, section dividers, transmittal letters, and cover pages will not count in page limits.
Section L.7.2.2 Section 2 - Executive Summary and Table of Contents (no more than 3 pages) indicates that Table of Contents are counted as part of the Executive Summary page count.
Please delete the Table of Contents from the Executive Summary page count.
Table of Contents will not be counted as part of Executive Summary.
16 It appears that Section 6 is missing. The Section jumps from Section 5 Past Performance on page 88 (L.7.2.8.) to Section 7 Assumptions, Exceptions, and Deviations on page 89 (L.7.2.9).
Section L will be Amended to correct administrative error: L.7.2.9 is Section 6 L.7.2.10 is Section 7
17 Technical Sub-factor 1.12 of RFP states that "Vendor can meet the required delivery schedule: 1-3 ULAD Systems in 180 days after delivery order award; subsequent systems and subsystems within 90 days of delivery order award."
Is it the Government's intent that the vendor deliver all systems ordered on a subsequent delivery order (DO), i.e. after the first DO, 90 days after receipt of order (ARO) regardless of the quantity ordered; or would deliveries commence 90 days ARO and the vendor can propose an optimum monthly delivery rate?
If the latter, does the Government have a desired or required minimum monthly delivery rate?
As currently written, if a large quantity of systems is ordered on a single DO, the vendor would have to deliver all systems in a very short period - probably faster than the Government can deploy them. It would be more economical and less risky for vendors to have the opportunity to start deliveries within 90 or 45 days and deliver at a steady rate until the order is filled.
F.2.1 amended (See solicitation amendment)
Delivery of subsequent systems to commence within 90 days of delivery order award and deliver at a steady rate until order is filled.
The vendor's proposed schedule will be for evaluation purposes. The actual delivery schedule will be established when orders are placed.
18 Inconsistent Objective values for Minimum velocity. M.7.4 Sub-factor 1.8a lists Min Vel <5 kts. Attachment J12 Sub-factor 1.8a is <2 kts. Please clarify.
The objective for minimum velocity is 4 kts.
19 Inconsistent Objective values for Maximum Velocity. M.7.4 Sub-factor 1.8b lists MDV <100 kts. Attachment J12 Sub-factor 1.8b is <120 kts. Please clarify.
The objective for maximum velocity is �120 kts.
20 M.7.4 Technical Sub-factor 1.12 System Delivery and Subsequent System Delivery states that the Threshold for desired delivery schedule of 1-3 ULAD systems is 180 days and subsequent systems and subsystems within 90 days. The Objective is for delivery of 1-3 ULAD systems in 90 days and subsequent in 45 days.
F.2.1 Desired and Required Delivery Time is listed as Quantity TBD within 150 days. If the offeror is unable to meet the desired delivery schedule it may offer a delivery schedule of Quantity TBD within 180 days.
Please clarify the Threshold and Objective and Desired and Required Delivery Schedules.
F.2.1 Amended See solicitation amendment.
21 We assume Attachment J-15 ICSP (CDRL A002) is an attachment and not part of the 50 page limit for the Technical volume. Please clarify.
ICSP will not be counted toward 50 page count
22 Directions state "Vendor will submit a table showing price of each CDRL." In the Table samples, CLIN 0007 CDRLs state "NSP."
Additionally, Section B.2.5 of the solicitation states "CDRLs shall be non-separately priced." Please confirm all CDRLs are to be NSP.
All CRDL's are NSP.
23 Is it the Government's intent to have the vendor price 50 ULAD systems in the "Total Base Price" and 50 ULAD units each for Option periods 1, 2, and 3? This would total 200 ULAD systems rather than the 155 maximum as stated in Section B.2.4 of the Solicitation (Page 4 of 101).
B.2.4 Amended. See amendment to solicitation.
Intent is to price 144 total units.
See Attachment J 16 (Pricing Instructions) Revised
24 Please clarify how vendors should address obsolescence management on a FFP contract that extends 10 years in duration.
The vendor should describe a proactive obsolescence plan appropriate for each phase in the system life cycle system and plan accordingly (e.g. component upgrades, technology refresh). See C.6.1.6
25 Section C 3.1.3 states: "The ULAD System shall be IEC 61000 compliant."
In Attachment 9, Environment Document, there is no reference to IEC 61000, but it directly references FCC Title 47, CFR 15 and
MIL-STD-461.
Recommend removing reference to IEC 61000.
C.3.1.3 Amended (See solicitation amendment).
26 Section 3.3.3 states: "The ULAD system should be able to operate continuously off its own power for 96 hours without operator intervention."
Is refueling of a generator considered during the 96 hours of continuous operation?
Refueling is considered operator intervention.
27 A review of section L,7.2 of the solicitation, pages 88-89, Lists section 1 thru 5 and 7.
Section 6 appears to be missing. Please clarify?
Section L will be Amended to correct administrative error: L.7.2.9 is Section 6 L.7.2.10 is Section 7
28 Reference Section M.7.3.5 refers to sub-factor
1.13. Please clarify where this sub-factor is
listed in Table Cla as described in paragraph M.7.3?
Sub-factor 1.13 is located in Table Clb.
29 M.7.5, page 96, Table C lb lists one criteria.
Please confirm this is the only criteria in Table C lb?
Confirmed.
30 Does the PWS required by paragraph C.4.2, page 36 of the RFP, count as part of the page limitation of the technical response or does this attachment fall outside of the page count?
Paragraph C.4.2 is part of the PWS which is part of the not to exceed 50 page limit
31 If we provide an ILSP, will it be counted against the maximum 50 page count limitation?
ICSP will not be counted toward 50 page count
32 If an offeror provides a WBS, does this count in the page count for the Technical Volume?
No
33 Is CLIN 0001 to be priced as a complete ULAD system to include the Sensor, Remote Power, and Communications subsystems combined?
Yes
See Attachment J 16 (Pricing Instructions) Revised
34 Is CLIN 0002 to be priced as a "stand alone" (non-integrated) Sensor subsystem?
Yes See Attachment J 16 (Pricing Instructions) Revised
35 Is CLIN 0003 to be priced as a "stand alone" (non-integrated) Remote Power subsystem?
Yes See Attachment J 16 (Pricing Instructions) Revised
36 Is CLIN 0004 to be priced as a "stand alone" (non-integrated) Communications subsystem?
Yes See Attachment J 16 (Pricing Instructions) Revised
37 As technical proposal responses may be significantly impacted by the eventual publication of answers to the questions submitted on March 15, would the Government please consider a 2 week proposal response extension to account for this expected response time?
See solicitation Amendment.
38 Page 4 of 101 paragraph B.2.4 states the vendor shall provide pricing for each CLIN identified below in accordance with Instructions in Section L.
Starting on page 5 of 101 there are individual blocks set up for each CLIN. How should the offeror present pricing on this format? For example, the block CLIN 001 on page 5 of 101 has one box each for Quantity, Unit Price and Total Price. Is it expected that the offeror reflect a weighted average of the step pricing at a specific quantity in completing the CLIN pricing for Section B? Please clarify.
Vendor will not provide pricing in Section B CLIN structure relative to CLIN's 0001 — 0004 and their associated option period CLIN's.
See Attachment J 16 (Pricing Instructions) Revised
39 Pages 5-34 of 101: Can the Government provide these pages in editable format?
No
40 Page 36 of 101 Par. C.4.1: What is the significance of using the reference to FAR 12.204b with respect to performance of an acceptance inspection? Please provide a corrected FAR reference, if applicable.
C.4.1 Amended. See amendment to solicitation.
41 Page 36 of 101 Par. C.5.1.1: Please provide the forecasted quantities, by maintenance location, by option year, so that an accurate assessment of resources can be made for each of the four facilities. Please clarify which location in Washington is correct (Par C.5.1.1 "Blaine", Wa. Or CLIN 0012 "Bellingham", Wa.)
C.5.1.1 Amended. See amendment to solicitation.
42 Page 37 of 101 Par. C.5.1.1: This paragraph directs offerors to base maintenance pricing on 16 ULAD's in Tucson, however the base year quantity could be as large as 50 systems.
What assumptions are offerors to make about the other (potential) 34 ULAD systems? Is 16 the maximum quantity in Tucson and the other 34 allocated evenly between the other three locations? Please clarify why this paragraph describes 16 ULAD's in Tucson but is silent on the remaining potential quantities and the remaining three locations.
See Attachment J 16 (Pricing Instructions) Revised.
Pricing for evaluation is nine (9) per location for a total of 36 units per location per period.
43 Page 38 of 101 Par. C.7.3: Please clarify the meaning of "suggested services" since it does not appear in MIL-PRF-49506.
MIL-PRF-49506 is an informative reference that states a range of services that the vendor could propose.
44 Page 39 of 101 Par C.8.3: Please clarify the "operational scenarios" that should be emphasized in the training.
The vendor is to give recommendations on training for operations and maintenance of the system.
45 Page 39 of 101 Par. C.11.1: Please confirm that the technical drawing package required is for the adequate level of sustainment at the operator level since maintenance levels below the operator level will be managed by the offeror.
The Government intends to use the commercial drawing packages as source documentation to manage the product baseline of the ULAD System.
46 Page 40 of 101 Par. C.13.2: For consistency of pricing, how many trips and how many days per trip should be assumed for each of the 3 locations? Was Bellingham, Washington intentionally omitted from this paragraph?
Vendor to propose as a NTE based on vendor's Maintenance and Logistics Support concept.
47 Page 43 of 101 Par. F.2.2. (a) & (b): There are no estimated quantities provided. Please provide the estimated number of ULADs per location.
FAR 52.247-62 Specific Quantities Unknown remains TBD.
48 Page 60 of 101 Par 1.2.7: Clause 52.216-24 "Limitation of Government Liability" has been included in the Government's solicitation. This clause provides for a limitation of the Contractor's expenditures when a letter contract is anticipated. In the solicitation, CBP identified this value as "one ATE system". Please elaborate the use of the term ATE and how this relates to a ULAD.
FAR 52.216.24 will be removed.
49 Can an editable version of the Past Performance Questionnaire be provided?
No
50 Par. 1.0: Please confirm "MSC" should be
"ULAD".
Confirmed.
51 Att 9 Pg 7 of 14(EMC): Please clarify the requirement for ULAD system interoperability in the presence of an LMR.
(An LMR is not mentioned in the SOO or the Required Capabilities Matrix)
Minimal disruption of system when LMR is transmitting.
See SOO C.3.2 (ULAD Environmental Requirements)
52 Att 11 & Sec C.6.1: Please clarify if the ICSP is due with the proposal (per C.6.1) or 45 days ARO (per J11).
See solicitation amendment. Due with proposal.
53 Att 10 & 12: There appears to be a disparity with two references citing max detection range in the solicitation, (e.g. the objective max detection range in (J10) is 25km and in (J12) it is 26km. Is this a typographical error?
Please clarify.
Attachment J 12 will be amended.
54 Att 16, Pg 1: In the instructions for Volume II there is a description of the Executive Pricing Summary that states that all of the Offeror's prices proposed will be listed and described. Do the Pricing Tables 1 thru 6 provide an acceptable listing?
Yes
55 Att. 16, Pg. 3: Please confirm that the pricing provided in CLIN's 0009-0012 are for both warranty and non warranty maintenance actions.
Pricing will not pertain to warranty.
56 Att16, Pg 3: In the instructions for Volume II it states that for calculation of the Total Base Price and Total Option Prices CLINs X002, X003 and X004 are excluded. In Table 1 the sum of the prices for each subsystem is more than the total system price (i.e. Total Price for CLIN 0002 QTY 10 $2,500 plus CLIN 0003 QTY 10 $2,500 plus CLIN 0004 QTY 10 $2,500 equals $7,500 total price. This is more than the CLIN 0001 QTY 10 total price of $7,000. Are the subsystem prices intended to equal the total ULAD system price?
See Attachment J 16 (Pricing Instructions) Revised
Prices displayed are a sample. Vendor determines if sub-system prices equal the total ULAD System price.
57 Does the Government intend to procure any ULAD Sub-systems as stand-alone components?
The Government may procure standalone sub-systems.
58 Attachment 16 Can all required pricing tables be provided in editable format?
No
59 Pg 86 of 101 Par L.6.7 & L.6.10.1: Please clarify what appears to be contradictory language; "There is no intent to limit the contents of proposals" (L.6.7) vs. the 50 page limitation defined in L.6.10.1.
The sections are intended to be read in conjunction with each other, and that while offerors are not limited in the content or types of information or data they wish to provide, the length of the proposal must conform to the page limit requirements.
60 Par L.7.1.1: As a competitive procurement, the offeror believes cost or pricing data is not required. Please clarify this paragraph requesting "labor hours and categories, Materials, subcontracts, etc. that "must be contained in the technical proposal...."
L.7.1.1 Deleted (See solicitation amendment).
61 L.7.2.x Pg 89 of 101: The paragraph defining the content of Section 6 appears to have been omitted. Please clarify.
Section L will be Amended to correct administrative error: L.7.2.9 is Section 6 L.7.2.10 is Section 7
62 Attachment 11 General: Assuming the ICSP is required with the proposal submission (reference question "Att 11" above) please specify where in volume 1 it goes. (Section 6?)
Vendor can submit as an attachment.
63 Par M.7.3.1: Table Cla does not use the term "Satisfactory". Please correlate "Satisfactory" to either "Threshold" or "Objective".
Table remains as is.
64 Page 35: C.3.1.1 and C.3.1.2 state that the ULAD system must comply with an FCC requirement for low power devices and that it must also comply with IEC 61000. The FCC requirement covers unlicensed equipment with emitted power levels of 10mW maximum. IEC 61000 is a more general International requirement for electromagnetic compatibility. Please elaborate on what is the intention of specifying these two diverse requirements and their applicability to the ULAD system.
See solicitation Amendment.
IEC 61000 compliance is a desired capability.
65 Please provide clarification, with regards to L.2.7.3, are completed attachments J.12 and J.13 to be provided as attachments and are they included within the 50p limit for Technical Proposal?
Provided as attachments not included in 50 page limit.
66 The provided scans of Appendices J.12 and J.13 have illegible column headers; will the government please provide clear scans or electronic version of these tables for vendors to complete?
Revised Attachments J 12 and J 13 headers made clear
67 Technical proposal Section 6 is missing or undefined is this placeholder for future material or should vendors disregard it in their responses?
Section L will be Amended to correct administrative error: L.7.2.9 is Section 6 L.7.2.10 is Section 7
68 With regards to L.2.7.4 Independent Validation, should the vendors provide copies of these reports as attachments to submittal?
Yes
69 Should the vendors complete and provide hard copies of the Certifications and Representations as part of the Price Volume — or are the online versions sufficient?
Submit in Volume I, Representations and certifications will not count against 50 page limit.
70 Per L.2.52.216-1, the change to a single awardees will limit USG options for the consideration of a variety of technical approaches, please consider returning to the multiple award option so the USG can consider low cost technical solutions, such as biostatic radars, optical systems, and other novel approaches from small businesses in parallel to primary radar effort.
No change.
HSBP 1010R0074
SECTION SF 1449 — CONTINUATION SHEET
SOLICITATION/CONTRACT FORM
The solicitation is amended as follows:
B.2.4 Amended (Change 155 complete units to 144 complete units).
CLIN 0007 and associated option CLIN's Amended (CDRL A004 deleted).
C.3.1 Amended (Any proposal not meeting the requirement of 3.1.1 — 3.1.5 will not be considered for further award).
C.3.1.3 Amended (Move — The ULAD system shall be IEC 61000 compliant to C.3.3.5. Add:
"US Government NTIA Certifications: The contractor will ensure that all radio frequency radiating/transmitting equipment offered either already has a "NTIA Certification of Spectrum Supportability" and will deliver a copy of the certification to OTIA in PDF format, or they will document the requisite product technical data in NTIA 'El-CID" program database needed for a certificate application, and deliver it in "EL-CID" format to OTIA for further submission to
NTIA".
C.3.3.5 Added (The ULAD system shall be IEC 61000 compliant).
C.4.1 Amended (Replace FAR 12.204(b) with FAR 12.402).
C.5.1.1 Amended (The second sentence to read: The vendor should develop their support plan and pricing based on maintaining ULAD systems for a period of one year at the Tucson Arizona, El Paso Texas, Yuma Arizona and Bellingham Washington locations).
C.7.2 Amended (CDRL A003 changed to A002).
C.8 Amend (CDRL A002 ICSP deleted — A002 now CMLS Services Monthly Activity Report — A003 now T3 Course Documentation — A004 deleted).
C.8.1 Amended (The Government requires the vendor to provide a T3 Course for development of a cadre group (Master Trainers) within CBP. The Train-the Trainer (T3) course for ULAD covers the Base Period and any update training required that impacts system functionality and preventive maintenance through the final ordering period.
F.2.1 Amended (Add to F.2.1 — Delivery of subsequent systems and sub-systems to commence within 90 days of Delivery order award and deliver at a steady rate until order is filled).
1.2.5 (b) (1) Amended (Replace 50 with 36).
HSBP 1010R0074
Attachment J 11 Amended (CDRL revised numbering — A002 CMLS Services Monthly Activity Report — A003 T3 Course Documentation).
Attachment J 12 Amended (Sub-factor 1.8a — replace < 2 with �2, Sub-factorl.8b — replace < 100 with �120) Revised (Documents revised to display headers clearer).
Attachment J 13 Revised (Documents revised to display headers clearer).
Attachment J 16 Amended (Replace Attachment J 16 Pricing Instructions with Attachment J 16 Pricing Instructions Revised).
L.1 Amended (FAR 52.212-1 is Incorporated By Reference).
L.6.2.2 Amended (The proposal is due April 20, 2011 NLT 12:00 A.M.).
L.7.1.1 Deleted
L.6.2.3 Amended (8 Hard copies of Volume I and 4 Hard copies of Volume II shall be delivered by US Mail, FEDEX, UPS, DHL or hand delivered to: address remain the same)
L.7.2.8.1.6 Amended (The Vendor shall ensure completed Questionnaires are submitted by 3:00 P.M., April 13, 2011 to ULAD @ cbp.dhs.gov referencing the Solicitation Number and offeror evaluated.
L.7.2.9 Amended (Replace Section 7 with Section 6).
L.7.2.10 Amended (Is now Section 7 Warranty).
M.7.4 — Sub-factor 1.2b Amended (Under (Objective) replace 26km with 25 km).
M.7.4 Sub-factor 1.8a Amended ( Under Objective, replace < 5 knots — Not including where radial velocities are less than 5 knots with �2knots).
M.7.4 Sub-factor 1.8a Amended ( Under Objective, replace < 5 knots — Not including where radial velocities are less than 5 knots with knots).
27. M.7.4 Sub-factor 1.8b Amended ( Under Objective, replace > 100 knots with �120 knots).
| Page 1 |
| Page 2 |
| Page 3 |
| Page 4 |
| Page 5 |
| Page 6 |
| Page 7 |
| Page 8 |
| Page 9 |
| Page 10 |
| Page 11 |
| Page 12 |
| Page 13 |
File details come from the government source that posted it. Updated .