rfp #06-118-3388 digital video audit system for the pennsylvania turnpike commission ·...

Addendum No. 1

RFP #06-118-3388 DIGITAL VIDEO AUDIT SYSTEM

FOR THE PENNSYLVANIA TURNPIKE COMMISSION

Following are the answers to questions submitted in response to the above referenced RFP as of 12:00 Noon, Friday, December 15, 2006. All of the questions have been listed verbatim, as received by the Pennsylvania Turnpike Commission.

Q1. The RFP states “The Contractor will provide a system that would record real time and match lane equipment inputs and toll collector inputs to a video image of a particular toll transaction…The system must also provide the user with the ability to view a transaction by inquiry using either a transaction number, date and time or predefined exception events associated with a transaction.” Will you please provide a technical description of the data interface (including hardware specifications, software protocols and transaction formats) used to send transaction information from the toll system at each plaza to the DVAS?

A1. Please refer to Addendum No. 1 - DVAS System Flow Requirements.

Q2.a. How many days of images do you want to store on-line and how many days of images will be archived? A2.a. Minimum of 60 days stored on-line; 6 months archived. If need arises to retain a specific transaction/video, ability to identify transaction/video and store longer (i.e. 1 year minimum). Also, must be able to transfer to a permanent media. Q2.b. Is the storage and archiving to be done at the plaza level or at the PTC Administration offices? A2.b. Storage and archiving is to be done at the plaza level.

Q3. Is a single overview camera for all entry lanes at each plaza sufficient or are discrete cameras for image and transaction data capture required for entry lanes as well? A3. If the camera can capture all entry lanes, then a single camera would be sufficient. Please refer to Addendum No. - Lane Configuration Chart.

Q4. Is there a bonding requirement for the project? A4. Yes. The contractor should anticipate that the requirement would be the amount of the project.

Q5. Are toll transactions being displayed in real time at the PTC Central Office now? A5. No.

Q6. Are toll transactions being displayed in real time at each plaza now?

A6. The transactions are captured in real time, but not displayed.

Q7. Is all required DVAS transaction information displayed now or available now as an output from the toll system? If so, what type of file format and can a sample be provided? (Specifically transaction number and exceptions) A7. It is available, but not displayed from the toll system. It is displayed from the audit system. Minimum transactional data required: Date / Time / Plaza / Lane / Transaction number. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will mutually develop details with existing Pennsylvania Turnpike Commission representatives and contractor(s).

Q8. How much bandwidth can be allocated to the DVAS in the system network? A8. At manned lanes, the bandwidth max value is anywhere from 512K to 1920L depending on the “size” of the plaza.

Q9. How is the toll system being synchronized?

A9. The system is synchronized by a satellite enabled time server.

Q10. Is UPS power required for the DVAS equipment and if so will available UPS capacity be available at the plazas or is the contractor required to supply separate UPS equipment for the DVAS? A10. The PTC has UPS available at the plazas; It is not a requirement of the contractor.

Q11. Does PTC foresee the DVAS cameras working with the current plaza lighting or is the contractor responsible for determining appropriate illumination levels? A11. It is expected that the cameras will work with the current lighting. However, the contractor should determine if lighting will work with the specific cameras being used.

Q12. You have an existing PTC software package for toll collection and accounting, in order to successfully bid; we will need to know:

a. What software and API we can get b. What terminals are you using and the manufacturer c. How your system is architected, it appears you have a NOC so

we will need to understand what information is on the main server and how we can extract the collected data

A12.a. The PTC uses a third party custom developed software

application.

A12.b. Standard Windows terminal

A12.c. NOC has not been defined. Please refer to Addendum No. 1 - DVAS System Flow Requirements

