SFMTA-2026-43-LOC_-_Attachment_2_-_Contract_Terms.docx
DOCX document 216 KB Posted
- Attached to
- EXT MTA | Traffic Signal Central Management
- Solicitation number
- SFGOV-0000012216
- Issued by
- San Francisco County, San Francisco City, California
About this file
This is a Software as a Service (SaaS) Agreement between the City and County of San Francisco Municipal Transportation Agency (SFMTA) and a contractor for the provision of a Traffic Signal Central Management Software (CMS) solution. The SFMTA seeks to procure a centralized platform for monitoring, controlling, and managing the Agency's traffic-signal infrastructure, with the contractor responsible for configuration, implementation, hosting, maintenance, and support of the SaaS Application and related services. The contract was competitively selected pursuant to Invitation for Bids (IFB) No. SFMTA-2026-43-LOC, with a virtual Pre-Bid Conference scheduled for November 12, 2026, at 1:00 PM PT. The contract term commences on the Effective Date (upon Controller certification of funds) and expires five years from that date, with the SFMTA holding the option to extend for four additional years at the Director of Transportation's sole discretion. The contract encompasses SaaS Implementation and Training Services, SaaS Application and Hosting Services, Disaster Recovery Plan provisions, and comprehensive Service Level Obligations as detailed in the appendices.
The compensation structure includes one-time costs for Project Kick-Off Meeting, Implementation and Integration, System Documentation, and Training, with fixed annual fees for the CMS License and ongoing Services (support, maintenance, updates, and other services). Pricing is firm and not subject to escalation during the applicable Contract Year or option year, except as expressly provided. The Local Business Enterprise (LBE) subcontracting participation requirement for Services has been waived pursuant to waiver CMD14BPREBID0002963. The contractor must maintain specified insurance coverage, including Commercial General Liability ($1,000,000), Technology Errors and Omissions Liability ($5,000,000), and Cyber and Privacy Liability ($5,000,000). The agreement is subject to the City's budget and fiscal provisions, with termination without penalty if funds are not appropriated for subsequent fiscal years. The City retains the right to terminate for cause (with a 10-day cure period) or for convenience (with 30 days' notice), and the contractor must provide transition services for up to six months upon request, including data transfer to a successor service provider at no cost to the City.
View the file
Other files
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
City and County of San Francisco Municipal Transportation Agency One South Van Ness Ave., 7th Floor San Francisco, California 94103
Software as a Service Agreement between the City and County of San Francisco and
[Insert Name of Contractor]
Contract No. SFMTA-2026-43-LOC
| SFMTA P-648 (4-26) | SFMTA-2026-43-LOC |
| EFJ | 4924-8253-4092 v.1 |
TABLE OF CONTENTS
| Article 1 | Definitions | 2 |
| Article 2 | Term of the Agreement | 6 |
| 2.1 Term | 6 | |
| 2.2 Options to Extend | 6 | |
| Article 3 | Financial Matters | 6 |
| 3.1 Certification of Funds; Budget and Fiscal Provisions | 6 | |
| 3.1.1 Termination in the Event of Non-Appropriation | 6 | |
| 3.1.2 Guaranteed Maximum Costs | 7 | |
| 3.2 Authorization to Commence Work | 7 | |
| 3.3 Compensation | 7 | |
| 3.3.1 Contract Not to Exceed Amount | 7 | |
| 3.3.2 Payment Limited to Satisfactory Services and Delivery of Goods | 8 | |
| 3.3.3 Withhold Payments | 8 | |
| 3.3.4 Invoicing | 8 | |
| 3.3.5 LBE Payment and Utilization Tracking System | 8 | |
| 3.3.6 Payment Terms | 8 | |
| 3.3.7 Reserved. (Grant Funded Contracts) | 8 | |
| 3.4 Audit and Inspection of Records | 9 | |
| 3.5 Submitting False Claims | 9 | |
| Article 4 | SaaS Services and Resources | 9 |
| 4.1 SaaS Licensed Software | 9 | |
| 4.1.1 Click-Wrap Disclaimer | 9 | |
| 4.1.2 SaaS Application Title | 9 | |
| 4.1.3 Authorized APIs | 9 | |
| 4.1.4 Proprietary Markings | 10 | |
| 4.2 Project Managers; Services Contractor Agrees to Perform | 10 | |
| 4.2.1 Project Managers | 10 | |
| 4.2.2 Services Contractor Agrees to Perform | 10 | |
| 4.3 Acceptance Testing; Document Delivery; Training | 11 | |
| 4.4 Qualified Personnel | 12 | |
| 4.5 Subcontracting | 12 | |
| 4.6 Independent Contractor; Payment of Employment Taxes and Other Expenses | 12 | |
| 4.6.1 Independent Contractor | 12 | |
| 4.6.2 Payment of Employment Taxes and Other Expenses | 13 | |
| 4.7 Assignment | 13 | |
| 4.8 Reserved. (Liquidated Damages) | 13 | |
| Article 5 | Insurance; Indemnity; and Warranties | 13 |
| 5.1 Insurance | 13 | |
| 5.1.1 Required Coverages | 13 | |
| 5.1.2 Additional Insured | 14 | |
| 5.1.3 Waiver of Subrogation | 14 | |
| 5.1.4 Primary Insurace | 14 | |
| 5.1.5 Other Insurance Requirements | 14 | |
| 5.2 Indemnification | 15 | |
| 5.2.1 General Indemnification | 15 | |
| 5.2.2 Infringement Indemnification | 15 | |
| 5.3 Warranties of Contractor | 16 | |
| 5.3.1 Warranty of Authority; No Conflict | 16 | |
| 5.3.2 Warranty of Performance | 16 | |
| 5.3.3 Compliance with Description of Services | 17 | |
| 5.3.4 Title | 17 | |
| 5.3.5 Disabling Code | 17 | |
| 5.3.6 Warranty of Suitability for Intended Purpose | 17 | |
| 5.3.7 Business Continuity | 17 | |
| Article 6 | Liability of the Parties | 18 |
| 6.1 Liability of City | 18 | |
| 6.2 Liability for Use of Equipment | 18 | |
| 6.3 Liability for Incidental and Consequential Damages | 18 | |
| Article 7 | Payment of Taxes | 18 |
| 7.1 Contractor to Pay All Taxes | 18 | |
| 7.2 Possessory Interest Taxes | 18 | |
| 7.3 Withholding | 18 | |
| Article 8 | Termination; Disposition of Content; Survival | 19 |
| 8.1 Termination for Cause and/or Convenience | 19 | |
| 8.1.1 Termination for Cause | 19 | |
| 8.1.2 Termination for Convenience | 19 | |
| 8.2 Termination for Default; Remedies | 19 | |
| 8.3 Bankruptcy | 20 | |
| 8.4 Transition Period and Disposition of City Data | 20 | |
| 8.4.1 Transition Period | 20 | |
| 8.4.2 Disposition of City Data. | 21 | |
| 8.5 Remedies | 22 | |
| 8.6 Notice of Default. | 22 | |
| 8.7 Non-Waiver of Rights. | 22 | |
| 8.8 Survival | 22 | |
| 8.9 Data Rights | 22 | |
| Article 9 | Rights in Deliverables | 23 |
| 9.1 Ownership of Results | 23 | |
| 9.2 Works for Hire | 23 | |
| Article 10 | Additional Requirements Incorporated by Reference | 23 |
| 10.1 Laws Incorporated by Reference | 23 | |
| 10.2 Governmental Conduct-Related Contractual Obligations | 23 | |
| 10.2.1 Conflict of Interest | 23 | |
| 10.2.2 Prohibition on Use of Public Funds for Political Activity | 23 | |
| 10.2.3 Limitations on Contributions | 23 | |
| 10.3 Employment Related Contractual Obligations | 24 | |
| 10.3.1 Local Business Enterprise and Non-Discrimination in Contracting Ordinance | 24 | |
| 10.3.2 Minimum Compensation Ordinance | 24 | |
| 10.3.3 Health Care Accountability Ordinance | 24 | |
| 10.3.4 First Source Hiring Program | 24 | |
| 10.3.5 Alcohol and Drug-Free Workplace | 25 | |
| 10.3.6 Nondiscrimination in Contracts | 25 | |
| 10.3.7 Nondiscrimination in the Provision of Employee Benefits | 25 | |
| 10.4 Environmental-Related Contractual Obligations | 25 | |
| 10.4.1 Food Service Waste Reduction Requirements. | 25 | |
| 10.4.2 Tropical Hardwood and Virgin Redwood Ban | 25 | |
| 10.5 Reserved. (Slavery Era Disclosure) | 25 | |
| 10.6 Reserved. (Nonprofit Contractor Obligations) | 25 | |
| Article 11 | General Provisions | 25 |
| 11.1 Notices to the Parties | 25 | |
| 11.2 Compliance with Laws Requiring Access for People with Disabilities | 26 | |
| 11.3 Incorporation of Recitals | 26 | |
| 11.4 Sunshine Ordinance | 26 | |
| 11.5 Modification of this Agreement | 26 | |
| 11.6 Dispute Resolution Procedure | 27 | |
| 11.6.1 Negotiation; Alternative Dispute Resolution | 27 | |
| 11.6.2 Government Code Claim Requirement | 27 | |
| 11.7 Agreement Made in California; Venue | 27 | |
| 11.8 Construction | 27 | |
| 11.9 Entire Agreement | 27 | |
| 11.10 Compliance with Laws | 27 | |
| 11.11 Severability | 27 | |
| 11.12 Cooperative Drafting | 27 | |
| 11.13 Order of Precedence | 28 | |
| 11.14 No Third-Party Beneficiaries | 28 | |
| Article 12 | SFMTA Specific Terms | 28 |
| 12.1 Large Vehicle Driver Safety Training Requirements | 28 | |
| Article 13 | Data and Security | 28 |
| 13.1 Management of City Data | 28 | |
| 13.1.1 Ownership of City Data | 28 | |
| 13.1.2 Use of City Data | 29 | |
| 13.1.3 Use of Generative Artificial Intelligence in Deliverables | 29 | |
| 13.1.4 Access to and Extraction of City Data | 29 | |
| 13.1.5 Backup and Recovery of City Data | 29 | |
| 13.1.6 Data Breach; Loss of City Data | 30 | |
| 13.2 Nondisclosure of Private; Proprietary or Confidential Information | 31 | |
| 13.2.1 Protection of Private Information | 31 | |
| 13.2.2 Proprietary or Confidential Information of City | 32 | |
| 13.2.3 Obligation of Confidentiality | 32 | |
| 13.2.4 Nondisclosure | 32 | |
| 13.2.5 Litigation Holds | 32 | |
| 13.2.6 Notification of Legal Requests | 32 | |
| 13.2.7 Cooperation to Prevent Disclosure of City Data | 33 | |
| 13.2.8 Remedies for Breach of Obligation of Confidentiality | 33 | |
| 13.2.9 Data Security | 33 | |
| 13.2.10 Data Privacy and Information Security Program | 34 | |
| 13.2.11 City’s Right to Termination for Deficiencies | 34 | |
| 13.2.12 Data Transmission | 35 | |
| 13.3 City’s Required Cybersecurity Review Assessment | 35 | |
| 13.4 Reserved. (Payment Card Industry (PCI) Requirements) | 36 | |
| 13.5 Protected Health Information | 36 | |
| 13.6 Reserved. (Business Associate Agreement) | 36 | |
| Article 14 | Force Majeure | 36 |
| 14.1 Liability | 36 | |
| 14.2 Duration | 36 | |
| 14.3 Effect | 36 | |
| 14.4 Disaster Recovery | 37 | |
| 14.5 Acknowlegdment of Obligations | 37 | |
| Article 15 | Appendices | 37 |
| 15.1 Appendices | 37 | |
| Article 16 | MacBride And Signature | 37 |
| 16.1 MacBride Principles -Northern Ireland | 37 |
| SFMTA P-648 (4-26) | iv | SFMTA-2026-43-LOC |
| EFJ | 4924-8253-4092 v.1 |
City and County of San Francisco Municipal Transportation Agency One South Van Ness Ave., 7th Floor San Francisco, California 94103
SOFTWARE AS A SERVICE AGREEMENT
BETWEEN THE CITY AND COUNTY OF SAN FRANCISCO AND
[Insert name of contractor] Contract No. SFMTA-2026-43-LOC
This Agreement is made as of ____________________, in the City and County of San Francisco (“City”), State of California, by and between [name of Contractor] (“Contractor”) and City, a municipal corporation, acting by and through its Municipal Transportation Agency (SFMTA).
Recitals A. The SFMTA wishes to procure from Contractor a Traffic Signal Central Management Software (CMS) solution that will be delivered as the hosted and licensed software defined in this Agreement as the “SaaS Application,” together with related hosting, support, maintenance, and other services defined herein as the “SaaS Services.” The SaaS application is a centralized platform that monitors the performance of networked traffic-signal-related devices and provides alerts based on customized settings to City staff.
B. Contractor represents and warrants that it is qualified to provide the SaaS Application and SaaS Services required by the SFMTA as set forth under this Agreement.
C. Contractor shall configure, implement, host, maintain, and support the SaaS Application in accordance with Appendix A (SaaS Implementation and Training Services), Appendix B (SaaS Application and Hosting Services), and Appendix E (Disaster Recovery Plan).
D. Contractor was competitively selected pursuant to an Invitation for Bids entitled IFB No. SFMTA-2026-43-LOC: Traffic Signal Central Management Software issued through Sourcing Event ID 0000012216.
E. This is a contract for Services and the Local Business Enterprise (“LBE”) subcontracting participation requirement for the Services has been waived pursuant to waiver CMD14BPREBID0002963.
F. This Agreement is for off-the shelf proprietary software (as defined by the 2023 PSC Policy of the Civil Service Commission) and, as such, is exempt from Civil Service Commission review.
Now, THEREFORE, the parties agree as follows:
Definitions The following definitions apply to this Agreement:
“Acceptance” means notice from the City to Contractor that the SaaS Application meets the specifications and requirements contained in the Documentation and Appendices. City’s Acceptance shall be governed by the procedures set forth in Section 4.3.
“Acceptance Period” means the period allocated by the City to test the SaaS Application to determine whether it conforms to the applicable specifications and, if appropriate, properly operates in the defined operating environment, is capable of running on a repetitive basis, and is otherwise in compliance with the service level obligations without failure.
“Agreement” means this contract document, including all Appendices, and all applicable City Ordinances and Mandatory City Requirements, which are specifically incorporated into this Agreement by reference as provided herein.
“Appendices” means the appendices listed in Article 15 (Appendices) herein.
“Artificial Intelligence” or “Artificial Intelligence Model” means an engineered or machine-based system that varies in its level of autonomy and that can, for explicit or implicit objectives, infer from the input it receives how to generate outputs that can influence physical or virtual environments.
“Artificial Intelligence System” means a machine-based system that is designed to operate with varying levels of autonomy and that may exhibit adaptiveness after deployment, and that, for explicit or implicit objectives, infers, from the input it receives, how to generate outputs such as predictions, content, recommendations, or decisions that can influence physical or virtual environments.
“Authorized User” means any person authorized by the City to access the City Portal and use the SaaS Application, including any City employee, contractor, or agent, or any other individual or entity authorized by the City.
“Back-Up Environment” means Contractor’s back-up Data Center for the SaaS Services.
“Business Hours” means 6:00am-6:00pm U.S. Pacific Time.
“CCO” means the SFMTA Contract Compliance Office.
“City” or “the City” means the City and County of San Francisco, a municipal corporation, acting by and through its Municipal Transportation Agency.
“City Data” or “Data” means all data collected, used, maintained, processed, stored, or generated by or on behalf of City in connection with this Agreement, including, without limitation, data resulting from use of the SaaS Service. City Data includes, without limitation, Confidential Information and Deliverable Data.
“City Portal” means a Contractor provided online secure portal that allows the City and its Authorized Users to log in to an area where they can view and download information or request assistance regarding the SaaS Application and Services.
“SFMTA’s Project Manager” means the individual specified by the City pursuant to Section 4.2.1 hereof, as the Project Manager authorized to administer this Agreement on the SFMTA’s behalf.
“CMD” means the Contract Monitoring Division of the City.
“Confidential Information” means confidential City information including, but not limited to, personal identifiable information (PII), protected health information (PHI), or individual financial information (collectively, Proprietary or Confidential Information) that is subject to local, state or federal laws restricting the use and disclosure of such information. Confidential Information includes, without limitation, City Data.
“Contractor” means [insert name and address of contractor].
“Contractor Project Manager” means the individual specified by Contractor pursuant to Section 4.2.1 hereof, as the Project Manager authorized to administer this Agreement on Contractor’s behalf.
“Contractor’s Website” means the Website that provides Authorized Users access to the SaaS Application and Services.
“C&P” means SFMTA Contracts and Procurement.
“Data Breach” means any access, destruction, loss, theft, use, modification or disclosure of City Data by an unauthorized party or that is in violation of the Agreement terms and/or applicable local, state or federal law.
“Data Center(s)” means a physical location within the United States where Contractor (or its subcontractor) houses and operates the hardware (including computers, computer servers, routers, and other related equipment and devices) on which Contractor (and or its subcontractor) hosts via the Internet the SaaS Application and City Data pursuant to this Agreement.
“Day” (whether or not capitalized) means a calendar day, unless otherwise indicated.
“Deliverable Data” means any data that is required to be delivered to the City as a Deliverable, or as a part of a Deliverable, under this Agreement.
“Deliverables” means Contractor’s or its subcontractors’ work product, including any partially completed work product and related materials, resulting from the Services provided by Contractor to City during the course of Contractor’s performance of the Agreement, including without limitation, the work product described in the “SaaS Implementation and Training Services,” attached as Appendix A.
“Director” means the Director of Transportation of the SFMTA or his or her designee.
“Disabling Code” means computer instructions or programs, subroutines, code, instructions, data or functions (including but not limited to viruses, worms, date bombs or time bombs), including but not limited to other programs, data storage, computer libraries and programs that self-replicate without manual intervention, instructions programmed to activate at a predetermined time or upon a specified event, and/or programs purporting to do a meaningful function but designed for a different function, that alter, destroy, inhibit, damage, interrupt, interfere with or hinder the operation of the City’s access to the SaaS Services through Contractor’s Website and/or Authorized User’s processing environment, the system in which it resides, or any other software or data on such system or any other system with which it is capable of communicating.
“Documentation” means technical publications provided by Contractor to the City relating to use of the SaaS Application, such as reference, administrative, maintenance, and programmer manuals.
“Effective Date” means the date upon which the City’s Controller certifies the availability of funds for this Agreement as provided in Section 3.1 “Generative Artificial Intelligence” means Artificial Intelligence that can generate derived synthetic content, such as text, images, video, and audio, that emulates the structure and characteristics of the Artificial Intelligence’s training data.
“Internet” means that certain global network of computers and devices commonly referred to as the “internet,” including, without limitation, the World Wide Web.
“Mandatory City Requirements” means those City laws set forth in the San Francisco Municipal Code, including the duly authorized rules, regulations, and guidelines implementing such laws, which impose specific duties and obligations upon Contractor.
“Open-Source Software” means software with either freely obtainable source code, a license for modification, or permission for free distribution.
“Party” or “Parties” means, respectively, the City and Contractor either individually or collectively.
“Performance Credit” means credit due to the City by Contractor with regard to Contractor’s service level obligations in Appendix D (Service Level Obligations).
“Personal Identifiable Information (PII)” means information that identifies, relates to, describes, is reasonably capable of being associated with, or could reasonably be linked, directly or indirectly, with a particular individual or household. Personal information includes, but is not limited to, the following if it identifies, relates to, describes, is reasonably capable of being associated with, or could be reasonably linked, directly or indirectly, with a particular individual or household as further defined in the California Consumer Privacy Act.
“Precedence” means that, notwithstanding the terms of any other document executed by the Parties as a part of this Agreement, the terms of this Agreement shall control over any discrepancy, inconsistency, gap, ambiguity, or conflicting terms set forth in any other Contractor pre-printed document.
“Preexisting Data” means data owned by either Party that exists prior to the Agreement start date.
“SaaS Application” means the licensed and hosted computer program and associated documentation, as listed in this Agreement and Appendices, and any modification or Upgrades or modifications to the program(s), residing in Contractor’s servers that provides the SaaS Services that may be accessed by Authorized Users through the Internet. The SaaS Application may include Contractor-provided Third-Party Software.
“SaaS Application Error” means any failure of SaaS Software to conform in all material respects to the requirements of this Agreement or Contractor’s published specifications.
“SaaS Application Error Correction” means either a modification or addition that, when made or added to the SaaS Software, brings the SaaS Software into material conformity with the published specifications, or a procedure or routine that, when observed in the regular operation of the SaaS Software, avoids the practical adverse effect of such nonconformity.
“SaaS Application Patch” means an update to the SaaS Application comprised of code inserted (or patched) into the code of the SaaS Application, and which may be installed as a temporary fix between full releases of a SaaS Application Revision or SaaS Application Version. Such a patch may address a variety of issues including without limitation fixing a Software bug, installing new drivers, addressing new security vulnerabilities, addressing software stability issues, and upgrading the Software. SaaS Application Patches are included in the annual payments made by City to Contractor for the SaaS Services under this Agreement.
“SaaS Application Revision” means an update to the current SaaS Application Version of the SaaS Software code that consists of minor enhancements to existing features and code corrections. SaaS Application Revisions are provided and included with the annual service payments made by City to Contractor for the SaaS Services.
“SaaS Application Version” means the base or core version of the SaaS Software that contains significant new features and significant fixes and is available to the City. SaaS Application Versions may occur as the SaaS Software architecture changes or as new technologies are developed. The nomenclature used for updates and upgrades consists of major, minor, build, and fix and these correspond to the following digit locations of a release, a,b,c,d, an example of which would be NCC 7.4.1.3, where the 7 refers to the major release, the 4 refers to the minor release, the 1 refers to the build, and the 4 refers to a fix. All SaaS Application Versions are provided and included as part of this Agreement upon request or approval from City for the upgrade.
“SaaS Implementation and Training Services” means the services by which Contractor will implement all necessary Software configurations and modules necessary to make the SaaS Application available and accessible to the City.
“SaaS Issue” means a problem with the SaaS Services identified by the City that requires a response by Contractor to resolve.
“SaaS Maintenance Services” means the activities to investigate, resolve SaaS Application and Services issues and correct product bugs arising from the use of the SaaS Application and Services in a manner consistent with the published specifications and functional requirements defined during implementation.
“SaaS Services” means the Services Contractor performs to host the SaaS Application to provide the functionality described in the Documentation.
“SaaS Severity Level” means a designation of the effect of a SaaS Issue on the City. The severity of a SaaS Issue is initially defined by the City and confirmed by Contractor. Until the SaaS Issue has been resolved, the Severity Level may be raised or lowered based on Contractor’s analysis of impact to business.
“San Francisco Municipal Transportation Agency” or “SFMTA” means the agency of City with jurisdiction over all surface transportation in San Francisco, as provided under Article VIIIA of the City’s Charter.
“Scheduled SaaS Maintenance” means the time (in minutes) during the month, as measured by Contractor, in which access to the SaaS Services is scheduled to be unavailable for use by City due to planned system maintenance and major version upgrades.
“Services” means the work performed by Contractor under this Agreement as specifically described in Appendix A (SaaS Implementation and Training Services) and Appendix B (SaaS Application and Hosting Services), and Appendix E (Disaster Recovery Plan), including all services, labor, supervision, materials, equipment, actions, and other requirements to be performed and furnished by Contractor under this Agreement.
“SFMTA Project Manager” means the individual specified by the SFMTA pursuant to Section 4.2.1 hereof, as the Project Manager authorized to administer this Agreement on the City’s behalf.
“Software” means the SaaS Applications and any Contractor-provided Third-Party Software. All Software, revisions and versions provided by Contractor shall be subject to the terms and conditions of this Agreement, including any amendments thereto.
“Successor Service Provider” means a new service provider, if any, selected by City in the event the SaaS Services are terminated under this Agreement.
“Third-Party Software” means any third-party software included as part of the SaaS Application provided to the City under this Agreement described in Appendix B, “SaaS Application and Hosting Services.”
“Training data” means data used for training an AI system through fitting its learnable parameters.
“Transition Services” means that assistance reasonably requested by City to effect the orderly transition of the SaaS Services, in whole or in part, to City or to Successor Service Provider.
Term of the Agreement Term. The term of this Agreement shall commence on the Effective Date and expire five years from the Effective Date, unless earlier terminated as otherwise provided herein.
Options to Extend. The SFMTA has the option to extend the term of this Agreement for a period of four additional years. The SFMTA may exercise this option at the Director of Transportation’s sole and absolute discretion by modifying this Agreement as provided in Section 11.5, “Modification of this Agreement.” Extensions may be for the whole or partial period provided for above.
Financial Matters Certification of Funds; Budget and Fiscal Provisions Termination in the Event of Non-Appropriation. This Agreement is subject to the budget and fiscal provisions of Section 3.105 of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to the City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. The City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. The City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement.
THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.
Maximum Costs. The City’s payment obligation to Contractor cannot at any time exceed the amount certified by the Controller for the purpose and period stated in such certification. Absent an authorized emergency per the City Charter or applicable Code, no City representative is authorized to offer or promise, nor is the City required to honor, any offered or promised payments to Contractor under this Agreement in excess of the certified maximum amount without the Controller having first certified the additional promised amount and the Parties having modified this Agreement as provided in Section 11.5, “Modification of this Agreement.”
Authorization to Commence Work. Contractor shall not commence any work under this Agreement until the City has issued formal written authorization to proceed, such as a purchase order, task order or notice to proceed. Such authorization may be for a partial or full scope of services.
Compensation Contract Not to Exceed Amount. The amount of this Agreement shall not exceed [insert whole dollar amount in numbers and words in bold -- no pennies and no “.00”]. This contract not to exceed amount is based on the prices submitted by Contractor in its Bid Sheet, which are incorporated into Appendix C, “Calculation of Charges.” The City shall not be liable for interest or late charges for any late payments. The City will not honor minimum service order charges for any Services covered by this Agreement.
One-Time Costs. Contractor shall be compensated for the one-time costs identified as Items 1 through 4 in Appendix C at the fixed prices set forth therein. These items consist of the Project Kick-Off Meeting, Implementation and Integration, System Documentation, and Training. Contractor may invoice the City for each item upon satisfactory completion and acceptance by the SFMTA of the applicable item or Deliverable. For any item consisting of more than one separately identified Deliverable or milestone, Appendix C may provide for payment upon satisfactory completion and acceptance of each such Deliverable or milestone.
Annual CMS License Fees. Contractor shall be compensated for the Traffic Signal Central Management Software license at the fixed annual prices identified as Item 5 in Appendix C. The applicable annual fee for each Contract Year shall be the price bid by Contractor for that Contract Year. The first annual CMS License Fee shall become payable upon Final Acceptance of the CMS. Contractor may invoice the SFMTA for the applicable annual fee upon Final Acceptance and thereafter on each anniversary of Final Acceptance during the term of the Agreement. The annual license fee shall include all modules, features, licenses, and other items required by this Agreement and the Solicitation to provide the SaaS Application.
Annual Services Fees. Contractor shall be compensated for ongoing support, maintenance, updates, and other Services identified as Item 6 in Appendix C at the fixed annual prices set forth therein for each Contract Year. The Annual Services Fee for each Contract Year shall be payable at the same time and in the same manner as the Annual CMS License Fee under subsection (b), regardless of the number of support hours used during that Contract Year.
Firm Pricing. The prices set forth in Appendix C are fixed and shall not be subject to escalation during the applicable Contract Year or any option year, except as expressly provided in this Agreement. Exercise of an option to extend the Agreement does not obligate the City to pay any amount other than the applicable prices set forth in Appendix C for the option year exercised.
Payment Limited to Satisfactory Services and Delivery of Goods. Contractor is not entitled to any payments from City until the SFMTA approves the Services delivered. Payments to Contractor by the SFMTA shall not excuse Contractor from its obligation to replace the unsatisfactory Services even if the unsatisfactory character was apparent or could have been detected at the time such payment was made. Non-conforming Services may be rejected by the SFMTA and in such case must be replaced by Contractor without delay at no cost to the SFMTA.
Withhold Payments. If Contractor fails to provide the Services in accordance with Contractor’s obligations under this Agreement, the SFMTA may withhold any and all payments due to Contractor until such failure to perform is cured, and Contractor shall not stop work as a result of City’s withholding of payments as provided herein.
Invoicing. Contractor shall invoice the SFMTA for the one-time Services and Deliverables no later than 30 days after their completion and acceptance by the SFMTA, and for Annual CMS License Fees and Annual Services Fees in accordance with Section 3.3. Contractor shall submit the last invoice of the fiscal year no later than 15 days before the end of July. Invoices submitted by Contractor must be in a form acceptable to the Controller and the SFMTA and include a unique invoice number and a specific invoice date. Payment shall be made by the SFMTA as specified in Section 3.3.6, or in such alternate manner as the Parties have mutually agreed upon in writing. All invoices must show the PeopleSoft Purchase Order ID Number, PeopleSoft Supplier Name and ID, Item numbers (if applicable), complete description of Services performed, sales/use tax (if applicable), contract payment terms and contract price. Invoices that do not include all required information or contain inaccurate information will not be processed for payment.
LBE Payment and Utilization Tracking System. Contractor shall within ten (10) business days of City’s payment of any invoice to Contractor, confirm its payment to subcontractors using the B2GNow System (https://sfmta.diversitycompliance.com/) unless instructed otherwise by CCO.
Payment Terms Payment Due Date. Unless the SFMTA notifies Contractor that a dispute exists, Payment shall be made within 30 calendar days, measured from (1) the rendering of the Services or (2) the date of receipt of the invoice, whichever is later. Payment is deemed to be made on the date City issued a check to Contractor or, if Contractor agreed to electronic payment, the date City has posted electronic payment to Contractor.
Reserved. (Payment Discount Terms) Reserved. (Grant Funded Contracts) Audit and Inspection of Records. Contractor agrees to maintain and make available to the City, during regular business hours, accurate books and accounting records relating to its Services. Contractor will permit City to audit, examine and make copies of such books and records, and to make audits of all invoices, materials, payrolls, records or personnel and other data related to all other matters covered by this Agreement, whether funded in whole or in part under this Agreement. Contractor shall maintain such data and records in an accessible location and condition for a period of not less than five years after final payment under this Agreement or until after final audit has been resolved, whichever is later. Contractor shall include the same audit and inspection rights and record retention requirements in all subcontracts.
Submitting False Claims. The full text of San Francisco Administrative Code Section 21.35, including the enforcement and penalty provisions, is incorporated into this Agreement. Any contractor or subcontractor who submits a false claim shall be liable to the City for the statutory penalties set forth in that section.
SaaS Services and Resources SaaS Licensed Software. Subject to the terms and conditions of this Agreement, Contractor hereby grants the City and Authorized Users a renewable, non-exclusive, royalty-free license to access and use the SaaS Application and SaaS Services within the United States during the term of this Agreement and any extensions thereof.
Click-Wrap Disclaimer. No “click to accept” agreement that may be required for the City and/or Authorized Users’ access to the SaaS Services or Contractor’s Website and no terms of use, terms of service, or privacy policy referenced therein or conditioned for use of the SaaS Services or Contractor’s Website shall apply. Only the provisions of this Agreement as amended from time to time shall apply to the City and/or Authorized Users for access thereto and use thereof. The Parties acknowledge that the City and/or each Authorized User may be required to click “Accept” as a condition of access to the SaaS Services through Contractor’s Website, but the provisions of such “click to accept” agreement and other terms (including terms of use, terms of service, and privacy policy) contained or referenced therein shall be null and void for the City and/or each such Authorized User. The foregoing does not apply to the City’s own click-wrap agreements in the event the City chooses to have Contractor include terms of use, terms of service, privacy policies, or similar requirements drafted and approved by the City.
SaaS Application Title. The City acknowledges that title to each SaaS Application and SaaS Services shall at all times remain with Contractor, and that the City has no rights in the SaaS Application or SaaS Services except those expressly granted by this Agreement.
Authorized APIs. The City shall also be permitted to access and use Contractor’s SaaS Application Program Interfaces (APIs) when commercially available to develop and modify, as necessary, macros and user interfaces for use with any existing or future City systems and infrastructure. For purposes of this Agreement, such development shall be deemed an authorized modification and does not violate the licenses granted under this Agreement but will not be supported by Contractor unless provided for in this Agreement. Functionality and compatibility of the City developed macros will be sole responsibility of the City. Any such macros or user interfaces developed by the City shall become the property of the City. All flat-file exchanges will be over an encrypted file transport service (ftps/vsftpd/scp/sftp) to a secure private ftp site.
Proprietary Markings. The City agrees not to remove or destroy any proprietary markings or proprietary legends placed upon or contained within the SaaS Application or any related materials or Documentation.
Project Managers; Services Contractor Agrees to Perform Project Managers. Contractor and The SFMTA shall each designate a Project Manager, who shall be accessible by telephone throughout the duration of the Agreement and shall be available 9 a.m. to 5 p.m. (Pacific Standard Time), Monday through Friday, excluding City-designated holidays. These hours may be adjusted by mutual agreement of the SFMTA and Contractor. Contractor shall use its best efforts to maintain the same Project Manager throughout the duration of the Agreement. However, if Contractor needs to replace its Project Manager, Contractor shall provide the SFMTA with written notice thereof at least forty-five (45) days prior to the date the Project Manager shall be replaced. Notwithstanding the foregoing, Contractor will have the right to appoint temporary Project Managers in connection with short-term unavailability, sick leave or reasonable vacations. Contractor shall notify the SFMTA in advance of any such temporary appointments. The SFMTA may require Contractor to replace its Project Manager, by giving Contractor notification thereof and the SFMTA’s objective reasons therefor.
| Contractor’s Project Manager: | [Name] | |
| [Address] | ||
| [e-mail] | ||
| [phone number] |
| SFMTA’s Project Manager: | Liliana Ventura, PE | |
| Engineer | ||
| Streets Division | ||
| Liliana.Ventura@sfmta.com | ||
| (415) 646-2708 |
Services Contractor Agrees to Perform. During the Term of this Agreement, Contractor shall perform all of the Services described in the Agreement, including but not limited to, Appendix A (SaaS Implementation and Training Services), Appendix B (SaaS Application and Hosting Services), and Appendix D (Service Level Obligations). Officers and employees of the City are not authorized to request, and the City is not required to compensate Contractor for Services beyond those stated.
Maintenance and Support. Contractor shall provide Maintenance/Support in accordance with Appendix B (SaaS Application and Hosting Services). Maintenance and Support Services include the provision of upgrades and a service desk, during the term of this Agreement for the SaaS Application(s).
Hosting. Contractor shall provide hosting in accordance with Appendix B (SaaS Application and Hosting Services), including the following:
Hosting Infrastructure. Contractor shall provide all hosting infrastructure, including, but not limited to, hardware, software and other equipment, at Contractor’s hosting site as required to provide hosting and deliver the SaaS Application and Services.
Security. Contractor shall ensure that any electronic transmission or exchange of City Data between the Services and Authorized Users will be encrypted using current industry standards. Contractor shall ensure that all City Data exchanged between the Parties is used solely for the purposes described in this Agreement. Contractor shall not distribute, repurpose, or share City Data across any other applications, environments, or business units of Contractor not involved in administering this Agreement, unless expressly permitted herein. Remote access to view City Data for technical support purposes from outside the United States is prohibited unless the City gives prior written approval, and only if (1) City Data remains hosted exclusively in Data Centers located in the United States; and (2) no City Data is downloaded to or stored on any hardware outside U.S.-based Data Centers.
Access. Contractor shall provide Authorized Users 24/7 access to the SaaS Application(s).
Disaster Recovery and Business Continuity. Contractor shall provide Disaster Recovery Services and assist with business continuity as described in Section 14.4 and Appendix E.
Service Level Obligations. Contractor shall comply with the support (24/7 service desk) and Service Level Obligations described in Appendix D.
Acceptance Testing; Document Delivery; Training After the SFMTA has obtained access to the SaaS Application and Services, and subsequent to each SaaS Application version upgrade, revision and patch as further outlined in Appendix B, the SFMTA and Contractor shall conduct user acceptance testing as outlined in Appendix A and Appendix B, as the case may be, to verify that the SaaS Application and Services substantially conform to the specifications and the SFMTA’s requirements contained therein. In the event that the SFMTA determines that the SaaS Services do not meet such specifications, the SFMTA shall notify Contractor in writing, and Contractor shall modify or correct the SaaS Services so that it satisfies the Acceptance criteria. The date of Acceptance will be that date upon which the SFMTA provides Contractor with written notice of satisfactory completion of Acceptance testing. If SFMTA notifies Contractor after the Acceptance Testing Period that the SaaS Services do not meet the Acceptance criteria outlined in Appendices A and B, as the case may be, then the SFMTA shall be entitled to terminate this Agreement in accordance with the procedures specified in Article 8 herein, and shall be entitled to a full refund of any fees paid as part of this Agreement prior to termination.
Document Delivery. Contractor shall make available Documentation in electronic format for the SaaS Application and Services at the time it gives the SFMTA access to the SaaS Application and Services. The Documentation shall accurately and completely describe the functions and features of the SaaS Application and Services, including all subsequent revisions thereto. The Documentation shall be understandable by a typical end user and shall provide Authorized Users with sufficient instruction such that an Authorized User can become self-reliant with respect to access and use of the SaaS Application and Services. The SFMTA shall have the right to make any number of additional copies of the Documentation at no additional charge. The SFMTA may withhold its issuance of the notice of final Acceptance until the SFMTA receives the completed Documentation.
Qualified Personnel. Contractor represents and warrants that it is qualified to perform the Services for which it is contracted to provide through this Agreement, and that all Services will be performed by competent personnel with the degree of skill and care required by current and sound professional procedures and practices under the supervision of, and in the employment of, Contractor (or Contractor’s authorized subcontractors) to perform the Services. Contractor will comply with the City’s reasonable requests regarding assignment and/or removal of personnel, but all personnel, including those assigned at City’s request, must be supervised by Contractor. Contractor shall commit adequate resources for timely completion within the project schedule specified in this Agreement.
Subcontracting. Contractor may subcontract portions of the Services only upon prior written approval of the SFMTA. Contractor is responsible for its subcontractors throughout the course of the work required to perform the Services. All subcontracts must incorporate the terms of Article 10 “Additional Requirements Incorporated by Reference” of this Agreement, unless inapplicable. Neither Party shall, on the basis of this Agreement, contract on behalf of, or in the name of, the other Party. Any agreement made in violation of this provision shall be null and void. City’s execution of this Agreement constitutes its approval of the subcontractors listed below and/or in Appendices.
Independent Contractor; Payment of Employment Taxes and Other Expenses Independent Contractor. For the purposes of this Section 4.6, “Contractor” shall be deemed to include not only Contractor, but also any agent or employee of Contractor. Contractor acknowledges and agrees that, at all times, Contractor is an independent contractor and is wholly responsible for the manner and means by which it performs the Services and work required under this Agreement. Contractor, including its agents and employees will not represent or hold itself/themselves out to be employees of the City at any time. Contractor shall not have employee status with the City, nor be entitled to participate in any plans, arrangements, or distributions by the City pertaining to or in connection with any retirement, health or other benefits that the City may offer its employees. Contractor is liable for its acts and omissions. Contractor shall be responsible for all obligations and payments, whether imposed by federal, state or local law, including, but not limited to, FICA, income tax withholdings, unemployment compensation, insurance, and other similar responsibilities related to Contractor’s performing Services and work, or any agent or employee of Contractor providing same. Nothing in this Agreement shall be construed as creating an employment or agency relationship between the City and Contractor or any of its agents or employees. Contractor agrees to maintain and make available to the City, upon request and during regular business hours, accurate books and accounting records demonstrating Contractor’s compliance with Section 4.6. Should the City determine that Contractor is not performing in accordance with the requirements of Section 4.6, the City shall provide Contractor with written notice of such failure. Within five (5) business days of Contractor’s receipt of such notice, and in accordance with Contractor policy and procedure, Contractor shall remedy the deficiency. Notwithstanding, if the City believes that an action of Contractor warrants immediate remedial action by Contractor, the City shall contact Contractor and provide Contractor in writing with the reason for requesting such immediate action.
Payment of Employment Taxes and Other Expenses. Should City, in its discretion, or a relevant taxing authority such as the Internal Revenue Service or the State Employment Development Division, or both, determine that Contractor is an employee for purposes of collection of any employment taxes, the amounts payable under this Agreement shall be reduced by amounts equal to both the employee and employer portions of the tax due (and offsetting any credits for amounts already paid by Contractor which can be applied against this liability). The City shall then forward those amounts to the relevant taxing authority. Should a relevant taxing authority determine a liability for past Services performed by Contractor for City, upon notification of such fact by City, Contractor shall promptly remit such amount due or arrange with City to have the amount due withheld from future payments to Contractor under this Agreement (again, offsetting any amounts already paid by Contractor which can be applied as a credit against such liability). A determination of employment status pursuant to Section 4.6 shall be solely limited to the purposes of the particular tax in question, and for all other purposes of this Agreement, Contractor shall not be considered an employee of the City. Notwithstanding the foregoing, Contractor agrees to indemnify and hold harmless the City and its officers, agents and employees from, and, if requested, shall defend them against any and all claims, losses, costs, damages, and expenses, including attorneys’ fees, arising from Section 4.6.
Assignment. The Services to be performed by Contractor are personal in character. This Agreement may not be directly or indirectly assigned, novated, or otherwise transferred unless first approved by the SFMTA by written instrument executed and approved in the same manner as this Agreement. Any purported assignment made in violation of this provision shall be null and void.
Reserved. (Liquidated Damages)
Insurance; Indemnity; and Warranties Insurance Required Coverages. Without in any way limiting Contractor’s liability pursuant to the “Indemnification” section of this Agreement, Contractor must maintain in force, during the full term of the Agreement, insurance in the following amounts and coverages:
Commercial General Liability Insurance with limits not less than $1,000,000 each occurrence for Bodily Injury and Property Damage, including Contractual Liability, Personal Injury, Products and Completed Operations.
Reserved. (Commercial Automobile Liability Insurance) Workers’ Compensation Insurance, in statutory amounts, with Employers’ Liability Limits not less than $1,000,000 each accident, injury, or illness.
Reserved. (Professional Liability Insurance) Technology Errors and Omissions Liability Insurance, with limits of $5,000,000 for each claim and each loss. The policy shall at a minimum cover professional misconduct or lack of the requisite skill required for the performance of Services defined in this Agreement and shall also provide coverage for the following risks:
Network security liability arising from the unauthorized access to, use of, or tampering with computers or computer systems, including hacker attacks; and Liability arising from the introduction of any form of malicious software including computer viruses into or otherwise causing damage to City’s or third person’s computer, computer system, network, or similar computer related property and the data, software, and programs thereon.
Cyber and Privacy Liability Insurance with limits of not less than $5,000,000 per claim. Such insurance shall include coverage for liability arising from theft, dissemination, and/or use of confidential information, including but not limited to, bank and credit card account information or personal information, such as name, address, social security numbers, PHI or other PII, stored or transmitted in electronic form.
Additional Insured The Commercial General Liability Insurance policy must include as Additional Insured the City and County of San Francisco and, its Officers, Agents, and Employees.
Reserved. (Commercial Automobile Liability Insurance) Waiver of Subrogation. The Workers’ Compensation Insurance policy(ies) shall include a waiver of subrogation in favor of the City for all work performed by Contractor, and its employees, agents and subcontractors.
Primary Insurance The Commercial General Liability Insurance policy shall provide that such policies are primary insurance to any other insurance available to the Additional Insureds, with respect to any claims arising out of this Agreement, and that the insurance applies separately to each insured against whom claim is made or suit is brought.
The Commercial Automobile Liability Insurance policy shall provide that such policies are primary insurance to any other insurance available to the Additional Insureds, with respect to any claims arising out of this Agreement, and that the insurance applies separately to each insured against whom claim is made or suit is brought.
Other Insurance Requirements Thirty (30) days’ advance written notice shall be provided to the City of cancellation, intended non-renewal, or reduction in coverages, except for non-payment for which no less than ten (10) days’ notice shall be provided to the City. Notices shall be sent to the City address set forth in Section 11.1 entitled “Notices to the Parties.”
Should any of the required insurance be provided under a claims-made form, Contractor shall maintain such coverage continuously throughout the term of this Agreement and, without lapse, be maintained for a period of three (3) years beyond the expiration of this Agreement, to the effect that, should occurrences during the Agreement term give rise to claims made after expiration of the Agreement, such claims shall be covered by such claims-made policies.
Should any of the required insurance…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .