date: october 6, 2020question 10: metra’s initial goal is to offload at least 1 peta bytes of...

Date: October 6, 2020

Subject: Request for Proposal No. 64979 Video Surveillance Storage Equipment Addendum No. 1

Dear Sir/Madam:

Addendum No. 1 is being issued for changes to correct, amend, add and / or delete certain words, phrases, sentences or paragraphs in Metra RFP No. 64979.

1. The following separate documents are attached and marked Addendum No. 1 dated October 6, 2020: Proposer questions and Metra’s responses Exhibit 1-A – Scope of Work

The due date and time of proposal submittal has remained the same. All Addenda must be acknowledged in Exhibit 1, page 24 of 24.

Sincerely,

Alexis Karas Department Head Professional Services Procurement

AK/jz

Addendum No. 1, October 6, 2020

Page 1 of 20

Below are questions received and Metra’s responses: Question 1: In the current state overview of this Professional Services RFP, it describes current

Pivot3 appliances. Does this mean Metra purchased Pivot3 appliances in response to the video storage RFI from March 2020?

Metra Response: No. Metra currently has Pivot 3 equipment installed. This RFP is to replace existing Pivot 3 equipment. The RFP is not brand specific.

Question 2: Our submission involved a Dell Isilon storage solution for VSS, the same solution

deployed by the City of Chicago Emergency Response System (911). Is Metra only looking for professional services to install new Pivot3 storage appliances or is the video storage RFI from earlier this year still undecided upon?

Metra Response: This RFP is for turn-key solution for Professional Services, Equipment, Installation and Maintenance of high capacity video storage. All solutions that meet the minimum requirements of the RFP will be considered. Information gathered from the RFI was used to draft this RFP. RFIs do not result in contract awards or follow up responses from Metra.

Question 3: Does the Video Surveillance Storage System RFP for Metra include cameras and

DVRs for the actual buses?

Metra Response: No, this RFP is for storage only. For clarification, Metra runs trains not buses.

Question 4: What type/model cameras are currently being used, and can you provide the

FPS/resolution that is running?

Metra Response: The existing camera system is Genetec the resolution is 1920 x 1080. FPS varies based on our current limited storage availability. Moving forward Metra is specifying 30 FPS minimum.

Question 5: Could you advise me if you are using Genetec VMS or is it another vendor?

Metra Response: Yes, Metra is currently running Genetec VMS.

Question 6: How long does Metra plan on retaining the footage?

Metra Response: Our current policy is to retain footage for 30 days.


Page 2 of 20

Question 7: Are these continuously recording and if so, what is the frame rate (often very low like 1 of 5 FPS) and what activity (like jumping up to like 15 or 30 FPS)?

Metra Response: Yes, video is continuously recording. See answer to Question 4.

Question 8: Do you have a current VMS you’d like to stick with or are you open to suggestions?

Metra Response: Metra will not be replacing the current VMS as part of this RFP. Metra may be releasing an RFP in the future to replace the VMS.

Question 9: Reference section XIV. SCOPE OF WORK

Metra intends to replace the existing 4.3 Peta Bytes VSS system at its KYD facility with high capacity, 2U VSS equipment which will be housed in existing 42U electronic rack cabinets, with the following dimensions: 73.5”h x 19” w x 34” d. Please explain what this means?

Metra Response: Please see the revised Exhibit 1-A – Scope of Work - Metra will be correcting the existing storage total from 4.3 Petabytes to 8.6 Petabytes of raw storage. In all instance where existing storage capacity is mentioned the total capacity will be changed to 8.6 Petabytes. Metra will be migrating the 8.6 Petabytes of existing storage located in 18 Forty-two (42U) storage racks with the dimensions specified above. For the intent of this RFP the maximum capacity for the 2U appliance will be a maximum of 20 appliances which will take up 20 Rack Units spaces.

Question 10: Metra’s initial goal is to offload at least 1 Peta Bytes of (Raw) data storage with

high capacity compute/storage appliances. The initial offload is required to allow space for expansion to 13 Peta Bytes (Raw) data storage. Based on the size of the 2U appliance the chart below shows the space savings from 24 to 336 Terra Bytes units. Off load to where and from where?

Metra Response: Metra’s plan is to migrate/offload the existing system to the new higher capacity solution.

Question 11: Please explain what the expansion to 13pb is?

Metra Response: Metra currently has maximum capacity of 9.3 PB. The expansion to 13 PB is to migrate from lower capacity appliances to higher capacity appliances to allow for the future expansion space. As it stands, Metra has 18 racks of 20 appliances each having 24TB raw storage. Each rack has a total capacity of 480 TB. Our calculated total capacity is 8.6 PB with an additional 768 TB of data storage which was purchase under an emergency procurement due to limited space. 13 Petabytes storage is the maximum storage if 4 Racks of ten (10) 336TB appliances were assumed. This RFP is for 13 PB of raw storage.

Question 12: What is the total storage size of the system or are we to calculate it out?


Page 3 of 20

Metra Response: See answer to Question 11 above.

Question 13: Will there be redundant recording?

Metra Response: No, but the storage system should have the capability of redundancy and/or failover.

Question 14: Type of Camera (Analog or Digital): IP ? a. Resolution to be used/Or Camera Model Number)? b. Estimated daily recording time. (24 hours = 100%) or Motion Event Driven? c. How many frames per seconds? d. Camera Bitrate (Average)? e. Video Codec to be used in this solution H.264/H.265? f. Retention period in weeks, months or years?

Metra Response: This question, although accurate for the method to calculate storage required, is not necessary since Metra is in the market to upgrade capacity to 13 Petabytes. The reason this information was not provided before was because Metra has a hard limit requirement for storage of 13PB.

Question 15: For the multi-site requirements - Are you preferring using a centralized or decentralized approach?

Metra Response: There is no multi-site requirement. This RFP for storage will be housed in one location.

Question 16: The RFP mentions offloading…Do you require failover or any type of redundancy?

Metra Response: Yes, failover is required. For clarification the word “offloading” in this RFP refers to a one-time task to migrate or move our existing video from existing storage to the storage requirements of this RFP.

Question 17: How many workstations to view the live or recorded video streams are in the environment? a. Should we plan any room to grow?

Metra Response: Not Applicable. The RFP is for storage only.

Question 18: Is the 2RU server requirement firm?

Metra Response: This requirement was based on our existing rack system. The firm limit is for 13 Petabytes of raw storage. As long as the proposed appliances are able to fit into a 40U in a 42RU electronics rack, they will be considered. This RFP is


Page 4 of 20

specifically addressing migration from low capacity appliances to high capacity appliances to free space for the future expansion.

Question 19: Can racks be replaced if they are not sufficient for server dimensions?

Metra Response: No, Exhibit 1-A – Scope of Work describes the dimensions of the current racks.

Question 20: Exhibit 1-A page 10 calls for “spare equipment as specified”. After review of the RFP we did not see any spare equipment requested. What is the spare equipment that is to be provided?

Metra Response: Contractor shall supply 10% spare equipment for all equipment supplied, i.e., power supplies, hard drives, including whole appliances, etc.

Question 21: In addition to the 15% DBE goal is there any goals for WBE or MBE?

Metra Response: Please refer to Exhibit 1-L, IV. Counting DBE Participation.

Question 22: In order to accommodate internal COVID-19 protocols, will Metra accept digitally signed documents as part of bidder’s proposals?

Metra Response: Yes.

Question 23: Are you open to a solution that separates the application servers from the data storage offering growth options and efficiencies for both compute and storage?

Metra Response: If proposed and the proposal is accepted, Yes.

Question 24: It is understood Metra is a Genetec client today, are you open to an alternative Video Management System (VMS) software solution?

Metra Response: Currently, we are procuring storage for the VMS only. In the future, Metra will consider alternative VMS software solutions.

Question 25: How many hours per day does Metra record video?

Metra Response: 24/7

Question 26: Does the existing system run on a virtual environment today, VMWare or HyperV?

Metra Response: Yes, VMS runs on VMWare.


Page 5 of 20

Question 27: What are the make and model of the cameras in use today?

