Quote — Riverside City Council, August 6, 2024

Page 2 of 21 ends

Contents1.0 PURPOSE ......................................................................................................................... 32.0 PROJECT OVERVIEW .......................................................................................................... 3 3.0 CITY OF RIVERSIDE RESPONSIBILITIES AND ASSUMPTIONS .................................................... 3 4.0 SOFTWARE-AS-A-SERVICE / COMMERCIAL-OFF-THE-SHELF ..................................................... 5 5.0 PROJECT SCOPE................................................................................................................ 6 6.0 TASKS TO BE ACCOMPLISHED/FUNCTIONS TO BE PERFORMED ............................................ 7 1.0 Preparation ......................................................................................................................................... 7 2.0 Plan and Design ................................................................................................................................. 8 3.0 Configuration ..................................................................................................................................... 8 4.0 User Acceptance Testing .................................................................................................................... 9 5.0 Training .............................................................................................................................................. 9 6.0 Go-Live ............................................................................................................................................. 10 7.0 Products and Services .................................................................................................. 10 8.0 Out of Scope for this project .......................................................................................... 19 9.0 eCivis RESPONSIBLITIES ............................................................................................... 19 10.0 eCivis PROJECT MANAGEMENT CONTACTS ..................................................................... 20 11.0 Project Schedule and Key Milestones .............................................................................. 20 12.0 COST ASSUMPTIONS ................................................................................................... 20 13.0 APPENDIX A................................................................................................................ 21 Copyright © 2017-2020 eCivis. All rights reserved.

Page 3 of 21 ends

1.0 PURPOSEThis Statement of Work (SOW) ensures expectations are documented and understood by all entities engaged in this project. The following sections include: project overview, responsibilities and assumptions, software-as-a-service/commercial-off-the-shelf, project scope, tasks to be accomplished/functions to be performed, products and services, out of scope for this project, eCivis responsibilities, eCivis project management contacts, project schedule and key milestones, and cost assumptions. 2.0 PROJECT OVERVIEW To meet the goals of the City of Riverside eCivis will rapidly deploy eCivis cloud-hosted, Commercial-off-the-shelf (COTS) Software-as-a-Service (SaaS) full lifecycle grants management system. eCivis will implement its proprietary grants management systems configured for CITY OF RIVERSIDE authorized internal users to administer the grants management process and provide CITY OF RIVERSIDE with direct management, accountability and oversight of federal funds in compliance with 2 CFR 200. eCivis will also include services for its solution with all relevant systems without impact to existing processes, developing, and providing appropriate comprehensive training of personnel, and all other applicable implementation and support services. 3.0 CITY OF RIVERSIDE RESPONSIBILITIES AND ASSUMPTIONSThe projected deployment date and project implementation start date will be determined after a contract is executed after which CITY OF RIVERSIDE can commit to the implementation schedule and the following responsibilities and assumptions: 1. CITY OF RIVERSIDE shall provide a designated single point of contact for the duration of planning and implementation engagement. 2. CITY OF RIVERSIDE shall engage in bi-weekly status meetings with eCivis to go over current progress, issues, resolutions, and other agenda. 3.CITY OF RIVERSIDE shall provide all required data calls by the dates agreed upon in the project plan Copyright © 2017-2020 eCivis. All rights reserved.

Page 4 of 21 ends

Staffing ROLERESPONSIBILITYNAME, TitleContact InformationMailing AddressEmail TelephoneGMS IMPLEMENTATION TEAMeCivis Project Manager Responsible for planning, executing, monitoring, controlling, and closing the project. Responsible for the day-to-day management, coordination, planning, problem solving, and implementation of requirements to achieve task completion as presented in the Integrated Project Plan. Accountable for the project scope, project team, resources, and success of the project. eCivis Solution Architect SME on GMS System, Responsible for System Configuration. eCivis TrainerResponsible training, coordinating the training schedule, providing training materials. CITY OF RIVERSIDE Grants Team Lead Primary decision maker and contact for business requirements and deployment planning CITY OF RIVERSIDE Grants Team SMEReview and approve business and systems configuration requirements CITY OF RIVERSIDE PMO Project Manager Co-responsibility for the Integrated GMS Project Plan and Reporting. Maintain SharePoint project page. Track and report budget status. SUPPORT POST-IMPLEMENTATION TEAM eCivis Executive Sponsor Responsible for ensuring that the project's goals are aligned with the needs of the customer. Champions the project by Copyright © 2017-2020 eCivis. All rights reserved.

