C250192_Exhibit_A,_Attachment_A_Business_Requirements.pdf

RFP 250192

EXHIBIT A

ATTACHMENT A

A1. VENDOR RESPONSE INSTRUCTIONS

A2. FUNTIONAL REQUIREMENTS LISTS

A2. NON-FUNCTIONAL REQUIREMENTS LISTS

A3. VENDOR QUESTIONAIRE

B1: TERMS DEFINITIONS

B2: REPORT AND FORMS LIST

B4: INTERFACES AND DATA EXCHANGE

B5: SYSTEM USERS

B6: PRINTERS

B7: LOCATION DEMOGRAPHICS

B8: BUSINESS PROCESS FLOW DIAGRAMS

B9: OCTA SYSTEM TOPOLOGY DIAGRAMS

Table of Contents

VENDOR TO COMPLETE and or REVIEW

SYSTEM REFERENCE DOCUMENTS

ATTACHMENT A

OCTA's Priority Description 1 - Required Solution must have in core application.

2 - Nice to have Process that is neither manual or in OCTA's current solution but would be beneficial to OCTA.

3 - Out of Scope Not available.

OCTA's Priority Description 1 - Required, if solution is hosted (cloud-based)

Software is hosted (cloud-based) and non-functional requirement can fully be met.

2 - Required, if recommending on-prem environment

Recommending an on-prem environment and the non-functional requirement can fully be met.

3 - Nice to have Process that is neither manual or in OCTA's current solution but would be beneficial to OCTA

Proposed Solution's Capability Description

Yes: Software has the ability to meet the requirements functionality.

Exception: Software has the ability to meet the requirement, explanation required.

Future Enhancement: Software feature is approved and the product roadmap and includes a timeframe.

Not Available: Software does not have the functionality and no plans for the function in product roadmap.

Method to Implement Description

OOtB with configurations: The "Out-Of-the-Box" product has this capability using system configuration(s) .

Software customization: Requirement can be met when software is customized.

Software customization and 3rd party software: Both a product customization and 3rd party software would be required to meet this requirement.

3rd party software: Other customers accomplish this requirement using 3rd party software.

Proposed Solution's Capability Description

Y Yes, the firm can fully meet the requirement;

N No, the firm cannot meet the requirement;

E The firm has an Exception to the requirement. If “E”, then the firm shall describe what the firm can or cannot do. (Firms can use (Exhibit F, Exceptions and Deviations Form), if the complete description of the Exception does not fit in the cell provided.

A1. Vendor Response Instructions *Note: Please use the following table to respond to A2 Functional and non-Functional Requirements

Functional Requirements List

TAB A2. FUNCTIONAL

Column G

Non-Functional Requirements List

TAB A2. NON-FUNCTIONAL

Column D

Responses for both Functional and Non-Functional Requirements TAB A2. FUNCTIONAL and NON-FUNCTIONAL

Please use the following table to respond to requirements

Responses for Vendor Questionnaire

TAB A3 - PROJECT IMPLEMENTATION TASKS AND DELIVERABLES SECTION

Printed on: 3/24/2026 at 12:29 PM Page 2 of 21 A1

ATTACHMENT A

INFORMATION PROVIDED BY OCTA TO BE UPDATED BY THE PROPOSER / VENDOR

System Requirement Business Area Type Process Category Process Type Task/Action OCTA's Priority Proposed Solution's Capability

Method to Implement

Software Customization Cost

3rd Party Software Cost Comments Assumptions

1.0 As a CFR Contractor, I can issue parts to CFR work orders only from inventory locations assigned to CFR and shall prevent issuance from OCTA or other business inventory locations.

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

2.0 The system shall ensure that CFR Contractor users have the ability to issue inventory exclusively from inventory locations assigned to CFR Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

3.0 The system shall enable the CFR Contractor to maintain and manage its inventory independently from OCTA inventory operations, including separate inventory locations, stock records, transactions, and controls.

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

4.0

The system shall support segregation of parts inventory at Non-OCTA operated locations (e.g., CFR Contractor / non-OCTA domain users), with inventory ownership remaining with the vendor and maintained separately from OCTA inventory records, balances, and transactions.

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

5.0

As an OCTA user, I will have the ability to upload/enter initial inventory for CFR Contractor run location:

-User Name -Date of Update -Part Number -Part Description -Qty -Location (Infor example Store/Location ) -Price

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Create 1 - Required

6.0 CFR Contractor/non-octa domain will have the ability to view on hand inventory. Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control View 1 - Required

7.0 CFR Contractor/non-octa domain will have the ability to edit on-hand inventory for their respective location only with the necessary role assignment.

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Edit 1 - Required

8.0

The system shall provide the ability for CFR Contractor (Non-OCTA domain) users to perform inventory quantity adjustments (positive and negative) within their authorized inventory locations and shall capture complete adjustment audit details, including:

-User Name -Date of Update -Part Number -Part Description -Qty -Location (For example Store/Location) -Warehouse

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Edit 1 - Required

9.0

The system shall allow third-party vendor (Non-OCTA domain) users to manage and record inventory movements within their authorized inventory locations. All inventory movement transactions shall capture and retain detailed audit information, including:

-User Name -Date of Update -Part Number -Part Description -Location (For example Store/Location) -Inventory Adjustments (Qty) -Data of Adjustment (MM/DD/YYYY) -Warehouse (i.e. moving part a quarantine warehouse)

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Edit 1 - Required

10.0

The system shall support the use of a common asset identifier selection (e.g., Bus Number) across both OCTA and Non-OCTA operated locations, enabling authorized users to reference the same asset records regardless of location or domain.

Contracted Fixed Route (CFR) Functional Asset Management Asset Setup Assign/Select 1 - Required

11.0

The system shall support multiple warehouse and inventory status designations to enable movement of materials between locations (e.g., On- Hand to Quarantine), while maintaining accurate inventory balances and full transaction history

Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

12.0

The system shall assign CFR Contractor users to defined role-based access control (RBAC) profiles that restrict system access, data visibility, and transaction permissions in accordance with their authorized business functions.

Contracted Fixed Route (CFR) Functional Security & Administration User Management Access 1 - Required

13.0

The system shall enable CFR Contractor users to utilize the same reporting tools and features currently available to OCTA users, including report creation, filtering, scheduling, and export, while enforcing role-based permissions and restricting access to authorized data only.

Contracted Fixed Route (CFR) Functional Reporting & Analytics Custom Reports Assign/Select 1 - Required

14.0

The system shall provide OCTA with the ability to generate Period Preventive Maintenance (PM) on-time performance reports to monitor CFR compliance and ensure proper oversight of scheduled maintenance activities.

Contracted Fixed Route (CFR) Functional Reporting & Analytics Custom Reports Create 1 - Required

15.0 The system shall support inventory reporting with configurable filters for single or consolidated locations, including cost and no-cost reporting views. Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Create 1 - Required

16.0 Application will support the ability to view asset maintenance history when asset is transferred from an OCTA run location to a Non-OCTA run location.

Contracted Fixed Route (CFR) Functional Asset Management Asset Setup View 1 - Required

17.0 The system shall allow CFR Contractor users to manually enter and maintain employee hourly labor rates for use in work order cost calculations, subject to role-based access controls.

Contracted Fixed Route (CFR) Functional Maintenance Management Work Orders Create 1 - Required

18.0 EAM PM Inbox shall provide a filter to sort PMs by Meters 1 due, minimum date due, hours used, calendar days, or other criteria identified by OCTA. Contracted Fixed Route (CFR) Functional Security & Administration User Management Edit 1 - Required

19.0 Ability to issue parts associated to a specific workorder, decrementing from on hand inventory. Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

20.0 Ability to return a part as defective/warranty in to its specific warehouse.

(i.e. shelf and or bin). Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Assign/Select 1 - Required

21.0 Ensure mobile device solution replicates desktop application functionality. Contracted Fixed Route (CFR) Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

22.0 Vendor Document mobile device solution limitations that differ from desktop application. Contracted Fixed Route (CFR) Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

23.0 the CFR Contractor Ability to create material part numbers and associate to specific locations specific to CFR. Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Create 1 - Required

24.0 Ability to create materials with a zero cost. Contracted Fixed Route (CFR) Functional Inventory Management Inventory Control Create 1 - Required

28.0 The system shall provide a User-Defined Field (UDF) to capture Badge Number information and shall support alphanumeric text entry. Contracted Fixed Route (CFR) Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

Printed on: 3/24/2026 at 12:29 PM Page 3 of 21 A2 Functional

ATTACHMENT A

INFORMATION PROVIDED BY OCTA TO BE UPDATED BY THE PROPOSER / VENDOR

System Requirement Business Area Type Process Category Process Type Task/Action OCTA's Priority Proposed Solution's Capability

Method to Implement

Software Customization Cost

3rd Party Software Cost Comments Assumptions

30.0 The system shall allow the Badge Number User-Defined Field (UDF) to be available for filtering, sorting, and inclusion in reports, dashboards, and data exports as required.

Contracted Fixed Route (CFR) Functional Reporting & Analytics Custom Reports Assign/Select 1 - Required

31.0 Inspections and maintenance activities may be completed earlier or later than the scheduled mileage, provided the variance does not exceed ±10% of the defined maintenance interval mileage.

OC Streetcar Functional Inspection Management Digital Inspections Schedule 1 - Required

32.0

As a user, I want to access a fully digital inspection checklist for defined scheduled maintenance events, including visual diagrams of inspection points, So that I can complete inspections accurately, consistently, and in compliance with maintenance standards for the following service intervals:

-Weekly -Monthly (2.5K) -3 mo. (8.25K) -6 mo. (16.5K) -Annually (33K) -14 Mo. (40K) -2 Yr. (66K) -5 Yr.(165K) -8 Yr. (264K) -10 Yr. (330K) -15 Yr. (495K)

OC Streetcar Functional Inspection Management Digital Inspections Schedule 1 - Required

33.0

The system shall provide a digital inspection checklist associated with specific maintenance intervals -Weekly -Monthly (2.5K) -3 mo. (8.25K) -6 mo. (16.5K) -Annually (33K) -14 Mo. (40K) -2 Yr. (66K) -5 Yr.(165K) -8 Yr. (264K) -10 Yr. (330K) -15 Yr. (495K)

OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

33.1 The system shall allow inspection checklists to be attached to the work order, linking the user to the item level Manufacturer repair guide. OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

33.2 The system shall allow technicians to record findings, measurements, pass/fail results, comments, and attachments (e.g., photos). OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

33.3 The system shall store completed inspection records as part of the asset maintenance history. OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

33.4 The system shall allow version control of inspection templates. OC Streetcar Functional Inspection Management Digital Inspections Edit 1 - Required

33.5 The inspection checklist shall be accessible via mobile devices. OC Streetcar Functional Mobile Functionality Mobile Work Orders Access 1 - Required

33.6 The system shall allow Manufacturer repair guides to be attached to the asset at the item level. OC Streetcar Functional Maintenance Management Digital Inspections Assign/Select 2 - Nice to have

34.0

As a user, I want to access a fully digital inspection checklist for defined scheduled maintenance events, including visual diagrams of inspection points, So that I can complete inspections accurately, consistently, and in compliance with maintenance standards for Daily Inspections "Pre Trip"

OC Streetcar Functional Inspection Management Digital Inspections Schedule 1 - Required

35.0 Ability to retire/EOL asset within the application. Logging the needed information. (i.e. Year, Odometer) OC Streetcar Functional Asset Management Asset Setup Assign/Select 1 - Required

36.0 As a user, I want to report on retired/EOL assets including attributes such as year and odometer so that I can support lifecycle and replacement planning.

OC Streetcar Functional Reporting & Analytics Custom Reports Assign/Select 1 - Required

36.1 The system shall support reporting on retired/EOL assets including configurable asset attributes (e.g., year, odometer). OC Streetcar Functional Reporting & Analytics Custom Reports Assign/Select 1 - Required

37.0 Application will have the ability to output inspection lists with images or drawings in PDF or word format. OC Streetcar Functional Inspection Management Digital Inspections Print/Output 1 - Required

38.0 Application to provide predictive maintenance schedule including alerts of when maintenance is coming due for service. OC Streetcar Functional Maintenance Management Planned Maintenance Schedule 1 - Required

39.0 The system shall support scanning assets using barcodes, including the ability to scan and track work orders. OC Streetcar Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

40.0 The system shall support scanning assets using barcodes, including the ability to scan and track parts. OC Streetcar Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

41.0 The system shall support scanning assets using barcodes, including the ability to scan and wayside assets. OC Streetcar Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

42.0 The system must enable Users to easily and efficiently navigate to add / input Defects (as Work Orders) during an inspection process using mobile devices where needed.

OC Streetcar Functional Mobile Functionality Mobile Work Orders Create 1 - Required

43.0 The system must provide functionality that supports Preventive (Scheduled) Maintenance Management:

-Notifications of upcoming maintenance

OC Streetcar Functional Workflow Workflow Routing Schedule 1 - Required

44.0 As a user, I want to manage planned maintenance activities in near real time so that schedules remain accurate and up to date. OC Streetcar Functional Security & Administration User Management Schedule 1 - Required

45.0 The system shall support near real-time updates for planned maintenance activities. OC Streetcar Functional Maintenance Management Planned Maintenance Edit 1 - Required

46.0 As a user, I want to manage unplanned maintenance activities in near real time so that corrective actions are tracked promptly. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

47.0 The system shall support near real-time creation and updates of unplanned maintenance work. OC Streetcar Functional Maintenance Management Planned Maintenance Edit 1 - Required

48.0 As a user, I want near real-time visibility into work order status so that I can monitor progress. OC Streetcar Functional Security & Administration User Management View 1 - Required

48.1 The system shall provide near real-time work order status updates. OC Streetcar Functional Maintenance Management Planned Maintenance Edit 1 - Required

Printed on: 3/24/2026 at 12:29 PM Page 4 of 21 A2 Functional

ATTACHMENT A

INFORMATION PROVIDED BY OCTA TO BE UPDATED BY THE PROPOSER / VENDOR

System Requirement Business Area Type Process Category Process Type Task/Action OCTA's Priority Proposed Solution's Capability

Method to Implement

Software Customization Cost

3rd Party Software Cost Comments Assumptions

49.0 As a user, I want to manage planned maintenance activities in near real time so that schedules remain accurate and up to date. OC Streetcar Functional Security & Administration User Management Schedule 1 - Required

49.1 The system shall provide near real-time work order status updates. OC Streetcar Functional Maintenance Management Planned Maintenance Edit 1 - Required

50.0 The system must support maintenance scheduling as defined by the business. (i.e., AC, Electric) OC Streetcar Functional Maintenance Management Planned Maintenance Schedule 1 - Required

51.0 As a technician, I want to record labor, materials, warranty, and defect information against assets so that maintenance history is accurate. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

52.0 The system shall capture and store work performed details including labor hours, materials used, warranty status, and defect information. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

53.0 The system must have the ability to attach files, including .pdfs (i.e. Images Certificates, Invoices) to the Asset. OC Streetcar Functional Document Management Document Library Print/Output 1 - Required

54.0 As a mobile user (e.g., technician or supervisor), I want to access the application on a mobile device (i.e.., Phone, Tablet) OC Streetcar Functional Mobile Functionality Mobile Work Orders Access 1 - Required

55.0 As a user, I want to access the application on a desk top or mobile device and update work orders, so that work status and maintenance records remain current while working in the field.

OC Streetcar Functional Mobile Functionality Mobile Work Orders Edit 1 - Required

55.1 System shall support on a desk top or mobile device and update work orders, so that work status and maintenance records remain current while working in the field.

OC Streetcar Functional Security & Administration User Management Edit 1 - Required

55.2 The system shall allow entry of labor time, notes, defect information, and warranty indicators. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

56.0 As a mobile user, I want to create work orders from a mobile device so that maintenance activities can be initiated in the field without delay. OC Streetcar Functional Mobile Functionality Mobile Work Orders Create 1 - Required

56.1 The system shall allow authorized users to create work orders from a mobile device. OC Streetcar Functional Mobile Functionality Mobile Work Orders Create 1 - Required

56.1 The system shall support required data entry fields (asset, location, description, priority, category). OC Streetcar Functional Asset Management Asset Setup Assign/Select 1 - Required

57.0 As a mobile user, I want to view detailed work order information on my mobile device so that I can understand scope, history, and requirements while in the field.

OC Streetcar Functional Mobile Functionality Mobile Work Orders View 1 - Required

57.1

The system shall allow users to view detailed work order information, including:

-Asset details -Task lists -Labor and materials -Notes and attachments -Work order history -Current status

OC Streetcar Functional Inventory Management Inventory Control View 1 - Required

58.0 As a mobile technician, I want to update work orders from my mobile device so that status and completion data remain accurate and timely. OC Streetcar Functional Mobile Functionality Mobile Work Orders Edit 1 - Required

58.1 The system shall allow users to update work order status (e.g., Open, In Progress, On Hold, Complete). OC Streetcar Functional Security & Administration User Management Edit 1 - Required

58.2 The system shall allow entry of labor time, notes, defect information, and warranty indicators. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

59.0 As a mobile user, I want to assign materials to a work order from my mobile device so that material usage is captured at the point of work. OC Streetcar Functional Mobile Functionality Mobile Work Orders Edit 1 - Required

59.1 The system shall allow users to assign materials to a work order via mobile device. OC Streetcar Functional Mobile Functionality Mobile Work Orders Edit 1 - Required

59.2 The system shall validate inventory availability prior to assignment. OC Streetcar Functional Inventory Management Inventory Control Edit 1 - Required

59.3 The system shall support barcode scanning where applicable. OC Streetcar Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

60.0 As a mobile user, I want to view work order status from my mobile device so that I can monitor progress and prioritize tasks. OC Streetcar Functional Mobile Functionality Mobile Work Orders Edit 1 - Required

60.1 The system shall allow filtering and searching by status, priority, asset, and assignment. OC Streetcar Functional Asset Management Asset Setup Edit 1 - Required

61.0 Mobile transactions shall reflect in the system in near real time. OC Streetcar Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

62.0 Role-based access controls shall be enforced consistently across mobile and desktop platforms. OC Streetcar Functional Mobile Functionality Mobile Work Orders Access 1 - Required

63.0 The mobile interface shall be responsive and optimized for field use. OC Streetcar Functional Mobile Functionality Mobile Work Orders Data Exchange 1 - Required

64.0 Data entry shall be streamlined to minimize keystrokes in field conditions. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

65.0 Mobile transactions shall integrate seamlessly with core EAM, inventory, and reporting modules. OC Streetcar Functional Mobile Functionality Mobile Work Orders Data Exchange 1 - Required

66.0 The system shall allow mobile users to record time worked and materials used directly from a mobile device. OC Streetcar Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

67.0 The system shall provide mobile access with GPS/GIS capability to capture and display asset and work order locations. OC Streetcar Functional Mobile Functionality Mobile Work Orders View 2 - Preferred / Nice to Have

68.0

The system must provide Reporting, and Analytics (i.e. Performance Reporting, Asset Reporting, Lifecycle cost tracking (TCO), Total Cost of Ownership (TCO) / cost to maintain the asset to include cost of associated parts)

OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

69.0 Application is to have the ability to support both a paperless and paper when applicable by the user. (i.e. workorder output/print or share details via work order link)

OC Streetcar Functional Security & Administration User Management Print/Output 1 - Required

70.0 Ability to assign workorders to a resource (i.e. mechanic) OC Streetcar Functional Maintenance Management Planned Maintenance Edit 1 - Required

71.0 Application to support search capabilities using filters and or key words. OC Streetcar Functional Document Management Document Library Search 1 - Required

72.0 As a user, I want to search for components using partial text within the component description, so that I can quickly locate items even when I do not know the exact part number or full description.

OC Streetcar Functional Security & Administration User Management Search 1 - Required

73.0 The system shall support partial (“contains”) search on component descriptions. OC Streetcar Functional Maintenance Management Planned Maintenance Search 1 - Required

74.0 The system shall support searching by keywords across description fields (e.g., component description, manufacturer, model, part number where available).

OC Streetcar Functional Document Management Document Library Search 1 - Required

75.0 The system shall return relevant matches with key fields displayed (e.g., Part Number, Description, Category, Status, Location if applicable). OC Streetcar Functional Maintenance Management Planned Maintenance View 1 - Required

76.0 The system shall allow filtering and sorting of results (e.g., by category, asset type, availability/status). OC Streetcar Functional Asset Management Asset Setup Search 1 - Required

77.0 As a user, I want to search by part number, work order number, and assigned individual so that I can quickly locate records. OC Streetcar Functional Security & Administration User Management Edit 1 - Required

77.1 The system shall provide multi-criteria search functionality. OC Streetcar Functional Maintenance Management Planned Maintenance Search 1 - Required

Printed on: 3/24/2026 at 12:29 PM Page 5 of 21 A2 Functional

ATTACHMENT A

INFORMATION PROVIDED BY OCTA TO BE UPDATED BY THE PROPOSER / VENDOR

System Requirement Business Area Type Process Category Process Type Task/Action OCTA's Priority Proposed Solution's Capability

Method to Implement

Software Customization Cost

3rd Party Software Cost Comments Assumptions

78.0 Application will have the ability to support multiple attachments to a record (i.e. Workorders) OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

79.0 As an administrator, I want to assign role-based access by business line so that users access only relevant data. OC Streetcar Functional Security & Administration User Management Edit 1 - Required

79.1 The system shall enforce role-based access control (RBAC) by organizational category. OC Streetcar Functional Security & Administration User Management Access 1 - Required

80.0 The system must provide the ability to trace historical movement material consumption ( i.e. workorders, warranty defects) OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

81.0 The system must provide the ability to trace historical inventory movement (i.e. equipment / parts between location, bin, shelf) OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

82.0 These new digital inspection forms and work order forms shall retain all language, fields and options on the paper-based forms as designed by both OCTA and 3rd Party contractor.

OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

83.0 As a user, I want submitted inspection forms stored in the system so that inspection records are retained and reportable. OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

83.1 The system shall store inspection form data in a centralized database. OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

84.0 The system shall store inventory records in the database. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

85.0 The system shall store material/part records in the database. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

86.0 The system shall allow administrators to create users and assign roles. OC Streetcar Functional Security & Administration User Management Create 1 - Required

87.0 User will have the ability to view work orders and respective attachments (i.e. inspection checklist) on mobile devices. OC Streetcar Functional Mobile Functionality Mobile Work Orders View 1 - Required

88.0 As a user, I want to view only my assigned work orders and inspections. OC Streetcar Functional Inspection Management Digital Inspections View 1 - Required

88.1 The system shall restrict desktop and mobile views to records assigned to the authenticated user. OC Streetcar Functional Mobile Functionality Mobile Work Orders View 1 - Required

89.0 As a user, I want to edit only my assigned work orders and inspections. OC Streetcar Functional Inspection Management Digital Inspections Edit 1 - Required

89.1 The system shall support desktop and mobile edits to records assigned to the authenticated user. OC Streetcar Functional Mobile Functionality Mobile Work Orders Edit 1 - Required

90.0 The system shall have the ability to store estimated maintenance labor time. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

91.0 The system shall have the ability to store actual maintenance labor time. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

92.0 The system shall have the ability to report on labor time actual verse estimate labor time. OC Streetcar Functional Reporting & Analytics Custom Reports Assign/Select 1 - Required

93.0 Vendor will assess current environment, identify gaps in current set up to support OCStreetcar/Wayside day to day operations. OC Streetcar Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

94.0 As a user, I want the vendor to provide documented recommendations for identified gaps so that operational needs are fully addressed. OC Streetcar Functional Document Management Document Library Create 1 - Required

94.1 The vendor shall document functional gaps and proposed remediation strategies. OC Streetcar Functional Document Management Document Library Assign/Select 1 - Required

95.0 As a user, I will have the ability to manually create asset records and define the asset number (e.g., Car Number). OC Streetcar Functional Security & Administration User Management Create 1 - Required

95.1 The system shall allow users to manually create asset records and define the asset number (e.g., Car Number). OC Streetcar Functional Security & Administration User Management Create 1 - Required

96.0 As a user, I will have the ability update an asset item with read only on the asset number (e.g., Car Number) and not editable after creation. OC Streetcar Functional Security & Administration User Management Edit 1 - Required

96.1 The system shall allow users to update asset records; however, the asset number (e.g., Car Number) shall be read-only and not editable after creation.

OC Streetcar Functional Security & Administration User Management Edit 1 - Required

97.0 As a user, I want to categorize assets by defined asset types (e.g., Car, Wayside), so that assets can be organized, managed, filtered, and reported by business classification.

OC Streetcar Functional Reporting & Analytics Custom Reports Search 1 - Required

97.1 The system shall support configurable asset categories and subcategories (e.g., Car, Wayside). OC Streetcar Functional Asset Management Asset Setup Assign/Select 1 - Required

97.2 The system shall allow assets to be assigned to one or more defined categories. OC Streetcar Functional Asset Management Asset Setup Edit 1 - Required

97.3 Asset category values shall be available for filtering, reporting, and role-based access control. OC Streetcar Functional Reporting & Analytics Custom Reports Search 1 - Required

97.4 Asset categorization shall be configurable without requiring system code changes and shall support future expansion of categories. OC Streetcar Functional Asset Management Asset Setup Assign/Select 1 - Required

98.0 Ability to assign asset to a location (i.e. maybe a building, crossing gate or rail) OC Streetcar Functional Asset Management Asset Setup Edit 1 - Required

99.0 Application will have the ability to create new roles that align with the Hexagon environment for 3rd party contractor. OC Streetcar Functional Security & Administration User Management Create 1 - Required

100.0 As a system administrator, I want to modify user permissions so that access aligns with job responsibilities. OC Streetcar Functional Security & Administration User Management Edit 1 - Required

100.1 The system shall allow administrators to update user roles and permissions (read, write, report access). OC Streetcar Functional Reporting & Analytics Custom Reports Edit 1 - Required

101.0 Create New Users for both OCTA and Non-OCTA domain users to specific roles assignment. (i.e. Herzog@htsi.com, twright@octa.net) OC Streetcar Functional Security & Administration User Management Create 1 - Required

102.0 Ability to apply filters to display work order history with drill in capabilities (i.e. creation date, user name, updates, transaction details). OC Streetcar Functional Security & Administration User Management Edit 1 - Required

103.0 Ability to monitor work order state via user interface (i.e. Open, Closed, Pending review) through workflow notifications. OC Streetcar Functional Security & Administration User Management View 1 - Required

104.0 Ability to report on work order state. (i.e. Open, Closed, Pending review) OC Streetcar Functional Reporting & Analytics Custom Reports View 1 - Required

105.0 Ability to create on demand reporting with user defined filter criteria. OC Streetcar Functional Reporting & Analytics Custom Reports Create 1 - Required

106.0 Application will support the functionality to save reports using naming convention defined by end user. OC Streetcar Functional Reporting & Analytics Custom Reports Assign/Select 1 - Required

107.0 Application will support the functionality to copy canned reports, modify and save report using naming convention defined by end user. OC Streetcar Functional Reporting & Analytics Custom Reports Edit 2 - Preferred / Nice to Have

108.0 As a report creator, I want to designate reports as private or published and share them via email so that stakeholders receive required information. OC Streetcar Functional Reporting & Analytics Custom Reports E-mail 2 - Preferred / Nice to Have

108.1 The system shall allow reports to be marked private or published and distributed via email. OC Streetcar Functional Reporting & Analytics Custom Reports E-mail 1 - Required

Printed on: 3/24/2026 at 12:29 PM Page 6 of 21 A2 Functional

ATTACHMENT A

INFORMATION PROVIDED BY OCTA TO BE UPDATED BY THE PROPOSER / VENDOR

System Requirement Business Area Type Process Category Process Type Task/Action OCTA's Priority Proposed Solution's Capability

Method to Implement

Software Customization Cost

3rd Party Software Cost Comments Assumptions

109.0 As a user, I want to schedule recurring reports so that reports are automatically delivered. OC Streetcar Functional Reporting & Analytics Custom Reports Schedule 1 - Required

109.1 The system shall support scheduled recurring report generation and email distribution. OC Streetcar Functional Reporting & Analytics Custom Reports Schedule 1 - Required

110.0 As an administrator, I want to assign report-level permissions so that report access aligns with defined roles that align with the streetcar business unit for both OCTA and our 3rd Party partner.

OC Streetcar Functional Reporting & Analytics Custom Reports Edit 1 - Required

110.1 The system shall support granular report permissions (Read, Modify Criteria, Delete). OC Streetcar Functional Reporting & Analytics Custom Reports Edit 1 - Required

111.0 Ability to issue parts against a specific work order, decrementing on hand inventory. (i.e. allocating parts to be assigned to a specific workorder) OC Streetcar Functional Inventory Management Inventory Control Edit 1 - Required

112.0 Application will have the ability to create a blanket purchase requests. OC Streetcar Functional Procurement Requisition Create 1 - Required

113.0 As a user, I want to generate purchase requests when inventory reaches minimum thresholds so that stock levels remain sufficient. OC Streetcar Functional Inventory Management Inventory Control Create 1 - Required

113.1 The system shall support min/max inventory thresholds and purchase request generation. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

114.0 Application will have the ability to view purchase orders converted from purchase requisitions, that is associated to a it's respective workorder. OC Streetcar Functional Procurement Requisition View 1 - Required

115.0 Application will have the ability to receive assets from purchase orders incrementing inventory. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

116.0 As a user, I want to adjust inventory quantities (+/-) based on authorization so that records remain accurate. OC Streetcar Functional Inventory Management Inventory Control Edit 1 - Required

116.1 The system shall allow role-restricted inventory quantity adjustments. OC Streetcar Functional Inventory Management Inventory Control Edit 1 - Required

117.0 As an user, I want to move inventory between statuses so that materials are accurately tracked. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

117.1 The system shall support inventory movement between locations and statuses. OC Streetcar Functional Inventory Management Inventory Control Assign/Select 1 - Required

118.0

Ability to export maintenance history report for specific assets (i.e. Car, Wayside ), filters defined by user. Output details such as but not limited to;

-Asset number -Work No -Inspector -Parts used if repair was made (i.e. Part No. Lot, VIN No.)

-Part Qty -Part Cost -Inspected area -Inspector results -Inspector comments -Inspector recommendations -Date of Inspection -Maintenance type (i.e. Planned or Reported issue) -Manager Approval Sign off Name -Sign Off Date -Next inspection date -Actual Labor hours *Note will also include federal mandated safety inspection details

OC Streetcar Functional Reporting & Analytics Custom Reports Search 1 - Required

119.0

Application to support Federal Mandated Safety inspections for assets through reporting from digital inspection lists for the following (examples):

Wayside- Rail -Wishbone crossing gate -Track Class -Track Structure -Rails -Crossties -Special track work (turnouts, bridge lift assemblies), -Tie plates, and -Rail fastening systems -Track Geometry -Track gage -Alignment -Elevation -Curvature -Track surface -Road Bed:

-Ballast -Track Inspection -Frequency and -Quality of a railroad’s inspection -Special inspections

OC Streetcar Functional Inspection Management Digital Inspections Assign/Select 1 - Required

121.0 As the user, I must log all inventory adjustments with complete audit details so that traceability is maintained. OC Streetcar Functional Procurement Requisition Data Exchange 1 - Required

122.0 System shall log all inventory adjustments for audit compliance and traceability. OC Streetcar Functional Procurement Requisition Data Exchange 1 - Required

122.1 The system shall support secure integration leveraging Phase 1 integrations. OC Streetcar Functional Security & Administration User Management Access 1 - Required

Printed on: 3/24/2026 at 12:29 PM Page 7 of 21 A2 Functional

ATTACHMENT A

INFORMATION PROVIDED BY OCTA TO BE UPDATED BY THE PROPOSER / VENDOR

ID System Requirement Business Area Type Process Category Process Type Task/Action OCTA's Priority Proposed Solution's Capability

Method to Implement

Software Customization Cost

3rd Party Software Cost Comments

NF 1.0

The system shall maintain a complete and traceable audit log within the CFR Contractor environment for all necessary inventory field changes, including user identification, timestamp, previous value, and new value.

Contracted Fixed Route (CFR) Non-Functional Security & Administration User Management Edit 1 - Required

NF 1.1 Deliver hands on training for configured roles/user. Contracted Fixed Route (CFR) Non-Functional Security & Administration User Management Assign/Select 1 - Required NF 1.2 Deliver written training for applications modules. Contracted Fixed Route (CFR) Non-Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

NF 1.3 Deliver technical documentation detailing configuration, integration and design details. Contracted Fixed Route (CFR) Non-Functional Integration Phase 1 Integrations Data Exchange 1 - Required

NF 1.4 Vendor will update the BDD documentation. Contracted Fixed Route (CFR) Non-Functional Document Management Document Library Edit 1 - Required NF 1.5 Vendor will update the ICD documentation, Contracted Fixed Route (CFR) Non-Functional Document Management Document Library Edit 1 - Required

NF 1.6

NF 1.7 Update Configuration Matrix. Contracted Fixed Route (CFR) Non-Functional Maintenance Management Planned Maintenance Edit 1 - Required

NF 1.8 Vendor will participate in unit testing for all interfaces including both enabled and disabled interfaces. Contracted Fixed Route (CFR) Non-Functional Maintenance Management Planned Maintenance Data Exchange 1 - Required

NF 1.9 Completed inspection data shall be audit logged and retained per records retention policy defined by OCTA 7 years. OC Streetcar Non-Functional Inspection Management Digital Inspections Assign/Select 1 - Required

NF 1.10 The system shall provide secure mobile access (phone and tablet) to authorized users. OC Streetcar Non-Functional Mobile Functionality Mobile Work Orders Access 1 - Required

NF 1.11 Mobile access shall require secure authentication (e.g., SSO and/or MFA if required). OC Streetcar/Mobile Non-Functional Mobile Functionality Mobile Work Orders Access 1 - Required

NF 1.12

The system shall maintain a complete audit trail for all transactions, recording user identification, date and time stamp, and a description of the action performed to ensure traceability and accountability.

OC Streetcar/Mobile Non-Functional Security & Administration User Management Assign/Select 1 - Required

NF 1.13 Mobile functionality shall align with enterprise uptime requirements. OC Streetcar/Mobile Non-Functional Mobile Functionality Mobile Work Orders Create 1 - Required

NF 1.14

Where offline functionality is enabled, the system shall securely store transactions performed during offline operation and automatically synchronize them with the central system upon network reconnection, preserving data integrity and audit history.

OC Streetcar/Mobile Non-Functional Mobile Functionality Mobile Work Orders Assign/Select 1 - Required

NF 1.15 Changes to forms should be simple configuration changes, not software customizations. OC Streetcar Non-Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

NF 1.16

Configure Hierarchy for location(s) that conforms to the current hierarchal structure, which separates OCStreetcar/Wayside/Linear from the other lines of business such as MSF and CFR currently configured in Hexagon for Phase 1.

OC Streetcar Non-Functional Maintenance Management Planned Maintenance Assign/Select 1 - Required

NF 1.17 Ability to export work order history from application in multiple formats.

(i.e. pdf). OC Streetcar Non-Functional Reporting & Analytics Custom Reports Print/Output 1 - Required

NF 1.18

The system shall maintain a complete and auditable record of all inventory adjustments. The audit record shall capture, at a minimum:

user identification, date and time of adjustment part number, part description, quantity adjusted, previous balance, updated balance, and inventory location, to ensure full traceability and accountability.

OC Streetcar Non-Functional Inventory Management Inventory Control Edit 1 - Required

Printed on: 3/24/2026 at 12:29 PM Page 8 of 21 A2 Non-Functional

ATTACHMENT A

A3. VENDOR QUESTIONNAIRE

Category Questionnaire Response

Where is our data stored?

What encryption methods are employed for data transmission and storage?

Do you have backup recovery procedures in place? Yes, describe

Do you have disaster recovery procedures in place? Yes, describe

Do you have cybersecurity insurance? Yes, describe coverage

Does your cybersecurity insurance coverage include customers?

Describe your user authentication and authorization processes.

How often are access controls reviewed?

How often are access controls updated?

How do you control access to our data?

Do you have a Cyber Incident Response Plan?

Is your Cyber Incident Response Plan regularly tested? Yes, describe

What is the notification timeline to Client/Customers in the event of a data breach?

Do you meet any major compliance standards (e.g., ISO 27001, SOC 2)?

How do you ensure compliance with relevant data protection laws and regulations?

Do you have an annual compliance report? If so, can you please provide it?

Describe the security measures implemented in your physical and network infrastructure.

Physical Security Measures:

Access control systems such as biometric scanners, smart cards, and key fobs

Security cameras and surveillance systems to monitor the premises

Intrusion detection systems to detect unauthorized access

Regular maintenance and inspection of the infrastructure to identify and fix vulnerabilities

Network Security Measures:

Firewall systems to prevent unauthorized access to the network

Intrusion detection and prevention systems to detect and block malicious traffic

Encryption technologies to protect sensitive data

Regular software updates and patching to fix security vulnerabilities Access control mechanisms such as passwords, multi-factor authentication, and role-based access control?

Network segmentation to isolate sensitive data and limit the impact of security breaches

How do you protect against DDoS attacks and other network threats?

Employee Training How do you educate/train your employees about cybersecurity awareness and best practices?

Do you use third-party vendors? If yes, how do you ensure their security practices align with yours?

Can you provide a list of third-party vendors involved in our services?

Do you contract with any offshore third-party vendors?

What secure coding practices do you follow during software development?

How do you address vulnerabilities and apply patches to your software?

General Performance Assessment

What are the key performance indicators (KPIs) for this application?

How does the system perform under normal operating conditions?

Are there any performance benchmarks for comparison?

System Resource Utilization

How much CPU, memory, and disk I/O does the application consume?

Are there any memory leaks or high CPU usage spikes?

Does the system utilize multiple cores efficiently?

Response Time & Latency

What is the average response time for critical operations?

Are there noticeable delays in specific processes?

How does the application handle real-time requests?

User interface to menu selections average response time?

Log in response average response time?

Log off average response time?

Record Save average response time?

Software Development Security

Data Protection

Access Control

Incident Response

Compliance and Certification

Infrastructure Security

Third-Party Security

ATTACHMENT A

Simple Report query report average response time?

Complex Report query report average response time?

Print request average response time?

Dashboard refresh average response times?

Batch Processing average response time? (if applicable)

Scalability & Load Handling

How does the system perform under peak load conditions?

What is the maximum number of concurrent users the system can support?

Does the system scale horizontally or vertically?

Network Performance

What is the average network latency for data transmission?

Are there any network bottlenecks affecting performance?

Is data compression used to optimize network usage?

Application Architecture

Is the software designed using microservices or a monolithic approach?

How is caching implemented to improve performance?

Are third-party integrations affecting system speed?

Error Handling & System Logs

Are there recurring errors or performance-related logs?

How are exceptions and failures handled in the system?

What monitoring tools are used to track errors and warnings?

Security & Performance Trade-offs

Are there security measures that impact performance (e.g., encryption, authentication)?

How does the system handle secure transactions without sacrificing speed?

Are there any performance concerns with API rate limiting?

Optimization & Future Improvements

Are there performance testing tools in place (e.g., JMeter, LoadRunner)?

How frequently is the application updated for performance enhancements?

Application Response

ATTACHMENT A

PROJECT IMPLEMENTATION TASKS AND DELIVERABLES Vendor Response (Y, N, E)

If Vendor Response is "E", please provide what the firm can or cannot do in detail.

Task 1 - Project Planning & Management Project Schedule Cost Roles and Responsibilities Matrix Change Orders Issues, Risks, Action Items, Bugs, Future Enhancements Log (aka Item Log).

Project Status Reports Overall Project Status Trend Tasks Completed, Tasks in progress Next Steps Resources Project Issues Short Term Risks Long Terms Risks Kick Off and Ongoing Meetings Meeting Agendas Meeting Minutes Ancillary Project Deliverables Documentation and Deliverables Task 2 - Requirements Gathering Requirements Documentation Design Review Conceptual Design Review Preliminary Design Review Final Design Review Conceptual Design Review System Documentation Task 3 - Design Design Documentation (all phases) Back-up and Recovery Plan Systems Integration Design…