Functionality Descriptions

1. 
   Rail Operations Software Suite (TRMS II). TRMS II is the primary asset that the Operator will use in the operation of Agreement Services. Using TRMS II, the Operator shall record information that includes, but is not limited to, information about train movements including train number, date, equipment, crew members, detailed delay information and causes, and number of passengers carried. Further information about the Operator responsibilities in this area is set out in the Operating Agreement.
   

2. 
   Dispatching Systems. The two dispatching systems, located at CROCC and CETC, are the primary tools that will be used to provide train dispatching services for all lines in the Service Property that are under the dispatch control of the MBTA. Using CROCC and CETC, the Operator shall direct, supervise and control the movement of all trains on such lines, including but not limited to MBTA commuter rail trains, freight railroad trains, and Amtrak’s inter-city passenger trains. The Operator shall be responsible for operating and maintaining the existing dispatching system, including all software and hardware components, at CROCC. The Operator shall operate the existing dispatching system, including all software and hardware components, at CETC, while Amtrak shall continue to maintain such system.
   

3. 
   Trapeze EAM. Trapeze EAM is the primary system that the Operator will use related to activities at maintenance facilities on the Service Property. Using Trapeze EAM, the Operator shall perform activities including, but not limited to: (i) maintaining an inventory of maintenance facilities on the Service Property (including buildings, layover facilities, and components) with a unique identifying number and digital photograph, where applicable; (ii) recording required tests and inspections; (iii) recording preventive, predictive and corrective maintenance activities; (iv) scheduling and control of predictive, preventive, and corrective maintenance programs and associated labor and materials; (v) issuing work orders and purchase orders; (vi) issuing facility status and repair reports; (vii) retaining up to three (3) years worth of information on predictive, preventive and corrective maintenance for each facility or component to produce and analyze trends; (viii) recording information necessary for warranty administration and then generate individual warranty claims that itemize labor and material.
   

1. 
   Trapeze EAM is also the primary tool that the Operator will use for the inspection and maintenance of all Service Property other than the CRMF, Readville and S&I maintenance facilities. Using this tool, the Operator shall perform activities including, but not limited to: (i) maintaining an inventory of each component of railroad infrastructure on the Service Property (including stations, structures, track, Right-of-Way and associated components; grade crossing systems; signals and communication systems; and electrical systems) with a unique identifying number and digital photograph, where applicable; (ii) recording required tests and inspections; (iii) recording preventive, predictive and corrective maintenance activities; (iv) scheduling and control of predictive, preventive, and corrective maintenance programs and associated labor and materials; (v) issuing work orders and purchase orders; (vi) issuing status and repair reports for railroad infrastructure components; (vii) retaining a minimum of ten (10) years worth of information on predictive, preventive and corrective maintenance for each railroad infrastructure component to produce and analyze trends; (viii) recording information necessary for warranty administration.
   

2. 
   Trapeze EAM is also the primary tool that will be used for fleet management and the Operator maintenance of the Service Equipment. Using Trapeze EAM, the Operator shall perform activities including, but not limited to: (i) recording vehicle histories, including dates and serial numbers of components inside-and-out, to be used for fleet performance analysis; (ii) recording the maintenance work on systems and components for reliability and warranty analysis; (iii) tracking the warranty of individual components and complete vehicles; (iv) providing hardcopy reports of vehicle histories to improve field troubleshooting; (v) providing a vehicle-specific work order system for vehicle maintenance including the reporting of open work orders; (vi) recording and tracking defects by date, train, location, symptom, defect, and action; (vii) recording and tracking in-service failures by date, time, train, location, symptom, failure, and action; (viii) recording and tracking mileage of each vehicle; (ix) providing labor and material detail required for warranty claims; (x) providing status of modification and retrofit programs; (xi) recording multiple programs and cost roll up; and (xii) demonstrating compliance with FRA and other regulatory requirements.
   