Q13. Regarding Section IV-2: Please clarify the definition of “Lane Equipment” for which the contractor is required to interface. It is not clear of the specific make, model or type of equipment. A13. Lane Equipment: Lane controller is QNX and plaza computer is QNX. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will work with existing Pennsylvania Turnpike Commission representatives and contractor(s). Q14. Generally speaking, the contractor seeks to clarify the specific nature of the interfaces that are available for the capture of data from the various systems for which audit data is desired. Also, the contractor seeks to understand the specific data being requested for that audit system. The following questions pertain to that request.

Are the software products used by the PTC as mentioned in Section IV-3 purchased, off the shelf package or custom packages that were written specifically for PTC? (The packages mentioned are 1. PTC Desktop, 2. PTC Network Software, 3. PTC fare collection system of transaction capturing and reporting, 4. PTC plaza/lane configuration, 5. PTC audit system and exception reports). A14. PTC desktop / network software = commercial off the shelf. PTC Fare Collection System of transaction capturing and reporting / PTC lane plaza configuration / PTC audit software: exception codes = PTC used a third party custom developed software application. Q15. If they are off the shelf packages, please provide specific make, model and version of software for which this new system must interface. A15. Desktop – Mircosoft Windows XP Service Pack 2 Network Software – Microsoft Windows 2003 – (Pure CISCO

Network Operating System.)

Q16. Also, please provide the type of interface that may or exist or that may be required. Example – do these systems provide an API, a real-time TCP/IP feed or other interface from which the actual data will be available to the new system. A16. Please refer to Addendum No. 1 - DVAS System Flow

Requirements.

Q17. Does the PTC desire real time monitoring thereby requiring transaction data to be received from the toll collection system at the time of the actual transaction so it can be displayed in real time with the video. Or, is it desired that the data be collected for “audit” purposes only and be available for playback? A17. The PTC desires that the data be collected for “audit” purposes and be available for playback.