Metra Response: We are not replacing cameras. We are replacing computer/storage equipment.

Question 28: What is the space utilization or requirement per camera?


Question 29: Are the cameras always recording, or record on motion, or a combination of both? If a combination, how many are always recording vs. record on motion?

Metra Response: Cameras record 100%.

Question 30: What is the frames per second metric for these cameras?

Metra Response: 30 FPS

Question 31: What is the resolution of the cameras, HD resolution? 4K resolution?

Metra Response: 1920 x 1080 Full HD

Question 32: What is the codec, mjpeg?, H.264? H.265?

Metra Response: H.264 - Metra is also considering H.265 in future expansions.

Question 33: Is everything recorded from a central data center or is there recording in the field with nightly uploading?

Metra Response: All video is recorded to a central data center.

Question 34: Do trains have an NVR and if so, does that data stay local on the train until uploaded to the central data center?

Metra Response: This storage is only for fixed mount camera in stations/yards/etc.

Question 35: Is there a camera cellular uplink in use today?

Metra Response: No. See answer to Question 34 above.

Question 36: What is Metra’s VMS retention policy, 90 days? 120 days? Longer?

Metra Response: Currently Metra’s retention policy is 30 days.


Page 6 of 20

Question 37: Is there a long-term archival retention target as well?

Metra Response: No.

Question 38: In reference to data center space, does Metra’s existing data center have enough capacity to house two systems during the implementation and cut over, allowing more for full data migration from one system to another? What are the performance requirements for the solution storage in the form of a Mbps metric?

Metra Response: No. This is the reason we will need minimum of 8.6 PB installed first.

Question 39: Is there a need for DR replication of the VMS infrastructure to another data center?

Metra Response: No. But there should be built in redundancy in the data center in case of failure.

Question 40: Is there a need for High-Availability configuration of the VMS infrastructure? Within the same data center or across multiple data centers?

Metra Response: Yes. Within the same data center.

Question 41: Regarding the future upgrade to a more advanced analytics video system, what is the current manufacture and version # of the VMS software that is used today?

Metra Response: Genetec Security Center 5.8.

Question 42: Has a timeframe been established for future upgrades of the VMS system?

Metra Response: No.

Question 43: Are there other 3rd party software VMS providers that are used by Metra for the management of the system?

Metra Response: No.

Question 44: Does the current VMS software include Video analytics/tools such as? · Left object detection · Object tracking · Fare evasion detection · Thrown object detection · Wrong-way detection · Crowd management · People counting · Face recognition · Voice recognition


Page 7 of 20

· GPS Tracking · Traffic Management · License Plate Recognition

Metra Response: No.

Question 45: Does Metra currently have their fleet cameras pulled into their central VMS?

Metra Response: No.

Question 46: What Camera system is in use on the different rolling stock assets within Metra • Per video analytics, would Metra be interested in evaluating any of the

following: Deep Learning behavioral tracking People counting / line Queue Face mask detection Contact tracing

Metra Response: This system does not apply to rolling stock assets.

Question 47: Regarding an interest in more advanced analytics, has Metra evaluated driver safety behavioral analytics. (Analytics based on accelerometer, GPS, and other IoT sensors, NON-VIDEO )

Metra Response: This question does not apply to this RFP. This RFP is for storage only.

Question 48: Does Metra have a standardized or preferred CCTV manufacturer?


Question 49: Does Metra have a cloud strategy for Video in the coming years?

Metra Response: Metra does not have a cloud strategy for video. Metra is not interested in cloud-based storage.

Question 50: Would it be helpful to get insights on storage and files created on a per-camera basis?

Metra Response: This RFP is for a storage solution only.

Question 51: How many people will be in charge of managing the VSS storage part of the solution?

Metra Response: Up to 10 individuals should have simultaneous access.


Page 8 of 20

Question 52: How does Metra want to migrate file data from current solution to proposed and selected solution?

Metra Response: Metra would like to migrate/offload data with no interruption to existing camera footage collection. As part of this RFP Metra is interested in a proposed plan for seamless conversion from one appliance to the next. This RFP includes a seamless migration plan.

Question 53: What interoperability standard (SMB or NFS) might be needed for data migration from old storage to new?

Metra Response: The interoperability standard is ISCSI.

Question 54: When would you like this implementation to be started and completed?

Metra Response: As outlined in Exhibit 1-A – Scope of Work, the work will begin within 30 days after Notice to Proceed and should be completed within a 12-month maximum.

Question 55: What is the VSS software in scope for this project?

Metra Response: Metra software is Windows Server 2019 x 64 x 12 core with embedded VMware + Product Key, with VMware foundation licenses.

Question 56: Can the VSS application(s) be installed on a VMware hypervisor?


Question 57: What operating system will be used for the VSS applications?

Metra Response: Windows Server 2019.

Question 58: Can new storage systems be 4U (rack unit)?

Metra Response: Please see answer to Question 18 above.

Question 59: For components of the proposed solutions, are suppliers able to provide options with corresponding pros/cons and associated costs for each option?


Question 60: What is the Video Management System (VMS) vendor and product? a. Does the VMS use REST API, SMB/NFS protocol or other to connect to

the storage?


Page 9 of 20

b. What is Metra’s preference?

Metra Response: The VMS is VMware. The VMS protocol is iSCSI. It runs on the storage host VMware. VMware is Metra’s preference, but other VMS products will be considered if proposed.

Question 61: RAID technology could be considered antiquated. Instead, we can provide a solution that can use software to more efficiently protect data and reduce time to recovery by days - Is it acceptable to protect data with software while still maintaining a better drive resiliency than RAID 6 of at least N+2?

Metra Response: Metra is open to all proposed solutions, except a cloud-based solution.

Question 62: Regarding up to 18 x LFF drives per appliance, there are appliances available with up to 20 LFF near-line SAS hard disk drives, hot-swappable - Is it acceptable to use higher density appliances with more than 18 LFF drives as long as reliability and performance is not sacrificed?


Question 63: Is hyperconverged the architecture you want to go with? Or is there a preference for a more "inexpensive and deep" type of storage?

Metra Response: See answer to Question 61.

Question 64: Will there be a willingness to leverage hosted services or public cloud?

Metra Response: No.

Question 65: Exhibit 1-A, XIV. SCOPE OF WORK, B. SYSTEM REQUIREMENTS bullet 3 notes VSS capacity up to 336 TB raw storage. This seems to contradict section E. FUTURE UPGRADE OF VSS SYSTEM bullet 7 with capacity of 336 TB effective - Is it referring to raw capacity or effective capacity?

Metra Response: Raw capacity.

Question 66: Below is an assumed statement. It is correct? 1 PB raw storage = 840TB effective storage (XIV. A. -- 18 Arrays of 10 nodes = 180 nodes / 4.3 PB = ~24 TB raw per node = 18 drives per node x 2 TB drives with RAID 6 ~20TB effective storage)

Metra Response: Yes, that is a correct assumption. But to clarify, for the purposes of this RFP there are 36 Arrays of 10 nodes = 360 nodes / 8.6 PB = 24 TB. There are 18 racks instead of 18 arrays. There are 2 arrays in each rack. Metra intends to fill 4 emptied racks with high capacity nodes to equal approximately 13 Petabytes.


Page 10 of 20

Question 67: What Video Surveillance Software are you currently using?

Metra Response: Genetec.

Question 68: Contract Question: Will you allow redlines and negotiate the T's and C's before contract execution?


Question 69: Technical Proposal - Content (page 3, para 2) (PDF page 30) - Please confirm that “rollout order” pertains to the order of operations for cut-over.

Metra Response: Yes. In the context of the wording on page 3, para 2, page 30 “Technical Proposal” rollout order would have the same meaning as cut-over.

Question 70: Future Upgrade of VSS (page 9, para 4) (PDF page 36) - What are the onsite replacement part requirements? i.e. quantities, and response time.

Metra Response: The replacement parts are the 360/24TB appliances. The response time for the entire project is 1 year. A portion of the project will consist of completing an already started data rack which still requires 6 additional appliances to fill (1 Petabytes).

Question 71: What is the estimated number of computer servers required to handle the existing number of cameras and future cameras?

