MILWAUKEE TRANSPORT SERVI ES · During the Contract, the successful Bidder/Proposer and all subcontractors will use the County’s online reporting system B2G to document DBE participation

MILWAUKEE TRANSPORT SERVICES 1942 NORTH 17TH STREET MILWAUKEE, WI 53205

(website: www.ridemcts.com) [email protected]

REQUEST FOR PROPOSAL NO: MM-06-20

DATE: June 26, 2020

Milwaukee Transport Services, Inc., (MTS), operator of the Milwaukee County Transit System (MCTS) is seeking proposals from experienced, qualified contractors to provide a CAD AVL / onboard communication update for the Milwaukee County Transit System. Proposals will be accepted through:

2:00 P.M. CST – August 4, 2020 Proposals shall be manually signed by an officer of the firm and shall be returned in a sealed envelope, with the return address and “Proposal No. MM-06-20" clearly marked on the outside, and mailed/delivered to:

Milwaukee Transport Services, Inc. 1942 North 17th Street Milwaukee, WI 53205

Attn: Materials Management Department Late proposals will not be opened or accepted for evaluation. Any proposals received after the established due date and time at the place designated for receipt of proposals is late, without exception. Faxed or emailed proposals will not be accepted. One proposal per contractor. The proposal shall include the offer to provide CAD AVL onboard communications update as specified, based on the contractor’s professional experience in the marketplace. The proposal should be based upon specifications as outlined in the RFP to include all services as specified. Proposals will be evaluated by MTS as defined in the RFP specification. Overview: The Milwaukee County Transit System (MCTS) was founded in 1975 and provides services to the Milwaukee metropolitan area. MCTS provides approximately 150,000 passenger-trips daily. Fixed-route services is currently operated by a fleet of 385 buses. MCTS currently uses an OrbCAD CAD/AVL system on fixed-route buses and related garage and central systems and a P25 radio system for voice communication. In addition, MCTS uses various separately procured or home-grown systems for other functions including vehicle health monitoring, incident reporting, and data playback. MCTS relies on these systems to manage service provision and unplanned events, communicate between central staff, mobile supervisors, and operators, and generate reporting data for a broad cross-section of departments. This project will replace the existing CAD/AVL and a collection of peripheral systems with a new CAD/AVL system, and optionally supplement the existing P25 radio system with cellular Voice over IP. In general, the CAD/AVL and voice communication system envisioned for MCTS includes:

• Onboard components with the ability to:

o Track and report bus positions accurately.

o Support operators in daily duties including continuously updating work assignment, navigation,

and schedule adherence information.

o Provide reliable voice communication between operators and supervisors over radio and

(optional) cellular Voice over IP, for regular and emergency needs.

o Monitor vehicle health; and

o Integrate with retained onboard systems such as fare collection, automated vehicle

announcements, and video surveillance to support single-point logon, data transfer, and incident

response.

• Mobile dispatcher components with the ability to:

o Track mobile dispatcher vehicle positions accurately; and

o Effectively manage service and document incidents on-scene.

• A central system with the ability to:

o Support dispatchers in locating and tracking regular bus movements.

o Correct schedule disruptions.

o Manage detours quickly and effectively.

o Provide reliable voice and text communication channels with operators.

o Enable incident response actions; and

o Provide comprehensive data storage and versatile reporting functions.

Term of Contract This is a firm fixed price contract to start at issue of purchase order. Contractors shall propose a detailed timeline for project completion. Proposals shall be based upon specifications as outlined in the RFP to include all services as specified. Proposals will be evaluated by MTS as defined in the RFP specification.

All documents are posted on our website at www.ridemcts.com

RFP documents and addenda

No changes will be allowed to the RFP documents unless confirmed in writing by MTS, Inc. All questions regarding this RFP shall be in writing and may be submitted via email by the close of business on July 17, 2020 to the Purchasing Agent [email protected]

DBE Goal This project has a Disadvantaged Business Enterprise (DBE) goal of 17% to be considered for this project, the Prime must submit a Subcontractor/Supplier Information Sheet (DBE-02) with your Bid/Proposal. Additionally, the award of this Contract is conditioned upon your good faith efforts in achieving this project’s DBE goal, and you must document those efforts by submitting with your Bid/Proposal one of the following:

• A signed and notarized Commitment to Contract with DBE Firms (DBE-14) form(s), one for each DBE documenting the participation achieved toward satisfying the goal *, evidencing your proposed participation plan to meet or exceed the DBE goal.

OR

• A signed and notarized Certificate of Good Faith Efforts (DBE-01) form** and all relevant documentation, including a signed and notarized Commitment to Contract with DBE Firms (DBE-14) form for each DBE documenting the participation achieved toward satisfying the goal.

http://www.ridemcts.com/

mailto:[email protected]

*DBE-14 form(s) must identify (1) the DBE firm(s) by name and address, (2) the scope(s) of work/service(s) to be provided, (3) the dollar amount(s) of such work, and (4) the percentage of the DBE goal to be met. The form must be signed by the Prime and notarized to be considered responsive. The signature of the DBE firm in the affirmation section is not required at time of bid but will be required for the participation plan to be approved. Milwaukee County is entitled to reject your Bid/Proposal for failing to identify this information for each DBE. **DBE-01 form(s) must fully be complete possible and outline communications with both solicited DBE firm(s) and Milwaukee County’s Community Business Development Partners department (CBDP). Submission of form(s) with supporting documentation such as emails and similar correspondence is strongly recommended. A necessary step in the good faith efforts process and for documentation in the Certificate of Good Faith Efforts (DBE-01) form, is contacting CBDP at 414-278-4747 or [email protected] for assistance in identifying DBE firms and understanding the County’s DBE Program procedures. During the Contract, the successful Bidder/Proposer and all subcontractors will use the County’s online reporting system to document DBE participation. The Disadvantaged Business Enterprise (DBE) Utilization Specifications and forms to be used are included in the BID/RFP. The official directory of eligible DBE firms can be accessed through the following link: http://wisconsindot.gov/Pages/doing-bus/civil-rights/dbe/certified-firms.aspx To access the North American Industry Classification System (NAICS), please go to Business Classifications by NAICS Code: http://www.census.gov/eos/www/naics/

Pre-Proposal Meeting: To attend the virtual pre-proposal meeting, email [email protected] to request a Teams invite to the meeting. This pre-proposal virtual meeting will be held on Thursday July 9, 2020 from 10:30 to 11:30. It is required that you notify [email protected] by Noon on Wednesday July 8, 2020 if you intend to attend. There will be only one pre-proposal meeting scheduled. The question deadline for this RFP is COB Friday July 17, 2020 close of business. Email all questions to [email protected] by the question deadline. Questions responded to during the virtual pre-proposal meeting are not official answers and must be asked in writing. Questions: All questions regarding the RFP and requirements must be submitted in writing to [email protected] by close of business on July 17, 2020. All questions will be answered as addendum and posted to the MTS website. Addendum are required return documents with the proposal package. Discussion during the walk through are not official answers, again all questions must be submitted in writing. Negotiations: This is a negotiated procurement. Negotiation is a procedure that includes the receipt of proposals from offerors, permits bargaining, and usually affords an opportunity to revise offers before award of a contract. Bargaining in the sense of discussion, persuasion, alteration of initial assumption and position and give-and-take may apply to price, schedule, technical requirements, type of contract, or other terms of a proposed contract.


http://wisconsindot.gov/Pages/doing-bus/civil-rights/dbe/certified-firms.aspx

http://www.census.gov/eos/www/naics/





Right to Reject: MTS reserves the right to make an award based on its own determination, or to reject any or all proposals or portions of same, if in the opinion of MTS, the best interest of MTS will be served thereby. Waiver of Informalities: In its sole discretion, MTS may waive informalities and minor irregularities in proposals received. Binding Contract: A proposal received in response to a Request for Proposal (RFP) is an offer that can be accepted by Milwaukee Transport Services, Inc., to create a binding contract without negotiation with any offeror. Alternate Proposals Contractors may only submit one proposal for evaluation. Alternate proposals (proposals that offer something different than what is asked for) will be rejected. Milwaukee Transport Services Inc., (MTS) reserves the right to make an award based on its own determination, or to reject any or all proposals or portions of same, if in the opinion of MTS, the best interests of Milwaukee Transport Services, Inc., will be serviced thereby. Insurance Requirements Insurance Certificate meeting the MTS minimums, must be received from all parties doing work at the work site, prior to any work starting. The certificates of insurance must list Milwaukee County and Milwaukee Transport Services as additionally insured.

Order of Precedence: An order of precedence is hereby formally established and will be used to form a binding contract. The order is as follows:

1. Purchase of Services Agreement 2. All documents related to the RFP MM-06-20 3. The Service Level Agreement 4. The Purchase Order 5. Accepted Proposal of the successful contractor

The order of precedence establishes that any conflict between the accepted offer and the Purchase Order and/or RFP Documents, the Purchase Order and/or RFP Documents take precedence and control. Funds If funds are not appropriated for payment of this contract, Purchaser may terminate contract at the end of any fiscal year upon 30 days written notice. MTS operates the transit system for, and under an agreement with, Milwaukee County, Wisconsin. All multi-year contracts / agreements with MTS are contingent upon Milwaukee County retaining MTS as the operator of the transit system. The continuation of this agreement beyond December 31 of any given year, shall be contingent upon MTS receiving the necessary funding from the government agency. County Rights of Access and Audit The Contractor, Lessee, or other party to the contract, its officers, directors, agents, partners and employees shall allow the County Audit Services Division and department contract administrators (collectively referred to as Designated Personnel) and any other party the Designated Personnel may name, with or without notice, to audit, examine and make copies of any and all records of the Contractor, Lessee, or other party to the contract, related to the terms and performance of the Contract for a period of up to three years following the date of last payment,

the end date of this contract, or activity under this contract, whichever is later. Any subcontractors or other parties performing work on this Contract will be bound by the same terms and responsibilities as the Contractor. All subcontracts or other agreements for work performed on this Contract will include written notice that the subcontractors or other parties understand and will comply with the terms and responsibilities. The Contractor, Lessee, or other party to the contract, and any subcontractors understand and will abide by the requirements of Section 34.09 (Audit) and Section 34.095 (Investigations Concerning Fraud, Waste, and Abuse) of the Milwaukee County Code of General Ordinances. Continuation Clause: Contractor recognizes that the services under this contract are vital to MTS and to the public and must be continued without interruption. Contractor agrees that MTS, in its sole discretion, and by written notice to Contractor at least 30 days prior to contract expiration, may extend this Agreement for up to an additional 120 days. If extended by MTS, Contractor shall continue to provide services under this Agreement, on the same Terms as set forth in this Agreement. MTS may terminate any such extension by providing Contractor with 30 days’ notice. Contractor further agrees to exercise its best efforts and cooperation to affect an orderly and efficient transition to any successor Contractor. Written Change Orders Oral change orders are not permitted. No change in this contract shall be made unless the contracting officer gives his prior written approval, therefore. The contractor shall be liable for all costs resulting from, and/or for satisfactorily correcting, any specification changes not properly ordered by written modification to the contract and signed by the contracting officer. Protests and Appeals Policy for Requests for Proposal:

Calculation of time in days and hours shall exclude Saturdays, Sundays and major holidays. A. Prior to RFP closing -due date:

1. Protests to form and content of bid documents shall be received by the Director of Materials Management not less than five (5) days prior to the time scheduled for RFP closing. Protests shall be in writing and state the reason for it.

2. The Director of Materials Management shall review protests and if modification is necessary, prior to the RFP closing date shall be extended and addenda containing the changes shall be sent to each contractor. If the modification is rejected, the protestor shall be notified. The decision of the Director of Materials Management is final.

B. After RFP closing date:

1. Protests concerning irregularities on RFP procedures or compliance by contractors with bid documents shall be received by the Director of Materials Management within seventy-two (72) hours after time of the RFP close date.

2. When the RFP is awarded, all contractors shall be notified in writing by e mail, or by fax machine

transmission of the proposed award. Protest to the award must be delivered to the Director of Materials Management within seventy-two (72) hours after receipt of notice. A copy of the sent email transmission shall be conclusive proof of the time and date of receipt by a contractor.

3. A protest under either (B.1.) or (B.2.) above must be in writing and state the reason for it. The Director of

Materials Management shall review the protest and notify the protestor of a decision in writing via email

or via certified mail return receipt requested, within five (5) days. No contract shall be awarded while a protest is pending. A protest that is untimely or fails to clearly state the reason for it or shall have been made prior to bid opening is invalid. The decision of the Director of Materials Management disqualifying the protest for these reasons is final and cannot be appealed. A copy of the sent email shall be conclusive proof of the time and date of receipt by a contractor.

C. Appeals to the Purchasing Appeals Committee:

1. Protest from the decision of the Director of Materials Management shall be made to the Purchasing Appeals Committee by delivering a written request for appeal hearing both to the Materials Management Department and the Purchasing Appeals Committee within seventy-two (72) hours after the receipt of the Director of Materials Management's decision.

2. Written appeals to the Purchasing Appeals Committee shall be addressed as follows: Purchasing Appeals Committee C/O MTS Materials Management Department 1942 North 17th Street Milwaukee, WI 53205

3. The request shall state the grounds upon which the protest is based and shall request an appeal

hearing. No contract shall be awarded until the final disposition of the protest.

4. The Chairperson of the Purchasing Appeals Committee shall notify all interested persons of the time and place of the hearing.

5. The Purchasing Appeals Committee shall affirm, reverse or modify the decision of the Director of

Materials Management and its' decision shall be final. Code of Ethics The Milwaukee County Code of Ethics states in part, "No person may offer to give to any Public official or employee or his immediate family, and no Public official or employee or his immediate family may solicit or receive anything of value pursuant to an understanding that such officers or employees' vote, official actions or judgment would be influenced thereby." No person(s) with a personal financial interest in the approval or denial of a contract being considered by a County department or with an agency funded and regulated by a County department, may make a campaign contribution to any County official who has approval authority over that contract during its consideration. Contract consideration shall begin when a contract is submitted directly to a County department or to an agency until the contract has reached final disposition, including adoption, county executive action, proceedings on veto (if necessary) or departmental approval. Non-Discrimination

The contractor, lessee, offeror, supplier, purchaser, etc., agrees not to discriminate against any employee or applicant for employment because of race, religion, color, national origin, age, sex, or handicap, which include, but not limited to: recruitment or recruitment advertising; employment; upgrading; demotion or transfer, layoff or termination; rates of pay or other forms of compensation; selection for training, including apprenticeship. A violation of this provision shall be enough cause for MTS to terminate the contract, lease, order, etc. pursuant to County Ordinance 56.17 - Non-Discriminatory Contracts.

Schedule: MTS has established the following anticipated schedule for request for proposal.

RFP Dates Dates

Issue RFP June 26, 2020

Pre-proposal virtual meeting July 9, 2020 starts at 10:30 a.m.

Deadline for Questions July 17, 2020 close of business

Proposals Due August 4, 2020 2:00 PM CST

Virtual Interviews/Presentations (if necessary) As needed

Technical Proposal Content Requirements

Include in your Proposal the following minimum requirements: 1. A cover letter signed by an authorized officer of the Proposers’ company stating contents of the Proposal

submission and agreement with the terms and conditions of the RFP.

2. All forms and schedules that make up this document, fully completed, including:

a. Completed Code Responses for all System Specifications.

b. Completed and signed Price Proposal Forms

c. Signed copies of all required forms.

3. Corporate capability statement, including:

a. Corporate summary, including but necessarily limited to:

i. A description of the Proposers’ corporate structure.

ii. A brief corporate history with number of years in business delivering solutions for clients.

iii. Core services/goods offered as part of the Proposers’ business.

iv. Location(s) of office(s) providing the primary support for the project.

v. Number of employees (by location, if applicable).

b. Corporate experience demonstrating the Proposers’ experience in performing work of similar

type, size, and complexity by detailing:

i. Corporate qualifications and relevant experience of the Proposers.

ii. Full details on any Subcontractors proposed as part of the Project Team.

iii. Reference projects of a similar nature with full contact information (including name,

phone number, and email address) for relevant client references.

4. Team experience and qualifications, including:

a. Functional organization of the Project Team, consisting of:

i. A clear description of the proposed relationship(s) and responsibilities between the

Proposers and any Subcontractors; and

ii. An organizational chart of Project Team roles, and identifying which roles correspond to

the Proposers or any Subcontractors.

b. Identification of Key Personnel names, experience and qualifications, including but not limited to:

i. Summary of experience with related work.

ii. Years of experience in the specified position, and education; and

iii. Availability throughout the project timeframe, including working locations and time

commitments.

5. Project methodology and work plan, demonstrating thorough understanding of project delivery

requirements, including but not limited to:

a. Overview of methodology.

b. Implementation plan and schedule.

c. Overview of design review, installation, testing, and training plans; and

d. Proposers expectations of MCTS.

6. Complete set of specifications with all items on each page of specifications completed, including

response codes for all requirements with proposed modified requirement language for requirements

with a “CM” response code.

7. System Solution, describing the proposed system and cross-referenced to the System Specifications,

including:

a. An overview of the Proposers’ hardware, software, and configurations proposed for

implementation.

b. An overview conceptual diagram illustrating all proposed system elements and high-level data

flows.

c. High-level specifications for the system hardware components identified in the System

Specifications as being the responsibility of MCTS to procure separately.

d. Detailed descriptions of the Proposers’ standard system modules and functionalities; with

graphical user interface samples, for dispatchers, mobile dispatchers, and operators.

e. Provisions for database security and vulnerability mitigation plans.

f. Standard approach to scheduled system maintenance and upgrades; and

g. A proposed Service Level Agreement to address unplanned maintenance.

8. System Support Agreement, which will be negotiated in parallel with a system implementation contract.

Proposal Evaluation: MCTS intends to award a Contract to the proposal that represents the best value to

Milwaukee Transport Services. The scoring methodology is supplied in the following table.

In determining the number of points a Proposal will receive in each category, MTS will consider the Proposal material submitted, references, oral interviews (if applicable), and any other relevant information given about a Proposers.

Evaluation Criterion Key Factors Considered Up to Points

Experience Base • Overall installation and deployment experience

• Experience and past performance on similar projects

• References from past customers on similar projects

300

Demonstrated Financial Stability

• Demonstrated financial solvency and capacity of Proposers

• Demonstrated financial solvency and capacity of Subcontractors

60

Qualifications of the Personnel Assigned to the Project

• Project management team personnel and organization

• Personnel experience with deploying similar projects

• Anticipated availability of Key Personnel

140

Implementation Approach

• Feasibility of Proposed System Implementation Plan 140

Capability of the Proposed System to Meet MCTS Needs

• Compliance with System Specifications

o Acceptability of any “CM” (complies with modified requirement) responses

o Impact of any “N” (does not comply) responses

o Usefulness of any offered enhancements

• System life cycle, usability, expandability, and maintainability

• Minimization of risk by use of the most current, proven and available state-of-the-practice technologies

1349

Method of Award Evaluation Team:

1. The MTS evaluation committee will consist of five (5) persons who will review proposals submitted by all respondents.

2. MTS reserves the right to change the makeup of the committee based on personnel changes, availability, or special knowledge needed to help evaluate the proposals.

3. Respondents who submit a proposal may be required to make an oral presentation of their proposal to the MTS evaluation committee. Presentation will be scheduled through the MTS Materials Management Department and will be at the respondent’s expense. Selected respondents will be given adequate notice of the date and time for preparation of presentation.

Evaluation and Scoring Criteria: In awarding a contract, price is one factor to be considered, and the award is not required to be made to the lowest responsive, responsible offeror. Awards shall be made to the responsive, responsible firm whose proposal overall is the most advantageous to MTS. Such determination is the sole opinion of MTS.

In addition to the Technical response, the price proposal will also be considered in determining the best offer/value. When determining the best offer/value, price will have approximately equal value to the Technical response. After technical scores are complete, price will be evaluated alongside technical merit in a tradeoff fashion to choose the proposal that represents the best value to MCTS.

The Company intends to award a contract to the qualified contractor who submits a responsive and responsible proposal that offers MTS the best value. Ranking will be based on a maximum of 1989 points, as indicated on included table.

Cost Response: The cost response should be provided in a separate sealed envelope with the DBE paperwork. Do not adjust the Excel pricing format. The cost figures shall be furnished on the price sheet(s) provided and shall be submitted in a sealed envelope separate from your technical response. Your cost response shall include the price sheets(s) and the signature sheet. One (1) original copy of the price sheet and signature sheet, plus one (1) copy on a USB drive are required to be returned. Provide both in a separate sealed envelope. The price quoted should fully loaded (overhead and margin). No hidden charges will be allowed, therefore a complete, disclosure of charges should be included within the submitted bid. Any charges not disclosed on the bid would be the sole responsibility of the Contractor proposing the cost. MTS is tax exempt. This Request for Proposal should not be construed as a contract to purchase goods or services from any of the participating Contractors. Liquidated Damages Once an agreed upon project timeline is established, liquidated damages shall also be established, as a means to keep the project timeline moving and meet the milestone payment schedule. Any liquidated damages assessed will be show as a line item on the contractor invoice, subtracting said liquidated damage from the amount due for that period.

Payment Milestone Schedule The payment milestone schedule will form part of the Contract. Upon each milestone being completed and approved by MCTS, payment to be released as a percentage of the total cost of the Contract will be as indicated in the following table:

Milestone Payment

(% Contract value)

System Implementation Plan Accepted 5%

Acceptance of Final Design Document 10%

Factory Testing Accepted 15%

Mini-Fleet Testing Accepted 20%

Completion of Installs 20%

Final System Acceptance 30%

Enclosures:

1. Request for Proposal MM-06-20 2. MCTS Functional Specification IT-01-20 3. Purchase of Services Agreement 4. DBE Utilization Specifications and Forms 5. FTA Terms & Conditions

Return only these forms with RFP Response Package

On the USB drive save each document as a separate document. Note that all items listed below shall be submitted, clearly labeled and in the following order in your proposal:

RFP Submittal Requirement Verified Included in Submittal

Signature Sheet (one sided original)

Technical Response -One (1) Original hard copy and one copy (1) on a USB drive saved as Technical response. Include answers to all Technical Proposal Contract Requirements

Buy America Form One (1) hard copy and one (1) copy on a USB drive saved as Buy America form.

Proposal Price Sheet(s) (1) one printed copy and (1) one electronic EXCEL copy on the USB drive. Hard copies of these items must be in a separate sealed envelope with the completed DBE paperwork.

One (1) hard copy of the DBE paperwork in a separate sealed envelope with the price pages and one (1) copy on a USB drive

One original signed EEO Certificate and one (1) copy of the USB drive saved as EEO Certificate

Independent Contractor Form (1) original and one (1) copy on the USB drive saved as Independent Contractor form

Completed Bidders List form (1) original and one (1) copy on the USB drive, saved as Bidders list form Completed Debarment form (1) original and one (1) copy on the USB drive, saved as Debarment form

Completed Confidential Information form (1) original and one copy on the USB drive, saved as Confidential information form. Conflict of Interest Form (1) original and one (1) copy on the USB drive saved as Conflict of Interest form

False Claims Form (1) original and one (1) copy on the USB drive saved as False Claims form.

Signed copies of all addenda released to our website at www.ridemcts.com, Plus one copy on the USB saved as Addenda.

One (1) copy of the Completed Anti-lobby form and one (1) on the USB drive, saved as Anti Lobby form.

One (1) copy of the Completed Insurance Acknowledgement form and one (1) on the USB drive, saved as Insurance Acknowledgement form.

Proposed Project timeline completion and one (1) on the USB drive, saved as Project timeline.

One (1) copy of a recent financial audit report and one copy (1) on the USB drive, saved as financial audit

Proposals that do not follow the submission directions may be deemed unresponsive. Do not return the full RFP with the proposal – only return required documents in the order stated for the hard copy and the USB copy.

http://www.ridemcts.com/

PROPOSAL PRICE SHEETS RFP MM-06-20 CAD AVL onboard communications update General Notes

1. MTS/MCTS reserves the right to adjust a line item quantity up to +/- 20%, at the stated unit price 2. Some vehicles may already have a Digi WR54 router by the time of implementation, in which case existing

routers will be used. 3. Prices must be entered, if existing equipment cannot be reused. 4. MTS/MCTS reserves the right to purchase additional test benches at the stated unit price

Price Proposal Form

CAD/AVL and Voice Communications System for MCTS

Table 1: Core System Components

Cost Items

Installed Quantity

Installed Unit Cost

Installed Total Cost

Spares Quantity

Spares Unit Cost

Spares Total Cost

Extended Cost

(G) = C+F (A) (B) (C) = A x B (D) (E)

(F) = D x E

Fixed Route Onboard Components

1. Mobile Data Terminal 385 19

2. Vehicle Logic Unit 385 19

3. Digi WR54 Router (Note 2) 385 19

4. Antenna Hardware (Cellular, Wi-Fi, GPS) if required (Note 3) 385 19

5. Radio Handsets if required (Note 3) 385 19

6. Covert Alarm Switch 385 19

7. Covert Microphone 385 19

8. Onboard Software Lot

Fixed Route Onboard Subtotal

Mobile Dispatcher Components

9. Cellular Data Modem/GPS Reciever 25 1

10. Dispatching Software (Mobile-Adapted) Lot

Mobile Dispatcher Subtotal

Central System Components

11. Server Hardware Lot

12. Central Software Lot

Central System Subtotal

Integration

13. HASTUS Integration Lot

14. Human Management System Integration Lot

15. Destination Sign Integration Lot

16. Automated Vehicle Announcement System Integration Lot

17. Fare System Integration Lot

18. Onboard Surveillance System Integration Lot

19. Battery Charge Monitoring System Integration Lot

20. Solar Winds Integration Lot

Integration Subtotal

Project Implementation

21. Project Management and Documentation Lot

22. Design Review Lot

23. Acceptance Testing Lot

24. Training and Manuals Lot

Project Implementation Subtotal

Warranty and Technical Support

25. Base Warranty Period - Year 1 and 2 after System Acceptance Lot

Warranty and Technical Support Subtotal

GRAND TOTAL

Information about labor included in cost when labor exists

Total Non-DBE labor

hours

Non-DBE hourly Rate

Total DBE labor hours

DBE hourly

rate Extended

hours (L) = H+J

(H) (I) (J) (K)

Table 2: Options

Cost Items

Installed Quantity

Installed Unit Cost

Installed Total Cost

Spares Quantity

Spares Unit Cost

Spares Total Cost

Extended Cost

(G) = C+F (A) (B) (C) = A x B (D) (E)

(F) = D x E

Option 1: VoIP Communication (Specifications Chapter 4.5)

26. Voice over IP Communication Lot

GRAND TOTAL OPTION 1

Option 2: Test Environment, Bench, and Database (Specifications Chapter 3.3.4)

27. Test Environment and Database Lot


Option 3: Test Bench (Specifications Chapter 5.7)

28. Test Bench (Note 4) 2


Options 4-11: Warranty Period Extensions

29. Option 4: Additional Warranty - Year 3 after System Acceptance Lot








Contact [email protected] for an Excel version of the price pages


MILWAUKEE COUNTY – BIDDERS LIST FORM

DOT ASSISTED CONTRACTS [49 CFR, Part 26]

49 CFR, Part 26 requires that all recipients of Federal Funds collect certain information from all bidders submitting responses to solicitations. To assist in the building of demographics for the area upon which reasonable and effective expectations of DBE opportunities may be based, all bidders are required to return this certificate with their offer. Any offer submitted that does not contain a completed copy of this form will be ruled as non-responsive and dropped from further consideration in the procurement process of the solicitation.

Firm Name:_______________________________________________________________________ Firm Address:______________________________________________________________________ ______________________________________________________________________ Firm Phone (____) ____________________________ Firm Email Address____________________ Firm Fax: (____) ______________________________ General Classification of Firm by Quantity of Employees: _____ Less than 10 _____ 11-50 _____ 51-100 ____ 101-500 _____ 501-1000 _____ 1001-5000 _____ More than 5000 General Classification of Firm in Age of Existence: ____ 0-5 years ____ 6-10 years ____11-50 years ____ Over 50 years General Classification by Type: ____ Firm is a Small Business ____ Firm is a Certified DBE ____ Firm is a Certified WBE ____ Firm is not one of the above General Classification by Annual Gross Income: ____ The approximate annual gross income for this firm is less than $100,000 ____ The approximate annual gross income for this firm is $100,000 - $250,000 ____ The approximate annual gross income for this firm is $250,001 - $500,000 ____ The approximate annual gross income for this firm is $500,000 - $1M ____ The approximate annual gross income for this firm is $1M - $5M ____ The approximate annual gross income for this firm is greater than $5M I certify this information is accurate to the best of my knowledge. ___________________________________ ___________________________ _____________ Signature Print Name Date

DESIGNATION OF CONFIDENTIAL AND PROPRIETARY

INFORMATION The attached material submitted in response to Proposal No. includes proprietary and confidential information which qualifies as a trade secret, as provided in Section l9.36(5), Wis. Stats., or is otherwise material that can be kept confidential under the Wisconsin Open Records Law. As such, we ask that certain pages, as indicated below, of this proposal response be treated as confidential material and not be released without our written approval. We request that the following pages not be released: Section Page # Topic ______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

IN THE EVENT THE DESIGNATION OF CONFIDENTIALITY OF THIS INFORMATION IS CHALLENGED, THE UNDERSIGNED HEREBY AGREES TO PROVIDE LEGAL COUNSEL OR OTHER NECESSARY ASSISTANCE TO DEFEND THE DESIGNATION OF CONFIDENTIALITY. This does not apply to proposal prices. Prices are always open. Other information usually cannot be kept confidential unless it is a trade secret. Trade secret is defined in s.l34.90(l)(c), Wis. Stats. as follows: "Trade secret" means information, including a formula, pattern, compilation, program, device, method, technique or process to which all the following apply: l. The information derives independent economic value, actual or potential, from not being generally known to, and not being readily ascertainable by proper means by, other persons who can obtain economic value from its disclosure or use. 2. The information is the subject of efforts to maintain its secrecy that are reasonable under the circumstances. Failure to include this form in the proposal response may mean that all information provided as part of the proposal response will be open to examination and copying. Milwaukee Transport Services, Inc., considers other markings of confidential in the proposal document to be insufficient. The undersigned agrees to hold Milwaukee Transport Services, Inc., harmless for any damages arising out of the release of any materials unless they are specifically identified above. ______________________________________________________________________________ Name-Authorized Representation Company Name ______________________________________________________________________________ Signature-Authorized Representative Date

Conflict of Interest Statement

____________________________hereby certifies that our Firm’s officers and personnel assigned to the

_________________________project or their immediate family members do not have a conflict of

interest performing the duties outlined in this contract with Milwaukee County Transit System (MCTS)

or Milwaukee Transport Services (MTS). To the best of our knowledge no officer or personnel assigned

or the immediate family members has a material financial interest in any commercial entity which may

provide products or services as part of the ____________________________ project. If any officers and

personnel that are assigned to the ___________________________project become aware of a conflict

of interest they will notify MTS immediately and take necessary action to address the conflict.

Conflict of Interest: A situation in which a person or organization is involved in multiple interests (financial, emotional, or otherwise) one of which could corrupt the motivation of the person or organization. Company Name: __________________________________________________________ Authorized Name______________________________ Title: _______________________ Name of Consultant Assigned: _______________________________________________ Signature: ______________________________________________________ Date:____________________________________________________________________

SIGNATURE SHEET CASH DISCOUNT: Cash invoice discount for payment of invoices following receipt and acceptance of goods or services: % 30 days. DELIVERY: Price shall include delivery to: FOB FINAL DESTINATION to Milwaukee Transport Services, Inc., 1525 W. Vine St., Milwaukee, WI 53205, unless otherwise noted in this bid. BY SIGNING THIS FORMYOU ARE AGREEING WITH THE FOLLOWING STATEMENTS: 1. This bid has been made without any connection with any other bidder and is in all respects fair and without

collusion or fraud. 2. This bid has been made with the understanding that no elected officer/employee of Milwaukee Transport

Services, Inc., or Milwaukee County is interested therein, directly or indirectly. 3. The specifications for this bid have been read and understood. 4. Your company has never defaulted on any contract with Milwaukee Transport Services, Inc., or Milwaukee

County. In signing and submitting this bid, the bidder assures Milwaukee Transport Services, Inc., that the furnishing of the subject materials, services or equipment is under his/her control, accepts and has read all the Terms and Conditions of this BID/RFP and all of its documents. If the bidder’s performance, in the event he/she is successful is contingent upon the act of another party, the bidder assures MTS that he/she has the necessary commitments to complete the contract which may be awarded him/her. Date: _____________ Submitted by: ________________________________________________________ Name of firm: _______________________________________________________ Address of firm: ______________________________________________________ Signed per: (manual signature required) ____________________________________ Print name: __________________________________________________________ Title: __________________________________Email:________________________

TELEPHONE: ___________________________FAX: ____________________________

DUNS#: ____________________

Insurance and Indemnity Acknowledgement Form

Contractor must at the time of the contract award provide to the County proof of all Liability clauses listed below:

Indemnity: Contractor agrees to the fullest extent permitted by law, to indemnify, defend and hold harmless, MTS and its agents, officers and employee, from and against all loss or expenses including cost and attorney's fees by reason of liability for damages including suits at law or in equity, caused by any wrongful, intentional, or negligent act or omission of Contactor, or its (their) agent(s) which may arise out of or are connected with the activities covered by this agreement. Insurance: Contractor agrees to maintain policies of insurance and proof of financial responsibility to cover costs as may

arise from claims for damages to property of and/or claims which may arise out of or result from Contractors

activities, by whomever performed, in such coverage and amounts as required and approved by MTS.

Acceptable proof of such coverage shall be furnished to MTS prior to commencement of activities under this

agreement. A Certificate of Insurance i n c l u d i n g d e c l a r a t i o n s p a g e , shall be submitted for review for

each successive period of coverage for the duration of this agreement, unless otherwise specified by MTS, in

the minimum amounts specified below.

Contractor shall provide evidence of the following coverages and minimum amounts: Type of Coverage Minimum Limits Wisconsin Workers’ Compensation and Employer’s Liability & Disease

Statutory/Waiver of Subrogation $100,000/$500,000/$100,000

General Liability Bodily Injury and Property Damage to include: Personal Injury, Fire, Products and Completed Operations

$1,000,000 Per Occurrence $2,000,000 Aggregate

Automobile Liability Bodily Injury and Property Damage All Autos

$1,000,000 Per Accident

Professional Liability Refer to Additional Provision A.1.


Umbrella Liability Policy will follow form to underlying Employer’s, General, and Automobile Liability policies


Milwaukee Transport Services, Inc (MTS) and Milwaukee County shall be named as an Additional

Insured on the General and Automobile L iability policies as respects the services provided in this

agreement. A Waiver of Subrogation shall be afforded to MTS on the Workers' Compensation

policy. A thirty (30) day written notice of cancellation or non-renewal shall be afforded to Milwaukee

County.

The insurance specified above shall be placed with a Carrier approved to do business in the State of Wisconsin. All carriers must be A rated or better per AM Best's Rating Guide. Any requests for deviations from or waivers of required coverages or minimums shall be submitted in writing and approved by MTS’s Risk Manager as a condition of this agreement. A.1. Professional Liability – Additional Provision. Contractor agrees to provide additional information on its professional liability coverage as respects policy type, i.e. errors and omissions for consultants, architects, and/or engineers, etc.; applicable retention levels; coverage form, i.e. claims made, occurrence; discover clause conditions, and effective retroactive and expiration dates, to MTS’s Procurement Department as may be requested to obtain approval of coverage as respects this section. It is understood and agreed that coverage which applies to the services inherent in this agreement will be extended for two (2) years after completion of all work contemplated on this project if coverage is written on a claims-made basis. The undersigned certifies and represents an understanding of MTS’s Insurance and Indemnification requirements. The undersigned acknowledges that MTS is, in part, relying on the information contained in this Proposal document in order to evaluate and compare the response to the RFP.

__________________________________________

Contractor’s Name __________________________________________ Title __________________________________________

Signature __________________________________________

Date

INDEPENDENT CONTRACTOR INFORMATION (For Professional Services Contract Only) As per 1995 Wisconsin Act 118, amending Wisconsin Statute 108.02(12)b; comprehensive revisions to the Wisconsin Unemployment Compensation Act includes a new definition for “independent contractor”, which became effective on January 4, 1996.

1. Are you a Corporation? □ YES □ NO

If yes, in what state: ___________________________________ If no:

2. Federal Employer Identification Number: _________________________________

If no number issued, date of application ______________________, or Social Security Number: __________________________________

3. Year of last business or self-employment tax return: ________________

_________________________________________________________________ Firm Name __________________________________________________________________ Signature of Authorized Owner/Agent __________________________________________________________________ Printed name and title of Authorized Owner/Agent ___________________________ Date Revised: 3/19/18

False Claims Act Form

A recent amendment to the Federal Acquisition Regulation requires contractors to disclose violations of criminal law and the False Claims Act in connection with the award and performance of government contracts and subcontracts. By signing this form, it assures Milwaukee Transport Services, Inc., that Contractors are subject to debarment and suspension from government contracting for knowingly failing to disclose such violations and overpayments on government contracts in a timely manner.

Date: _____________ Submitted by:________________________________________________________ Name of firm:_______________________________________________________ Address of firm: ______________________________________________________ Signed per: (manual signature required)____________________________________ Print name:__________________________________________________________ Title: __________________________________Email:________________________ Telephone: ___________________________Fax: ____________________________

COMMUNITY BUSINESS DEVELOPMENT PARTNERS

MILWAUKEE COUNTY

DBE-00 (11/01/2016) Previous Editions Obsolete 1

DISADVANTAGED BUSINESS ENTERPRISE (DBE) UTILIZATION SPECIFICATIONS

1. The award of this contract is conditioned upon your good faith efforts in achieving this project’s Disadvantaged

Business Enterprise (DBE) goal of __%, and you must document those efforts.

2. DBE Goal: This participation goal is based on the total dollar value of your base bid, initial offer or initial scope of work, less allowance and/or reimbursable items. Participation must be maintained throughout the contract, including additional contract work, e.g., acceptance of alternates, negotiated procurements, change orders, addendums, use of allowances, etc.

BID/PROPOSAL CONSIDERATIONS 3. The County will reject your bid/proposal if it does not include documentation of your good faith efforts in one of

the following ways:

a. When you meet or exceed the goal, include the Commitment to Contract with DBE (DBE-14) form(s).

b. When you do not meet or exceed the goal, include the Certificate of Good Faith Efforts (DBE-01) goal. EXAMPLE: 20% goal. You have 4% participation in commitment(s). You submit the commitment(s) for the 4%, along with the Certificate of Good Faith Efforts (DBE-01) documenting the efforts undertaken to achieve the remaining 16%.

4. Your good faith efforts are those that one could reasonably expect to be taken if you were actively and

aggressively trying to obtain DBE participation sufficient to meet the goal. Additional guidance is part of the Certificate of Good Faith Efforts (DBE-01) form).

5. If awarded the contract, you will enter into a contractual agreement, directly or through subcontractors, according to the Commitment to Contract with DBE (DBE-14) form(s) submitted with your bid/proposal. Copies of the executed contract(s) or purchase order(s) will be required to be submitted to the County.

6. DBE participation credit, for both DBE and non-DBE primes, is calculated as follows:

a. All of the identified scope(s) of work must have a commercially useful function in the actual work of the contract and must be performed directly by the DBE. This means that DBEs must perform the contract work with their own employees, as determined by the County.

b. One hundred percent (100%) for the work performed by a DBE. If a DBE subcontracts a portion of its work

to another firm, the value of the subcontracted work will not be counted towards the DBE goals unless the work is performed by another DBE. Material, equipment and supplies provided and installed (put into use) by a DBE also count dollar for dollar to toward the goal.

c. One hundred percent (100%) for products manufactured by a DBE. DBE manufacturers operate or

maintain a facility that produces goods from raw materials, or substantially alters the materials or supplies, on-site.

d. Sixty percent (60%) for materials or supplies purchased from a certified DBE regular dealer. Regular Dealers own, operate, or maintain stores, warehouses, or other establishments where materials

or supplies are kept in stock, and regularly sold to the public in the usual course of business. A regular dealer in bulk items such as steel, cement, gravel, stone, and petroleum products don’t need to keep stock, if it owns or operates distribution equipment.


MILWAUKEE COUNTY


e. One hundred percent (100%) for the fees or commissions charged for assistance in the procurement of

material and supplies. Fees or transportation charges for the delivery of material or supplies by a DBE to a job site also count dollar for dollar toward the goal. The cost of the materials and/or supplies themselves will not be credited towards its DBE goals. Brokers, Trade Agents and Manufacturers’/Independent Sales Representatives arrange or expedite transactions without taking title of the goods being sold and receive a commission or fee for their service.

f. One hundred percent (100%) for DBE trucking firms. The DBE must be responsible for the management

and supervision of the entire trucking operation for which it has contracted. The DBE must also use trucks it owns, insures, and operates using drivers it employs. The DBE may lease trucks from another firm, or an owner-operator, certified as a DBE. The DBE may also lease trucks from a non-DBE firm, or owner-operator, but credit will only be given for the fee or commission and not the trucking itself. Ready mix operations will not receive credit for deliveries made by non-DBE firms.

g. You are required to notify the County if any DBE contractor(s) working on this contract will sublet any portion

of their work.

7. Only DBEs certified by the State of Wisconsin Unified Certification Program (UCP) prior to the bid/proposal submission deadline count towards the satisfaction of the goal. If you want to use a firm certified in another state or with another agency, the firm must apply for certification with the UCP prior to submission of your offer/bid deadline. For assistance related to DBE certification of firms, contact the Certification Compliance Administrator at (414) 278-4747.

8. The County reserves the right to request supporting documentation from both you and any listed DBE. If you fail to respond within the time specified, the County will determine you to be non-responsive and remove you from further consideration for contract award.

FOLLOWING CONTRACT AWARD 9. The County reserves the right to conduct compliance reviews and request, both from you and your subs or

suppliers, supporting documentation to verify DBE participation, in addition to the information entered monthly into the County’s online reporting system. The County will notify you if you are not in compliance with contract specifications. If you fail to take corrective action as directed, the County will take one or more of the following actions:

a. Terminate or cancel your contract, in whole or in part; b. Remove you from the list of qualified contractors/consultants, and refuse to accept future bids/proposals

from you for a period not to exceed three (3) years; c. Withhold contract payments, or pay subs and/or suppliers directly, to cover shortfall; and/or

d. Bring suit to recover damages up to the amount of the shortfall, including interest at the rate of 12% annually,

plus the County’s costs, expenses and actual attorney’s fees incurred in the collection action. 10. You must submit copies of the executed subcontract agreement(s) or purchase order(s) for each sub and/or

supplier listed on the contract. Include copies with the first monthly request for payment. REQUESTS FOR PAYMENT WILL NOT BE PROCESSED IF AGREEMENTS/PURCHASE ORDERS ARE NOT SUBMITTED. In addition, you will document that each DBE is notified at least three (3) working days before start of their subcontract work.


MILWAUKEE COUNTY


11. You are required to notify the County if any DBE contractor(s) working on this contract will sublet any portion of

their work. 12. If the DBE(s) cannot perform, if you have a problem in meeting the goal, or any other issue such issues come

up, you must immediately contact CBDP Compliance at (414) 278-4851. You must submit written notification of your desire for substitution to the DBE affected, and copy the County. This notice must state the reason for the request. The DBE has five (5) business days to provide written objection/acceptance to you. Approval must be obtained from County prior to making any substitutions. DBE contractors are also required to notify and obtain approval from the County prior to subletting work on this project.

13. Requests for Payment: You will enter payments to subs and suppliers directly into the County’s online reporting system on a monthly basis. These entries will cover payments made during the preceding month and will include zero dollar ($0) entries where no payment has occurred. You must also indicate on the AIA Document G703 - Continuation Sheet, or equivalent, work being performed by DBEs. Either a) place the word “DBE” behind the work item or b) break out the work done by DBEs at the end of the report. If you don’t do these things, the County will deny payments, or enforce other sanctions including those listed in Section 9, above.

14. The County has a revolving loan program for DBEs. If you use a DBE that is using these County funds, you

must assist the County repayment of these funds. This may include, but is not limited to, providing written information regarding the sub’s contract balance, prior payment (two or three party) agreements, and the issuance of two-party checks payable in the name of Milwaukee County and the DBE indebted to the County under this program.

15. The County reserves the right to waive any of these specifications when it is in our best interest.


CERTIFICATE OF GOOD FAITH EFFORTS

Completion of this form is required for all bidders who have not achieved participation goal. Submission of a complete

form is a matter of responsiveness to this bid. Completion of all three tabs in this spreadsheet is required.

Certificate of Good Faith Efforts

Guidance on completing these documents.This guidance and information is provided to assist bidders in compliance with the provisions under all Milwaukee County Ordinances and US DOT 49

CFR part 26, pertaining to the implementation of the US DOT disadvantaged business enterprise program. Like all guidance material, these questions

and answers are not, in themselves, legally binding or mandatory, and do not constitute regulations. They are issued to provide an acceptable means,

but not the only means, of compliance with Part 26 and other guiding statutes, regulations and laws. For US DOT projects the regulations in 49 CFR

26 and others can be reviewed at: https://www.transportation.gov/civil-rights/disadvantaged-business-enterprise/dbe-program-overview The

Milwaukee County CBDP program can be reviewed in more detail at: http://county.milwaukee.gov/cbdp including links to relevant regulations.

When Milwaukee County assigns a participation goal, you will make good faith efforts to meet this goal prior to submitting a bid or proposal in order to

be responsive. If you haven't met the goal, you can document adequate good faith efforts toward that end. This means that you must show that you

took all necessary and reasonable steps to achieve the participation goal. The County will make a fair and reasonable judgment as to whether you made

adequate good faith efforts according to the following guidelines. It is important to consider the quality, quantity, and intensity of the different kinds of

efforts that were made. These efforts should be those that one could reasonably expect you to take if you were actively and aggressively trying to obtain

participation sufficient to meet the participation goal. Going through the motions by making a phone call or two to a firm that you think should qualify is

not good faith efforts to meet the project requirements. The County’s determination concerning the sufficiency of your good faith efforts is a judgment

call and meeting quantitative formulas is not required. The following is a list of types of actions the County considers as part of your good faith efforts.

This isn’t a mandatory checklist, nor is it all-inclusive. Other factors or types of efforts may be relevant in appropriate cases, see regulations for more

information.

DBE-01 (09/27/2016) Previous Editions Obsolete 1 of 5



Prime Contractor Firm Name and

Address

Authorized Representative Email Address Telephone

Number

Other Contact

Info

Is the Prime a DBE?

Goal Pledged

Certificate of Good Faith Efforts

Provide a brief summary of why your firm is unable to meet the participation goal on this project.

This document is required to detail what your firm has done to meet this project’s participation goal if the participation you have attained is less than the goal set for this project. Guidance

as to acceptible ‘good faith efforts’ is found on the Guidance page of this spreadsheet. Failure to use and properly document good faith efforts to meet the assigned participation goal will

result in the rejection of your bid/proposal. By submitting this document, do hereby acknowledge that I am authorized as the representative for the bidder/proposer on the following

Milwaukee County Project and that we have provided documented proof of our firms good faith efforts to solicit, negotiate with and utilize certified firms to meet the participation goal of

this contract as demonstrated by my response to the questions contained in this fully completed set of documents.

Total Contract

Amount

Project Title Bid NumberProject Number DBE Total Project Percentage




NAICS codes (Required) Description of work Estimated Dollar Value

(Required)

Was this work made available to DBE

Firms? If no, explain why.

Explanation

Contractible Work ItemsYou are required to determine portions of work to be contracted in a manner that will increase the likelihood of meeting the participation goal set for this project. In selecting work to be contracted, you

must consider, where appropriate, breaking down contracts into economically feasible units to faciliate DBE participation. To assist in these efforts and to provide consistent definitions, use NAICS codes

(http://www.census.gov/eos/www/naics/) to identify each category of work you identified. DBE firms are registered by NAICS code and a list is available in the Wisconsin UCP directory.




Firm Name Describe Work Solicited

(NAICS codes pull from

"Contractible Work

Items")

Date of Original

Solicitation

Solicitation

Method Used

Date of Follow Up

Solicitation

Solicitation Follow

Up Method Used

Quote Received

Y/N

Quote Accepted

(Y/N)

Reason for Rejecting Quote

You must have solicited quotes in good faith from certified firms. List certified firm(s) that you have solicited for participation in this project. Documentation of information provided below will be required upon

evaluation of a Good Faith Effort. "Original Solicitation" and "Solicitation Follow Up" with certified firms must be documented in written form (email or fax only).

Soliciting from Interested Firms




Firm Name Describe Work Solicited

(NAICS codes pull from

"Contractible Work

Items")

Date of Original

Solicitation

Solicitation

Method Used

Date of Follow Up

Solicitation

Solicitation Follow

Up Method Used

Quote Received

Y/N

Quote Accepted

(Y/N)

Reason for Rejecting Quote


DBE-02 (11/01/2016) Previous Editions Obsolete

SUBCONTRACTOR/SUBCONSULTANT/SUPPLIER INFORMATION SHEET

Milwaukee County requires the following collection of information on all subcontractors, sub-consultants and/or suppliers submitting quotes on Milwaukee County projects. This information is to be submitted with bid/proposal.

PROVIDE THE FOLLOWING INFORMATION ON EACH BID/QUOTE

Name

CERTIFICATION

DBE or none

Address

Date Firm

Established

Work or Service to be Performed

Note: Information gathered on the background and financial status of firms is protected from disclosure by Federal Regulation.

FIRM: Project No: ______________________


MILWAUKEE COUNTY


COMMITMENT TO CONTRACT WITH DBE

PROJECT No. ________________ PROJECT TITLE __________________________________________________ TOTAL CONTRACT AMOUNT (less allowances) $ ________________________ DBE Goal:

Name & Address of DBE(*)

Scope of Work Detailed Description

DBE Contract Amount

% of Total Contract

Bidder/Proposer Commitment (To be completed by firm committing work to DBE)

I certify that the DBE firm quoted the identified service(s) and cost(s). I further acknowledge our firm having negotiated with, and having received confirmation, on partnering, pricing and delivery from DBE firm listed herein. Our firm Phone No._________________, or one of our subcontractors, will enter into contract with the DBE firm listed, for the service(s) and amount(s) specified when awarded this contract. A copy of the contract between our firm and that of the named DBE will be submitted directly to CBDP within seven (7) days from receipt of Notice-to-Proceed on this contract. The information on this form is true and accurate to the best of my knowledge. I further understand that falsification, fraudulent statement, or misrepresentation will result in appropriate sanctions under applicable law. Signature of Authorized Representative Name & Title of Authorized Representative Date

Subscribed and sworn to before me this day of____________, 20 ________________________________________________________ [SEAL] Signature of Notary Public

State of ________ My Commission expires _____________

* Only firms certified as DBEs (within qualifying NAICS codes) by the Wisconsin UCP prior to bid/proposal opening will be credited on this contract

DBE Affirmation (To be completed by DBE Owner/Authorized Representative)

I affirm that the Wisconsin UCP has certified our company as a DBE, and that our company is currently listed in the Wisconsin UCP Directory.

I acknowledge and accept this commitment to contract with my firm for the service(s) and dollar amount(s) specified herein, as put forth by .

I understand and accept that this commitment is for service(s) to be rendered in completion of the Milwaukee County project specified herein to be completed with my own forces, unless otherwise approved by CBDP.

I affirm that approval from CBDP will be obtained prior to subletting any portion of this work awarded to my firm on this project.

__________________________________ ________________________________________________________________________ Signature of Authorized DBE Representative Name & Title of Authorized DBE Representative Phone Number Date

FOR CBDP USE ONLY

Commitment number of Participation: (A) ____ (V) _____ Project Total _______________

____ ________ Signature Date Authorized Signature Date


MILWAUKEE COUNTY


COMMITMENT TO CONTRACT WITH DBE

ADDITIONAL INFORMATION & REQUIREMENTS: 1. The Directory of Certified DBE firms eligible for credit toward the satisfaction of this project’s DBE goal will be found at the following link, and can be searched by Name and/or NAICS code.


2. CONTRACT ADJUSTMENTS: The successful Bidder/Proposer will maintain the approved DBE participation level during the term of the contract with the County, including any additional work on the contract, e.g., change orders, addendums, scope changes, etc. Contract adjustments shall include proportional DBE participation. 3. WRITTEN CONTRACTS WITH DBEs: The County requires that the successful Bidder/Proposer enter into contract, directly or through subcontractors, as stated in this form. Agreements must be submitted to the County within 7 days of receipt of the Notice-To-Proceed. By executing this commitment, you are certifying that you have had contact with the named DBE firm and that they will be hired if you are awarded the contract by the County. 4. SUBSTITUTIONS, DBE SUBCONTRACTING WORK, TRUCKING FIRMS: The successful Bidder/Proposer must submit written notification of desire for substitution to the DBE affected, and send a copy to the County, stating the reason(s) for the request. The DBE will have five (5) business days to provide written objection/acceptance of the substitution. The “right to correct” must be afforded any DBE objecting to substitution/termination for less than good cause as determined by the County. Approval must be obtained from the County prior to making any substitutions. DBEs are also required to notify and obtain approval from the County prior to seeking to subcontract out work on this project. In the case of DBE trucking firms, credit will be given for trucks leased from other DBE firms; however, if the DBE leases trucks from non-DBE firms, the commission or fee will be counted for DBE crediting.

5. REQUESTS FOR PAYMENT: The successful Bidder/Proposer must indicate on the Continuation Sheet (AIA form G703, or equivalent) the work being performed by DBE by either a) placing the word “DBE” behind the work item or b) breaking out the work done by DBEs at the end of the report. The successful Bidder/Proposer shall notify DBE firms of the date on which they must submit their invoices for payment. 6. DBE UTILIZATION REPORTS: The successful Bidder/Proposer will enter payments to subs and suppliers directly into the County’s online reporting system on a monthly basis. These entries will cover payments made during the preceding month and will include zero dollar ($0) entries where no payment has occurred. If you have any questions related to Milwaukee County’s DBE Program, please contact:

414.278.4747 or [email protected]


Page 1 of 13

Milwaukee Transport Services, Inc. 2020 Sample Purchase of Service Contract – CAD/AVL Onboard Communication Update

Vendor Name__________________

This Contract is made and entered between Milwaukee Transport Services, a quasi-governmental

instrumentality of Milwaukee County, 1942 North 17th Street, Milwaukee, Wisconsin 53205 (hereinafter

called MTS) _Name and address of provider____________(hereinafter called Contractor).

1. Dates of Performance

The work shall start with the issue of the purchase order and shall follow the proposed project timeline agreed upon which will be in this agreement after award.

2. Scope of Service

Contractor shall specifically perform all of the services and achieve the objectives as set forth in the proposal submitted by Contractor to MTS, which is attached hereto. Contractor shall perform all services provided under this Contract in the manner prescribed by the relevant RFP or Specifications, which are herein incorporated by reference and made a part of this Contract as if physically attached hereto.

The Contract consists of the following five (5) documents listed below, all of which are incorporated herein by reference, in the following order of precedence that will be govern any inconsistencies between the terms of this Contract and the terms of any Exhibits, Schedules, or Attachments thereto:

a. Purchase of Services Agreement b. Service Level Agreement c. MTS RFP MM-06-20 and all its Documents d. MTS Purchase Order e. Proposal from Awardee

3. Staffing and Delivery of Programs/Services

A. Contractor shall provide all personnel required to perform the programs or services under this Contract. Such personnel shall not be employees of MTS, or have any other contractual relationships with MTS. Any replacement of personnel listed in Contractor's proposal shall be by persons of like qualifications, which shall be attested to by Contractor. Whenever possible, notification of replacement of personnel shall be provided to MTS prior to replacement.

B. Contractor will provide proper supervision to all employees providing programs or services

under this Contract. C. Except as provided herein and relevant RFP and Specifications, Contractor shall determine the

methods, procedures, and personnel policies to be used in services under this contract.

Page 2 of 13

D. This Contract in its entirety is at all times subject to such local, state, and federal laws and

administrative regulations as exist at the time this Contract is executed and as shall become effective after execution but prior to termination of this Contract. Contractor shall comply with all federal, state, and local laws and regulations and shall maintain in good standing all licenses, permits, and certifications relating to the services referred to herein.

H. Contractor shall complete all forms and documents requested by the MTS within timeframes

outlined by the MTS. 4. Compensation

A. Contractor shall be compensated for work performed as stated in Contractor’s proposal attached hereto and made a part of this Contract. Contractor recognizes that the total service needs of MTS may not be met. Under no circumstances shall payments under this Contract exceed the amount(s) authorized for this Contract. The parties agree that section 66.0135, Wisconsin Statutes, Prompt Pay Law, shall not apply to payment for programs and services provided hereunder.

B. MTS and Contractor acknowledge that funding of this Contract is completely dependent upon state and federal grants and contracts. The obligation of the MTS to purchase the services described herein is contingent upon present state and federal grants and contracts continuing at their present levels. Should such funding sources terminate or be reduced, MTS reserves the right, in its sole discretion, either to terminate this agreement or revise the scope of services being purchased to reflect any reduction in such funding. It is further recognized and agreed by MTS and Contractor that the programs and services provided under this Contract are subject to all provisions of said federal and state grants and contracts, and Contractor agrees to comply with all such provisions for the period of this Contract, including all applicable provisions of the standard State/County contract.

C. MTS will not accept any changes to the compensation stated in Contractor’s proposal during the Term of this contract.

5. Billing and Reporting

A. Contractor shall provide MTS with monthly billings and reports for programs and services provided under this contract by the fifteenth (15th) working day of the month following the month in which services are provided. Contractor shall submit billings and reports according to the manner specified by MTS.

B. Within thirty (30) days of the receipt of all required billings and reports, MTS shall make

payment to Contractor of the net amount due. The 30 days does not start to run until all forms are accurate, complete, and include all revisions requested by MTS.

Page 3 of 13

6. Record Keeping and Access to Records

A. Contractor shall maintain and, upon request, furnish to MTS, at no cost to MTS, any and all information requested by MTS relating to the quality, quantity, and cost of services covered by this Contract and shall allow authorized representatives of MTS and MTS's funding sources to have access to all records necessary to confirm Contractor's compliance with law and the Bid or Specifications for this Contract. Access to information shall include computerized data and/or other electronic information used by the Contractor, made available in formats suitable for data analysis, such as queries, using conventional software programs.

B. Contractor shall maintain written verification of programs and services provided under this

Contract, including the dates of programs and services performed for all of the purchased programs and services rendered, as specified by MTS. Contractor shall maintain clearly identified and readily accessible documentation of costs supported by properly executed payrolls, time records, invoices, contracts, vouchers, or other official documentation evidencing in proper detail the nature and propriety of the programs and services provided. Contractor shall retain all such records for a period of at least four (4).

7. County Rights of Access and Audit. The Contractor, Lessee, or other party to the contract, its officers, directors, agents, partners and employees shall allow the County Audit Services Division and MTS contract administrators (collectively referred to as Designated Personnel) and any other party the Designated Personnel may name, with or without notice, to audit, examine and make copies of any and all records of the Contractor, Lessee, or other party to the contract, related to the terms and performance of the Contract for a period of up to three years following the date of last payment, the end date of this contract, or activity under this contract, whichever is later. Any subcontractors or other parties performing work on this Contract will be bound by the same terms and responsibilities as the Contractor. All subcontracts or other agreements for work performed on this Contract will include written notice that the subcontractors or other parties understand and will comply with the terms and responsibilities. The Contractor, Lessee, or other party to the contract, and any subcontractors understand and will abide by the requirements of Chapter Section 34.09 (Audit) and Section 34.095 (Investigations concerning fraud, waste, and abuse) of the Milwaukee County Code of General Ordinances.

8. Affirmative Action, TBE Goals, Non-Discrimination and Equal Employment Opportunity

A. Affirmative Action.

The Contractor assures that it will undertake an affirmative action program as required by Milwaukee County Code of General Ordinances (MCCGO) 56.17(1d), to insure that no person shall, on the grounds of race, creed, color, national origin, or sex be excluded from participating in any employment activities covered in MCCGO 56.17(1d). The Contractor assures that no person shall be excluded, on these grounds, from participating in or receiving the services or benefits of any program or activity covered by this subpart. The Contractor assures that it will require that its covered organizations provide assurances to the Contractor that they similarly

Page 4 of 13

will undertake affirmative action programs and that they will require assurances from their suborganizations, as required by MCCGO 56.17(1d), to the same effect.

B. Disadvantaged Business Enterprises.

This project has a Disadvantaged Business Enterprise (DBE) goal of 17%. To be considered for this project, the Prime must submit a Subcontractor/Supplier Information Sheet (DBE-02) with your Bid/Proposal. Additionally, the award of this Contract is conditioned upon your good faith efforts in achieving this project’s DBE goal, and you must document those efforts by submitting with your Bid/Proposal one of the following: A signed and notarized Commitment to Contract with DBE Firms (DBE-14) form(s), one for each DBE documenting the participation achieved toward satisfying the goal *, evidencing your proposed participation plan to meet or exceed the DBE goal;

OR A signed and notarized Certificate of Good Faith Efforts (DBE-01) form** and all relevant documentation, including a signed and notarized Commitment to Contract with DBE Firms (DBE-14) form for each DBE documenting the participation achieved toward satisfying the goal. *DBE-14 form(s) must identify (1) the DBE firm(s) by name and address, (2) the scope(s) of work/service(s) to be provided, (3) the dollar amount(s) of such work, and (4) the percentage of the DBE goal to be met. The form must be signed by the Prime and notarized to be considered responsive. The signature of the DBE firm in the affirmation section is not required at time of bid, but will be required for the participation plan to be approved. MTS is entitled to reject your Bid/Proposal for failing to identify this information for each DBE.

**DBE-01 form(s) must be complete to the fullest extent possible and outline communications with both solicited DBE firm(s) and Milwaukee County’s Community Business Development Partners department (CBDP). Submission of form(s) with supporting documentation such as emails and similar correspondence is strongly recommended. A necessary step in the good faith efforts process and for documentation in the Certificate of Good Faith Efforts (DBE-01) form, is contacting CBDP at 414-278-4747 or [email protected] for assistance in identifying DBE firms and understanding the County’s DBE Program procedures.

During the Contract, the successful Bidder/Proposer and all subcontractors will use the County’s online reporting system B2G to document DBE participation. The Disadvantaged Business Enterprise (DBE) Utilization Specifications and forms to be used are included in the BID/RFP. The official directory of eligible DBE firms can be accessed through the following link: http://wisconsindot.gov/Pages/doing-bus/civil-rights/dbe/certified-firms.aspx To access the North American Industry Classification System (NAICS), please go to Business Classifications by NAICS Code: http://www.census.gov/eos/www/naics/

C. Non-Discrimination, Equal Employment Opportunity, and Affirmative Action Goals.

In the performance of work or execution of this contract, the Contractor shall not discriminate against any employee or applicant for employment because of race, color, national origin or ancestry, age, sex, sexual orientation, gender identity and gender expression, disability, marital status, family status, lawful source of income, or status as a victim of domestic abuse, sexual assault or stalking, which shall include but not be limited to the following: employment,



http://www.census.gov/eos/www/naics/

Page 5 of 13

upgrading, demotion or transfer; recruitment or recruitment advertising; layoff or termination; rates of pay or other forms of compensation; and selection for training including apprenticeships. The Contractor will post in conspicuous places, available for employment, notices to be provided by MTS setting forth the provisions of the nondiscriminatory clause. A violation of this provision shall be sufficient cause for MTS to terminate the Contract without liability for the uncompleted portion or for any materials or services purchased or paid for by the Contractor for use in completing the contract.

The Contractor agrees that it will strive to implement the principles of equal employment opportunities through an effective affirmative action program, and will so certify prior to the award of the Contract, which program shall have as its objective to increase the utilization of women, minorities and handicapped persons, and other protected groups, at all levels of employment in all divisions of the contractor's workforce, where these groups may have been previously under-utilized and under-represented. The Contractor also agrees that in the event of any dispute as to compliance with the aforestated requirements, it shall be his/her responsibility to show that he/she has met all such requirements.

The Contractor agrees that it will strive to implement the principles of active and aggressive efforts to assist Milwaukee in meeting or exceeding its overall annual goal of participation of target enterprise firms.

When a violation of the non-discrimination, equal opportunity or Affirmative Action provisions of this section has been determined by MTS Contractor shall immediately be informed of the violation and directed to take all action necessary to halt the violation, as well as such action as may be necessary to correct, if possible, any injustice to any person adversely affected by the violation, and immediately take steps to prevent further violations.

If, after notice of a violation to Contractor, further violations of the section are committed during the term of the Contract, MTS may terminate the Contract without liability for the uncompleted portion or any materials or services purchased or paid for by the Contractor for use in completing the Contract, or it may permit Contractor to complete the Contract, but, in either event, Contractor shall be ineligible to bid on any future contracts let by County.

9. Indemnity

A. The Contractor agrees to the fullest extent permitted by law, to indemnify, defend, and hold harmless, the MTS, and its agents, officers, and employees, from and against all loss or expense including costs and reasonable attorney’s fees by reason of liability for damages including statutory benefits under Workers’ Compensation laws, suits at law or in equity, caused by any wrongful, intentional, or negligent act or omission of the Contractor, or its (their) agents which may arise out of or are connected with the activities covered by this Contract.

B. Contractor shall indemnify and save MTS harmless from any award of damages and costs against

MTS for any action based on intellectual property infringement regarding materials, including, but not limited to, computer programs involved in the performance of the programs and services covered by this Contract.

Page 6 of 13

C. Contractor agrees to indemnify MTS for any amount(s) MTS may be required to repay MTS by virtue of payments made to Contractor by MTS under this Contract that MTS, Milwaukee County, or FTA determines to be overpayments or inappropriate payment.

10. Insurance

Contractor agrees to strictly comply with the insurance requirements set forth on Exhibit I. 11. Liquidated Damages

A. Failure of Contractor to comply with Contract requirements and agreed upon project timeline may result in a liquidated damage being assessed at the time the Contractor invoices MTS. Liquidated damages will be agreed to with awardee.

12. Contract Termination

A. MTS or Contractor may terminate this Contract for any reason, with or without cause, following thirty (30) days written notice. In the event of termination, the MTS will only be liable for programs and services rendered through the date of termination and not for the uncompleted portion or any materials or services purchased or paid for by Contractor for use in completing this Contract.

B. Contractor shall notify MTS in writing, whenever it is unable to provide the required quality or

quantity of programs and services. Upon such notification, MTS and Contractor shall determine whether such inability to provide the required quality or quantity of programs and services will require a revision or early termination of this Contract.

C. Notwithstanding any other right of termination, MTS reserves the right to immediately

terminate, or reduce in scope, its obligations under this contract in the event that the sources of funding to the MTS derived through State or Federal grants or contracts is terminated or reduced. This right of immediate termination for loss of funding applies even if Contractor has not been paid for services previously rendered.

13. Mission Critical Contract

MTS has identified this Contract as critical to MTS’s ability to provide essential services. During the duration of the current COVID-19 pandemic, while there are federal, state, and/or local orders relating to or arising from this pandemic, or during any future pandemic or state of emergency declared during the term of this contract by federal, state, or local governments, Contractor will: a. Dedicate resources to identify and mitigate situations in the workplace or jobsite which may

introduce, expose, or spread COVID-19.

Page 7 of 13

b. Screen employees following current CDC guidelines to verify they have not: : a) Traveled to a Level 2 or 3 Country in the past 14 days, or visited an area that requires self-quarantine because of COVID-19 infection, b) Had close contact (within 6 feet) with anyone known or suspected to have COVID19, c) Exhibited any symptoms (chest or back pain, cough, difficulty breathing) of COVID-19 or had a fever greater than 100.4 in the past 14 days.

c. Educate employees on key CDC recommendations including how employees can protect

themselves and what employees should do if they feel sick.

d. Provide MTS services remotely, to the greatest extent possible.

e. Notify MTS within 24 hours of becoming aware of any employee who has been on site at any MTS building, or in contact with any MTS employee, that has a confirmed or suspected case of COVID-19.

f. Notify MTS immediately if Contractor believes, or has reason to believe, Contractor will be

unable to provide services or goods under this Contract.

g. Agrees that MTS is not responsible for any costs, and will not be invoiced for any incomplete work, if MTS revokes permission for Contractor’s employees to be on MTS property due to that employee exhibiting symptoms of COVID-19, or any other illness.

14. Coordination of Services

Contractor agrees to coordinate its service efforts with other health and human service providers to eliminate unnecessary duplication of services.

15. Modifications

Contractor recognizes the right of MTS to make reasonable modifications in the programs and services purchased under this Contract. Contractor shall be notified in writing 30 days prior to any such modifications.

16. Contract Renegotiation or Revision

A. This Contract may be renegotiated in the event of changes required by law, regulations, court action, or inability of either party to perform as committed in this Contract.

B. This contract may be revised in a written amendment signed by the authorized representatives

of both parties. 17. Independent Contractor

Nothing contained in this Contract shall constitute or be construed to create a partnership, joint venture, or employer-employee relationship between MTS or its successors or assigns and Contractor or its successors or assigns. In entering into this Contract and in acting in compliance herewith, Contractor is at all times acting and performing as an independent contractor duly authorized to perform the acts required of it hereunder.

Page 8 of 13

18. Subcontracts

Assignment of any portion of the services by subcontract is prohibited except upon prior written approval of MTS.

19. Assignment Limitation

This Contract shall be binding upon and inure to the benefit of the parties and their successors and assigns provided, however, that neither party could assign its obligations hereunder without the prior written consent of the other.

20. Prohibited Practices A. During the period of this Contract, Contractor shall not hire, retain, or utilize for compensation, any

member, officer, or employee of the MTS of Aging representing MTS or any person who to the knowledge of Contractor has a conflict of interest. No employee of the MTS on Aging representing MTS shall be an officer, member of the Board of Directors, or have a proprietary interest in Contractor's business.

B. Contractor shall furnish MTS with written disclosure of any financial interest, purchase or lease agreements, employment relationship, or professional services/consultant relationship which any of Contractor's employees, officers, board members, stockholders, or members of their immediate family may have with respect to any supplier to Contractor of goods and services under this Contract.

C. Contractor attests that it is familiar with Milwaukee County's Code of Ethics (Chapter 9 of the

General Ordinances of Milwaukee County) which states in part, "No person shall offer or give to any public official or employee, directly or indirectly, and no public official or employee shall solicit or accept from any person, directly or indirectly, anything of value if it could reasonably be expected to influence the public official’s or employee’s vote, official actions or judgment, or could reasonably be considered as a reward for any official action or inaction or omission by of the public official or employee.”

21. Certification Regarding Contractor Debarment or Suspension

Contractor certifies to the best of its knowledge and belief, that it and its principals; (1) are not presently debarred, suspended, proposed for debarment, declared ineligible, or voluntarily excluded from covered transactions by any Federal MTS or agency; (2) have not within a three-year period preceding this proposal been convicted of or had a civil judgment rendered against them for commission of fraud or a criminal offense in connection with obtaining, attempting to obtain, or performing a public (Federal, State or local) transaction or contract under a public transaction; violation of Federal or State antitrust statutes or commission of embezzlement, theft, forgery, bribery, falsification, or destruction of records, making false statements, or receiving stolen property; (3) are not presently indicted for or otherwise criminally charged by a governmental entity (Federal, State or local) with commission of any of the offences enumerated in (2) of this certification; and (4) have not within a three-year period preceding this contract had one or more public transactions (Federal, state or local) terminated for cause or default.

Page 9 of 13

By: Date: (Signature of Official Authorized to Sign Contract) 22. Certification Regarding Lobbying

Contractor certifies, to the best of his or her knowledge and belief, that: 1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned,

to any person for influencing or attempting to influence an officer or employee of any agency, a member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any federal grant, the making of any federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan or cooperative agreement.

2) If any funds other than Federal appropriated funds have been paid or will be paid to any person

for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with this Federal contract, grant, land, or cooperative agreement, the undersigned shall complete and submit Standard Form-LLL, “Disclosure Form to Report Lobbying,” in accordance with its instructions.

3) The undersigned shall require that the language of this certification be included in the award documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under grants, loans and cooperative agreements) and that all subrecipients shall certify and disclose accordingly.

This certification is a material representation of fact upon which reliance was placed when this transaction was entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by section 1352, title 31, U. S. Code. Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.

By: Date: (Signature of Official Authorized to Sign Contract) 23. Political Activity of Employees

Where applicable, Contractor shall comply with the provisions of the Hatch Act, which limit the political activity of employees who work in federally funded programs.

Page 10 of 13

24. Notices

Notices to MTS provided for in this Contract shall be sufficient if sent by certified or registered mail, postage prepaid, and notices to Contractor shall be sufficient if sent by certified or registered mail, postage prepaid, to the respective addresses stated in this Contract or to such other respective addresses as the parties may designate to each other in writing. Contractor agrees, that in conduct of its meetings, it will be guided by Wisconsin Statutes 19.81 et. seq.

25. Contract Content

The entire Contract of the parties, with all attached exhibits and assurances, together with the relevant BID or Specifications as negotiated is contained herein. This Contract supersedes all oral agreements and negotiations and all writings not herein referred to and incorporated. This Contract may be executed in two or more counterparts, each of which shall be deemed as original.

26. Approval

It is expressly understood and agreed that the parties' obligations hereunder are subject to state approval and federal concurrence with this Contract.

MTS enters into this Contract as authorized under ss. 59.17 (2) (b) 4, 59.255 (2) (e), and 59.42 (2)

(b) 5 Wisconsin Statutes. Contractor enters into this Contract pursuant to and by authority of its

owners/ Board of Directors.

Page 11 of 13

27. AUTHORIZATION.

IN WITNESS WHEREOF, this contract is effective on the date of the last acquired signature. Signer for Contractor warrants they are authorized to sign on behalf of Contractor.

CONTRACTOR

By: _________________________________ Date: _________________________ Signed __________________________________ __________________________

Name Printed Title

Milwaukee Transport Services, Inc

By: _________________________________ Date: __________________________ Signed __________________________________ __________________________

Name Printed Title

Page 12 of 13

Exhibit I

Insurance Minimums Insurance: Contractor agrees to maintain policies of insurance and proof of financial responsibility to cover costs

as may arise from claims for damages to property of and/or claims which may arise out of or result

from Contractors activities, by whomever performed, in such coverage and amounts as required and

approved by MTS. Acceptable proof of such coverage shall be furnished to MTS prior to

commencement of activities under this agreement. A Certificate of Insurance including

declarations page, shall be submitted for review for each successive period of coverage for the

duration of this agreement, unless otherwise specified by MTS, in the minimum amounts specified

below.

Contractor shall provide evidence of the following coverages and minimum amounts: Type of Coverage Minimum Limits Wisconsin Workers’ Compensation and Employer’s Liability & Disease

Statutory/Waiver of Subrogation $100,000/$500,000/$100,000

General Liability Bodily Injury and Property Damage to include: Personal Injury, Fire, Products and Completed Operations


Automobile Liability Bodily Injury and Property Damage All Autos

$1,000,000 Per Accident

Professional Liability Refer to Additional Provision A.1.


Umbrella Liability Policy will follow form to underlying Employer’s, General, and Automobile Liability policies


Milwaukee Transport Services, Inc (MTS) and Milwaukee County shall be named as an Additional

Insured on the General and Automobile L iability policies as respects the services provided in this

agreement. A Waiver of Subrogation shall be afforded to MTS on the Workers' Compensation policy.

A thirty (30) day written notice of cancellation or non-renewal shall be afforded to Milwaukee County.

Page 13 of 13

The insurance specified above shall be placed with a Carrier approved to do business in the State of Wisconsin. All carriers must be A rated or better per AM Best's Rating Guide. Any requests for deviations from or waivers of required coverages or minimums shall be submitted in writing and approved by MTS’s Risk Manager as a condition of this agreement. A.1. Professional Liability – Additional Provision. Contractor agrees to provide additional information on its professional liability coverage as respects policy type, i.e. errors and omissions for consultants, architects, and/or engineers, etc.; applicable retention levels; coverage form, i.e. claims made, occurrence; discover clause conditions, and effective retroactive and expiration dates, to MTS’s Procurement Department as may be requested to obtain approval of coverage as respects this section. It is understood and agreed that coverage which applies to the services inherent in this agreement will be extended for two (2) years after completion of all work contemplated on this project if coverage is written on a claims-made basis.

CAD/AVL and Radio System Specifications

Prepared for Milwaukee County Transit System

by IBI Group & E-Squared Engineering

June 19, 2020

IBI GROUP SYSTEM SPECIFICATIONS DOCUMENT CAD/AVL AND RADIO SYSTEM SPECIFICATIONS Prepared for Milwaukee County Transit System

Document Control Page

June 19, 2020

Client: Milwaukee County Transit System

Project Name: MCTS CAD/AVL and Radio Specifications Writer

Report Title: CAD/AVL and Radio System Specifications

IBI Reference: 125436

Version: 1.1

Digital Master:

Originator: Andrew Schagen, Seth McDermott, Dorothy Liu, Richard Easley;

Gregory De Santis

Reviewer: Michael Mandelzys

Authorization: Doug Parker

Circulation List:

History: 0.9 Draft to MCTS 1.0 Complete Specifications 1.1 Revised based on MCTS comments


Table of Contents

June 19, 2020 i

1 Introduction ......................................................................................................................... 1

2 Background ......................................................................................................................... 2

2.1 The Future of Transit in Milwaukee: MCTS NEXT .................................................. 3

2.2 Existing Computer and Infrastructure Environment ................................................. 4

2.3 Future Computer and Infrastructure Environment ................................................... 5

2.4 Operational Concept ................................................................................................ 6

2.4.1 System Administrator .................................................................................. 6

2.4.2 Dispatch and Transportation ....................................................................... 7

2.4.3 Information Technology .............................................................................. 7

2.4.4 Vehicle Operators ....................................................................................... 7

2.4.5 Maintenance ................................................................................................ 7

2.4.6 Schedule and Planning ............................................................................... 7

2.4.7 Marketing .................................................................................................... 7

2.4.8 Human Resources ...................................................................................... 8

3 Information Technology (IT) Infrastructure Requirements ............................................ 9

3.1 General Requirements ............................................................................................. 9

3.2 Installation .............................................................................................................. 10

3.3 Data Management ................................................................................................. 11

3.3.1 General ..................................................................................................... 11

3.3.2 Production Database................................................................................. 12

3.3.3 Archive Database ...................................................................................... 13

3.3.4 Test Environment and Database (Option) ................................................ 14

3.3.5 Data Ownership ........................................................................................ 15

3.3.6 Data Security ............................................................................................. 16

3.3.7 Data Documentation ................................................................................. 16

3.4 System Performance ............................................................................................. 17

3.5 Disaster Recovery and Redundancy ..................................................................... 17


Table of Contents (continued)

June 19, 2020 ii

4 Wireless Voice and Data Communications .................................................................... 19

4.1 General Requirements ........................................................................................... 19

4.2 On-board Equipment .............................................................................................. 21

4.2.1 Antenna ..................................................................................................... 21

4.2.2 Vehicle Operator Handset and Speakers ................................................. 21

4.3 Commercial Carrier Data Integration ..................................................................... 22

4.4 Mobile Voice Communications (P25 Voice System) ............................................. 23

4.5 Voice over IP Communication (Option) ................................................................. 25

4.5.1 General ..................................................................................................... 25

4.5.2 Onboard .................................................................................................... 26

4.5.3 Performance .............................................................................................. 26

4.6 Yard and Transit Center Communication .............................................................. 27

4.6.1 General ..................................................................................................... 27

4.6.2 WLAN Data Transfer Support Software .................................................... 28

5 Onboard Systems ............................................................................................................. 30

5.1 General .................................................................................................................. 30

5.2 Environment ........................................................................................................... 31

5.3 Electrical................................................................................................................. 32

5.4 Vehicle Logic Unit and Mobile Data Terminal ........................................................ 34

5.4.1 General Requirements .............................................................................. 34

5.4.2 MDT Graphical User Interface (GUI) ........................................................ 37

5.4.3 Safe Driving Mode..................................................................................... 38

5.4.4 Vehicle Operator Logon and Logoff .......................................................... 39

5.4.5 Pre- and Post-Trip Inspection ................................................................... 40

5.4.6 Vehicle Location Tracking ......................................................................... 41

5.4.7 Location Data Management and Reporting .............................................. 43

5.4.8 Voice Call Management ............................................................................ 44

5.4.9 Canned Data Messaging .......................................................................... 45

5.4.10 Wireless Data Communication Gateway .................................................. 47



June 19, 2020 iii

5.4.11 Covert Alarm Switch and Covert Microphone ........................................... 47

5.4.12 Schedule Adherence Management ........................................................... 48

5.4.13 Headway Adherence Management ........................................................... 49

5.4.14 Navigation Assistance ............................................................................... 50

5.4.15 Route Adherence Management ................................................................ 51

5.5 Vehicle Health Monitoring (VHM) .......................................................................... 51

5.6 Supervisor/Support Vehicle Equipment ................................................................. 53

5.7 Test Bench (Option) ............................................................................................... 53

6 Central System .................................................................................................................. 54

6.1 General .................................................................................................................. 54

6.2 Built-in Maps .......................................................................................................... 56

6.3 Data Import/Export and Integration Interfaces ....................................................... 57

6.3.1 Scheduling System Interface .................................................................... 57

6.3.2 Human Resources Management .............................................................. 58

6.4 CAD/AVL System ................................................................................................... 59

6.4.1 CAD/AVL Workstations ............................................................................. 59

6.4.2 Mobile Access ........................................................................................... 60

6.4.3 MDT Logon Verification ............................................................................ 61

6.4.4 Vehicle Location Tracking ......................................................................... 62

6.4.5 Voice Call Management ............................................................................ 63

6.4.6 Data Messaging ........................................................................................ 66

6.4.7 Central Covert Alarm Handling ................................................................. 68

6.4.8 Incident Management and Reporting ........................................................ 69

6.4.9 Vehicle Tracking Interface for External Systems ...................................... 72

6.4.10 Route and Schedule Adherence Tracking ................................................ 72

6.4.11 Headway Management ............................................................................. 74

6.4.12 Service Management ................................................................................ 74

6.4.13 Detour Management ................................................................................. 75

6.5 Data Feeds and Application Programming Interfaces ........................................... 78



June 19, 2020 iv

6.5.1 Schedule Information Data Feed (GTFS) ................................................. 78

6.5.2 Real-Time Information Data Feed ............................................................. 79

6.5.3 CAD/AVL API ............................................................................................ 80

6.5.4 VHM Data API ........................................................................................... 80

6.6 Operational Data and Business Intelligence Reporting ......................................... 81

6.6.1 Operations Reporting Database ............................................................... 81

6.6.2 Data Playback ........................................................................................... 82

6.6.3 Reporting ................................................................................................... 83

7 External Systems Integration .......................................................................................... 89

7.1 General .................................................................................................................. 89

7.2 Odometer ............................................................................................................... 89

7.3 Destination Signage ............................................................................................... 90

7.4 Automated Vehicle Announcement System .......................................................... 91

7.5 Fare System ........................................................................................................... 92

7.6 Onboard Surveillance System ............................................................................... 92

7.7 Battery Charge Monitoring Systems ...................................................................... 94

7.8 Network Management System ............................................................................... 94

8 Project Implementation .................................................................................................... 95

8.1 Project Management .............................................................................................. 95

8.1.1 Project Staff ............................................................................................... 95

8.1.2 System Implementation Plan (SIP) ........................................................... 96

8.1.3 Coordination Meetings .............................................................................. 97

8.1.4 Action Item List .......................................................................................... 98

8.2 System Design ....................................................................................................... 99

8.2.1 General ..................................................................................................... 99

8.2.2 Requirements Review ............................................................................... 99

8.2.3 Gap Analysis ........................................................................................... 100

8.2.4 Preliminary Design .................................................................................. 100



June 19, 2020 v

8.2.5 Final Design ............................................................................................ 102

8.3 Documentation ..................................................................................................... 103

8.3.1 General ................................................................................................... 103

8.3.2 System Configuration .............................................................................. 104

8.3.3 As-Built Documentation .......................................................................... 105

8.4 Installation ............................................................................................................ 105

8.4.1 General ................................................................................................... 105

8.4.2 Onboard Installation ................................................................................ 110

8.5 Training ................................................................................................................ 112

8.5.1 General ................................................................................................... 112

8.5.2 Training Manuals ..................................................................................... 114

8.6 Testing and Acceptance ...................................................................................... 116

8.6.1 General ................................................................................................... 116

8.6.2 Factory Testing ....................................................................................... 118

8.6.3 Mini-Fleet Testing .................................................................................... 119

8.6.4 System Testing ....................................................................................... 120

8.6.5 Burn-in Testing ........................................................................................ 120

9 System Warranty and Support ...................................................................................... 122

9.1 General ................................................................................................................ 122

9.2 System Warranty Coverage ................................................................................. 122

9.3 Repair or Replacement of Faulty Components ................................................... 124

9.4 Systemic Failures ................................................................................................. 126

9.5 Spare Components .............................................................................................. 127

9.6 Software Updates ................................................................................................ 128

9.7 Technical Support and Service Level Agreements .............................................. 129

Appendix A: Glossary .............................................................................................................. 132

Appendix B: Fleet Inventory .................................................................................................... 134

Table B-1: Revenue Bus Fleet (May 29, 2020) ................................................... 134



June 19, 2020 vi

Table B-2: Non-Revenue Vehicle Fleet Supported by Current CAD/AVL (May 29, 2020) ....................................................................................................... 135


List of Figures

June 19, 2020 vii

Figure 1: MCTS 2020 Existing System Map ........................................................................ 2

Figure 2: MCTS 2020 Recommended System Map ............................................................ 3

Figure 3: Existing CAD/AVL System Architecture ............................................................... 5

Figure 4: Future State Operational Diagram ........................................................................ 6


List of Tables

June 19, 2020 viii

Table 1: Requirements Response Codes ............................................................................ 1

IBI GROUP SYSTEM SPECIFICATIONS DOCUMENT

CAD/AVL AND RADIO SYSTEM SPECIFICATIONS


June 19, 2020 1

1 Introduction

The Milwaukee County Transit System (MCTS) is replacing its current Computer Aided Dispatch/Automatic

Vehicle Location (CAD/AVL) system and upgrading its voice communications system. The specifications in this

document define requirements for these systems, and are divided into the following sections:

• Section 2 provides a brief overview of MCTS’s objectives and technical scope of this project;

• Section 3 defines MCTS information technology (IT) requirements;

• Section 4 defines wireless voice and data communications system requirements;

• Section 5 defines on-board systems requirements;

• Section 6 defines central systems requirements;

• Section 7 defines integrations with external systems;

• Section 8 defines project implementation requirements; and

• Section 9 defines warranty and maintenance support requirements.

Please note that Proponents are required to complete the compliance matrix as provided within the document.

Proponents must respond to all tabular items using one of the response codes listed in Table 1. Proposals with

missing, incomplete, or ambiguous responses in the matrix may be deemed non-responsive.

Response Code Definition

F Fully Compliant – Function or feature fully complies with MCTS

requirements. Responses that are marked as fully compliant but are

qualified by exceptions or limitations, etc. in the Compliance Matrix

shall be considered the equivalent of “N” (does not comply).

CM Complies with Modified Requirement – Proponents shall propose

modified requirement language to which they commit to comply. The

“CM” will be equivalent to a response of “F” if MCTS opts to change the

requirement as proposed, or to a response of “N” if MCTS opts to not

change the requirement. If alternate requirement wording is not

proposed in conjunction with a “CM” response, the response shall be

considered “N” (does not comply).

Note: For greater clarity, Proponents are not to provide explanations,

caveats, or functionality descriptions in the compliance matrix.

Responses must be in the form of modified requirement language to

the Proponent is willing to commit if MCTS accepts.

N Does Not Comply – Proponent does not comply with MCTS’s

requirement. Accompanying comments are discouraged.

Table 1: Requirements Response Codes

Proponents are encouraged to reference specific sections and page numbers in the proposal that describe more

fully the features called for in the compliance matrix. If the proposal text conflicts with the requirement language

to which the proposer offers to commit, the requirement language shall govern for system acceptance purposes.




June 19, 2020 2

2 Background

MCTS provides reliable, convenient and safe public transportation services to meet the travel needs of the

community. MCTS strives to make quality service available that people need and use. The objectives in-line with

achieving this mission include the following: maximize ridership, provide service that meets travel demands,

maximize reliability and safety in operations, strive for excellence in job performance, provide a positive work

atmosphere, promote a positive public image, manage in a fiscally responsible manner, enhance internal

cooperation and understanding, and serve as an advocate for public transportation.

In addition to Milwaukee County, MCTS also serves Ozaukee and Waukesha Counties. With over 50 service

routes, MCTS operates 369 fixed route buses out of three garages. The current MCTS system map can be

found in Figure 1. Maintenance is performed at the Fleet Maintenance Garage (1525 West Vine Street), KK

Garage (1710 South Kinnickinnic Avenue) and FDL Garage (3343 West Fond du Lac Avenue); operations are

run out of the KK and FDL garages.

Figure 1: MCTS 2020 Existing System Map




June 19, 2020 3

2.1 The Future of Transit in Milwaukee: MCTS NEXT

MCTS is looking to redesign routes for the future of transit in Milwaukee County. The transit system has served

the people of Milwaukee for generations but as times change, people’s needs change and the transit system

must also adapt to a ‘new’ customer with differing needs. Through a series of public engagement meetings and

stakeholder interactions, MCTS has refined its service plan and proposed the 2020 Recommended System Map,

shown in Figure 2.

Figure 2: MCTS 2020 Recommended System Map




June 19, 2020 4

MCTS NEXT is a new way of looking at transit and making transit easier to use. There are three primary

objectives of MCTS NEXT:

• Faster Service;

• More Connections; and

• Increased Accessibility.

MCTS NEXT is an initiative that requires an increased understanding of ridership, bus routes, fleet management,

vehicle maintenance, improved risk mitigation, and an improved level of visibility of overall operations and

service. To this end, MCTS recognizes that one tool necessary for improved data (and improved decision

making) is an updated transit technology program to modernize the existing and future fleet and management

systems.

2.2 Existing Computer and Infrastructure Environment

MCTS currently operates 393 fixed-route buses with additional orders anticipated in the short-term, including 4-

15 battery electric buses. There are also 30 supervisor, maintenance and support vehicles. The existing

CAD/AVL system uses an older version of OrbCAD as its central system. OrbCAD accepts the following inputs:

• Schedule, route traces, and stop locations (from HASTUS);

• Location requests (from dispatchers);

• Operator names and badges (from human resources); and

• Logon information, messages, and alerts (from the bus via OrbCAD’s onboard system).

OrbCAD is also providing the following feeds (outputs):

• Real time vehicle position and operator logon (to the homegrown MCTS Live Map, where it is merged

with live data from Clever IVN);

• Historical vehicle position and operator logon (to the homegrown MCTS Playback);

• Schedule adherence (to the HASTUS-ATP module for use in schedule refinement);

• Schedule adherence (to dispatcher, for service management);

• Log on/off, accident/incident reports, real time location (to a homegrown reporting system);

• Database access (to Tableau for reports);

• Accidents/incidents (to SAFER);

• Real-time deviation/detour data (to RSA, OrbCAD Route and Schedule Adherence monitoring module);

and

• Schedule adherence (to the bus operator, via OrbCAD’s onboard system).

A diagram of these interfaces is provided in Figure 3.




June 19, 2020 5

Figure 3: Existing CAD/AVL System Architecture

2.3 Future Computer and Infrastructure Environment

The new CAD/AVL system resulting from this procurement will interface with or replace the functionality from

selected existing systems, to provide an increased level of service for all MCTS stakeholders. MCTS currently

utilizes a variety of systems and technologies to meet the needs of its various business units. Existing vendors

whose systems will interact with the new CAD/AVL include:

• HASTUS for schedule import and for returning historical segment travel time data to its ATP module;

• SolarWinds, for its computing network monitoring and performance data;

• Clever Devices, to provide a single-point logon for its automated vehicle annunciation system;

• Tableau, for interactive data visualizations;

• Apollo Video System, for tagging of onboard video data;

• Luminator, to periodically provide content updates to the ODK4 for control of the vehicle destination sign;

and

• Ceridian, to import a list of valid operators daily from the up-to-date staff list.




June 19, 2020 6

Figure 4: Future State Operational Diagram

2.4 Operational Concept

Though not forming part of the contract requirements, this section provides for context an overview for how

MCTS currently anticipates the new system will be used by various positions in the organization.

The CAD/AVL shall be able to operate without daily intervention once the system is installed and operational.

The following functional areas will regularly use the system and have responsibilities once the system is fully

operational: System Administrator, Transportation, Information Technology, Vehicle Operators, Maintenance,

Planning, Risk Management, and HR/Labor Relations.

2.4.1 System Administrator

The System Administrator (SA) will assist the Contractor during the system configuration phase of the project. As

the party with the highest level of system access, the SA will set security parameters, approve system access,

administer passwords, coordinate decisions regarding configuration settings, and ensure standard operating

procedures are in place. The SA will also work with the Contractor to coordinate design and approval of standard

reports.




June 19, 2020 7

On an on-going basis, the SA will perform a regular health check on the system, execute requests for the

download of archive data files, and manage updates and configuration changes.

2.4.2 Dispatch and Transportation

Dispatchers will use the CAD/AVL system to communicate with drivers via voice and text, to monitor vehicle

locations, monitor events (late pull out, schedule/route adherence, etc.), respond to covert alarms, document

and control incidents and incident reports, and complete myriad other functions typical of dispatcher

responsibilities. Occasionally, some SA tasks will be assigned to a dispatcher, as the dispatch office is staffed

during all operating hours while the SA observes only regular business hours.

2.4.3 Information Technology

The Information Technology (IT) department will support much of the SA functionality including regular health

checks, maintaining the communications network, and software configuration. The IT department will liaise with

the Contractor via the support agreement for software bug fixes, server maintenance, and software upgrades.

2.4.4 Vehicle Operators

Operators will have regular interaction with the system, including requests to communicate via Request-To-Talk

(RTT), Priority-Request-To-Talk (PRTT), and Covert Alarms (CA). Operators will also be able to send pre-

defined text messages to dispatchers, and activate pre-defined text/audio messages on the internal signage and

annunciator via integration with the existing Automated Vehicle Announcement (AVA) system. The mobile data

terminal (MDT) onboard the vehicle will inform drivers of their scheduled work, schedule adherence, and other

operational data.

2.4.5 Maintenance

Maintenance will provide ongoing preventative and routine maintenance on the CAD/AVL system components

onboard the vehicles. During the warranty period, Maintenance will partner with the Contractor to prepare for the

turnover of warranty-level support to MCTS. MCTS will work with the Contractor to develop Standard Operating

Procedures (SOPs), refine the set of standard and ad-hoc reports, and communicate with Maintenance and

Transportation staff to identify failed system hardware and software. Appropriate automated reporting will alert

maintenance of failures and other problems with the CAD/AVL to enable proactive maintenance and avoid

failures.

2.4.6 Schedule and Planning

The Planning department will use a feed from the new CAD/AVL system into the HASTUS ATP module to help

build accurate schedules from schedule performance data, as well as to use the reports generated by the new

CAD/AVL system to inform activities like service changes, route changes, and timetable changes. Schedule and

route data are regularly exported from HASTUS to the current CAD/AVL system, and this approach will persist

with the new CAD/AVL. MCTS is upgrading HASTUS from version 2012 to version 2019 by the end of 2020.

2.4.7 Marketing

Marketing will be a key partner in using the new system, especially as they use the real-time information to

interact with customers.




June 19, 2020 8

2.4.8 Human Resources

Human Resources and Labor Relations will provide a feed from the HR system containing a list of active

operators and users with their appropriate titles, for use in role-based security. HR and Labor Relations may also

use data generated by the CAD/AVL for performance review and incident investigation as required.




June 19, 2020 9

3 Information Technology (IT) Infrastructure Requirements

This section outlines functional requirements for IT infrastructure to be used by the proposed solution. This section lists requirements for an MCTS-hosted solution.

3.1 General Requirements

REQ. ID REQUIREMENT TEXT RESPONSE

(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.1.1 The system applications shall fully run in the user

context without requiring elevated permissions or

administrative permissions on the desktop, except for

functionality explicitly defined as having SA-only

privileges.

3.1.2 The software applications shall include context sensitive

help capability, where the results on the help screen are

filtered and customized so as to be relevant to the

application, view, and feature set that the user is

interacting with at the time help is requested.

3.1.3 The Contractor solution shall be compatible with existing

MCTS operating system and database environments,

including the following:

3.1.3.a • Oracle 12.2 with an Oracle Linux 6.5 OS on an

Oracle data appliance;

3.1.3.b • MS SQL server 2017 on Windows Server OS

2019; and

3.1.3.c • Workstations running Windows 10.

3.1.4 All proposed software applications shall support role-

based security.

3.1.5 All software shall be the current version in production at

the time of system acceptance.

3.1.6 All software shall scale without modification to newer,

higher performance hardware, operating systems and

other solution components.

3.1.7 All software shall be modular in design and scalable to

support service expansion. Potential future service

expansion may include new modes, fleet increase to up

to two times the size of the current fleet, faster data

rates, and a wider geographic coverage area within and

outside of Milwaukee County.




June 19, 2020 10


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.1.8 To ensure that MCTS has unrestricted access to and

use of the source code if the Contractor ceases to exist,

ceases to support the application, or otherwise

terminates its relationship and/or ownership to the

product, the Contractor shall:

3.1.8.a • Establish an escrow account that continues to

maintain the exact version of the source code in

operation at MCTS, for MCTS to access in such

an event; or

3.1.8.b • Provide an alternative solution acceptable to

MCTS.

3.1.9 The system shall follow an open architecture or API

model, allowing MCTS to develop system interfaces

independently to enable integration with other internal or

third-party systems. The use of standard network

communication protocols (e.g., Transmission Control

Protocol/Internet Protocol (TCP/IP) and system

interfaces (e.g., open database connectivity (ODBC) for

databases) is required.

3.1.10 The Contractor shall enable MCTS to transfer all

software licenses between physical units, including

servers and all peripheral equipment (such as

workstations and mobile dispatching devices), with no

impact to system performance.

3.2 Installation

This section lists requirements for installing systems in the central environment.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.2.1 The Contractor shall be responsible for providing

hardware for servers, databases, and any required

networking infrastructure to connect with the existing

MCTS network, at a location that MCTS identifies.

3.2.2 Equipment installed in MCTS offices or facilities shall

operate from a nominal line voltage of 110 Voltage

Alternating Current (VAC), within voltage tolerances of

105V – 128V and a frequency range of 57 to 64 Hz.




June 19, 2020 11


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.2.3 All Contractor-provided central system equipment shall

be designed for use in a normal office and transit

Operations Control Center (OCC) environment and

shall maintain specified performance under the

following environmental conditions:

3.2.3.a • Operating temperatures: between +32°F and

+110°F; and

3.2.3.b • Humidity: 10-90% relative humidity, non-

condensing.

3.2.4 Where equipment does not comply with environmental

conditions, equipment shall be protected with

environmentally protected enclosures or cabinets. The

enclosures or cabinets shall internally maintain the

operating environment required by the contained

equipment, under the above required environmental

conditions.

3.3 Data Management

This section defines requirements for data logging, data and database ownership, management, access, documentation, security, performance and maintenance.

3.3.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.1.1 The Contractor shall make all database-related

components (e.g. tables, scripts, extensible markup

language (XML) schema, and related information)

available and fully accessible for use and maintenance

support by MCTS.

3.3.1.2 The Contractor shall use prescribed standards for SQL

Server virtualization to develop and configure their

solutions. These solutions shall be flexible enough to run

in consolidated database environments with other

applications using different schemas and virtualization.

3.3.1.3 All database queries shall be logged for audit purposes.

MCTS shall have the ability to view these logs when

required.




June 19, 2020 12


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.1.4 The online data storage system shall ensure data

integrity in case of storage drive or Storage Area

Network (SAN) failure. This may be achieved through

fail-safe fallback data storage, archiving data, or

restoration of data from an archive while the system is

operating. It shall not be necessary to shut the database

down while performing a successful backup operation

with mirrored storage.

3.3.1.5 The Contractor shall not use the SA account with SQL

server applications.

3.3.2 Production Database


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.2.1 All incoming and outgoing data from the production

system shall be stored in a read-only historical database

for retrieval, analysis, display, printing and playback.

This historical information shall include all data

exchanged between vehicles and OCC (e.g., location

data, route/schedule adherence data, vehicle

logon/logoff data, covert alarms, device alarms, text

messages, and RTT/PRTT call begin and end time) and

all central system user logons and logoffs.

3.3.2.2 The historical database shall enable authorized MCTS

users to retrieve system data for all normal business

functions without having to re-import data from external

storage, and without support from in-house IT staff or the

Contractor. To facilitate this, the historical database shall

have sufficient capacity to retain all data generated by all

systems provided under this contract for a period of at

least two (2) years before archiving would be required.

3.3.2.3 The system shall restrict access to all data within the

historical database to MCTS-designated users in

accordance with MCTS-specified data access policies.

3.3.2.4 The stored data shall be time and date stamped and

shall contain sufficient information to enable selective

sorting and retrieval based on user-specified selection

criteria. At a minimum, the following sorting and

selection criteria shall be supported for accessing the

historical data from both the online and archived storage:

date and time, GPS latitude/longitude, vehicle number,

vehicle operator number, dispatcher ID, run number, and

incident type (where needed).




June 19, 2020 13


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.2.5 Historical database records shall be readily accessible in

a form that is directly accessible or importable into

common database management and analysis tools.

3.3.2.6 A notification or alarm in response to a data error or

event shall be automatically distributed to a configurable

email list. A notification or alarm shall be triggered in

response to the following errors:

3.3.2.6.a • Detection of invalid or erroneous data (i.e. data

corruption), including data import errors from

external systems; and

3.3.2.6.b • Detection of a device or system fault.

3.3.2.7 All alarm notifications, error details, and the actions

taken in their response shall be logged in the database

for later review and archiving.

3.3.2.8 The solution shall support moving the historical database

to another server with no impact to the continuity of

operations or data storage.

3.3.3 Archive Database


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.3.1 The Contractor shall supply a data archiving and archive

retrieval solution. There shall be sufficient space to store

all archived data generated by the provided system for a

minimum of seven (7) years plus an additional fifty (50)

percent for additional data and fleet expansion.

3.3.3.2 The Contractor shall provide a backup and recovery

plan that includes hardware specifications, storage

requirements, and configuration parameters. The

backup and recovery procedures must integrate with the

existing MCTS backup process.

3.3.3.3 The system’s backup and recovery functions shall

enable MCTS to create backup copies of all archive

database content, stored externally from the system.

3.3.3.4 The system shall enable the archive database to be

restored from a backup in case of database crashes.




June 19, 2020 14

3.3.4 Test Environment and Database (Option)

In the event that MCTS exercises the option for the Contractor to supply a test environment and database, the

following requirements shall apply.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.4.1 The Contractor shall implement a test environment, with

all software components installed on duplicate server

hardware at an MCTS-identified location, where

software updates and configuration changes can be

tested.

3.3.4.2 The test environment shall represent the exact system

configuration of the production environment, including

databases, at the time of testing.

3.3.4.3 The Contractor shall test all software and firmware

changes for central and on-board system components

using a hardware test bench setup before installing in

the production system or on vehicles.

3.3.4.4 The Contractor shall install one test bench setup for

permanent use at MCTS.

3.3.4.5 The Contractor shall provide licensing and applications

necessary to establish an independent central system

test environment within the virtual environment.

3.3.4.6 The test environment shall be sufficiently designed to:

3.3.4.6.a • Allow end-to-end testing of:

o All imported scheduling and mapping

data;

o Configuration files;

o Test bench units;

o Virtual or physical OCC workstations;

and

3.3.4.6.b • Provide real-time travel time predictions, real-

time displays, and summary reports.

3.3.4.7 The Contractor shall provide simulations (or alternatively

access to playbacks of actual data) that run within the

test environment and accept input from the test bench

units.

3.3.4.8 The test environment shall include at least one

workstation with voice communications functionality for

testing and training purposes.




June 19, 2020 15


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.4.9 The test environment shall enable MCTS to test voice

communications, including updates and patches to voice

communications software, applications, and settings

prior to transferring this data to the production

environment.

3.3.4.10 The test environment shall provide for setup and

configuration of separate test scenarios where resulting

data is stored and retrievable by MCTS.

3.3.4.11 The Contractor shall supply a test database to support

the test environment.

3.3.4.12 The test database shall store a complete copy of data

from the reporting database used in the production

system, updated at a frequency configurable by MCTS.

3.3.4.13 All data ownership, retention, and access requirements

pertaining to the production historical database shall

apply equally to the test database.

3.3.5 Data Ownership


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.5.1 All data and the database where the data resides shall

be MCTS property and shall be available immediately to

MCTS.

3.3.5.2 MCTS shall be allowed royalty-free access to the

database tables, and royalty-free use of the data and

interfaces. MCTS shall be allowed to extend such

access and use to third party vendors for integration

purposes.

3.3.5.3 Provisions shall be made for enabling MCTS to

integrate the database with other applications, should

MCTS choose. Any security or access concerns related

to the database components shall be clearly identified

(e.g. any specific database tables that are used in real-

time operations should be identified to indicate that

running queries on those tables might impact

operations).

3.3.5.4 Application software shall be transferable to other

workstations using compatible hardware, database

software and operating system without any

modifications or use of hardware keys.




June 19, 2020 16

3.3.6 Data Security


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.6.1 The Contractor shall follow MCTS IT security policies

when the systems are hosted by MCTS, including but

limited to the use of domain security groups, GPOs,

firewalls, monitoring software, and virus protection.

3.3.6.2 All software security shall be provided in accordance

with best practices identified in the National Institute of

Standards and Technology (NIST) Cybersecurity

Framework or an equivalent alternative published

standard from a recognized security-standards body, if

approved by MCTS.

3.3.6.3 Proposers shall provide evidence of security audit of the

proposed solution to verify that proposed solution is free

of security vulnerabilities.

3.3.6.4 Vulnerabilities or exploits the Contractor or others

discover for the proposed application must be reported

to MCTS immediately with a proposed mitigation

strategy.

3.3.6.5 All central system software applications must have the

ability to use Windows Authentication based on the

MCTS Active Directory setup.

3.3.6.6 The Contractor must disclose methods used for

encrypting stored passwords and must employ industry

standard encryption methods using at least 256-bit

encryption techniques.

3.3.7 Data Documentation


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.7.1 The Contractor shall provide the following:

3.3.7.1.a • Scripts to recreate the database;

3.3.7.1.b • An entity relationship diagram;

3.3.7.1.c • A database schema with a data dictionary

detailing all database entities (e.g. tables,

columns, and attributes); and

3.3.7.1.d • A recommended practices document for

supporting and maintaining the database.




June 19, 2020 17


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.3.7.2 The Contractor shall supply the specifications for

dispatcher workstations and monitors, which MCTS will

supply and/or procure.

3.4 System Performance


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.4.1 The Contractor shall provide real-time system

monitoring dashboards configurable by authorized

MCTS users, to enable MCTS staff to monitor the

status of all CAD/AVL software and databases. At

minimum, the system shall track and report on the

following metrics:

3.4.1.a • System availability;

3.4.1.b • System usage (data usage, server usage);

3.4.1.c • System security breaches and attempted

breaches; and

3.4.1.d • System errors (server hardware/software

malfunctions).

3.4.2 The overall system availability (up-time for data and

applications access to all systems implemented under

this contract divided by the total time not including time

scheduled in advance for system maintenance) shall

meet or exceed 99.9%.

3.4.3 In addition to the system self-monitoring, availability

shall be monitored by the MCTS network monitoring

solution and quantified quarterly for compliance.

3.5 Disaster Recovery and Redundancy


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.5.1 The Contractor shall clearly describe its approach for

enabling redundant server configurations in accordance

with MCTS disaster management policy.




June 19, 2020 18


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

3.5.2 The Contractor shall set-up the central system in

redundant configuration by default, so that the

secondary application shall automatically start running if

the primary application fails.

3.5.3 The system architecture shall support at minimum an

active-passive relationship between the production

server, and the production and (optional) test reporting

databases.




June 19, 2020 19

4 Wireless Voice and Data Communications

This section defines hardware and software requirements for voice and data communications between vehicles and control center and vehicle and garage/yard communication equipment.

Included in this section are requirements for integration with the existing P25 radio system in place at MCTS, as well as supplying equipment required to support data communication over a combination of WLAN while in range at facilities and cellular while out of WLAN range.

It is MCTS’ intent to initially operate with radio as the primary voice communication channel and cellular as the primary data communication channel. In future, MCTS plans to transition to fully cellular communications for both voice and data, as existing radio infrastructure piggybacks with other County functions, and sunsetting of this legacy system is anticipated.

To this end, MCTS has defined the supply of cellular VoIP radio as optional, and if the option is exercised, VoIP communication would supersede radio as primary voice communication for the purposes of the contract.

4.1 General Requirements


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.1.1 The Contractor shall interface the CAD/AVL workstation

hardware and software to the existing voice radio

consoles for voice and the public cellular head end for

data.

4.1.2 The interface between the CAD/AVL central software

and the voice radio system central software shall

support the voice radio system auto-selecting the

channel to be used and providing this to the CAD/AVL

system, triggered by a dispatcher selecting to set up a

vehicle voice call using a CAD/AVL dispatcher console.

This will be accomplished using an API from Motorola

that MCTS will provide.

4.1.3 The Contractor shall provide appropriate

communications equipment and applications required to

complete these interfaces in order to satisfy the

following communication needs:

4.1.3.a • One-way and two-way wireless voice and data

communication between the MCTS central

system, and fixed-route vehicles, while located

in yards;

4.1.3.b • One-way and two-way wireless voice and data


system and fixed-route vehicles while within the

MCTS coverage area;




June 19, 2020 20


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.1.3.c • One-way and two-way wireless voice and data


system and supervisor/maintenance/support

vehicles, while located in yards; and

4.1.3.d • One-way and two-way wireless voice and data


system and supervisor/maintenance/support

vehicles, while they are in the field within the

MCTS coverage area.

4.1.4 The primary voice communication path shall be via the

existing P25 radios, and the primary data

communication path shall be via cellular. To support

additional communications paths provided in future or

through optional functionality, assignment of primary

and secondary voice and/or data communication paths

shall be configurable by MCTS.

4.1.5 When multiple cellular data network paths are available

(now or in future, i.e. connections through two separate

SIM cards), the system shall automatically determine

the best path by policy.

4.1.6 Policy for selecting the best path shall be configurable

by MCTS and include, at minimum, the following

parameters:

4.1.6.a • Network availability;

4.1.6.b • Network priority;

4.1.6.c • Time of day;

4.1.6.d • Data type;

4.1.6.e • Bandwidth;

4.1.6.f • Location; and

4.1.6.g • Data plan usage.

4.1.7 Contractor shall identify and provide any additional on-

board and central hardware and software that will be

required to establish wireless communication

infrastructure.

4.1.8 The communications infrastructure provided shall

comply with all applicable local, state, and federal

standards and regulations.




June 19, 2020 21


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.1.9 The Contractor shall perform Wi-Fi coverage tests

during preliminary design within MCTS vehicle garages

and yards, to determine the quality and reliability of Wi-

Fi coverage when vehicles are within the garage/yard.

The Contractor shall make recommendations if

necessary to MCTS for MCTS WLAN coverage

enhancements needed to achieve a minimum signal

strength of -70dBm with a ping of under 80ms

throughout the yard.

4.2 On-board Equipment

4.2.1 Antenna


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.2.1.1 The existing voice radio antenna and feedline to the

existing voice radio shall be retained for each vehicle if

compatible. If new cellular and Wi-Fi antennas are

required, the Contractor shall provide and install, for

each vehicle, a combined omnidirectional roof-mounted

antenna with low-profile fiberglass radome. This new

antenna installation, if required, shall also include the

Global Positioning System (GPS) antenna, for

connection to the new Vehicle Logic Unit (VLU).

4.2.1.2 Antennas shall be designed, installed, and placed such

that any device, whether or not it is designed to transmit

RF, shall not interfere with or degrade the performance

of any other MCTS device or with different components

within the same device.

4.2.1.3 If new cellular and Wi-Fi antennas are required exterior

antenna installation shall not allow for water ingress into

the vehicle under any weather conditions.

4.2.2 Vehicle Operator Handset and Speakers


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.2.2.1 The Contractor shall either supply new or reuse existing

telephone-style handsets with an integral PTT button and

a cradle assembly.




June 19, 2020 22


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.2.2.2 Vehicle operators shall be able to adjust the volume of

the audio at any time during the voice communication.

4.3 Commercial Carrier Data Integration


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.3.1 The Contractor shall be responsible for the following:

4.3.1.a • Integrating and/or providing the Digi WR54

onboard gateway router, cellular and WLAN

modems, with the new Vehicle Logic Unit (VLU)

using Ethernet for data exchange;

4.3.1.b • Performing the installation of any necessary

integration components; and

4.3.1.c • Interfacing the commercial cellular provider

devices with the CAD/AVL central system via

APN-protected internet connection.

4.3.2 The Contractor shall provide a Digi WR54 cellular

gateway router where not already installed to support all

needed on-board interfaces and integrations.

4.3.3 The Contractor's CAD/AVL system shall operate with the

Digi WR54 gateway router to maintain an IPv4 or IPv6

connection with the cellular provider network, and MCTS

WLAN infrastructure. The design of the onboard system

shall not preclude the upgrade of the cellular modem or

gateway router to accommodate emerging technologies,

including 5G.

4.3.4 The Contractor shall incorporate the gateway router into

the equipment installation design for each type of vehicle.

If relocation of existing or installation of new equipment is

required for an appropriate and ergonomic layout,

Contractor will provide all associated materials and labor

necessary.

4.3.5 The Contractor shall provide a method to measure

communications latency between on-board devices and

OCC consoles in both directions. Measured latency in

either direction shall not exceed two (2) seconds,

excluding the latency imposed by the cellular network,

ninety-five (95) percent of the time.




June 19, 2020 23


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.3.6 The full commercial carrier data pathway between the on-

board end devices and central system applications shall

be of sufficient bandwidth to support receiving time-

stamped location updates from every operating vehicle

as frequently as every two (2) seconds.

4.3.7 The onboard system shall support bidirectional

communications with the existing MCTS WLAN

infrastructure as vehicles move within the WLAN

coverage range, including session persistence and

handoff between WLAN access points.

4.3.8 All data communications with vehicles shall be

exchanged as soon as communications capability is

restored, if the vehicle was out of communications when

the message was originated.

4.4 Mobile Voice Communications (P25 Voice System)


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.4.1 The Contractor shall integrate with existing mobile radios

on fixed route, maintenance, and supervisor vehicles.

MCTS will arrange that any new vehicles purchased

during the Contract Period will have mobile radios

preinstalled by the Original Equipment Manufacturer

(OEM) before delivery.

4.4.2 The Contractor shall be responsible for the following:

4.4.2.a • Reviewing the technical requirements, features

and functions of the installed P25 radios and

ensuring that their CAD/AVL system is

compatible with this radio for the purpose of

voice radio integration;

4.4.2.b • Designing voice radio CAD/AVL integration;

4.4.2.c • Planning the integration of existing radios; and

4.4.2.d • Installing necessary interconnecting cables and

power conditioning equipment for voice radio

integration on fixed route vehicles.

4.4.3 The Contractor shall supply, install and test all Audio

Input and Output devices associated with integrating the

existing mobile radios and VLU for fixed-route vehicles.




June 19, 2020 24


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.4.4 Onboard Audio Input and Output devices for general

communication (i.e. excluding the covert microphone)

shall:

4.4.4.a • Have a hook switch, PTT handset and speaker;

4.4.4.b • Use speaker output when the handset is on the

hook; and

4.4.4.c • Use the handset audio output when handset is

off hook.

4.4.5 Audio user-interface devices such as speakers and

handsets shall have volume levels appropriate for typical

public transit environments. The Audio Output speaker

shall have a maximum volume so as not to be heard

beyond the operator area.

4.4.6 Microphone design shall reduce ambient noise levels to

improve transmitted voice quality.

4.4.7 The covert microphone audio input supplied by the

Contractor shall pick up conversational level ambient

voice from the bus front area surrounding the operator

compartment.

4.4.8 MCTS will supply radio manufacturer-specific cables

where necessary. However, the Contractor shall be

responsible for completing the physical and electrical

interface between the mobile radio and VLU. MCTS will

be responsible for applying any firmware updates needed

to the voice radio and any subcontracting for support

services needed from the voice radio vendor.

4.4.9 The integration shall allow for the voice radios to be “hot-

swappable”, that is, in the event of a failure, the radios

can be replaced without having to shut down the VLU or

any other integrated components. Likewise, operators

shall also not be required to log-off.

4.4.10 The CAD/AVL shall notify the vehicle operator visually

and by tone when a call has connected or dropped.

4.4.11 The Contractor shall provide or reuse all necessary radio

user-interface devices and capabilities (e.g., headsets,

microphones, speakers, push-to-talk [PTT] devices) as

required to meet performance requirements.

4.4.12 For fixed-route vehicles, the communication module shall

enable half-duplex functionality.

4.4.13 The communication module within VLU shall manage

interfaces with handsets and speakers and covert

microphone for radio communications.




June 19, 2020 25


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.4.14 For portable radio unit users (e.g., street supervisors),

the CAD/AVL application shall provide One-way and two-

way voice functionality. The application shall provide

options to assign the PTT-function to momentary contact

buttons resident on the smartphones and tablets. Further,

the application shall allow users to select a talk path or

conference session to listen in to an ongoing

conversation.

4.4.15 Contractor-provided equipment shall not introduce more

than 25ms latency into the end-to-end communication

path.

4.5 Voice over IP Communication (Option)

4.5.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.5.1.1 Optionally, the Contractor shall provide on-board and

central VoIP applications for one-way and two-way voice

communications.

4.5.1.2 If this option is exercised, the VoIP system shall become

the primary voice communications path, with P25 voice

radio as fallback. The assignment of primary and

secondary voice communication paths shall still be

configurable by MCTS.

4.5.1.3 When multiple cellular data network paths are available

(now or in future, i.e., connections through two separate

SIM cards), the system shall automatically determine the

best path to provide maximum call quality and stability or

by policy (e.g. via data usage monitoring).

4.5.1.4 The VoIP protocol shall allow creating, modifying and

terminating unicast (two-party) and multicast (multi-party)

voice and data communication sessions from the central

software.

4.5.1.5 The VoIP system shall utilize an audio codec which is

appropriate for high quality transmission of audio over a

wide area network. The codec operation shall be

implemented in dedicated hardware rather than software

on microprocessor, for optimization. Contractor shall

supply a hardware codec module for each fixed route

maintenance, and supervisor vehicle in order to support

the VoIP implementation.




June 19, 2020 26


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.5.1.6 The Contractor shall provide an IP-based recording

system to record all voice communications generated by

the new VoIP solution.

4.5.1.7 The CAD/AVL system shall output the real-time

maintenance and diagnostics data for VoIP, including

status, through an API call.

4.5.1.8 The VoIP system shall use the same user facing

equipment (e.g. handset, headset, volume controls) as

the radio voice communication system.

4.5.2 Onboard


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.5.2.1 For non-revenue vehicles and/or portable users, the VoIP

application shall operate on all smartphones and tablets

using an Android or iOS operating system within two

minor versions from the latest generation.

4.5.2.2 For revenue vehicles, the VoIP system shall enable full

duplex and half-duplex functionality.

4.5.2.3 The communication module within VLU shall manage

interfaces with handsets and speakers and covert

microphone for VoIP communications.

4.5.2.4 The VLU on revenue vehicles shall include a VoIP-

specific communication module to: intelligently process

VoIP requests, generation of VoIP packets using

appropriate codecs and exchange of VoIP packets with

the central VoIP system.

4.5.3 Performance


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.5.3.1 The maximum call setup delay for all VoIP calls shall not

exceed 400 milliseconds, for 95% of calls. Call-setup

delay is calculated from call activation to establishment of

a voice path, not including network latency.




June 19, 2020 27


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.5.3.2 Average end-to-end latency of all VoIP calls shall not

exceed 400 milliseconds (excluding network latency), for

95% of calls. Latency is the sum of digital voice coding

delay, processing delay, transmission delay and routing

delay associated with each call.

4.5.3.3 For calls initiated during regular use by MCTS,

successful call connection maintenance for VoIP-enabled

users shall be greater than 99%, measured monthly.

4.5.3.4 Mean Opinion Score (MOS) for the VoIP system should

meet or exceed a value of 3.8 out of 5 for all

communications, as measured by a representative

sample of 25 regular calls by MCTS and evaluated by

MCTS stakeholders.

4.6 Yard and Transit Center Communication

4.6.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.6.1.1 The Contractor shall provide end to end IP network

communications within and between the various MCTS

locations, including all three garages and the admin

building. The Contractor shall work with MCTS's

IT/Networking group to verify that isolated virtual local

area networks (VLANs) for CAD/AVL data backhaul are

defined and implemented. MCTS will work with the

Contractor to identify VLAN requirements, and MCTS

shall have the ability to extend the VLANs to new

locations as desired.

4.6.1.2 The end to end network communications shall enable

data communications between revenue vehicles, non-

revenue vehicles, central servers, workstations, and

other remote dispatching equipment within the identified

locations.




June 19, 2020 28

4.6.2 WLAN Data Transfer Support Software


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.6.2.1 The WLAN data transfer support software shall manage

WLAN data transfers between vehicles and the central

software.

4.6.2.2 MCTS Personnel shall be able to select or assign the

data/software to be updated, assign it to an individual

bus, subset of buses, or the entire fleet, and specify the

date and time for which the upload/download shall take

place.

4.6.2.3 The CAD/AVL system shall upload/download all of the

required bulk data from/to MCTS vehicles once they

enter into the Wi-Fi coverage area, including:

4.6.2.3.a • Fixed-route schedule data to vehicles;

4.6.2.3.b • Configurations, firmware upgrades, and patches

to vehicles;

4.6.2.3.c • Vehicle Health Monitoring data from revenue

vehicles over J1939; and

4.6.2.3.d • Operational data recorded by the VLU from

revenue vehicles.

4.6.2.4 When the WLAN data transfer software has a download

available for a vehicle that has successfully associated

with a MCTS WLAN access point, the WLAN data

transfer software shall check with that VLU whether it has

already received that download and if not, initiate and

complete that download.

4.6.2.5 File transfers shall be initiated with each vehicle as soon

it has successfully associated with a MCTS WLAN

access point, and shall not be interrupted as long as the

VLU remains on (including for a time period after the

ignition is turned off; see requirement 5.4.1.9).

4.6.2.6 The system shall report in real-time and offline on the

current status of all uploads/downloads (e.g., in progress,

scheduled or completed/failed) for the entire MCTS fleet

at any given point, and for historical uploads/downloads.

For in-process downloads, the system shall provide the

download status.

4.6.2.7 MCTS shall be able to download updates or changes to

fixed-route schedule data prior to the effective service

date. These updates or changes shall be accessible the

first time a vehicle operator logs on for service beginning

from that effective date. The software shall ensure that

no data is deleted prior to successful upload/download.




June 19, 2020 29


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

4.6.2.8 If an upload or download is interrupted, the upload or

download shall resume from the point of disconnect to

prevent retransmitting the portions of the

upload/download that have already been completed.




June 19, 2020 30

5 Onboard Systems This section defines hardware and software requirements for on-board systems for the revenue and non-

revenue fleet.

5.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.1.1 All onboard equipment shall be designed for use in the

transit industry, with specific attention to ergonomics,

reliability, efficiency, and safety of all system users. The

Contractor shall be responsible for demonstrating and

documenting these design considerations.

5.1.2 Interruption of a configuration data download/transfer

shall not cause a failure of the onboard equipment,

corruption of data, or prevent such equipment from being

fully functional.

5.1.3 Operation of onboard equipment shall not affect or be

affected by any vehicle components, such as engine

ignition, or other onboard equipment including vehicle

power supplies, radios, automatic vehicle identification

systems, fare collection systems, onboard video

surveillance and onboard data collection and processing

equipment.

5.1.4 For onboard equipment, protection shall be provided

against radio frequency interference (RFI) and

electromagnetic interference (EMI) emission sources, as

well as internal conductive or inductive emissions. The

Contractor shall be responsible for demonstrating RFI

and EMI compliance to an accepted standard such as

ISO/IEC and IEEE.

5.1.5 The onboard equipment shall have light emitting diode

(LED) indications for power and circuit breakers.

5.1.6 All onboard systems shall be fully operational within one-

hundred and twenty (120) seconds of ignition on.

5.1.7 The Contractor shall include provisions to protect all

onboard and publicly-accessible equipment and

components from common vandalism, unauthorized

access and physical abuse as may be expected on

transit vehicles and at stops. The Contractor is

responsible for documenting and demonstrating these

provisions.

5.1.8 Onboard equipment shall not pose a hazard to MCTS

staff or passengers when operated in accordance with

manufacturer recommendations.




June 19, 2020 31


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.1.9 Equipment modules, cables, mounting hardware, and

connectors shall not interfere with the operation of

existing onboard equipment.

5.1.10 Onboard equipment shall include hardware circuitry and

software functionality to automatically reboot or restart an

onboard device in the event of a software or hardware

freeze, crash or process failure.

5.1.11 Logged data shall be stored in non-volatile memory, and

shall not become corrupted due to any power condition,

including: spike, drop, or loss.

5.1.12 Data shall not be corrupted due to short-term power

interruptions (e.g., vehicle start-up or power-down),

including complete loss of vehicle power.

5.1.13 System operation shall not be interrupted due to

intermittent power loss or voltage drops.

5.1.14 All equipment shall be compliant with applicable sections

of Title 47 of the Code of Federal Regulations (CFR) Part

15 of Federal Communications Commission (FCC) rules

and regulations regarding radio frequency devices and

shall be designed to operate in a transit environment.

5.1.15 The Contractor shall guarantee a minimum ten (10) years

of availability of devices for replacement or fleet

expansion. Newer versions of devices may be supplied,

provided that they are backwards compatible with

existing devices and systems.

5.2 Environment


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.2.1 Unless otherwise approved by MCTS, Onboard

equipment shall meet the following environmental

specifications:

5.2.1.a • Operating temperatures between -30°F (-34°C)

and 140°F (60°C) for exterior equipment;

5.2.1.b • Operating temperatures between 32°F (0°C) and

110°F (+43°C) for interior equipment;

5.2.1.c • Storage temperatures between -40°F (-40°C) to

158°F (+70°C);

5.2.1.d • Relative humidity, non-condensing between 10%

to 90%;




June 19, 2020 32


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.2.1.e • Shock: 18g of 2 milliseconds;

5.2.1.f • Operating vibration: three-axis 10-500 Hz per

SAE 1455 or approved equivalent standard; and

5.2.1.g • Endurance vibration: three-axis 28-800 Hz per

SAE 1455 or approved equivalent standard.

5.2.2 Unless otherwise approved by MCTS, onboard

equipment, including all exterior connectors and exposed

ports, shall be rated for IEC IP 54 or better for interior

equipment and IEC IP 66 or better for exterior equipment

and designed for use in a mobile environment subjected

to dirt, water, oil, and cleaning solvents.

5.2.3 Where compliance with the environmental specifications

presented here is not achievable for particular

equipment, the equipment shall be shielded within

environmentally-protected enclosures or cabinets that

comply with said environmental specifications, while

maintaining the necessary operating conditions for the

equipment within.

5.3 Electrical


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.3.1 Onboard wiring and cabling shall meet the following

requirements:

5.3.1.a • The Contractor shall be responsible for the

provision of all wiring, cabling, connectors, and

terminations;

5.3.1.b • Wire dress shall include strain relief and allow

sufficient slack on either end of a cable for re-

termination if needed at a future date;

5.3.1.c • All terminations and cables shall be clearly

indexed, labeled and schematically identifiable;

5.3.1.d • Where components must be connected to each

other through individual wires, the wiring shall be

incorporated into a wiring harness;

5.3.1.e • For onboard equipment, all wiring and cables

shall be protected against abrasion and

moisture/dirt ingress. All openings to provide

cable pass through shall be sealed after

installation; and




June 19, 2020 33


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.3.1.f • Provisions shall be included to protect against

incorrect cable connections in the event

equipment is removed and replaced.

5.3.2 All in-vehicle equipment shall incorporate power

conditioners/filters.

5.3.3 The Contractor shall protect equipment inputs and

outputs to absorb “routine” electrostatic discharges, over-

voltages, and reverse polarity conditions. In the event of

“extraordinary” conditions, the Contractor shall design

equipment to sacrifice inexpensive and easily identifiable

components when necessary to protect more expensive

components or those less easy to troubleshoot.

5.3.4 Devices shall not freeze up in the event that power is

applied in the incorrect order (ignition sense versus

continuous power on the load side of the master switch),

or due to short-term power interruptions (e.g., vehicle

start-up or power-down), including complete loss of

vehicle power.

5.3.5 Onboard components shall operate at a nominal +12.5

volts direct current (VDC) or +24 VDC, and be fully

functional within operating supply voltage ranges of +9

VDC to +32 VDC. Voltages shall be measured at the

power connector to the device.

5.3.6 The equipment shall be tested and proven capable of

withstanding power transients, electromagnetic

interference and radio frequency interference without

degradation at levels encountered in typical transit

operations.

5.3.7 The Contractor shall securely mount onboard equipment

in the vehicle’s interior, clear of obstructions and

interference-generating devices. The Contractor shall

collaborate with MCTS staff to determine the installed

location of onboard components.

5.3.8 Cabling to all roof or exterior mounts shall incorporate a

drip loop.

5.3.9 The Contractor shall identify the power requirements

including start-up and operation for all equipment to be

installed on vehicles.




June 19, 2020 34

5.4 Vehicle Logic Unit and Mobile Data Terminal

This section provides hardware requirements for operator terminal and the vehicle processing units that will

provide on-board CAD/AVL and other functions. The operator terminal is referred to as MDT and the processing

unit is referred to as VLU.

5.4.1 General Requirements


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.1.1 The VLU shall act as the central processor, data

storage, and device manager for all onboard devices.

5.4.1.2 The VLU shall initialize and control all devices supplied

under this contract, along with the destination sign and

voice communications system.

5.4.1.3 The VLU and MDT will operate using the latest version

of the OS, and the Contractor shall demonstrate that the

OS supplied will have a minimum of five years support

according to supplier information.

5.4.1.4 The VLU shall allow for maintenance reset without

opening the equipment enclosure.

5.4.1.5 The VLU and MDT shall allow for remote reset and

configuration without being on the bus or within Wi-Fi

range.

5.4.1.6 The VLU shall include physical ports, sufficient

processing capacity, and storage capacity for all

functions of the proposed onboard components.

5.4.1.7 All storage for on-board devices shall be solid-state.

5.4.1.8 The VLU shall include a standard port to connect an

external portable computing device for manual data

configuration using provided utility software.

5.4.1.9 The VLU and MDT shall turn on automatically when the

vehicle power is turned on and shall shut down at an

MCTS-configurable time after the vehicle power is

turned off. The VLU and MDT shall remain turned on for

up to forty-five (45) minutes after vehicle power is turned

off.

5.4.1.10 The VLU and MDT shall automatically reboot after a

fatal error. All such actions shall be automatically

recorded in VLU logs and shall not be overwritten until

downloaded.

5.4.1.11 The VLU and MDT shall use non-volatile memory so

that regardless of the amount of time that power is lost

onboard a vehicle, data stored in the VLU and MDT

shall not be affected.




June 19, 2020 35


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.1.12 The VLU shall provide the master time sync available to

all other devices based on time available from MCTS

time server, as obtained at the time of logon. The VLU

time should be synchronized at least daily.

5.4.1.13 The VLU shall monitor and log the following existing

discrete external circuits, where available by vehicle

type:

5.4.1.13.a • Odometer;

5.4.1.13.b • All door contacts;

5.4.1.13.c • Battery status;

5.4.1.13.d • Kneeling function;

5.4.1.13.e • Lift or ramp deploy, and return from deploy

(stow);

5.4.1.13.f • Bicycle rack use;

5.4.1.13.g • Stop request activation;

5.4.1.13.h • Headlight activation and deactivation;

5.4.1.13.i • Turn signals, activation and deactivation;

5.4.1.13.j • Hazard lights, activation and deactivation;

5.4.1.13.k • Master-run switch status and change in status

(off, day-run, night-run, park);

5.4.1.13.l • Ignition, activation and deactivation; and

5.4.1.13.m • Covert alarm use.

5.4.1.14 The VLU shall include physical and software interfaces

or multiplexer modules to connect to the vehicle CAN(s)

where needed to receive required discrete inputs.

5.4.1.15 The VLU shall, when connected to MCTS WLAN, check

for and download bulk data files containing service,

operator assignment, and other from the central

computer system. Capacity shall be provided to allow for

storage of at least three (3) full schedule changes of

data. Provisions shall be included to restrict the size of

downloads transmitted during log-in to avoid pull-out

delays.

5.4.1.16 The VLU shall provide a versioning mechanism for files

to be wirelessly downloaded to the vehicle, but for the

VLU to delay implementation of the file until some later

date. Any stored version may be initiated and made

current at any time, when scheduled or requested by the

system administrator.




June 19, 2020 36


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.1.17 The VLU shall store accumulated data in a non-volatile

memory with capacity to hold at least thirty (30) days of

data assuming 24 revenue hours per day.

5.4.1.18 The VLU shall allow a maintenance staff person to

manually access and download stored data during a

communications or other hardware failure as a

redundant back-up option. This may be accomplished

using a service laptop connected to a USB port or using

removable media. If removable media is used, the VLU

operating system must not reside on the same

removable media as other data.

5.4.1.19 The VLU shall automatically log and report faults or

failed communications with all on-board devices

integrated to the VLU.

5.4.1.20 The VLU fault logs for integrated devices shall be

available at vehicle start-up and end of operating period

or upon request from the MCTS system administrator.

5.4.1.21 The MDT shall contain a speaker and tone generator to

be used to provide audio alerts. The MDT shall include a

volume control for these functions that is accessible to

the operator.

5.4.1.22 MDT brightness and volume settings shall be

configurable including pre-defined defaults and pre-

defined limits, both globally by authorized MCTS users,

and within the global limits by individual operators. All

settings modified by operators shall return to their

default values when a different operator logs onto the

MDT.

5.4.1.23 The MDT shall automatically switch between daytime

and nighttime brightness and display settings based on

visible light for the bus. This function shall allow for

operator override.




June 19, 2020 37

5.4.2 MDT Graphical User Interface (GUI)

This section lists requirements for the visual look and feel of the vehicle operator terminal.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.2.1 The GUI shall include general function menus and

context-sensitive menus for specialized functions, where

available options are customized so as to be relevant to

the application, view, and feature set that the user is

interacting with. The menus shall be customizable by

MCTS.

5.4.2.2 The MDT operator terminal shall use a color backlit

display that the vehicle operator can read from the

seated position under the full range of ambient

illumination conditions. This includes capabilities such as

vehicle operator-controlled brightness/contrast control,

anti-glare coating, and adjustable orientation mounting.

5.4.2.3 The MDT shall be equipped with a color, liquid crystal

display (LCD) touch-screen that meets the following

requirements:

5.4.2.3.a • Able to be used by operators wearing gloves;

5.4.2.3.b • Readable by operators wearing polarized lenses;

5.4.2.3.c • Sufficient brightness to be readable in direct

sunlight;

5.4.2.3.d • Dimmed or night mode operation;

5.4.2.3.e • A minimum size of 7 inches as measured

diagonally; and

5.4.2.3.f • A minimum resolution of 800x600 pixels.

5.4.2.4 The color combination to be used on the MDT terminal

shall provide legibility for people who are color blind.

5.4.2.5 The MDT display shall include functionality to display

both text and icon-based messages and key labels.

5.4.2.6 The MDT display shall include functionality to display

different font sizes, icons, colors, and styles on the

screen.

5.4.2.7 The operator terminal shall be operated using touch

screen programmable buttons with visual and audible

feedback.

5.4.2.8 The MDT shall notify the operator about data

communication connectivity status through a distinct

symbol on the operator screen.




June 19, 2020 38


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.2.9 The MDT shall notify the operator about GPS

connectivity status through a distinct symbol on the

operator screen.

5.4.2.10 The operator shall not be able to manually shut off or

disconnect the operator terminal power or manually shut

down the MDT application software.

5.4.2.11 If tactile buttons are present on the MDT, then they shall

be reconfigurable to various uses with appropriate labels

without limitation.

5.4.2.12 The MDT shall allow messages from OCC to appear on

the primary display such as detour or service adjustment

messages (if so configured) and be cleared through

vehicle operator acknowledgement or configured display

duration.

5.4.2.13 The MDT shall allow the operator to reach any

messaging function (e.g. read message, view message,

confirm message, etc.) within two buttons presses.

5.4.3 Safe Driving Mode

This section lists requirements for activating a safety mode on the screen to deter vehicle operators from

interacting with MDTs when the vehicle is in motion.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.3.1 For safety, the MDT shall have a safe driving mode

enabled when the vehicle is moving above an MCTS-

configurable speed limit (e.g., 5 miles/hour) for an MCTS-

configurable amount of time (e.g., 5 seconds).

5.4.3.2 The MDT shall allow MCTS to enable the following

screen configurations under safe driving mode:

5.4.3.2.a • Blank display on the screen;

5.4.3.2.b • Disabled MDT buttons to limit vehicle operators

from performing actions on the screen; and

5.4.3.2.c • Display of information relevant to vehicle

operators when of high priority (e.g., route and

schedule adherence status, missed messages or

calls from dispatcher).

5.4.3.3 All screen configurations shall support continued use of

EA, PRTT, and RTT functions during safe mode if

configured by MCTS.




June 19, 2020 39


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.3.4 All screen configurations shall support continued use of

turn-by-turn navigation functions during safe mode if

configured by MCTS.

5.4.3.5 MCTS shall have the ability to remotely change

configurations for the safe driving mode. This ability will

be limited to a select set of users that can be defined and

configured by MCTS.

5.4.3.6 MCTS shall be able to change the safe driving mode

configurations by vehicle operator login. For example, the

safe driving mode could be disabled for maintenance or

training purposes.

5.4.4 Vehicle Operator Logon and Logoff


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.4.1 The VLU shall allow vehicle operator logon using

operator ID and block/run ID entry. The VLU shall check

with the central system to validate that the operator ID

and block/run ID are valid and not already in use. In the

event of a conflict, the system shall notify the vehicle

operator of an “invalid” logon.

5.4.4.2 Once it validates the operator and block/run IDs, the VLU

shall select the schedule data stored in the VLU

corresponding with that block/run to complete the logon.

5.4.4.3 After logon, the MDT shall display the current block/run,

route, trip, next time point, and vehicle operator ID for

fixed-route operations. Also, the MDT shall provide

access to the operator paddle (the full work assignment

for the operator’s shift) based on logon information.

5.4.4.4 The VLU shall provide for automatic notification of the

central system if a vehicle is in service but not logged on,

and shall provide for remote logon by OCC if the vehicle

operator has not logged on.

5.4.4.5 The MDT shall include a log-over feature to allow a new

operator to login directly as the replacement operator for

the current block.

5.4.4.6 The MDT shall allow the vehicle operator to logoff by

selecting the logoff key.

5.4.4.7 The VLU shall send a message to the dispatcher as a

confirmation of the vehicle operator logoff.




June 19, 2020 40


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.4.8 The VLU shall automatically log the vehicle off after a

MCTS-configurable time has passed once the vehicle

has been detected as having returned to the garage, if

the operator has not already completed a manual logoff.

5.4.4.9 The VLU shall periodically attempt to send a logon or

logoff message until it receives an acknowledgement

message from the central system. If no response was

received from the central system within an agency

configurable time, the MDT shall provide the operator

with a “no logon response” message.

5.4.4.10 The VLU shall validate vehicle operator logon to verify if

the vehicle operator logging on to the MDT is valid

according to vehicle operator/vehicle assignment. In the

event of a violation, the system shall display “invalid

logon” error but shall allow the vehicle operator to logon

and report the violation to the dispatcher as an exception.

5.4.4.11 The system shall allow the operator to lock out the MDT

without logging off, to prevent unauthorized access

anytime the operator is away from the bus (for instance,

on break at a layover).

5.4.5 Pre- and Post-Trip Inspection


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.5.1 Upon successful logon, the MDT shall display

configurable pre-trip inspection screens that shall be filled

in by the vehicle operator after conducting their pre-trip

inspection of the vehicle. Activation of this feature shall

be a configurable parameter that MCTS can choose

when to use.

5.4.5.2 As part of the pre-trip inspection, functionality shall be

provided to test all on-board components and

integrations provided under this contract.

5.4.5.3 The system shall record results of the pre- and post-trip

inspections to be conducted by vehicle operators.

5.4.5.4 The Contractor shall design the inspection forms in

coordination with MCTS to be consistent with existing

inspection processes.




June 19, 2020 41


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.5.5 The inspection forms shall provide the capability for

vehicle operators to record their “electronic signatures.”

The system shall record the vehicle operator id, vehicle

id, and date and time of form completion once form is

electronically signed. The system shall provide a prompt

on the MDT screen for vehicle operators to confirm all

input before the report is finally submitted.

5.4.5.6 All inspection data shall be uploaded automatically to the

central system in real-time, and available to authorized

staff to review as needed. MCTS will decide at the time of

design review on what other inspection items shall be

displayed on the dispatcher screen or available for offline

reporting.

5.4.5.7 Prior to log off, the MDT shall display a configurable post-

trip inspection screen that shall be filled in by the vehicle

operator after conducting the completion of a run.

Activation of this feature shall be a configurable

parameter that MCTS can choose when to use.

5.4.6 Vehicle Location Tracking

This section lists hardware and software requirements for tracking revenue and non-revenue fleet with GPS

receivers built into the on-board units. When GPS receivers are not available, alternate methods such as dead

reckoning will be used.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.6.1 GPS receivers used by the VLU shall be designed for

operation in downtown urban, suburban, and rural areas,

including the ability to continue logical vehicle position

tracking when a GPS signal is not available or is

degraded. This could include, but is not limited to,

environments such as mountainous areas, heavily

forested areas, office tower "Urban Canyons", tunnels,

multimodal transit centers, garages and transit yards.

5.4.6.2 The VLU shall compute the vehicle position, speed, and

direction based on multiple positioning systems and

inputs including the following:

5.4.6.2.a • A wide area augmentation system (WAAS)-

enabled GPS receiver; and

5.4.6.2.b • A dead-reckoning system including at minimum

odometer and other gyroscopic sensors.




June 19, 2020 42


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.6.3 The GPS Receiver shall be integrated with the GPS

Antenna to continuously gather signals from available

GPS satellites.

5.4.6.4 The GPS Receiver shall in response to a command from

the VLU report absolute location (latitude, longitude),

speed, time, direction of travel (heading) and whether the

receiver has a GPS position lock.

5.4.6.5 The GPS Receiver shall be at least a sixteen-channel

parallel tracking receiver that simultaneously tracks at

least eight GPS satellites in the best available geometry,

while also tracking at least the four next best and/or

upcoming (rising) satellites.

5.4.6.6 The GPS Receiver shall include multi-path rejection

capabilities to help eliminate spurious signals caused by

reflections of buildings, other structures, or natural

features.

5.4.6.7 The GPS Receiver must use WAAS, providing position

accuracy within ten feet (or three meters) 95 percent of

the time.

5.4.6.8 The GPS receiver shall have a cold start solution time of

120 seconds or less.

5.4.6.9 The GPS receiver shall have a warm start solution time

of 45 seconds or less and a re-acquisition time of 15

seconds or less.

5.4.6.10 The GPS Receiver shall instantly report loss of its GPS

lock to the VLU. The GPS Receiver shall also report the

loss of WAAS service to the VLU.

5.4.6.11 The GPS Receiver shall be able to calculate and provide

an accurate position fix within five (5) seconds of signal

re-acquisition.

5.4.6.12 The GPS equipment’s velocity measurements shall be

accurate to within 0.3281 feet (0.1 meters) per second.

5.4.6.13 The GPS antenna shall be securely mounted on the

vehicle’s exterior. The antenna, mounting and sealants

shall be impervious to physical and chemical damage by

automatic bus washing equipment, and inclement

weather and environmental conditions experienced in the

Midwest region.

5.4.6.14 If location data is not available from the GPS receiver,

the VLU shall be able to calculate vehicle location based

on the dead reckoning system.




June 19, 2020 43

5.4.7 Location Data Management and Reporting


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.7.1 The VLU shall compute and update onboard vehicle

position information every one (1) second or less and

shall provide that position information to other onboard

devices as needed.

5.4.7.2 Vehicle location computation lag time shall not exceed

one (1) second (lag time is defined as the time to

compute position information, correct it, and update the

onboard system).

5.4.7.3 Location data shall be sufficiently precise to accurately

and reliably identify the location of each vehicle on the

street network. Vehicle location shall be accurate to

within 10 feet 97% of the time.

5.4.7.4 The VLU shall provide position reports to the central

system as follows:

5.4.7.4.a • Routine position reports shall be provided every

5 seconds while the vehicle is in operation,

regardless of whether it is logged-on or not;

5.4.7.4.b • Event-based position reports shall be provided

every time the vehicle passes a stop or time-

point, regardless of whether the vehicle stops or

not; and

5.4.7.4.c • At transit centers, position reports shall be

provided when the vehicle enters the transit

center, when it arrives at the designated bay,

when it departs the bay, and when it leaves the

transit center.

5.4.7.5 All transmitted data shall be stamped with the following

information: date and time, “GPS lock” status, latitude

and longitude, heading, block and run number, vehicle

number, and vehicle operator ID number.

5.4.7.6 The VLU shall store the most recent location received

from the GPS receiver.

5.4.7.7 The VLU shall alert OCC if a logged-on vehicle has not

moved between a number of successive location reports.

The threshold for successive location reports shall be


5.4.7.8 The VLU shall support MCTS-configurable trigger points

(e.g. for use at transit centers, layovers, and other MCTS

defined locations) where system actions could be

programmed based on the vehicle being detected at the

trigger point, and any combination of the following:




June 19, 2020 44


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.7.8.a • Route;

5.4.7.8.b • Direction;

5.4.7.8.c • Schedule adherence; and

5.4.7.8.d • Remaining layover.

5.4.7.9 The level of precision available for trigger points shall be

sufficient to distinguish separate lanes and bus bays with

99% accuracy.

5.4.7.10 The VLU shall be able to distinguish with 99% accuracy

the difference between a next trip departure and a

maneuver repositioning within the transit center or

layover area and shall properly assign related data to the

actual start of trip.

5.4.7.11 The VLU shall retain information from the start and end

of the trip and assign passenger counts and times based

on door open actions and time, if does not detect that it

has started the route until it has passed stops along the

trip pattern.

5.4.7.12 If the VLU does not detect that it has arrived at the first

stop of the trip, it will create a special flag that is passed

to and stored in the central system for data analysis.

5.4.8 Voice Call Management

This section provides requirements for initiating and completing radio sessions using CAD/AVL software.

Detailed information on radio hardware and software is provided in Section 4.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.8.1 The MDT shall provide Request to Talk (RTT) and

Priority Request to Talk (PRTT) buttons to allow the

vehicle operator to ask a dispatcher to set up a voice call.

5.4.8.2 When OCC enables a one-way voice call to one or more

vehicles, the MDT shall provide a distinct audible tone

and visual alert. The audio shall be routed through the

vehicle operator speaker; if the operator picks up the

handset, the audio shall instead be routed through the

handset.

5.4.8.3 When OCC enables a two-way voice call to the vehicle,

the MDT shall provide a distinct and visual alert tone. The

audio will be routed through the handset once the vehicle

operator picks up the handset audio, until the end of the

timed voice call after which the MDT shall automatically

end the voice call.




June 19, 2020 45


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.8.4 When the vehicle operator hangs up the handset during a

two-way voice call, the MDT shall detect it and the voice

call shall end. The MDT shall send a data message to

notify OCC that the voice call has ended.

5.4.8.5 A dispatcher shall have the ability to end a timed voice

call at any time while the call is in progress.

5.4.8.6 At any time while the MDT is on, the MDT shall allow the

operator to adjust the voice communications system

speaker volume within a range configurable by

authorized MCTS administrative users. The MDT shall

not enable the operator to mute the speaker audio.

5.4.9 Canned Data Messaging

This section provides requirements for sending pre-configured data messages as stored on the MDTs.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.9.1 The MDT shall not allow vehicle operators to send or

view a canned data message when the safe driving mode

is enabled on their vehicles.

5.4.9.2 The MDT shall allow the vehicle operator to select from a

set of pre-defined messages to send a canned data

message to the central system. All canned messages to

OCC shall include the date, time, location (latitude and

longitude), vehicle ID and vehicle operator ID.

5.4.9.3 The MDT's pre-defined messages to OCC shall include:

5.4.9.3.a • Logon/Logoff/System test/Maintenance;

5.4.9.3.b • Critical messages;

5.4.9.3.c • Vehicle status report (on time, early, late, on

route, off route);

5.4.9.3.d • Call for a field supervisor;

5.4.9.3.e • Vehicle mechanical problem; and

5.4.9.3.f • Capacity for a minimum of fifty (50) other routine

or "canned" messages.

5.4.9.4 The MDT canned messages shall allow a minimum of

three different message sets based on vehicle types (e.g.

supervisor, maintenance, fixed route bus, BRT).




June 19, 2020 46


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.9.5 Canned messages shall be able to be grouped into a

minimum of two levels allowing some message

categories to contain specific sub-options for canned

messages.

5.4.9.6 The system shall allow MCTS staff to add, edit, delete, or

reorder the listing of canned data messages to be stored

on MDT without Contractor assistance or intervention

using Contractor provided tools/software.

5.4.9.7 The MDT shall be able to display free form text

messages from OCC up to at least 254 ASCII characters

in length per page, and shall paginate longer messages

at appropriate word and sentence boundaries.

5.4.9.8 The VLU shall store up to a configurable number (e.g.

100) of canned data messages received from OCC,

indicate to the vehicle operator when there are unread

text messages, and allow stored messages to be viewed

or deleted. The MDT shall allow the vehicle operator to

view received messages that are longer than can fit on

one line of the display.

5.4.9.9 The MDT shall allow the vehicle operator to send the

following responses to certain messages received from

the central system:

5.4.9.9.a • Acknowledgement; and

5.4.9.9.b • Yes/No.

5.4.9.10 The MDT shall periodically attempt to send a canned

data message or response until it receives an

acknowledgement message from the central system.

5.4.9.11 The MDT shall issue separate and distinct audible tones

and visual alerts to:

5.4.9.11.a • Indicate that inbound messages from OCC have

been received; and

5.4.9.11.b • Confirm that outbound messages to OCC have

been sent.

5.4.9.12 Messages received by the MDT shall be displayed to the

user in a large typeface readable by a user with 20/20

eyesight from a distance up to three (3) feet.

5.4.9.13 The MDT shall indicate when there are unviewed

messages in the incoming message queue and how

many messages are in that queue. The MDT shall allow

the operator to view a message in the queue, delete a

message from the queue only after it has been viewed, or

send an acknowledgement if required upon viewing the

message.




June 19, 2020 47

5.4.10 Wireless Data Communication Gateway

This section lists requirements for the central component that will act as a message gateway between the

vehicle and central systems.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.10.1 The VLU shall use wireless data communications through

the cellular or WLAN modem to send and receive

messages with the central software at any time.

5.4.10.2 The data protocol used for transmission shall

accommodate the required functionality for up to at least

400 vehicles at a 5-second polling interval.

5.4.10.3 The VLU shall store data if communications are

interrupted and forward data to the central system once

communications are restored.

5.4.11 Covert Alarm Switch and Covert Microphone

This section lists requirements for covert alarm activation and VLU support for related necessary actions and

clearing of the event.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.11.1 The covert alarm switch mounted at a location that can be

easily pressed by the operator in a discreet manner but

unlikely to be accidently activated (e.g. surrounded by a

guard ring that still allows the button to be pressed from

above).

5.4.11.2 Pressing the covert alarm switch shall allow the VLU to

activate the covert microphone. The VLU shall begin

recording audio via the covert microphone within one (1)

second, and the dispatcher shall be able to hear the audio

feed within three (3) seconds of the covert alarm switch

being pressed.

5.4.11.3 Vehicle vibration shall not activate the covert alarm switch.

5.4.11.4 The VLU shall be equipped with a covert microphone

having adjustable orientation and sensitivity.

5.4.11.5 The VLU shall detect if the covert alarm switch circuit is

closed for at least one second and automatically send an

alarm message to the OCC and place the VLU into covert

alarm mode.

5.4.11.6 The VLU shall allow OCC to activate audio transmission

from the covert microphone but only after the vehicle

operator has activated the covert alarm.




June 19, 2020 48


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.11.7 The VLU shall disable the receipt of voice calls or the

sending/receiving of text messages while in the covert

alarm state but shall leave the RTT and PRTT buttons

activated.

5.4.11.8 Only OCC shall be allowed to terminate the covert alarm

state once the covert alarm state has been activated.

5.4.11.9 The VLU shall periodically attempt to send the covert

alarm message until it receives an acknowledgement

message from the central system.

5.4.11.10 The VLU shall increase the frequency of vehicle location

information polling to a configurable time (e.g. 5 seconds)

when the covert alarm is activated.

5.4.11.11 When the MDT is in the covert alarm mode, there shall be

no indication on the display other than subtle symbols or

icons MCTS approves, signifying whether a dispatcher

has accepted the covert alarm and whether MCTS is

monitoring the covert microphone.

5.4.12 Schedule Adherence Management


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.12.1 When a vehicle operator is logged on to a fixed-route run,

the MDT operator terminal shall display continuous

feedback on current schedule adherence status and

displayed to the vehicle operator.

5.4.12.2 The estimated on-schedule time between timepoints shall

be based on the typical link running times.

5.4.12.3 The VLU shall send the most recent schedule adherence

data as part of each location report.

5.4.12.4 The VLU shall calculate an updated schedule adherence

based on the estimated on-schedule time for the current

location, every thirty (30) seconds, with an accuracy of

within one (1) second and with no more than one (1)

second of latency.

5.4.12.5 The VLU shall support free running mode (where

scheduled timepoints are not included in the on-time

performance) but continue to report stops in free running

mode with arrival, departure, and dwell times.




June 19, 2020 49


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.12.6 The MDT shall indicate to operators the current schedule

adherence in the form of a text-based display (e.g. + or –

2 minutes) and a stylistic display (e.g. ahead of schedule

is red, behind schedule yellow, on time is green).

5.4.12.7 The MDT shall provide configurable distinct audio alerts to

operators when they are a configurable time ahead of or

behind schedule.

5.4.12.8 The MDT shall provide a configurable visual alert to

operators when they are a configurable time ahead of or

behind schedule.

5.4.12.9 The VLU shall send an incident message to OCC when a

vehicle is determined to be running an MCTS-configurable

time ahead of or behind schedule.

5.4.12.10 The MDT shall provide an alert to the operator when the

bus in front has gone out of service.

5.4.13 Headway Adherence Management


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.13.1 For headway-based service, the system shall calculate

schedule adherence status based on headway adherence;

the VLU shall not utilize an underlying schedule.

5.4.13.2 For headway-based service, the VLU will report departure

from each stop to the central system for comparison

purposes.

5.4.13.3 For headway-based service, the MDT shall display

headway information to the operator including:

5.3.13.3.a • Distance to the previous and next bus;

5.3.13.3.b • Actual headway to the previous and next bus;

5.3.13.3.c • Scheduled headway to the previous and next bus;

and

5.3.13.3.d • Notifications when the bus in front has gone out of

service.

5.4.13.4 For headway-based service, the MDT shall indicate, both

audibly and visually, when an operator is required to hold

at the next feasible location to address a headway

maintenance issue. MCTS shall be able to configure the

headway threshold at which the alert is generated.




June 19, 2020 50


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.13.5 For headway-based service, the MDT shall indicate both

audibly and visually when an operator should proceed,

including:

5.4.13.5.a • At the start of trips;

5.4.13.5.b • At transit centers; and

5.4.13.5.c • After holding to correct headway issues.

5.4.14 Navigation Assistance


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.14.1 The VLU shall be equipped with a navigation assistance

module to use the MDT to provide visual and audible turn-

by-turn instruction for operators of fixed-route vehicles.

Whether or not this feature is enabled shall be configurable

by MCTS.

5.4.14.2 The navigation module shall allow vehicle operators to

toggle between map and text-based turn-by-turn direction.

5.4.14.3 Once the vehicle operator logs on, the MDT shall provide

an option to activate turn-by-turn navigation showing the

current location of the vehicle, the location of bus stops and

timepoints, and the routing between them, at the closest

zoom level where this route fits on the display. As the

vehicle travels, the map view will automatically pan and

zoom to continue to show this entire routing at the closest

possible zoom level.

5.4.14.4 The MDT shall allow operators to override the map zoom

level or pan the map display, and to select for the display to

return to the default mode that automatically follows the

routing.

5.4.14.5 The driving instructions shall include both the turn

directions and the name of the street, and this information

shall be provided at an agency configurable distance in

advance of the turn.

5.4.14.6 The navigation module shall allow the operator to activate

and deactivate the navigation map display and/or the

audible instructions as desired. The MDT shall provide a

way to increase or decrease audio volume for navigation

instructions. The audio volume should be interrupted for

any audio alert generated for an incoming message from

the OCC.




June 19, 2020 51


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.14.7 The navigation map shall be updateable over the bulk data

transfer using the WLAN.

5.4.15 Route Adherence Management


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.4.15.1 Based on configurable thresholds, the on-board system

shall continuously compute whether a fixed-route vehicle is

running on-route or off-route.

5.4.15.2 The system shall not consider a bus to be off-route if it is

following an applicable detour routing already received by

the VLU.

5.4.15.3 The VLU on fixed-route vehicles shall send an incident

message to OCC when a vehicle is determined to have

gone off-route or have come back on-route.

5.4.15.4 The VLU shall periodically attempt to send an off-route

message until it receives an acknowledgement message

from the central system.

5.4.15.5 The MDT shall display whether the vehicle is on-route or

off-route.

5.5 Vehicle Health Monitoring (VHM)

This section describes the requirements of the Vehicle Health Monitoring subsystem.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.5.1 The on-board system shall include a vehicle health

monitoring (VHM) subsystem that shall interface with

existing multiplex and powertrain systems using a physical

interface method compatible with interface adaptor kits

available for these systems.

5.5.2 The system shall immediately report alarms detected

through monitoring the VLU, destination sign, multiplex

system and powertrain onboard computer, as device alarm

data messages to the central system.

5.5.3 The MDT shall be integrated with existing J1708/1587 and

J1939 network on the fixed-route fleet to collect SPN/FMI

(PID) codes from Engine Control Module, Transmission

Control Module and Automatic Braking System.




June 19, 2020 52


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.5.4 The VHM shall monitor over J1708, J1939, multiplex, or

through discrete, as applicable, the following:

5.5.4.a • Pressures - air, oil, hydraulic;

5.5.4.b • Braking events - hard braking events, fast

acceleration events, anti-lock brake system (ABS)

activity;

5.5.4.c • Temperatures - engine, oil/fluid;

5.5.4.d • Fluid levels - engine oil, engine coolant, other fluid,

and fuel;

5.5.4.e • Voltage;

5.5.4.f • Heating, ventilation and air conditioning (HVAC);

5.5.4.g • Wheelchair/Bus Kneel;

5.5.4.h • Door open/close; and

5.5.4.i • Onboard battery levels and discharge performance

(for potential future battery-electric bus orders).

5.5.5 The VHM system shall be integrated with the VLU to obtain

the system date/time and current vehicle latitude/longitude

information.

5.5.6 The VHM system shall use MCTS configurable frequency

and duration thresholds, as available for sensor data, to

determine which data shall be stored in the system as

system warnings. These shall be transmitted to the central

software in real-time or as part of bulk data transfer and

available through maintenance reporting.

5.5.7 The VHM system shall use a separate set of MCTS

configurable frequency and duration thresholds for sensor

data as available, to determine which data shall be sent

immediately to the central software as critical system alerts

data messages. These thresholds shall be initially

configured by the Contractor at the time of vehicle

installations. Only users authorized by MCTS shall be

allowed to modify these thresholds.

5.5.8 The VHM system shall periodically attempt to send device

alarm and critical alert data messages until it receives an

acknowledgement message from the central system.

5.5.9 The MDT shall provide access to maintenance diagnostic

and troubleshooting information screen to appropriately

authorized users.

5.5.10 Diagnostic information displayed shall update (at a

minimum) once every second.




June 19, 2020 53

5.6 Supervisor/Support Vehicle Equipment

This section defines requirements for non-revenue fleet for vehicle tracking, voice communication and remote

dispatching (on street supervisor vehicles).


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.6.1 The Contractor shall provide technical requirements for

ruggedized laptops or equivalent mobile hardware such as

tablets to allow remote mobile access for supervisor

vehicles to the central CAD/AVL system over a cellular data

connection. (MCTS shall procure these devices).

5.6.2 The Contractor shall equip support vehicles with cellular

data modems having built-in GPS receivers to enable

vehicle location tracking.

5.6.3 If the Contractor recommends tablets as the mobile

dispatching device, the device shall include GPS tracking

capability and shall report its position to the central system

every thirty (30) seconds.

5.7 Test Bench (Option)


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

5.7.1 The Contractor shall supply equipment for the test bench to

provide the following functions:

5.7.1.a • Radio and cellular data communications;

5.7.1.b • CAD/AVL;

5.7.1.c • GPS simulator; and

5.7.1.d • Signals to simulate discrete inputs.

5.7.2 The Contractor shall supply integration points for the test

bench to the following external systems:

5.7.2.a • AVA;

5.7.2.b • VHM; and

5.7.2.c • ODK4 controller for destination sign.




June 19, 2020 54

6 Central System

6.1 General

This section lists central system requirements as they relate to system and user environment configuration and

operation.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.1.1 The Contractor shall leverage the existing infrastructure

and equipment wherever possible. The Contractor shall be

fully responsible for implementing these interfaces.

6.1.2 The Contractor shall lead the effort with the suppliers of

existing systems as needed to confirm requirements and

designs, prepare and review ICD’s, and coordinate

installation and upgrade work.

6.1.3 All software shall integrate with standard printer drivers to

allow reports to be printed directly from within the software.

6.1.4 The system shall be designed for continuous operation

without the need to manually “reboot” computers or

devices. Necessary scheduled reboots will not impact day-

to-day operations.

6.1.5 The central system and all CAD/AVL subsystems shall

automatically recognize any stoppage, failure, failover, or

lock-up of a system process and automatically log the

problem, attempt a restart if appropriate, and notify OCC

and system administrator.

6.1.6 The system shall not place limitations (through licensing or

otherwise) on the number of concurrent workstations

sessions running on virtual or physical workstations.

6.1.7 The central system shall be designed to allow for at least

thirty (30) simultaneous users without a noticeable

reduction in system response times. The system shall allow

users to work simultaneously in CAD/AVL without creating

data conflicts with or overriding actions by other users.

6.1.8 The performance and output of the CAD/AVL data and

mapping software shall be sufficiently precise to accurately

and reliably identify the location of each vehicle on the

street network.




June 19, 2020 55


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.1.9 Commonly used database queries, queue displays,

information windows, and map displays shall be displayed

within one (1) second from user initiation for physical and

virtual workstations. All physical and virtual workstation

displays and information shall be consistent and show

current and identical status within ten (10) seconds of one

another.

6.1.10 The software shall have a site license that allows its usage

at MCTS facilities and on mobile equipment.

6.1.11 All central systems shall be accessible only to authorized

users as managed by the SA. The approach for use

authorization and management should be documented and

signed off by MCTS.

6.1.12 The central system shall provide a single-point interface for

the management of user accounts, groups, and associated

privileges.

6.1.13 Once a user is logged on to the system via a desktop client

on a workstation, the central system software shall enable

automatic logon to other software packages installed on

that workstation supporting CAD/AVL operations.

6.1.14 The central system shall have full capability to add, delete,

or modify users, groups, or roles in any systems and shall

have full administrative rights to do so.

6.1.15 The central system shall allow the system administrator to

manage user access permissions for specific user groups.

6.1.16 The central system shall enable role-based access control

to allow the SA to delegate management of certain user

access permissions to other authorized users.

6.1.17 All central system components shall record in the historical

database all successful and attempted logons, logoffs, and

which modules were accessed during the user’s session.

6.1.18 The system shall enable authorized MCTS users to

configure user logons, logoffs, and accessing of system

modules as notifiable events that trigger automatic email

notifications to configurable recipient lists.

6.1.19 All central system components shall lock out the user after

a number of successive failed logon attempts within a set

time frame. The number of permissible failed logon

attempts and the time frame shall be configurable by

MCTS.

6.1.20 All central system components shall continuously monitor

for unauthorized access to managed functions.




June 19, 2020 56

6.2 Built-in Maps

This section provides requirements for the base map, built-in mapping and spatial visualization tools used by

AVL and other products.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.2.1 The central system shall have a map-based GUI. The GUI

shall support various map views, with full zoom, pan and

auto-centering capability.

6.2.2 Base mapping for all applications (central and onboard)

shall utilize an MCTS-approved third-party mapping source

that provides current and continuously updated base map

data.

6.2.3 The system shall correctly transform map data between

map projections, merging all internally and externally

derived data into an accurate and complete map.

6.2.4 The GIS editing software shall allow MCTS to develop

additional overlay map layers that can include polygons

(e.g., municipal boundaries, fare zones), lines (e.g., route

traces) and points (e.g., landmarks, transfer locations, time

points, stop locations), with the color, shape and thickness

being selectable.

6.2.5 MCTS shall be able to edit and update map layers used in

Contractor-provided GIS modules. The Contractor shall

provide the cost and details of the geographic information

system (GIS) editing software as needed as part of the

proposed solution for maintenance of built-in GIS maps.

6.2.6 The proposed software shall incorporate maps to support

the functionality, comprised of a selection of individually

selectable theme layers (e.g., streets, street names, water

features, parks, major buildings).

6.2.7 The system shall include mechanisms to allow for periodic

independent updates by MCTS to custom map layers in the

central and on-board systems.

6.2.8 The built-in GIS module in the proposed software shall

allow the user to calculate the distance along a line drawn

on the map as a sequence of straight lines between points

(e.g. the distance of a route trace).

6.2.9 The built-in GIS module shall allow MCTS system users to

save and reload a map view in the AVL window.

6.2.10 The system shall include mechanisms to accept real-time

traffic or event-based roadway conditions.




June 19, 2020 57

6.3 Data Import/Export and Integration Interfaces

6.3.1 Scheduling System Interface

This section defines requirements for interface between existing schedule data management software and the

new systems provided by the Contractor. MCTS utilizes HASTUS 2019 for schedule data creation and

management, and HASTUS-ATP for run-time and performance analysis.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.3.1.1 The system shall have the ability to independently import

scheduling data from the MCTS scheduling system, with the

central system checking for files or views in a

predetermined directory, or database table, or as a real-time

service (service-oriented architecture). The system shall

support scheduling dataset imports:

6.3.1.1.a • Immediately, in response to a manual trigger by

authorized users; and

6.3.1.1.b • As part of an automated procedure at a frequency


6.3.1.2 The system shall accept and correctly incorporate the

following data imported from the MCTS scheduling system:

6.3.1.2.a • Stops;

6.3.1.2.b • Timepoints;

6.3.1.2.c • Combined stop/Timepoints;

6.3.1.2.d • Routes;

6.3.1.2.e • Route traces/Shape files;

6.3.1.2.f • Route variants;

6.3.1.2.g • Patterns;

6.3.1.2.h • Blocks;

6.3.1.2.i • Trips;

6.3.1.2.j • Timetables;

6.3.1.2.k • Service calendars;

6.3.1.2.l • Day types;

6.3.1.2.m • Service types;

6.3.1.2.n • Exceptions; and

6.3.1.2.o • Any other relevant schedule data to support

CAD/AVL functions.




June 19, 2020 58


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.3.1.3 The system shall perform a series of internal consistency

checks on all imported data prior to using the data in active

or production modes for the system. For any missing

imports or errors in imported data, the system shall

generate logs and send automated alarms to the MCTS SA.

Internal consistency checks will be performed on import.

6.3.1.4 Any faults or errors that occur during the automatic

conversion or transfer of data either within internal

subcomponents of the central system, or from external data

sources to internal subcomponents, shall be logged and an

error message/alert will be generated by the system.

6.3.1.5 The system shall store at least one future scheduling

dataset with a set future validity start date.

6.3.1.6 At the start of the validity period for a new scheduling

dataset, the system will automatically transition to using the

new scheduling dataset in production, including publishing

the dataset to all buses.

6.3.1.7 The system shall enable authorized MCTS users to extend

the end date for a scheduling dataset as needed.

6.3.1.8 The system shall enable automated exports of all recorded

real operating data to the run-time and performance

analysis module of the scheduling system.

6.3.2 Human Resources Management

This section defines requirements for interface between the MCTS human resources management system

(currently provided by Ceridian) and CAD/AVL software.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.3.2.1 The system shall be interfaced with the MCTS human

resources management system to:

6.3.2.1.a • Receive updates to the active employee roster and

associated personnel data, including:

o Name;

o Badge number;

o Employee portrait; and

6.3.2.1.b • Return real-time updates on work performed by

operators as recorded by the CAD/AVL system to

generate exceptions reporting on payroll hours.




June 19, 2020 59


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.3.2.2 Data exchange between the human resources

management system and CAD/AVL system shall be

automated, so as not to require any manual data transfer

actions by MCTS staff.

6.3.2.3 The system shall enable authorized MCTS users to verify

operator data updates received from the Human

Resources Management system prior to publishing

changes to the active employee roster.

6.3.2.4 The system shall support configuring and sending an email

alert to an MCTS-configurable user list when operator data

updates have been received and are pending review, and

when changes have been approved and published.

6.3.2.5 The system shall automatically retrieve operator portraits

for display along with operator names and badge numbers,

by accessing the appropriate MCTS network folder.

6.4 CAD/AVL System

This section defines requirements for the CAD/AVL central hardware and software and interfaces.

6.4.1 CAD/AVL Workstations


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.1.1 The system shall use typical MS Windows-style graphical

user interface (GUI) conventions including but not limited to

resizable windows, point and click, right click context

menus, drop-down menus, toolbars, color displays, icons,

drag and drop, scroll bars, scroll wheel mouse and status

bars.

6.4.1.2 The GUI shall support all windows functions such as

concurrent display of multiple windows, including map

display windows or tabular windows, paging, scrolling.

6.4.1.3 The GUI shall support repositioning and resizing each

window as desired to present the maximum amount of

useable information.

6.4.1.4 The system shall support mouse and keyboard inputs with

all primary features supported by keyboard shortcuts.

6.4.1.5 The system shall provide easy-to-read displays when the

user is situated a standard distance from the display (i.e.

20/20 vision at a distance of three (3) feet).




June 19, 2020 60


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.1.6 The system shall permit MCTS to configure the

appearance of GUI elements enterprise-wide, including

agency branding, and general icon sets.

6.4.1.7 The system shall permit individual users to customize the

appearance of GUI elements per user preference, including

but not limited to: map colors, backgrounds, and font sizes.

6.4.1.8 The system shall save all user preferences by user logon

so that the GUI automatically conforms to the user’s saved

preferences when logging on to any CAD workstation.

6.4.1.9 All windows with static data shall open and populate within

one (1) second.

6.4.1.10 All windows with dynamic data shall open and initially

populate within two (2) seconds and thereafter, any

updates shall result in page population within one (1)

second.

6.4.1.11 Movement (e.g. panning, zooming, scrolling, dragging of

the cursor bar) through GUI displays shall be smooth,

without perceptible lag, and without disruption to displayed

graphics and text.

6.4.1.12 The system shall permit the user to filter stops on the GUI

displays by criteria including, but not limited to:

6.4.1.12.a • A subset of routes; and

6.4.1.12.b • In-service status (e.g. in-service, temporarily

closed, temporary stops).

6.4.2 Mobile Access

This section lists requirements for accessing CAD/AVL software on a mobile device. As stated in Section 5.6,

mobile devices may include laptops or tablets.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.2.1 Software functions and views to be displayed on the mobile

device shall be configurable by MCTS staff and shall

provide CAD/AVL functionality similar to the central site

CAD, optimized for a mobile environment (i.e. through a

mobile-adapted application for laptops or native OS

application for tablets (Android or iOS).

6.4.2.2 The dispatcher shall be able to view the location of

supervisor vehicles equipped with mobile devices on

CAD/AVL map views; in addition to fixed route vehicle

locations.




June 19, 2020 61

6.4.3 MDT Logon Verification

This section describes the functional requirements of the system for verification of logon/logoff process on

MDTs.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.3.1 The system shall receive and validate a logon request from

an MDT, if the vehicle operator ID and run/block ID are

valid and not already logged in on another VLU.

6.4.3.2 The system shall update the list of valid operator

credentials through importing a standard MCTS “List of

Operators” file in .csv format. MCTS will provide the

Contractor with a sample “List of Operators” file for the

purposes of integration with the CAD/AVL software.

6.4.3.3 The system shall allow dispatchers to manually logon/logoff

operators onto vehicles and runs/blocks.

6.4.3.4 The system shall allow vehicle operators to log on to a

vehicle to operate service that was assigned to another

vehicle operator, or to supplement service if more vehicles

are needed on a particular day or event.

6.4.3.5 The system shall receive and immediately process a logoff

message from an VLU.

6.4.3.6 The system shall provide a pull-in/pull-out summary display

for dispatchers that can be sorted by status of lateness,

depot, vehicle ID, operator number, and first and last name.

6.4.3.7 The system shall notify OCC of the following types of

vehicle status exceptions:

6.4.3.7.a • Vehicle movement when not logged on;

6.4.3.7.b • Logon request that is not unique or authentic;

6.4.3.7.c • Late operator logon/absent operator;

6.4.3.7.d • Missed operator relief; and

6.4.3.7.e • Late vehicle pull-out.

6.4.3.8 Vehicle status exception thresholds shall be configurable

by MCTS.

6.4.3.9 Operator and vehicle assignments shall update as

operators logon/logoff their vehicle’s MDTs either directly or

by dispatcher action (manual logon/logoff).




June 19, 2020 62

6.4.4 Vehicle Location Tracking

This section describes the requirements of the vehicle tracking functionality of the system.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.4.1 The system shall be able to process and provide real-time

location and mapping of revenue and non-revenue vehicles

(e.g. supervisor vehicles). The system shall receive

location reports from revenue and non-revenue vehicles

after a time period MCTS configures has passed after

receiving the last location report. The location reporting

interval shall be configurable to at least every five (5)

seconds.

6.4.4.2 The system shall provide access to all vehicle location

tracking functions through the map-based and schematic

interface.

6.4.4.3 The system shall track and report on vehicle locations

regardless of whether a user is logged into the CAD/AVL,

and regardless of whether the vehicle power is turned on,

within the window when the CAD/AVL is configured to

remain active (see requirement 5.4.1.9).

6.4.4.4 After the onboard CAD/AVL components have shut off on a

vehicle, the system will continue to indicate the vehicle’s

last known location.

6.4.4.5 The system shall indicate any vehicle that is not reporting

its status and location within a configurable time period.

6.4.4.6 The system shall receive and store latitude and longitude

information stamped with date, time, vehicle, vehicle

operator, run, route, and trip information from VLUs.

6.4.4.7 The dispatcher shall be able to center a map view on a

vehicle, or track a vehicle by:

6.4.4.7.a • Selecting the vehicle on the map display;

6.4.4.7.b • Entering the block, vehicle, operator ID, or route;

6.4.4.7.c • Selecting the vehicle from a list of vehicles;

6.4.4.7.d • Selecting a communication event/message;

6.4.4.7.e • Selecting the operator from a list of operators; and

6.4.4.7.f • Selecting the block from a list of blocks.

6.4.4.8 The system shall enable the dispatcher to choose what

label(s) vehicle points on the map view will display

including vehicle number, block number, route number,

and/or vehicle operator number.

6.4.4.9 The system shall enable the dispatcher to select a bus and

view:




June 19, 2020 63


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.4.9.a • The current vehicle block and all associated

scheduled activities;

6.4.4.9.b • The current operator paddle (the full work

assignment for the operator’s shift).

6.4.4.10 The display shall provide an indication if the last reported

location being displayed is older than the reporting interval.

If a vehicle’s location on the AVL map is shown to be older

than a minute, the system shall let the dispatcher manually

poll/locate a vehicle.

6.4.4.11 The system shall receive and store information related to

event types and event data with event-triggered automatic

location reports. Event types that trigger location reports

shall include:

6.4.4.11.a • Location and schedule/route adherence reports;

6.4.4.11.b • Text and pre-defined messaging;

6.4.4.11.c • Data upload and download;

6.4.4.11.d • Software updates;

6.4.4.11.e • Device parameter changes;

6.4.4.11.f • Onboard device status, changes, and error reports;

6.4.4.11.g • System ignition/shutdown;

6.4.4.11.h • Operator log-on/off/over;

6.4.4.11.i • Arrival/Departure at stop and time-point;

6.4.4.11.j • Start and stop motion;

6.4.4.11.k • Door open and close;

6.4.4.11.l • Destination sign changes; and

6.4.4.11.m • Onboard logs and alerts from the VLU.

6.4.4.12 The system shall reconcile all data received from vehicles

through location, event, and schedule adherence reports

with the detailed information downloaded from the VLU

after the vehicle returns to its storage depot to ensure data

integrity in the event that some reports are not received at

central.

6.4.4.13 The system shall store the vehicle’s last known location as

received from that vehicle, even after a VLU has been shut

down.

6.4.5 Voice Call Management

This section describes the functional requirements for the voice call management feature.




June 19, 2020 64


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.5.1 The system shall allow the dispatcher to view RTT and

PRTT messages received from MDTs on a tabular

communication display together with the time received.

6.4.5.2 The voice call functionality shall allow the dispatcher to set

up a quick voice call response to the initiating vehicle

operator by selecting RTT or PRTT from the

communications display.

6.4.5.3 Only one (1) RTT and PRTT shall be active in the

communication display queue for each vehicle attempting

to make a call. A PRTT will replace a RTT should the

vehicle change from RTT to PRTT, whereas repeated

presses of RTT or PRTT will simply update the existing

message in the communications display queue.

6.4.5.4 Dispatchers shall be able to initiate voice communications

by double-clicking RTT or PRTT messages.

6.4.5.5 Once connected, PRTT and RTT messages will display as

being handled by the connecting dispatcher on all

workstations displaying that message.

6.4.5.6 When an RTT/PRTT is received, the system shall produce

an audible alert and a visual indicator. The visual indicator

shall not disappear off the communications display queue

until the RTT/PRTT is dealt with by a dispatcher.

6.4.5.7 The audible RTT/PRTT alert shall be configurable by

MCTS based on the following properties:

6.4.5.7.a • Enabled/disabled; and

6.4.5.7.b • The audio clip to be played.

6.4.5.8 Covert alarms shall take top priority in the communications

display queue, followed by PRTT and RTT respectively.

6.4.5.9 The system shall allow set up of a one-way broadcast voice

call to a single vehicle or a group of vehicles.

6.4.5.10 The system shall provide the capability to set up a two-way

voice call with an individual vehicle, individual vehicle

operator, all vehicles in a fleet group, all vehicles on a route

or set of routes, all vehicles in a selected group or all

vehicles within a selected geographic area on the map.

6.4.5.11 The system shall require the dispatcher to establish a

timeout interval for any voice call.

6.4.5.12 The voice call timeout setting shall offer a default interval

and alternative intervals determined by MCTS.

6.4.5.13 The system shall automatically notify dispatchers after a

configurable amount of time has passed, that a call or

event has not been resolved/closed.




June 19, 2020 65


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.5.14 The system shall allow dispatchers to seamlessly switch

voice communications between their handset and

telephone headset.

6.4.5.15 The system shall allow dispatchers to utilize a single

headset for voice radio and telephone communications.

Initiating any outgoing radio communications shall mute the

dispatcher’s voice towards the telephone system. Likewise,

dispatcher audio intended for the telephone shall not be

conveyed over the radio system. Telephone and

communications audio into the headset shall be

configurable as summed or provide priority for

communications messages (e.g., muting or attenuating the

telephone audio) while selected communications traffic is

present.

6.4.5.16 Voice communications requests shall be separately

highlighted and displayed in the communications display

queue.

6.4.5.17 The system shall notify the dispatcher when the call cannot

be setup and present the dispatcher with a choice to cancel

the call or to continue trying for a configurable number of

retry actions to set up the call and notify the dispatcher

when it was successful.

6.4.5.18 The system shall notify the dispatcher visually and by tone

when a call has connected and the dispatcher may begin

speaking.

6.4.5.19 The system shall automatically and immediately locate and

update vehicle information when a dispatcher takes a call.

6.4.5.20 The remote access for supervisors to the CAD/AVL system

via the mobile laptop or tablet shall allow supervisors the

ability to set up a voice call with one or more vehicle

operators. Further, the system shall allow supervisors to

listen in to an ongoing call.

6.4.5.21 Calls initiated from portable radios to OCC shall provide a

unique radio ID, which will be correlated with a name

assigned to the radio and displayed to the dispatcher.

6.4.5.22 The system shall record all voice communications and will

restrict access to voice recordings to users authorized by

MCTS. Recordings will include metadata that allow ease of

searching the voice recording database (e.g. call time,

user, location, call type).




June 19, 2020 66

6.4.6 Data Messaging

This section describes the requirements for data messaging functionality.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.6.1 The system shall support data messaging functionality to

communicate between dispatchers and vehicle operators,

including text and static images.

6.4.6.2 All messages and metadata (e.g. time sent and received,

acknowledgements) shall be considered CAD/AVL system

data and logged for reporting and archiving accordingly.

6.4.6.3 The system shall transmit data messages of unlimited

length, and shall automatically paginate messages

exceeding the display limit.

6.4.6.4 The system shall transfer messages between a dispatcher

workstation and the vehicle cellular data gateway within

one second.

6.4.6.5 The system shall allow authorized user roles (at minimum

the dispatcher and SA) to view received data messages in

a tabular display updated in real-time that also indicates the

following metadata. These messages and corresponding

metadata shall also be logged in the database for future

retrieval.

6.4.6.5.a • Vehicle ID;

6.4.6.5.b • Time the message was sent;

6.4.6.5.c • Time the message was received; and

6.4.6.5.d • Whether the operator has acknowledged the

message.

6.4.6.6 The system shall allow the dispatcher to send a message

to:

6.4.6.6.a • An MDT;

6.4.6.6.b • A predefined group of MDTs;

6.4.6.6.c • All MDTs within an area selected on the map

display; and

6.4.6.6.d • All MDTs operating on the same route, and all

MDTs.

6.4.6.7 The system shall allow the dispatcher to select one of a set

of predefined messages (canned data messages) or enter

a free text message.

6.4.6.8 The system shall store of at least 50 canned data

messages for dispatcher use. Canned text messages shall

be configurable by the system administrator.




June 19, 2020 67


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.6.9 The system shall store recently sent messages (canned or

free text) available for the user to easily select from.

6.4.6.10 The system shall indicate when a data message has been

viewed by the operator (i.e. a read-receipt).

6.4.6.11 The system shall allow for any message sent by OCC to be

flagged as requiring vehicle operator acknowledgement as

a Y/N response, and shall allow the dispatcher to view a list

of such messages that have not yet been acknowledged.

The system shall automatically resend messages that have

not been acknowledged.

6.4.6.12 The system shall allow for triggered, automatic messages.

Automatic message triggers shall be defined by:

6.4.6.12.a • Time of day;

6.4.6.12.b • Trigger location; and

6.4.6.12.c • Trigger boundary (i.e. enclosed area).

6.4.6.13 Triggered automatic messages shall be further configurable

by identifying that they be sent when a vehicle starts the

specified:

6.4.6.13.a • Route(s);

6.4.6.13.b • Trip(s); and

6.4.6.13.c • Block(s).

6.4.6.14 Triggered automatic messages shall be used to notify

operators of route changes, detours, or special

announcements. Regardless of whether or not the

message requires a response from the operator, there shall

be a notification to the dispatcher if the message was not

delivered to the vehicle or not viewed by the operator for an

MCTS-configurable time period after login.

6.4.6.15 When a dispatcher sends a message, along with the

message text, the system shall display the following data

points:

6.4.6.15.a • Times sent and received;

6.4.6.15.b • Recipient route and block;

6.4.6.15.c • Recipient vehicle ID;

6.4.6.15.d • Recipient operator name, badge number, and

portrait; and

6.4.6.15.e • Real-time delivery status (i.e. successful, failed, or

pending).




June 19, 2020 68


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.6.16 The system shall indicate to the dispatcher when a data

message has been received by the VLU onboard the

recipient vehicle.

6.4.6.17 When a dispatcher receives a message, along with the

message text, the system shall display the following data

points:

6.4.6.17.a • Message priority;

6.4.6.17.b • Times sent and received;

6.4.6.17.c • Route and block;

6.4.6.17.d • Vehicle ID;

6.4.6.17.e • Operator name, badge number, and portrait;

6.4.6.17.f • Location;

6.4.6.17.g • Schedule adherence; and

6.4.6.17.h • Trip status.

6.4.6.18 Messages shall be displayed in an MCTS-configurable priority order. Within this priority order, messages shall be ordered chronologically.

6.4.6.19 The system shall support audible and visual alerts for

incoming messages that are clearly distinguishable for

each priority level and read/unread status. These alerts

shall be configurable by authorized MCTS users.

6.4.7 Central Covert Alarm Handling

This section lists the requirements with regards to covert alarm handling on the central system side.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.7.1 When a covert alarm signal is received from a vehicle, the

central CAD/AVL system shall display the event in the

performance queue to all dispatchers, using MCTS

approved visual and audio alerting methods, and the

system shall monitor that vehicle continuously until

otherwise specified by OCC.

6.4.7.2 The CAD/AVL system shall notify the dispatcher in the

performance queue that a covert alarm message has been

received using a MCTS approved visual interface. There

shall also be a MCTS approved audio notification method,

which MCTS shall be able to configure as on or off.




June 19, 2020 69


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.7.3 When acknowledging a covert alarm, the system shall

zoom and center the map display on the alarming vehicle

and also show the location for the nearest Road Supervisor

vehicle when selected by OCC. The scale for the zoom

shall be configurable by MCTS.

6.4.7.4 Activation of a covert alarm shall place the vehicle in a

priority status for frequency of location and message

updates which will result in vehicle location and status

updates at a more frequent rate. The frequency of the

location report interval shall be configurable by MCTS.

6.4.7.5 Once one of the dispatchers selects the covert alarm event,

this shall be indicated to that dispatcher and other

authorized staff.

6.4.7.6 Once a dispatcher has selected the covert alarm event, the

dispatcher shall be able to opt whether to monitor the

covert microphone audio and separately whether to monitor

the onboard video feed.

6.4.7.7 The dispatcher can opt at any time to end the covert

microphone monitoring or the overall covert alarm event.

6.4.7.8 The system shall send signals back to the VLU that

generated the alarm once a dispatcher has selected the

event, once covert microphone monitoring has started or

ended, and once the event has been ended.

6.4.7.9 During a covert alarm event, the system shall not allow

dispatchers to initiate voice calls with the vehicle or send a

text message, but all other location/performance monitoring

and the ability to receive an RTT/PRTT signal shall remain

operational.

6.4.8 Incident Management and Reporting

This section lists requirements for built-in incident management and reporting feature of the CAD software.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.8.1 The system shall automatically generate an incident

record when certain MCTS-configurable CAD incidents

(e.g. covert alarms) occur.

6.4.8.2 The system user shall be able to select an incident record

as the basis for an incident report, with the form auto-

populated with all information already known in the system

about the incident.




June 19, 2020 70


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.8.3 The dispatcher shall be able to manually initiate an

incident record by:

6.4.8.3.a • Selecting an incident generation function via

hotkey, drop down menu, or button on a toolbar;

6.4.8.3.b • Selecting an incident generation function in

relation to a particular vehicle from the AVL map

or message queue, with the appropriate CAD

available information populating the incident

automatically; and

6.4.8.3.c • Selecting an incident generation function from a

vehicle list, block table, or stop list display with the

appropriate CAD available information populating

the incident automatically.

6.4.8.4 The system shall generate a unique, progressive

identification for each incident regardless of re-booting the

system.

6.4.8.5 Incidents shall be classified according to numerical codes

for ease of grouping. These codes shall be:

6.4.8.5.a • Be configurable by MCTS; and

6.4.8.5.b • Support multi-level sub-codes to enable finer

classification and continuity.

6.4.8.6 The system shall impose no effective limit on the number

of incident codes and sub-codes that can be defined.

6.4.8.7 The dispatcher shall be able to quickly locate and center a

vehicle on a map once an incident is generated.

6.4.8.8 The system shall allow authorized users the ability to tag

an incident report with an index or link to specific CCTV

frame(s)/clips or vehicle data replay.

6.4.8.9 The system shall maintain one central report associated

with each incident, accessible from a server so all

authorized users see the same current report information,

but only one instance of the report can be open at a time

for editing.

6.4.8.10 The system shall allow authorized users to append to an

existing open incident report, with other system users

limited to read-only access.

6.4.8.11 The open incident report shall display the vehicle status

relating to the incident.

6.4.8.12 The system shall provide a summary display for all

currently active incidents.

6.4.8.13 The user shall be able to select from a list of currently

open incident reports that can be sorted and filtered by:




June 19, 2020 71


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.8.13.a • Date/Time;

6.4.8.13.b • Incident type;

6.4.8.13.c • Keyword; and

6.4.8.13.d • Initiating dispatcher.

6.4.8.14 The users shall have the ability to attach files, such as an

image file, to the incident report.

6.4.8.15 The system shall be able to set limits on which users can

open, modify or close incident reports.

6.4.8.16 The system shall require all incidents be assigned to a

dispatcher for response.

6.4.8.17 The system shall permit authorized personnel to adjust

selected metadata of incident reports, including:

6.4.8.17.a • Reassigning open incidents to other dispatchers;

6.4.8.17.b • Changing the incident type (e.g. in response to

updated information); and

6.4.8.17.c • Linking and merging incident reports (e.g. in case

multiple reports are opened describing the same

incident).

The system shall retain a record of all such adjustments

for traceability and auditing.

6.4.8.18 The system shall track the user and date/time associated

with every action performed on an incident report,

including generation, modification or closure.

6.4.8.19 The system shall allow authorized users to close an

existing open incident report. The user shall be asked to

confirm the selected incident report before the incident is

closed.

6.4.8.20 Once an incident report is closed, the system shall not

permit further modifications, unless by authorized

personnel with specific authorization to do so.

6.4.8.21 Immediately upon closing an in-progress incident report, it

shall be available for review by other users.

6.4.8.22 The incident report database shall indicate, for each

incident report, the date/time of opening the report, the

incident type, the initial incident text, the initiating

dispatcher, the date/time of each subsequent modification,

each modified version of the text, the modifying

dispatcher, the date/time the incident was closed, and the

closing dispatcher.




June 19, 2020 72


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.8.23 The system shall allow the dispatcher to forward specific

incident types to distribution groups via e-mail and text to

cell phone numbers. Types of incidents and distribution

groups shall be configurable by MCTS.

6.4.8.24 The system shall allow the dispatcher to set up automated

email distribution for selected incident types.

6.4.8.25 The system shall enable authorized personnel to mute

selected incident types for a configurable time period (e.g.

delays in case of severe weather).

6.4.9 Vehicle Tracking Interface for External Systems


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.9.1 The system shall have the capability to receive, store, and

display vehicle location data received from multiple external

systems (e.g., ride hail services). Contractor shall provide

documentation regarding the standardized data interface

formats (GTFS-realtime, SIRI, or other standards) and

retrieval mechanisms supported by the CAD/AVL system

for the external vehicle tracking data.

6.4.9.2 The system shall support multiple methods for receiving the

external vehicle tracking data interface feeds, including:

6.4.9.2.a • Direct integration through a client-server

mechanism (such as through APIs); and

6.4.9.2.b • Data retrieval mechanism where a standard format

file is located at an identified URL.

6.4.10 Route and Schedule Adherence Tracking


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.10.1 The system shall provide access to all route and schedule

adherence tracking functions through the GUI.

6.4.10.2 The system shall utilize trip-based timepoint arrivals and

scheduled headways as imported from the MCTS

scheduling system for the purposes of determining

schedule adherence.




June 19, 2020 73


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.10.3 The system shall receive automatic route and schedule

adherence reports from vehicles at identified time points

and at a rate of at least once every 5 seconds as

configured by MCTS. Reports shall be stamped with date,

time, stop, vehicle, block, operator, run, route, trip, latitude,

and longitude from MDTs.

6.4.10.4 The system shall account for temporary changes in route

and schedule adherence tracking (e.g. in the case of a

detour or service curtailment) for any given route or

portions of a route and for groups of vehicles as defined by

the dispatcher.

6.4.10.5 Based on MCTS-configurable thresholds, the system shall

use the reported schedule adherence data to designate

when vehicles are “early,” “late,” or “on time.” The system

shall provide a separate MCTS configurable “late”

parameter specifically to support TSP and other needs.

6.4.10.6 The system shall provide an alert to OCC for vehicles that

are “early” or “late”, as defined by parameters configurable

by authorized MCTS users.

6.4.10.7 The system shall provide an alert to OCC for vehicles that

remain at layover points late or leave layover points late.

6.4.10.8 The system shall provide an alert to OCC for bunching

vehicles; the threshold parameters shall be configurable by

the system administrator.

6.4.10.9 Based on thresholds that MCTS staff configures, the

system shall determine when vehicles are deemed off-route

and when off-route vehicles have returned to route.

6.4.10.10 The system shall generate off-route message for vehicles

deviating from routes by a configurable distance. There

shall also be a tool that allows the system to receive detour

and alternate route information that prevents the off-route

notification when a bus is on the detour or alternate route.

6.4.10.11 The system shall display schedule and route adherence,

gapping/bunching, headways, and status by route and

allow "drill-down" selection by dispatcher to view

associated vehicles.

6.4.10.12 The system shall highlight the vehicle IDs of those vehicles

that are operating early, late, or off-route, using tabular and

map displays to indicate their current schedule and route

adherence status to the dispatcher. The tabular display

entries and the map display symbols for these vehicles

shall use distinct and configurable color codes for early,

late, and off-route status.




June 19, 2020 74


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.10.13 The system shall provide a GTFS-realtime output of the

current location and the schedule adherence for all fleet

vehicles for use by next stop prediction software.

6.4.10.14 The system shall allow for a global change to an alternate

set of behind/ahead of schedule threshold parameters and

headway threshold parameters (e.g. in the case of

inclement weather). The alternate set of threshold

parameters shall be configurable by the system

administrator.

6.4.10.15 The system shall provide the ability to disable route and/or

schedule adherence tracking temporarily for a route or

route segment.

6.4.10.16 The system shall flag buses when out-of-service to avoid

triggering route and schedule adherence alerts, and visibly

indicate this out of service status to dispatchers.

6.4.10.17 The system shall flag buses on active detours to avoid

triggering off-route alerts, and visibly indicate this detour

status to dispatchers.

6.4.11 Headway Management


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.11.1 The Contractor shall provide a display to visualize routes

and vehicles that are operating based on headway.

6.4.11.2 The display shall visually show geographic location of each

vehicle on a route along with timepoints and shall allow

dispatchers to take necessary actions to avoid bunching

and spacing.

6.4.11.3 The visual interface shall allow dispatchers to communicate

necessary actions to vehicle operators to hold, depart, slow

down or speed up for managing headways.

6.4.12 Service Management


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.12.1 The system shall include management for a series of

standard service restoration/correction functions including:




June 19, 2020 75


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.12.1.a • Detour: Activate predefined detours for service

routes;

6.4.12.1.b • Ad-hoc Detour: Create short term detours for

accidents/incidents and events;

6.4.12.1.c • Delete/Add a block to support operating

unscheduled specials;

6.4.12.1.d • Delete/Add a Trip to a block to adjust service

levels;

6.4.12.1.e • Replace a Vehicle/Operator: Assign a replacement

vehicle and/or operator to take over service from a

scheduled block that cannot continue for any

reason;

6.4.12.1.f • Skip Stop: Notify an operator to bypass a series of

stops to restore headways, with the ability to

identify and log the starting and stopping point for

the skip stop measure;

6.4.12.1.g • Drop-off Only: Notify or approve an operator to

serve alighting passengers only; and

6.4.12.1.h • Initiate management based on headway instead of

on schedule: The headway mode will automatically

evenly distribute the vehicles on the route. This

function shall communicate the revised “schedule

adherence” to all affected vehicles.

6.4.13 Detour Management


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.13.1 The system shall include features to manage detours in

real-time, including maintaining accurate route and

schedule adherence in the event of a detour.

6.4.13.2 The system shall allow dispatchers to create and edit

detours by designating road segments and stops to

define the Trip Pattern and indicating at which existing

points the detour connects with a scheduled Trip Pattern.

The system shall support this function through a map-

based click-and-draw feature within the dispatcher UI.

6.4.13.3 The system shall enable dispatchers to edit both active

and inactive detours, and distribute updates to active

detours in real-time.




June 19, 2020 76


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.13.4 The system shall permit the dispatcher to define

temporary stops for use during a detour, including new

stops that are not part of an existing route.

6.4.13.5 The system shall automatically create a detour shape file

connecting the start and end existing stops, including the

designated road segments and temporary stops forming

the detour.

6.4.13.6 The system shall automatically generate full text

descriptions of detours including turn-by-turn text

directions and the stops to be serviced based on the

dispatcher’s input on the map-based UI.

6.4.13.7 The system shall allow users to filter out stops on the UI

if they have been taken out of service for a detour.

6.4.13.8 The system shall allow dispatchers to specify a start date

and time and an end date and time for a detour. By

default, the central system shall indicate the detour to

start at the current date and time, and end at the end of

the current operating day.

6.4.13.9 The system shall allow dispatchers to specify which

blocks shall use the detour. Detoured blocks shall be

recorded in the central system as an appropriate status,

with the start and end time of the detour recorded as an

event.

6.4.13.10 The system shall allow dispatchers to modify blocks by

designating stops as inactive or by reassigning or

removing vehicles from certain blocks.

6.4.13.11 The system shall allow dispatchers to configure

automatic notifications to blocks affected by a detour

including turn-by-turn routing and active stops in both text

and interactive map format, and to a configurable email

list.

6.4.13.12 Once the dispatcher has created a detour, the system

shall automatically apply the detour to all affected blocks.

The system shall successfully transmit all relevant detour

data to buses such that it is available from the time they

log onto affected blocks, and remains available for the

duration of the detour. For affected blocks that are

already in service, the system shall push the relevant

detour data and adjust the block in real-time, providing a

visible and audible alert to the operator.

6.4.13.13 The system shall save the routing and active stops of all

created detours for future use, with unique identification

codes.




June 19, 2020 77


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.4.13.14 The system shall enforce an MCTS-configurable naming

convention for all saved detours.

6.4.13.15 The system shall provide dispatchers with a list of

previously created detours for use as templates, with

configurable start and end times.

6.4.13.16 The system shall allow dispatchers to designate where

vehicles are to short turn.

6.4.13.17 The system shall allow users to modify the routing and

active stops of a selected detour template and save this

as a new detour template.

6.4.13.18 The system shall enable dispatchers to search previously

created detour templates by:

6.4.13.18.a • Identification code;

6.4.13.18.b • Keyword (found in turn-by-turn directions); and

6.4.13.18.c • Associated route(s).

6.4.13.19 The system shall enable the dispatcher to apply a detour

to all applicable routes (i.e. all routes following the same

detour between the same start and end points) in one

action, without repeating the detour creation process for

each route individually.

6.4.13.20 The system shall permit detours to be created that

relocate the start and end point of a route to a location

not on the regular routing (e.g. if a terminal is out of

service and buses are diverted to a temporary location).

6.4.13.21 For detours that relocate the start/end point of a route,

the system shall automatically adjust scheduled trip start

and end times and schedule adherence for the operator,

so that buses maintain their schedule at timepoints not

affected by the detour.

6.4.13.22 The system shall allow the dispatcher to indicate that a

bus stop is not in service, and have that information

propagate to all routes and lines serving that stop.

6.4.13.23 All OCC service adjustments shall be logged and

disseminated to the MCTS's Customer Information

Center, predefined e-mail groups, and other staff.

Information dissemination triggers, timing, and staff to be

contacted will be configurable by MCTS.

6.4.13.24 For all dispatcher service adjustments, lost service miles

and hours shall be calculated and stored for later

reporting. Lost service and miles shall be displayed to

OCC.




June 19, 2020 78

6.5 Data Feeds and Application Programming Interfaces

This section lists requirements for standard data feed for passenger information application development by third

parties and APIs for obtaining CAD/AVL and VHM datasets for third party reporting application developments.

6.5.1 Schedule Information Data Feed (GTFS)

This section defines requirements for the GTFS feed to be generated by the Contractor.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.5.1.1 The CAD/AVL system shall export schedule data in

General Transit Feed Specification (GTFS) format.

6.5.1.2 The exported data (hereinafter referred to as the ‘GTFS

dataset’) shall be designed in accordance with GTFS Best

Practices, and shall include all the required GTFS files as

well as optional files designated by MCTS as part of the

design review process.

6.5.1.3 For each GTFS file, the GTFS dataset shall include all the

required fields as well as optional fields designated by

MCTS as part of the design review process.

6.5.1.4 The Contractor shall verify that the exported GTFS

datasheet shall result in zero (0) critical warnings when

tested using the Google-provided schedule validator.

6.5.1.5 All data generated by the GTFS Schedule Module including

the GTFS dataset shall be the property of MCTS. MCTS

shall have the right to store and use this data, and provide

it to third-parties.

MCTS shall be provided a perpetual and royalty free

license for access to the GTFS dataset including the right

for MCTS to provide the data to external entities of its

choosing.

6.5.1.6 The Contractor shall coordinate with MCTS to resolve any

abnormal situations in trip planning, including but not

limited to the following:

6.5.1.6.a • Excessive walking to/from an origin/destination

transit stop;

6.5.1.6.b • Stops connected by a straight line on the map

instead of following the appropriate route trace;

6.5.1.6.c • Excessive wait-time suggested for transfers; and

6.5.1.6.d • Major and minor stop locations not marked on the

map.

6.5.1.7 The Contractor shall provide the option to host GTFS feeds

for access by third parties.




June 19, 2020 79

6.5.2 Real-Time Information Data Feed

This section defines requirements for the GTFS-realtime feed to be generated by the Contractor.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.5.2.1 The system shall output the following real-time vehicle

location information through GTFS-realtime feeds:

6.5.2.1.a • Vehicle positions;

6.5.2.1.b • Trip updates; and

6.5.2.1.c • Service alerts.

6.5.2.2 The Vehicle Positions feed shall include:

6.5.2.2.a • Locations for all vehicles in service;

6.5.2.2.b • Status of a vehicle with respect to which stop it is

stopped at, incoming at, or in transit to (i.e. current

status field); and

6.5.2.2.c • Buses that have been taken out of service.

6.5.2.3 The Trip Updates feed shall include:

6.5.2.3.a • Predicted arrival and departure times;

6.5.2.3.b • Trip additions and cancellations (i.e., schedule

relationship field at the trip-level); and

6.5.2.3.c • Skipped stops (i.e., schedule relationship field at the stop-level).

6.5.2.4 The Service Alerts feed shall include, for all current and future service alerts, the following:

6.5.2.4.a • Header and description;

6.5.2.4.b • Cause and effect;

6.5.2.4.c • Active period(s);

6.5.2.4.d • Affected entities including agency, route, mode, trip

and stop; and

6.5.2.4.e • A uniform resource locator (URL), where entered.

6.5.2.5 The Service Alerts feed shall include all of the latest service alerts entered by dispatchers through the CAD/AVL system.

6.5.2.6 The Service Alerts feed shall incorporate alerts that are categorized by at least the following entity types:

6.5.2.6.a • Route;

6.5.2.6.b • Trip; and

6.5.2.6.c • Stop.




June 19, 2020 80


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.5.2.7 Recipients of the Service Alerts feed shall be able to

identify if certain Service Alerts are associated with only

specific routes (in the case of route entity identification),

only specific trips (in the case of trip entity identification),

only specific stops (in the case of stop entity identification),

or some combination of these.

6.5.2.8 The CAD/AVL system shall update the GTFS-real-time data feeds 1) immediately after new content is available, OR 2) every 30 seconds, whichever is more frequent.

6.5.2.9 The GTFS-realtime data feed shall be designed to be consistent with the CAD/AVL system's GTFS data.

6.5.2.10 The Contractor shall validate GTFS-realtime feed for accuracy.

6.5.2.11 The Contractor shall provide the option to host GTFS feeds for access by third parties.

6.5.3 CAD/AVL API

This section lists requirements for an API to provide real-time data on operations.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.5.3.1 The Contractor shall provide an API for obtaining key data

fields from the CAD/AVL system. Details of the API shall be

finalized at the time of design.

6.5.3.2 When requested, the API shall provide the following data:

6.5.3.2.a • Current vehicle location data;

6.5.3.2.b • Current route and schedule adherence data; and

6.5.3.2.c • Active incidents.

6.5.4 VHM Data API

This section lists requirements for an API to obtain real-time data on vehicle component health.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.5.4.1 The CAD/AVL system shall output the real-time vehicle

maintenance and diagnostics data through an API. Details

of the API shall be finalized at the time of design.




June 19, 2020 81


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.5.4.2 The CAD/AVL system shall provide the following

information through API calls:

6.5.4.2.a • Monitored component status (by vehicle);

6.5.4.2.b • Critical faults or equipment failures (by vehicle or

by monitored component) expressed as J1939

SNP/FMI (PID) data or diagnostic trouble codes,

including:

o CAD/AVL;

o AVA;

o Wheelchair ramp;

o Covert alarm; and

6.5.4.2.c • Pre-trip and post-trip inspection results.

6.6 Operational Data and Business Intelligence Reporting

This section defines requirements for storing and accessing data for operational and business intelligence uses.

6.6.1 Operations Reporting Database


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.1.1 The Contractor shall supply an operations reporting

database to support business intelligence data storage and

reporting functions for authorized system users at MCTS.

6.6.1.2 The reporting database shall support querying and data

extraction using SQL to support broader MCTS business

functions, including with the existing MCTS data analysis,

business intelligence, and report generation tools.

6.6.1.3 MCTS shall always have ownership and control of the data

stored in the reporting database. No confidential data

(network, financial, employee, etc.) shall be hosted on any

third-party or Contractor system without the expressed

written permission of MCTS.

6.6.1.4 The Contractor shall automate the data transfer process

between the system and the reporting database, so as not

to require MCTS staff’s day-to-day involvement.

6.6.1.5 The data transfer process will generate a daily log of data

upload activities and will alert staff in the event of an upload

failure.




June 19, 2020 82


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.1.6 The data transfer logic shall have exception handling built-

in to avoid uploading any unwarranted data.

6.6.1.7 Data transfer settings and status shall be accessible to

monitor and configure through an administrative interface

and dashboard. The system administration tool shall also

allow management of user roles and privileges for

accessing reports.

6.6.1.8 The system’s backup and recovery functions shall enable

MCTS to create backup copies of all operations reporting

database content, stored externally from the system.

6.6.1.9 The system shall enable the reporting database to be

restored from a backup in case of database crashes.

6.6.2 Data Playback

This section defines requirements for a tool to integrate and replay historical operations data.


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.2.1 The Contractor shall supply a tool to enable integrated

playback of all historical data from the CAD/AVL system

(such as vehicle locations, statuses, messages, and the

VHM subsystem) regardless of vehicle logon status, as well

as integrated feeds from other MCTS operations systems,

including the:

6.6.2.1.a • Voice communications recordings;

6.6.2.1.b • GTFS-realtime feeds;

6.6.2.1.c • Automated Vehicle Announcement System; and

6.6.2.1.d • Onboard Surveillance System.

6.6.2.2 The data playback tool shall enable the user to select which

data feeds to incorporate into a playback analysis, and view

instantaneous, synchronized feeds from all selected

sources as part of an integrated, simultaneous playback.

6.6.2.3 The playback tool shall include a function to assess

recorded real data in comparison with planned data, e.g.

instantaneous real vs. scheduled bus location.

6.6.2.4 The system shall provide playback controls to view the

entire sequence of data from the beginning of the time

period, including:

6.6.2.4.a • Pause;

6.6.2.4.b • Play forward;




June 19, 2020 83


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.2.4.c • Skip forward; and

6.6.2.4.d • Skip reverse.

6.6.2.5 The play forward/reverse playback control shall enable the

user to run the playback at slower, faster, and equal to real

speed.

6.6.2.6 The data playback tool shall enable the user to flag

timepoints during playback for revisiting, and comment on

flagged timepoints.

6.6.2.7 The data playback tool shall enable the user to create and

export integrated playback data clips including all selected

data feeds, in one record. The system shall enable the user

to select the start and end times of clips to a precision of

one (1) second.

6.6.2.8 The system shall, when designated, store vehicle data

playback in a video file format that can be exported for

viewing on a different computer equipped to view such files

using a standard video file format such as .avi or .mpg.

6.6.2.9 The system shall be able to export a still image of the

vehicle data playback view as a .pdf, .jpg, or .png.

6.6.2.10 Any exported video or still image vehicle data playback

export shall indicate for each vehicle icon the vehicle and

operator number as well as the date and time.

6.6.2.11 The system shall be able to run playback functions without

interrupting live dispatching functions.

6.6.2.12 The system shall allow playback for a single vehicle,

selected set of vehicles or all vehicles on the selected map

view for selected time period.

6.6.2.13 The system shall allow playback for a single route, selected

set of routes or all routes on the selected map view for

selected time period.

6.6.2.14 The system shall allow selection of any time period for the

historical data stored in the database.

6.6.3 Reporting


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.3.1 The Contractor shall supply a reporting tool and any

required software interfaces to retrieve real-time and

historical data from the system databases.




June 19, 2020 84


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.3.2 The business intelligence tool GUI shall include analytical

functionality in addition to raw data reporting functionality

(e.g. differences between scheduled and actual

performance, including service hours, deadhead hours,

revenue miles, revenue hours, etc.).

6.6.3.3 All dashboards, worksheets, and reports shall support

custom MCTS branding, including colors, fonts, and logos.

6.6.3.4 The reporting tool shall provide a set of agency-

configurable graphics used to represent key performance

indicators (KPIs) as defined by MCTS.

6.6.3.5 The reporting tool shall report all KPIs in real-time, where

data is available to support real-time reporting. The

delivered system shall provide real-time displays for

schedule performance and service adjustment data by

default.

6.6.3.6 The reporting tool shall incorporate levels of data to allow

the user to filter by:

6.6.3.6.a • Date and time;

6.6.3.6.b • Route;

6.6.3.6.c • Block;

6.6.3.6.d • Operator;

6.6.3.6.e • Facility;

6.6.3.6.f • Municipality;

6.6.3.6.g • Geographical area; and

6.6.3.6.h • Keywords (e.g. for incident records).

6.6.3.7 The reporting tool shall have an easy-to-use GUI that

allows the standard user to create reports, KPIs, and

dashboards as desired without requiring intervention from

the system administrator.

6.6.3.8 Each user shall be able to save a configuration and set of

KPIs for future use. This configuration shall be

automatically loaded the next time the user opens the tool.

6.6.3.9 Each created dashboard, KPI, and report shall be

shareable with other users through an email link. The

system shall identify if the recipient does not have

sufficient permissions to access the form and alert the

sender prior to sending.

6.6.3.10 The reporting tool shall be intuitive and require no training

or prior knowledge of databases and query methods for

basic use. The Contractor shall provide a training course

on advanced features of the tool.




June 19, 2020 85


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.3.11 All reports and dashboards provided by the business

intelligence tool shall be filterable, and shall provide

information in real-time, and in historical time intervals

configurable by MCTS to time increments as short as one

minute.

6.6.3.12 The reporting tool shall allow MCTS system administrators

to define particular user groups and the permissions and

views available to each user group.

6.6.3.13 An ICD and data dictionary shall be provided by the

Contractor to allow third-party applications to pull read-

only data from the reporting tool.

6.6.3.14 The reporting tool shall enable the export of any CAD/AVL

or database data using a common export format (e.g., text

file, CSV, Microsoft Excel, and portable document format

[PDF]).

6.6.3.15 The reports shall provide the ability to drill-down and drill-

through reported information.

6.6.3.16 The reporting interface shall allow MCTS to generate ad-

hoc reports, including customizing variants of standard

reports.

6.6.3.17 The reports shall include the date generated and the

system user ID of the report generator.

6.6.3.18 The Contractor shall work with MCTS as part of the design

review to determine the requirements for each of the

following reports:

6.6.3.19 Operations:

6.6.3.19.a • On-time performance: Shall report on schedule adherence patterns by date, day of week, time of day, route, and timepoint;

6.6.3.19.b • Logon/logoff summary: Shall report on vehicle operator logon and logoff statistics comparing scheduled and actual times for logon and logoffs, route, block, vehicle ID, and operator ID;

6.6.3.19.c • Vehicle operator workpiece summary: Shall report on the actual pieces of work each vehicle operator performed in the field in comparison with the scheduled piece of work for each run by comparing the following data: logon/logoff times, vehicle, block, operator ID, and timepoint crossings;

6.6.3.19.d • Operator performance summary: Shall report on vehicle operator performance with respect to schedule adherence at timepoints. The reports shall be run by date, day of week, time of day, route, and stop;




June 19, 2020 86


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.3.19.e • Running times: Shall report on running time by timepoints and timepoint segments and run the reports by date, day of week, time of day, route, and stop;

6.6.3.19.f • Added trips: Shall report on additional trips that were not prescheduled and were introduced to meet passenger demand in real-time;

6.6.3.19.g • Dwell time summary: Shall report on dwell times at stops by date, day of week, time of day, route, and stop;

6.6.3.19.h • Mobility Aid and Bicycle Boarding Summary: Shall report on boardings reported in CAD/AVL that involve mobility aids and bicycles;

6.6.3.19.i • Space-time diagram: Shall provide a visualization of scheduled and actual trips by creating a scatterplot of timepoint locations and arrival/departure times;

6.6.3.19.j • Missed trips summary: Shall report trips that could not be performed;

6.6.3.19.k • Deadhead summary: Shall report on deadhead miles and distinguish pullout and pull-in events from other deadheads (e.g., when start or end point of a deadhead in not the garage);

6.6.3.19.l • Headway reliability summary: Shall provide a comparative summary of actual and scheduled headways for each timepoint;

6.6.3.19.m • Voice and data communication (or event log) summary including response times: Shall report on a chain of activities tied to inbound and outbound communications. For example, when a vehicle operator initiates an RTT and upgrades that to a PRTT. The report should be able to link these activities to create a record of activities tied to the original RTT request;

6.6.3.19.n • Off-route summary: Shall report on start and end points and start and end times of off-route events by date, day of week, time of day, route, and operator;

6.6.3.19.o • System health summary: Shall report on current health of each equipment and computer hardware that is part of the ITS system;

6.6.3.19.p • Road call summary: Shall report on the road calls vehicle operators/dispatchers make;

6.6.3.19.q • Incidents summary: Shall report on any incidents by type and relevant summary information; and

6.6.3.19.r • Incidents detail: Shall report on incidents by type with all collected data.

6.6.3.20 Maintenance:




June 19, 2020 87


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.3.20.a • Real-time vehicle availability: Shall be able to provide the current availability of a vehicle based on the current health of maintenance components and on-board ITS equipment on that vehicle;

6.6.3.20.b • Maintenance work summary: Shall report on identified problem, resolution, and cause for ITS and non-ITS maintenance works; and

6.6.3.20.c • Repeat failures summary: Shall report on recurring maintenance issues.

6.6.3.21 System administration and alarm/failure monitoring:

6.6.3.21.a • On-board equipment status: Shall report on the functional status of hardware and software versions (e.g., MDT software version, route version, farebox software version, destination sign software version);

6.6.3.21.b • Vehicle uploads and download summary: Shall report on the status of the WLAN data exchange by indicating successful, in progress, or failed data transfers;

6.6.3.21.c • Real-time information accuracy: Shall report on the accuracy of disseminated real-time information on predicted arrival/departure; and

6.6.3.21.d • Real-time information usage on web and other personal media devices: Shall report on the use of dissemination media.

6.6.3.22 OCC:

6.6.3.22.a • Response Time: Shall report on individual and average time from when a RTT or PRTT was triggered to when the dispatcher initiated communications;

6.6.3.22.b • Detour Management: Shall report on service measures implemented by type of measure;

6.6.3.22.c • Incident Management Summary: Shall report on incidents created, active durations, and incidents closed;

6.6.3.22.d • OCC Work: Shall report on number of average vehicles and routes active; and

6.6.3.22.e • Session Time: Duration of log-on.

6.6.3.23 OCC statistics shall be automatically reported by the

system and made available to the OCC supervisor as

summary reports by day of week, week of month and

month of year.

6.6.3.24 In addition to above specific reports, the Contractor shall

provide all reports needed by the National Transit

Database for operations, revenue and safety data

reporting.




June 19, 2020 88


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

6.6.3.25 The reporting interface shall provide spatial or temporal

segmentation of summary data ‘on the fly’ (if applicable)

by the following parameters:

6.6.3.25.a • Route and direction;

6.6.3.25.b • Variation/Pattern;

6.6.3.25.c • Stop and timepoint;

6.6.3.25.d • Communication type (applicable only to

communication reports, for example, RTT, PRTT,

and covert microphone events);

6.6.3.25.e • Jurisdiction/Agency;

6.6.3.25.f • Trip;

6.6.3.25.g • Run;

6.6.3.25.h • Block;

6.6.3.25.i • Vehicle; and

6.6.3.25.j • Time of day, day of week, month, rating, fiscal

year, and calendar year.




June 19, 2020 89

7 External Systems Integration

This section lists integration requirements between the CAD/AVL and external systems, both in on-board and central contexts.

7.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.1.1 The Contractor shall provide interfaces and all necessary

interface control document’s (ICD's) to existing onboard

systems provided including but not limited to:

7.1.1.a • Odometer;

7.1.1.b • Destination signage;

7.1.1.c • Automated Vehicle Announcement System (AVA);

7.1.1.d • Farebox and Fare Collection Systems;

7.1.1.e • Onboard Surveillance System;

7.1.1.f • Potential future battery charge monitoring systems

(e.g. for battery-electric buses); and

7.1.1.g • Network Management System.

7.1.2 The system shall support a single point of logon from the

MDT for all interfaced onboard components.

7.1.3 The VLU shall synchronize the dispatcher date/time for all

integrated systems at least daily with the MCTS system

time.

7.1.4 The CAD/AVL system shall enable patches and updates to

external system integrations to be tested without affecting

live operations, prior to deploying these updates enterprise-

wide.

7.2 Odometer


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.2.1 The VLU shall interface with the existing vehicle odometer,

receiving the digital or analog signal and determining the

distance traveled since the MDT was logged on.

7.2.2 The system shall reconcile the signal received from the

vehicle odometer with the system’s GPS-odometer to

correct inaccuracies in the vehicle’s reported position.




June 19, 2020 90

7.3 Destination Signage


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.3.1 The VLU shall integrate with the existing destination sign

controller to display text on destination signs.

7.3.2 The Contractor shall confirm if any upgrades to the

destination sign or destination sign controller firmware are

needed to implement this interface. MCTS will complete

needed upgrades.

7.3.3 The system shall enable fully automated and manually-

triggered downloads of new destination sign data whenever

updates are available, as part of routine data

synchronization with the central system.

7.3.4 The vehicle operator shall continue to be able to use all

features of the existing destination sign controller,

regardless of whether the vehicle operator has logged into

a run using the MDT or whether the MDT is operational.

7.3.5 The system shall automatically display the appropriate

overhead destination sign message(s) based upon the

route/block of service the vehicle is logged on to perform.

7.3.6 The onboard system shall allow operator and dispatcher

override of the destination sign code and log such

overrides.

7.3.7 At an MCTS-configurable distance before each trip starts,

the system MDT shall change the destination sign

message to display an MCTS-configurable message.

7.3.8 When the vehicle is logged into a run using the MDT but

operating on deadhead from the garage to the first trip of

the run, the system MDT shall automatically command the

destination sign to display a message that MCTS can

configure. This message could be “OUTBOUND”,

“INBOUND”, “OUT OF SERVICE”, “FROM GARAGE” or

the message the vehicle will display during the first trip.


operating on deadhead to the garage from the final trip of

the run, the system MDT shall automatically command the

destination sign to display a message that MCTS can

configure. This message could be “OUT OF SERVICE”,

“TO GARAGE” or the message the vehicle will display

during the final trip.




June 19, 2020 91


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)


operating on deadhead for interlining between trips in the

course of a run, the system MDT shall automatically

command the destination sign to display a message MCTS

can configure. This message could be “OUT OF SERVICE”

or the message displayed during either the previous or

upcoming trip.

7.3.11 When the vehicle is logged into any run using the MDT, the

vehicle operator shall be able to manually command the

destination sign to display one of a set of preconfigured

messages MCTS can configure (e.g., “OUT OF SERVICE”,

“IN TRAINING”).

7.3.12 The MDT shall notify the operator of overhead destination

sign malfunctions.

7.3.13 The system shall generate a fault and log all overhead

destination sign malfunctions on board the vehicle, as

reported by the sign system. Logs shall include block,

route, operator ID, vehicle ID, date, time, and GPS location.

These logs shall be available either through a system

reporting function or through WLAN communications within

the vehicle.

7.4 Automated Vehicle Announcement System


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.4.1 The system shall integrate with the existing AVA equipment

to provide:

7.4.1.a • Automatic operator and trip/block logon to the AVA

system;

7.4.1.b • Manual triggering and canceling of canned

passenger announcements by operators through

the MDT interface; and

7.4.1.c • Real-time sending and manual triggering of free-

form and canned passenger announcements by

dispatchers.

7.4.2 Automated announcements shall continue to operate

normally when the vehicle is in covert alarm mode.

7.4.3 The integration with the AVA system shall enable OCC

initiated service adjustments and detour management

actions to disable stop announcements, or trigger modified

announcements to support out of service stops.




June 19, 2020 92

7.5 Fare System


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.5.1 The system shall integrate with MCTS's onboard fare

payment components to:

7.5.1.a • Provide operator ID and block/trip ID logon

information to the fare payment system;

7.5.1.b • Provide route, direction of travel, trip and fare set

info to the fare payment system;

7.5.1.c • Update the fare system when there is a change to

the run, route, trip, or operator;

7.5.1.d • Provide stop ID or trip information to the fare

payment system;

7.5.1.e • Provide time synchronization to the fare payment

system;

7.5.1.f • Provide geolocation data to the fare payment

system for the purpose of tagging fare transactions

with time and location information;

7.5.1.g • Provide segmentation data to the fare payment

system at the beginning of each trip; and

7.5.1.h • Receive fault codes from the fare payment system.

7.5.2 The system shall allow the operator to use all fare payment

system components manually when the MDT is not

operational or is not communicating with the fare payment

system.

7.5.3 The Contractor shall determine any need for fare payment

system upgrades to accomplish functionalities listed in this

section. MCTS will provide any upgrades needed to meet

functional requirements.

7.6 Onboard Surveillance System


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.6.1 The Contractor shall integrate with the existing CCTV/DVR

equipment provided by Apollo to enable the following

functions:

7.6.1.a • Setting the event flag on the digital video recorder

(DVR) when the covert alarm is triggered;




June 19, 2020 93


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.6.1.b • Tagging live and recorded video images with

metadata including:

o Vehicle number;

o Vehicle location;

o System time;

o Vehicle operator ID;

o Trip ID; and

7.6.1.c • Automatically showing the dispatcher a live video

feed from a vehicle when a PRTT or Covert Alarm

is active. This can be accomplished by either:

o Integrating the video feed directly into the

CAD/AVL software; or

o Automatically opening the Apollo video

software and loading video feeds from the

relevant vehicle.

7.6.2 The Contractor shall determine any CCTV/DVR upgrades

needed to meet requirements. MCTS shall implement any

required upgrades needed to meet system requirements.

7.6.3 The Contractor shall be responsible for connecting and

testing all interfaces, label all sources, and confirm that

video is correctly tagged and stored.

7.6.4 The system shall alert the operator, OCC and the central

video surveillance system of any CCTV/DVR hardware and

software that is disabled or malfunctioning.

7.6.5 The system shall receive a status messages that the

CCTV/DVR transmits, including fault codes, and notify the

operator, OCC, and the central video surveillance system

of any system faults.

7.6.6 The system shall provide current latitude/longitude data to

the onboard surveillance system in real time but not less

frequently than every two (2) seconds.

7.6.7 The VLU shall provide time synchronization to the

CCTV/DVR system.




June 19, 2020 94

7.7 Battery Charge Monitoring Systems


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.7.1 The system shall support integration with potential future

battery charge monitoring systems on Battery-Electric

Buses (BEBs) to provide:

7.7.1.a • Time synchronization with the battery charge

monitoring system;

7.7.1.b • Single-point operator log-on;

7.7.1.c • Block data to the battery charge monitoring

system; and

7.7.1.d • Real-time battery charge levels to dispatchers

within the CAD/AVL application user interface.

7.8 Network Management System


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

7.8.1 The central system shall integrate with the existing MCTS

Network Management System (SolarWinds) by

automatically sending, receiving, and storing all necessary

data to support existing NMS system management

functionality, including:

7.8.1.a • Fault management;

7.8.1.b • Configuration management;

7.8.1.c • Performance management;

7.8.1.d • Security management; and

7.8.1.e • Provisioning management.

7.8.2 Integration between the central system and the Network

Management System will be achieved through a direct

service.




June 19, 2020 95

8 Project Implementation

8.1 Project Management

8.1.1 Project Staff


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.1.1 The Contractor shall appoint a Project Manager, who will

be the primary point of contact with MCTS.

8.1.1.2 The Project Manager or their deputy shall participate in all

scheduled project activities, attend scheduled meetings,

and promptly respond to new meeting requests, requests

for information, technical support, or other necessary

communication activities.

8.1.1.3 The Contractor shall provide relevant education,

experience and qualifications for at least the following:

8.1.1.3.a • Project manager;

8.1.1.3.b • Technical lead/Project engineer; and

8.1.1.3.c • Training lead.

8.1.1.4 MCTS may, at its discretion, require that the Contractor

provide an alternate resource, should MCTS deem one of

the proposed Contractor personnel unsuitable for any

reason.

8.1.1.5 The Contractor shall provide written notice to MCTS at

least two weeks in advance of any change in key personnel

indicating the specific reason, and the qualifications of the

new personnel. The change in key personnel must be

approved by MCTS before the change can occur.

8.1.1.6 Contractor shall make the following staff available in person

for every onsite design review and testing activity:

8.1.1.6.a • Project manager;

8.1.1.6.b • Project engineer (or a substitute staff-person if the

intent of the onsite meeting is to discuss some

other topic of relevance, such as network

integration); and

8.1.1.6.c • Additional staff as per Contractor needs.

8.1.1.7 Contractor shall provide an onsite Project Engineer for the

following periods:

8.1.1.7.a • For both dry run and formal testing activities;

8.1.1.7.b • While installations are underway; and

8.1.1.7.c • As needed for project activities.




June 19, 2020 96


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.1.8 Contractor shall notify and request approval for all other

onsite meetings and onsite presence of Contractor staff.

8.1.2 System Implementation Plan (SIP)


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.2.1 The Contractor shall prepare a System Implementation

Plan (SIP), including the detailed implementation activities,

a project schedule, roles, and responsibility of parties in the

proposed project team, progress milestones/status and

assigned staff.

8.1.2.2 The SIP shall include details on transitioning from the

current system to the new system provided by the

Contractor. The Transition Plan shall be developed such

that MCTS operations are not impacted in any way due to

project implementation activities.

8.1.2.3 The Project Schedule shall be implemented in PERT,

GANTT, or equivalent form to show MCTS and any third-

party responsibilities and activities and their associated

dependencies.

8.1.2.4 The Contractor shall also include a Safety Management

Plan in their SIP, which shall detail their responsibilities and

procedures for safety during the different phases of the

project, including (1) conducting pre-installation surveys to

identify potential project safety hazards; (2) identifying

project hazard control procedures, including occupational

(worker) and public hazards; (3) providing project safety

orientation and training to its subcontractors and MCTS

staff who will be involved in the project; and (4) furnishing

procedures and training for project accident reporting and

investigations.

Additionally the Contractor shall provide documentation on

safety certification process that highlights areas of concern,

for example, how the new system will impact bus

operators, dispatchers, and or supervisors, if measures

have been considered and dealt with relating to potential

safety concerns that the new system and or sub

components of the system may have on MCTS daily

operations.

8.1.2.5 The initial draft of the SIP shall be provided to MCTS within

two weeks from notice to proceed (NTP).




June 19, 2020 97


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.2.6 The revised SIP, addressing comments from the first onsite

meeting, shall be provided to MCTS within two weeks after

this meeting.

8.1.2.7 The SIP must be approved and accepted by MCTS before

it can become effective.

8.1.2.8 The SIP shall be updated by the Contractor monthly to

reflect the progress attained in the previous month and the

anticipated changes in the future. The updated SIP shall be

submitted to MCTS at the beginning of each month.

8.1.2.9 Any updates to the SIP including the project schedule shall

be detailed and clearly expressed to MCTS. The updated

Project Schedule shall clearly identify all affected tasks new

start and end dates, and updated task duration.

8.1.2.10 The SIP shall include a rollout plan for all MCTS and

contractor vehicles.

8.1.2.11 The SIP shall identify planned delivery of documentation.

8.1.2.12 The Contractor shall include in the SIP, the necessary time

and resources to modify documentation to incorporate

comments from MCTS. The Contractor should assume a

minimum of two weeks for MCTS to provide comments on

submission.

8.1.2.13 The Contractor shall include in the SIP the time for MCTS

to review the revised documentation.

8.1.3 Coordination Meetings


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.3.1 The Contractor shall participate in person in a kick-off

meeting between the MCTS project team and the

Contractor team at the start of the project.

8.1.3.2 The Contractor shall convene regular progress review

meetings, such as:

8.1.3.2.a • Weekly or bi-weekly design/contract review

meetings with MCTS; and

8.1.3.2.b • Technical and contractual interface meetings with

subcontractors, if any.




June 19, 2020 98


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.3.3 The agenda for these meetings shall be to discuss the

most current status of and plans related to all issues

identified in the recent releases of the SIP and action item

list (AIL).

8.1.3.4 MCTS reserves the right to identify for discussion any

additional issues beyond those in the SIP and AIL.

8.1.3.5 A status report shall be issued to MCTS at least two days

prior to each conference call, including:

8.1.3.5.a • An agenda for the upcoming conference call

highlighting key discussion items; and

8.1.3.5.b • An updated AIL with the updates incorporating the

discussions of the previous bi-weekly conference

call as well as other subsequent developments

since the previous AIL release.

8.1.3.6 The Contractor shall be available to meet the MCTS

Project Manager in person upon request for resolution of

major obstacles or significant schedule delays.

8.1.3.7 The Contractor shall be represented in these conference

calls by at minimum their Project Manager as well as any

additional Contractor staff necessary to properly address

the current issues and project status.

8.1.3.8 MCTS will be represented by its designated implementation

management representatives.

8.1.3.9 Conference call facilities shall be arranged and paid for by

the Contractor.

8.1.3.10 The Contractor shall submit minutes within two days of

each conference call.

8.1.4 Action Item List


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.4.1 The Contractor shall maintain an Action Items List (AIL),

indicating for each item the following:

8.1.4.1.a • Item number;

8.1.4.1.b • Date generated;

8.1.4.1.c • Item priority;

8.1.4.1.d • Brief item descriptive title;

8.1.4.1.e • Assigned person with lead resolution responsibility;




June 19, 2020 99


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.1.4.1.f • Date resolved; and

8.1.4.1.g • Ongoing dated notes on resolution status.

8.1.4.2 The Contractor shall sort AIL primarily by unresolved vs.

resolved items, priority, and by the date the item was

generated.

8.2 System Design

8.2.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.1.1 At the first onsite meeting, the Contractor shall be prepared

to discuss MCTS feedback on draft SIP and conduct a

Requirements Review (RR).

8.2.1.2 At the second onsite meeting, the Contractor shall be

prepared to discuss MCTS feedback on draft Design

Review documentation.

8.2.2 Requirements Review


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.2.1 The Contractor shall participate in the requirements review

(RR) as part of the first onsite meeting to discuss the

contractually agreed requirements for design. The RR will

initialize the Requirements Matrix. The Contractor shall use

this Matrix to produce the draft Design Document for

conducting the preliminary design review (PDR) at the

second on-site meeting. The RR meeting shall review the

following for each contract requirement: (1) MCTS’s design

intent; (2) the intended Contractor design approach; and (3)

the Contractor’s approach to demonstration through the

acceptance testing process.

8.2.2.2 The Contractor shall prepare a traceability matrix with

finalized contract requirements after the RR meeting. This

matrix will be referred to as the requirements matrix (RM)

hereafter.




June 19, 2020 100

8.2.3 Gap Analysis


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.3.1 The Contractor shall review the current system

environment at MCTS and prepare a gap analysis report as

part of the design phase. The gap analysis shall include at

least the following:

8.2.3.1.a • Format and accuracy of route and stop data;

8.2.3.1.b • Data conversion for fixed-route schedule;

8.2.3.1.c • Data import of base map;

8.2.3.1.d • Data conversion for passenger complaint

information;

8.2.3.1.e • Data conversion for incidents and detour

information;

8.2.3.1.f • All Interfaces to external systems;

8.2.3.1.g • Existing paper format reports;

8.2.3.1.h • Existing pre-trip and post-trip inspection forms;

8.2.3.1.i • Existing yard management process;

8.2.3.1.j • Network infrastructure; and

8.2.3.1.k • Computer hardware infrastructure.

8.2.4 Preliminary Design


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.4.1 The preliminary design document (PDD) shall include the

following materials:

8.2.4.1.a • A conceptual diagram illustrating all elements in

the system and data flow;

8.2.4.1.b • An overview of the equipment, system, and

configuration proposed for implementation;

8.2.4.1.c • Detailed technical documentation for each

equipment item;




June 19, 2020 101


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.4.1.d • Detailed technical documentation on all software,

addressing:

o Each module’s functions;

o The formats, content and features of all

user interface screens and dashboards;

o The formats and content types for all

reports;

o The data fields to be included in all data

exchange interfaces;

o All database structures;

o Any proprietary interfaces;

o Any other software aspects warranting

advance agreement with MCTS before

system customization/configuration; and

8.2.4.1.e • A table providing cross-references for each section

of the PDD to the appropriate element of the RM.

8.2.4.2 As part of the technical documentation for the system

equipment, the Contractor shall provide specifications and

diagrams for the recommended dispatcher workstation

layout, including hardware and a concept showing the

Contractor’s suggested arrangement of application

windows on all screens.

The Contractor shall indicate a recommended number of

desktop monitors per workstation and monitor

specifications (e.g. aspect ratio) to support what the

Contractor considers optimal viewing of all applications and

windows associated with the system (e.g. without

minimizing/layering windows). Regardless of this

recommendation, the Contractor’s recommended hardware

shall include support for a minimum of 4 monitors. MCTS

shall procure the workstation hardware separately.

8.2.4.3 The PDD shall include the necessary ICDs.

8.2.4.4 An ICD shall be included for the following interfaces:

8.2.4.4.a • All data inputs;

8.2.4.4.b • All configuration files;

8.2.4.4.c • All application programming interfaces (APIs); and

8.2.4.4.d • Other interfaces in the proposed solution.

8.2.4.5 The ICDs shall include:

8.2.4.5.a • Description of data formats into and out of the

interface;




June 19, 2020 102


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.4.5.b • Description of the data structure;

8.2.4.5.c • Description of the data protocol; and

8.2.4.5.d • A data dictionary.

8.2.4.6 MCTS shall retain exclusive and perpetual license to

reproduce and share ICD with third parties for the purposes

of integration and contracted work.

8.2.4.7 The RR and PDR meetings shall include a review of the

facilities and available resources that may need to be

updated to accommodate the added technologies. The

Contractor shall determine and detail the exact demand of

resources such as electrical power and HVAC.

8.2.5 Final Design


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.2.5.1 The Contractor shall update the PDD based on MCTS

feedback and submit the updated documentation as the

final design document (FDD).

8.2.5.2 The FDD shall include the following materials:

8.2.5.2.a • Updated PDD incorporating MCTS feedback and

comments;

8.2.5.2.b • Final list of equipment to be procured;

8.2.5.2.c • Final design and configurations of the system to be

built including all customizations to be made to the

system; and

8.2.5.2.d • An updated table providing cross-references

between sections in the FDD and elements of the

RM.

8.2.5.3 The PDD and FDD are intended only to reduce the chance

of any misunderstandings on the design intent or

interpretation of the contract requirements. The FDD shall

not alter the need for each requirement’s successful formal

demonstration through Acceptance Testing process.

8.2.5.4 The FDD shall be modified as necessary to address

feedback and comments from MCTS, until the FDD is

accepted.




June 19, 2020 103

8.3 Documentation

8.3.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.3.1.1 All documentation shall be in English and utilize US

customary units.

8.3.1.2 All documentation shall be submitted directly to MCTS

electronically in the following formats, as relevant:

8.3.1.2.a • MS Office formats (DOC, XLS, PPT, VSD);

8.3.1.2.b • Adobe PDF (searchable); and

8.3.1.2.c • Scanned documents consisting of signatures, etc.

may be approved for submittal.

8.3.1.3 All submissions to the MCTS Project Manager shall be via

email or via an online repository used for sharing files,

such as SharePoint, as approved by MCTS.

8.3.1.4 Equipment installation drawings shall be prepared and

submitted in AutoCAD and/or Adobe Acrobat formats and

accompanied with calculations, material specifications,

process specifications, and test data required to support

review and approval of the drawings.

8.3.1.5 Electrical and electronic drawings shall be supplied to

show engineering changes made to any component or

module up to the end of the warranty period of the system

supplied.

8.3.1.6 All revisions necessary to the documentation shall be

done by the Contractor at no additional cost to MCTS.

8.3.1.7 Manuals shall be complete, accurate, up-to-date, and shall

contain only information that pertains to the system

installed.

8.3.1.8 All pages of the documentation shall carry a title, version

number and issue date, and they shall contain a complete

subject index. The Contractor shall be responsible for fully

coordinating and cross-referencing all interfaces and

areas associated with interconnecting equipment and

systems.

8.3.1.9 Documentation shall require re-issues if any change or

modification is made to the equipment proposed to be

supplied. The Contractor may re-issue individual portions

of the documentation that are affected by the change or

modification. Each re-issue or revision shall carry the

same title as the original with a change in version number

and issue date.




June 19, 2020 104


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.3.1.10 Submission of revisions shall be accompanied with a

comment-by-comment response to MCTS prior

comments.

8.3.1.11 The System Documentation shall include at least the

following:

8.3.1.11.a • System Implementation Plan (SIP);

8.3.1.11.b • Preliminary and Final Design Documents (PDD)

(FDD);

8.3.1.11.c • Acceptance Test Plan (ATP);

8.3.1.11.d • Installation Design Document (IDD);

8.3.1.11.e • Interface Control Document (ICD);

8.3.1.11.f • Test Results Documentation (TRD);

8.3.1.11.g • Maintenance and Operations Support Plan;

8.3.1.11.h • As-Built Document (ABD);

8.3.1.11.i • Operations, Maintenance, Training and User

Manuals; and

8.3.1.11.j • Disaster Recovery Documentation.

8.3.2 System Configuration


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.3.2.1 The Contractor shall create a detailed list of all system configurations by individual system component. The Contractor shall also indicate which of these configurations is user-configurable and which require intervention by the Contractor.

8.3.2.2 The Contractor shall document configurations of the fixed-

end computer hardware and networking infrastructure

(e.g., list of IP addresses).




June 19, 2020 105

8.3.3 As-Built Documentation


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.3.3.1 Following the conclusion of all installations and testing and

as a condition of Final System Acceptance, the Contractor

shall update and provide copies of all engineering and

design reports, “as-built” drawings, data, and other

material produced for the equipment installed and/or

procured as part of this contract and submit them to

MCTS.

8.3.3.2 The ABD shall include:

8.3.3.2.a • An inventory of all components supplied including

supplier, model number, serial number and

installation location;

8.3.3.2.b • An inventory of all spare parts supplied including

supplier, model number, serial number and

storage location;

8.3.3.2.c • All reference and user manuals for system

components, including those components

supplied by third parties;

8.3.3.2.d • All warranties documentation, including that for

components supplied by third parties;

8.3.3.2.e • A diagram indicating the as-built interconnections

between components; and

8.3.3.2.f • The version number of all software, including that

supplied by third parties.

8.3.3.3 MCTS shall retain exclusive and perpetual license to

reproduce and share ABD with third parties for the

purposes of integration and contracted work.

8.4 Installation

8.4.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.1.1 All equipment shall be new and unused, excluding pre-

existing MCTS equipment approved for reuse by MCTS.

Equipment procured for prototype and development

purposes may be reused in the final system with the

permission of MCTS.




June 19, 2020 106


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.1.2 The Contractor shall submit Installation Design

Documentation (IDD) for MCTS approval before

undertaking or making any modifications to MCTS

equipment or installations.

8.4.1.3 The IDD shall provide adequately detailed text, drawings,

illustrations, and images to allow a technician’s quality

installation without further training or installation

instructions from the vendors of the individual equipment

components.

8.4.1.4 The IDD shall include details on:

8.4.1.4.a • Equipment installation locations/mounting;

8.4.1.4.b • Routing, conductors, color-coding, labeling, and

connectors for power, communications, and

vehicle ground circuits;

8.4.1.4.c • Connections with, any required modifications to

and restoration of existing infrastructure;

8.4.1.4.d • Work area and equipment storage requirements;

8.4.1.4.e • Methods and quality standards; and

8.4.1.4.f • Supervision and quality assurance procedures.

8.4.1.5 The IDD shall include procedures for pre- and post-

installation checklists for tests that the installers shall

perform. The installations shall not be considered

complete unless MCTS signs off on the pre- and post-

installation checklist for each vehicle.

8.4.1.6 No adjustments, modifications, or substitutions to the IDD

shall be made by the Contractor during installation, except

with written approval by MCTS.

8.4.1.7 The Contractor shall install and configure the entire

system, including any MCTS provided computer hardware

and integration with existing systems.

8.4.1.8 The Contractor shall be responsible for locating all vehicle

equipment for each unique vehicle configuration, and

prepare all shop, installation, material fabrication, and

wiring drawings. A prototype installation for each type of

bus will be performed and approved by MCTS prior to

proceeding with installation of additional busses of the

same type.




June 19, 2020 107


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.1.9 A prototype installation for each sub-fleet of vehicle types

shall be performed by the Contractor. The prototype

installations shall be approved by MCTS before

proceeding with the installation of remaining buses.

Contractor shall document the approved installations by

creating photos or AutoCAD drawings of the equipment

locations and electrical wiring routing, and electrical

schematic of wiring installation in the IDD. The IDD shall

be submitted to and approved by MCTS prior to

production installation. All installations shall be consistent

and uniform with the prototype installations in quality,

equipment location, and wire routing.

8.4.1.10 For storage of all equipment prior to installation in MCTS

facilities and vehicles, the Contractor shall either:

8.4.1.10.a • Store equipment at the MCTS Administration

Building (which is a separate site from the vehicle

garages) and transport the equipment to the

MCTS-approved installation location(s); or

8.4.1.10.b • Provide suitable secure storage facilities (e.g.

portable storage containers) at the MCTS-

approved installation location(s).

8.4.1.11 The Contractor shall conduct a pre-installation inspection

for each installation site, documenting the existing

condition of any existing infrastructure that the installation

may affect. MCTS shall only authorize installations after

approving each pre-installation inspection.

8.4.1.12 The Contractor shall supply any electrical equipment

necessary to operate system components using existing

DC electrical power available on MCTS vehicles and

existing AC electrical power at fixed facilities. If existing

power arrangements are unsatisfactory, the Contractor

must specify proposed alterations.

8.4.1.13 The Contractor shall perform installations at specific times

during the day that MCTS approves. MCTS may require

the Contractor to perform installations over nights and

weekends and may require installations performed at the

vehicle’s home base.

8.4.1.14 Onboard installations shall take place at an MCTS garage,

as space and availability permit.

8.4.1.15 The Contractor shall perform installations in designated

spaces made available at MCTS facilities.

8.4.1.16 The Contractor is responsible for delivering all onboard

and central system material and components to the

installation site(s).




June 19, 2020 108


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.1.17 The Contractor shall provide all labor, materials,

integration and services to enable complete system

delivery.

8.4.1.18 The Contractor shall be responsible for the security of

equipment prior to installation.

8.4.1.19 The Contractor shall be responsible for removing existing

equipment, connectors, and cables before installing the

new equipment. Existing equipment shall be transferred to

an on-site storage location designated by MCTS. MCTS

shall be responsible for salvaging or disposing of all

removed equipment. All containers used to ship new

equipment will become the property of MCTS and may be

used to store or ship salvaged equipment.

8.4.1.20 A MCTS designated representative may be present during

the onsite installation to monitor quality control of the

installation process. The MCTS representative shall have

full authority to halt or suspend installation work if, in the

sole opinion of the MCTS representative, work is being

unsatisfactorily conducted.

8.4.1.21 Regular, clear, and consistent communication with MCTS

personnel during the installation process is of utmost

importance. Installers shall check in with designated

MCTS supervisors at the start of the workday and check

out to report the work progress at the end of the workday.

8.4.1.22 All Contractor, subcontractor, and/or supplier employees

shall comply with MCTS policies, procedures, and safety

regulations while on MCTS property.

8.4.1.23 Equipment shall be installed in a neat and professional

manner, in accordance with good practice, by competent

technicians or mechanics.

8.4.1.24 For each vehicle, following onboard system installation the

Contractor shall test the communications systems

between the bus and the OCC, including all forms of calls,

Emergency Alarms, and data message formats. Evidence

of successful transmission of all communications shall be

required for MCTS to approve the vehicle to enter

operation.

8.4.1.25 Equipment shall be properly grounded with onboard

equipment connected as directly as possible to the

chassis ground.

8.4.1.26 Equipment components shall be replaceable as discrete

units and identified by unique serial numbers. Each

connector shall be keyed or otherwise configured to

prevent inadvertent mis-wiring during equipment

replacement.




June 19, 2020 109


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.1.27 The Contractor shall protect equipment inputs and outputs

to absorb “routine” electrostatic discharges, over-voltages,

and reverse polarity conditions. In the event of

“extraordinary” conditions, the Contractor shall design

equipment to sacrifice inexpensive and easily identifiable

components when necessary to protect more expensive

components or those less easy to troubleshoot.

8.4.1.28 The Contractor shall house equipment in enclosures that

cannot be opened with standard hand tools and can resist

damage from vandalism.

8.4.1.29 All cables shall be fully labeled at both ends and uniformly

color coded or permanently marked in compliance with

established MCTS or industry standards where applicable.

Contractors shall provide a Cable Color/Labeling Plan as

part of the design documentation subject to approval by

MCTS.

8.4.1.30 Wire dress shall allow for enough slack at terminals to

provide for shock and vibration induced movements,

equipment lifting, alignment, cover removal and

component replacement.

8.4.1.31 All cables, wiring, inter-connectors, switches, circuit

breakers/fuses shall be designed for their purposes and

for transit onboard applications.

8.4.1.32 All wire sizes and insulations shall be based on the current

carrying capability, voltage drop, and mechanical strength,

temperature, and flexibility requirements. All

communication and signal wires and connectors shall be

selected to minimize signal loss.

8.4.1.33 All circuits shall be protected by fuses or circuit breakers.

The main power circuit from the vehicle to the system shall

be protected by a circuit breaker like what already exists in

the vehicle. All circuit breakers and fuses shall be

permanently labeled to show their functions.

8.4.1.34 Unless otherwise specified, the Contractor shall provide a

complete installation solution, including all labor, materials,

parts, interconnect cables and connectors. This includes

mounting brackets, stanchion extensions, hardware, cable

labels, grommets, cable clamps and harnesses, and other

materials required to install and make operational the

equipment.

8.4.1.35 The Contractor shall be responsible for all work and

expenses relating to the design, manufacture, and delivery

of the equipment at each location specified by MCTS.




June 19, 2020 110


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.1.36 The Contractor shall provide all necessary personnel,

tools, test equipment, transportation, hardware, and

supplies for the successful and complete installation of all

equipment and software.

8.4.1.37 The Contractor shall be responsible for their own and

subcontractors' performance and safety.

8.4.1.38 Installations shall be performed in accordance with all

Federal, State, and local laws and regulations.

8.4.1.39 System implementation shall not impact the performance

of existing infrastructure affected by or to be integrated

into the new system (e.g. MCTS’s LAN and WAN) at any

time.

8.4.1.40 After installations, the Contractor shall be responsible for

restoring the condition of any affected existing

infrastructure at the installation sites to their pre-

installation condition.

8.4.1.41 The Contractor shall remove all decommissioned

equipment, and properly dispose of all equipment not

eligible for resale or reuse. Decommissioned equipment

remains the property of MCTS.

8.4.1.42 Installation site and vehicles shall be left clean and free

from rubbish and debris. All material associated with site

preparation, unpacking of shipping materials, and/or

installation of new equipment related to this project shall

be removed from the premises by the Contractor and

properly disposed. All dumpsters, and related containers

for the use of proper disposal are the responsibility of the

Contractor. Removal of rubbish and debris shall be

performed daily.

8.4.1.43 Any damage to MCTS property or equipment due to the

mistake or negligence of the Contractor during installation

shall be corrected at the Contractor’s expense.

8.4.1.44 MCTS reserves the right to suspend installation upon

significant failures during testing.

8.4.2 Onboard Installation


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.2.1 Vehicles will be provided for installation throughout the

workday on a schedule to be provided by MCTS.




June 19, 2020 111


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.4.2.2 MCTS will permit a maximum of 4 vehicles to be out of

service for installation concurrently and reserves the right

to increase or decrease this allowable number due to

unrelated maintenance, operational needs, or other

contributing factors affecting vehicle availability.

8.4.2.3 The Contractor shall return all vehicles made available for

overnight installation work to MCTS staff for revenue

service by the start of the next service day (i.e. 4 a.m.).

8.4.2.4 All equipment shall be installed in a manner that allows for

simple component level replacement by MCTS

maintenance personnel in the event of failure.

8.4.2.5 Equipment shall allow for easy installation/ removal in

transit vehicles through the doors without requiring door

disassembly.

8.4.2.6 Onboard system devices shall be identical in installation

characteristics for each vehicle type and model.

8.4.2.7 Onboard equipment shall be designed so that swappable

components can be removed and replaced by a trained

technician in under 10 minutes per unit using only hand

tools.

8.4.2.8 Individual onboard components shall be carried by a

single person, and as such, shall not exceed 10lbs.

8.4.2.9 The Contractor shall be responsible for determining the

final location of MDT installation on each different vehicle

type and configuration, subject to approval from MCTS.

8.4.2.10 The Contractor shall securely mount onboard equipment

in the vehicle’s interior, clear of obstructions and

interference-generating devices. The Contractor shall

collaborate with MCTS staff to determine the installed

location of onboard components.

8.4.2.11 The Contractor shall provide system installation, and

integration assistance for the supervisor vehicles.

8.4.2.12 The Contractor shall provide a copy of the software, and

sufficient documentation and instructions for installing the

software such that MCTS staff can perform the installation

for the devices used by mobile supervisors in vehicles.




June 19, 2020 112

8.5 Training

8.5.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.5.1.1 The Contractor must complete all documentation and

training before MCTS will allow equipment installation.

8.5.1.2 The Contractor shall provide training courses for at least

the following user categories (for which MCTS will provide

the actual number of trainees in advance):

8.5.1.2.a • Management and supervisory staff;

8.5.1.2.b • Equipment installers/maintainers;

8.5.1.2.c • Trainers for vehicle operators;

8.5.1.2.d • Users of the fixed-route CAD/AVL software;

8.5.1.2.e • Users of any supplemental software provided;

8.5.1.2.f • Customer service staff; and

8.5.1.2.g • Data management and IT staff/systems

administrators.

8.5.1.3 The Contractor shall describe the necessary pre-requisite

computer skills and knowledge expected for each of the

training courses to develop training classes based on user

skill level.

8.5.1.4 The Contractor shall provide all training materials in

common electronic formats and storage media.

8.5.1.5 The training plan (TP), including the training schedule and

course outlines, must be provided to MCTS for review at

least three weeks in advance of the start of training. At

least the following topics must be included in the TP for

each training session:

8.5.1.5.a • Course objective;

8.5.1.5.b • Topics to be covered;

8.5.1.5.c • Required MCTS staff;

8.5.1.5.d • Time required for training;

8.5.1.5.e • Resources required from MCTS;

8.5.1.5.f • Follow-up need (in-person or webinar);

8.5.1.5.g • Prerequisites for trainees; and

8.5.1.5.h • Evaluation procedure for students.

8.5.1.6 The TP must be approved by MCTS before the start of

any training.




June 19, 2020 113


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.5.1.7 The Contractor shall furnish all special tools, equipment,

training aids, and any other materials required to train

course participants, for use during training courses only.

MCTS will provide a board room and projector that may be

used for training sessions.

8.5.1.8 The instructors shall demonstrate a thorough knowledge

of the material covered in the courses, familiarity with the

training materials used in the courses, and the ability to

effectively lead students in a classroom setting.

8.5.1.9 If any instructor is considered unsuitable by MCTS, either

before or during the training, the Contractor shall provide a

suitable replacement within five (5) business days of

receiving such notice from MCTS.

8.5.1.10 Following initial in-classroom training, the Contractor shall

provide over the shoulder training in the dispatch office

with dispatchers as they use the system in day to day

operations for a duration of 2 weeks.

8.5.1.11 The Contractor shall provide brief refresher versions of

each training course to the original trainees between three

to six (3-6) months after system acceptance for the system

at no additional cost.

8.5.1.12 The Contractor shall provide additional training to the

original trainees after system acceptance for the system at

no additional cost if major modifications are made to the

system after the initial training due to system upgrades or

changes made under warranty and/or system acceptance

occurs at least three (3) months after the completion of

training, due to delays for which the Contractor is

responsible.

8.5.1.13 The training course for management and supervisory staff

shall provide an overview of the system and project,

including but not limited to:

8.5.1.13.a • A physical and operational overview of the

system;

8.5.1.13.b • Identification of major system, subsystems and

components;

8.5.1.13.c • Description of system capabilities and limitations;

and

8.5.1.13.d • Summary of roles and responsibilities for MCTS

Operations, Maintenance, Schedule, and IT

departments.

8.5.1.14 The training course for operators shall provide instruction

on, at minimum:




June 19, 2020 114


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.5.1.14.a • Onboard system operations and relevant

dispatcher capabilities (e.g. in response to

operator actions);

8.5.1.14.b • Step-by-step descriptions of any required operator

interaction; and

8.5.1.14.c • Common problems and procedures for reporting

system faults.

8.5.1.15 The training course for data management and IT staff shall

provide instruction on, at minimum:

8.5.1.15.a • Data management;

8.5.1.15.b • Configuration data management;

8.5.1.15.c • Data transfer functions and procedures;

8.5.1.15.d • System backup and recovery functions and

procedures;

8.5.1.15.e • Off-line operations;

8.5.1.15.f • System interfaces;

8.5.1.15.g • Troubleshooting and help procedures;

8.5.1.15.h • Log management; and

8.5.1.15.i • Report development, including data dictionaries

required to prepare ad-hoc and custom reports.

8.5.2 Training Manuals


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.5.2.1 All manuals shall make extensive and appropriate use of

diagrams and graphics as determined by MCTS, to aid in

user comprehension and repeated reference.

8.5.2.2 The Contractor shall provide maintenance manuals (MM)

documenting:

8.5.2.2.a • The concept of operations of all components;

8.5.2.2.b • How the system components were installed;

8.5.2.2.c • A list of corresponding spare components;

8.5.2.2.d • How to install and configure spare components;

and




June 19, 2020 115


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.5.2.2.e • The schedule/procedures for preventative

maintenance, inspection, fault diagnosis,

component replacement and warranty

administration on each system component.

8.5.2.3 The Contractor shall provide user manuals (UMs) for the

fixed-route dispatchers, documenting use of all software

functions.

8.5.2.4 The Contractor shall provide vehicle operator manuals

(OMs) documenting use of the MDTs and on-board

equipment. In addition, drivers shall be provided short form

manual (1-2 pages) as quick reference guide during daily

operations.

8.5.2.5 The Contractor shall provide a Systems Manual (SM),

documenting:

8.5.2.5.a • The configuration and topology of all system

hardware and software;

8.5.2.5.b • Central systems software functions and

operations;

8.5.2.5.c • Start up and shut down procedures;

8.5.2.5.d • Backup and recovery procedures;

8.5.2.5.e • System diagnostics and performance analysis

procedures;

8.5.2.5.f • Report production capabilities and procedures;

8.5.2.5.g • Scheduled maintenance required for all system

components;

8.5.2.5.h • Datastore structure and documentation and data

dictionary for all databases;

8.5.2.5.i • Disaster recovery capabilities, highlighting how the

system can function and prevent any data loss in

the case of a natural disaster or other unexpected

events; and

8.5.2.5.j • A full glossary of descriptions and context for any

abbreviated data points provided by the Contractor

within the system.

8.5.2.6 The Contractor shall provide a Reporting Manual (RM) to

include graphical depictions and a written description of all

functions required for developing all types of standard and

custom reports.




June 19, 2020 116

8.6 Testing and Acceptance

8.6.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.1.1 The Contractor shall submit an Acceptance Test

Procedures document (ATP), for MCTS’s approval at least

three (3) weeks before undertaking any testing.

8.6.1.2 The Contractor shall submit a notice of readiness to MCTS

for approval, indicating that all dry run testing has been

completed satisfactorily at least one (1) week before

undertaking formal testing.

8.6.1.3 The ATP shall clearly address:

8.6.1.3.a • How each testable specification requirement will

be demonstrated, including the method for

performing the test;

8.6.1.3.b • A list of supporting equipment required;

8.6.1.3.c • The results that will constitute success for each

test;

8.6.1.3.d • Entry and exit criteria;

8.6.1.3.e • Responsibilities of both Contractor and MCTS’s

representatives during each test; and

8.6.1.3.f • Which contract requirements from the

Requirements Matrix each test addresses and

how it addresses them.

8.6.1.4 MCTS reserves the right at no additional costs to make

the following changes to the Test Plans and/or Procedures

including during test stages:

8.6.1.4.a • Procedural changes, adjustments, or reasonable

additions to enforce or confirm conformance with

requirements; and

8.6.1.4.b • Explanations from Contractor staff as necessary

to clarify the purpose, specific methods, functions,

and/or results of tests.

8.6.1.5 The ATP shall include an update to extend the RM from

the Design Review Document (DRD). These procedures

shall include the test stage at which each contract

requirement will be demonstrated and a cross-reference to

the test procedure(s) that serve to address each contract

requirement.

8.6.1.6 The ATP shall incorporate the following distinct testing

stages for the proposed system:




June 19, 2020 117


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.1.6.a • Factory Testing (FT);

8.6.1.6.b • Mini-Fleet Test (MFT);

8.6.1.6.c • System Testing (ST); and

8.6.1.6.d • Burn-in/Rigorous Testing (BT).

8.6.1.7 The Contractor shall demonstrate each contract

requirement during the distinct test stages unless

otherwise waived by MCTS or MCTS’s representatives.

8.6.1.8 MCTS may authorize the Contractor to proceed to the next

testing stage with certain deficiencies not yet resolved.

8.6.1.9 The Contractor shall provide written notice to MCTS at

least two weeks in advance of any testing, indicating the

specific tests to be completed as well as the date, time,

and location.

8.6.1.10 Testing shall be witnessed by MCTS or MCTS's

representatives.

8.6.1.11 The Contractor shall be required to reschedule testing if

MCTS’s witnessing representatives cannot be present or if

other circumstances prevent testing from taking place.

8.6.1.12 The Contractor shall provide written Test Results

Documentation (TRD) after completing each stage of

testing.

8.6.1.13 The TRD shall include for each item:

8.6.1.13.a • Detailed equipment information including type,

model number, and serial number of each

component tested;

8.6.1.13.b • Detailed description of test environment;

8.6.1.13.c • Test results recorded on approved test report

forms. For commercial off-the-shelf products, this

includes stamped quality testing documents from

before it leaves the factory environment;

8.6.1.13.d • The Requirements Traceability Matrix listing

linking each requirement proposed to be

demonstrated in the test to applicable test results;

8.6.1.13.e • Any additional submittals required by the

equipment Item specification; and

8.6.1.13.f • Documentation of all system equipment and

configuration changes required to meet system

requirements following test failures.

8.6.1.14 MCTS must approve the TRD before granting Acceptance

of the test stage.




June 19, 2020 118


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.1.15 The Contractor shall use the RM as a “punch list” to track

which requirements have not yet been fully demonstrated

at each stage of testing.

8.6.1.16 MCTS can subsequently redefine a requirement that was

classified as “fully demonstrated” during a certain

acceptance testing stage as “not demonstrated” if

compliance issues emerge before Final System

Acceptance.

8.6.2 Factory Testing


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.2.1 FT shall be performed to confirm that the supplied and

developed components meet all functional and

environmental requirements and specifications. FT shall

be performed at the Contractor’s manufacturing or

development site prior to any delivery of equipment to

MCTS. At a minimum the Contractor Project Manager and

Engineers shall be present during the FT.

8.6.2.2 The Contractor shall develop a comprehensive FT

program consisting, at a minimum, of the following

individual test programs:

8.6.2.2.a • Hardware test to verify the operating parameters

of all equipment are per the requirements of this

Contract, OEM specifications, and System Design

Document;

8.6.2.2.b • Functional test to demonstrate that all functional

and operational requirements and specifications

applicable to the device/subsystem have been

delivered;

8.6.2.2.c • Submit documents supporting appropriate

certifications showing environmental and electrical

compliance;

8.6.2.2.d • Human factors test for all devices/subsystems

with a user interface; and

8.6.2.2.e • Scenario or use-case testing to demonstrate end-

to-end connectivity and correct

processing/handling of data.




June 19, 2020 119


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.2.3 All equipment types shall be tested. A minimum of two (2)

units of each equipment type, identically configured to all

other units of that same equipment type, shall be subject

to FT unless waived by the MCTS Project Manager.

8.6.2.4 Any device certifications required by regulatory agencies

shall be the responsibility of the Contractor.

8.6.2.5 All required certifications shall be submitted with each

shipment of devices or subsystems.

8.6.2.6 Any changes to the hardware or hardware configuration

shall require a FT retest.

8.6.3 Mini-Fleet Testing


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.3.1 MFT shall be performed to demonstrate that the supplied

and developed components meet all functional and

environmental requirements and specifications in onsite

use on a limited fleet of MCTS vehicles and utilizing

MCTS's central system software. The fleetwide installation

of equipment shall not commence until successful

completion of MFT.

8.6.3.2 The Contractor shall complete MFT for at least one (1)

type of each vehicle in MCTS’s fleet for any on-board

system. The Contractor shall rectify any deficiencies

observed in a four-week (4) period following MFT before

initiating ST. (i.e. The vehicles used during MFT will be in

operation for four (4) weeks to observe issues that arise in

daily operations).

8.6.3.3 Before the commencement of MFT, the Contractor shall

validate all routes in the MCTS system to confirm that the

geographic parameters relevant to the system operation

(e.g., stop locations, route traces, and trigger zones) have

been accurately configured in the system database.




June 19, 2020 120

8.6.4 System Testing


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.4.1 ST can be initiated only once all of the system elements

have been installed and configured and all pre-installation

and installation Quality Assurance and Quality Control

(QA/QC) have been completed successfully. In addition,

all deficiencies from MFT must be rectified before ST. The

ST looks at the entire system, and tests are completed to

demonstrate that the overall functional requirements are

met. The ST is typically done from the central software out

to each device and is also known as an end-to-end test.

Where the software interfaces with other software, this

interface shall be tested through the ST for each piece of

software.

8.6.4.2 Each requirement listed in the specification shall be

tested. In case it may not be feasible to test certain

functions in the operational environment, evidence for

correct function is to be provided.

8.6.4.3 ST shall be witnessed by MCTS representatives (MCTS

staff and/or designated support consultants).

8.6.4.4 The Contractor shall complete ST after the entire system

has been installed and shall rectify any deficiencies before

initiating burn-in/rigorous testing.

8.6.5 Burn-in Testing


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

8.6.5.1 BT shall involve revenue service use of the system over a

30-day period after system testing is completed. Through

BT, the system is tested under full operations with full

scale deployment to demonstrate that the performance

requirements are met, and to measure the system

performance metrics, including reliability and availability.

8.6.5.2 System failures will be rated as significant, moderate, or

minor by MCTS based on operational impact. Significant

system failures will result in restart of BT. Minor failures

will result in suspension of the 30-day BT clock until

resolved. Moderate failures may result in suspension and

partial rollback of the 30-day BT clock as per MCTS’s

unilateral judgement (i.e. if the clock is suspended on day

15 for a moderate failure, MCTS may decide to set the

clock back to day 7).




June 19, 2020 121

8.6.5.3 The classification of a failure shall be the Contractor’s

responsibility and accompanied by a justification. MCTS

will not be required to accept the Contractor’s

classification, and may, at its own discretion, modify the

classification. In such cases, MCTS will provide a

justification for not accepting the Contractor’s

recommendation.

8.6.5.4 MCTS will not grant Final System Acceptance until the

Contractor has rectified any outstanding deficiencies and

formally met all contract requirements through BT.




June 19, 2020 122

9 System Warranty and Support

9.1 General


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.1.1 The Contractor shall prepare a Support Plan, including the

support hours availability, communication approach,

method of tracking tickets and software-related incidents,

support team, and severity classifications and response

times. The Support Plan shall be in conformance with all

finalized SLAs under this project (see section 9.7).

9.1.2 For on-site support, the Support Plan shall include a list of

the support firms, their support responsibilities, and the

response arrangements.

9.1.3 The Support Plan must be approved by MCTS as a

condition of Final System Acceptance and before the

initiation of the warranty period.

9.2 System Warranty Coverage


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.2.1 The base warranty period for the system, during which the

Contractor shall provide ongoing technical and

maintenance support, shall be through to two (2) years

from the date of Final System Acceptance.

9.2.2 The Contractor shall offer separate and distinct options to

extend the system’s warranty period in eight (8) one-year

increments, beginning from the conclusion of the base

warranty period, and concluding ten (10) years after the

date of Final System Acceptance. The Contractor shall

document any differences in the warranty terms for these

option years in their proposal.

9.2.3 The Contractor shall warrant that it has good title to the

system and its components and the right to sell to MCTS,

free of any proprietary rights of any manufacturer (if the

Contractor is not the manufacturer) or other party, and

free of any lien or encumbrance.

9.2.4 The Contractor shall warrant that it has good title to all

system software or that it has the right to license the use

of such software, or both, free of any proprietary rights of

any other party and free of any other lien or encumbrance.




June 19, 2020 123


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.2.5 The Contractor shall warrant that MCTS shall acquire

permanent title to all equipment and non-proprietary

software provided under the Contract, free and clear of all

liens and encumbrances.

9.2.6 The Contractor shall warrant that all installation work and

all system hardware furnished by the Contractor, including

but not limited to all such work and system hardware

provided by Contractors or other suppliers or

manufacturers, shall:

9.2.6.a • Be fit for their intended purpose as a component

of the overall transit management system in the

MCTS environment in conformity with this

Contract; and

9.2.6.b • Be new and shall be of good quality and free of

any defects or faulty materials and workmanship

for the warranty period.

9.2.7 The Contractor shall warrant that the documentation

provided shall completely and accurately reflect the

equipment and software’s operation and maintenance and

provide MCTS with all information necessary to maintain

the system.

9.2.8 If there is a change in the production configuration of any

equipment or software being installed before Final System

Acceptance, MCTS reserves the right to require that all

previously installed equipment and software be upgraded

to match the updated configuration at no additional cost.

9.2.9 The Contractor shall warrant compliance with all

applicable laws and regulations relating to the project.

9.2.10 The Contractor shall warrant that its employees, agents,

and subcontractors assigned to perform services under

this contract shall have the required skill, training, and

background to perform in a competent and professional

manner and that all work will be so performed. MCTS

reserves the right to remove any subcontractors if their

work is deemed incompetent or unprofessional.

9.2.11 During the warranty period, the Contractor shall at no cost

to MCTS furnish such materials, labor, equipment,

software, documentation, services and incidentals as are

necessary to maintain the system in accordance with the

warranty.




June 19, 2020 124


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.2.12 It is recognized that the original manufacturer or supplier

warranties may expire before the end of the warranty

period. The Contractor shall therefore provide extended

warranties for all such products or equipment (software,

hardware, spare parts) and must assume full responsibility

for replacement or repair for the duration of the warranty

period, the full cost of which must be included in the

contract price.

9.2.13 In addition to the foregoing warranties, the Contractor

shall assign to MCTS, and MCTS shall have the benefit of,

any and all subcontractors', Suppliers', and Vendors'

warranties and representations with respect to the

deliverables provided.

9.2.14 In its agreements with subcontractors, Suppliers, and

Vendors, the Contractor shall require that such parties:

9.2.14.a • Consent to the assignment of such warranties and

representations to MCTS;

9.2.14.b • Agree that such warranties and representations

shall be enforceable by MCTS in its own name;

and

9.2.14.c • Furnish documentation on the applicable

warranties to MCTS.

9.2.15 The Contractor shall provide a single point of contact for

all warranty administration during the warranty period.

9.2.16 Any patches, updates, and version upgrades by hardware

or software Contractors, (including operating systems),

shall not void CAD/AVL Contractor warranty.

9.3 Repair or Replacement of Faulty Components


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.3.1 All onboard equipment and outdoor equipment shall have

a minimum 20,000 hours mean time between failures

(MTBF) on average across the fleet, measured quarterly

from mini fleet acceptance.

9.3.2 During the warranty period, the Contractor shall repair or

replace any faulty components, with the cost included in

the warranty price.




June 19, 2020 125


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.3.3 For each system component or workmanship failure

during the warranty period, MCTS shall determine whether

to correct the failure by repair or replacement of part(s)

within an assembly, or by replacement of the entire

assembly.

9.3.4 MCTS shall perform removal of failed parts or assemblies

and installation of spare parts or assemblies for accepted

system elements under warranty with no impact on the

warranty validity, unless MCTS and the Contractor agree

to other arrangements for such work. The Contractor may

provide technical supervision for such removal or

installation work by MCTS.

9.3.5 The Contractor shall receive removed failed parts or

assemblies at a location on MCTS premises to be

designated, unless the Contractor requests shipment of

such failed parts or assemblies to its facilities; in such

case, MCTS will ship such failed parts or assemblies at

the Contractor's expense.

9.3.6 The Contractor shall deliver to MCTS a replacement or

repaired part or assembly for each such returned failed

part or assembly within five (5) business days of the

Contractor's receipt of each failed part or assembly.

9.3.7 If the Contractor determines through comprehensive

testing that a returned component is not faulty, MCTS

shall receive the original component back in working order

within two days of the Contractor originally receiving the

returned component.

9.3.8 Repaired, replaced, or returned components shall be

packaged, organized and labeled in the same manner as

the original supply of spare components.

9.3.9 All components received back at MCTS from the

Contractor will be tested in accordance with the original

ATP and shall be returned to the Contractor if faulty

accompanied by a certification.

9.3.10 In the event that a failed onboard part or assembly is

manufactured to order only and cannot be repaired or

replaced within the five (5) business day period, the

Contractor and MCTS mutually shall consider whether the

defective unit is to be repaired or replaced. The decision

as to which alternative will be used shall be based on

minimizing down time of the system, and the Contractor

shall return the repaired or replaced unit at the earliest

possible date.




June 19, 2020 126


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.3.11 The Contractor shall provide during the warranty period

the latest compatible version of the failed part/hardware

with the latest firmware and software as applicable.

9.3.12 The Contractor shall retain full responsibility for replaced

or repaired parts or assemblies throughout the duration of

the warranty coverage period for all parts and assemblies

replaced by MCTS.

9.3.13 Any materials, parts or components used for replacement

under the initial warranty period shall be warranted again,

such that the new warranty period shall begin upon date of

replacement as recorded in MCTS’s system maintenance

records, and shall be of the same duration as the original

warranty period regardless of the timeframe of the failure.

In the case of components that are replaced pursuant to a

modification program but have not yet failed, the new

warranty period shall be computed from the date of MCTS

notification to the Contractor of a requirement for the

particular modification program.

9.4 Systemic Failures


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.4.1 Systemic failures shall be defined as the occurrence of

specific component failures in excess of 5% during the

warranty period.

9.4.2 In the event of systemic failures during the warranty

period, the Contractor shall at their expense, within 30

days of notification of such instance, commence a

modification program to repair or replace all such

components, including those that have passed beyond the

warranty period, to correct the cause(s) of such failures.

The design of the repair or replacement for the

component(s) involved in each such modification program

shall be developed by the Contractor to remedy the nature

and probable cause of the component failures and shall be

approved by MCTS.

9.4.3 Repair and/or replacement of components pursuant to a

modification program shall be according to the same

provisions herein as if such components were failed

components requiring warranty repair and/or replacement,

whether or not actual failures for some or most of the

involved components have occurred following notification

of a requirement for a modification program.




June 19, 2020 127


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.4.4 Even if the systemic failure replacement activity extends

beyond the end of the two (2) -year warranty period, the

Contractor shall be obligated to complete it if the need was

documented before the end of the warranty period.

9.4.5 The Contractor shall warrant replacement of parts or

assemblies due to systemic failures for two (2) years from

replacement. Warranty terms and conditions shall be the

same as for the original system warranty.

9.5 Spare Components


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.5.1 The Contractor shall provide spare parts, documented in a

Spare Parts List. This list shall include replacement parts,

components or sub-assemblies for all items of equipment

provided, and their quantities, in sufficient number to meet

the estimated need for warranty and maintenance

purposes for a period of two years. This shall include a

minimum of 10% of the installed quantity for each

component (with a minimum quantity of 1). The Spare

Parts List shall include complete sets of all necessary

replacement parts.

9.5.2 The Spare Parts List shall contain a set of all specialized

tools and equipment necessary to install, calibrate, test

and maintain the system. All wiring, cabling and adapters

shall also be provided. Each item on the spare parts list

shall include all ancillary components (e.g., cables,

hardware) needed to complete a rapid onboard

replacement for the component.

9.5.3 The Contractor shall provide spare parts in accordance

with the agreed Spare Parts List, the full cost of which

shall be included in the Contract Price.

9.5.4 The Spare Parts shall be placed into the spare parts

inventory and become the property of MCTS upon

handover.

9.5.5 MCTS shall receive replacement spares within 7 calendar

days of notice of shipment of the defective part to the

Contractor.

9.5.6 MCTS shall have the option to purchase additional spare

components at the proposed price at any time within the

warranty period. Additional purchased spares shall be

received within 7 calendar days of order.




June 19, 2020 128

9.6 Software Updates


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.6.1 All software and software updates provided by the

Contractor shall be covered by the Warranty.

9.6.2 The Contractor shall supply compatible software versions

across the fleet over the term of this contract including the

warranty.

9.6.3 During the warranty period, the Contractor shall update all

applicable software with the then-current software version

at no additional cost to MCTS.

9.6.4 The Contractor shall be required to notify MCTS at least

two (2) weeks in advance of the installation when new

software releases become available.

9.6.5 The Contractor shall be required to notify MCTS at least

twelve (12) months in advance when it is expected that the

current releases and related systems will no longer be

supported.

9.6.6 The Contractor shall coordinate and request MCTS

approval for the implementation of any maintenance

activities, including patches or software upgrade.

9.6.7 Any “patches” recommended by the hardware or software

Contractors, (including operating systems), shall not void

the system warranty.

9.6.8 The Contractor shall conduct all software maintenance

activities as per a defined protocol approved by MCTS.

The protocol shall be documented in the Maintenance and

Operations Support Plan and shall indicate:

9.6.8.a • Communications before, during, and upon

completion of planned activities;

9.6.8.b • Template of communications prior to planned

activity, including:

o Expected timing of start and completion of

activity (including expected downtime);

o Anticipated impact(s) of activity on system

and ongoing operations; and




June 19, 2020 129


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.6.8.c • Template of communications during or after

planned activity, including:

o Mitigation plan and associated updates, (if

applicable in case of unsuccessful

completion of activity);

o Notice of successful completion of activity,

(in case of successful completion of

activity).

9.6.9 MCTS shall be notified at least 48 hours prior to any

scheduled system downtime (or alternative time period per

approved maintenance protocol) required for any software

maintenance activities, with MCTS approval required to

proceed with the planned activities.

9.6.10 The Contractor shall ensure that all existing and previous

software configurations are protected (through

configuration backups or data archives) after the system

has been upgraded or updated for the entire duration of

the time when MCTS uses the product.

9.7 Technical Support and Service Level Agreements


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.7.1 The Contractor shall provide, license, install, and integrate

all released software patches and updates for the

proposed solution and provide technical support during the

warranty period, including technical support for all

proposed hardware and software and a support line

available 24 hours a day, 365 days a year.

9.7.2 The Contractor shall, in collaboration with MCTS, enable

the ability for the Contractor to access the central software

remotely, using a VPN connection approved by MCTS (or

an approved alternate secured remote access method).

9.7.3 All system components shall be supported under a

Service Level Agreement (SLA).

9.7.4 The Contractor shall present a proposed SLA for MCTS

consideration. The final SLA shall be negotiated between

MCTS and the Contractor based on MCTS needs. The

proposed SLA shall describe the following:




June 19, 2020 130


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.7.4.a • Description and scope of service provided, clearly

defining:

o Coverage;

o Restrictions;

o Exclusions; and

9.7.4.b • System monitoring services provided by the

Contractor (e.g. monitored parameters, automatic

or manual monitoring, system security services);

9.7.4.c • Service standards, including:

o Service request categories and priority

levels;

o Average and maximum service request

response times for on-site and remote

requests at each priority level;

o Response protocols such as channels

and documentation; and

9.7.4.d • Expected MCTS responsibilities.

9.7.5 The Contractor shall arrange for support from one or more

qualified firms to be available on-site according to the

terms of the SLA when MCTS needs help with fault

diagnosis or component replacement.

9.7.6 If a support firm does not respond within the terms defined

by the SLA, or when a support firm is not able to provide

the needed support, the Contractor shall provide during

the warranty period supplementary support in accordance

with an agreed escalation procedure. The escalation

procedure can initially involve telephone support but must

culminate in the Contractor providing on-site support, if

needed. The Support Plan must define the proposed

support escalation procedures.

9.7.7 The Contractor shall provide an online issue reporting and

tracking system for MCTS users to input support requests.

MCTS must be able to view the status of all support

request(s) at any time through the online tracking system.

9.7.8 The Contractor shall provide a reliable method for

telephone problem notification. Maintenance issues should

be resolved in a timely manner, as agreed to per the

MCTS-approved maintenance plans.




June 19, 2020 131


(F-CM-N)

PROPOSED

REQUIREMENT

(FOR CM ONLY)

9.7.9 The Contractor shall designate a specific Technical

Support contact person (e.g., an account manager) to

handle all MCTS reported issues. This contact person

should be the first point of contact for the MCTS to report

all new issues and to follow up on previously reported

issues and shall be available during normal MCTS service

operating hours.

9.7.10 The Contractor shall notify MCTS of the availability of

enhancements, releases, and newer versions of the

software (including third party software), including all bug

fixes, patches, and modifications, or any modifications to

the hosting system. The Contractor shall conduct all

testing to confirm the enhancements or upgrades do not

impact the system, and shall consult with the MCTS

concerning the advisability of incorporating such

enhancements and newer versions and shall provide

supporting materials.

9.7.11 The Contractor shall only implement the enhancements or

hosting upgrades upon MCTS’s approval. On MCTS's

request, significant enhancements, new releases, or new

versions shall first be implemented on the test server, and

then on the production server once MCTS staff have

tested the updated version on the test server (if option

exercised). This testing will be in addition to testing the

Contractor will conduct. Following installation of the

enhancement, new release, or new version on the

production system, the Contractor shall be responsible for

ensuring system availability.




June 19, 2020 132

Appendix A: Glossary

ABD – As-built Documentation

ABS – Anti-lock Brake System

ADA – Americans with Disabilities Act

AGC – Automatic Gain Control

AIL – Action Item List

API – Application Programming Interface

APN – Access Point Name

ATP – Acceptance Test Plan

AVA – Automated Vehicle Announcements

AVL – Automatic Vehicle Location

BEB – Battery-Electric Bus

BI – Business Intelligence

BT – Burn-in Testing

CAD/AVL – Computer Aided Dispatch/Automated

Vehicle Location

CAN – Controller Area Network

CCTV – Closed-circuit Television

CDR – Critical Design Review

CFR – Code of Federal Regulations

CSV – Comma-separated Value

C2C – Center-to-Center (TSP)

DAQ – Delivered Audio Quality

DMS – Dynamic Message Sign

DRD – Design Review Document

DMVPN – Dynamic Multipoint Virtual Private

Network

DVR – Digital Video Recorder

EMI – Electromagnetic Interference

FCC – Federal Communications Commission

FDD – Final Design Document

FT – Factory Testing

FTA – Federal Transit Administration

GIS – Geographic Information System

GPS – Global Positioning System

GTFS – General Transit Feed Specification

GUI – Graphical User Interface

HTTPS – Hypertext Transport Protocol Secure

HVAC – Heating, Ventilation, and Air Conditioning

ICA – Independent Computing Architecture

ICD – Interface Control Document

IDD – Installation Design Document

IEC – International Electrotechnical Commission

IEEE – Institute of Electrical and Electronics

Engineers

IP – Ingress Protection (must be followed by a two-

digit number)

IP – Internet Protocol

ISO/IEC – International Organization for

Standardization and the International

Electrotechnical Commission

IT – Information Technology

ITS – Intelligent Transportation Systems

JRE – Java Run-time Environment

KPI – Key Performance Indicator

LAN – Local Area Network

LCD – Liquid Crystal Display

MCTS – Milwaukee County Transit System

MDT – Mobile Data Terminal

MFT – Mini-Fleet Testing

MM – Maintenance Manual

MTBF – Mean Time between Failures

NEMA – National Electrical Manufacturer’s

Association

NIST – National Institute of Standards and

Technology

NTD – National Transit Database

NTP – Notice to Proceed

OCC – Operations Control Center

ODBC – Open Database Connectivity




June 19, 2020 133

OEM – Original Equipment Manufacturer

OM – Operator Manual

PA – Public Announcement

PDD – Preliminary Design Document

PDF – Portable Data Format

PDR – Preliminary Design Review

PRTT – Priority Request to Talk

PTT – Push-to-Talk

QoS – Quality of Service

RDP – Remote Desktop Protocol

RFI – Radio Frequency Interference

RFID – Radio Frequency Identification

RM – Requirements Matrix

RR – Requirements Review

RSRP – Reference Signals Received Power

RSRQ – Reference Signal Received Quality

RSSI – Received Signal Strength Indicator

RTT – Request to Talk

SA – System Administrator

SAE – Society of Automobile Engineers

SIP – System Implementation Plan

SM – System Manual

ST – System Testing

SQL – Structured Query Language

TCP/IP – Transmission Control Protocol/Internet

Protocol

TP – Training Plan

TRD – Test Results Documentation

TSP – Transit Signal Priority

TTS – Text-to-Speech

UM – User Manual

VAC – Volts Alternating Current

VAN – Vehicle Area Network

VDC – Volts Direct Current

VHM – Vehicle Health Monitoring

VLAN – Virtual Local Ara Network

VLU – Vehicle Logic Unit

VM – Virtual Machine

VPN – Virtual Private Network

WAAS – Wide Area Augmentation System

WAN – Wide Area Network

WLAN – Wireless Local Area Network

XML – Extensible Markup Language




June 19, 2020 134

Appendix B: Fleet Inventory

Table B-1: Revenue Bus Fleet (May 29, 2020)

BUS NUMBERS

QUANTITY ACTIVE MAKE & MODEL YEAR

5100-5189 90 All NEW FLYER D40LFR 2010

5200-5234 34 All except 5219 NEW FLYER D40LFR 2011

5300-5354 54 All except 5334 NEW FLYER D40LFR 2012

5400-5454 55 All NEW FLYER XD40 2013

5500-5534 35 All NEW FLYER XD40 2014

5600-5627 28 All NEW FLYER XD40 2015

5700-5729 30 All NEW FLYER XD40 2016

5800-5814 15 All NEW FLYER XD40 2015

5900-5927 28 All GILLIG BRT 2019

6000-6023 24 Rolling out GILLIG BRT 2020

TBD Between 4 and 15

Not yet ? (ELECTRIC PROPULSION) 2021




June 19, 2020 135

Table B-2: Non-Revenue Vehicle Fleet Supported by Current CAD/AVL (May 29, 2020)

NUMBER MAKE & MODEL YEAR USE LOCATION

103 DODGE CARAVAN 2017 TRANSPORTATION KK

104 DODGE CARAVAN 2017 TRANSPORTATION FD

160 CHEVROLET EQUINOX 2019 ROUTE SUPERVISOR FM












172 CHEVROLET EQUINOX 2019 TREASURY FM

202 FORD TRANSIT VAN 2016 FARE BOX MAINTENANCE FM

203 FORD F-350 2016 B&G SIGN TRUCK FM

210 GMC SAVANA 3500 1998 RADIO TECH FM

212 GMC SAVANA 3500 1998 RADIO TECH FM

218 FORD TRANSIT 350 2018 B&G SHELTER REPAIR FM

219 FORD TRANSIT 350 2018 B&G ELECTRICIAN VAN FM

220 FORD TRANSIT 350 2018 B&G SHELTER WASH FM

250 N/A N/A ALLIED BARTON 1 (SECURITY) N/A





301 STERLING 2004 CASHIERS AD

303 STERLING 2001 SERVICE FD

305 FORD F550 2016 MAINTENANCE FD

FEDERAL CLAUSES

** updated 01/2020

SPECIAL NOTIFICATION REQUIREMENTS FOR STATES

FTA Master Agreement

Federal grant monies fund this contract, in whole or in part. As such, agencies receiving such funds and contractors awarded contracts that use such funds must comply with certain Federal certifications and clause requirements. This includes, for purchases of rolling stock over $150,000, compliance with Buy America Act requirements, including pre-award and post-delivery audit requirements and certifications, as well as requirements and certifications applicable under the Federal Motor Vehicle Safety Standard (FMVSS). It is the contractor’s responsibility to be aware of the pertinent certifications and contract clauses, as identified by the Issuing Agency for the instant procurement and ensure compliance with such requirements prior to award and throughout the term of any resultant contract. The full text of these clauses is available at the National Rural Transit Assistance Program (RTAP) website under

“ProcurementPro.” The website address is: http://www.nationalrtap.org/ .

FLY AMERICA REQUIREMENTS

49 U.S.C. §40118 41 CFR Part 301-10

Applicability to Contracts

The Fly America requirements apply to the transportation of persons or property, by air, between a place in the U.S. and a place outside the U.S., or between places outside the U.S., when the FTA will participate in the costs of such air transportation. Transportation on a foreign air carrier is permissible when provided by a foreign air carrier under a code share agreement when the ticket identifies the U.S. air carrier's designator code and flight number. Transportation by a foreign air carrier is also permissible if there is a bilateral or multilateral air transportation agreement to which the U.S. Government and a foreign government are parties and which the Federal DOT has determined meets the requirements of the Fly America Act.

Applicability to Micro-Purchases: Micro-purchases are defined as those purchases under 10,000. These requirements do not apply to micro-purchases; except for construction contracts over $2,000. Flow Down Requirements: The Fly America requirements flow down from FTA recipients and subrecipients to first tier contractors, who are responsible for ensuring that lower tier contractors and subcontractors are in compliance. Model Clause/Language: The relevant statutes and regulations do not mandate any specified clause or language. FTA proposes the following language. Fly America Requirements - The Contractor agrees to comply with 49 U.S.C. 40118 (the "Fly America" Act) in accordance with the General Services Administration's regulations at 41 CFR Part 301-10, which provide that recipients and subrecipients of Federal funds and their contractors are required to use U.S. Flag air carriers for U.S Government-financed international air travel and transportation of their personal effects or property, to the extent such service is available, unless travel by foreign air carrier is a matter of necessity, as defined by the Fly America Act. The Contractor shall submit, if a foreign air carrier was used, an appropriate certification or memorandum adequately explaining why service by a U.S. flag air carrier was not available or why it was necessary to use a foreign air carrier and shall, in any event, provide a certificate of compliance with the Fly America requirements. The Contractor agrees to include the requirements of this section in all subcontracts that may involve international air transportation.

http://www.nationalrtap.org/home.aspx

BUY AMERICA REQUIREMENTS

49 U.S.C. 5323(j) 49 CFR Part 661

Applicability to Contracts The Buy America requirements apply to the following types of contracts: Construction Contracts and Acquisition of Goods or Rolling Stock (valued at more than $150,000).

Flow Down Requirements: The Buy America requirements flow down from FTA recipients and subrecipients to first tier contractors, who are responsible for ensuring that lower tier contractors and subcontractors are in compliance. The $150,000 threshold applies only to the grantee contract, subcontracts under that amount are subject to Buy America.

Mandatory Clause/Language: The Buy America regulation, at 49 CFR 661.13, requires notification of the Buy America requirements in FTA-funded contracts, but does not specify the language to be used. The following language has been developed by FTA.

Buy America - The contractor agrees to comply with 49 U.S.C. 5323(j) and 49 C.F.R. Part 661, which provide that Federal funds may not be obligated unless steel, iron, and manufactured products used in FTA-funded projects are produced in the United States, unless a waiver has been granted by FTA or the product is subject to a general waiver. General waivers are listed in 49 CFR 661.7, and include software, microcomputer equipment and small purchases (currently less than $150,000) made with capital, operating, or planning funds. Separate requirements for rolling stock are stated at 5323(j)(2)(C) and 49 CFR 661.11. Rolling stock must be manufactured in the US and have a minimum 60% domestic content for FY2016 and FY2017, a minimum 65% domestic content for FY2018 and FY2019 and a minimum 70% domestic content for FY2020 and beyond.

A bidder or offeror must submit to the FTA recipient the appropriate Buy America certification (below) with all bids or offers on FTA-funded contracts, except those subject to a general waiver. Bids or offers that are not accompanied by a completed Buy America certification must be rejected as nonresponsive. This requirement does not apply to lower tier subcontractors.

Certification requirement for procurement of steel, iron, or manufactured products.

Certificate of Compliance with 49 U.S.C. 5323(j)(1)

The bidder or offeror hereby certifies that it will meet the requirements of 49 U.S.C. 5323(j)(1) and the applicable regulations in 49 CFR Part 661.5.

Date ____________________________________________________________

Signature______________________________________________________

Company Name_______________________________________________________

Title _____________________________________________________________

Certificate of Non-Compliance with 49 U.S.C. 5323(j)(1)

The bidder or offeror hereby certifies that it cannot comply with the requirements of 49 U.S.C. 5323(j)(1) and 49 C.F.R. 661.5, but it may qualify for an exception pursuant to 49 U.S.C. 5323(j)(2)(A), 5323(j)(2)(B), or 5323(j)(2)(D), and 49 C.F.R. 661.7.

Date _________________________________________________________________

Signature ___________________________________________________________

Company Name _________________________________________________________

Title _______________________________________________________________

Certification requirement for procurement of buses, other rolling stock and associated equipment.

Certificate of Compliance with 49 U.S.C. 5323(j)(2)(C).

The bidder or offeror hereby certifies that it will comply with the requirements of 49 U.S.C. 5323(j)(2)(C) and the regulations at 49 C.F.R. Part 661.11.

Date _________________________________________________________________

Signature ____________________________________________________________

Company Name ____________________________________________________________

Title _________________________________________________________________

Certificate of Non-Compliance with 49 U.S.C. 5323(j)(2)(C)

The bidder or offeror hereby certifies that it cannot comply with the requirements of 49 U.S.C. 5323(j)(2)(C) and 49 C.F.R. 661.11, but may qualify for an exception pursuant to 49 U.S.C. 5323(j)(2)(A), 5323(j)(2)(B), or 5323(j)(2)(D), and 49 C.F.R. 661.7.

Date _______________________________________________________________

Signature ____________________________________________________________

Company Name ________________________________________________________

Title _______________________________________________________________

CHARTER BUS REQUIREMENTS

49 U.S.C. 5323(d) 49 CFR Part 604


The Charter Bus requirements apply to the following type of contract: Operational Service Contracts.

Applicability to Micro-Purchases: Micro-purchases are defined as those purchases under $10,000. These requirements do not apply to micro-purchases.

Flow Down Requirements: The Charter Bus requirements flow down from FTA recipients and subrecipients to first tier service contractors.

Model Clause/Language: The relevant statutes and regulations do not mandate any specific clause or language. The following clause has been developed by FTA.

Charter Service Operations - The contractor agrees to comply with 49 U.S.C. 5323(d) and 49 CFR Part 604, which provides that recipients and subrecipients of FTA assistance are prohibited from providing charter service using federally funded equipment or facilities if there is at least one private charter operator willing and able to provide the service, except under one of the exceptions at 49 CFR 604.9. Any charter service provided under one of the exceptions must be "incidental," i.e., it must not interfere with or detract from the provision of mass transportation.

SCHOOL BUS REQUIREMENTS

49 U.S.C. 5323(F) 49 CFR Part 605

Applicability to Contracts: The School Bus requirements apply to the following type of contract: Operational Service Contracts.

Flow Down Requirements: The School Bus requirements flow down from FTA recipients and subrecipients to first tier service contractors.

Model Clause/Language: The relevant statutes and regulations do not mandate any specific clause or language. The following clause has been developed by FTA.

School Bus Operations - Pursuant to 69 U.S.C. 5323(f) and 49 CFR Part 605, recipients and subrecipients of FTA assistance may not engage in school bus operations exclusively for the transportation of students and school personnel in competition with private school bus operators unless qualified under specified exemptions. When operating exclusive school bus service under an allowable exemption, recipients and subrecipients may not use federally funded equipment, vehicles, or facilities.

CARGO PREFERENCE REQUIREMENTS

46 U.S.C. 1241 46 CFR Part 381

Applicability to Contracts: The Cargo Preference requirements apply to all contracts involving equipment, materials, or commodities which may be transported by ocean vessels.

Applicability to Micro-Purchases: Micro-purchases are defined as those purchases under $10,000. These requirements do not apply to micro-purchases; except for construction contracts over $2,000.

Flow Down Requirements: The Cargo Preference requirements apply to all subcontracts when the subcontract may be involved with the transport of equipment, material, or commodities by ocean vessel.

Model Clause/Language: The MARAD regulations at 46 CFR 381.7 contain suggested contract clauses. The following language is proffered by FTA.

Cargo Preference - Use of United States-Flag Vessels - The contractor agrees: a. to use privately owned United States-Flag commercial vessels to ship at least 50 percent of the gross tonnage

(computed separately for dry bulk carriers, dry cargo liners, and tankers) involved, whenever shipping any equipment, material, or commodities pursuant to the underlying contract to the extent such vessels are available at fair and reasonable rates for United States-Flag commercial vessels; b. to furnish within 20 working days following the date of loading for shipments originating within the United States or within 30 working days following the date of leading for shipments originating outside the United States, a legible copy of a rated, "on-board" commercial ocean bill-of -lading in English for each shipment of cargo described in the preceding paragraph to the Division of National Cargo, Office of Market Development, Maritime Administration, Washington, DC 20590 and to the FTA recipient (through the contractor in the case of a subcontractor's bill-of-lading.) c. to include these requirements in all subcontracts issued pursuant to this contract when the subcontract may involve the transport of equipment, material, or commodities by ocean vessel.

SEISMIC SAFETY REQUIREMENTS

42 U.S.C. 7701 et seq. 49 CFR Part 41

Applicability to Contracts: The Seismic Safety requirements apply only to contracts for the construction of new buildings or additions to existing buildings.


Flow Down Requirements: The Seismic Safety requirements flow down from FTA recipients and subrecipients to first tier contractors to assure compliance, with the applicable building standards for Seismic Safety, including the work performed by all subcontractors.

Model Clauses/Language: The regulations do not provide suggested language for third-party contract clauses. The following language has been developed by FTA.

Seismic Safety - The contractor agrees that any new building or addition to an existing building will be designed and constructed in accordance with the standards for Seismic Safety required in Department of Transportation Seismic Safety Regulations 49 CFR Part 41 and will certify to compliance to the extent required by the regulation. The contractor also agrees to ensure that all work performed under this contract including work performed by a subcontractor is in compliance with the standards required by the Seismic Safety Regulations and the certification of compliance issued on the project.

ENERGY CONSERVATION REQUIREMENTS

42 U.S.C. 6321 et seq. 2 CFR Part 1201

Applicability to Contracts: The Energy Conservation requirements are applicable to all contracts.


Flow Down Requirements: The Energy Conservation requirements extend to all third party contractors and their contracts at every tier and subrecipients and their subagreements at every tier.

Model Clause/Language: No specific clause is recommended in the regulations because the Energy Conservation requirements are so dependent on the state energy conservation plan. The following language has been developed by FTA.

Energy Conservation - The contractor agrees to comply with mandatory standards and policies relating to energy efficiency which are contained in the state energy conservation plan issued in compliance with the Energy Policy and Conservation Act.

CLEAN WATER REQUIREMENTS

33 U.S.C. 1251

Applicability to Contracts: The Clean Water requirements apply to each contract and subcontract which exceeds $150,000.

Flow Down Requirements: The Clean Water requirements flow down to FTA recipients and subrecipients at every tier.

Model Clause/Language: While no mandatory clause is contained in the Federal Water Pollution Control Act, as amended, the following language developed by FTA contains all the mandatory requirements.

Clean Water - (1) The Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Federal Water Pollution Control Act, as amended, 33 U.S.C. 1251 et seq . The Contractor agrees to report each violation to the Purchaser and understands and agrees that the Purchaser will, in turn, report each violation as required to assure notification to FTA and the appropriate EPA Regional Office.

(2) The Contractor also agrees to include these requirements in each subcontract exceeding $50,000 financed in whole or in part with Federal assistance provided by FTA.

LOBBYING

31 U.S.C. 1352 49 CFR Part 19 49 CFR Part 20

Applicability to Contracts: The Lobbying requirements apply to Construction/Architectural and Engineering/Acquisition of Rolling Stock/Professional Service Contract/Operational Service Contract/Turnkey contracts over $100,000.

Flow Down Requirement: The Lobbying requirements mandate the maximum flow down, pursuant to Byrd Anti-Lobbying Amendment, 31 U.S.C. § 1352(b)(5) and 49 C.F.R. Part 19, Appendix A, Section 7.

Mandatory Clause/Language: Clause and specific language therein are mandated by 49 CFR Part 19, Appendix A. Modifications have been made to the Clause pursuant to Section 10 of the Lobbying Disclosure Act of 1995, P.L. 104-65 [to be codified at 2 U.S.C. § 1601, et seq. ]

Lobbying Certification and Disclosure of Lobbying Activities for third party contractors are mandated by 31 U.S.C. 1352(b)(5), as amended by Section 10 of the Lobbying Disclosure Act of 1995, and DOT implementing regulation, "New Restrictions on Lobbying," at 49 CFR § 20.110(d)

Language in Lobbying Certification is mandated by 49 CFR Part 19, Appendix A, Section 7, which provides that contractors file the certification required by 49 CFR Part 20, Appendix A.

Use of "Disclosure of Lobbying Activities," Standard Form-LLL set forth in Appendix B of 49 CFR Part 20, as amended by "Government wide Guidance For New Restrictions on Lobbying," 61 Fed. Reg. 1413 (1/19/96) is mandated by 49 CFR Part 20, Appendix A.

Byrd Anti-Lobbying Amendment, 31 U.S.C. 1352, as amended by the Lobbying Disclosure Act of 1995, P.L. 104-65 [to be codified at 2 U.S.C. § 1601, et seq.] - Contractors who apply or bid for an award of $50,000 or more shall file the certification required by 49 CFR part 20, "New Restrictions on Lobbying." Each tier certifies to the tier above that it will not and has not used Federal appropriated funds to pay any person or organization for influencing or attempting to influence an officer or employee of any agency, a member of Congress, officer or employee of Congress, or an employee of a member of Congress in connection with obtaining any Federal contract, grant or any other award covered by 31 U.S.C. 1352. Each tier shall also disclose the name of any registrant under the Lobbying Disclosure Act of 1995 who has made lobbying contacts on its behalf with non-Federal funds with respect to that Federal contract, grant or award covered by 31 U.S.C. 1352. Such disclosures are forwarded from tier to tier up to the recipient.

APPENDIX A, 49 CFR PART 20--CERTIFICATION REGARDING LOBBYING

Certification for Contracts, Grants, Loans, and Cooperative Agreements

(To be submitted with each bid or offer exceeding $100,000)

The undersigned [Contractor] certifies, to the best of his or her knowledge and belief, that:

(1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to influence an officer or employee of an agency, a Member

of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with the awarding of any Federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement.

(2) If any funds other than Federal appropriated funds have been paid or will be paid to any person for making lobbying contacts to an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with this Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form--LLL, "Disclosure Form to Report Lobbying," in accordance with its instructions [as amended by "Government wide Guidance for New Restrictions on Lobbying," 61 Fed. Reg. 1413 (1/19/96). Note: Language in paragraph (2) herein has been modified in accordance with Section 10 of the Lobbying Disclosure Act of 1995 (P.L. 104-65, to be codified at 2 U.S.C. 1601, et seq .)]

(3) The undersigned shall require that the language of this certification be included in the award documents for all subawards at all tiers (including subcontracts, subgrants, and contracts under grants, loans, and cooperative agreements) and that all subrecipients shall certify and disclose accordingly.

This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this certification is a prerequisite for making or entering into this transaction imposed by 31, U.S.C. § 1352 (as amended by the Lobbying Disclosure Act of 1995). Any person who fails to file the required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.

[Note: Pursuant to 31 U.S.C. § 1352(c)(1)-(2)(A), any person who makes a prohibited expenditure or fails to file or amend a required certification or disclosure form shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such expenditure or failure.]

The Contractor, ___________________, certifies or affirms the truthfulness and accuracy of each statement of its certification and disclosure, if any. In addition, the Contractor understands and agrees that the provisions of 31 U.S.C. A 3801, et seq., apply to this certification and disclosure, if any.

__________________________ Signature of Contractor's Authorized Official

__________________________ Name and Title of Contractor's Authorized Official

___________________________ Date

ACCESS TO RECORDS AND REPORTS

49 U.S.C. 5325 18 CFR 18.36 (i) 49 CFR 633.17

Applicability to Contracts: Reference Chart "Requirements for Access to Records and Reports by Type of Contracts"


Flow Down Requirement: FTA does not require the inclusion of these requirements in subcontracts.

Model Clause/Language: The specified language is not mandated by the statutes or regulations referenced, but the language provided paraphrases the statutory or regulatory language.

Access to Records - The following access to records requirements apply to this Contract:

1. Where the Purchaser is not a State but a local government and is the FTA Recipient or a subgrantee of the FTA Recipient in accordance with 18 C. F. R. 18.36(i), the Contractor agrees to provide the Purchaser, the FTA Administrator, the Comptroller General of the United States or any of their authorized representatives access to any books, documents, papers and records of the Contractor which are directly pertinent to this contract for the purposes of making audits, examinations, excerpts and transcriptions. Contractor also agrees, pursuant to 49 C. F. R. 633.17 to provide the FTA Administrator or his authorized representatives including any PMO Contractor access to Contractor's records and construction sites pertaining to a major capital project, defined at 49 U.S.C. 5302(a)1, which is receiving federal financial assistance through the programs described at 49 U.S.C. 5307, 5309 or 5311.

2. Where the Purchaser is a State and is the FTA Recipient or a subgrantee of the FTA Recipient in accordance with 49 C.F.R. 633.17, Contractor agrees to provide the Purchaser, the FTA Administrator or his authorized representatives, including any PMO Contractor, access to the Contractor's records and construction sites pertaining to a major capital project, defined at 49 U.S.C. 5302(a)1, which is receiving federal financial assistance through the programs described at 49 U.S.C. 5307, 5309 or 5311. By definition, a major capital project excludes contracts of less than the simplified acquisition threshold currently set at $250,000.

3. Where the Purchaser enters into a negotiated contract for other than a small purchase or under the simplified acquisition threshold and is an institution of higher education, a hospital or other non-profit organization and is the FTA Recipient or a subgrantee of the FTA Recipient in accordance with 49 C.F.R. 19.48, Contractor agrees to provide the Purchaser, FTA Administrator, the Comptroller General of the United States or any of their duly authorized representatives with access to any books, documents, papers and record of the Contractor which are directly pertinent to this contract for the purposes of making audits, examinations, excerpts and transcriptions.

4. Where any Purchaser which is the FTA Recipient or a subgrantee of the FTA Recipient in accordance with 49 U.S.C. 5325(a) enters into a contract for a capital project or improvement (defined at 49 U.S.C. 5302(a)1) through other than competitive bidding, the Contractor shall make available records related to the contract to the Purchaser, the Secretary of Transportation and the Comptroller General or any authorized officer or employee of any of them for the purposes of conducting an audit and inspection.

5. The Contractor agrees to permit any of the foregoing parties to reproduce by any means whatsoever or to copy excerpts and transcriptions as reasonably needed.

6. The Contractor agrees to maintain all books, records, accounts and reports required under this contract for a period of not less than three years after the date of termination or expiration of this contract, except in the event of litigation or settlement of claims arising from the performance of this contract, in which case Contractor agrees to maintain same until the Purchaser, the FTA Administrator, the Comptroller General, or any of their duly authorized representatives, have disposed of all such litigation, appeals, claims or exceptions related thereto. Reference 18 CFR 18.39(i)(11).

7. FTA does not require the inclusion of these requirements in subcontracts.

REQUIREMENTS FOR ACCESS TO RECORDS AND REPORTS BY TYPES OF CONTRACT

Operational

Service

Contract

Turnkey

Contract

Construction

Contract

Arch. or

Engineering

Contract

Rolling

Stock

Contract

Professional

Service

Contract

State Grantees

Contracts below

Simplified

Acquisition

Threshold (Small

Purchase)

($250,000)

None

Those

imposed on

state pass

thru to

Contractor

None None None None

Contracts above

$100,000/Capital

Projects

None

unless1 non-

competitive

award

Those

imposed on

state pass

thru to

contractor

Yes, if non-

competitive

award or if

funded thru2

5307, 5309,

5311

None unless

non-

competitive

award

None unless

non-

competitive

award

None unless

non-

competitive

award

Non-State Grantees

Contracts below

Simplified

Acquisition

Threshold (Small

Purchase)

($250,000)

Yes

Those

imposed on

non-state

Grantee pass

thru to

Contractor

Yes Yes Yes Yes

Contracts above

$100,000/Capital

Projects

Yes

Those

imposed on

non-state

Grantee pass

thru to

Contractor

Yes Yes Yes Yes

Sources of Authority:49 USC 5325 (a), 49 CFR 633.17, 18 CFR 18.36 (i)

FEDERAL CHANGES

2 CFR Part 1201

Applicability to Contracts: The Federal Changes requirement applies to all contracts.


Flow Down Requirement: The Federal Changes requirement flows down appropriately to each applicable changed requirement.

Model Clause/Language: No specific language is mandated. The following language has been developed by FTA.

Federal Changes - Contractor shall at all times comply with all applicable FTA regulations, policies, procedures and directives, including without limitation those listed directly or by reference in the Master Agreement between Purchaser and FTA, as they may be amended or promulgated from time to time during the term of this contract. Contractor's failure to so comply shall constitute a material breach of

http://www.fta.dot.gov/3162.html

http://www.fta.dot.gov/3162.html

this contract.

BONDING REQUIREMENTS

Applicability to Contracts: For those construction or facility improvement contracts or subcontracts exceeding $250,000, FTA may accept the bonding policy and requirements of the recipient, provided that they meet the minimum requirements for construction contracts as follows:

a. A bid guarantee from each bidder equivalent to five (5) percent of the bid price. The "bid guarantees" shall consist of a firm commitment such as a bid bond, certifies check, or other negotiable instrument accompanying a bid as assurance that the bidder will, upon acceptance of his bid, execute such contractual documents as may be required within the time specified.

b. A performance bond on the part to the Contractor for 100 percent of the contract price. A "performance bond" is one executed in connection with a contract to secure fulfillment of all the contractor's obligations under such contract.

c. A payment bond on the part of the contractor for 100 percent of the contract price. A "payment bond" is one executed in connection with a contract to assure payment, as required by law, of all persons supplying labor and material in the execution of the work provided for in the contract. Payment bond amounts required from Contractors are as follows:

(1) 50% of the contract price if the contract price is not more than $1 million;

(2) 40% of the contract price if the contract price is more than $1 million but not more than $5 million; or

(3) $2.5 million if the contract price is more than $5 million.

d. A cash deposit, certified check or other negotiable instrument may be accepted by a grantee in lieu of performance and payment bonds, provided the grantee has established a procedure to assure that the interest of FTA is adequately protected. An irrevocable letter of credit would also satisfy the requirement for a bond.

Flow Down Requirement: Bonding requirements flow down to the first tier contractors.

Model Clauses/Language: FTA does not prescribe specific wording to be included in third party contracts. FTA has prepared sample clauses as follows:

Bid Bond Requirements (Construction)

(a) Bid Security

A Bid Bond must be issued by a fully qualified surety company acceptable to (Recipient) and listed as a company currently authorized under 31 CFR, Part 223 as possessing a Certificate of Authority as described thereunder.

(b) Rights Reserved

In submitting this Bid, it is understood and agreed by bidder that the right is reserved by (Recipient) to reject any and all bids, or part of any bid, and it is agreed that the Bid may not be withdrawn for a period of [ninety (90)] days subsequent to the opening of bids, without the written consent of (Recipient).

It is also understood and agreed that if the undersigned bidder should withdraw any part or all of his bid within [ninety (90)] days after the bid opening without the written consent of (Recipient), shall refuse or be unable to enter into this Contract, as provided above, or refuse or be unable to furnish adequate and acceptable Performance Bonds and Labor and Material Payments Bonds, as provided above, or refuse or be unable to furnish adequate and acceptable insurance, as provided above, he shall forfeit his bid security to the extent of (Recipient's) damages occasioned by such withdrawal, or refusal, or inability to enter into an agreement, or provide adequate security therefor.

It is further understood and agreed that to the extent the defaulting bidder's Bid Bond, Certified Check, Cashier's Check, Treasurer's Check, and/or Official Bank Check (excluding any income generated thereby which has been retained by (Recipient) as provided in [Item x "Bid Security" of the Instructions to Bidders]) shall prove inadequate to fully recompense (Recipient) for the damages occasioned by default, then the undersigned bidder agrees to indemnify (Recipient) and pay over to (Recipient) the difference between the bid security and (Recipient's) total damages, so as to make (Recipient) whole.

The undersigned understands that any material alteration of any of the above or any of the material contained on this form, other than that requested, will render the bid unresponsive.

Performance and Payment Bonding Requirements (Construction)

The Contractor shall be required to obtain performance and payment bonds as follows:

(a) Performance bonds

1. The penal amount of performance bonds shall be 100 percent of the original contract price, unless the (Recipient) determines that a lesser amount would be adequate for the protection of the (Recipient).

2. The (Recipient) may require additional performance bond protection when a contract price is increased. The increase in protection shall generally equal 100 percent of the increase in contract price. The (Recipient) may secure additional protection by directing the Contractor to increase the penal amount of the existing bond or to obtain an additional bond.

(b) Payment bonds

1. The penal amount of the payment bonds shall equal:

(i) Fifty percent of the contract price if the contract price is not more than $1 million.

(ii) Forty percent of the contract price if the contract price is more than $1 million but not more than $5 million; or

(iii) Two and one half million if the contract price is more than $5 million.

2. If the original contract price is $5 million or less, the (Recipient) may require additional protection as required by subparagraph 1 if the contract price is increased.

Performance and Payment Bonding Requirements (Non-Construction)

The Contractor may be required to obtain performance and payment bonds when necessary to protect the (Recipient's) interest.

(a) The following situations may warrant a performance bond:

1. (Recipient) property or funds are to be provided to the contractor for use in performing the contract or as partial compensation (as in retention of salvaged material).

2. A contractor sells assets to or merges with another concern, and the (Recipient), after recognizing the latter concern as the successor in interest, desires assurance that it is financially capable.

3. Substantial progress payments are made before delivery of end items starts.

4. Contracts are for dismantling, demolition, or removal of improvements.

(b) When it is determined that a performance bond is required, the Contractor shall be required to obtain performance bonds as follows:

1. The penal amount of performance bonds shall be 100 percent of the original contract price, unless the (Recipient) determines that a lesser amount would be adequate for the protection of the (Recipient).

2. The (Recipient) may require additional performance bond protection when a contract price is increased. The increase in protection shall generally equal 100 percent of the increase in contract price. The (Recipient) may secure additional protection by directing the Contractor to increase the penal amount of the existing bond or to obtain an additional bond.

(c) A payment bond is required only when a performance bond is required, and if the use of payment bond is in the (Recipient's) interest.

(d) When it is determined that a payment bond is required, the Contractor shall be required to obtain payment bonds as follows:

1. The penal amount of payment bonds shall equal:

(i) Fifty percent of the contract price if the contract price is not more than $1 million;

(ii) Forty percent of the contract price if the contract price is more than $1 million

but not more than $5 million; or

(iii) Two and one half million if the contract price is increased.

Advance Payment Bonding Requirements

The Contractor may be required to obtain an advance payment bond if the contract contains an advance payment provision and a performance bond is not furnished. The (recipient) shall determine the amount of the advance payment bond necessary to protect the (Recipient).

Patent Infringement Bonding Requirements (Patent Indemnity)

The Contractor may be required to obtain a patent indemnity bond if a performance bond is not furnished and the financial responsibility of the Contractor is unknown or doubtful. The (recipient) shall determine the amount of the patent indemnity to protect the (Recipient).

Warranty of the Work and Maintenance Bonds

1. The Contractor warrants to (Recipient), the Architect and/or Engineer that all materials and equipment furnished under this Contract will be of highest quality and new unless otherwise specified by (Recipient), free from faults and defects and in conformance with the Contract Documents. All work not so conforming to these standards shall be considered defective. If required by the [Project Manager], the Contractor shall furnish satisfactory evidence as to the kind and quality of materials and equipment.

2. The Work furnished must be of first quality and the workmanship must be the best obtainable in the various trades. The Work must be of safe, substantial and durable construction in all respects. The Contractor hereby guarantees the Work against defective materials or faulty workmanship for a minimum period of one (1) year after Final Payment by (Recipient) and shall replace or repair any defective materials or equipment or faulty workmanship during the period of the guarantee at no cost to (Recipient). As additional security for these guarantees, the Contractor shall, prior to the release of Final Payment [as provided in Item X below], furnish separate Maintenance (or Guarantee) Bonds in form acceptable to (Recipient) written by the same corporate surety that provides the Performance Bond and Labor and Material Payment Bond for this Contract. These bonds shall secure the Contractor's obligation to replace or repair defective materials and faulty workmanship for a minimum period of one (1) year after Final Payment and shall be written in an amount equal to ONE HUNDRED PERCENT (100%) of the CONTRACT SUM, as adjusted (if at all).

CLEAN AIR

42 U.S.C. 7401 et seq 40 CFR 15.61

2 CFR Part 1201

Applicability to Contracts: The Clean Air requirements apply to all contracts exceeding $150,000, including indefinite quantities where the amount is expected to exceed $150,000 in any year.

Flow Down Requirement: The Clean Air requirements flow down to all subcontracts which exceed $150,000.

Model Clauses/Language: No specific language is required. FTA has proposed the following language.

(1) The Contractor agrees to comply with all applicable standards, orders or regulations issued pursuant to the Clean Air Act, as amended, 42 U.S.C. §§ 7401 et seq . The Contractor agrees to report each violation to the Purchaser and understands and agrees that the Purchaser will, in turn, report each violation as required to assure notification to FTA and the appropriate EPA Regional Office.

(2) The Contractor also agrees to include these requirements in each subcontract exceeding $150,000 financed in whole or in part with Federal assistance provided by FTA.

RECYCLED PRODUCTS

42 U.S.C. 6962 40 CFR Part 247

Executive Order 12873

Applicability to Contracts: The Recycled Products requirements apply to all contracts for items designated by the EPA, when the purchaser or contractor procures $10,000 or more of one of these items during the fiscal year, or has procured $10,000 or more of such items in the previous fiscal year, using Federal funds. New requirements for "recovered materials" will become effective May 1, 1996. These new regulations apply to all procurement actions involving items designated by the EPA, where the procuring agency purchases $10,000 or more of one of these items in a fiscal year, or when the cost of such items purchased during the previous fiscal year was $10,000.


Flow Down Requirement: These requirements flow down to all to all contractor and subcontractor tiers.

Model Clause/Language: No specific clause is mandated, but FTA has developed the following language.

Recovered Materials - The contractor agrees to comply with all the requirements of Section 6002 of the Resource Conservation and Recovery Act (RCRA), as amended (42 U.S.C. 6962), including but not limited to the regulatory provisions of 40 CFR Part 247, and Executive Order 12873, as they apply to the procurement of the items designated in Subpart B of 40 CFR Part 247.

DAVIS-BACON AND COPELAND ANTI-KICKBACK ACTS

Background and Application The Davis-Bacon and Copeland Acts are codified at 40 USC 3141, et seq. and 18 USC 874. The Acts apply to grantee construction contracts and subcontracts that “at least partly are financed by a loan or grant from the Federal Government.” 40 USC 3145(a), 29 CFR 5.2(h), 18 CFR 18.36(i)(5). The Acts apply to any construction contract over $2,000. 40 USC 3142(a), 29 CFR 5.5(a). ‘Construction,’ for purposes of the Acts, includes “actual construction, alteration and/or repair, including painting and decorating.” 29 CFR 5.5(a). The requirements of both Acts are incorporated into a single clause (see 29 CFR 3.11) enumerated at 29 CFR 5.5(a) and reproduced below. The clause language is drawn directly from 29 CFR 5.5(a) and any deviation from the model clause below should be coordinated with counsel to ensure the Acts’ requirements are satisfied. Clause Language Davis-Bacon and Copeland Anti-Kickback Acts (1) Minimum wages - (i) All laborers and mechanics employed or working upon the site of the work (or under the United States Housing Act of 1937 or under the Housing Act of 1949 in the construction or development of the project), will be paid unconditionally and not less often than once a week, and without subsequent deduction or rebate on any account (except such payroll deductions as are permitted by regulations issued by the Secretary of Labor under the Copeland Act (29 CFR part 3)), the full amount of wages and bona fide fringe benefits (or cash equivalents thereof) due at time of payment computed at rates not less than those contained in the wage determination of the Secretary of Labor which is attached hereto and made a part hereof, regardless of any contractual relationship which may be alleged to exist between the contractor and such laborers and mechanics. Contributions made or costs reasonably anticipated for bona fide fringe benefits under section 1(b)(2) of the Davis-Bacon Act on behalf of laborers or mechanics are considered wages paid to such laborers or mechanics, subject to the provisions of paragraph (1)(iv) of this section; also, regular contributions made or costs incurred for more than a weekly period (but not less often than quarterly) under plans, funds, or programs which cover the particular weekly period, are deemed to be constructively made or incurred during such weekly period. Such laborers and mechanics shall be paid the appropriate wage rate and fringe benefits on the wage determination for the classification of work actually performed, without regard to skill, except as provided in 29 CFR Part 5.5(a)(4). Laborers or mechanics performing work in more than one classification may be compensated at the rate specified for each classification for the time actually worked therein: Provided, That the employer's payroll records accurately set forth the time spent in each classification in which work is performed. The wage determination (including any additional classifications and wage rates conformed under paragraph (1)(ii) of this section) and the Davis-Bacon poster (WH-1321) shall be posted at all times by the contractor and its subcontractors at the site of the work in a prominent and accessible place where it can be easily seen by the workers.

(ii)(A) The contracting officer shall require that any class of laborers or mechanics, including helpers, which is not listed in the wage determination and which is to be employed under the contract shall be classified in conformance with the wage determination. The contracting officershall approve an additional classification and wage rate and fringe benefits therefore only when the following criteria have been met: (1) Except with respect to helpers as defined as 29 CFR 5.2(n)(4), the work to be performed by the classification requested is not performed by a classification in the wage determination; and (2) The classification is utilized in the area by the construction industry; and (3) The proposed wage rate, including any bona fide fringe benefits, bears a reasonable relationship to the wage rates contained in the wage determination; and (4) With respect to helpers as defined in 29 CFR 5.2(n)(4), such a classification prevails in the area in which the work is performed. (B) If the contractor and the laborers and mechanics to be employed in the classification (if known), or their representatives, and the contracting officer agree on the classification and wage rate (including the amount designated for fringe benefits where appropriate), a report of the action taken shall be sent by the contracting officer to the Administrator of the Wage and Hour Division, Employment Standards Administration, U.S. Department of Labor, Washington, DC 20210. The Administrator, or an authorized representative, will approve, modify, or disapprove every additional classification action within 30 days of receipt and so advise the contracting officer or will notify the contracting officer within the 30-day period that additional time is necessary. (C) In the event the contractor, the laborers or mechanics to be employed in the classification or their representatives, and the contracting officer do not agree on the proposed classification and wage rate (including the amount designated for fringe benefits, where appropriate), the contracting officer shall refer the questions, including the views of all interested parties and the recommendation of the contracting officer, to the Administrator for determination. The Administrator, or an authorized representative, will issue a determination within 30 days of receipt and so advise the contracting officer or will notify the contracting officer within the 30-day period that additional time is necessary. (D) The wage rate (including fringe benefits where appropriate) determined pursuant to paragraphs (a)(1)(ii) (B) or (C) of this section, shall be paid to all workers performing work in the classification under this contract from the first day on which work is performed in the classification. (iii) Whenever the minimum wage rate prescribed in the contract for a class of laborers or mechanics includes a fringe benefit which is not expressed as an hourly rate, the contractor shall either pay the benefit as stated in the wage determination or shall pay another bona fide fringe benefit or an hourly cash equivalent thereof. (iv) If the contractor does not make payments to a trustee or other third person, the contractor may consider as part of the wages of any laborer or mechanic the amount of any costs reasonably anticipated in providing bona fide fringe benefits under a plan or program, Provided, That the Secretary of Labor has found, upon the written request of the contractor, that the applicable standards of the Davis-Bacon Act have been met. The Secretary of Labor may require the contractor to set aside in a separate account assets for the meeting of obligations under the plan or program. (v)(A) The contracting officer shall require that any class of laborers or mechanics which is not listed in the wage determination and which is to be employed under the contract shall be classified in conformance with the wage determination. The contracting officer shall approve an additional classification and wage rate and fringe benefits therefor only when the following criteria have been met: (1) The work to be performed by the classification requested is not performed by a classification in the wage determination; and (2) The classification is utilized in the area by the construction industry; and (3) The proposed wage rate, including any bona fide fringe benefits, bears a reasonable relationship to

the wage rates contained in the wage determination. (B) If the contractor and the laborers and mechanics to be employed in the classification (if known), or their representatives, and the contracting officer agree on the classification and wage rate (including the amount designated for fringe benefits where appropriate), a report of the action taken shall be sent by the contracting officer to the Administrator of the Wage and Hour Division, Employment Standards Administration, Washington, DC 20210. The Administrator, or an authorized representative, will approve, modify, or disapprove every additional classification action within 30 days of receipt and so advise the contracting officer or will notify the contracting officer within the 30-day period that additional time is necessary. (C) In the event the contractor, the laborers or mechanics to be employed in the classification or their representatives, and the contracting officer do not agree on the proposed classification and wage rate (including the amount designated for fringe benefits, where appropriate), the contracting officer shall refer the questions, including the views of all interested parties and the recommendation of the contracting officer, to the Administrator for determination. The Administrator, or an authorized representative, will issue a determination with 30 days of receipt and so advise the contracting officer or will notify the contracting officer within the 30-day period that additional time is necessary. (D) The wage rate (including fringe benefits where appropriate) determined pursuant to paragraphs (a)(1)(v) (B) or (C) of this section, shall be paid to all workers performing work in the classification under this contract from the first day on which work is performed in the classification. (2) Withholding - The Recipient shall upon its own action or upon written request of an authorized representative of the Department of Labor withhold or cause to be withheld from the contractor under this contract or any other Federal contract with the same prime contractor, or any other federally-assisted contract subject to Davis-Bacon prevailing wage requirements, which is held by the same prime contractor, so much of the accrued payments or advances as may be considered necessary to pay laborers and mechanics, including apprentices, trainees, and helpers, employed by the contractor or any subcontractor the full amount of wages required by the contract. In the event of failure to pay any laborer or mechanic, including any apprentice, trainee, or helper, employed or working on the site of the work (or under the United States Housing Act of 1937 or under the Housing Act of 1949 in the construction or development of the project), all or part of the wages required by the contract, the Recipient may, after written notice to the contractor, sponsor, applicant, or owner, take such action as may be necessary to cause the suspension of any further payment, advance, or guarantee of funds until such violations have ceased. (3) Payrolls and basic records - (i) Payrolls and basic records relating thereto shall be maintained by the contractor during the course of the work and preserved for a period of three years thereafter for all laborers and mechanics working at the site of the work (or under the United States Housing Act of 1937, or under the Housing Act of 1949, in the construction or development of the project). Such records shall contain the name, address, and social security number of each such worker, his or her correct classification, hourly rates of wages paid (including rates of contributions or costs anticipated for bona fide fringe benefits or cash equivalents thereof of the types described in section 1(b)(2)(B) of the Davis-Bacon Act), daily and weekly number of hours worked, deductions made and actual wages paid. Whenever the Secretary of Labor has found under 29 CFR 5.5(a)(1)(iv) that the wages of any laborer or mechanic include the amount of any costs reasonably anticipated in providing benefits under a plan or program described in section 1(b)(2)(B) of the Davis-Bacon Act, the contractor shall maintain records which show that the commitment to provide such benefits is enforceable, that the plan or program is financially responsible, and that the plan or program has been communicated in writing to the laborers or mechanics affected, and records which show the costs anticipated or the actual cost incurred in providing such benefits. Contractors employing apprentices or trainees under approved programs shall maintain written evidence of the registration of apprenticeship programs and certification of trainee programs, the registration of the apprentices and trainees, and the ratios and wage rates prescribed in the applicable programs. (ii)(A) The contractor shall submit weekly for each week in which any contract work is performed a copy of all payrolls to the Recipient for transmission to the Federal Transit Administration. The payrolls submitted shall set out accurately and completely all of the information required to be maintained under section 5.5(a)(3)(i) of Regulations, 29 CFR part 5. This information may be submitted in any form desired. Optional Form WH-347 is available for this purpose and may be purchased from the Superintendent of

Documents (Federal Stock Number 029-005-00014-1), U.S. Government Printing Office, Washington, DC 20402. The prime contractor is responsible for the submission of copies of payrolls by all subcontractors. (B) Each payroll submitted shall be accompanied by a "Statement of Compliance," signed by the contractor or subcontractor or his or her agent who pays or supervises the payment of the persons employed under the contract and shall certify the following: (1) That the payroll for the payroll period contains the information required to be maintained under section 5.5(a)(3)(i) of Regulations, 29 CFR part 5 and that such information is correct and complete; (2) That each laborer or mechanic (including each helper, apprentice, and trainee) employed on the contract during the payroll period has been paid the full weekly wages earned, without rebate, either directly or indirectly, and that no deductions have been made either directly or indirectly from the full wages earned, other than permissible deductions as set forth in Regulations, 29 CFR part 3; (3) That each laborer or mechanic has been paid not less than the applicable wage rates and fringe benefits or cash equivalents for the classification of work performed, as specified in the applicable wage determination incorporated into the contract. (C) The weekly submission of a properly executed certification set forth on the reverse side of Optional Form WH-347 shall satisfy the requirement for submission of the "Statement of Compliance" required by paragraph (a)(3)(ii)(B) of this section. (D) The falsification of any of the above certifications may subject the contractor or subcontractor to civil or criminal prosecution under section 1001 of title 18 and section 231 of title 31 of the United States Code. (iii) The contractor or subcontractor shall make the records required under paragraph (a)(3)(i) of this section available for inspection, copying, or transcription by authorized representatives of the Federal Transit Administration or the Department of Labor, and shall permit such representatives to interview employees during working hours on the job. If the contractor or subcontractor fails to submit the required records or to make them available, the Federal agency may, after written notice to the contractor, sponsor, applicant, or owner, take such action as may be necessary to cause the suspension of any further payment, advance, or guarantee of funds. Furthermore, failure to submit the required records upon request or to make such records available may be grounds for debarment action pursuant to 29 CFR 5.12. (4) Apprentices and trainees - (i) Apprentices - Apprentices will be permitted to work at less than the predetermined rate for the work they performed when they are employed pursuant to and individually registered in a bona fide apprenticeship program registered with the U.S. Department of Labor, Employment and Training Administration, Bureau of Apprenticeship and Training, or with a State Apprenticeship Agency recognized by the Bureau, or if a person is employed in his or her first 90 days of probationary employment as an apprentice in such an apprenticeship program, who is not individually registered in the program, but who has been certified by the Bureau of Apprenticeship and Training or a State Apprenticeship Agency (where appropriate) to be eligible for probationary employment as an apprentice. The allowable ratio of apprentices to journeymen on the job site in any craft classification shall not be greater than the ratio permitted to the contractor as to the entire work force under the registered program. Any worker listed on a payroll at an apprentice wage rate, who is not registered or otherwise employed as stated above, shall be paid not less than the applicable wage rate on the wage determination for the classification of work actually performed. In addition, any apprentice performing work on the job site in excess of the ratio permitted under the registered program shall be paid not less than the applicable wage rate on the wage determination for the work actually performed. Where a contractor is performing construction on a project in a locality other than that in which its program is registered, the ratios and wage rates (expressed in percentages of the journeyman's hourly rate) specified in the contractor's or subcontractor's registered program shall be observed. Every apprentice must be paid at not less than the rate specified in the registered program for the apprentice's level of progress, expressed as a percentage of the journeymen hourly rate specified in the applicable wage determination. Apprentices shall be paid fringe benefits in accordance with the provisions of the apprenticeship program. If the apprenticeship program does not specify fringe benefits, apprentices must be paid the full amount of fringe benefits listed on the wage determination for the applicable classification. If the Administrator of the Wage and Hour Division of the U.S. Department of Labor determines that a

different practice prevails for the applicable apprentice classification, fringes shall be paid in accordance with that determination. In the event the Bureau of Apprenticeship and Training, or a State Apprenticeship Agency recognized by the Bureau, withdraws approval of an apprenticeship program, the contractor will no longer be permitted to utilize apprentices at less than the applicable predetermined rate for the work performed until an acceptable program is approved. (ii) Trainees - Except as provided in 29 CFR 5.16, trainees will not be permitted to work at less than the predetermined rate for the work performed unless they are employed pursuant to and individually registered in a program which has received prior approval, evidenced by formal certification by the U.S. Department of Labor, Employment and Training Administration. The ratio of trainees to journeymen on the job site shall not be greater than permitted under the plan approved by the Employment and Training Administration. Every trainee must be paid at not less than the rate specified in the approved program for the trainee's level of progress, expressed as a percentage of the journeyman hourly rate specified in the applicable wage determination. Trainees shall be paid fringe benefits in accordance with the provisions of the trainee program. If the trainee program does not mention fringe benefits, trainees shall be paid the full amount of fringe benefits listed on the wage determination unless the Administrator of the Wage and Hour Division determines that there is an apprenticeship program associated with the corresponding journeyman wage rate on the wage determination which provides for less than full fringe benefits for apprentices. Any employee listed on the payroll at a trainee rate who is not registered and participating in a training plan approved by the Employment and Training Administration shall be paid not less than the applicable wage rate on the wage determination for the classification of work actually performed. In addition, any trainee performing work on the job site in excess of the ratio permitted under the registered program shall be paid not less than the applicable wage rate on the wage determination for the work actually performed. In the event the Employment and Training Administration withdraws approval of a training program, the contractor will no longer be permitted to utilize trainees at less than the applicable predetermined rate for the work performed until an acceptable program is approved. (iii) Equal employment opportunity - The utilization of apprentices, trainees and journeymen under this part shall be in conformity with the equal employment opportunity requirements of Executive Order 11246, as amended, and 29 CFR part 30.

(5) Compliance with Copeland Act requirements - The contractor shall comply with the requirements of 29 CFR part 3, which are incorporated by reference in this contract.

(6) Subcontracts - The contractor or subcontractor shall insert in any subcontracts the clauses contained in 29 CFR 5.5(a)(1) through (10) and such other clauses as the Federal Transit Administration may by appropriate instructions require, and also a clause requiring the subcontractors to include these clauses in any lower tier subcontracts. The prime contractor shall be responsible for the compliance by any subcontractor or lower tier subcontractor with all the contract clauses in 29 CFR 5.5. (7) Contract termination: debarment - A breach of the contract clauses in 29 CFR 5.5 may be grounds for termination of the contract, and for debarment as a contractor and a subcontractor as provided in 29 CFR 5.12. (8) Compliance with Davis-Bacon and Related Act requirements - All rulings and interpretations of the Davis-Bacon and Related Acts contained in 29 CFR parts 1, 3, and 5 are herein incorporated by reference in this contract. (9) Disputes concerning labor standards - Disputes arising out of the labor standards provisions of this contract shall not be subject to the general disputes clause of this contract. Such disputes shall be resolved in accordance with the procedures of the Department of Labor set forth in 29 CFR parts 5, 6, and 7. Disputes within the meaning of this clause include disputes between the contractor (or any of its subcontractors) and the contracting agency, the U.S. Department of Labor, or the employees or their representatives. (10) Certification of eligibility - (i) By entering into this contract, the contractor certifies that neither it (nor he or she) nor any person or firm who has an interest in the contractor's firm is a person or firm ineligible to be awarded Government contracts by virtue of section 3(a) of the Davis-Bacon Act or 29 CFR 5.12(a)(1). (ii) No part of this contract shall be subcontracted to any person or firm ineligible for award of a Government contract by virtue of section 3(a) of the Davis-Bacon Act or 29 CFR 5.12(a)(1).

(iii) The penalty for making false statements is prescribed in the U.S. Criminal Code, 18 U.S.C. 1001.

CONTRACT WORK HOURS AND SAFETY STANDARDS ACT

Background and Application The Contract Work Hours and Safety Standards Act is codified at 40 USC 3701, et seq. The Act applies to grantee contracts and subcontracts “financed at least in part by loans or grants from … the [Federal] Government.” 40 USC 3701(b)(1)(B)(iii) and (b)(2), 29 CFR 5.2(h), 18 CFR 18.36(i)(6). Although the original Act required its application in any construction contract over $2,000 or non-construction contract to which the Act applied over $2,500 (and language to that effect is still found in 18 CFR 18.36(i)(6)), the Act no longer applies to any “contract in an amount that is not greater than $100,000.” 40 USC 3701(b)(3)(A)(iii). The Act applies to construction contracts and, in very limited circumstances, non-construction projects that employ “laborers or mechanics on a public work.” These non-construction applications do not generally apply to transit procurements because transit procurements (to include rail cars and buses) are deemed “commercial items.” 40 USC 3707, 41 USC 403 (12). A grantee that contemplates entering into a contract to procure a developmental or unique item should consult counsel to determine if the Act applies to that procurement and that additional language required by 29 CFR 5.5(c) must be added to the basic clause below. The clause language is drawn directly from 29 CFR 5.5(b) and any deviation from the model clause below should be coordinated with counsel to ensure the Act’s requirements are satisfied. Clause Language Contract Work Hours and Safety Standards (1) Overtime requirements - No contractor or subcontractor contracting for any part of the contract work which may require or involve the employment of laborers or mechanics shall require or permit any such laborer or mechanic in any workweek in which he or she is employed on such work to work in excess of forty hours in such workweek unless such laborer or mechanic receives compensation at a rate not less than one and one-half times the basic rate of pay for all hours worked in excess of forty hours in such workweek. (2) Violation; liability for unpaid wages; liquidated damages - In the event of any violation of the clause set forth in paragraph (1) of this section the contractor and any subcontractor responsible therefor shall be liable for the unpaid wages. In addition, such contractor and subcontractor shall be liable to the United States for liquidated damages. Such liquidated damages shall be computed with respect to each individual laborer or mechanic, including watchmen and guards, employed in violation of the clause set forth in paragraph (1) of this section, in the sum of $10 for each calendar day on which such individual was required or permitted to work in excess of the standard workweek of forty hours without payment of the overtime wages required by the clause set forth in paragraph (1) of this section. (3) Withholding for unpaid wages and liquidated damages - The (write in the name of the grantee) shall upon its own action or upon written request of an authorized representative of the Department of Labor withhold or cause to be withheld, from any moneys payable on account of work performed by the contractor or subcontractor under any such contract or any other Federal contract with the same prime contractor, or any other federally-assisted contract subject to the Contract Work Hours and Safety Standards Act, which is held by the same prime contractor, such sums as may be determined to be necessary to satisfy any liabilities of such contractor or subcontractor for unpaid wages and liquidated damages as provided in the clause set forth in paragraph (2) of this section. (4) Subcontracts - The contractor or subcontractor shall insert in any subcontracts the clauses set forth in paragraphs (1) through (4) of this section and also a clause requiring the subcontractors to include these clauses in any lower tier subcontracts. The prime contractor shall be responsible for compliance by any subcontractor or lower tier subcontractor with the clauses set forth in paragraphs (1) through (4) of this section.

EQUAL EMPLOYMENT OPPORTUNITY

41 CFR §60-1.4

Applicability to Contracts: Applicable to all contracts except micro-purchases (except for construction contracts over $2,000.


Flow Down Requirement: Not required by statute or regulation for either primary contractors or subcontractors, this concept should flow down to all levels to clarify, to all parties to the contract, that the Federal Government does not have contractual liability to third parties, absent specific written consent.

Model Clause/Language: Federal Requirements and Guidance. The Recipient agrees to prohibit, and assures that each Third Party Participant will prohibit, discrimination on the basis of race, color, religion, sex, or national origin, and:

(a) Comply with Title VII of the Civil Rights Act of 1964, as amended, 42 U.S.C. § 2000e et seq., (b) Facilitate compliance with Executive Order 11246, “Equal Employment Opportunity,” as

amended by Executive Order 11375, “Amending Executive Order 11246, Relating to Equal Employment Opportunity,” 42 U.S.C. § 2000e note, and as further amended by Executive Order 13672, “Further Amendments to Executive Order 11478, Equal Employment Opportunity in the Federal Government, and Executive Order 11246, Equal Employment Opportunity,” July 21, 2014,

(c) Comply with Federal transit law, specifically 49 U.S.C. § 5332, as provided in section 13.a of this Master Agreement, and

(d) Follow Federal guidance pertaining to Equal Employment Opportunity laws and regulations, and prohibitions against discrimination on the basis of disability,

Specifics. The Recipient agrees: (a) Prohibited Discrimination. As provided by Executive Order 11246, as amended, and as

specified by U.S. Department of Labor regulations, to ensure that applicants for employment are employed and employees are treated during employment without discrimination on the basis of their: 1. Race, 2. Color, 3. Religion, 4. National origin, 5. Disability, 6 . Age, 7 . Sexual origin, 8. Gender identity, or 9. Status as a parent, and

(b) Affirmative Action. Take affirmative action that includes, but is not limited to: 1. Recruitment advertising, recruitment, and employment, 2. Rates of pay and other forms of compensation, 3. Selection for training, including apprenticeship, and upgrading, and 4. Transfers, demotions, layoffs, and terminations, but (c) Indian Tribe. Title VII of the Civil Rights Act of 1964, as amended, exempts Indian Tribes

under the definition of “Employer,” and Equal Employment Opportunity Requirements for Construction Activities. In addition to the foregoing, when undertaking “construction” as recognized by the U.S. Department of Labor (U.S. DOL), the Recipient agrees to comply, and assures that each Third Party Participant will comply, with:

(a) U.S. DOL regulations, “Office of Federal Contract Compliance Programs, Equal Employment Opportunity, Department of Labor,” 41 C.F.R. chapter 60, and

(b) Executive Order 11246, “Equal Employment Opportunity,” as amended by Executive Order 11375, “Amending Executive Order 11246, Relating to Equal Employment Opportunity,” 42 U.S.C. § 2000e note.

NO GOVERNMENT OBLIGATION TO THIRD PARTIES

Applicability to Contracts: Applicable to all contracts


Flow Down Requirement: Not required by statute or regulation for either primary contractors or subcontractors, this concept should flow down to all levels to clarify, to all parties to the contract, that the Federal Government does not have contractual liability to third parties, absent specific written consent.

Model Clause/Language: While no specific language is required, FTA has developed the following language.

No Obligation by the Federal Government.

(1) The Purchaser and Contractor acknowledge and agree that, notwithstanding any concurrence by the Federal Government in or approval of the solicitation or award of the underlying contract, absent the express written consent by the Federal Government, the Federal Government is not a party to this contract and shall not be subject to any obligations or liabilities to the Purchaser, Contractor, or any other party (whether or not a party to that contract) pertaining to any matter resulting from the underlying contract.

(2) The Contractor agrees to include the above clause in each subcontract financed in whole or in part with Federal assistance provided by FTA. It is further agreed that the clause shall not be modified, except to identify the subcontractor who will be subject to its provisions.

PROGRAM FRAUD AND FALSE OR FRAUDULENT STATEMENTS AND RELATED ACTS

31 U.S.C. 3801 et seq. 49 CFR Part 31 18 U.S.C. 1001

49 U.S.C. 5307

Applicability to Contracts: These requirements are applicable to all contracts.


Flow Down Requirement: These requirements flow down to contractors and subcontractors who make, present, or submit covered claims and statements.

Model Clause/Language: These requirements have no specified language, so FTA proffers the following language.

Program Fraud and False or Fraudulent Statements or Related Acts.

(1) The Contractor acknowledges that the provisions of the Program Fraud Civil Remedies Act of 1986, as amended, 31 U.S.C. § § 3801 et seq . and U.S. DOT regulations, "Program Fraud Civil Remedies," 49 C.F.R. Part 31, apply to its actions pertaining to this Project. Upon execution of the underlying contract, the Contractor certifies or affirms the truthfulness and accuracy of any statement it has made, it makes, it may make, or causes to be made, pertaining to the underlying contract or the FTA assisted project for which this contract work is being performed. In addition to other penalties that may be applicable, the Contractor further acknowledges that if it makes, or causes to be made, a false, fictitious, or fraudulent claim, statement, submission, or certification, the Federal Government reserves the right to impose the penalties of the Program Fraud Civil Remedies Act of 1986 on the Contractor to the extent the Federal Government deems appropriate.

(2) The Contractor also acknowledges that if it makes, or causes to be made, a false, fictitious, or fraudulent claim, statement, submission, or certification to the Federal Government under a contract connected with a project that is financed in whole or in part with Federal assistance originally awarded by FTA under the authority of 49 U.S.C. § 5307, the Government reserves the right to impose the penalties of 18 U.S.C. § 1001 and 49 U.S.C. § 5307(n)(1) on the Contractor, to the extent the Federal Government deems appropriate.

(3) The Contractor agrees to include the above two clauses in each subcontract financed in whole or in part with Federal assistance provided by FTA. It is further agreed that the clauses shall not be modified, except to identify the subcontractor who will be subject to the provisions.

TERMINATION

2 CFR Part 1201 2 CFR 200

FTA Circular 4220.1F

Applicability to Contracts: All contracts (with the exception of contracts with nonprofit organizations and institutions of higher education,) in excess of $10,000 shall contain suitable provisions for termination by the grantee including the manner by which it will be affected and the basis for settlement. (For contracts with nonprofit organizations and institutions of higher education the threshold is $250,000.) In addition, such contracts shall describe conditions under which the contract may be terminated for default as well as conditions where the contract may be terminated because of circumstances beyond the control of the contractor.

Flow Down Requirement: The termination requirements flow down to all contracts in excess of $10,000, with the exception of contracts with nonprofit organizations and institutions of higher learning.

Model Clause/Language: FTA does not prescribe the form or content of such clauses. The following are suggestions of clauses to be used in different types of contracts:

a. Termination for Convenience (General Provision) The (Recipient) may terminate this contract, in whole or in part, at any time by written notice to the Contractor when it is in the Government's best interest. The Contractor shall be paid its costs, including contract close-out costs, and profit on work performed up to the time of termination. The Contractor shall promptly submit its termination claim to (Recipient) to be paid the Contractor. If the Contractor has any property in its possession belonging to the (Recipient), the Contractor will account for the same, and dispose of it in the manner the (Recipient) directs.

b. Termination for Default [Breach or Cause] (General Provision) If the Contractor does not deliver supplies in accordance with the contract delivery schedule, or, if the contract is for services, the Contractor fails to perform in the manner called for in the contract, or if the Contractor fails to comply with any other provisions of the contract, the (Recipient) may terminate this contract for default. Termination shall be affected by serving a notice of termination on the contractor setting forth the manner in which the Contractor is in default. The contractor will only be paid the contract price for supplies delivered and accepted, or services performed in accordance with the manner of performance set forth in the contract.

If it is later determined by the (Recipient) that the Contractor had an excusable reason for not performing, such as a strike, fire, or flood, events which are not the fault of or are beyond the control of the Contractor, the (Recipient), after setting up a new delivery of performance schedule, may allow the Contractor to continue work, or treat the termination as a termination for convenience.

c. Opportunity to Cure (General Provision) The (Recipient) in its sole discretion may, in the case of a termination for breach or default, allow the Contractor [an appropriately short period of time] in which to cure the defect. In such case, the notice of termination will state the time period in which cure is permitted and other appropriate conditions.

If Contractor fails to remedy to (Recipient)'s satisfaction the breach or default of any of the terms, covenants, or conditions of this Contract within [ten (10) days] after receipt by Contractor of written notice from (Recipient) setting forth the nature of said breach or default, (Recipient) shall have the right to terminate the Contract without any further obligation to Contractor. Any such termination for default shall not in any way operate to preclude (Recipient) from also pursuing all available remedies against Contractor and its sureties for said breach or default.

d. Waiver of Remedies for any Breach In the event that (Recipient) elects to waive its remedies for any breach by Contractor of any covenant, term or condition of this Contract, such waiver by (Recipient) shall not limit (Recipient)'s remedies for any succeeding breach of that or of any other term, covenant, or condition of this Contract.

e. Termination for Convenience (Professional or Transit Service Contracts) The (Recipient), by written notice, may terminate this contract, in whole or in part, when it is in the Government's interest. If this contract is terminated, the Recipient shall be liable only for payment under the payment provisions of this contract for services rendered before the effective date of termination.

f. Termination for Default (Supplies and Service) If the Contractor fails to deliver supplies or to perform the services within the time specified in this contract or any extension or if the Contractor fails to comply with any other provisions of this contract, the (Recipient) may terminate this contract for default. The (Recipient) shall terminate by delivering to the Contractor a Notice of Termination specifying the nature of the default. The Contractor will only be paid the contract price for supplies delivered and accepted, or services performed in accordance with the manner or performance set forth in this contract.

If, after termination for failure to fulfill contract obligations, it is determined that the Contractor was not in default, the rights and obligations of the parties shall be the same as if the termination had been issued for the convenience of the Recipient.

g. Termination for Default (Transportation Services) If the Contractor fails to pick up the commodities or to perform the services, including delivery services, within the time specified in this contract or any extension or if the Contractor fails to comply with any other provisions of this contract, the (Recipient) may terminate this contract for default. The (Recipient) shall terminate by delivering to the Contractor a Notice of Termination specifying the nature of default. The Contractor will only be paid the contract price for services performed in accordance with the manner of performance set forth in this contract.

If this contract is terminated while the Contractor has possession of Recipient goods, the Contractor shall, upon direction of the (Recipient), protect and preserve the goods until surrendered to the Recipient or its agent. The Contractor and (Recipient) shall agree on payment for the preservation and protection of goods. Failure to agree on an amount will be resolved under the Dispute clause.

If, after termination for failure to fulfill contract obligations, it is determined that the Contractor was not in default, the rights and obligations of the parties shall be the same as if the termination had been issued for the convenience of the (Recipient).

h. Termination for Default (Construction) If the Contractor refuses or fails to prosecute the work or any separable part, with the diligence that will insure its completion within the time specified in this contract or any extension or fails to complete the work within this time, or if the Contractor fails to comply with any other provisions of this contract, the (Recipient) may terminate this contract for default. The (Recipient) shall terminate by delivering to the Contractor a Notice of Termination specifying the nature of the default. In this event, the Recipient may take over the work and compete it by contract or otherwise, and may take possession of and use any materials, appliances, and plant on the work site necessary for completing the work. The Contractor and its sureties shall be liable for any damage to the Recipient resulting from the Contractor's refusal or failure to complete the work within specified time, whether or not the Contractor's right to proceed with the work is terminated. This liability includes any increased costs incurred by the Recipient in completing the work.

The Contractor's right to proceed shall not be terminated nor the Contractor charged with damages under this clause if-

1. The delay in completing the work arises from unforeseeable causes beyond the control and without the fault or negligence of the Contractor. Examples of such causes include: acts of God, acts of the Recipient, acts of another Contractor in the performance of a contract with the Recipient, epidemics, quarantine restrictions, strikes, freight embargoes; and

2. The contractor, within [10] days from the beginning of any delay, notifies the (Recipient) in writing of the causes of delay. If in the judgment of the (Recipient), the delay is excusable, the time for completing the work shall be extended. The judgment of the (Recipient) shall be final and conclusive on the parties, but subject to appeal under the Disputes clauses.

If, after termination of the Contractor's right to proceed, it is determined that the Contractor was not in default, or that the delay was excusable, the rights and obligations of the parties will be the same as if the termination had been issued for the convenience of the Recipient.

i. Termination for Convenience or Default (Architect and Engineering) The (Recipient) may terminate this contract in whole or in part, for the Recipient's convenience or because of the failure of the Contractor to fulfill the contract obligations. The (Recipient) shall terminate by delivering to the Contractor a Notice of Termination specifying the nature, extent, and effective date of the termination. Upon receipt of the notice, the Contractor shall (1) immediately discontinue all services affected (unless the notice directs otherwise), and (2) deliver to the Contracting Officer all data, drawings, specifications, reports, estimates, summaries, and other information and materials accumulated in performing this contract, whether completed or in process.

If the termination is for the convenience of the Recipient, the Contracting Officer shall make an equitable adjustment in the contract price but shall allow no anticipated profit on unperformed services.

If the termination is for failure of the Contractor to fulfill the contract obligations, the Recipient may complete the work by contact or otherwise and the Contractor shall be liable for any additional cost incurred by the Recipient.

If, after termination for failure to fulfill contract obligations, it is determined that the Contractor was not in default, the rights and obligations of the parties shall be the same as if the termination had been issued for the convenience of the Recipient.

j. Termination for Convenience of Default (Cost-Type Contracts) The (Recipient) may terminate this contract, or any portion of it, by serving a notice or termination on the Contractor. The notice shall state whether the termination is for convenience of the (Recipient) or for the default of the Contractor. If the termination is for default, the notice shall state the manner in which the contractor has failed to perform the requirements of the contract. The Contractor shall account for any property in its possession paid for from funds received from the (Recipient), or property supplied to the Contractor by the (Recipient). If the termination is for default, the (Recipient) may fix the fee, if the contract provides for a fee, to be paid the contractor in proportion to the value, if any, of work performed up to the time of termination. The Contractor shall promptly submit its termination claim to the (Recipient) and the parties shall negotiate the termination settlement to be paid the Contractor.

If the termination is for the convenience of the (Recipient), the Contractor shall be paid its contract close-out costs, and a fee, if the contract provided for payment of a fee, in proportion to the work performed up to the time of termination.

If, after serving a notice of termination for default, the (Recipient) determines that the Contractor has an excusable reason for not performing, such as strike, fire, flood, events which are not the fault of and are beyond the control of the contractor, the (Recipient), after setting up a new work schedule, may allow the Contractor to continue work, or treat the termination as a termination for convenience.

GOVERNMENT-WIDE DEBARMENT AND SUSPENSION

2 CFR part 180 2 CFR part 1200

2 CFR § 200.213

2 CFR part 200 Appendix II (I) Executive Order 12549 Executive Order 12689

Background and Applicability A contract award (of any tier) in an amount expected to equal or exceed $25,000 or a contract award at any tier for a federally required audit (irrespective of the contract amount) must not be made to parties listed on the government-wide exclusions in the System for Award Management (SAM), in accordance with the OMB guidelines at 2 C.F.R. part 180. The Excluded Parties List System in SAM contains the names of parties debarred, suspended, or otherwise excluded by agencies, as well as parties declared ineligible under statutory or regulatory authority other than Executive Order 12549. Recipients, contractors, and subcontractors (at any level) that enter into covered transactions are required to verify that the entity (as well as its principals and affiliates) with which they propose to contract or subcontract is not excluded or disqualified. This is done by: (a) checking the SAM exclusions; (b) collecting a certification from that person; or (c) adding a clause or condition to the contract or subcontract. Flow Down Recipients, contractors, and subcontractors who enter into covered transactions with a participant at the next lower level, must require that participant to: (a) comply with subpart C of 2 C.F.R. part 180, as supplemented by 2 C.F.R. part 1200; and (b) pass the requirement to comply with subpart C of 2 C.F.R. part 180 to each person with whom the participant enters into a covered transaction at the next lower tier.

Debarment, Suspension, Ineligibility and Voluntary Exclusion The Contractor shall comply and facilitate compliance with U.S. DOT regulations, “Nonprocurement Suspension and Debarment,” 2 C.F.R. part 1200, which adopts and supplements the U.S. Office of Management and Budget (U.S. OMB) “Guidelines to Agencies on Governmentwide Debarment and Suspension (Nonprocurement),” 2 C.F.R. part 180. These provisions apply to each contract at any tier of $25,000 or more, and to each contract at any tier for a federally required audit (irrespective of the contract amount), and to each contract at any tier that must be approved by an FTA official irrespective of the contract amount. As such, the Contractor shall verify that its principals, affiliates, and subcontractors are eligible to participate in this federally funded contract and are not presently declared by any Federal department or agency to be:

a) Debarred from participation in any federally assisted Award;

b) Suspended from participation in any federally assisted Award;

c) Proposed for debarment from participation in any federally assisted Award;

d) Declared ineligible to participate in any federally assisted Award;

e) Voluntarily excluded from participation in any federally assisted Award; or

f) Disqualified from participation in ay federally assisted Award.

By signing and submitting its bid or proposal, the bidder or proposer certifies as follows: The certification in this clause is a material representation of fact relied upon by the Recipeint. If it is later determined by the Recipient that the bidder or proposer knowingly rendered an erroneous certification, in addition to remedies available to the Recipient, the Federal Government may pursue available remedies, including but not limited to suspension and/or debarment. The bidder or proposer agrees to comply with the requirements of 2 C.F.R. part 180, subpart C, as supplemented by 2 C.F.R. part 1200, while this offer is valid and throughout the period of any contract that may arise from this offer. The bidder or proposer further agrees to include a provision requiring such compliance in its lower tier covered transactions.

Date:_________________________________________________________________________

Signature:_____________________________________________________________________

Company Name:________________________________________________________________

Title:__________________________________________________________________________

PRIVACY ACT

5 U.S.C. 552

Applicability to Contracts: When a grantee maintains files on drug and alcohol enforcement activities for FTA, and those files are organized so that information could be retrieved by personal identifier, the Privacy Act requirements apply to all contracts.


Flow Down Requirement: The Federal Privacy Act requirements flow down to each third party contractor and their contracts at every tier.

Model Clause/Language: The text of the following clause has not been mandated by statute or specific regulation, but has been developed by FTA.

Contracts Involving Federal Privacy Act Requirements - The following requirements apply to the Contractor and its employees that administer any system of records on behalf of the Federal Government under any contract:

(1) The Contractor agrees to comply with, and assures the compliance of its employees with, the information restrictions and other applicable requirements of the Privacy Act of 1974, 5 U.S.C. § 552a. Among other things, the Contractor agrees to obtain the express consent of the Federal Government before the Contractor or its employees operate a system of records on behalf of the Federal Government. The Contractor understands that the requirements of the Privacy Act, including the civil and criminal penalties for violation of that Act, apply to those individuals involved, and that failure to comply with the terms of the Privacy Act may result in termination of the underlying contract.

(2) The Contractor also agrees to include these requirements in each subcontract to administer any system of records on behalf of the Federal Government financed in whole or in part with Federal assistance provided by FTA.

CIVIL RIGHTS REQUIREMENTS

29 U.S.C. § 623, 42 U.S.C. § 2000 42 U.S.C. § 6102, 42 U.S.C. § 12112 42 U.S.C. § 12132, 49 U.S.C. § 5332

29 CFR Part 1630, 41 CFR Parts 60 et seq.

Applicability to Contracts: The Civil Rights Requirements apply to all contracts.


Flow Down Requirement: The Civil Rights requirements flow down to all third party contractors and their contracts at every tier.

Model Clause/Language: The following clause was predicated on language contained at 49 CFR Part 19, Appendix A, but FTA has shortened the lengthy text.

Civil Rights - The following requirements apply to the underlying contract:

The following requirements apply to the underlying contract:

(1) Nondiscrimination - In accordance with Title VI of the Civil Rights Act, as amended, 42 U.S.C. § 2000d, section 303 of the Age Discrimination Act of 1975, as amended, 42 U.S.C. § 6102, section 202 of the Americans with Disabilities Act of 1990, 42 U.S.C. § 12132, and Federal transit law at 49 U.S.C. § 5332, the Contractor agrees that it will not discriminate against any employee or applicant for employment because of race, color, creed, national origin, sex, age, or disability. In addition, the Contractor agrees to comply with applicable Federal implementing regulations and other implementing requirements FTA may issue.

(2) Equal Employment Opportunity - The following equal employment opportunity requirements apply to the underlying contract:

(a) Race, Color, Creed, National Origin, Sex - In accordance with Title VII of the Civil Rights Act, as amended, 42 U.S.C. § 2000e, and Federal transit laws at 49 U.S.C. § 5332, the Contractor agrees to comply with all applicable equal employment opportunity requirements of U.S. Department of Labor (U.S. DOL) regulations, "Office of Federal Contract Compliance Programs, Equal Employment Opportunity, Department of Labor," 41 C.F.R. Parts 60 et seq ., (which implement Executive Order No. 11246, "Equal Employment Opportunity," as amended by Executive Order No. 11375, "Amending Executive Order 11246 Relating to Equal Employment Opportunity," 42 U.S.C. § 2000e note), and with any applicable Federal statutes, executive orders, regulations, and Federal policies that may in the future affect construction activities undertaken in the course of the Project. The Contractor agrees to take affirmative action to ensure that applicants are employed, and that employees are treated during employment, without regard to their race, color, creed, national origin, sex, or age. Such action shall include, but not be limited to, the following: employment, upgrading, demotion or transfer, recruitment or recruitment advertising, layoff or termination; rates of pay or other forms of compensation; and selection for training, including apprenticeship. In addition, the Contractor agrees to comply with any implementing requirements FTA may issue.

(b) Age - In accordance with section 4 of the Age Discrimination in Employment Act of 1967, as amended, 29 U.S.C. § § 623 and Federal transit law at 49 U.S.C. § 5332, the Contractor agrees to refrain from discrimination against present and prospective employees for reason of age. In addition, the Contractor agrees to comply with any implementing requirements FTA may issue.

(c) Disabilities - In accordance with section 102 of the Americans with Disabilities Act, as amended, 42 U.S.C. § 12112, the Contractor agrees that it will comply with the requirements of U.S. Equal Employment Opportunity Commission, "Regulations to Implement the Equal Employment Provisions of the Americans with Disabilities Act," 29 C.F.R. Part 1630, pertaining to employment of persons with disabilities. In addition, the Contractor agrees to comply with any implementing requirements FTA may issue.

(3) The Contractor also agrees to include these requirements in each subcontract financed in whole or in part with Federal assistance provided by FTA, modified only if necessary to identify the affected parties.

BREACHES AND DISPUTE RESOLUTION

2 CFR Part 1201 FTA Circular 4220.1F

Applicability to Contracts: All contracts in excess of $250,000 shall contain provisions or conditions which will allow for administrative, contractual, or legal remedies in instances where contractors violate or breach contract terms, and provide for such sanctions and penalties as may be appropriate. This may include provisions for bonding, penalties for late or inadequate performance, retained earnings, liquidated damages or other appropriate measures.

Flow Down: The Breaches and Dispute Resolutions requirements flow down to all tiers.

Model Clauses/Language: FTA does not prescribe the form or content of such provisions. What provisions are developed will depend on the circumstances and the type of contract. Recipients should consult legal counsel in developing appropriate clauses. The following clauses are examples of provisions from various FTA third party contracts.

Disputes - Disputes arising in the performance of this Contract which are not resolved by agreement of the parties shall be decided in writing by the authorized representative of the Recipient. This decision shall be final and conclusive unless within [ten (10)] days from the date of receipt of its copy, the Contractor mails or otherwise furnishes a written appeal to the Recipient. In connection with any such appeal, the Contractor shall be afforded an opportunity to be heard and to offer evidence in support of its position. The decision of the Recipient shall be binding upon the Contractor and the Contractor shall abide be the decision.

Performance During Dispute - Unless otherwise directed by (Recipient), Contractor shall continue performance under this Contract while matters in dispute are being resolved.

Claims for Damages - Should either party to the Contract suffer injury or damage to person or property because of any act or omission of the party or of any of his employees, agents or others for whose acts

he is legally liable, a claim for damages therefor shall be made in writing to such other party within a reasonable time after the first observance of such injury of damage.

Remedies - Unless this contract provides otherwise, all claims, counterclaims, disputes and other matters in question between the (Recipient) and the Contractor arising out of or relating to this agreement or its breach will be decided by arbitration if the parties mutually agree, or in a court of competent jurisdiction within the State in which the (Recipient) is located.

Rights and Remedies - The duties and obligations imposed by the Contract Documents and the rights and remedies available thereunder shall be in addition to and not a limitation of any duties, obligations, rights and remedies otherwise imposed or available by law. No action or failure to act by the (Recipient), (Architect) or Contractor shall constitute a waiver of any right or duty afforded any of them under the Contract, nor shall any such action or failure to act constitute an approval of or acquiescence in any breach thereunder, except as may be specifically agreed in writing.

PATENT AND RIGHTS IN DATA

2 CFR Part 1201

37 CFR Part 401 49 CFR Part 19

Applicability to Contracts: Patent and rights in data requirements for federally assisted projects ONLY apply to research projects in which FTA finances the purpose of the grant is to finance the development of a product or information. These patent and data rights requirements do not apply to capital projects or operating projects, even though a small portion of the sales price may cover the cost of product development or writing the user's manual.


Flow Down Requirement: The Patent and Rights in Data requirements apply to all contractors and their contracts at every tier.

Model Clause/Language: The FTA patent clause is substantially similar to the text of 49 C.F.R. Part 19, Appendix A, Section 5, but the rights in data clause reflects FTA objectives. For patent rights, FTA is governed by Federal law and regulation. For data rights, the text on copyrights is insufficient to meet FTA's purposes for awarding research grants. This model clause, with larger rights as a standard, is proposed with the understanding that this standard could be modified to FTA's needs.

CONTRACTS INVOLVING EXPERIMENTAL, DEVELOPMENTAL, OR RESEARCH WORK.

A. Rights in Data - This following requirements apply to each contract involving experimental, developmental or research work:

(1) The term "subject data" used in this clause means recorded information, whether or not copyrighted, that is delivered or specified to be delivered under the contract. The term includes graphic or pictorial delineation in media such as drawings or photographs; text in specifications or related performance or design-type documents; machine forms such as punched cards, magnetic tape, or computer memory printouts; and information retained in computer memory. Examples include, but are not limited to: computer software, engineering drawings and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog item identifications, and related information. The term "subject data" does not include financial reports, cost analyses, and similar information incidental to contract administration.

(2) The following restrictions apply to all subject data first produced in the performance of the contract to which this Attachment has been added:

(a) Except for its own internal use, the Purchaser or Contractor may not publish or reproduce subject data in whole or in part, or in any manner or form, nor may the Purchaser or Contractor authorize others to do so, without the written consent of the Federal Government, until such time as the Federal Government may have either released or approved the release of such data to the public; this restriction on publication, however, does not apply to any contract with an academic institution.

(b) In accordance with 49 C.F.R. § 18.34 and 49 C.F.R. § 19.36, the Federal Government reserves a royalty-free, non-exclusive and irrevocable license to reproduce, publish, or otherwise use, and to

authorize others to use, for "Federal Government purposes," any subject data or copyright described in subsections (2)(b)1 and (2)(b)2 of this clause below. As used in the previous sentence, "for Federal Government purposes," means use only for the direct purposes of the Federal Government. Without the copyright owner's consent, the Federal Government may not extend its Federal license to any other party.

1. Any subject data developed under that contract, whether or not a copyright has been obtained; and

2. Any rights of copyright purchased by the Purchaser or Contractor using Federal assistance in whole or in part provided by FTA.

(c) When FTA awards Federal assistance for experimental, developmental, or research work, it is FTA's general intention to increase transportation knowledge available to the public, rather than to restrict the benefits resulting from the work to participants in that work. Therefore, unless FTA determines otherwise, the Purchaser and the Contractor performing experimental, developmental, or research work required by the underlying contract to which this Attachment is added agrees to permit FTA to make available to the public, either FTA's license in the copyright to any subject data developed in the course of that contract, or a copy of the subject data first produced under the contract for which a copyright has not been obtained. If the experimental, developmental, or research work, which is the subject of the underlying contract, is not completed for any reason whatsoever, all data developed under that contract shall become subject data as defined in subsection (a) of this clause and shall be delivered as the Federal Government may direct. This subsection (c) , however, does not apply to adaptations of automatic data processing equipment or programs for the Purchaser or Contractor's use whose costs are financed in whole or in part with Federal assistance provided by FTA for transportation capital projects.

(d) Unless prohibited by state law, upon request by the Federal Government, the Purchaser and the Contractor agree to indemnify, save, and hold harmless the Federal Government, its officers, agents, and employees acting within the scope of their official duties against any liability, including costs and expenses, resulting from any willful or intentional violation by the Purchaser or Contractor of proprietary rights, copyrights, or right of privacy, arising out of the publication, translation, reproduction, delivery, use, or disposition of any data furnished under that contract. Neither the Purchaser nor the Contractor shall be required to indemnify the Federal Government for any such liability arising out of the wrongful act of any employee, official, or agents of the Federal Government.

(e) Nothing contained in this clause on rights in data shall imply a license to the Federal Government under any patent or be construed as affecting the scope of any license or other right otherwise granted to the Federal Government under any patent.

(f) Data developed by the Purchaser or Contractor and financed entirely without using Federal assistance provided by the Federal Government that has been incorporated into work required by the underlying contract to which this Attachment has been added is exempt from the requirements of subsections (b), (c), and (d) of this clause , provided that the Purchaser or Contractor identifies that data in writing at the time of delivery of the contract work.

(g) Unless FTA determines otherwise, the Contractor agrees to include these requirements in each subcontract for experimental, developmental, or research work financed in whole or in part with Federal assistance provided by FTA.

(3) Unless the Federal Government later makes a contrary determination in writing, irrespective of the Contractor's status (i.e. , a large business, small business, state government or state instrumentality, local government, nonprofit organization, institution of higher education, individual, etc.), the Purchaser and the Contractor agree to take the necessary actions to provide, through FTA, those rights in that invention due the Federal Government as described in

U.S. Department of Commerce regulations, "Rights to Inventions Made by Nonprofit Organizations and Small Business Firms Under Government Grants, Contracts and Cooperative Agreements," 37 C.F.R. Part 401.

(4) The Contractor also agrees to include these requirements in each subcontract for experimental, developmental, or research work financed in whole or in part with Federal assistance provided by FTA.

B. Patent Rights - This following requirements apply to each contract involving experimental, developmental, or research work:

(1) General - If any invention, improvement, or discovery is conceived or first actually reduced to practice in the course of or under the contract to which this Attachment has been added, and that invention, improvement, or discovery is patentable under the laws of the United States of America or any foreign country, the Purchaser and Contractor agree to take actions necessary to provide immediate notice and a detailed report to the party at a higher tier until FTA is ultimately notified.

(2) Unless the Federal Government later makes a contrary determination in writing, irrespective of the Contractor's status (a large business, small business, state government or state instrumentality, local government, nonprofit organization, institution of higher education, individual), the Purchaser and the Contractor agree to take the necessary actions to provide, through FTA, those rights in that invention due the Federal Government as described in U.S. Department of Commerce regulations, "Rights to Inventions Made by Nonprofit Organizations and Small Business Firms Under Government Grants, Contracts and Cooperative Agreements," 37 C.F.R. Part 401.

(3) The Contractor also agrees to include the requirements of this clause in each subcontract for experimental, developmental, or research work financed in whole or in part with Federal assistance provided by FTA.

TRANSIT EMPLOYEE PROTECTIVE ARRANGEMENTS

49 U.S.C. § 5310, § 5311, and § 5333 29 CFR Part 215

Applicability to Contracts: The Transit Employee Protective Provisions apply to each contract for transit operations performed by employees of a Contractor recognized by FTA to be a transit operator. (Because transit operations involve many activities apart from directly driving or operating transit vehicles, FTA determines which activities constitute transit "operations" for purposes of this clause.)

Applicability to Micro-Purchases: Micro-purchases are defined as those purchases under $10,000. These requirements do not apply to micro-purchases, except for construction contracts over $2,000.

Flow Down Requirement: These provisions are applicable to all contracts and subcontracts at every tier.

Model Clause/Language: Since no mandatory language is specified, FTA had developed the following language. Transit Employee Protective Provisions. (1) The Contractor agrees to comply with applicable transit employee protective requirements as follows:

(a) General Transit Employee Protective Requirements - To the extent that FTA determines that transit operations are involved, the Contractor agrees to carry out the transit operations work on the underlying contract in compliance with terms and conditions determined by the U.S. Secretary of Labor to be fair and equitable to protect the interests of employees employed under this contract and to meet the employee protective requirements of 49 U.S.C. A 5333(b), and U.S. DOL guidelines at 29 C.F.R. Part 215, and any amendments thereto. These terms and conditions are identified in the letter of certification from the U.S. DOL to FTA applicable to the FTA Recipient's project from which Federal assistance is provided to support work on the underlying contract. The Contractor agrees to carry out that work in compliance with the conditions stated in that U.S. DOL letter. The requirements of this subsection (1), however, do not apply to any contract financed with Federal assistance provided by FTA either for projects for elderly individuals and individuals with disabilities authorized by 49 U.S.C. § 5310(a)(2), or for projects for nonurbanized areas authorized by 49 U.S.C. § 5311. Alternate provisions for those projects are set forth in subsections (b) and (c) of this clause.

(b) Transit Employee Protective Requirements for Projects Authorized by 49 U.S.C.

§ 5310(a)(2) for Elderly Individuals and Individuals with Disabilities

- If the contract involves transit operations financed in whole or in part with Federal assistance authorized by 49 U.S.C. § 5310(a)(2), and if the U.S. Secretary of Transportation has determined or determines in the future that the employee protective requirements of 49 U.S.C. § 5333(b) are necessary or appropriate for the state and the public body subrecipient for which work is performed on the underlying contract, the Contractor agrees to carry out the Project in compliance with the terms and conditions determined by the U.S. Secretary of Labor to meet the requirements of 49 U.S.C. § 5333(b), U.S. DOL guidelines at 29 C.F.R. Part 215, and any amendments thereto. These terms and conditions are identified in the U.S. DOL's letter of certification to FTA, the date of which is set forth Grant Agreement or Cooperative Agreement with the state. The Contractor agrees to perform transit

operations in connection with the underlying contract in compliance with the conditions stated in that U.S. DOL letter.

(c) Transit Employee Protective Requirements for Projects Authorized by 49 U.S.C.

§ 5311 in Nonurbanized Areas

- If the contract involves transit operations financed in whole or in part with Federal assistance authorized by 49 U.S.C. § 5311, the Contractor agrees to comply with the terms and conditions of the Special Warranty for the Nonurbanized Area Program agreed to by the U.S. Secretaries of Transportation and Labor, dated May 31, 1979, and the procedures implemented by U.S. DOL or any revision thereto.

(2) The Contractor also agrees to include any applicable requirements in each subcontract involving transit operations financed in whole or in part with Federal assistance provided by FTA.

DISADVANTAGED BUSINESS ENTERPRISE (DBE)

49 CFR Part 26

Applicability to Contracts: The Disadvantaged Business Enterprise (DBE) program provides guidance to grantees on the use of overall and contract goals, requirement to include DBE provisions in subcontracts, evaluating DBE participation where specific contract goals have been set, reporting requirements, and replacement of DBE subcontractors. Additionally, the DBE program dictates payment terms and conditions (including limitations on retainage) applicable to all subcontractors regardless of whether they are DBE firms or not. The DBE program applies to all DOT- assisted contracting activities. A formal clause such as that below must be included in all contracts and subcontracts above the micro-purchase level ($10,000 except for construction contracts over $2,000). Clause Language Each contract the Recipient signs with a contractor (and each subcontract the prime contractor signs with a subcontractor) must include the following Federal Clause language:

a. This contract is subject to the requirements of Title 49, Code of Federal Regulations, Part 26, Participation by Disadvantaged Business Enterprises in Department of Transportation Financial Assistance Programs. The national goal for participation of Disadvantaged Business Enterprises (DBE) is 10%. WisDOT has established a 1.85% transit DBE goal with a 0.22% race conscious, 1.63% race neutral split for FFY 2020-2022. A separate contract specific goal has/has not been established for this procurement. b. The contractor shall not discriminate on the basis of race, color, national origin, or sex in the performance of this contract. The contractor shall carry out applicable requirements of 49 CFR Part 26 in the award and administration of this DOT-assisted contract. Failure by the contractor to carry out these requirements is a material breach of this contract, which may result in the termination of this contract or such other remedy as the Recipient deems appropriate, which may include, but is not limited to:

1) Withholding monthly progress payments 2) Assessing sanctions 3) Liquidated damages, and/or 4) Disqualifying the contractor from future bidding as non-responsible

c. The contractor shall utilize the specific DBEs listed to perform the work and supply the materials for

which each is listed in its written documentation of its contract commitment to the Recipient unless

the contractor obtains written consent from the Recipient.

d. The contractor shall not be entitled to any payment for work or material unless it is performed or

supplied by the DBEs as listed in its written documentation of its commitment to the Recipient unless

the contractor obtains written consent from the Recipient.

e. The contractor will be required to report its DBE participation obtained throughout the period of

performance.

f. Prompt Payment - The contractor is required to pay its subcontractors performing work related to

this contract for satisfactory performance of that work no later than 10 calendar days after the

contractor’s receipt of payment for that work from the Recipient. In addition, the contractor is required

to return any retainage payments to those subcontractors within 10 calendar days after incremental

acceptance of the subcontractor’s work by the Recipient and contractor’s receipt of the partial

g. The contractor shall not terminate a DBE subcontractor listed in its written documentation of its

commitment to the Recipient to use a DBE subcontractor (or an approved substitute DBE firm)

without the Recipient’s prior written consent. This includes, but is not limited to, instances in which a

prime contractor seeks to perform work originally designated for a DBE subcontractor with its own

forces or those of an affiliate, a non-DBE firm, or with another DBE firm.

h. The contractor must promptly notify the RECIPIENT whenever a DBE subcontractor performing work related to this contract is terminated or fails to complete its work and must make good faith efforts to engage another DBE subcontractor to perform at least the same amount of work.

For purposes of this paragraph, good cause includes the following circumstances:

i. The listed DBE subcontractor fails or refuses to execute a written contract. ii. The listed DBE subcontractor fails or refuses to perform the work of its subcontract in a

way consistent with normal industry standards. Provided, however, that good cause does not exist if the failure or refusal of the DBE subcontractor to perform its work on the subcontract results from the bad faith or discriminatory action of the prime contractor.

iii. The listed DBE subcontractor fails or refuses to meet the prime contractor's reasonable, nondiscriminatory bond requirements.

iv. The listed DBE subcontractor becomes bankrupt, insolvent, or exhibits credit unworthiness;

v. The listed DBE subcontractor is ineligible to work on public works projects because of suspension and debarment proceedings pursuant 2 CFR Parts 180, 215 and 1,200 or applicable state law;

vi. WisDOT determined that the listed DBE subcontractor is not a responsible contractor; vii. The listed DBE subcontractor voluntarily withdraws from the project and provides to you

written notice of its withdrawal; viii. The listed DBE is ineligible to receive DBE credit for the type of work required; ix. A DBE owner dies or becomes disabled with the result that the listed DBE contractor is

unable to complete its work on the contract; x. Other documented good cause that compels the termination of the DBE subcontractor.

Provided, that good cause does not exist if the prime contractor seeks to terminate a DBE it relied upon to obtain the contract so that the prime contractor can self-perform the work for which the DBE contractor was engaged or so that the prime contractor can substitute another DBE or non-DBE contractor after contract award.

i. The contractor may not terminate any DBE subcontractor and perform that work through its own forces or those of an affiliate without prior written consent of the RECIPIENT.

j. Before transmitting to WisDOT its request to terminate and/or substitute a DBE subcontractor, the prime contractor must give notice in writing to the DBE subcontractor, with a copy to WisDOT, of its intent to request to terminate and/or substitute, and the reason for the request.

INCORPORATION OF FEDERAL TRANSIT ADMINISTRATION (FTA) TERMS

FTA Circular 4220.1F

Applicability to Contracts: The incorporation of FTA terms applies to all contracts.


Flow Down Requirement: The incorporation of FTA terms has unlimited flow down.

Model Clause/Language: FTA has developed the following incorporation of terms language:

Incorporation of Federal Transit Administration (FTA) Terms - The preceding provisions include, in part, certain Standard Terms and Conditions required by DOT, whether or not expressly set forth in the preceding contract provisions. All contractual provisions required by DOT, as set forth in FTA Circular 4220.1F are hereby incorporated by reference. Anything to the contrary herein notwithstanding, all FTA mandated terms shall be deemed to control in the event of a conflict with other provisions contained in this Agreement. The Contractor shall not perform any act, fail to perform any act, or refuse to comply with any (name of grantee) requests which would cause (name of grantee) to be in violation of the FTA terms and conditions.

DRUG AND ALCOHOL TESTING

49 U.S.C. §5331 49 CFR Part 655

Applicability to Contracts: The Drug and Alcohol testing provisions apply to Operational Service Contracts.

Applicability to Micro-Purchases: Micro-purchases are defined as those purchases under $10,000. These requirements do not apply to micro-purchases, except for construction contracts over $2,000.

Flow Down Requirements: Anyone who performs a safety-sensitive function for the recipient or subrecipient is required to comply with FTA regulation 49 CFR 655 “Prevention of Alcohol Misuse and Prohibited Drug Use in Transit Operations” and DOT regulation, 49 CFR Part 40 “Procedures for Transportation Workplace Drug and Alcohol testing Programs”.

Explanation of Model Clause/Language

Federal regulations 49 CFR 655 includes the following elements. First, they require recipients to ensure that any entity performing a safety-sensitive function on the recipient's behalf (usually subrecipients and/or contractors) implement a complex drug and alcohol testing program that complies with 49 CFR Part 655. Second, the rules condition the receipt of certain kinds of FTA funding on the recipient's compliance with the rules; thus, the recipient is not in compliance with the rules unless every entity that performs a safety-sensitive function on the recipient's behalf is in compliance with the rules. Third, the rules do not specify how a recipient ensures that its subrecipients and/or contractors comply with them.

Explanation of Model Contract Clauses

Drug and Alcohol Testing

The contractor agrees to:

(a) Establish and implement a drug and alcohol testing program that complies with Federal Transit Administration (FTA) regulation, 49 CFR Part 655 “Prevention of Alcohol Misuse and Prohibited Drug Use in Transit Operations” and US DOT regulation, 49 CFR Part 40 “Procedures for Transportation Workplace Drug and Alcohol Testing Program”.

(b) Participate in the Drug and Alcohol Testing Consortium administered by WisDOT’s approved Third Party Administrator that complies with 49 CFR Part 655.

(c) Provide documentation and reports necessary to establish its compliance with Part 655, as amended, and permit any authorized representative of the United States Department of Transportation or its operating administrations and/or the State of Wisconsin, Department of Transportation or its authorized agents, to inspect the facilities and records associated with the

implementation of the drug and alcohol testing program as required under 49 CFR Part 655 as amended and review the testing process.

SAFE OPERATION OF MOTOR VEHICLES

23 U.S.C. part 402 Executive Order No. 13043 Executive Order No. 13513 U.S. DOT Order No. 3902.10


The Safe Operation of Motor Vehicles requirements apply to all federally funded third party contracts. In

compliance with Federal Executive Order No. 13043, “Increasing Seat Belt Use in the United States,”

April 16, 1997, 23 U.S.C. Section 402 note, FTA encourages each third party contractor to adopt and

promote on-the-job seat belt use policies and programs for its employees and other personnel that

operate company owned, rented, or personally operated vehicles, and to include this provision in each

third party subcontract involving the project. Additionally, recipients are required by FTA to include a

Distracted Driving clause that addresses distracted driving, including text messaging in each of its third

party agreements supported with Federal assistance.

Flow Down Requirements: The Safe Operation of Motor Vehicles requirements flow down to all third party

contractors at every tier.

Model Clause/Language: There is no required language for the Safe Operation of Motor Vehicles clause.

Recipients can draw on the following language for inclusion in their federally funded procurements.

Safe Operation of Motor Vehicles Requirements -

Seat Belt Use: The Contractor is encouraged to adopt and promote on-the-job seat belt use policies and

programs for its employees and other personnel that operate company-owned vehicles, company A-60

rented vehicles, or personally operated vehicles. The terms “company-owned” and “company-leased”

refer to vehicles owned or leased either by the Contractor or AGENCY.

Distracted Driving: The Contractor agrees to adopt and enforce workplace safety policies to decrease

crashes caused by distracted drivers, including policies to ban text messaging while using an electronic

device supplied by an employer, and driving a vehicle the driver owns or rents, a vehicle Contactor owns,

leases, or rents, or a privately-o wned vehicle when on official business in connection with the work

performed under this agreement.

ADA ACCESS

49 USC 531 (d)

Applicability to Contracts: The ADA Access Requirements apply to all contracts.

Applicability to Micro-Purchases: Micro-purchases are defined as those purchases under $10,000.

These requirements do not apply to micro-purchases; except for construction contracts over $2,000.

Flow Down Requirement: The ADA Access Requirements flow down to all third party contractors and

their contracts at every tier.

Model Clause/Language: ADA Access. The Americans with Disabilities Act of 1990 (ADA) prohibits

discrimination and ensures equal opportunity and access for persons with disabilities.

Access Requirements for Persons with Disabilities

Contractor shall comply with 49 USC 5301(d), stating Federal policy that the elderly and

persons with disabilities have the same rights as other persons to use mass transportation

services and facilities and that special efforts shall be made in planning and designing

those services and facilities to implement that policy. Contractor shall also comply with all

applicable requirements of Sec. 504 of the Rehabilitation Act (1973), as amended, 29 USC

794, which prohibits discrimination on the basis of handicaps, and the Americans with

Disabilities Act of 1990 (ADA), as amended, 42 USC 12101 et seq., which requires that

accessible facilities and services be made available to persons with disabilities, including

any subsequent amendments thereto.

VETERANS EMPLOYMENT

FTA Circular 4220.1F (Chapter IV) 49 USC §5325(K)

Applicability to Contracts: The Veterans Employment provisions apply to all construction contracts. Veterans Employment. Recipients and subrecipients of Federal financial assistance under this chapter shall ensure that contractors working on a capital project funded using such assistance give a hiring preference, to the extent practicable, to veterans (as defined in section 2108 of title 5) who have the requisite skills and abilities to perform the construction work required under the contract. This subsection shall not be understood, construed or enforced in any manner that would require an employer to give preference to any veteran over any equally qualified applicant who is a member of any racial or ethnic minority, female, an individual with a disability, or former employee.