3. 
   Trapeze EAM is also the primary tool that the Operator will use for maintenance of non-revenue vehicles and other Support Property used in performance of the Agreement Services. Using Trapeze EAM, the Operator shall perform activities including, but not limited to: (i) maintaining an inventory of each non-revenue vehicle and piece of equipment, with a unique identifying number and digital photograph, where applicable; (ii) recording required tests and inspections; (iii) recording preventive, predictive and corrective maintenance activities; (iv) scheduling and control of predictive, preventive, and corrective maintenance programs and associated labor and materials; (v) issuing work orders and purchase orders; (vi) issuing status and repair reports for each non-revenue vehicle or piece of equipment; (vii) retaining a minimum of three (3) years worth of information on predictive, preventive and corrective maintenance for each non-revenue vehicle and piece of equipment to produce and analyze trends; (viii) recording information necessary for warranty administration.
   

4. 
   Materials Management. The Commuter Rail IT Environment shall include a materials management tool that will be used to monitor Operator materials control and handling. Using this tool, Operator shall perform activities including, but not limited to: (i) maintaining an inventory of all existing materials and parts, including capital spares and materials used for Supplemental Work; (ii) optimizing stocking of materials and parts; (iii) calculating the costs of materials and parts used for work orders and Supplemental Work; (iv) tracking the status of all materials sent to vendors for repair and return; (v) controlling the ordering of materials and parts; and (vi) tracking specific materials, serialized components, budgets and project costs. The tool shall also: (a) automatically calculate the appropriate order level and order quantity for an inventory item, based upon inventory turnover, order frequency and expected delivery time, and (b) have the capability for the automatic calculation to be overridden by manual input for each inventory item. The tool shall record, at a minimum, the following types of information:
   

(1) Inventory identification and description, including serial numbers where appropriate

(2) Location identification and description

(3) Manufacturer

(4) Number of units on hand

(5) Unit cost

(6) Main supplier and alternative supplier

(7) DBE status of suppliers

(8) Number of units ordered and total cost per MBTA Fiscal Year

(9) Total dollar value paid to each supplier during each MBTA Fiscal Year

(10) Delivery time from when order is placed

(11) Level at which an order shall be placed

(12) For spare parts, list the equipment items(s) for which they are spares

(13) Inventory issues to work orders and Force Account Work projects

5. 
   Human Resources. The Commuter Rail IT Environment shall include a human resources application, that shall be the primary tool used by the Operator for management of its personnel involved in performing the Agreement Services. Using this tool, the Operator shall record information that includes, but is not limited to: employee certifications and qualifications; training received; disciplinary actions; drug and alcohol program status; and employee roster and assignments.
   

6. 
   Financials. The Commuter Rail IT Environment shall include a financial tool that the Operator will use for financial activity related to the performance of the Agreement Services. Using this tool, the Operator shall perform activities including, but not limited to: (i) recording daily ticket sales, and revenues collected and deposited by the Operator; (ii) recording direct costs and producing invoices associated with Supplemental Work; (iii) recording direct costs and producing invoices associated with Service Changes until such time as a fixed price for the Service Change is established; (iv) reporting on DBE compliance; and (v) tracking receipts from sale of scrap materials, and purchases of supplies and materials from same.
   

1. 
   Inventory documents: (i) Complete asset inventory; (ii) Current by-site list, role-based and sortable list of IT assets; (iii) Owner and serial list inventory; and (iv) History of retired or destroyed equipment, tied to asset control and Ticket information, detailing disposal reason and purpose.
   
2. 
   Systems documents: (i) Build guides; (ii) System lists; and (iii) Configuration documents.
   
3. 
   Networks: (i) Logicals; (ii) Connection diagrams; (iii) Site diagrams; (iv) Inter-site diagrams; (v) Ports, protocols and services (PPS) listing for site integration; and (vi) Interface diagrams.
   
4. 
   Storage: (i) Configuration logicals; (ii) Replication diagram; (iii) Access controls; and (iv) Backup and restore procedure.
   
5. 
   Access: (i) Access control list; (ii) Covers rights and level of access; and (iii) Approval process and procedure for gaining and revoking access.
   
6. 
   Logical: (i) Complete systems diagram; (ii) Complete site diagrams; and (iii) Aggregate logical diagrams.
   
7. 
   Architecture: (i) Security posture; (ii) Compliance mechanisms; (iii) Growth direction and support plan; (iv) Capacity guidelines; and (v) Security Architecture and Stance.
   
8. 
   Baseline: (i) Configuration; (ii) Images; and (iii) Template forms and documents.
   
9. 
   Compliance Scans
   
10. 
    Policy and operational guidance documents
    

Appendix 3 to Schedule 3.16: