Request for Information for Safety Management Software System. RFI No. SFMTA-2011/12-31

Request for Information for Safety Management Software System RFI No. SFMTA-2011/12-31 Date Issued: Wednesday, March 20, 2013 Written Questions Due: Monday, April 1, 2013, 11:59p.m., PDT Participation Confirmation and Friday, April 5, 2013, 5:00p.m., PDT Written RFI Response Due:

(SFMTA) Request for Information for Safety Management Software System RFI#SFMTA-2011/12-31 Table of Contents Page I. RFI Intent and Schedule... 1 II. System Specifications and Information Requested... 2 III. Demonstration Requirements... 8 IV. Contents of Written Response to RFI... 9 V. Terms and Conditions for Receiving RFI Responses... 11 Appendices: A. Confirmation Form for System Demonstration Participation... A-1 B. System Cost Estimation... B-1 C. Attachments to Section III. Demonstration Requirements Incident Report Example... C-1 Incident Reporting Flowchart... C-2 SFMTA Ride Check Form... C-3 SFMTA Monthly Facility Inspection Checklist... C-4 Efficiency Test Field Observation Form... C-5 Corrective Action Report Notification... C-6 Corrective Action Plan Status Tracking Sheet Example... C-7 Operator Accident Re-Training Flowchart... C-8 SFMTA Operator Training Evaluation... C-9 Security Incident Extract Examples...C-10 Security Incident Analysis and Reporting Flowchart...C-11 Incident GIS Map Example...C-12 Safety Management Software System i March 20, 2013 RFI#SFMTA2011/12-31 00835272

A. Intent of RFI I. RFI Intent and Schedule San Francisco is the fourth largest city in California and serves as a center for business, commerce and culture for the West Coast. The City and County of San Francisco ( City ) established by Charter in 1850, is a legal subdivision of the State of California with the governmental powers of both a city and a county under California law. The San Francisco Municipal Transportation Agency is the agency of the City with jurisdiction over all surface transportation in San Francisco, including the San Francisco Municipal Railway ( Muni ), the City s public transit system. Muni, the seventh largest public transit system in the United States measured by ridership, provides approximately 700,000 trips on an average weekday and registers about 215 million boardings annually. Muni serves a diverse clientele of residents and visitors with a variety of socioeconomic and ethnic backgrounds. SFMTA currently uses TransitSafe, implemented in 2005 to track Training, Corrective Actions, Incidents, Audits, and generate regulatory reports. Because of the current program s age, the SFMTA is seeking to replace the existing product with a more comprehensive and advanced safety management software product. SFMTA seeks safety management software system information and demonstrations to determine product capabilities, the availability and feasibility of a comprehensive safety management software package that meets the SFMTA s needs. Materials submitted in response to this RFI will be used for information purposes only and will not be evaluated or scored. B. Schedule The anticipated schedule for the RFI process is as follows: Phase Date RFI Issuance Wednesday, March 20, 2013 Written Questions Due Monday, April 1, 11:59 p.m., PDT Questions and Answers Available Wednesday, April 3, 2013 Submission of Written RFI Response and Deadline to Confirm RFI Participation* Friday, April 5, 5:00p.m., PDT Notification of Participation Issued Monday, April 8, 2013 Software System Online Demonstration Monday, April 15 through Friday, April 19 Note: *Participants should make themselves available on the demo dates. SFMTA will assign a 2-hour time slot to each demonstration participant during the demo week. Safety Management Software System 1 of 13 March 20, 2013