Page 5 of 21 ends

ROLE RESPONSIBILITY NAME, Title Contact InformationMailing AddressEmailTelephonegathering support, communicating goals, and overcoming resistance. Provide ongoing direction to the project team during a project's lifecycle.eCivis Sr. Customer Success ManagerResponsible for the ongoing user support and adoption of GMS. eCivis Customer Support Lead Provide technical support to GMS users. CITY OF RIVERSIDE Technical Support Manager IT infrastructure support CITY OF RIVERSIDE Application SupportIT application support CITY OF RIVERSIDE Help DeskSupport GMS trouble management processes and application performance reporting. 4.0 SOFTWARE-AS-A-SERVICE / COMMERCIAL-OFF-THE-SHELFeCivis is a cloud-hosted, Commercial-off-the-shelf (COTS) SaaS grants management platform. The system is compatible with any hardware device that provides Internet access via a modern web browser and requires minimal internal IT support beyond the initial implementation.eCivis is specifically built for managing the full grants management lifecycle and will standardize and streamline processes so that CITY OF RIVERSIDE staff can save time, Copyright © 2017-2020 eCivis. All rights reserved.

Page 6 of 21 ends

increase transparency, reduce redundancies, data entry, mitigate compliance risk, and improve organizational collaboration and knowledge.eCivis provides ongoing innovation with continual updates, leading to: Consistently updated software features and functions. Improved data sharing with systemsUniform Grant Guidance training, indirect cost support and fund maximization, and access to additional learning resources Improved internal control and regulatory requirements compliance 5.0 PROJECT SCOPEThis project will implement eCivis’ grants management solution for CITY OF RIVERSIDE. The solution will be implemented across all applicable agencies and departments performing grant management functions. eCivis’ project approach includes a Master Strategic Timeline that will be finalized upon contract execution. The project approach is conducted in a hybrid waterfall agile phased-gate approach. A phased - gate approach allows for quick added software value, concurrent active phases, and early user adoption while ensuring critical dependencies are completed. The phases outlined below will support the Project Scope from initial Preparation to Full Product Adoption - Go Live. All Project Scope areas will be incorporated within the Strategic Timeline and will be discussed in more depth to address deliverables and descriptions.eCivis proposes the following Statement of Work (SOW): 1. Preparationa. Pre Kick Off Meetingi. Review Project Plan Components ii. Communicate Master Project TimeLineiii. Provide Data Call forms b. Project Kick Off Meeting2. Plan and Design a. Data Gathering3. Configuration Copyright © 2017-2020 eCivis. All rights reserved.

Page 7 of 21 ends

a. Grantee Pre/Post-award management 4. User Acceptance Testinga. Review all implementation components built, configured, migrated and imported during the build and configuration stage are delivered and operational.5. Project Closeout a. Remote training, training manuals and support6. Go Live 6.0 TASKS TO BE ACCOMPLISHED/FUNCTIONS TO BE PERFORMED During each phase, work proceeds in several areas and will be performed by both CITY OF RIVERSIDE and eCivis. 1.0 PreparationTask Deliverable Description Preparation:Pre-Kickoff Meeting Tasks Pre KickoffPresentation Document Master Project Timeline All data call forms eCivis and CITY OF RIVERSIDE to review master project timeline, scope of work and identify risks. eCivis will email master project timeline to CITY OF RIVERSIDE eCivis will email pertinent eCivis staff contact information to CITY OF RIVERSIDE . eCivis will schedule required meetings with CITY OF RIVERSIDE eCivis will provide CITY OF RIVERSIDE with the following data call forms which are due back to eCivis by the time agreed upon in the project timeline: o Add User/Department form (Excel Template) o Data Migration Information eCivis will record Project Goals and Objectives determined during Pre Kick Off Meeting Copyright © 2017-2020 eCivis. All rights reserved.

Page 8 of 21 ends

