9-816192-Ex-F-Solar Power Monitoiring-Requirements Traceability Matrix 8 4 2026.xlsx

Drop Downs

Instructions This matrix contains the following Appendices. Some Appendices require a response, while others are for reference purposes to help proposers prepare a response.

1. General Requirements - For each Compliance Term, select "C-Comply," "N-Cannot Comply," or "A-Will Comply with Alternative." If "N" or "A" are selected, comments are required; however, CapMetro strongly recommends that comments be added for each item.

2. Appendix A: Core Requirements RTM - Please provide a response to each item. Additional instructions are provided within the Appendix.

3. Appendix B: Project Phase Requirements - For reference/informational purposes

4. Appendix C: Technical Questions - Please provide a response to each item. Additional instructions are provided within the Appendix.

5. Appendix C2: Technical Questions - Please provide a response to each item. Additional instructions are provided within the Appendix.

6. Appendix D: Integrations - For reference/informational purposes

7. Appendix F: Definitions - For reference/informational purposes

Additional Instructions:

1. The Contractor must deliver a system encompassing all hardware (if needed), software, license, and service requirements, including the delivery of third-party products to make the solution fully functional.

2. The requirements in the Scope of Work and Compliance Matrix are functional in nature and do not encompass all requirements. The Contractor shall determine the technical modifications needed to carry out the intent herein. Vendor shall document and discuss said needs with CapMetro and implement the agreed-upon solution accordingly.

3. The vendor must deliver all Compliance Terms unless it is within a section marked "Optional" that is not exercised by CapMetro or CapMetro agrees to an alternative.

INSTRUCTIONS EXHIBIT F - COMPLIANCE MATRIX AND SCOPE OF WORK

RFP 816192 &P OF &N

Template Definitions CapMetro - Requirement Traceability Matrix (RTM) Definitions

PURPOSE: To define each of the columns in the Requirements Traceability Matrix (Master Requirements Listing tab)

a. Required – required functionality.

b. Key – provides significant benefit to the business. c. Desired – provides important benefit to the business.

d. Optional – would enhance the product and provide benefit.

TEMPLATE DEFINITIONS EXHIBIT F - COMPLIANCE MATRIX AND SCOPE OF WORK

RFP 816192 &P OF &N

1. General Requirements

• Organization chart identifying key project personnel and contact information.

• Master schedule, identifying key project milestones and activities in Microsoft Projects format.

• Schedule for all project design and development elements that require CapMetro approval.

• Project meetings and schedule for recurring meetings.

• Methodology to control project schedule, scope, cost, and risk.

• Risk management plan and risk register, including identified project risks and actions required to mitigate them.

• Transition and change management processes and procedures.

• Quality assurance processes and procedures to confirm that the requirements of the contract are being met.

• Subcontractor management and communications.

• Document naming conventions and Action Items and Issues List (AIL) control processes and procedures, including version and traceability controls.

• Change management plan and procedures for all deliverables and subsequent revisions.

• Cost management.

• Communication Plan.

13.2 CapMetro may grant Final System Acceptance only when:

• The SAT has been successfully completed and approved by CapMetro.

• All system modules, interfaces, and integrations are delivered, installed, and operational.

• All back-office applications and software, including all required reports, are installed and fully functional.

• All requisite contract deliverables have been delivered to CapMetro and accepted.

• The Disaster Recovery Plan has been successfully demonstrated and approved by CapMetro.

• All required training has been provided and accepted by CapMetro.

• All required intellectual property has been delivered to CapMetro or the escrow agent.

• Final resolutions to all identified critical issues (as classified by the Test Failure Log Review Board) are fully implemented and accepted by CapMetro.

CapMetro will issue written certification upon approval of Contractor's request for Final System Acceptance.

• Utilization of all financial and procurement modules

• Utilization of all optional modules exercised by CapMetro, as applicable

• Back-office system administration, configuration, operations and maintenance, reporting, backup, and disaster recovery.

• Reporting, including ad hoc report creation, canned report generation, and report utility

1. System Name

2. System roles

3. User information

Contractor shall ensure compliance of all equipment and system interfaces and create an Accessibility Compliance Plan to document compliance. This plan will be used throughout design and implementation to ascertain that all accessibility and ADA requirements will be met and to track compliance.

20.2 COMPLIES WITH WCAG 2.0 AA ACCESSIBILITY STANDARDS AND MEETS ALL FOUR SUCCESS CRITERIA.:

- All screens are compatible with assistive technologies including screen readers and screen magnification

- Screens make proper use of forms mode, include alt tags on all data collection boxes and image fields, and metadata read back is strictly limited.

