RFP 76C-18 Form B Technical Response Form.docx

ENTER YOUR COMPANY NAME HERE 7

RFP 76C-18

FORM B: Technical Response Form

Instructions:

· Enter your company name in the header

· Enter your response to each question in the “Response” column

· Please do not change the response font (Times New Roman 11), the column width, the margins, or the header/footer

· Ensure that your responses fill no more than 20 pages

Enter Your Company Name and a contact person for this RFP

Solution: Outline your proposed solution for the MBTA RFID System and your overall architecture for setting up the RFID system based on the three phase approach contemplated in this RFP. Clearly indicate all MBTA deliverables necessary. If you recommend another implementation approach, please describe in detail and clarify the benefits for the MBTA.

Solution: Will you be teaming with a subcontractor and if so indicate the subcontractor and provide information on their experience.

Experience: Describe past RFID Solutions your company has setup for Passenger Transit Systems in North America

Experience: Describe how your system improved your customer’s maintenance and asset management practices and how these can enhance the MBTA’s practices

Experience: How do you feel your company is different than other companies providing a similar service and what sets your company apart that will benefit the MBTA?

RFID tags: Describe the RFID Tags being proposed and give their manufacturer, physical dimensions, memory size, whether the tag is passive or active, and if a parent-child relationship will be used between tags?

RFID tags: How long have you been using these tags?

RFID tags: How do you plan on mounting these tags to the trains and also individual assets such as brakes and motors?

RFID tags: Describe from past projects where a similar mounting technique was used that meets or exceeds the MBTA’s operating conditions?

RFID tags: Detail the product lifecycle for the proposed RFID tags – for example, is there a known end of life date, are there updates or maintenance requirements, etc.

RFID tags: Describe your mitigation plan if the tags become obsolete? This plan shall include how to transfer data, ensure that tags can be used with your operating system, discuss vendor support, and outline any transition costs to the MBTA.

RFID tag information: From your past projects describe the types of information that is typically stored on RFID Tags?

RFID tag information: How much data can typically be stored on the RFID Tag you are proposing?

RFID tag information: Provide examples where you have used RFID solutions to improve a customer’s maintenance, asset management practices, and other operational areas such as warranty repairs.

RFID tag information: From past projects what information do you feel that needs to be or can be captured on the RFID Tag that can enhance the MBTA’s maintenance and asset management practices?

Programming RFID tags: Describe the process for programming the tags, software required for programming the tags and how the software manages the creation of new tags?

Programming RFID tags: Does your system have the ability to read a manufacturers bar code and apply this information to the creation your proposed RFID Tag?

Programming RFID tags: The MBTA would like to track overhaul and repair information on the RFID Tags. Is this information stored on the RFID tags or through your software? How does your system and prosed tag allow for updating? Can these updates be made through the handheld readers?

Programming RFID tags: Provide examples of customers where you have set up similar systems?

RFID readers: Provide the manufacturer and model number of the proposed hand held reader? Provide basic information about the capabilities given the environmental conditions.

RFID readers: Do the proposed RFID readers require a wireless connection?

RFID readers: Describe how your RFID readers are powered and charged. If appropriate, describe charging times, battery life, and battery replacement.

RFID readers: Do you develop the application software used by the reader to display the data or does the manufacturer of the hand held device provide that?

RFID readers: How does the MBTA change the application data to change the fields that are displayed for the data?

RFID readers: Does the MBTA have the ability to define user views depending on their role so only pertinent data is displayed and how is this done?

Antenna Arrays: Provide the manufacturer and model number of the proposed antenna arrays? Provide basic information about the capabilities given the environmental conditions.

Antenna Arrays: Describe network connection and power requirements for the proposed antenna arrays.

Antenna Arrays: Describe your plan to set up the antenna array in the MBTA Yards.

Antenna Arrays: Give examples where you have set up a similar array?

Antenna Arrays: Give an example of where you set up an Antenna Array to read passenger transit vehicles in North America that would see similar weather conditions to the Boston Area?

Software: Describe your RFID Asset Management Software. This description should include its ability to track MBTA assets, their locations and the vehicle it is assigned to.

Software: Does the software have the ability to allow the user to look at a certain fleet, such as the Orange Line, and provide reports on that fleet.

Software: How does the software resolve conflicts when duplicate records are generated due to erroneous data entry? How does the software report on missing tags on our vehicles?

Software: How does the software allow the user to look at certain assets and provide reports on those assets such as location, usage and repair state.

Software: Explain the degree to which the software may be customized to add new fields to parts or information about specific parts when MBTA needs change.

Software: Indicate if your software is cloud based or housed locally at the MBTA. If cloud based clarify how data can be migrated in the event another provider is selected in the future. If housed locally please describe hardware requirements.

Software: Describe the reports and information that can be generated based on our assets and their usage. Indicate if reports can be scheduled and ad hoc.

Software: Describe how the MBTA can add maintenance cycle information to the software so that the software will alert the Maintenance Staff when assets are due for maintenance.

Software: Does the software have the ability to send email and text alerts to certain identified users under specified conditions? How can the MBTA change the individuals who will receive these alerts and texts?

Software: Can reports be exported to Excel or a pdf format? Clarify if such reports can include the following information: part serial number, manufacturer, vehicle part is associated with, and location such as vehicle, car house, or Everett Main Repair Facility.

Software: What support will be required from the MBTA Software Administrative Staff to support the transfer of data from our legacy system to your system and vice versa?

Software: If the MBTA were to significantly increase the number of assets (tags), could the proposed software support this?

Integration: List any systems that your software currently integrates with for similar applications.

Integration: Describe how your software will interface into the MBTA’s legacy maintenance software including your plan for interfacing to the Legacy System (Trapeze) and what industry open standards you will use?

Software Licensing and Support: What platform or application is your software built upon, including the database?

Software Licensing and Support: Will this platform or application require additional software or support from the MBTA to run your application? If so please describe in detail.

Software Licensing and Support: Describe how readily available your software is 24/7 365 days per year? Indicate any maintenance windows or other times at which your solution would not be available.

Software Licensing and Support: What protocols are in place for your software to update itself on MBTA maintenance activities if your system is down or the MBTA system is down for maintenance or network connection issues?

Network Interface: What are the power requirements, connection type (e.g. wired, wireless), and network interfaces required for your proposed antenna array solution?

Network Interface: What network interface (e.g. wireless) is required for your hand held devices to operate and connect to your software system?

Network Interface: What is the network connection you will require to interface your software platform to the MBTA Network?

Network Interface: Please describe how this network interface will take place and what access is required by your system?

Network Interface: Describe the network and infrastructure you will require from the MBTA to implement your RFID solution.

Information Security: Describe in detail how the field-based components (antennas, handhelds, tags, etc.) of your solution guard against intrusion, data breach, and other unauthorized system access.

Information Security: If you are proposing a hosted solution, provide an overview of the data and information security processes, solutions, and auditing in place.

Optional: What else would you like us to know about your company or the services you intend to provide to the MBTA?