Q18. Please provide specific details on the actual record level transactional data required for storage and how the PTC proposes or anticipates the contractor to receive this transactional data. (example: will require to show “amount deposited into hopper,” “actual time,” “booth/lane number,” “attendant #,” “attendant name,” “license plate #,” etc.)

A18. Minimum transactional data required for storage: Date/Time/ Plaza/Lane/ Transaction number. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will mutually develop details with existing Pennsylvania Turnpike Commission representatives and contractor(s). Q19. Does the PTC expect the system to capture and retain a searchable text version actual License Plate numbers for each vehicle within its data warehouse or database? (i.e. is a License Plate Recognition system required as a fully integrated, real-time component of this system?) A19. License plate recognition is not a requirement. Q20. From which of the 5 noted systems will this new audit system be receiving actual “transactional” data? A20. Please refer to Addendum No. 1 – Overview of Toll Equipment

Interfaces.

Q21. For each system please specify the nature of the transactional data to be received. It seems clear that there is “fare collection” information which would imply a Point of Sale type device at every toll booth, but it is not clear as to the method by which this information would be provided from the transactional system. A21. Please refer to Addendum No. 1 – DVAS System Flow Requirements and Overview of Toll Equipment Interfaces. Q22. Does there exist a TCP/IP based Ethernet Network on which the new system would be connected and on which video could be transported for review and audit? Q22. Yes. Q23. If there are off the shelf packages, does this network connect all necessary components to which the new audit system must interface? Q23. Plaza PC = Yes. Lane Controller = No. Q24. Is there an environmentally controlled area at each toll plaza for electronic equipment to be placed (computers for this system). Q24. Yes.

Q25. Is there internet connectivity at each toll plaza for external maintenance of the systems? A25. Yes. However, there is restricted access thru PTC backbone. Q26. Does the PTC require this “audit” system to be viewable from outside locations via the internet or a private network? If yes, does that network exist and what bandwidth does it provide? A26. Yes. Bandwidth 512K to 1920L.

Q27. Does this system need to provide “enterprise” data collection for all 36 toll plazas? In other words, does the database need to have a “consolidation” view of statistical information for all toll plazas and the ability to audit or search from locations not local to that plaza? A27. No.

Q28. If yes to 27, where would such information need to be viewed? A28. N/A Q29. If yes to 27, does a network exist between each of the 36 toll plazas for collecting the data from the toll systems remotely? A29. N/A.

Q30. Does the system need to be able to “store and retain” case information including:

a. Actual videos and all synchronized transactional data b. Case number and other specific information regarding attendant,

lane, etc. A30.a. Yes.

A30.b. Case number = N/A.

Q31. For what period of time should the data be retained for each transaction? A31. Minimum of 60 days stored on-line; 6 months archived. If need arises to retain a specific transaction/video ability to identify transaction/video and store longer (i.e. 1 year minimum). Also, must be able to transfer to a permanent media.

Q32. Can the PTC provide logical and physical diagrams of how the toll booth systems are interconnected and how network communications are expected to occur between those systems and the new audit system? A32. Please refer to Addendum No. 1 - DVAS System Flow Requirements and Overview of Toll Equipment Interfaces. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will mutually develop details with existing Pennsylvania Turnpike Commission representatives and contractor(s). Q33. Since interface is required with several systems, please provide make, model and vendor (or service provider) contact for the following:

a. PTC networking software b. Fare collection system of transaction capturing and reporting

i. Provide specific data on the collection workstation in the tollbooth; workstation type (PC, DTR…) operating system (Linux, DOS, WindowsXX….) communication method with the greater system (Ethernet, serial, custom), Monitor type (CRT, LCD)

ii. Can additional software/service be installed on these workstations to create the interface with the video system?

c. Audit software and exception reports d. Any existing CCTV system that is to remain or interfaced to

A33.a. CISCO A33.b.i. Please refer to Addendum No. 1 – Overview of Toll Equipment Interfaces. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will mutually develop details with existing Pennsylvania Turnpike Commission representatives and contractor(s). A33.b.2. Please refer Addendum No. 1 – Overview of Toll Equipment Interfaces. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will mutually develop details with existing Pennsylvania Turnpike Commission representatives and contractor(s). A33.c. PTC uses a third party custom developed software application. A33.d. No.

Q34. As data needs to be transferred between the interchanges and the PTC Central Office in Harrisburg, please clarify the available network bandwidth between the different interchanges and the center. A34. The minimum bandwidth at a manned interchange would be 512K. Q35. Please provide a one-line sketch of current plaza/lane system configuration. A35. Please refer to Addendum No. 1 – Overview of Toll Equipment Interfaces. Q36. Transaction information varies from one authority to the other. Please provide sample of the transaction data PTC expects to appear alongside the video. A36. Minimum transaction data required: Date/Time/Plaza/Lane/Transaction number. Please refer to Addendum No. 1 - DVAS System Flow Requirements. The Commission cannot provide detailed requirements at this time. It is anticipated that the successful Proposer will mutually develop details with existing Pennsylvania Turnpike Commission representatives and contractor(s). Q37. What are the durations PTC expects to archive the video (specification P-11 calls for backup archiving of specific exit plaza locations as well as long term storage of identified incidents). Current video system offer unlimited storage duration, however actual storage size/duration will affect the overall cost. A37. Minimum of 60 days stored on-line; 6 months archived. If need arises to retain a specific transaction/video ability to identify transaction/video and store longer (i.e. 1 year minimum). Also, must be able to transfer to a permanent media.

Q38. Is license plate number recognition a requirement for any of the cameras? (The spec calls for “capture the vehicle but the customer should not be seen clearly”). A38. No. Q39. How many workstations required in the PTC Central Office? Do they exist, or should we include them as part of our offering? A39. Hardware exists via PTC supplied workstations.

Q40. What is the expected overall duration of the project? A40. According to the RFP, the initial period (pilot) is expected to last 3-6 months with full implementation to begin after PTC determination of successful acceptance test results. Q41. What are the restrictions (if any) on labor dates/hours? A41. Contractor should assume that work will be performed during non-peak hours and non-holiday periods. Details to be determined with successful proposer. Q43. Our system includes many options, added value components. To provide best system composition to PTC’s expectation, can the allocated project budget be revealed? A43. The Commission reserves the right to select a proposal based upon responses received to the RFP and will not necessarily choose the proposal offering the lowest financial cost to the Commission. The Commission will select the firm with the proposal that best meets the needs and desires of the Commission, in the sole discretion of the Commission. Q44. Page 3 of 12, paragraph I-1. Purpose. This paragraph states that the DVAS system “would videotape transactions as they occur in the toll lanes.” Is the use of video tape necessary or is it permissible to store images on a hard drive instead of on video tape? A44. The contractor should propose according to their suggested solution. Q45. Page 8 or 12, paragraph II-8. (A., 1.) Cost Submittal, Direct Labor Costs. Will the installation work be paid at Prevailing Wages (PW) and, if so, when will the PTC provide the PW determinations from the Labor and Industry Dept? A45. It is the contractor’s responsibility to determine the wages to be paid. Q46. Page 10 of 12, paragraph IV-3. Requirements. The first sentence of the second paragraph requires the contractor, “to provide system with fixed cameras located on the exit/entry side of the toll plaza that is able to capture a continuing stream of traffic 24x7 so as to cross over several lanes as well as the area where the vehicle arrives and departs the toll plaza.”

a. Does this mean that the system must view pre and post class areas or entering and exiting traffic at the toll plazas? This is a total of four different areas at each plaza.

b. Will this system be used for general video surveillance of the toll plaza?

c. Where is camera coverage required? For instance is it required in post-class exit? Pre-class exit?

d. If a truck with a box trailer temporarily obstructs the view of an adjacent toll lane, will this be acceptable or will it be considered an unacceptable system design?

A46.a. The camera must capture at a minimum Pre-Class, but Post-Class exit as well as a visual of entry. A46.b. The system is a video audit system. A46.c. The camera must capture at a minimum Pre-Class, but Post-Class exit as well as a visual of entry. A46.d. Cameras should be able to capture images of all exit lane transactions. The contractor’s solution should ensure all transactions can be viewed. Q47. of 12, paragraph IV-3. Requirements. The second sentence of the second paragraph requires the camera to, “provide an overall view of the traffic flow as well as allowing for the identification of a vehicle type.” What constitutes an overall view of traffic flow to the Commission? A47. The Commission would define “traffic flow” as: viewing vehicles that enter the turnpike system and immediately U-turn into an exit lane. The camera should capture the vehicle, but the customer should not be seen clearly. Q48. Page 10 of 12, paragraph IV-3. Requirements. The last sentence of the second sub-paragraph states that the DVAS system, “camera should capture the vehicle, but the customer should not be seen clearly.” We create a 640x480 image, in which faces are not normally clear enough to identify a person. Is this adequate? A48. Yes. Q49. Page 10 of 12, paragraph IV-3. Requirements. The third sub-paragraph, fifth bulleted point, requires that the system be designed to interface with the current audit software and exception reports. The current

selection criteria for these reports are plaza, lane, date and time. What selection criteria is required as part of the scope of this RFP? A49. The minimum transaction data required: Date / Time / Plaza / Lane / Transaction number. Q50. of 12, paragraph IV-3. Requirements. The fourth sub-paragraph requires the capability “of providing long term storage and review of identified incidents.” How much storage capability is required and where should the storage capability be located? Does the Commission desire 30, 60, 90 days or a different amount? A50. Minimum of 60 days stored on-line; 6 months archived. If the need arises to retain a specific transaction/video ability to identify transaction/video and store longer (i.e. 1 year minimum). Also, must be able to transfer to a permanent media. Q51. Page 11 of 12, paragraph IV-4. Tasks. Are there restrictions as to the locations where the cameras can be mounted? A51. The PTC will work with the selected vendor concerning the restrictions for cameras. Q52. Page 11 of 12, paragraph IV-4. Tasks. Will the Commission provide sufficient AC power (Clean and Dirty) at each interchange? A52. Yes. Q53. Page 11 of 12, paragraph IV-4. Tasks. How will the lanes be marked or designated if there are no lane number signs on the canopy? A53. All lanes have lane numbers on the canopy.

All other terms, conditions and requirements of the original RFP dated December 1, 2006 remain unchanged unless modified by this Addendum. By signing below, I acknowledge that I have read all addendums that pertain to this RFP. ____________________________________ _______________ Contractor’s Signature Date

Interchange Lane Configuration Chart Updated: 10-25-06Page: 1 of 8

413TOTAL ALL LANES

133TOTAL COMBINED ENTRY LANES 280

TOTAL MAINLINE EXIT LANES

Automatic Coin Machine Entry

198

TOTAL EXPANSION ENTRY 10 TOTAL EXPANSION EXIT 82

TOTAL MAINLINE ENTRY LANES 123

167

Ticket Only Entry Lane - Not EZPass Capable 1 1% Cash Only Exit Lane -

Not EZPass Capable 31

Total EZPass Capable Exit Lanes

Total EZPass Capable Entry Lanes

Dedicated Exit Lane30%

2%

99%

9

EZPass Capable Exit Lane Operated in Cash

Only Mode86

Dedicated Entry Lane 37

EZPass Capable Entry Lane Operated in Ticket

Only Mode2

Mixed-mode Entry Lane 83 Mixed-mode Exit

Lane67%

122

72

% of Exit Lanes

3%

10 20

6

Automatic Coin Machine Exit

Manual Toll Collector Exit

ENTRY LANE SUMMARY EXIT LANE SUMMARY

8% 10%

16%

5%

36%

43%

84%

% of Entry Lanes

TOTAL COMBINED EXIT LANES

AMM / EZPass Capable 22 11%

AMM 34 17%

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

N/A N/A

2 2 2 2 2 2 2 2 2 2 2 2 2

N/AExpress Express

N/A

1 1 1 1 1 1 2 2 2 2 2 2 2 2 2

1 1 1 2 2 2

1 1 1 1 2 2 2 2 2

1 2 3 4 5 6

1 2 3 4 5 6

2 1 4 3

CAR TRK CAR TRK

2 1 4 3

CAR TRK CAR TRK


AMM AMM / EZPass Capable Cash Only Exit Lane - Not EZPass Capable


Manual Toll Collector ExitDedicated Exit Lane

Mixed-mode Exit LaneEZPass Capable Entry/Exit Lane Operated in Ticket/Cash Only Mode

ENTRY EXIT

Ticket Only Entry Lane - Not EZPass Capable

N/B Entry

Mixed-mode Entry Lane

Dedicated Entry Lane

5/48 Allegheny Valley

Moravia Ramp S/B Entry N/B Exit

135/02 Gateway

42/30 Warrendale

4/39 Butler Valley

ENTRY

Eastbound EXIT

ENTRY EXIT

Color Key

North Toll 60

South Toll 60

N/B ExitS/B Exit

S/B Exit N/B Exit

Mount Jackson Ramp

S/B Exit

W/B Exit

EXIT

District 6

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17








Dedicated Entry LaneColor Key

2 1 4 3

CAR TRK CAR TRK

Temp

1 1 1 1 2 2 2 2 2 2 2 2

11

1 2 2

1 1 1 1 2 2 2 2 2 2 2

1 2 3 4 5 6 7 8

2 1 4 3

CAR TRK CAR TRK

2 1 4 3

CAR TRK CAR TRK

2 1 4 3

CAR TRK CAR TRK

2 1 4 3

CAR TRK CAR TRK

N/B Entry

6/57 Pittsburgh

7/67 Irwin

8/75 New Stanton

Beaver Falls Ramp

ENTRY

Northbound Exit

S/B Exit

EXITENTRY

ENTRY

AKH Mainline Southbound Exit

Route 66 Ramp S/B Exit N/B Entry

Route 130 RampS/B Exit N/B Entry

EXIT

EXIT

District 6 (Continued)

District 1

Route 30 RampS/B Exit N/B Entry

Route 136 Ramp S/B Entry N/B Exit

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17









2 1 3 4

CAR TRK CAR TRK

1 2 3 4 5 6

1 2 3 4 5 6

2 1 3 4

CAR TRK CAR TRK

2 1 3 4

CAR TRK CAR TRK

2 1 3 4

CAR TRK CAR TRK

1 2 3 4 5 6

N/A N/A

Northbound

M4S/B N/B

M5 S/B N/B

M52 Southbound

California S/B N/B

S/B N/B

M48S/B N/B

M39S/B N/B

M44

District 1 (Continued)

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17









1 1 2 2

1 1 2 2 2EXIT

1 1 1 1 2 2 2 2 2 2 2

1 1 2 2

1 1 2 2

1 1 2 2

10/110 Somerset

11/146 Bedford

12/161 Breezewood

13/180 Ft. Littleton

ENTRY

14/189 Willow Hill

15/201 Blue Mt.ENTRY EXIT

ENTRY EXIT

District 2

9/91 Donegal

ENTRY

ENTRY

EXIT

EXIT

EXIT

EXIT

ENTRY

ENTRY

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17









1 1 2 2 2

N/A

Cars only

1 1 2 2 2

1 1 1 2 2 2 2 2

1 1 1 2 2 2 2

1 1 1 2 2 2 2

ENTRY

EXIT

18/242 Hbg. West

16/226 Carlisle

17/236 Gettysburg

19/247 Hbg. East

20/266 Lebanon/ Lancaster

21/286 Reading

22/298 Morgantown

23/312 Downingtown

ENTRY EXIT

ENTRY

ENTRY EXIT

ENTRY EXIT

EXIT

EXITENTRY

District 3

ENTRY EXIT

ENTRY EXIT

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17









1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2

N/A

1 1 1 2 2 2 2 2 2

Express Express Express Express

1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2 2EXIT

1 1 2 2EXIT

1 1 1 1 2 2 2 2 2 2

1 1 1 1 1 1 2 2 2 2 2 2 2 2 2 2

1 1 2 2 2

1 1 1 1 2 2 2 2

30/359 Del. River Bridge

ENTRY EXIT

EXITENTRY

ENTRY

District 4

27/343 Willow Grove

41/340 Virginia Drive

39//20 Mid-County

24/326 Valley Forge

25/333 Norristown

26/339 Ft. Washington

29/358 Del.Valley

28/351 Philadelphia

ENTRY EXIT

ENTRY EXIT

ENTRY

EXIT

ENTRY

ENTRY EXIT

ENTRY EXIT

12/26/2006


Interchange 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17









1 1 1 1 2 2 2 2 2 2

1 1 1 2 2 2 2 2

1 1 1 1 2 2 2 2 2 2 2 2 2

1 1 2 2 2

1 1 1 2 2 2 2 2

1 1 2 2

1 1 1 2 2 2 2

No Tickets/Barrier System - Automatic Multi-Mode Machines

2 2 2 2 2 2

No Tickets/Barrier System - Automatic Multi-Mode Machines

2 2 2 2

EXIT

District 5

37/115 Wyoming Valley

36/105 Wilkes-barre

35/95 Pocono

34/74 Mahoning Valley

33/56 Lehigh Valley

32/44 Quakertown

31/31 Landsdale

ENTRY EXIT

EXIT

ENTRY EXIT

ENTRY EXIT

ENTRY

ENTRY

ENTRY

ENTRY EXIT

EXIT

38/122 Keyser Avenue

Southbound EXIT Northbound EXIT

39/131 Clarks Summit

S/B EXIT N/B EXIT

12/26/2006

rfp #06-118-3388 digital video audit system for the pennsylvania turnpike commission ·...

Documents