Amendment_A00001 _HSTS05-14-R-STR003.pdf

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 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.

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (If applicable)

7. ADMINISTERED BY (If other than Item 6) CODE

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION

NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

10B. DATED (SEE ITEM 13)

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.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO.

IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Attachments: RFP HSTS05-14-R-STR003 Questions & Answers 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.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (No., street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

NSN 7540-01-152-8070

Previous edition unusable

A00001

N/A

Guy D. Galloway

The purpose of this amendment is to provide responses to questions, and to extend the response date for

RFP HSTS05-14-R-STR003.

Proposal responses are due by 5:00 PM EST on Tuesday, October 14, 2014.

All other sections of RFP HSTS05-14-R-STR003 remain unchanged.

TSA Office of Acquisition 701 S. 12th Street Arlington, VA 22202 Guy Galloway 571-227-3727

2114204STR003

HSTS05-14-R-STR003

1 4

09/26/2014

09/17/2014

RFP HSTS05-14-R-STR003 Questions & Answers

Technical Questions

1. Q: Will the government be providing a sample set of railcar tracking data to be used in the dashboard capability demonstration?

A: All tracking data elements that are required for this project are spelled out in Section 2.1, Deliverables table. The table states the Deliverable action, the Due Date/Frequency of the action, who the deliverable recipient will be and the deliverable format. For example, Section 2.1 #3 reads:

3 Secure web based portal must be accessible to authorized users and allow for user generated historical and forecast TIH/RSSM rail car outputs by sorting on varying data fields.

o Data fields include, but are not limited to:

State(s), AOR(s), HTUA(s), Railroads(s), Receiver(s), Shipper(s) Interchange Location(s), Date Range, Cars in AOR Originating or Terminating within AOR, Overhead or Through TIH/RSSM Cars Inside or Outside AOR, Terminating Standardized AOR specific reports that can be generated via web based portal or delivered by request through secure email system.

o TIH/RSSM cars enroute to AOR or HTUA.

o Ability for users to query specific

TIH/RSSM rail car(s) history and forecast data o TIH/RSSM rail car data must include:

Contents, Railroad, Railcar ID, Waybill #, Origin, Ship Date, Last Reported Location, Next Forecasted Event, Current Status, Destination Location (name and location of interchange to railroad or receiver), Destination ETA, Timestamp. Origination AOR/HTUA, Destination AOR/HTUA, Last AOR/HTUA and current AOR/HTUA.

o All interchange data must include:

Railroad(s) name and Shipper/Receiver Name. Default GPS Standardized AOR specific reports that can be generated via web based portal or delivered by request through secure email system.

o Coordinate assigned to individual interchange locations to plot the location of interchange in Google Earth. Reports available with customizable date ranges and data fields.

Daily as needed by the SCB and Surface Field TSIs

TBA at time of award Standardized AOR specific reports that can be generated via web based portal or delivered by request through secure email system.

2. Q: Does the Government expect all reports that are outlined in Section 2.1 of the Statement of Work to be available via the web-accessible dashboard at time of submission?

A: No; however a link to a functional dashboard (per the RFP) will need to be included as part of offeror submissions. Offerors should use a sample set of their own data to demonstrate the functionality of the dashboard.

The contractor must source the actual CLM/GPS data independent of the Government, and it should be accessible via the dashboard and available for use within 5 days of the contract award.

3. Q: Is the current solution considered a GOTS solution? If so, will the Government provide interface documentation?

A: No, this is not a GOTS solution and there is no interface or documentation. The CLM-GPS

Data Services initiative will not be hosted on TSA (Government) servers or systems. This will be external of TSA where TSA personnel will access the data via secure web access to the contractor’s web dashboard. Per the SOW/RFP, the contractor will also need to be able to provide data points and car locations etc. via PDF, MS Excel or other mobile/portable means to a

TSA inspector’s Government issued smartphone email.

4. Q: Upon award, will the railcar tracking data be provided by the Government to the Contractor to be hosted at the Contractor site, or will the Contractor have remote access to the live railcar tracking data, or will the railcar tracking data be hosted on Government servers?

A: Per the SOW, the selected contractor will need to source the CLM/GPS data independent of the Government. This initiative will not be hosted in any way by Government servers. The contractor will not have access to any Government systems.

5. Q: Is the work to be completed on a Government site or at a Contractor location?

A: The work related to this initiative will be completed at the contractor location.

Contractual Questions

1. Q: Will the Government be providing Section L requirements for the solicitation to include proposal formatting instructions?

A: The technical volume of the proposal should be no more than 25 pages in length, with 1 inch margins, in either Adobe Acrobat or Microsoft Word format. Pricing volume has no page limitations. Any representations and certifications should be included as an addendum to your proposal response.

2. Q: Is there a current incumbent for this work? If so, will the Government share that information?

A: There is no current incumbent for the work described in RFP HSTS05-14-R-STR003. This is a new requirement.

3. Q: Will the Government share the size (FTE and dollar value) of the expiring TIHRRVS task order?

A: The TIHRRVS task order expired on 12/3/2013; the overall value was $3,508,140.90.

4. Q: Given the nature of the questions above, would the government consider extending the due date for proposals by 30 days?

A: The Government will extend the proposal due date, but not by an additional 30 days. The proposal due date is now October 14, 2014.

5. Q: Does the Combined Synopsis/Solicitation under solicitation number HSTS0514RSTR003 contain requirements similar to a current contract? If possible, please provide the current contract number.

A: No, the requirements are different. The expired TIHRRVS Task Order number is HSTS03-11-J-

MLS360.

6. Q: Is this a new requirement for the government?

A: Yes, this is a new requirement for the Government.