Metra Response: This RFP is for an estimated 13 Petabytes of computer/storage data.

Question 72: How many virtual machines (VMs) are currently deployed across video storage Pivot3 array?

Metra Response: Each appliance (360) has an embedded virtual machine licenses This does not include the 4 recently purchased appliances which also has embedded virtual machine licensed technology. The total would than become 364 VMware licenses.

Question 73: How does METRA plan on purchasing the computer/storage? Is it the plan to purchase 1PB for phase one and then the additional 12PB for phase two, or will all 13PB be purchased at initially?

Metra Response: This RFP is for the purchase of the entire 13 Petabytes of computer/storage. The 1 PB is for completion of an array that was initially started but not completed. The 1 PB is part of the 13 Petabytes total.


Page 11 of 20

Question 74: Section XIV Scope of work: 336TB appliances were mentioned. Higher density computer/storage appliances, 384TB are available. Using the 384TB appliances will also yield to less rack space. Would this design be acceptable?

Metra Response: Yes, as long as the appliances are within the dimensions of 42RU electronic rack and able to fit in the existing racks.

Question 75: Section XIV: Scope of Work, B: System Requirements: Throughput: VSS system must be capable of managing a combined 2100 Mbps of total throughput with handling for simultaneous recording, playback and live streaming. Can you confirm total system performance requirements is 2100Mb for the entire VSS environment to support all 1800 cameras? Will there be growth calculated into the camera counts? If so, how much?

Metra Response: No. Camera count growth will be addressed under a future RFP. The number 13 PB represents the calculated growth required today to migrate existing storage to new storage devices.

Question 76: Section XIV: Scope of Work, B: System Requirements: Expansion: System must be configured to be capable of future expansion and scaling. Can you confirm total capacity scaling requirements? Up to how many PBs?

Metra Response: Metra does not have a hard limit for expansion. For this RFP the goal is 13 Petabytes. Future expansion will be greater and will come under a future RFP.

Question 78: Section XV: Contractor Requirements: Contractor shall supply all spare equipment as specified. Define what Spare equipment is required. Spare drives, spare memory, etc.


Question 79: Section XIV: Scope of Work How does Metra plan on purchasing the computer/storage? Is it the plan to purchase 1PB for phase one and then the additional 12PB for phase two, or will all 13PB be purchased at initially?

Metra Response: See answer to Question 73. The equipment will be purchased over a 12-month period. The 1 PB will be installed in a rack that was initially started in 2019 for an emergency capacity upgrade due to limited space. The completion of the first rack will allow for


Page 12 of 20

the migration of 1 PB from 2 racks which currently holds 40 appliances with a capacity of 24TB per appliance for a 2-rack total of 960 TB or approximately 1 Petabyte. After the 1st rack is completed, we will then start migration to higher capacity units to be stored on 2 racks that were freed. Depending on the size of the higher capacity appliances the 2 freed racks are being marked to hold only 10 appliances of the new appliances. A chart was included as a part of this RFP to explain this. The higher the capacity the more storage can be moved from other racks. It is the intent of this RFP to move all 18 racks onto higher capacity storage appliances, utilizing a minimum number of racks. The proposer is expected to submit a migration plan/offload strategy to accomplish this within the allowed timeframe. At least 4.3 PB is expected to be freed within 3-6 months and the remaining 4.3 PB over the balance of the contract. Up to 13 Petabytes of storage will be purchased. The increased capacity of each appliance will allow for the reduction in storage space. This RFP will consider compatible equipment from 192 TB-384 TB per appliance. This process will then allow for future growth. Depending on the size of the new appliances the rack space can be reduced from 18 racks to 4-6 racks.

Question 80: Section XIV Scope of Work: 336TB appliances were mentioned. Higher density computer/storage appliances, 384TB are available. Using the 384TB appliances will also yield to less rack space. Would this design be acceptable?

Metra Response: Yes. As long as the equipment adheres to the rack dimensions.

Question 81: Section XIV: Scope of Work, B: System Requirements: Throughput: VSS system must be capable of managing a combined 2100 Mbps of total throughput with handling for simultaneous recording, playback and live streaming. Can you confirm total system performance requirements is 2100Mb for the entire VSS environment to support all 1800 cameras? Will there be growth calculated into the camera counts? If so, how much?

Metra Response: The performance of the cameras is not an issue at this point because this is a storage only RFP. Metra is however, expecting camera growth to approximately 3,000 over the next year and a half.

Question 82: Section XIV: Scope of Work, B: System Requirements: Expansion: System must be configured to be capable of future expansion and scaling. Can you confirm total capacity scaling requirements? Up to how many PBs?


Page 13 of 20

Metra Response: At the time we cannot give a finite answer as to our future storage requirements. Metra is estimating an expansion up to 19,000 cameras over the next 10 years, but that is not part of this RFP.

Question 83: Section XV: Contractor Requirements: Contractor Shall supply all spare equipment as specified. Please define what Spare equipment is required. Spare drives, spare memory, etc.


Question 84: What is the front-end VMS currently being used with the PIVOT3 VSS? Does METRA prefer to use that VMS with the new VSS?

Metra Response: The VMS currently used is VMWare. All proposed solutions will be considered, with the exception of cloud-based solutions.

Question 85: The requirements state “Processing requirements Operating system must be compatible with the existing operating system.” What is the ‘…existing operating system?”

Metra Response: The existing operating system is Windows Server. The RFP expects the most recent version of Windows Server to be implemented.

Question 86: Section XIV SOW mentions “allow space for expansion to 13 PB (raw) storage” – when and what is that expansion expected? Is the expansion task expected to be completed by the Consultant or some unknown future date by METRA? How are you determining your current storage growth needs?

Metra Response: Our current requirement is based on actual usage. Metra procured an emergency expansion in 2019 due to the lack of storage space. The 13 PB raw storage is based on the actual 8.6 PB currently available in Metra’s storage facility with an additional 768 TB previously purchased due to storage requirements.

Question 87: The requirements specify “Video Storage: Up to 18 x large form factor near-line SAS hard disk drives, hot-swappable, RAID 6.” The provider nodes are configured with 9 or 24 HDDs, depending on the model. Any concern with a 24-drive node in our response?

Metra Response: No, as long as all 24 drives are hot-swappable. (Does not require the equipment to be powered down.)


Page 14 of 20

Question 88: The requirements spell out 10gbps networking interfaces, 2 per VSS. The OEM appliance nodes use SFP28 or QSFP28 adapters. Metra’s switch would need to support this faster speed. Please confirm that METRA’s equipment has the correct port types? Or should we include port-ready network switches and any transceivers?

Metra Response: No. Proposer would need to provide port-ready network switches and any transceivers.

Question 89: What model of camera are you using or is that in scope for this RFP as well? Can we get actual camera usage data? Camera resolution influences video streaming storage needs – what resolution should we use for any calculations?

Metra Response: The cameras are not in scope for this RFP. Metra realizes that there are formulas that influence video streaming. We have taken this in consideration in our request for 13 Petabytes for this RFP.

Question 90: If the DBE engaged to work the primary lead contractor fails to perform after acceptance and initiation of the contract, will METRA allow another DBE to replace it as providing a commercially useful function?

Metra Response: Please refer to Exhibit 1-L, VII. Contract Performance, (F. Substitution of DBE Firms).

Question 91: Does the DBE engaged to work the primary contractor need to be paid on the same schedule as the negotiated milestone payment schedule to the lead for DBE pay-out credit to qualify?

Metra Response: Please refer to Exhibit 1-L, VII. Contract Performance, (D. Prompt Payment). Payment milestones can be discussed with the Prime during award negotiations.

Question 92: What is the current centralized “health management system” being used with the PIVOT3 system (mentioned in XIV-C)?

Metra Response: VMware monitoring software and PRTG monitoring software.

Question 93: Clarify who will be responsible for the migration and retirement of the PIVOT3 storage? METRA or Consultant?

Metra Response: Metra forces are responsible for the migration from the existing to new equipment under the direction of the contractor and/or consultant. Metra forces will be responsible for the retirement of the PIVOT3 equipment.

