RFP 24-009 EAMS Intructions to Proposers.pdf

SALEM AREA MASS TRANSIT DISTRICT

REQUEST FOR PROPOSAL

RFP 24 - 009

ENTERPRISE ASSET MANAGEMENT SOFTWARE

Date Issued: June 24, 2024

Pre-Proposal Conference: July 16, 2024 at 10:00 AM PST

● Non Mandatory VIRTUAL ONLY

Requests for Question Deadline: August 1, 2024 no later than 5:00 PM PST

SAMTD Response to Questions: August 9, 2024 no later than 5:00 PM PST

Proposal Closes & Responses Due: August 29, 2024 no later than 5:00 PM PST

Project Manager: TBD

Procurement Contact: Charleen McCurdy, Procurement Analyst

Submit Proposal: procurement@cherriots.org

Salem Area Mass Transit District (SAMTD) RFP 24-009 Enterprise Asset Management Software (EAMS)

RFP 24-009 EAMS Intructions to Proposers Final Page 1 of 29

Contents Part 1 – Introduction Part 2 – Scope of Work Part 3 – Submission Guidelines Part 4 – Proposal Evaluation Part 5 – Special Terms and Conditions Part 6 – Confidentiality Part 7 – Proposers Checklist

Included as separate attachments Appendix A – General Terms and Conditions Appendix B – Sample Contract Appendix C – Federal Terms and Conditions

Included as a single separate file Exhibit 1 – Proposal Form Exhibit 2 – Non-Collusion Affidavit Exhibit 3 – Organizational Conflict of Interest Exhibit 4 – DBE Determination of Good Faith Effort Exhibit 5 – Contractor’s Representations & Warranties Certification Exhibit 6 – Federal Debarment & Suspension Certificate Exhibit 7 – Certification Regarding Lobbying Exhibit 8 – Buy America Certification

Included as a separate Excel file Exhibit 9 – Price Proposal Form Exhibit 10 – Compliance Matrix

RFP 24-009 EAMS Intructions to Proposers Final Page 2 of 29

Part 1 – Introduction

SALEM AREA MASS TRANSIT DISTRICT (“SAMTD” or “Cherriots”) is a public transportation agency operating fixed-route transit and paratransit service within the urban growth boundary of Salem and Keizer, and regional express service between communities in Marion, Polk, and Linn counties. Other SAMTD services include Cherriots Shop and Ride, travel training and rideshare (Cherriots Commuter Options) information including carpool and vanpool matching.

SAMTD operates 68 Cherriots local buses, 43 Cherriots LIFT (paratransit service), 19 Cherriots Regional express buses and 4 Cherriots Shop and Ride buses (shopper shuttle and dial-a-ride).

In addition, Cherriots Route 1X is a commuter service that connects Salem with Wilsonville and the Portland Metro area to the North. SAMTD also manages ride share services called Cherriots Commuter Options. Currently, Cherriots Local buses generally operate during the weekdays between the hours of 6:00 a.m. and 11:00 p.m., Saturdays, 7:00 a.m. to 9:00 p.m., and Sundays and most holidays, 8:00 a.m. to 8:00 p.m. Cherriots Regional buses operate 5:00 a.m. to 8:30 p.m. on weekdays and 7:00 a.m. to 8:00 p.m. on Saturdays.

SAMTD Locations:

Administrative Offices The Cherriots General Manager, Communication, Finance, and Human Resources departments are located at:

555 Court St NE, Suite 5230, Salem, OR 97301.

Operations, Contracted Services, and Maintenance The Transportation, Maintenance, and Planning and Development Departments are located at the Del Webb Operations Headquarters. The Del Webb facility also includes the parking area for buses not in service:

3140 Del Webb Ave NE, Salem, OR 97301.

Keizer Transit Center 5860 Keizer Station Blvd., N.E.

Keizer, OR 97303

Additional information about SAMTD can be found at www.cherriots.org

SAMTD is soliciting proposals from qualified providers of Enterprise Asset Maintenance System software.

Proposers are required to adhere to the terms and conditions of the solicitation packet. SAMTD will not negotiate any aspect of the required service or Contract once the Notice of Intent to Award is issued. SAMTD will not make any concessions for Proposers who are not completely familiar with the scope or Contract requirements.

All submittals become the property of SAMTD and are subject to public disclosure after award.

Equal Opportunity: Small, minority, veteran, women-owned, and Disadvantaged Business Enterprises (DBE), as defined by 49 CFR Part 26, are encouraged to submit Proposals in response to this solicitation. SAMTD ensures non-discrimination in the award and administration of all Contracts, creates a level playing field where businesses can compete fairly and remove barriers to the participation in our contracts.

End of Part 1 - Introduction http://www.cherriots.org/

RFP 24-009 EAMS Intructions to Proposers Final Page 3 of 29

Part 2 – Scope of Work

2. A Introduction & Background

SAMTD currently utilizes FleetNet for its Enterprise Asset Maintenance System (“EAM”) as an On Premises (“On Prem”) solution. FleetNet has discontinued support of the On Prem solution and is migrating users to its Software as a Service (“SaaS”) model. SAMTD utilizes data contained within its EAM to generate required reports utilized for the National Transit Database, Federal Transportation Administration, and Oregon State Auditors. EAM is also used for inventory tracking and ordering, asset tracking, and work order tracking and reconciliation.