Project Kickoff Meeting Project Kickoff Presentation Document Assemble Teams (eCivis and CITY OF RIVERSIDEresources)Conduct a formal Project Kick-Off meeting Review Project Objectives and Master Project Timeline Record Project Goals and Objectives determined during Kick Off Meeting 2.0 Plan and Design Task Deliverable Description Data Migration CITY OF RIVERSIDE to provide ALL completed data call forms to eCivis CITY OF RIVERSIDE staff has compiled and completed the following data call forms for eCivis to validate prior to configuration of their Grants Network account: Project/Grant Information (CITY OF RIVERSIDE compiled all active award data to be migrated to eCivis) Data Integration CITY OF RIVERSIDE to provide ALL completed data call forms to eCivis CITY OF RIVERSIDE staff has completed the mapping to eCivis integration fields and provided test data Completed mapping form Test data delivered for 13 integration fields Script created for auto creation/delivery Department Structure CITY OF RIVERSIDE to provide ALL completed data call forms to eCivis CITY OF RIVERSIDE staff has compiled and completed the following data call forms for eCivis to validate prior to configuration of their Grants Network account: User information and Department structure 3.0 ConfigurationTask Deliverable Description Copyright © 2017-2020 eCivis. All rights reserved.

Page 9 of 21 ends

SSO Setup Implement SSO setupData Migration eCivis will load current and active grant award data from the completed Data Migration Worksheet into eCivis. Data Integration Begin regular import on a scheduled basisConfigureeCivis will load new users and configure the eCivis system4.0 User Acceptance TestingTask Deliverable Description Validate imported data Readiness Assessment CITY OF RIVERSIDE staff will review and validate all implementation components built, configured, migrated, and imported during the build and configuration stage are delivered and operational. 5.0 TrainingTask Deliverable Description User Training Training Manuals, Virtual User Training Communicate ongoing support details eCivis will work with CITY OF RIVERSIDE to complete the following initiatives: *Provide standard user guides and training resources Provide training for licensed users of Grants Network Ongoing support details *CITY OF RIVERSIDE will provide and maintain training resources unique to their specific use case and business processes.

Page 10 of 21 ends

6.0 Go-LiveTask Deliverable Description Go LiveFinal Readiness Assessment Go Live Success and Support Meeting – eCivis will continue to support CITY OF RIVERSIDE 7.0 Products and Services PRODUCT(S): Grantee Pre-Post Award SERVICE: Pull Integration (Client FMS to eCivis) INTRODUCTION The purpose of this integration is to import grant expenditure and revenue data to align with grant awarded budgets. Grant expenditures will be aligned at the “GL Code” level to identify specific grant transactions expended against an awarded grant budget category. DESCRIPTION 1. FMS data will be mapped to the following eCivis fields: eCivis Grants Network data field: Required: Definition: extGrantID Yes Unique identifier for a single grant in the financial systemextGrantName No Name or description of the grant in the financial systemextProjectID Yes Unique identifier for a single project in the financial system Copyright © 2017-2020 eCivis. All rights reserved.

Page 11 of 21 ends

extProjectName No Name or description of the project in the financial systemtransID Yes Unique identifier for each transaction, usually generated in the client’s financial system transNameYesName or description from the financial system. Could be a vendor name, or some other piece of data defining the transaction transPostDateYesEntry date, date of when the actual entry posted in the financial system, it can be entered manually or automatically generated by the system transPerfPeriodStartDate No Date of receipt, or date that goods or services was provided transPerfPeriodEndDate No Date of receipt, or date that goods or services was provided accountNumber Yes G/L code or account code to reference budget line item of transaction dollarAmount Yes Amount of transaction dollarClass Yes Category of the dollar amount. USE "105" for each transaction related to grant expenditures and "201" for each transaction related to a reimbursement received for a grant. dollarTransNumber NoNumber associated with the dollar classification, or other description of transaction 2. Mapped data will be exported from the client FMS in a .csv file 3. Client will set up and test sFTP connectivity to eCivis and perform as many sample file uploads as needed 4. The CSV file will be scheduled for upload every 24 hours ASSUMPTIONS 1. No additional data can be sent in the CSV file that is not listed in the description portion of this service Copyright © 2017-2020 eCivis. All rights reserved.

Page 12 of 21 ends

2. Client has unique identifier(s) in their FMS to isolate grant related transaction to a specific grant award Client will send as many sample file as needed by the eCivis team until such a time as the data and file pass validation logic and go / no go assessments 3. Client is responsible for setting up sFTP automation of a daily CSV file which is then pushed to eCivis through sFTP connectivity 4. Client will coordinate code promotion and deployment between client FMS and Grants Network. 5. Client is responsible for testing the non-eCivis side of all interfaces and for performing end-to-end tests in conjunction with the eCivis team 6. Client is responsible for creating a historical .CSV file, if applicable, which includes all grant related expenditures for a specific period of time as determined by the COR and the eCivis team. 7. Client will be responsible for understanding and detailing non-eCivis system file structure and providing timely and accurate file downloads, managing third party vendor relationships, and ensuring an adequate test environment in those systems to which eCivis interfaces 8. Client is responsible for developing the SQL or other method to extract and push the required data to eCivis Grants Network. 9. Client is responsible for the integrity of their financial data. 10. Client utilizes financial accounting practices that comply with state and federal regulations related to grant management/project management. 11. Any deviation from the SOW above will require an adjustment of cost estimates 12. Start date of the project and duration/timeline will be determined after execution of a contract (Optional) SERVICE: Budget Auto Update Integration (Client FMS to eCivis) INTRODUCTION The purpose of this integration is to import grant budget category information to update grantee award budgets on an automated basis. To accomplish this the existing budgets in the system will be deleted and the new budgets imported on a set frequency. DESCRIPTION 1. Client and eCivis will conduct a financial data mapping workshop. 2. FMS data will be mapped to the following eCivis fields: eCivis Grants Network data field:Required:Definition:extProjectID Yes Unique identifier for a single project in the financial system Copyright © 2017-2020 eCivis. All rights reserved.

Page 13 of 21 ends

extGrantID Yes Unique identifier for a single project in the financial systemCategory YesBudget class category that a budget line-item title is assigned to in the financial system.LineItemTitleYesUnique name/title of the budget line item in the financial system. LineItemDescriptionYesExplanation/description for the budget line-item title in the financial system. (If not available, use Line-Item Title) AccountNumberYes Unique G/L accounting code used to reference the budget line-item title in the financial system Cost Yes Most current amount budgeted for a specific budget line-item GL cost LineItemType Yes This is default value of “Direct Cost” 3. Mapped data will be exported from the client’s FMS in a .csv file format 4. Formatting of .csv file will require a header row and subsequent lines with each value encapsulated by double quotes and separated by a comma. 5. Cost value will not include thousand indicators, spaces or dollar symbols and include only 2 decimal places. 6. Client will set up and test sFTP connectivity to eCivis and perform as many sample file uploads as needed 7. The CSV file will be scheduled for upload no more than every 24 hours ASSUMPTIONS 1. Client is able to dedicate resources and complete components of Budget Auto Update Integration in a parallel workstream with the components of SERVICE: Pull Integration (Client FMS to eCivis)

Page 14 of 21 ends

2. No additional data can be sent in the CSV file that is not listed in the description portion of this document 3. Client has unique identifier(s) in their FMS to isolate grant related budget information for a specific grant award. 4. Client will send as many sample files as needed by the eCivis team until such a time as the data and file pass validation logic and go / no go assessments 5. Client is responsible for setting up sFTP automation of a daily CSV file which is then pushed to eCivis through sFTP connectivity 6. Client will coordinate code promotion and deployment between their FMS and Grants Network. 7. Client is responsible for testing the non-eCivis side of all interfaces and for performing end-to-end tests in conjunction with the eCivis team 8. Client is responsible for developing the SQL or other method to extract and push the required data to eCivis Grants Network. 9. Client is responsible for the integrity of their financial data. 10. Client utilizes financial accounting practices that comply with state and federal regulations related to grant management/project management. 11. extProjectID should mirror the FINAL version of the same field on the eCivis Financial Data Integration Crosswalk 12. extGrantID should mirror the FINAL version of the same field on the eCivis Financial Data Integration Crosswalk. 13. GLCode should mirror the FINAL version of the same data field on the eCivis Financial Data Integration Crosswalk. 14. Any deviation from the SOW above will require an adjustment of cost estimates 15. Start date of the project and duration/timeline will be determined after execution of a contract SERVICE: Data Migration The purpose of this service is to migrate existing grantee award data into eCivis Grants Network.1. CITY OF RIVERSIDE is responsible for collecting grant data from the appropriate staff2. Data Migration will utilize only the fields included in the eCivis standard data migration form (see Appendix A)3. Data Migration includes only open and active grant awardsSERVICE: Single Sign On Copyright © 2017-2020 eCivis. All rights reserved.