Question 94: What is the ROI lifecycle time span expected of the new VSS in years?

Metra Response: The Return on Investment lifecycle for the new storage equipment is 7 years.


Page 15 of 20

Question 95: Does METRA expect to use support agreements with the same integrator beyond the first year? (See section XX).

Metra Response: Yes. Please refer to page 36 of the Bid Documentation Section X.V. Contractors Requirements. Paragraph 3.

Question 96: Does this solution need to comply with the non-rolling stock Buy America requirements of the FTA/STAA or similar rules (does Exhibit 1-D apply here)?

Metra Response: This is an FTA funded procurement. Proposers shall indicate their ability to comply with the requirements of Buy America or indicate if they do not comply but that a waiver exists for the type of equipment requested. Please note, that a waiver may exist for certain equipment solicited as part of this RFP, but not all. Buy America requirements would apply for any equipment which does not have an existing waiver. Additional Buy America information can be found at: https://www.transit.dot.gov/buyamerica

Question 97: Should the responding consultant/provider include backup and/or replication of the primary storage to another cluster or location or will METRA handle that exclusively?

Metra Response: No. The proposed storage system is expected to have redundancy and/or failover embedded in the system.

Question 98: The RFP refers to the respondent as “consultant” rather than solution provider or reseller. The role and responsibilities of consultant, in the trade, usually does not provide delivery of goods and service integration but design and oversight. Elsewhere in the scope of work, you refer to “contractor” to furnish goods and services. Are you really looking for a solution provider (“contractor”) in the context of this RFP?

Metra Response: For the purposes of the RFP the words “consultant” and “contractor” are interchangeable.

Question 99: Current Metra KYD Site has 18 arrays consisting of ten (10) Pivot3 appliances (180 total appliances) supporting mission-critical video surveillance. Total (Raw) Storage of 4.3 Peta Bytes. Each appliance currently has a maximum capacity of 24 TB (Raw Storage). It is anticipated that work will be performed at Metra’s Kensington Yard (KYD) located a 12301 S. Indiana, Chicago, IL 60628. – is Metra planning to expand to take feeds from other yards? How much rack space is available at each site?


Page 16 of 20

Metra Response: Please see answer to Question 9 amending the total number of appliances and capacity of the existing system. There are 36 arrays, 2 arrays per rack. Or 20 appliances per rack and 18 racks for a total of 360 appliances. Each appliance has 24 TB of storage. Each rack has 480 TB of storage x 18 Racks for a total capacity of 8.6 Petabytes. There is also a rack with 4-192 TB appliances that was recently purchase due to the storage limitations. For an overall total capacity of 9.3 Petabytes. For the purpose of this RFP the migration to higher capacity storage appliances is to free space for future growth. The 13 PB is an assumption that the appliances are 336 TB with 10 appliances in each rack for 3.360 Petabytes per rack for a total of 13.4 Petabytes. This may or may not be the quantity of racks used or the number of appliances in each rack. It is Metra’s assumption for migration. All work will be performed at Metra’s facilities located at the 12301 S. Indiana, Chicago, IL. All current and future feeds will terminate at this location.

Question 100: Page 34 states “Mounting: Standard server enclosure (rack) mounting, requiring no greater than a 2U configuration. “, we are asking for clarification.

Metra Response: Please refer to answer of Question 74.

Question 101: The requirements specify support for 2100Mbps search feature combined throughput. We almost never hear requirements stated in Mbps. Please clarify intended search size speed: MBps vs Mbps. FWIW, 2100 Mbps = 262.5 MBps.

Metra Response: The requirement for 2100Mbps is throughput. To get the MBps divide 2100 by 8.

Question 102: Is METRA using a recording server now or a direct to storage system in PIVOT3?

Metra Response: Genetec recording software resides directly on Pivot3.

Question 103: Exhibit 1-A states 1800 mission-critical cameras are now deployed. How many more cameras are you looking to deploy within the expansion scope of this project? Are you asking us to design or plan for a VSS that is future expandable to support these new cameras? Or should we include the actual hardware/software needed for future expansion in the total purchase price?

Metra Response: This project is for storage only.

Question 104: Number of Streams per Camera Frames Per Second? Hours of Recording? Hours of Motion Sensed Recording? Daylight/Nightlight Recording? Compression Used? Data Ingest Rate? How many locations will be recording video?

Metra Response: This project is for a fixed storage of 13 Petabytes. No new calculation is necessary.


Page 17 of 20

Question 105: What is the retention policy desired for the VSS data?

Metra Response: The retention policy is 30 days.

Question 106: How fast does the VSS data or footage need to be available for research, litigation, other purposes?

Metra Response: Immediately.

Question 107: Will any science or engineering be run against the VSS footage (pattern recognition, facial recognition, etc.)?

Metra Response: Not currently. Metra will be pursuing a separate RFP to add this feature in the future.

Question 108: Will you accept management of the data or data itself to be in the public cloud?

Metra Response: No. Metra is not interested in a cloud-based system.

Question 109: How many total hours per day do you expect to record, if not continuous 24 hours?

Metra Response: 24 hours/7 days per week, continuous recording.

Question 110: What codec support do you need?

Metra Response: H.264 up to H.265

Question 111: Are you open to a solution that separates the application servers from the data storage offering growth options and efficiencies for both compute and storage? Would it be helpful to get insights on storage and files created on a per camera basis? How many people will oversee managing the VSS storage part of the solution?

Metra Response: Yes. Metra is open to a solution that separates the application servers from the data storage. Up to 10 individuals may simultaneously access the VSS management system.

Question 112: Clarify who is responsible for the migration of the camera data in the PIVOT3 VSS to new VSS. If the consultant will be responsible for the migration, is any proprietary knowledge of PIVOT3 required for this?

Metra Response: Metra will be responsible for migration of the data from the existing PIVOT3 VSS to the new VSS with the stand-by assistance of the awarded proposer. Although not required, it is preferred that the vendor have working knowledge of the PIVOT3 system. Proprietary knowledge of PIVOT3 is not required.


Page 18 of 20

Question 113: Section XIV. Scope of Work: The RFP indicates rack cabinet depth is 34 inches. Can you please confirm that is the correct rack cabinet depth? Further, can you please indicate whether this is internal or external depth?

Metra Response: This is the usable internal depth.

Question 114: Section XIV. Scope of Work, B. System Requirements: The RFP calls out a requirement for no greater than a 2U server with 336TB raw disk space. Advances in chassis density, performance options, and disk sizes create options that Metra may not have seen prior to drafting the RFP requirements, but could greatly increase system density and reduce the rack space required. Would Metra consider rack enclosure options greater than 2U and/or 336TB if they are currently available in the market and are capable of delivering higher performance and storage density than the 2U 336TB specified in the RFP?

Metra Response: Yes. See answer to Question 74.

Question 115: Section XIV. Scope of Work, C. Electrical Power: The Drive configuration is listed as “Up to 18x large form factor near line SAS hard disk drives” and in section “B. System Requirements”, the capacity is listed as “up to 336TB raw storage.” To achieve 336TB in 18 drives would require hard drives with a capacity of 18.67TB or more. Can you please clarify whether Metra is looking for 20TB Hard Drives or whether that is an error in the number of drives in the chassis?

Metra Response: Please refer to answer to Question 87.

Question 116: Camera Count: How many cameras will be supported by this new 4.3PB raw solution at the KYD facility?

Can you supply the resolution, frame rates and retention times for those cameras?

Metra Response: This RFP is not for camera replacement. It is for storage migration to free up rack space for future expansion.

Question 117: Video Data Protection: The requirements call for RAID6 data protection; no requirements are stated for more extensive video data protection. Can you please clarify whether any higher protection than RAID6 is required?

Metra Response: No, RAID 6 minimum as stated, and more extensive data protection will be considered.


Page 19 of 20

Question 118: Video Data Redundancy: The requirements call for RAID6 video protection; no requirements are stated for additional protection, including redundant copies of the video. Can you please clarify whether Metra would like to see higher data redundancy options, including fully redundant copies of the video data?

Metra Response: Metra is not interested in duplicating. Equipment redundancy and/or failover is expected to be embedded in the equipment.

Question 119: Application Failover: The RFP does not state requirements for Video Management System or Directory Server Failover. Can you please confirm whether Metra desires VMS or Directory Server failover capability?

Metra Response: No. We will be migrating the Genetec Security software over the new equipment which is where the VMS and/or Directory Service failover resides.

Question 120: System Resiliency: System resiliency items mentioned in the RFP are redundant power supplies, mirrored boot drives and RAID6 for the Video storage drives. Is Metra looking for any failover, redundancy or resiliency beyond that?


Question 121: Usable Disk Storage Space: The requirements call for a 4.3PB raw storage requirement at KYD; can you please clarify how much usable disk space is required for video storage?

Metra Response: Please see answer to Question 9. The usable storage space should provide at least 75% or more of RAW data capacity.

Question 122: Video Management System (Current): Can you please clarify the legacy Video Management System brand, type, and release?

Metra Response: Genetec.

Question 123: Section XIV. Scope of Work, B. System Requirements: the total throughput is listed as 2100Mbit/sec. Is that 2100Mbit/sec for each 336TB raw node, or a total of 2100Mbit/sec for the entire set of nodes that will make up the 4.3PB total storage?

Metra Response: The 2100Mbps is for each raw node.

Question 124: Section XIV. Scope of Work, C. Electrical Power: The processing requirements indicate that “Operating system must be compatible with the existing operating system.” Can you please clarify the details of the existing operating system?


Page 20 of 20

Metra Response: The current operating system is Windows Server 2016.

Question 125: Section XIV. Scope of Work, C. Electrical Power: The Operating System drive configuration is listed as “(2) M.2 SSD Drives, RAID 1.” Would Metra accept a higher availability option that delivers (2) 2.5” SSD (which are hot swappable) as a substitute for the (2) M.2 SSD which are typically not hot swappable?


Question 126: Section XIV. Scope of Work, E. Future Upgrade of VSS System: Can you please clarify any intent to migrate to a new Video Management System brand, type, or release now or in the future?

Metra Response: Although Metra will be upgrading to a new VSS system in the future the timeframe for such upgrade is undetermined.

Question 127: Section XIV. Scope of Work, E. Future Upgrade of VSS System: The scope of this RFP is 4.3PB of raw storage. Can you comment on future Metra plans for expansion or growth?

Metra Response: The scope of this RFP is 13 Petabytes of storage not 4.3 PB. The 4.3 PB will allow for the migration of approximately 50% of the racks which will need to be freed in order to complete the full installation of the 13 PB.

EXHIBIT 1-A Addendum No. 1 dated October 6, 2020

Page 1 of 13

REQUEST FOR PROPOSAL NO. 64979

VIDEO SURVEILLANCE STORAGE SYSTEM SCOPE OF WORK

I. INTRODUCTION Northeast Illinois Regional Commuter Railroad Corporation (NIRCRC) D/B/A Metra is the public corporation (unit of local government) that is responsible for commuter rail transportation in Cook, DuPage, Kane, Lake, McHenry, and Will Counties of Northeastern Illinois. Metra's existence resulted from legislation enacted by the Illinois General Assembly in November 1983, which reorganized the Regional Transportation Authority (RTA). The RTA, formerly responsible for all levels of public transportation policy in the region, was reorganized as a planning and oversight agency. Legislation then established the Commuter Rail Division (Metra), along with the Suburban Bus Division (Pace) and the Chicago Transit Authority (CTA) as the direct operating subsidiaries of the RTA. Under this arrangement, each of the service boards is entrusted with responsibility for policy-making with respect to actual day-to-day operations, capital investments, fare levels, and the planning service and facilities for their respective systems. Metra is one of the largest and most complex commuter rail systems in North America. The agency provides service to and from downtown Chicago with 241 stations over 11 routes totaling nearly 500 route miles and approximately 1,155 miles of track. Metra operates more than 700 weekday trains, providing about 300,000 passenger trips each weekday. Metra is responsible for 24 railyards, 571 grade crossings, 12 fuel facilities and 823 bridges.

II. OBJECTIVE Metra is seeking to identify a qualified firm to provide the replacement and expansion of Metra’s video surveillance storage systems.

III. SOLICITATION SCHEDULE The anticipated schedule for this procurement is outlined below for guidance. Metra reserves the right to modify the procurement schedule as circumstances may warrant. Modifications made after the RFP due date may not be provided via addenda or other notification.

IV. COMMUNICATIONS Questions regarding this RFP shall be submitted via email to Jennifer Zellers, Sr. Contracting

Agent, at [email protected], at the time and date indicated in III. Solicitation Schedule above. Questions submitted after this date and time will not be accepted.

Prospective Proposers and their representatives shall not make any contact with or communicate

with any members of Metra, or its employees and consultants, other than the Contracting Agent regarding any aspect of this solicitation or offer.

Date Time Activity 9/8/2020 - Request for Proposals issued

9/15/2020 4:00 p.m. Questions due 10/16/2020 4:00 p.m. Proposals due *All times are LPT (Local Prevailing Time)

mailto:[email protected]


Page 2 of 13

If it should appear to a prospective Proposer that the performance of the Work under the Contract, or any of the matters relating thereto, is not sufficiently described or explained in the solicitation or Contract documents, or that any conflict or discrepancy exists between different parts thereof or with any federal, state, or local law and any Metra ordinance, rule, regulation, or other standard or requirement, then the Proposer shall submit a written request for clarification to Metra within the time period specified above.

V. PRE-PROPOSAL MEETING

RESERVED VI. ADDENDA

Metra reserves the right to amend the RFP at any time. Any amendments to or interpretations of the RFP will be described in written addenda. Failure of any prospective proposer to receive the notification of addenda shall not relieve the proposer from any obligation under the RFP as clarified, interpreted, or modified. All addenda issued shall become part of the RFP. Failure to acknowledge in their proposals receipt of addenda may at Metra’s sole option disqualify the Proposal. All clarifications and RFP revisions will be documented in an addendum and published on Metra’s website at www.metrarail.com.

VII. PROPOSAL CONTENT AND RFP SUBMISSION REQUIREMENTS All Exhibits should be completed, dated, signed, and/or notarized (when applicable). The contract

and exhibits submitted shall be the originals provided with the solicitation package and shall not be altered or modified. If the Buy America Certification (if applicable) is not completed properly and signed, the proposal may be determined to be non-responsive and not considered further.

If the proposal does not include all executed and required documents for the Contract Proposal,

include a determinable price, or if a Proposer has failed to acknowledge an addendum, Metra may deem the proposal as non-responsive.

A. Submittal Instructions

Proposals shall be clearly marked RFP 64979 – VSS in header of email. Complete proposal submittals are due no later than October 16, 2020 at 4:00 P.M. CST. Metra does not accept late proposals. Submit proposals to the email below:

[email protected] Attn: Jennifer Zellers

B. Proposal Format Proposals are expected to be formatted in a logical manner, as outlined here and include the specific information detail in this section. Do not provide promotional or advertising information, unless this information is requested and/or is necessary to support the technical submittal.

Proposal submittal shall be comprised of three (3) separate pdf files sent as one email, as

outlined below:

1. Eligibility and Certification Requirements a. Submit a signed Contract Signature Page on Page 24 of 24 of the Agreement for

Professional Services and acknowledgement of addenda b. Completed, notarized and signed Exhibit 1-B – Affidavits/Certifications c. Completed and signed Exhibit 1-D – Buy America Certificate

http://www.metrarail.com/

mailto:[email protected]


Page 3 of 13

d. Completed and signed Exhibit 1-L – DBE Compliance Requirements e. Submit any exceptions to Metra’s contract terms and conditions marked “Exceptions to

Metra’s Terms & Conditions” and shall reference each exception by document name and corresponding line, section, number, etc.

2. Technical Proposal

Technical proposal submittal shall include: a. A cover letter summarizing the proposal and an INDEX of all documents submitted. b. One (1) copy of the technical proposal.

3. Price Proposal

A complete original Exhibit 1-C – Price Proposal.

VIII. TECHNICAL PROPOSAL CONTENT

Technical proposals shall include the following:

A. Cover Letter The cover letter should summarize key points of the proposal and should not exceed two pages in length. The cover letter shall identify the RFP title and proposal number, name of proposing organization, address, telephone number, and name and contact information of project manager or contact representative. The cover letter shall also include the statement of offer, provide the name, title, address and telephone number of the individual authorized to negotiate and contractually bind the company during the period of the proposal evaluation, and provide a statement that the proposal is valid for a minimum of one hundred eighty (180) calendar days from the proposal due date.

B. Project Methodology & Understanding Provide a statement of understanding of what would constitute a successfully completed project, including project approach, schedule, rollout order, risks, assumptions, constraints, anticipated problems and resolutions, etc.

C. Overall System Architecture Provide your proposed overall system design based on the requirements of this RFP; including system and integrated features.

D. Installation Design & Cutover Plan Provide your proposed installation design and cutover plan.

E. Firm & Key Personnel Qualifications Provide your firms experience and qualifications and your project teams experience and qualifications with resumes, as indicated in XVIII - Contractor & Key Personnel Qualifications. Submit organizational charts for both firm and key personnel.

F. Training, Licensing, Warranty and Maintenance & Support • Provide your proposed training agenda for Operator, System Administration, and

Technical Maintenance.

• Provide your software and equipment licensing agreement documentation.

• Provide, in detail, the standard warranty for all software and equipment. All software


Page 4 of 13

required for implementation must be included. Proposer may assume that all hardware required for implementation will be purchased by the vendor and included in the Price Proposal for a fixed standard warranty period.

• Provide your maintenance and support schedule as described in the RFP requirements.

G. Additional Services • Describe any other facets of your organization and your firm’s experience that are

relevant to this proposal that have not been previously described and you feel warrant consideration.

H. References

Provide references on three (3) project installations, that occurred within the last five (5) years, of similar type and size to the requirements in this RFP. Provide the company name, phone number and email address of the Project Manager or person with broad knowledge of the project for each reference. Also, provide a reference list of three (3) firms that the proposer has provided support to within the past five (5) years. Provide the company name, phone number and email address of the Project Manager or person with broad knowledge of the project for each reference. Metra reserves the right to request additional references, if deemed necessary.

IX. REVIEW OF PROPOSALS FOR RESPONSIVENESS AND PROPOSER FOR RESPONSIBILITY Each proposal will be reviewed to determine if the proposal is responsive to the submission requirements outlined in this RFP and if the proposer is responsible.

A responsive proposal is one that follows the material requirements of this RFP, includes all documentation, is submitted in the format outlined in this RFP, is of timely submission, and has the appropriate signatures as required on each document. Failure to comply with these requirements may result in the proposal being deemed nonresponsive. A responsible proposer is one that demonstrates the capability to satisfy the commercial and technical requirements set forth in this RFP. A proposer’s failure to demonstrate that it is responsible may result in the proposal being rejected.

Any proposal found to be nonresponsive or any proposer that is found to be not responsible will not be considered further for award. Proposals that do not comply with the RFP instructions and requirements or do not include the required information may be rejected as insufficient and may not be further considered. Metra will provide written notification to proposers if their proposal has been deemed non-responsive. Metra reserves the right to waive minor informalities or irregularities in the proposals received and reserves the right to request a proposer to provide additional information and/or to clarify information.

X. EVALUATION COMMITEE

An evaluation committee, which may include officers, employees, and agents of Metra, will be established. The evaluation committee will carry out the detailed evaluations, including establishing the competitive range (if applicable), carrying out negotiations, and making the selection of the proposer, if any, that may be awarded the Contract. The evaluation committee will make a


Page 5 of 13

recommendation based on the below evaluation criteria to the awarding authority – e.g., Board of Directors.

XI. RFP PROCESS/ BASIS OF AWARD This is a Firm Fixed Price Contract. Proposals will be evaluated based on the criteria described herein. Proposals determined to be in the competitive range may be further evaluated through an interview and negotiations (including the Best and Final Offer process).

Metra may elect to conduct interviews with those Proposers who are determined to be in the competitive range. Once interviews are conducted the Evaluation Committee may conduct a final scoring of those potential Proposers in order to determine the final ranking. Additional negotiations (included Best and Final Offer process) may be necessary. Award will be made to the Proposer who represents the best overall value to Metra.

Failure of a Proposer to report for an interview will be cause for removing the Proposer’s proposal from further consideration provided that Metra has given adequate notice for the Proposer to prepare for the interview. Such adequate notice shall be determined solely by Metra. Metra reserves the right to award contracts based on the initial proposal submitted and without providing any Proposer the opportunity for interview or negotiations.

XII. PROPOSAL EVALUATIONS AND SELECTION PROCESS The following describes the general process by which proposals will be evaluated and a selection made for a potential award. Any such selection of a proposal shall be made by consideration of only the criteria set forth below in this section.

A. This section describes requirements that must be met for a proposal to be considered for the

competitive range. The requirements are not listed in any particular order of importance. Any proposal that Metra determines is unable to meet these requirements will be excluded from further consideration. The requirements are as follows:

1. Proposer is initially evaluated as responsible in accordance with the requirements stated

in the RFP, or as Metra finds it is reasonable that said proposal can be modified to meet the requirements. Final determination of responsibility will be made with final evaluations.

2. Proposer has followed the instructions of the RFP and included sufficient detailed information, such that the proposal can be evaluated. Any deficiencies in this regard must be determined by Metra to be either a defect that Metra will waive in accordance with the RFP, or that the proposal can be sufficiently modified to meet these requirements.

3. Proposal price would not render this procurement financially infeasible, or it is reasonable that such proposal price might be reduced to render the procurement financially feasible. Metra will carry out and document its evaluations in accordance with the criteria and procedures of this RFP. Any extreme proposal deficiencies that may render a proposal unacceptable will be documented. Metra will make specific note of questions, issues, concerns, and areas requiring explanation by proposers and to be discussed in any meetings with proposers that Metra finds to be within the competitive range.

Proposals Not Within the Competitive Range Proposers submitting proposals that have been determined by Metra not to be in the competitive range and cannot reasonably be made to be within the competitive range, will be notified in


Page 6 of 13

writing in accordance with Metra procedures. Such proposals will receive no further consideration.

Discussions with Proposers in the Competitive Range The proposers whose proposals are found by the Metra to be within the competitive range or may be reasonably improved to be within the competitive range, will be notified of any questions or requests for additional information. Metra may elect to conduct interviews with those firms in the Competitive Range, which will be scored in accordance with the technical Evaluation Criteria stated herein. Failure of a Contractor to report for an interview will be cause for removing the Contractor’s proposal from further consideration provided that Metra has given adequate notice for the Contractor to prepare for the interview.

If a proposal that has been included in the competitive range contains conditions, exceptions, reservations or understandings to any Contract requirements as provided in this RFP then said conditions, exceptions, reservations or understandings may be negotiated during these meetings. However, Metra shall have the right to reject any and all such conditions and/or exceptions and instruct the proposer to amend its proposal and remove said conditions and/or exceptions; and any proposer failing to do so may cause Metra to find the proposal to subsequently be outside the competitive range.

No information, financial or otherwise, will be provided to any proposer about any of the proposals from other proposers. Proposers will not be given a specific price or specific financial requirements that they must meet to gain further consideration, except that proposed prices may be considered to be too high with respect to the marketplace or otherwise unacceptable. Proposers will not be told of their rankings among the other Proposers.

If the competitive range process is used, Metra will determine the competitive range after a careful analysis of the technical and price proposals. Such determination will be at Metra’s sole discretion. Discussions and negotiations may then be carried out with only and all proposers within the competitive range. Best & Final Offers (“BAFOs”) may be requested from all within the competitive range. Metra reserves the right to award without discussions, negotiations, or any request for BAFO. Therefore, initial proposals should be submitted on the most favorable terms the Proposer can submit to Metra. Metra will award to the responsible proposer whose proposal is most advantageous and provides the best value to Metra. Accordingly, Metra may not necessarily award to the proposer with the highest technical ranking, nor to the proposer with the lowest price proposal, if doing so would not be in the overall best interest of the agency.