SAMTD desires the new solution to be provided in a SaaS model and anticipates a total of 70 users accessing the system.

The new solution must integrate and provide export data functionality with:

● Tyler Technologies Enterprise ERP for financial and payroll modules

● Fuel Force for fluid and fuel usage monitoring/inventory functions

● Avail Technologies Dashboard for CAD/AVL functions

Some portions of Tyler Technologies ERP and Trapeze software, which is used for dispatching, are on premises (“On Prem”). Any proposed SaaS solution must seamlessly work/integrate with the On Prem modules.

2. B Technical Requirements & Scope of Work

Proposers are directed to review Exhibit 10 - Compliance Matrix. SAMTD requires, at a minimum, for the successful solution to provide the identified features on the Compliance Matrix as standard Commercial Off The Shelf (COTS) or require a low level of configuration.

The EAM solution will be deployed in six (6) key phases: Initiation, Planning and Design, Execution, Training, Testing, and Deployment and Closure.

SAMTD intends to negotiate milestone payments for each Phase with the awarded contractor.

As a public entity, SAMTD is permitted to only provide pre-payment for required software licenses. Any implementation services or hardware provided by the awarded Contractor will be paid after SAMTD staff acceptance of the work and deliverables.

Documentation provided for deliverables must cover all installations, testing and training plans, configurations, processes, integrations, design diagrams, and any other material related to the overall project.

Phase 1: Initiation

Vendor’s Responsibilities SAMTD Responsibilities Deliverables

• Conduct kick-off meeting

• Conduct orientation session

• Develop and maintain the project schedule

• Develop and maintain the

Data Dictionary to be finalized by Go Live acceptance

• Ensure all appropriate stakeholders attend the kick-off and orientation

• Schedule the kick-off and orientation and provide meeting facility

• Provide input for the project schedule

• Identify key stakeholders

• Delivery of kick-off meeting and orientation

• Develop project schedule with recovery plan if needed.

RFP 24-009 EAMS Intructions to Proposers Final Page 4 of 29

The Initiation phase defines the objectives for the project and provides an opportunity for Vendor’s project team to align with SAMTD regarding project requirements, approach, and timelines. Key tasks associated with this phase include:

• Conducting an on-site project kick-off meeting

• Conducting an on-site EAM orientation demo

• Confirming Vendor’s understanding of project goals and objectives

• Agreeing on project methodology and scope of services effort

• Identifying potential project risks and mitigation strategies

• Discussing and agreeing on a preliminary project plan, project schedule, and project resources required to execute the plan

• Reviewing roles and responsibilities for Vendor and SAMTD resources

Vendor will develop a mutually-acceptable plan and schedule for the work to be completed and identify the resources and timeframe required for the efforts. The plan and schedule will include a recovery plan in the event work is delayed for more than ten (10) working days. Vendor will provide updated schedules on a bi-weekly basis throughout the implementation to go live acceptance.

Phase 2: Planning and Design

Vendor’s Responsibilities SAMTD Responsibilities Deliverables

• Conduct current state and future state workshops

• Map future state processes

• Conduct SAMTD interviews; prepare and deliver preliminary SAMTD status report; update and present final SAMTD status report

• Conduct system setup consulting workshops

• Develop a “Data Load Sequence Guide” explaining the system design and how it meets SAMTD needs

• Develop and present regular project updates

• Configure modules in accordance with the Data Load Sequence Guide, the Design Options Guide, and support approved SAMTD workflows in EAM environments

• Conduct software demonstrations

• Develop design specifications for all custom development items

• Transition existing data from FleetNet for cleaning,

• Participate in Business Process Assessment (SAMTD) meetings

• Ensure SAMTD’ resources are available to meet the schedule for completion

• Provide documentation on business processes including maintenance practices, codes, and key reports

• Highlight critical processes related to the operation of all proposed software

• Review preliminary design guide SAMTD and provide feedback

• Support workshops and provide appropriate attendees

• Provide crosswalk for definitions of all applicable Vendor EAM data elements based on configuration options presented in the workshops

• Provide facilities for meetings and workshops

• Review setup and configuration options with additional stakeholders

• Delivery of final consolidated SAMTD report

• Completed system setup consulting workshops

• Data Load Sequence Guide

• System Design Options

Guide

• Configured Software in

EAM environments

• System demonstrations

• Bi-weekly schedule updates

• If applicable, completed

Test Environments.

RFP 24-009 EAMS Intructions to Proposers Final Page 5 of 29 validation and integration to new solution

• Provide necessary support during vendor’s configuration of the EAM environments

• Provide sample data for vendor to utilize during the software demonstrations

• Provide facilities for and participate in the software demonstrations

• Participate in the custom development design process and provide signoff on each specification

• Begin review and validation of FleetNet data and ensure it meets the appropriate data element type formats, and all required fields have been provided

• Coordinate existing FleetNet data download to be integrated to Test environment, if applicable

As an option, the successful Proposer may be required to provide a functioning Test Environment by Phase 2 of the Implementation that will be utilized throughout the life of the contract. In the event SAMTD requests a Test Environment, the completion of the Test Environment will be added as a deliverable for Phase 2. Vendor will push any system upgrades to the Test Environment to allow SAMTD time to verify operability with any 3rd party integration.