Page 15 of 21 ends

eCivis supports Single Sign On (SSO) integration with Grants Network using popular identity providers. We partner with Auth0 to support a variety of enterprise connection types: OpenID Connect Microsoft® Active Directory™/LDAP Microsoft® Azure® AD™ SAML (Service Provider Initiated) This document has been assembled to provide an overview of the SSO SAML integrationbetween a client’s Azure Active Directory (AD) service and eCivis Grants Network™. DESCRIPTION Grants Network provides a username (email address) / password authentication scheme, standard across SaaS applications. When a client wants to control access to Grants Network within their domain eCivis permits Single Sign-On (SSO). This provides the following benefits: 1. The client is in control of eCivis access. When a user needs to be deactivated, this becomes a client Information Technology (IT) function. 2. The client sets the password policy, including complexity rules and refresh rate.3. Client users only need to remember one set of credentials across the enterprise. During setup, the eCivis Implementation team works with the client’s IT department to define and configure their active directory implementation. This document covers Azure Active Directory authentication via Security Assertion Markup Language (SAML) 2.0.The following configuration steps encompass the implementation: 1. eCivis Implementation works with the client to identify users and appropriate authorization levels.2. eCivis provides the Client with an Identifier (Entity ID) and Reply URL (Assertion Consumer Service URL).

Page 16 of 21 ends

3. The Client IT creates a “Non-Gallery” enterprise application in their Azure AD organization. Upon request, the eCivis implementation team can provide an eCivis logo for the enterprise application. 4. The client adds authorized users to a security group associated with the enterprise application.5. The Client IT configures SAML SSO for the new application using the details provided in step 2.6. The Client IT sends the SAML Signing Certificate (Base64) and Login URL to eCivis.7. The Client and eCivis Implementation Team verify setup and configuration.8. The Client IT assigns additional users to the application, as needed, to allow access to Grants Network.Implementation Overview

Page 17 of 21 ends

Client users will access Grants Network by visiting https://gn.ecivis.com. Based on their username, they will be redirected to the Microsoft IdP workflow. Once the user authenticates on Azure AD, Azure provides a SAML assertion that is passed along to eCivis Grants Network. Grants Network then authorizes the authenticated user providing the proper permissions as defined by the eCivis account setup team. The client user will now be granted access to eCivis Grants Network resources permitted by their access level.

Page 18 of 21 ends

The user experience mimics the following flow:

Page 19 of 21 ends

Reference DocumentationAdd an unlisted (non-gallery) application to your Azure AD organization: https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/add-non-gallery-app Configure SAML-based single sign-on to non-gallery applications:https://docs.microsoft.com/en-us/azure/active-directory/manage-apps/configure-single-sign-on-non-gallery-applicationsASSUMPTIONS preferred 1. The CLIENT has the internal expertise required to complete the process setup2. The login will be directly at www.ecivis.com3. SSO applies only to eCivis Grants network. Some administrative tools and external users will not be covered under the SSO process. 8.0 Out of Scope for this project Customizations or enhancements that are not mutually agreed upon by eCivis and CITY OF RIVERSIDE in this statement of work. Historical award data System integrations that are not mutually agreed upon by eCivis and CITY OF RIVERSIDE in this statement of work. Reporting integration outside of eCivis Grants Network 9.0 eCivis RESPONSIBLITIES1. eCivis shall provide the following personnel Project Manager Implementation Specialist Customer Success Manager 2. eCivis will provide Master Project Timeline, and software user training resources. 3. eCivis shall provide Service Level Agreement (SLA), which will include:

Page 20 of 21 ends