XIII. EVALUATON CRITERIA The following are the complete criteria, listed in descending order of importance, by which proposals from responsible proposers will be evaluated and ranked for the purposes of determining any competitive range and to make any selection of a proposal for a potential award. A. Technical Criteria

1. Project Methodology & Understanding

2. Overall System Architecture

3. Installation Design and Cutover Plan


Page 7 of 13

4. Firm & Key Personnel Experience

5. Training, Licensing, Warranty, Maintenance & Support

B. Price Criteria

Pricing will be evaluated and scored separately based on the Grand Total.

XIV. SCOPE OF WORK Metra intends to replace the existing 8.6 Peta Bytes VSS system at its KYD facility with high capacity, 2U VSS equipment which will be housed in existing 42U electronic rack cabinets, with the following dimensions: 73.5”h x 19” w x 34” d. Each rack contains 2 arrays of 240 Terra Bytes or 480 Terra Bytes per rack. Metra’s initial goal is to migrate at least 1 Peta Bytes of (Raw) data storage with high capacity compute/storage appliances. The initial offload is required to allow space for expansion to 13 Peta Bytes (Raw) data storage. Based on the size of the 2U appliance the chart below shows the space savings from 24 to 336 Terra Bytes units.

Appliance Array Size # of RU Required

Data Storage Data Storage for 8.6 PB Raw Data

24 Terra Bytes 240 Terra Bytes 18 Rack Cabinets 192 Terra Bytes 1.9 Peta Bytes Approx. 3 Cabinets 288 Terra Bytes 2.8 Peta Bytes Approx. 2 Cabinets 336 Terra Bytes 3.3 Peta Bytes Approx. 1.5 Cabinets

A. CURRENT SYSTEM OVERVIEW

• Current Metra environment consists of 325+ Pivot3 appliances supporting 1800 cameras/

mission-critical video surveillance.

• Current Metra KYD Site has 36 arrays consisting of ten (10) Pivot3 appliances (360 total appliances) supporting mission-critical video surveillance. Total (Raw) Storage of 8.6 Peta Bytes. Usable storage of the current system is 79%. Each appliance currently has a maximum capacity of 24 TB (Raw Storage), or 18.96 TB Usable.

• Emergency expansion procurement of four (4) 192 Terra Bytes Pivot 3 Watch appliances for a total of 768 TB (Raw) Storage or 500 TB Usable.

• Current equipment includes legacy appliances over seven years old, which are at End of Support and experiencing accelerated component failures.

B. SYSTEM REQUIREMENTS

VSS shall be designed specifically for the high throughput workload required by video surveillance systems.

• The VSS must be optimized to work in low latency, high consistency video

surveillance environments from the manufacturer. Providing a 15% increase in performance over comparable off the shelf servers.


Page 8 of 13

• Throughput: VSS system must be capable of managing a combined 2100 Mbps of total throughput with handling for simultaneous recording, playback and live streaming.

• VSS capacity up to 336 TB raw storage. • Expansion: System must be configured to be capable of future expansion and

scaling. • Mounting: Standard server enclosure (rack) mounting, requiring no greater than a

2U configuration.

C. ELECTRICAL POWER • Input: 100 to 240 V AC, 50/60 Hz, auto-switching. • Dual Power Supply: 80Plus rating redundant, hot swappable. • Power Consumption: Average: 429W (1+1) (1463.8 BTU/h), Maximum

750W (2559.1 BTU/H) • Drive Configuration: o Video Storage: Up to 18 x large form factor near-line SAS hard disk

drives, hot-swappable, RAID 6. o Operating System: (2) M.2 SSD drives, RAID 1. o Processing requirements Operating system must be compatible with the

existing operating system. o Minimum Processor: 2.2G o Minimum RAM: 32GB DDR4

The bare-metal VSS must have a built-in interface for centralized health management. Utilizing methods by which Metra can review recording service health, future analytics service health, VSS hardware health and camera connection details which includes retention time. The health management software must be compatible with Metra’s existing network monitoring system that supports SNMP (Simple Network Management Protocol) and Ping. Health reports must be easily exported into excel or PDF format.

D. NETWORK CONNECTIVITY REQUIREMENTS

The different solutions will be connected through the existing LAN. Metra will be responsible for connectivity between the various networks.

Contractor will work with METRA’s Telecommunications personnel to ensure that connectivity meets minimum requirements and that network design is mutually agreed upon prior to configuration and deployment.

Network Requirements • Two (10gbps) network port for each VSS (failover). • Two (2) circuits to distribute power to the server rack (dual power supplies).

Network Requirements • Network ports will be 10gbps capable. • Adequate bandwidth will be provided to support the VMS Servers. Final

bandwidth requirements will be determined at Detailed Design Review.

Any on-site activities required during execution of the project, shall follow all


Page 9 of 13

applicable safety and access requirements, as specified by Metra.

E. FUTURE UPGRADE OF VSS SYSTEM Metra is also interested in upgrading to a more advanced analytics video system in the future. The proposed system should consider the capability of the units for future upgrade to a more sophisticated advanced analytical unit.

The proposed VSS system should encompass, at a minimum, the following:

• Be an out-of-the box, ready to deploy video recording platform designed for single site

surveillance or to be distributed across multiple remote sites. • Have the ability to leverage full power of an internal control management system and

Appearance Search technology to deliver the highest available throughput, retention and availability.

• Be able to be used individually or as a cluster of VSS designed for IP video and video analytics metadata storage.

• Have a five-year warranty, with support and onsite parts replacement for continuous recording and retention of video while minimizing disruptions to security operations.

• Be preloaded with a management control center. • Have search technology up to 2,100 Mbps total throughput, simultaneous recording,

playback and live streaming, as well as be highly scalable and with flexible capacity options.

• Have data/compute capacity ranging from a minimum of 192TB to 336 TB effective (RAID 6) for long- term video retention or high camera count recording. Equipment must be hot-swappable to maintain video recording and playback operations even in the event of multiple simultaneous component failures. This system must be independent of operating system and video storage volumes to enable independent, non-disruptive operation.

• Should not require the replacement of equipment to supply future analytic capacity but must have the ability to be upgraded through software with the flexibility to expand the surveillance system.

XV. CONTRACTOR REQUIREMENTS

• All equipment furnished under this contract shall be of the most modern design utilizing the most recent software. In all details not specifically stated herein, it is understood that the equipment shall meet or exceed those standards of the Electronics Industries Association and the Federal Communications Commission.

• The Contractor shall provide all coordination, management, staffing, services, labor, materials, new and current production equipment, parts, tools and incidentals, delivery, installation, implementation, data, documentation, manuals, testing, commissioning, cutover, support and training required for a turnkey installation of the new solution. The system will operate on a stand-alone VLAN network utilizing Metra’s existing Telecommunication infrastructure.

• VSS ’s must have manufacturer 5-year, 24/7 Technical Support with 4-hr response time on hardware replacement.

• Contractor shall supply, install and/or license:

1. All servers and appliances as required


Page 10 of 13

2. All required gateways

3. All software necessary for virtual environment(s), if used

4. All VSS hardware

5. All patch cables required

• Contractor shall provide:

1. All spare equipment as specified.

2. All software and usage licensing for entire system, including spares, as specified for entire warranty period.

3. All initial programming and system administration for installation and cutover.

4. Standard manufacturer’s warranty for all hardware and software as specified.

5. Warranty for all installed equipment.

6. Operator, System Administration and Technical Maintenance training as specified.

7. QMP, s afety plans, and other related documents as per applicable FTA requirements.

XVI. METRA RESPONSIBILITIES

• Migrate existing video data to new system

• Breakdown existing video storage system

• Provide necessary Ethernet port/ports for Redundancy

• Provide UPS

• Provide power for all hardware

• Assist in physical cutover of system

• Provide all required router and firewall connections

XVII. DELIVERABLES

The following deliverables are required:

• Software with appropriate licensing for Metra’s needs.

• Hardware (including overstock) for the system as required to meet Metra’s needs.

• Training materials in an electronic format that can be reused by Metra to train new users.

• Complete system documentation, in an electronic format, for all roles that interact with the new system, including but not limited to: Telecommunication Management and


Page 11 of 13

Communication Maintainers.

• Technical documentation on all facets of the system where technical support is expected of Metra, including but not limited to: database documentation, infrastructure specifications and documentation, software documentation, information on reporting tools, etc.

• All other deliverables required to replace/upgrade Metra’s system as indicated and required in this Exhibit 1-A, Scope of Services and other attachments to this RFP.

XVIII. CONTRACTOR & KEY PERSONNEL QUALIFICATIONS

The Contractor and its Key Personnel shall have the following qualifications required to complete this project:

• Firm shall have at least five (5) years’ experience on at least five (5) projects similar in type and size within the past three (3) years.

• Project Manager and other key personnel necessary for successful completion of the project shall have five (5) years’ experience and at least three (3) installations of similar type and size as this RFP within the past three (3) years.

• System Administrator shall be manufacturer certified in the installation and administration of the system offered. They shall have installed a minimum of three (3) similar systems within the past three (3) years.

XIX. PLACE OF PERFORMANCE It is anticipated that work will be performed at Metra’s Kensington Yard (KYD) located a 12301 S. Indiana, Chicago, IL 60628.

XX. PERIOD OF PERFORMANCE

The period of performance for this contract shall be twelve (12) months from Notice to Proceed. The 1st phase of the project shall be completed in no more than two months and includes off-load of 1 Peta Byte of data, providing equipment and equipment delivery, installation and commissioning of equipment for the 1 Peta Byte offload. Phase 2, consisting of the remaining 10 months, includes the offload of the remaining 3.3 PB from the existing equipment as Metra migrates data from existing system to the new proposed system.

XXI. STATEMENT OF OFFER By submitting your proposal, you are stating that the proposal is valid for 180 days after the proposal due date.

XXII. MODIFICATION OR WITHDRAWAL OF PROPOSALS A modification of a proposal already received will be accepted by Metra only if the modification is received prior to the proposal due date, is specifically requested by Metra, or is made with a requested BAFO. All modifications shall be made in writing and executed and submitted in the same form and manner as the original proposal.

A Proposer may withdraw a proposal already received prior to the proposal due date by submitting to Metra, in the same manner as the original proposal, a written request for withdrawal executed by the proposer’s authorized representative. The withdrawal of a proposal does not prejudice the right of a proposer to submit another proposal within the time set for receipt of proposals.


Page 12 of 13

XXIII. NEGOTIATION DELAY If a written Contract cannot be negotiated within thirty days of notification of the successful Proposer, Metra at its sole discretion at any time thereafter, terminate negotiations with that Proposer and either negotiate a Contract with the next qualified Proposer or choose to terminate the RFP process and not enter into a Contract with any of the Proposers.

XXIV. RESERVATIONS

Proposers should read and understand the solicitation and tailor their proposal to ensure compliance. Metra reserves the right to: (i) amend the solicitation; and (ii) reject any or all proposals/options submitted. Metra is not responsible for and will not pay any costs associated with the preparation and submission of your proposal. By submitting a proposal, Proposer agrees it shall not have any rights against Metra arising at any state of the solicitation from any negotiations that take place, or from the fact that Metra does not select a Proposer for negotiation, or because Metra chooses another Proposer with whom to contract. If your firm is selected, you shall not commence, and will not be paid for any work performed prior to the date all parties execute the contract and Metra issues a Notice to Proceed letter.

XXV. CONTRACT AWARD AND EXECUTION

A Proposer’s participation in this RFP is at its own risk. Whether or not Metra chooses to make an award, or take any other permitted action under this RFP, Proposer will have no cause of action for failure to receive award.

XXVI. COST OR PRICE ANALYSIS

Metra may make a cost or price analysis in conjunction with this RFP. If Metra cannot perform the needed analysis, Metra may obtain the services of a qualified firm to perform the analysis.

By submitting its proposal, the Proposer agrees to furnish, upon request from Metra, all information (including a list of subcontractors and suppliers and their prices) reasonably necessary for such analysis. Furthermore, Metra may request that the Proposer show, in detail, the kinds, quantities, and prices of direct material and direct labor used to develop prices/costs submitted in the proposal.

In addition, Metra reserves the right to request and receive information explaining any estimating process, including the factors, methods, and assumptions used to project from known data, and the contingencies used. Metra may require the Proposer to show how it computes and applies indirect costs and to show trend and budgetary data.

XXII. GOVERNING LAW AND FORUM This Request for Proposal and any resulting contract therefrom shall be governed by the laws of the State of Illinois, and venue for any disputes that may arise shall be either the Circuit Court of Cook County Illinois or the United States District Court for the Northern District of Illinois.

XXIII. FOIA REQUIREMENTS

Metra is subject to the Illinois Freedom of Information Act (5 ILCS 140/1 et seq., “FOIA”), and pursuant to FOIA, your proposal and any subsequent agreement is subject to disclosure. In addition, from time to time, Metra may be required to produce certain “public records” as defined in Section 2 of the FOIA, that are in the possession of or under the control of proposer/operator. Upon Metra’s notification to proposer/operator of a request pursuant to the FOIA, proposer/operator will, within two (2) business days of Metra’s notice, either (i) produce the public records, (ii) notify Metra, in writing, that additional time is required to produce the public records, or (iii) notify Metra, in writing, that the public records do not exist or have been destroyed. In the event that


Page 13 of 13

proposer/operator requires additional time to produce the public records, the written notification under (ii), above, will provide an explanation for the delay and the date when the public records will be received from proposer/operator by Metra. Proposer/operator agrees that in no event shall a delay to produce records exceed five (5) business days.

XXIV. PROPOSAL PROTEST PROCEDURES

Metra will use, if necessary, the applicable provisions of its Bid Protest Procedures ("Procedures") for this RFP. References under the Procedures to bid, bidders, and lowest bidder will mean proposal, Proposers, and highest ranked proposal, respectively. The Proposers have the right to protest the RFP. There are important time limits set forth in the Procedures which are summarized here, but this paragraph is not meant to be a substitute for the Procedures. For a complete copy of Metra's Procedures or any related questions, contact the Contract Officer. In general, the Procedures will control in the case of a discrepancy between this RFP and the Procedures. Deadlines contained in this Section will control over those set-out in the Procedures, and the roles of Department Head, Materials Management, and Executive Director, as used in the Procedures, may be adjusted as necessary.

XXV. CONFLICT OF INTEREST Contractor agrees that the Contractor is prohibited from performing any work or services for Metra which conflicts with the role of the Contractor in any other contract between the Contractor and Metra. This paragraph is also applicable to all sub-consultants which are proposed to be uses by the Contractor for the proposed services. The Contractor has sole responsibility for compliance with this provision. The Contractor is prohibited from performing any work or services for Metra which would result in an organizational conflict of interest (OCI). An OCI occurs when, because of other activities or relationships with other persons, (1) a person is unable or potentially unable to render impartial assistance or advice to Metra or the person’s objectivity in performing services to Metra is or might otherwise be impaired, or (2) a person has an unfair competitive advantage (the term “person” includes companies and other contracting entities). OCIs generally fall into three categories: (a) a person has access to non-public information a part of its performance of services to Metra that might provide that person with a competitive advantage in a future procurement; (b) a person, as a part of its performance of contract responsibilities to Metra, has set the ground rules for the performance of a future contract (e.g. defining the specifications); and (c) a person’s work under one contract with Metra could entail evaluating its own work or that of a competitor, either through an assessment of performance under another contractor through an evaluation of proposals. In the event of an OCI, Contractor shall provide Metra with recommendations to avoid, neutralize, or mitigate the OCI. The Acting Sr. Division Director, Procurement Operations in consultation with General Counsel shall make the final determination as to whether an OCI exists and whether the Contractor’s recommendations to avoid, naturalize, or mitigate the OCI are sufficient. If awarded a Contract, any violation of this provision will constitute a material breach of the Contract, which is cause for termination of the Contract.

date: october 6, 2020question 10: metra’s initial goal is to offload at least 1 peta bytes of...

Documents