At least annually, the Test Environment will be updated with SAMTD production data. (See Exhibit 9 Price Proposal).

Following the conclusion of the project kick-off, the Vendor’s project team will conduct an analysis of SAMTD’s operational processes, business rules, infrastructure and integration points in order to reach a mutual understanding of the specifications and reach an agreement on the design intent.

Key tasks associated with the Planning and Design phase include:

• Reviewing current operational policies and procedures as they relate to SAMTD processes, including pain points with current Software and discussion of best practice recommendations.

• Discussing specific Software configuration items and customizations.

• Discussing existing infrastructure and how operations can be improved, as well as how the Software will fit into the existing infrastructure.

• Reviewing testing, training, and go-live transition strategies and timelines.

• Evaluating existing process documentation.

• Establishing an understanding of current processes by surveying key stakeholders through questionnaires.

• Following up on interviews of key process owners, as required.

• Creating preliminary documentation of business processes and mapping them to

Vendor’s software.

• Leading workshops to validate and refine preliminary business processes.

RFP 24-009 EAMS Intructions to Proposers Final Page 6 of 29

• Leading software demonstrations to showcase the preliminary workflows in Vendor’s solution.

• Finalizing workflows in a SAMTD report.

• Coordinating with 3rd party software providers for all integration requirements.

• Completion of functional Test Environment with SAMTD data, if selected as an option by

SAMTD.

• Coordinating download of current FleetNet data for upload to new EAM software.

The SAMTD report will include an assessment of SAMTD’ maintenance activities to identify the critical practices and procedures that can be improved using Vendor’s EAM. The SAMTD report will be comprised of Current State Analysis, Future State Workshops and Preparation of SAMTD report.

Phase 3: Execution

Vendor’s Responsibilities SAMTD Responsibilities Deliverables

• Perform Internal

Acceptance Testing (IAT) to ensure data and configurations have been properly entered into EAM

• Perform Installation Testing to ensure applications are connected to the appropriate database(s) and general software functionality is working as designed

• Configure baseline EAM modules based on System Design Option Guide developed during System Setup Consulting

• Configure the mapping GIS module

• Develop functional and/or technical design specifications for Vendor-side of custom integrations based on requirements of the SAMTD report

• Provide final end-to-end specification documents for customizations to SAMTD for approval

• Develop and provide data loading templates

• Support with subject matter expertise and guidance during data gathering

• Assist SAMTD staff with data conversion, including migration and cleanup

• Obtain mapping service and any other 3rd party license(s) from 3rd party provider(s)

• Provide staff able to make decisions on each custom specification

• Provide and monitor method of data exchange or “handshake” for each integration

• Review and approve the functional and/or technical design specifications within ten (10) days of submission

• Coordinate the collection of data elements and provide in Vendor-provided data loading templates

• Complete data review and cleaning to ensure the data is consistent and cleansed to meet the appropriate data element type formats, and all required fields have been provided

• Assist in correcting data loading errors when errors are the result of missing or incorrect data

• Review and approve data loads to new environment

• Ensure resources are available to meet the schedule for completion

• GIS data properly displaying in EAM

• Software is installed/upgraded and configured in the test environment

• Approved functional and/or technical design specifications

• Completed custom development items

• Custom development items deployed to the environments

• Data Load Templates Data successfully loaded in environments

• Completed data conversion

• Bi-weekly schedule updates

RFP 24-009 EAMS Intructions to Proposers Final Page 7 of 29

• Load data into environments

• Troubleshoot and resolve issues during the data load process

• Validate all data loads have completed successfully

• Perform one (1) mock cutover data loads for dynamic data

Internal Acceptance Testing (IAT) is completed remotely by Vendor before any Software is installed/upgraded in SAMTD’ environment. After unit and regression testing is completed, the Vendor will run a series of tests in a local testing environment to ensure that all Software is functioning properly.

Following the completion of final SAMTD approval, Vendor will work with SAMTD to remotely install/upgrade and configure the software in SAMTD’ environment.

Installation Testing is designed to ensure the Software is functioning properly. Vendor will validate the following:

• Applications are connected to the appropriate database(s).

• General software functionality is working as designed.

• All configurations and settings are functioning as agreed upon in the SAMTD report.

In addition, Vendor will create initial users and user groups, (with administrator rights), and will confirm that these initial users have access to the areas necessary to proceed with software setup activities.

Vendor will work with SAMTD to configure the EAM modules necessary to support the business process workflows as agreed to in the SAMTD. Upon completion of this transfer of information, SAMTD’ core team will be able to configure various EAM screens as they deem appropriate.

Vendor will provide the services to configure the Mapping Geographic Information System (GIS) module to display the location, status and work activity associated with SAMTD’ assets in EAM.

SAMTD will obtain necessary mapping service, and any other additional third-party party licenses and to comply with all restrictions and limitations imposed by the third-party provider(s).

Vendor will develop functional and/or technical design specifications for each of the agreed-upon custom integrations specified in the SAMTD report. Vendor will submit each design specification to SAMTD for review and approval.

After specifications are agreed upon, Vendor will develop the items based on the approved design specifications. Vendor will then deploy the custom development items into the appropriate environments.

For each required integration, the project team will discuss and specify the data elements required, the time of the exchange, and the method of data exchange.

Vendor will work with SAMTD’ Maintenance department to review and optimize their current coding structures at the system-wide and location levels for use with the EAM modules.

RFP 24-009 EAMS Intructions to Proposers Final Page 8 of 29

Vendor will determine the data required to make the system operational (e.g., assets, parts, vendors, employees, etc.) and then identify, in conjunction with SAMTD staff, what data will be available from current systems, and what data SAMTD may have to develop for the new modules. Once the data-loading specifications are completed, SAMTD will collect the data as required. SAMTD will be responsible for providing and populating EAM with approved data that adheres to the Vendor templates provided.

Vendor will provide data-loading templates for SAMTD to complete. With support from Vendor, SAMTD staff will add data and return templates to Vendor for validation of content and format.

Vendor will load data from these templates into corresponding Vendor EAM screens. Vendor and SAMTD’ subject matter experts will jointly resolve any errors that may occur as part of the loading process.

Historical work order or purchase order data will be loaded into EAM or migrated from the FA product through the data export by the Vendor.

Phase 4: Training

Vendor’s Responsibilities SAMTD Responsibilities Deliverables

• Develop Training Plan

• Deliver Train-the-Trainer

Training

• Provide training materials in electronic format

• Provide support for end user training

• Ensure resources are available to meet the schedule for completion

• Ensure trainers are available to be trained

• Provide training facilities with network connectivity and individual workstations for each participant per class

• Reproduce training materials and provide printed copies for all class participants and instructor

• Deliver end user training

• Manage training environment (user logins, permissions, etc.)

• Finalized Training Plan

• Delivery of Train-the-

Trainer Training

• Standard training materials delivered

• Bi-weekly schedule updates

Vendor will develop a Training Plan that incorporates each module that is provided in the final solution. The Training Plan will be tailored to ensure a successful implementation and operation of the new system, addressing, at a minimum, the following topics:

• Training schedule to be conducted at SAMTD locations.

• Training curricula, including a listing of each course and delivery method.

• Course descriptions, intended audience, length of each course, and resources required.

• Course instructor.

Once SAMTD approves the Training Plan, Vendor will provide standard training materials and begin scheduling and planning for the training. The training will cover common features and transactions, including those finalized by the SAMTD team during the software setup and follow-up tasks. Training will ensure all stakeholders are trained to sufficient proficiency to perform their daily tasks within the system.

RFP 24-009 EAMS Intructions to Proposers Final Page 9 of 29

Additional end user training support should be available and will be negotiated as a separate Purchase Order.

Phase 5: Acceptance Testing

Vendor’s Responsibilities SAMTD Responsibilities Deliverables

• Develop test plan content

• Develop test scripts

• Perform Site Acceptance

Testing and any associated remediation

• Provide completed Test Script results and Test Report

• Support User Acceptance Testing

• Set initial Issue Classification for items found in User Acceptance Testing

• Ensure resources are available to meet the schedule for completion

• Perform User Acceptance Testing and assist with remediation as needed

• Participate in Issue Classification for items found in User Acceptance Testing

• Approve test plan and test scripts

• Test Plan Finalized

• Completed User

Acceptance Testing

• Participate in Issue

Classification for items found in User Acceptance Testing

• Provide bi-weekly schedule updates

Vendor will prepare a test plan with a comprehensive testing timeline to ensure the system configuration meets the “To-Be” functional design outlined in the SAMTD. After Vendor executes the test scripts, SAMTD may use the same test scripts to execute its own user acceptance testing.

After completion of all in-scope development services, internal testing, software configuration, and data loading, Vendor will remotely execute Site Acceptance Testing (SAT) with SAMTD staff present, within SAMTD’s environment to ensure that all EAM Software is working successfully. SAT will include the following specific testing activities:

• Unit Testing: To validate the individual functions of the EAM Software to ensure they are working as designed.

• System Testing: To test all major business functions as designated in the Compliance Matrix (Exhibit 10), including reporting and any shortcuts, to ensure they are working as designed.

• Integration Testing: With SAMTD, to jointly test the integration per the approved project schedule to ensure it is working as designed.

User Acceptance Testing (UAT) involves utilizing the new Vendor Software in SAMTD’s environment to ensure it responds accurately to user inputs and that all features and functions work as specified in the SAMTD Compliance Matrix (Exhibit 10).

During User Acceptance Testing, SAMTD will document and prioritize any defects encountered throughout the testing period (if any exist), which Vendor will assess for root cause, provide a timeline for resolution, and resolve based on their severity levels.

After SAMTD confirms all critical and major defects have been resolved, User Acceptance Testing will be considered complete, and the Software deemed ready for production use.

SAMTD will be required to sign off on the User Acceptance Testing. Minor defects will be transitioned to the Vendor maintenance and support program.

RFP 24-009 EAMS Intructions to Proposers Final Page 10 of 29

Phase 6: Deployment, Testing, and Closure

Vendor’s Responsibilities SAMTD Responsibilities Deliverables

• Provide and Support the

Deployment/Go-Live Plan

• Migrate the Software into production environment

• Lead and support EAM-related cutover activities, including scheduling, testing, coordinating, and communicating progress related to cutover

• Provide on-site cutover, deployment, and post go-live support

• Provide Post Go-Live Support Plan

• Finalize and close all contract deliverables

• Prepare for and lead a Vendor Customer Care transition call

• Ensure resources are available to meet the schedule for completion

• Participate in cutover activities

• Provide frontline Subject Matter Experts (SME) support for end user questions

• Escalate issues to Vendor

• Update the production system to ensure all records are up to date

• Ensure data correctness

• Confirm connectivity, logins, etc.

• Confirm finalization and closure of all contract deliverables

• Clear any outstanding project balance

• Participate in Customer Care transition call

• Deployment/Go- Live Plan Finalized

• On-site cut-over and deployment support

• Vendor Software operational and functional in production environment

• Post Go-Live Support Plan

Before the deployment into the production environment can proceed, the following activities must be completed:

1. Vendor-led Site Acceptance Testing

2. SAMTD-led User Acceptance Testing

3. Vendor-led Train-the-Trainer Training

4. SAMTD-led End User Training

5. No open Level 1 or 2 severity errors

6. One (1) successful mock cutover data conversion for dynamic data

During the deployment activities, Vendor, in coordination with SAMTD, will release Software to production environment at SAMTD location so that it can be used to support live operations.

SAMTD will be responsible for the roll out of the Software to their remaining employees and its use to support live operations.

Vendor will provide a detailed Deployment Plan describing the cutover preparation, cutover support, and go-live activities and responsibilities. In addition, Vendor will verify readiness to move data, configurations and new modules into production, load required dynamic data elements, and ensure permissions and access are in place. SAMTD will be responsible for scheduling, coordinating, and communicating cutover activities to ensure all prerequisites are met, all resources scheduled, and all parties are prepared.

RFP 24-009 EAMS Intructions to Proposers Final Page 11 of 29

The final stage of the project involves transitioning the Software to the production environment.

Tasks include:

• Preparing the production environment

• Providing deployment support

• Installing software into the production environment

Phase 7: Burn In Period

Vendor will provide remote post-deployment support for ninety (90) days, following the on-site go-live acceptance. Any warrantable issues will be resolved at no charge. After the completion of the post-deployment support period, all support will be transitioned to the Vendor long-term maintenance program.

Any new configurations will be quoted as a change order.

End of Part 2 – Scope of Work

RFP 24-009 EAMS Intructions to Proposers Final Page 12 of 29

Part 3 – Submission Guidelines

3. A Procurement Schedule

Dates preceded by an asterisk (*) are estimated dates and provided for information only.

Estimated dates may change after proposal submission and not be part of any addenda.

Procurement Activity Date - 2024 Procurement Request Released June 24 Pre-Proposal Conference July 16 at 10:00 AM PST (Virtual) Clarification Deadline August 1, no later than 5:00 PM PST *SAMTD Clarification Response August 9, no later than 5:00 PM PST Submissions Due August 29, no later than 5:00 PM PST *Interviews/Demonstrations Week of September 23 *Notice of Intent to Award October 4 *Estimated Award Date October 24

SAMTD reserves the right to modify the Procurement Schedule through written addenda.

Submissions are not reviewed or considered after the due date has passed. SAMTD reserves the right to award a contract without a Best and Final Offer. Issuance of a Notice of Intent to Award is not a substitute for a Contract and can be revoked.

SAMTD may invite the top firms (competitive range) for a semifinal interview/presentation.

SAMTD provides requirements for the interview when the interview is scheduled. SAMTD will not be responsible for any costs for preparing submissions, attending a pre-proposal conference, or participating in interviews including but not limited to travel expenses, preparation costs, or materials.

3. A.1 Pre-Proposal Conference

A pre-proposal conference will be held virtually via Google Meet at the date and time provided in the Procurement Schedule. Interested proposers are encouraged to attend as a means of gaining clarity for the requested scope of work and ensuing contract.

To join virtually:

https://meet.google.com/pgy-hthv-yry

To join via phone:

(240) 617-0140

PIN: 264 373 686#

3. B Proposal Guidelines

Proposers should fully inform themselves of the conditions, requirements, and specifications before submitting a Proposal. The submission of a Proposal constitutes Proposers acceptance of the terms and conditions of this solicitation request, including the underlying Contract terms and conditions which are set out herein.

The Proposer is responsible for all costs related to the preparation of the Proposal, demonstrations or interviews. Any costs associated with the project not specifically set forth in this Request for Proposal will be the responsibility of the Proposer and will be deemed included in the fees and charges proposed.

RFP 24-009 EAMS Intructions to Proposers Final Page 13 of 29

SAMTD reserves the right to:

● Award to one or more vendors at SAMTD’s sole option

● Accept or reject any or all Proposals and their Proposers

● Reject this solicitation and issue a new one for any reason

● Waive deviations from the requirements

● Waive any informality or minor irregularity in Proposals received

● Issue changes to the solicitation in the form of written addenda

● Request additional information to fully evaluate a Proposal

A Proposal may be rejected when:

● It is late

● The Proposer fails to meet the minimum qualifications listed in Part 3.C

● The Proposer is determined to be not responsible as described in Part 4.D

● Any required form/exhibit is not signed

● Vendor information, references, or any other form/exhibit is incomplete or incorrect

● Any other reason determined to be in the best interest of the SAMTD

● It does not meet required terms and conditions

● The details of the Proposal have been altered

● A Proposer fails to timely respond to a request for additional information

● It fails to contain any of the required information

● A conflict of interest is not properly disclosed or is deemed by SAMTD to disqualify the Proposal as provided by law

● Proposer fails to acknowledge in writing an addenda

Proposals may not be modified after opening unless requested by SAMTD. Prior to opening, Proposals may be withdrawn at any time.

SAMTD may request that information be displayed differently than presented (for example, request a bundled pricing structure be itemized).

Proposal pricing shall be valid for a period of 120 days from Proposal or Best and Final Offer (BAFO) deadline, if a BAFO occurs.

SAMTD may request clarification or additional information, including, but not limited to, financial statements.

3. C Minimum Proposer Qualifications

At time of submission, Proposer will meet the following minimum requirements. Proposers will not substitute the experience of any subcontractors for their own.

● Proven experience providing technical consulting and acquisition services

● Has successfully passed a Service Organization Control Type II (SOC2) Audit within the past twelve (12) months

● Have a State of Oregon and all required local government business license(s), registrations, and endorsements.

● Not be suspended or debarred with SAM.gov.

● Not be debarred by any Oregon contracting agency under ORS 279B.130

● Not be disqualified from bidding under ORS 279C.860

● Not in violation of any Oregon tax laws set forth at ORS chapters 118, 314, 316 - 318, 321 and 323; under ORS 320.005-320.150; under ORS 403.200-403.250; and local tax laws administered by the Oregon Department of Revenue under ORS 305.620

RFP 24-009 EAMS Intructions to Proposers Final Page 14 of 29

3. D Questions, Clarifications, Request for Deviation, Substitution or Approved Equals

Questions, clarifications, and alternates pertaining to the RFP must be submitted in writing to procurement@cherriots.org no later than the date and time listed in the Procurement Schedule above. The request shall specify the provision of the RFP in question, and, if a change is requested, contain an explanation for the requested change. Where applicable, Proposers are required to provide the value of each proposed modification and a brief explanation as to why the change is requested. SAMTD does not guarantee a response to questions submitted after this date or questions and requests that are not submitted in writing via email.

Any unapproved deviations, exceptions, substitutions, alternates, or conditions contained in a Proposal are cause for the Proposal’s rejection as non-responsive.

Unauthorized contact regarding this RFP with SAMTD employees or agents may result in disqualification. Any oral communications will be considered unofficial and non-binding on SAMTD. Proposers should rely only on written statements issued by Procurement in a formal Addenda (See Part 3.F).

Do not add any SAMTD email address to company marketing email lists.

SAMTD will only accept a substitution of alternate material or equipment when:

1. The Contractor submits documentation acceptable to SAMTD attesting that the material or equipment specified in this Contract is no longer available;

2. The alternate material or equipment will be supplied at no additional cost; and

3. The alternate material or equipment meets the requirements and specifications set forth in the Scope of Services/Specifications.

Documentation supporting the non-availability of material or equipment may include, but not be limited to, one of the following: certification from the manufacturer that the item has been discontinued or that there has been a substantial change in its specifications; the manufacturer has gone out of business; or new import restrictions have been imposed on the item.

Any Proposer(s) believing a Contract term or scope requirement is unnecessarily restrictive or wishing to propose an alternate must submit their request in writing to procurement@cherriots.org by the deadline provided in the Procurement Schedule. Requests submitted after this date, or as a Proposal condition will not be reviewed or considered. SAMTD will not agree to terms or conditions to the Contract after Proposals are submitted and conditioned Proposals may be rejected as non-responsive. Any changes or requests pertaining to the Contract must be made evident prior to the close of the procurement.

3. E Submission Packages

Proposals will be in PDF format submitted to procurement@cherriots.org or be sent as a USB/Thumb drive via regular mail no later than the due date outlined in the Procurement Schedule. It is the Proposers responsibility to ensure the submission packet is received on time by SAMTD.

Proposals sent via Fed-Ex, UPS or other carrier providing guaranteed delivery but were not delivered, will be accepted upon receiving proof of guaranteed delivery date. SAMTD will not review submissions if the packet or forms are altered in any way.

SAMTD will not review submissions if the Exhibits are altered in any way.

mailto:procurement@cherriots.org

RFP 24-009 EAMS Intructions to Proposers Final Page 15 of 29

Submissions must be typed to be legible. Digital signatures are encouraged and preferred.

Proposers may submit a wet signature, provided the remainder of the submission is typed.

Failure to include any of the requested information using the provided Exhibits will render the Proposal non-responsive. Marking a Proposal, or portions of the Proposal, as “confidential” or “proprietary” does not automatically exempt it from disclosure under the Oregon State Public Records Act, ORS Chapter 192.

Marketing materials, alternate and unapproved agreements, and any other information not specifically requested or required in this RFP will not be reviewed. Proposer will NOT add SAMTD to any marketing email lists.

All proposals will contain the following information in addition to the Exhibits provided. In addition to all completed exhibits as outlined in Part 7 “Proposers Checklist”, Proposers will submit a technical response addressing the following. Proposers may emphasize in their narrative any areas of their proposal that they believe exceed SAMTD requirements. Proposers are advised to clearly communicate enough detail and relevant information to ensure effective evaluation by SAMTD’s Evaluation Committee.

1. Firm Information Introduce the firm and the product being proposed. Provide feedback collected from previous customers regarding your performance. Less than favorable feedback should include steps the firm has taken to remedy any issues, or address the customer’s concerns.

List any contracts within the past three (3) years that the firm may have defaulted on or failed to meet contract terms. Identify any past (within the last three (3) years) or pending litigation alleging failure to perform in accordance with contractual obligations and describe present status. Explicitly state if there is no such litigation. List any projects resulting in time extensions and/or the assessment of liquidated damages against the Firm or sub-contractors during the last five (5) years. Explicitly state if there were no extensions/assessments. Identify any past (within the last three (3) years) or pending liens, claims, infractions, or citations filed or recorded by a County, State or the federal government, or filed by subcontractors, suppliers, or materialmen. List with whom, for what, and the amount claimed. Explicitly state if none of these situations apply. Provide a list of contracts in the last five (5) years that may have terminated for reasons other than the natural expiration. Include details about why the contract terminated.

Submit no more than five (5) completed relevant project experiences (within the past three (3) years) that demonstrate successful contract performance similar in size and scope as described in this RFP. Include the following for each reference (include transit or government experience):

i. Company name and full address

ii. Point of contact name, title, e-mail address, and phone number

iii. Contract title, number, start and completion dates

iv. Contract description & order / service details

2. System Description & Functionality Provide a brief overview of the system including a description of the environment (SaaS, On Prem, etc.) and functionality of each option. If the software is locally installed on a desktop computer, what are the recommended specifications? Describe the way that licenses are calculated (each or in bundles), and the licensing types (named, per seat, concurrent, etc.). Does the software have any hardware requirements? Does the

RFP 24-009 EAMS Intructions to Proposers Final Page 16 of 29 software necessitate the use of any peripherals or specialty hardware? Include any equipment (bar code scanners, tablets, etc.) that would augment any functionality of the software. Indicate if the equipment is agnostic and can be sourced anywhere. If equipment is available from the proposer, indicate pricing on the Price Proposal Exhibit 9.

Describe how the new software system integrates with Tyler Enterprise EFP (ERP), Active Directory, AVAIL CAD/AVL system, Google Workspace, and Fuel Force. Identify what, if any, data SAMTC possesses that is integral to the operation of your software.

Please also identify any data SAMTD must create to be successful in utilizing your software

Describe any embedded reporting features including specifics on canned reports, data extraction tools and dashboards supplied as part of the software. Outline what attributes are accessible for reporting. Provide sample “canned” reports that are pre-loaded into the system. Describe how are reports configured and customized.

State how data will be stored, the data retention period and how it can be retrieved by SAMTD. SAMTD will retain all property rights related to any new data generated by the new software system.

Describe the tools, techniques, and algorithms proposed for data encryption and security. Describe your plan to meet data privacy requirements, such as HIPAA and FERPA (if applicable). Describe any additional security measures that protect Internet accessible components. Provide results from the most recent SOC2 audit and any other relevant independent application security testing reviews.

Does the software have any specific network or bandwidth requirements? Does the software necessitate cellular or radio communications? Describe how the software behaves during network outages.

3. Project Plan Outline intended plan for full implementation and integration. Include detail on the approach, include project management, change management, data conversion/migration, testing and training. Describe how the Project Manager will keep SAMTD informed of any issues related to delivering the services described in the scope of work.

Describe the approach to meet SAMTD requirements and avoidance of customizations.

Address the process for fixing failures during each phase. Describe how repeated failures are corrected. Detail the approach to providing and monitoring quality control and quality assurance during all phases.

Define the proposed implementation team. Include working hours, time zones, locations, role, and provide a highlight of the individuals qualifications and experience. Include staffing resource requirements for SAMTD staff. Outline the process for changing any key resources on Proposer staff. Discuss any additional time constraints on Vendors implementation such as additional projects that may conflict, how positions may be backfilled in the event of an extended absence, and provide a plan for how SAMTD may escalate any unresolved issues with Contractor staff.

RFP 24-009 EAMS Intructions to Proposers Final Page 17 of 29

Describe any intended deliverables above what is listed as a requirement for each Phase.

Detail a comprehensive training program that incorporates each module that may be provided in the final solution. Provide additional training that may be available including frequency of any user conferences, regional training or road shows, user groups, on demand training, etc. Describe any additional training/support options for users (phone support, remote diagnostics, etc.)

4. Project Timeline Include a proposed timeline for each Phase from Implementation to the completion of Burn In. Identify all critical path items and any other dependencies. Explain methods and processes used to ensure timely project delivery. Where applicable, identify impacts in the event of an item identified in the Risk Mitigation plan occurs. Describe methods for mitigating delays.

5. Warranty and Support Describe the warranty and technical support options available for ongoing support after the Burn In period is complete. Detail any operational services that are available after the any warranty period ends.

6. Risk Mitigation Plan Proposer will provide a comprehensive list of potential risks that may impact any stage of the project based on the understanding of the Scope of Work communicated in this RFP and the Compliance Matrix (Exhibit 10). Include concerns relating to performance success, explain why the risk is a risk, and make sure the risk is specific to the phases included in the Scope of Work. Identify solutions to avoid or minimize the identified risks.

Develop a plan to reduce the impact to the project and prioritize the risks in order of importance.

7. Value Added Options Express any value-added options or ideas that may benefit SAMTD that is not outlined in the Scope of Work or on the Compliance Matrix (Exhibit 10). This could include ideas or suggestions on alternatives in performance, security, timelines, scope, goals, additional related services, etc. These ideas must be logical and based on verifiable metrics.

8. Price Proposal Using Exhibit 9 provided, complete all applicable fields for the proposed software. Any travel is based on actual receipts and will follow the process outlined in Part 5, section B below. If there are items not listed, prospers are encouraged to add rows.

BASE SERVICES: This is the section that will be assigned points for evaluation and will only include all base costs to implement the software as requested in the Scope of Work.

Update software license charges appropriately based on how they are calculated and the type detailed in the System Description & Functionality description above.

ONGOING LICENSES: Provide costs for ongoing licensing of the software. Include pricing to add licenses after Go-Live.

OPTIONAL ITEMS/VALUE ADD: Detail any additional items not considered in the original Scope of Work, including the value add options provided in the section above.

9. Disentanglement Proposers will provide a plan for continued performance for the smooth transition to a new service and the transfer of data from the proposers solution in the event of contract

RFP 24-009 EAMS Intructions to Proposers Final Page 18 of 29 termination or expiration. This plan should include a transition plan and how SAMTD data will be provided back to the agency:

1. What format will the data be provided in.

2. How long will data retrieval will take.

3. Proposers process for wiping/destroying customer owned data from Proposer servers.

4. Verification process to ensure all data is returned to SAMTD and destroyed.

5. Process for requesting and receiving data.

6. Any costs associated with disentanglement.

3. F Addenda

Modifications to this RFP shall be made only by addenda posted to the OregonBuys site.

Verbal, faxed, or e-mailed instructions, interpretations, and changes shall not serve as official expressions of SAMTD and shall not be binding. All cost adjustments or other changes resulting from said addenda shall be taken into consideration by Proposers and included in their proposals. All addenda issued by SAMTD (posted to OregonBuys site) shall be acknowledged by Proposer on the Acknowledgement of Addenda form.

3. G Protest Procedures

Protests shall only be accepted from participating proposers and must be submitted in writing and in a timely fashion, in accordance with SAMTD’s formal protest procedures. SAMTD’s formal protest procedures may be requested by contacting SAMTD Procurement in writing at procurement@cherriots.org. Once a Proposer exhausts SAMTD’s protest procedures, as described in applicable SAMTD Procurement Policy, the Contractor may request review from the FTA’s Region 10 office within five (5) working days of SAMTD’s final decision of the protest.

However, Proposers are cautioned that FTA’s jurisdiction over protests are limited in scope.

3. H Conflict of Interest

SAMTD officers, employees, agents, or Board members will not solicit or accept gifts, favors, or anything of monetary value from Proposers. Any SAMTD officer, agent, employee, or Board member with a perceived or actual financial or other interest in the award of the proposed Contract will recuse himself/herself from any evaluation or decision on any Proposal.

Proposers and their staff must declare any perceived or actual conflict of interest using the form/exhibit provided. For example, a conflict of interest would arise if a Proposer or staff did the following:

● Assists in the creation of the scope of work. This includes, but is not limited to, reviewing and commenting on the preliminary scope in whole or part, assisting staff in specification writing, or recommending the use of a particular brand or supplier/distributor in the specification or evaluation of Proposals.

● Has access to nonpublic information during the performance of an earlier Contract or has been provided with information other Contractors have not during procurement.

● Assists in the creation of a project budget.

● Has a personal or professional relationship or affiliation (past or present) with a member of the evaluation committee or project team.

● Has a financial gain from the recommendation and/or purchase of a particular good or service relating to a Contract or potential Contract. (e.g. distributor/manufacturer relationship)

RFP 24-009 EAMS Intructions to Proposers Final Page 19 of 29

SAMTD will review all conflict of interest statements and notify the Proposer of its decision to allow or reject a Proposal as it pertains to the conflict.

In the event that a conflict of interest is discovered post-award, this will be considered a breach of Contract and the Contract will be terminated under the terms and conditions provided. The Proposer must pay any additional costs incurred by SAMTD to engage another Contractor to finish the work.

3. I Disadvantaged Business Enterprise.

SAMTD has an overall agency goal of 2.49 percent (2.49%) for the utilization of DBEs using race neutral means. This contract will utilize Federal Funds and therefore is subject to the terms and conditions outlined in Exhibit C “Federal Terms and Conditions”. SAMTD strongly encourages and expects Proposers to pursue subcontracting, mentoring, joint venturing, teaming, and partnering opportunities with DBE firms in the ordinary course of its business/teaming strategies. Proposers are encouraged and expected to create a level playing field to the maximum practical extent, consistent with the objectives and requirements of the SAMTD DBE Program, which is based on federal regulations codified at 49 CFR Part 26. The DBE participation goal applies to the total value of all anticipated SAMTD Federal contracts.

SAMTD’s DBE Program and Policy may be accessed at www.Cherriots.org/en/about-us/procurement.

3. J Buy America

This contract is funded in part from the Federal Transportation Administration. Any manufactured good must adhere to Buy America requirements.