- Properly labelled images and proper use of alt tags is required.

- The ability to navigate pages, utilize functionality and traverse layouts without a mouse is required.

- Users of assistive technology shall have ways to skip redundant navigation.

- Correct headings and labelling structures for pages, forms and data tables.

- Readable content with sufficient contrast ratios and font sizing.

- Contractor shall provide information about user testing with people with disabilities and the results of such testing.

- Software solution shall be compatible will all applicable standards and/regulations regarding accessible information technology resources and (IRIT). In cases where there is conflict between standards the most stringent standard shall be applicable.

• Presents no safety hazards for customers and CapMetro employees.

• Will withstand the rigors of the environments in which the equipment will be installed, and the public use to which it will be subjected.

• Provides for the secure storage and transmittal of data.

• Is designed using state-of-the-art methods to maximize quality.

• Satisfies federal, state, and other requirements for ergonomics and usability.

Applicable codes, laws, ordinances, statutes, standards, rules, and regulations include, but are not be limited to the list below (in 3.1.4-2). The latest revisions in effect at the time of Final System Acceptance will apply.

21.2 • Americans with Disabilities Act (ADA)

• Americans with Disabilities Act Accessibility Guidelines (ADAAG)

• Advanced Encryption Standard

• ANSI X9.24, Financial Services Retail Key Management

• European Norm EN55022, Emissions standards for CE marking

• European Norm EN55024, Immunity standards for CE marking

• FCC Part 15 Class B – Radio Frequency Devices

• FIPS 140-2

• IEEE 802.11 a/b/g/n standard for wireless data communications

• IEEE 802.11 i standard for wireless data network security

• IEEE 802.11-2016

• International Electrotechnical Commission Standard 529 (IEC529)

• ISO/IEC 7810, Identification Cards – Physical Characteristics

• ISO 9001

• ISO/IEC‑8583 – Financial transaction card originated messages

• ISO/IEC 14443 Parts 1 through 4 – Contactless Smart Card Standard

• ISO/IEC 18092 / ECMA-340, Near Field Communication Interface and Protocol-1

• ISO/IEC 21481 / ECMA-352, Near Field Communication Interface and Protocol-2

• National Electrical Code (NFPA 70)

• National Electrical Manufacturers Association Publication 250-2003

• National Electrical Safety Code (ANSI C2)

• National Fire Protection Association (NFPA) 130

• NCITS 322-2002, American National Standard for Information Technology – Card Durability Test Methods

• Occupational Safety and Health Administration (OSHA)

• Payment Card Industry Data Security Standards (PCI-DSS)

• Payment Card Industry Payment Application Data Security Standards (PA-DSS)

• Society of Automotive Engineers SAE J1113-13 Electrostatic Discharge

• Society of Automotive Engineers SAE J1455 Vibration and Shock

• UL Standard 60950, “Information Technology Equipment – Safety”

• World Wide Web Consortium, Mobile Web Application Best Practices

• Web Content Accessibility Guidelines WCAG 2.0

back-office availability will be calculated based on the total out of service time for the associated system:

Back-office application availability = 1 - (out of service time / total operating time)

Total Operating Time is defined as the number of minutes in a day (1440) multiplied by the number of days in the month of measurement, while Out of Service Time is defined as all time during which the System is not in a fully operational state, and includes all time necessary to respond and repair to issues. Scheduled maintenance time is excluded from the calculation.

The availability requirement for each System back-office application is as follows: Application availability must meet or exceed 99.99% each calendar month

24.2 Back-office accuracy shall be based on the number of incidents where a device or Back-office generated transaction is recorded incorrectly within the associated system. Performance will only be measured for those applications for which Contractor is responsible. The accuracy requirements for the System Back-office applications are as follows:

Financial Management application: No more than 2 incidents of inaccurate reporting per calendar month.

Contractor agrees that onsite field engineerings support and onsite prescence may be required by CapMetro at any time during the term of the contract.

24x7x365 - Tech support within 15 minutes of contact

Severity Level 1 - One or more CapMetro department's ability to perform mission critical business functions is in jeopardy because the system is not available. All Severity Level 1 issues will be responded to within 15 minutes of contact and a Mean Time to Resolution (MTTR) of 4 hours or less. These outages will be escalated to the contractor's Account Manager if issues are not resolved within 4 hours, the Chief Techincal Office if not resolved within 8 hours, and the President/CEO if not resolved within 12 hours of down time.

Severity Level 2 - One or more CapMetro department's ability to perform mission critical business functions is in jeopardy because the system is not available, but a workaround can be established within a reasonable time. All Severity Level 2 issues will be responded to within 15 minutes and a Mean Time to Resolution (MTTR) of 8 hours or less. These outages will be escalated to the contractor's Account Manager if issues are not resolved within 8 hours, the Chief Techincal Officer if not resolved within 16 hours, and the President/CEO if not resolved within 24 hours of down time.

GENERAL REQUIREMENTS EXHIBIT F - COMPLIANCE MATRIX AND SCOPE OF WORK

RFP 816192 &P OF &N

2. Appendix A - Core Reqs. RTM

CapMetro connects people, jobs and communities by providing Central Texans with safe, high-quality and sustainable transportation alternatives. The agency provides 30 million rides annually on its buses, trains, paratransit and vanpool vehicles and serves a population of more than 1.2 million in its 543-square-mile service area. The region’s transportation leader, CapMetro has invested in transit services like its High-Frequency Network, which move more people, more reliably, as well as its innovative on-demand service Pickup. CapMetro is committed to increasing regional mobility and, through Project Connect, will transform how people travel throughout Central Texas. Visit capmetro.org for more information.

The currently equipped bus stops (49 total) have installed a solar power system to provide lighting and infomation signage at stop locations.

1.2 Solar Power at CapMetro Bus Stops Vision. CapMetro seeks to establish remote monitoring of the Solar Power systems currently installed at 49 locations and to be prepared for expansion. The Solar Monitoring System (Monitoring System) provided as a demo proved valuable in providing operational data to show impact in various weather conditions. This knowledge provides design information that may be needed for upgrades and expansion. Data also provided value where power could be sent back to the grid, lowering CapMetro operating costs.

The goal is to continue to support the existing system that is cost-effective to maintain following prime objectives - Full system monitoring that includes:

•Login access via SSO •Ability to access current hardware without modification to existing systems.

• Diagnostic trends to improve current and future installations

• Analytics to establish performance •System Health •Load Impact from powered systems, lights, monitors...

• Remote access to individual power stations •Automated controls to monitor and manage battery life to ensure continuous operation

Provide KPIs: system availability (% of period in normal operation), average daily solar vs. load ratio, BPM event frequency and recovery time, and overall health classification.

accomplished by a single technician under regular circumstances.

4.2 Generate error logs and reports that will facilitate predictive maintenance; rapid and accurate root cause analysis for efficient resolution; logs shall be available remotely, through the backend, and exportable to PDF, CSV and Excel. At a minimum, error logs shall contain error number, date, time, severity code, error description, unique Solar System identifier, location

notifications via email for the Solar solution; remote monitoring shall include "condition based monitoring" of equipment such as internal temperature, amp draw, and other parameters that can be used to determine when maintenance is needed; notifications shall be configurable so that various alerts can be sent to specific individuals

5.0 Training - Minimum Requirements; in the Comment column

indicate for each training the areas to be covered:

maintenance, repair, component change-out, and scheduled maintenance of Solar Monitoring system and hardware

plan and processes to include recommended spare parts inventory, 24x7x365 phone, email and incident management response, including all time necessary for the support of software, solar equipment for all stations, and test units including:

•Repair Services (beyond RMA) •Software Updates •Test Use Cases •Test Environment •Documentation •On-Site and Field Support as required

6.2 Parts must be readily available with minimal lead times; in the Comments section describe the parts availability and maximum lead times to receive.

6.3 Contractor shall replace any part that becomes obsolete

during the life with one that functions at an equivalent level and maintains parts availability and maximum lead time guarantee

6.4 Provide Service Level Agreement (SLA) to include incident priority, escalation process, hourly rates for additional services (e.g. future training)

7.0 Other Provisions: Contractual or IT Security Provisions of Cap Metro.

technician(s) and all support to meet the SLAs and provisions in the WMA.

8.1 Contractor will provide the requirements of Cap Metro

providing field technician(s) and first-line software support (perform diagnostics and troubleshooting) to include recommendation of number of full-time equivalent employees (FTE) to support. Describe fully in the Comments column.

8.2 Cap Metro will provide field technician(s) to perform

preventative maintenance and Return Merchandise Authorization (RMA) repairs (replacing components)

8.3 Cap Metro will investigate presenting software issues and submit tickets to Contractor that Contractor shall resolve

APPENDIX A - CORE REQUIREMENTS EXHIBIT F - COMPLIANCE MATRIX AND SCOPE OF WORK

RFP 816192 &P OF &N

Feedback On Reqs Name of Reviewer Date of Review Process Level 0

staff have, so when they terminate them, they just shotgun a request to have every application removed even if the person

processed in the correct order. We often receive the new account requests before the old ones which causes confusion

3.Appendix B - Proj. Phase Req.

1. Project organization chart

2. Project schedule and Project Management Plan - (draft)

3. Action Items and Issues log (AIL)

4. Project Decisions Log

5. Project Review Documents (PRDs) for project decisions

6. Initial Risk Register

7. System Implementation Plan (draft)

8. Scope and Compliance Matrix Review and Update

2.0 Design. Contractor's configuration and implementation approach based on CapMetro's previously gathered requirements. This phase will determine how the system will be installed, product wireframe presentation to the customer, and how it will be managed in the back end. Contractor will work with CapMetro to develop materials that will provide a basis to help instruct CapMetro stakeholders in the easiest and most efficient way to use the system to their utmost advantage. Design Deliverables:

. 1. Configuration Management Document (“CMD” - Draft)

2. Solution Design Documents / MVP Lists (If Hybrid Agile Approach)

3. Application Landscape Design Document

4. Integration Design Plan

5. System Implementation Plan (Final) / Sprint Plan (If Hybrid Agile Approach)

6. Data Migration Plan (Draft)

7. Disaster Recovery Plan (Draft)

8. Quality Assurance Plan (Draft)

9. Risk Management Plan (Final)

10. Data dictionary and Entity Relationship Diagram (ERD)

11. Project Schedule (Baseline) with Resource Loading

12. Network architecture diagram (Draft)

13. Perform Preliminary Design Review (PDR) Design and System Implementation Plan with Stakeholders

14. Create Final Design based on review and perform Final Design Review (FDR)

15. Review and Acceptance of Final Design and Project Management Plan

16. Scope and Compliance Matrix Review and Update

3.0 Develop. Development, configuration and installation of the solution and integration as well as installation within a development and a test environment so configuration and testing of the required functionality can be started. This task will include setting the initial configuration values by Contractor so they can be tested and changed if needed. During this phase, the rollout of the system must be worked on to include training all IT and Operational staff who will use or have on-going support roles. Develop Deliverables:

1. Quality Assurance Plan Including QA/QC Checklist (Final)

2. Development of modules, application and interfaces

3. Develop and Design Review Sessions per Sprint (If Hybrid Agile)

4. Retrospective sessions on prior development (If Hybrid Agile)

5. Test Environment Installation that provides CapMetro full access throughout the project and the life of the system

6. Supporting Infrastructure Implemented as applicable

7. Test Procedure/Plan including test Scripts, use cases, acceptance test criteria demonstrating each Compliance Matrix term is developed and meets requirement (Draft)

8. Update Compliance Matrix with Test Number(s)

9. High-level Training of CapMetro Staff to Prepare for Test Phase

10. Contractor Warranty and Maintenance Plan Review

11. Review and Feedback of CapMetro Support Responsibility Matrix

12. Role-based, On-site Training Plan for all User Types (Draft):

•Training schedule and course outlines for review a minimum of three weeks prior to the scheduled classes •Separate training sessions based on functional and technical area •Provide all materials necessary to train participants (CapMetro will provide space and laptops) •Schedule the training staff to be on site timely to ensure equipment, materials, student accounts and classroom are fully ready for when class begins •Arrange for an instructor(s) with thorough knowledge of the material covered in the course(s) and the ability to effectively lead the knowledge transfer •Provide customized training manuals specific to CapMetro's environment in Microsoft Word and PDF. Contractor shall provide the agreed-to number of hard copies

4.0 Test. Contractor shall develop and implement a comprehensive program to test all components and applications that comprise the integrated Contractor ERP solution. Testing is to be performed in five distinct and separate phases:

1. Functional Unit Test (FUT)

2. System Integration Test (SIT)

3. End to End Test (EET)

4. Pilot Test (Day in the Life)

5. System Acceptance Test (SAT) The testing phase shall not be deemed completed until all functional requirements have been fully tested and approved by CapMetro. Contractor shall develop an ERP Test Plan that includes the number and range of tests, detailed schedule indicating the sequence of each test, and when and where each test will take place. Contractor shall not perform any test until the corresponding test plan and procedures have been approved by CapMetro. Contractor shall develop Test Procedure documents with test scripts, all anticipated use cases and acceptance criteria for review and approval by CapMetro for each phase of testing. Test deliverables:

1. Test Plan (including automated testing processes)

2. Test Procedures (including automated testing processes)

3. System Acceptance Test Plan and Execution

4. Execution of FUT, SIT, EET, Day in the Life and System Acceptance Testing

5. Security Penetration Test (performed as part of SAT)

6. Disaster Recovery Test - End-to-End

7. Volume and Stress…