C. Designated RFI Contact: Winnie Xie, C.P.M. Contract Services Manager San Francisco Municipal Transportation Agency One South Van Ness Ave., 6 th Floor San Francisco, CA 94103 Telephone: (415)701-4583 Email: winnie.xie@sfmta.com II. System Specification and Information Requested The following is a summary of the software attributes desired by the San Francisco Municipal Transportation Agency (SFMTA) for a comprehensive Safety Management Software Package. A. Definitions: Cal/OSHA The Division of Occupational Safety and Health, better known as Cal/OSHA, protects workers and the public from safety hazards through its Occupational Safety and Health inspection program California Public Utilities Commission (CPUC) The regulatory agency responsible for Rail Safety in the state of California. California Code of Regulations Title 8 The section of the State of California s Administrative Code governing Industrial Relations. Efficiency Test An operational test or inspection to determine the extent of compliance with rules, policies, bulletins and Standard Operating Procedures (SOPs) specific to an employee's skill set. It involves observing and recording compliance with particular rule requirements in a field application at a pre-determined location. National Transportation Database (NTD) The Federal Transit Administration s (FTA) primary national database for statistics on the transit industry. Transit Division A division of the San Francisco Municipal Transportation Agency Transit Operations Section which operates rail, bus, or trolley transportation service. Verification of Transit Training (VTT) A DMV issued certificate indicating that certain training requirements have been met for new and veteran bus operators. To meet the legal standards for operating a transit bus the operator must possess a VTT, a valid medical certificate and a commercial driver license. B. Information Requested Safety Management Software System 2 of 13 March 20, 2013

The RFI consists of two stages. First, interested firms must respond via email to winnie.xie@sfmta.com by Friday, April 5, 2013, 5:00p.m. (Pacific Daytime-Saving Time), to confirm the participation in the system demonstration and submit a written response including completed Appendix A and Appendix B to this RFI. Second, each participating firm will conduct an approximately 2-hour remote online demonstration between April 15 and April 19 at a time slot pre-assigned by SFMTA. The system demonstration and written information submission shall respond to the following specifications that SFMTA is seeking: 1. System Features and Functions The SFMTA seeks a comprehensive Safety Management Software product that enables the tracking of multiple Safety Management functions under one system, with emphasis on moving away from paper and utilizing electronic data entry forms that are ipad or Android Tablet compatible. Specific report functions, capabilities, forms and documents are described below under their corresponding module. Examples of existing forms are listed under Section III, Demonstration Requested and attached to this RFI. Data will be entered either through the uploading of electronic data entry forms that are ipad or Android Tablet compatible or through a graphical user interface accessible in the software program. The user interface must enable the entry of information in all electronic forms and modules listed below. The software product should also generate tracking reports automatically with minimal user effort. The following items are the desired technical functions and features for demonstration of the anticipated system and the written information submission. The SFMTA encourages vendors to respond to the RFI to schedule a software demonstration even if the product does not contain all of the listed functions. Incidents - An incident tracking function that enables the SFMTA to collect incident data, analyze trends, investigate incidents, and create regulatory reports (examples include California Public Utilities Commission Form R and Form EZ, National Transportation Database forms S&S 40 1 and S&S 50 2. The function or module will enable users to perform root cause analysis and accident preventability determination. The SFMTA will provide incident reporting forms and criteria. Data should automatically geocode with longitude and latitude for use in Tableau Dashboard Reports. The contractor shall ensure incident reporting forms are mobile application compatible for use on an Android Tablet or ipad, (PDF or HTTP) and have capability for attaching pictures, video or audio recordings taken with the tablet. 1 http://www.ntdprogram.gov/ntdprogram/pubs/safetyrm/2012/pdf/2012_s&s_reportable_incid ent_report_form_s&s-40.pdf 2 http://www.ntdprogram.gov/ntdprogram/pubs/safetyrm/2012/pdf/2012_s&s_monthly_summa ry_report_form_s&s-50.pdf Safety Management Software System 3 of 13 March 20, 2013

Inspections - An inspection function that contains forms and pre-built electronic checklists, enabling safety employees to perform inspection and track compliance for on-site safety inspections. Users shall be able to create their own checklists utilizing pre-defined checklist criteria. Standard checklists are to be designed from California Code of Regulations Title 8 3 and CPUC 21 elements criteria. Risk assessments and status tracking of safety hazards will also be included in the function. Automatic alerts of inspection status and safety hazard status are necessary to notify key personnel of status updates. The SFMTA will provide inspection forms and criteria. The contractor shall ensure incident reporting forms are mobile application compatible for use on an Android Tablet or ipad, (PDF or HTTP) and have capability for attaching pictures, video or audio recordings taken with the tablet. Corrective Actions - A corrective action function that enables the SFMTA to create plans for incidents, hazards, safety inspections, and security activities. Corrective action plans will be generated by SFMTA staff based on incident reports, inspections, and regulatory agency recommendations. Corrective action plans shall have the capability to link to specific incident and inspection reports. The corrective action function shall also link to Training Function and update or display the status of recommended Employee re-training or certifications. Employee discipline information will not be part of the software system. The function shall generate reports listing the status and progress of corrective actions and recommended training. Automatic alerts shall notify key personnel of status updates, due dates, or changes in corrective action plans. Training - A training function to track and analyze training activities and incidents, including the training and safety history of employees. Training data will be entered by SFMTA Training staff. Users must be able to view Operator Incident History reports. Operator incident history data will automatically transfer from the Incidents module. The training module will also need to link recommended training or certifications from the Corrective Actions module. Users must be able to query by individual and view operation, training, certification, and incident history. Users must be able to perform ride checks, efficiency tests, and training evaluations. Users must be able to generate reports of employees who need recertification training or specialized training for specific job assignments, triggered by alerts to key personnel and managers. Users must be able to compare actual training received with recertification or specialized training requirements. Automatic alerts will notify employees and supervisors of required training. Operator Verification of Transit Training (VTT) and California Driver s License information will be exported to Trapeze. VTT training is pursuant to California Education Code 40085.5 4. The SFMTA will provide training, efficiency testing, and ride check forms and criteria. The Contractor shall ensure training, efficiency testing, and ride check forms are mobile application compatible for use on an Android Tablet or ipad, (PDF or HTTP) and have capability for attaching pictures, video or audio recordings taken with the tablet. Security Incidents - A security function that enables the entering of security incidents, enables 3 http://www.dir.ca.gov/title8/sub7.html 4 http://www.dmv.ca.gov/pubs/vctop/appndxa/edcode/edc40085_5.htm Safety Management Software System 4 of 13 March 20, 2013

the performance of security inspections and the creation of status reports, and allows users to analyze trends by division, line, and incident type using Excel or Tableau Dashboard Reporting. Data should automatically geocode with longitude and latitude for use in Tableau Dashboard Reports. The SFMTA will provide incident reporting forms and criteria. The contractor shall ensure incident reporting forms are mobile application compatible for use on an Android Tablet or ipad, (PDF or HTTP) and have capability for attaching pictures, video or audio recordings taken with the tablet. Industrial Hygiene - A function that enables safety employees to track and analyze industrial hygiene activities such as exposure assessments, personal protective equipment monitoring, and other key industrial hygiene functions. Medical surveillance data must be confidential, user access to this module shall be limited, and automatic reporting shall notify Safety Staff of fixed cycle examinations. The contractor shall ensure industrial hygiene forms are mobile application compatible for use on an Android Tablet or ipad, (PDF or HTTP) and have capability for attaching pictures, video or audio recordings taken with the tablet. Automated Data Management and Statistical Reporting - The software should have the ability to standardize intersection locations for inspections and incident reports and automatically geocode with longitude and latitude for use in Tableau Dashboard Reporting. Location information will be entered by the user on incident and inspection forms, using either an intersection or choose from a list of pre-defined fixed locations when incidents and inspections do not occur on the street. Examples of these fixed locations are Underground Transit Stations, Maintenance Yards, Facilities, etc. The software must be compatible with Tableau Dashboard reporting and establish a Tableau data connection with minimal user effort. Basic statistical reports and tallies will need to be generated on a monthly, quarterly, and fiscal year basis. The software must have the ability to generate ad-hoc reports utilizing user-defined criteria (fields, values, dates, etc.) and export capability to multiple formats such as Adobe PDF and Excel. The software must have the ability to export data from all modules and should be formatted for entry and use in IBM SPSS Statistics with minimal user effort. Optional Features: Awards - An awards system to notify Division Superintendents of Operator eligibility for awards due to safe performance and operation over a period of time based on the Operator s incident history data stored in the database. Eligibility criteria will be determined by SFMTA Management and customizable for each Transit Division. Injuries - An injury tracking system that enables safety employees to track injuries by facility, incident, and transit division. Injury data will be manually entered into the injury tracking system by SFMTA staff. Injuries are categorized by body part, type of injury, and cause of injury. Automated summary reports shall notify managers and executive staff of injury rates on a monthly basis. 2. Technical Requirements Safety Management Software System 5 of 13 March 20, 2013

RFI respondents are requested to provide documentation detailing the software and database s capability to meet the following requirements: a. The software must have a data input system where data can be entered through a network accessible interface and from mobile devices such as Android tablets or ipads. Data must automatically fill between specified forms in order to minimize duplication of data entry. Specific fields, criteria, and form values will be provided by SFMTA staff for use by the Contractor in developing the electronic forms. Forms should be able to be uploaded remotely via Android Tablet or ipad, (PDF or HTTP) or entered into the database directly using a graphical user interface as detailed in Section 1. System Features and Functions. Forms and information will be linked by a unique Incident Number assigned automatically by the system. b. Tableau is the method currently used by the SFMTA for Dashboard Report generation and maintenance. Data should be easily transferrable to Tableau via extract or database connection and require minimal user modification, input, or updating of data, c. Oracle 11g compatibility is preferred, followed by Microsoft SQL 2008 server, d. A cluster aware environment is preferred, e. The software must be compatible with the VMWare virtual host environment, f. A web application server is the preferred software platform. If the software is a client server, it must be Citrix 6.5 environment compatible. The software must be able to run on a 64-bit operating system. Licensing: Concurrent seat licensing is preferred. Hosting: The SFMTA will host the software on its internal servers and provide maintenance. The Contractor must provide support, software patches and updates to be installed by SFMTA IT staff based on the support maintenance agreement. Security: The software must have configurable multi-layer security based on user, groups, and functions. Safety Management Software System 6 of 13 March 20, 2013

Data Migration: The SFMTA Safety Division currently has ten years of data stored in the existing TransitSafe database. This includes Incident, Employee History, Training, Industrial Safety, and Corrective Action data. The existing data will need to be migrated into the new software product via a data dump from the existing database. The contractor will work with SFMTA IT staff to ensure the data can be properly migrated with minimal manual input. Customization: The Contractor will provide customization of modules, functions, reports and searches to tailor the software to the SFMTA s specific needs as listed above in the requirements for each function. A highly configurable user interface is desired in order to meet the varied needs as listed above. The customized module(s) must be able to integrate into future update release without additional cost. Administrator Console: The software must have a security configuration console that has administrative functionality to manager user access, user security levels, and general application configurations. Data Interface: The software will exchange data with multiple systems the SFMTA currently uses. Web service exchange of data is preferred. The programs that the Safety Management Software will interface with include: Trapeze - Scheduling and Operation Dispatching, and Operator Payroll Software Infor (Spear) System (SHOPS) - Vehicle Maintenance and Fleet and Material Management software. Software must be able to import mileage data from SHOPS for incident rate analysis HR Database- Human Resources Database for Operator Information Awards - The proprietary awards system used by SFMTA Tableau Software platform used for SFMTA s internal reporting system and dashboard reporting with chart and graphs for multiple systems and databases IBM SPSS Statistics Software platform used for SFMTA s statistical analysis 3. Training The SFMTA plans to train 20 employees who will act as trainers for the rest of the users. Training will occur on an SFMTA training site to be determined later. Additional interactive Safety Management Software System 7 of 13 March 20, 2013

testing materials, customized documentation and presentations for trainers are preferred for ease of user training. 4. Documentation SFMTA requires software documentation in printed and electronic format, and expects that the documentation will be updated based on the support maintenance agreement. Software documentation includes technical documentation, data diagrams, data dictionary, and work flow documentation. Respondents shall confirm its participation in the demonstration process and its availability during the one-week demonstration period. 5. Maintenance Support SFMTA requires phone and remote support capabilities for its software. In addition SFMTA requires an on-line knowledge base, emergency after-hour support, estimated response time, and service-level agreement. Please detail the types of consulting and on-site support offered with the software package. 6. Delivery, Schedule, and Warrantees SFMTA requires respondents to specify terms and conditions for delivery, the estimated delivery schedule and the applicable warrantees. 7. Proprietary Conditions and Copyright SFMTA requires respondents to specify any proprietary or copyright software or materials in the submittal. 8. Cost Estimation Respondents are expected to submit estimated line item list pricing for all elements of the system/solution, including the estimated cost of the software on the per user, per module, and yearly license renewal basis. The cost estimation provided by respondents is for informational purposes only, and will not be evaluated or scored. III. Demonstration Requirements Respondents are required to participate in an online demonstration of the software and database system and remotely showcase the system functions and capability to SFMTA staff within the one-week demonstration period. The demonstration is scheduled to occur between April 15 and April 19, 2013. SFMTA will notify each firm, who has confirmed the RFI participation and submitted a written information presentation, the demonstration date and time. The following is a summary of the demonstration requirements: Safety Management Software System 8 of 13 March 20, 2013

A. Guidelines: Software demonstrations shall be performed remotely using a conference call and web-based meeting service such as Go To Meeting or WebEx. B. Software System Functions: The SFMTA requests respondents to demonstrate their respective software and database s ability to meet the functions listed in Section II, Scope of Work. The reports, forms, and processes are provided as examples for respondents to demonstrate their product s functionality and ability to integrate multiple processes and should not supersede requirements listed in the Information Requested. 1. Incidents: Attachment C-1 is an example of an incident form, extracted from the existing Safety Management Software. Fields on the demonstration Incident form should be mapped to NTD S&S 40 Criteria. Attachment C-2 is a flowchart illustrating the current incident investigation and reporting process. 2. Inspections: Attachment C-3 (Ride Check), Attachment C-4 (Monthly Facility Safety Inspection) and Attachment C-5 (Efficiency Test Field Observation Form) are examples of these existing forms. 3. Corrective Actions: Attachment C-6 is an example of a corrective action report that is transmitted to the CPUC. Attachment C-7 is an example of a CAP status tracking sheet manually generated in Excel. 4. Training: Attachment C-8 is a flowchart illustrating the accident re-training process after a preventable accident. Attachment C-9 is an example of an Operator Training Evaluation Form. 5. Security: Attachment C-10 is an extract from the existing Safety Management Software system. Attachment C-11 is a flowchart illustrating the Security Incident Reporting Process. 6. Automated Data Management and Reporting: Attachment C-12 is an example of a map generated with ArcGIS showing types of incidents across the system using geocoded data. C. Technical Requirements: The SFMTA requests respondents to provide documentation detailing their respective software s technical capabilities as requested under Section II, Information Requested. IV. Contents of Written Response to RFI The written response to the RFI should include the following information. For the purpose of easy review, each requested element should be addressed in a separate section proceed by an index tab to identify the subject of the section. The response should be formatted on consecutively numbered pages and include a table of contents. Safety Management Software System 9 of 13 March 20, 2013

A. Cover Letter The respondent should include a cover letter, in the form of a standard business letter, and must be signed by an authorized official of the entity. It should include: 1. A statement regarding the respondent s legal structure (e.g. a California Corporation), federal tax identification number, and principal place of business. 2. The respondent s primary contact for this RFI who has authority to answer questions regarding the response, including: Firm Name, Contact s Name, Contact s Title, Contact s Address, Contact s Phone Number and Email Address. B. Written Presentation of Software and Database System Response Package Respondents must submit a written package via email in responding to the RFI, addressing each element listed under section II. Respondent s system/solution must explain if it is able to meet or exceed these attributes and requirements, or if it does not meet the requirements, explain why and the possible benefits of the requirement adjustment. The cost estimation section shall explain the value difference regarding the pricing difference if respondent proposes different system options. Respondents may provide any other information you believe relevant to this RFI. Please use three-hole recycled paper, print double-sided to the maximum extent practical, and submit it in a three-ring binder. Please do not bind the submittal with a spiral binding, glued binding, or anything similar. Reference Please provide a statement describing the system your firm has utilized and supported over the last five years for public transit systems or public agencies that are similar in system requirements and functionalities described in this RFI. The reference should include: The names, address, and phone number of the client, The name and phone number of a responsible official who may be contacted as a reference. A summary description of the system presented and significant benefits it accomplished C. Time and Place for Submission of Responses Please provide an electronic copy of the information response, the completed Appendix B and the Confirmation Form for System Demonstration Participation via email only to winnie.xie@sfmte.com no later than 5pm, Pacific Daylight Saving Time, April 5, 2013. Safety Management Software System 10 of 13 March 20, 2013

Information that are submitted by fax will not be accepted. Late submissions will not be considered. D. Questions Questions regarding this RFI shall be submitted in writing to the designated SFMTA staff Winnie Xie via email to winnie.xie@sfmta.com. Verbal questions will NOT be accepted nor answered. Written questions are due by 11:59pm, Monday, April 1. Answers to the questions will be posted on the City s Bids and Contracts website by Wednesday, April 3. Questions shall not contain proprietary or classified information. To access the City s Bids and Contracts website, go to http://mission.sfgov.org/ocabidpublication/reviewbids.aspx, select consultants and professional services category, and then click the RFI member to view the RFI document. A. Errors and Omissions in RFI V. Terms and Conditions for Receipt of RFI Responses Respondents are responsible for reviewing all portions of this RFI. Respondents are to promptly notify SFMTA, in writing, if respondents discover any ambiguity, discrepancy, omission, or other error in the RFI. Any such notification should be directed to the designated contact for this RFI promptly after discovery, but no later than five (5) working days prior to the due date for receipt of responses. Modifications and clarifications will be made by addenda as provided below. B. Inquiries Regarding RFI Inquiries regarding the RFI and all intent to request modification or clarification of the RFI must be in writing and submitted via email to winnie.xie@sfmta.com. C. Special Provisions The submittal of a response to this RFI does not guarantee use of the information provided. This is not a Request for Proposals. This RFI is to be used solely for the purpose of this industry review and SFMTA assumes no responsibility for any other use of this document. Participation in this industry review is strictly voluntary and SFMTA will not reimburse participants for any costs in connection therewith. D. Public Records Act and Sunshine Ordinance Responses to this RFI become the exclusive property of SFMTA and subject to the California Public Records Act and the City's Sunshine Ordinance. Information and elements contained in each submittal which are trade secrets as defined in Civil Code section 3426.1(d) or otherwise exempt by law from disclosure, and which are prominently marked as TRADE SECRET, CONFIDENTIAL, OR PROPRIETARY may not be subject to disclosure. SFMTA shall not in any way be liable or responsible for the disclosure of any such records including, without Safety Management Software System 11 of 13 March 20, 2013

limitation, those so marked if disclosure is deemed to be required by law or by an order of the Court. Respondents who indiscriminately identify all or most of their submittal as exempt from disclosure without justification may be deemed non-responsive. In the event the City is required to defend an action on a California Public Records Act or San Francisco Sunshine Ordinance request for any of the contents of a submittal marked confidential, proprietary, or trade secret, respondent agrees, upon submission of its submittal for SFMTA s consideration, to defend and indemnify the City from all costs and expenses, including attorneys fees, in any action or liability arising under the California Public Records Act or San Francisco Sunshine Ordinance. E. Financial Responsibility SFMTA accepts no financial responsibility for any costs incurred by a firm in responding to this RFI. Submissions of the response will become the property of SFMTA and may be used by SFMTA in any way deemed appropriate. F. Reservations of Rights by the City The issuance of this RFI does not constitute an agreement by the City that any contract will actually be entered into by the City. The City expressly reserves the right at any time to: 1. Waive or correct any defect or informality in any response and RFI procedures; 2. Reject any or all responses; 3. Reissue a Request for Information or Cancel the Request for Information to issue an Request for Proposals or Request for Qualifications instead; 4. Prior to RFI response submission deadline, modify all or any portion of the RFI procedures, including deadlines for accepting responses, the specifications or requirements for any materials, equipment or information to be sought under this RFI, or the requirements for contents or format of the responses; 5. Determine that no follow-up RFP will be pursued. G. No Waiver No waiver by the City of any provision of this RFI shall be implied from any failure by the City to recognize or take action on account of any failure by a respondent to observe any provision of this RFI. Summary This Request for Information (RFI) is only for the purpose of collecting information on potential sourcing and product availability of the Safety Management Software System that meets SFMTA s needs. SFMTA has not made any commitment to procure any of the items discussed, and release of this RFI should not construed as such a commitment or as authorization to incur Safety Management Software System 12 of 13 March 20, 2013

cost for which reimbursement would be required or sought, or for which a potential solicitation will be conducted, or a potential contract will be awarded. Safety Management Software System 13 of 13 March 20, 2013

Appendix A Confirmation Form for Online System Demonstration Participation (to submit with completed Appendix B and system information package via email) Name of the firm requesting to participate in the online system demonstration: The date and 2-hour time slot we prefer (SFMTA will make its best effort to accommodate the time you prefer, but we do no guarantee the requested time slot will be available or assigned as requested): I understand that my firm s participation is voluntary, and we will make ourselves available for the time slot SFMTA assigns for us during the demonstration period of April 15 to April 19, 2013. Signature: Name of the Official Authorized to Sign: Contact Phone Number: Email Address: Date: Safety Management Software System Page A-1 March 20, 2012 RFI#SFMTA2011/12-31 00835272

Appendix B System Cost Estimation Estimated line item pricing for all elements of the system/solution: - Cost of the software per user - Cost of the software per module - Cost of the software annual renewal Safety Management Software System Page B-1 March 20, 2013 RFP#SFMTA2011/12-31 00835272

Appendix C Attachments to Section III. Demonstration Requirement The following attachments can be downloaded from the online posting of this RFI in the City and County of San Francisco, Office of Contract Administration s Bids and Contracts website via the following link: http://mission.sfgov.org/ocabidpublication/reviewbids.aspx (select the category Consultants and Professional Services, then select the RFI number RFI#SFMTA2011-12-31 or the RFI title Safety Management Software System ) Incident Report Example... C-1 Incident Reporting Flowchart... C-2 SFMTA Ride Check Form... C-3 SFMTA Monthly Facility Safety Inspection Checklist... C-4 Efficiency Test Field Observation Form... C-5 Corrective Action Report Notification... C-6 SFMTA CAPs Tracking Sheet Example... C-7 Operator Accident Re-Training Flowchart... C-8 SFMTA Operator Training Evaluation Form... C-9 Security Incident Extract Example... C-10 Security Incident Analysis and Reporting Flowchart... C-11 Incident GIS Map Example... C-12 Safety Management Software System Page C-1 March 20, 2013 RFP#SFMTA2011/12-31 00835272