99.9% monthly uptime. Single point of contact made via email or by calling a toll-free support number. Phone and email Technical Support Monday-Friday 8am-5pm ET Access to all patches (patches developed internally by ECivis to address core software issues like security, performance, etc.Access to new versions/upgrades Seamless modifications/enhancements per month 10.0 eCivis PROJECT MANAGEMENT CONTACTSThe eCivis’ Project Manager and Customer Success Manager will be determined aftercontract execution. 11.0 Project Schedule and Key Milestones Start date for the project will be influenced by the executed, signed contract. A detailed project plan will be developed after the project kick off meeting. 12.0 COST ASSUMPTIONS Copyright © 2017-2020 eCivis. All rights reserved.

Page 21 of 21 ends

13.0 APPENDIX A Grant title*The proper name of the specific funding opportunity. In some scenarios the proper name of the specific funding opportunity may be identical to the Project name depending on how your accounts are structured in your Financial Management System. ( 150 character limit)Department*The department in which the project is being administrated. Departments must be the same departments that are in your eCivis Grants Network Account. (80 character limit)Project name*Every grant in eCivis must be attached to a project. The project name can be anything the grant funding is being used to support. (255 character limit)Project summary*A brief description of the project. (1500 character limit)Project lead*The single person who is primarily responsible for managing grants related to this project. This person must be a licensed user in eCivis Grants Network.Project type (Construction or a Non-construction)*Indicates if the grant is a Construction or a Non-construction project.Internal project nameThe unique name associated with a specific project located in your financial system of record where grants are being managed. This can be the same or a variation of the project title in eCivis. (255 character limit)Internal project ID**A unique code associated with a specific project located in your financial system of record where grants are being managed. This value must match the value of the extProjectID field that will be exported/imported daily. (255 character limit)Internal grant nameThe unique name associated with a specific grant located in your financial system of record where grants are being managed. This can be the same or a variation of the grant title in eCivis. (255 character limit). Internal grant ID**A unique code associated with a specific grant located in your financial system of record where grant funding is being managed. This value must match the value of the extGrantID field that will be exported/imported daily.(255 character limit)Competitive or Not Competitive (Yes/No)*This field distinguishes between non-competitive sources like pass through, formula, or direct funding and competitive funding that had an evaluation or application process.FY*The fiscal year in which the funding was made available.Funding type*Identifying the funding source as Federal, State, Foundation, Other, County/Regional, Non-Profit or Tribal. Funding type (Optional)Indicate whether funding type is a formula grant where award is predetermined by distribution formulas or pass-through funding where is open to discretionary funding decisions.CFDA# (Optional)Catalog of federal Domestic Assistance. This is a unique number assigned to every Federal grant opportunity and is essential for ensuring the right funding opportunities in eCivis are identified.Grantor*The specific department/office within State or Federal government. Or the specific name of the local or private source. (75 character limit)Award date*Indicate the day you received award notification. Grant award amount*The amount awarded to you from the funding agencyMatch required (Yes/No)*A simple yes/no answer if a match is required for the grant opportunity.Cash match amountThe total amount of cash cost share required by the grant. Doller value required if "Match required"="Yes". ($0.00 and up)In-kind match amountThe total amount of in-kind cost share required by the grant. Doller value required if "Match required"="Yes". ($0.00 and up)Contract start date*The beginning date agreed to with the funding agency when funds can begin to be expended and the project will begin.Contract end date*The end date agreed to with the funding agency when funds must be expended and the project complete. This can be extended in cases of an extension.(Optional) Grant TagThe grant tag(s) that a template task will be limited to. The template task will only be triggered when the project grant contains the matching tag. Leave blank if this grant will not require specific tagging for tasks.(Optional) FAINFederal Award Identification Number is intended to enhance data quality on USASpending.gov This optional field can also be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “FAIN” will not be changed. (75 character limit)(Optional) STATE IDA unique number assigned to a business or organization by the state where the business operates. This optional field can be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “State ID” will not be changed. (75 character limit)(Optional) Federal FONFunding Opportunity Number is a unique number used on Grants.gov This optional field can be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “Federal FON” will not be changed. (75 character limit)(Optional) Organization IDoptional field can be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “Organization ID” will not be changed. (75 character limit)(Optional) DUNS NumberDun & Bradstreet or D-U-N-S Number is a unique nine digit identification number, for each physical location of your business. This optional field can be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “DUNS Number” will not be changed. (9 character limit) Note: Specific format (XX-XXX-XXXX)(Optional) Grantor Contract NumberVaries depending on Organization. This optional field can be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “Grant Contract Number” will not be changed. (50 character limit)(Optional) Grant ContactVaries depending on Organization. This optional field can be used to store any data specific to this grant in eCivis Grants Network to later capture in reports but the field name “Grant Contact” will not be changed. (5000 character limit)*Indicates a required field in eCivis. Placeholder values can be used but will require updating in your live account after implementation.**Indicates a required field for client using Data Integration.

Riverside City CouncilAugust 6, 2024

Riverside City Council
August 6, 2024