Statement of Work
City of Santa Maria, CA
Creation Date: 1/12/2026
SoW Expiration Date: 6/30/2026
Document Number: PS-10707.5
Created by: Emily Scheckel
PS-10707.5
1 ATTACHMENT C
Table of Contents OpenGov Statement of Work 3 1. Project Scope and Understanding 3 2. Exhibits 3 3. OpenGov Responsibilities 3 4. Customer Responsibilities 3 5. Project Delivery 4 6. Estimated Schedule 4 7. Acceptance Procedure 5 8. Modifications 5 9. Communication and Escalation Procedure 5 Exhibit 1: Implementation Activities 6 OpenGov Implementation Methodology Overview 6 Budgeting & Performance 6 Initiate 6 Validate 7 Configure 7 Train 10 Launch 12 Government App Builder: 12 Initiate 12 Validate 13 Configure 13 Train 16 Launch 17 Exhibit 2: Technical Requirements 17 Budgeting & Performance Technical Requirements 17 Government App Builder Technical Requirements 18 PS-10707.5 2
OpenGov Statement of Work
1. Project Scope and Understanding This Statement of Work (“SOW”) outlines the Professional Services OpenGov will provide
to
City
of
Santa
Maria,
CA
(“Customer”)
under
the
applicable
Order
Form.
Professional
Services
or
technical
requirements
not
listed
in
this
SOW
are
out
of
scope.
2. Exhibits The following exhibits are incorporated by reference and are part of this SOW: 2.1. Exhibit 1: Implementation Activities 2.1.1. Budgeting & Performance 2.1.2. Government App Builder 2.2. Exhibit 2: Technical Requirements 2.2.1. Budgeting & Performance 2.2.2. Government App Builder 3. OpenGov Responsibilities OpenGov will provide a framework for planning, communication, progress tracking, and
coordination
for
activities
in
Exhibit
1. In
collaboration
with
Customer,
OpenGov
will
develop
and
maintain
the
Project
Plan.
The
“Project
Plan”
is
a
detailed,
living
document
that
defines
how
the
project
will
be
executed,
including
tasks,
timelines,
milestones,
and
team
assignments.
OpenGov
will
monitor
progress
against
the
Project
Plan,
coordinate
adjustments
to
tasks
and
schedules
as
needed,
and
conduct
status
meetings
as
agreed
to
by
the
parties.
OpenGov
will
provide
weekly
status
reports,
a
Project
Charter,
and
a
RAID
register
(Risks,
Actions,
Issues,
and
Decisions).
The
“Project
Charter”
is
a
high-level
document
outlining
the
project’s
purpose,
goals,
key
stakeholders,
success
criteria,
and
major
milestones.
4. Customer Responsibilities The Customer will appoint a primary point of contact with authority to make binding decisions
(“Customer’s
Project
Manager”).
This
person
will
coordinate
internal
resources,
assign
subject
matter
experts
(“SMEs”),
and
oversee
implementation.
Responsibilities
include
attending
status
meetings,
making
timely
decisions,
providing
requested
information,
escalating
issues
internally,
and
collaborating
on
the
Project
Plan
and
Change
Order
process,
if
applicable.
Customer acknowledges that the success of this project is contingent on its full participation.
Customer
must
provide
data
within
ten
(10)
business
days
of
a
request,
maintain
consistent
data
formats
and
access
throughout
the
project,
and
allocate
the
necessary
Customer
resources
and
time
to
support
deliverables
and
meet
agreed-upon
timelines.
PS-10707.5 3
Any failure by Customer to meet its responsibilities under this SOW (each, a “Customer
Delay”)
will
automatically
suspend
the
affected
obligations
of
OpenGov
for
the
duration
of
the
Customer
Delay
and
for
a
reasonable
restart
period
thereafter.
All
affected
milestones,
delivery
dates,
and
service-level
commitments
will
be
extended
on
a
day-for-day
basis
(or
as
otherwise
reasonably
necessary)
to
account
for
the
Customer
Delay,
and
may
result
in
an
adjustment
of
the
fees
if
OpenGov
incurs
additional
time,
materials,
or
other
costs
as
a
result.
Under
no
circumstances
will
any
consequence
of
a
Customer
Delay
constitute
a
breach
by
OpenGov
of
this
SOW
or
of
the
Agreement,
nor
will
OpenGov
be
liable
for
any
failure
to
meet
a
performance
obligation
that
is
caused,
in
whole
or
in
part,
by
a
Customer
Delay.
5. Project Delivery OpenGov will perform services under this SOW remotely. OpenGov may use a combination
of
OpenGov
personnel
and
OpenGov-trained
implementation
partners
to
deliver
the
services
described
in
this
SOW.
6. Estimated Schedule The estimated duration of this work is 12 months. The specific timeline, including order
of
delivery
of
the
suite(s),
will
be
determined
during
the
project
planning
activities
in
the
Initiate
Phase.
Services
are
estimated
to
begin
within
two
(2)
weeks
and
no
later
than
four
(4)
weeks
from
contract
signature.
OpenGov
reserves
the
right
to
adjust
the
schedule
based
on
the
availability
of
Customer
or
OpenGov
resources,
and
the
timeliness
of
deliverables
provided
by
the
Customer.
7. Acceptance Procedure OpenGov will submit completed deliverables to the Customer’s Project Manager for review.
Within
five
(5)
business
days
of
receipt,
the
Customer’s
Project
Manager
will
either
provide
written
acceptance
or
a
list
of
requested
revisions.
In
the
event
there
are
requested
revisions,
the
subsequent
review
period
for
acceptance
will
follow
the
same
timeline
until
final
acceptance.
If
Customer
does
not
respond
within
this
period,
the
deliverable
will
be
deemed
accepted.
Once
a
deliverable
is
accepted,
any
requested
changes
will
require
a
paid
Change
Order.
Acceptance milestones and review timelines will be tracked in the Project Plan.
Both
parties
acknowledge
that
delays
in
task
completion
or
unresolved
issues
may
impact
the
project
timeline.
If
OpenGov
determines
in
good
faith
that
Customer
is
not
fulfilling
its
responsibilities
under
this
SOW,
OpenGov
may
place
services
on
hold
following
a
minimum
of
five
(5)
business
days’
written
notice.
The
notice
will
PS-10707.5 4
specify the actions needed to progress the project. During the hold period, OpenGov may
reallocate
resources
without
penalty
and
will
not
be
responsible
for
resulting
delays.
8. Modifications The fees and estimated timeline are based on the scope and assumptions in this SOW.
If
either
party
determines
that
a
change
to
the
scope
is
necessary,
the
parties
will
collaborate
to
define
the
required
modification,
which
may
result
in
fee
adjustments
based
on
OpenGov’s
standard
rates.
All
modifications
must
be
documented
in
a
written
Change
Order
and
signed
by
both
parties
(“Change
Order”)
.
Examples
of
changes
include
revisions
to
the
project
timeline,
deliverables,
or
resource
allocation.
9. Communication and Escalation Procedure OpenGov and Customer agree to maintain regular communication in alignment with the
Project
Plan
to
ensure
progress,
resolve
questions
promptly,
and
minimize
risk.
Both
parties
will
raise
any
issues
or
concerns
in
a
timely
manner.
If
challenges
are
not
resolved
through
standard
project
discussions,
Customer
and
OpenGov
Project
Managers
will
escalate
to
their
respective
executive
leadership
teams
to
jointly
determine
a
resolution
and
align
on
a
path
to
successful
implementation.
PS-10707.5 5
Exhibit 1: Implementation Activities OpenGov Implementation Methodology Overview Every OpenGov implementation follows a five-phase hybrid methodology designed to ensure a structured
and
collaborative
deployment.
The
phases
are:
1. Initiate – OpenGov provisions access and performs initial system setup. 2. Validate – OpenGov works with the Customer to confirm requirements and review initial configurations.
3. Configure – OpenGov completes system configuration as outlined in this SOW. 4. Train – OpenGov provides training to system administrators and/or end users, as applicable. 5. Launch – OpenGov provides post-go-live support and transitions the Customer to OpenGov’s
Customer
Success
Team.
Each implementation is structured around these phases. Deliverables, sign-offs, and completion criteria
are
aligned
to
the
relevant
phase.
Budgeting & Performance Use Cases Build for Budgeting & Performance: ● Operating Budget ● Workforce Planning ● Budget Book Publication ● B&P Integration Initiate
Provisioning Budget & Planning
OpenGov will: ● Provision Customer’s OpenGov entity and verify Customer has access to all purchased modules.
Customer will:
PS-10707.5 6
● Confirm access to entity and modules. Completion Criteria ● Customer verifies access to the site.
Validate
Technical Project Review
OpenGov will: ● Provide up to one (1) one-hour working sessions at the beginning of the project to: o Review deliverables o Review technical requirements o Provide documentation on requirements and processes OpenGov Assumptions: ● Customer will provide relevant data within two (2) weeks immediately following the kick-off meeting.
Customer will: ● Identify relevant participants for attendance. ●
Confirm deliverables.
●
Gather and provide relevant data for the project. Completion Criteria ● Customer sign-off on the project plan.
Configure Chart of Accounts (COA)
OpenGov will: ● Build Customer's COA in OpenGov in accordance with OpenGov technical requirements. ● Review configured COA and uploaded data and provide training to Customer on how to: o Manage new codes o Edit COA o Create Masks Customer will: ● Provide current COA and transactional data. ● Validate and provide sign off on COA. ●
Maintain the COA following configuration. Completion Criteria ● Customer sign-off that the Chart of Accounts has been configured.
Operating Budget OpenGov will:
●
Configure one (1) Budget instance.
●
Configure budget proposal based on a Segment of the Chart of Accounts. ●
Train and assist on the modification of the configuration. ● Configure and upload Customer’s base budget file into OpenGov budget instance. ● Configure OpenGov Budget Proposals and Worksheets for Departments in the base budget file
based
on
the
agreed
upon
structure.
PS-10707.5 7
● Review configured OpenGov Budget and provide training to Customer on how to: o Create new Proposals and Worksheets o Manage Budgets Customer will: ● Provide a current budget. ● Validate Budget Proposals and Worksheets. ● Signoff on Budget Proposals and Worksheets. Completion Criteria ● Customer sign-off that Operating Budget proposals and worksheets have been configured.
Workforce
OpenGov will: ● Provide cost elements based on Customer’s existing personnel forecast to workforce document
as
per
OpenGov’s
best
practices.
● Review configured OpenGov Workforce Plan and provide training to Customer on how to: o Create Cost Elements o
Populate and upload the Position Template Customer will: ● Provide Position calculations and tables. ● Populate the Position Template and upload the completed template into OpenGov. ● Validate and provide signoff on the Workforce Plan calculations. ●
Maintain the Workforce Plan and data once configured. Completion Criteria ● Customer sign-off that the Workforce Plan has been configured.
Reporting
OpenGov will: ● Set up one (1) export and Dataset View to enable OpenGov Budget Reports for the Operating and
Capital
Budget(s).
● Configure up three (3) standard reports using the customer’s integrated financial data: o Annual o Budget to Actuals o Transactions ● Configure up to four (4) Operating Budget Reports using OpenGov budget data: o Milestones o Development o Fund Balance Projections o Categories* ● Configure up to two (2) Capital Budget Reports using OpenGov budget data: o Development o Effect on Operating ● Review configured OpenGov Reports and provide training Customer on how to: o Export Budget Data for use in OpenGov Reports. o Create new Reports PS-10707.5 8
o Manage Reports o Share Reports *Budget Categories report is only available to customers using a zero-based budget.
Customer will:
●
Validate and provide sign-off of Reports.
●
Maintain the Reports once configured. ● Map OpenGov Budget export to Customer ERP import format. Completion Criteria ● Customer sign-off that Reports have been configured.
Budget Book Publication OpenGov will: ● Deliver the following Online Budget Book deliverables for use with the completion of the first
OpenGov
Budget
development.
○ Based on best practices, build out the look and feel of six (6) Standard OBB Templates:
■ Home Page ■ Generic (multi-use) ■ Operating ■ Department ■ Capital ■ Capital Project ○ Using the above standard templates, create up to 100 total Project and/orDepartment
page
shells.
○ Create an Annual Budget Report and FTE Report using OpenGov Budget data and
Report
Views
to
use
in
Department
and
Project
OBB
Story
Shells. ○ Provide up to ten (10) one-hour working sessions to answer Customer questions
on
OBB
Configuration
Customer will: ● Provide logo and branding colors to OpenGov. ● Create any additional OBB Reports, Report Views, and OBB Stories required by the Customer
● Add all content to Stories including: ○ Narrative ○ OpenGov Report Views ○ Images ○ Data not in OpenGov ● Attend working sessions to get answers on OBB questions. ● Make Stories public and Publish OBB. Completion Criteria ● Customer sign-off that the Budget Book Publication templates are configured.
PS-10707.5 9
Financial Integration
OpenGov will: ● Set up a SFTP and Sample File Format. ● Integrate the following functionalities: o General Ledger Actuals and Budget (Revenue and Expenses) ● Extract, transform (when required) and load the data. ● Build Validation Reports for Budget and Actuals. ● Validate the historical data and current year data based on the Customer provided summary report.
● Schedule the current year data load. ● Monitor the data load. OpenGov assumptions: ● Integration is unidirectional from the Customer’s Workday into OpenGov. ● The data will be linked to the Customer’s COA. Customer will: ● Provide an IT resource to assist the project team in the initial set-up. ● Provide assistance to understand source system specific customizations and configurations
when
building
the
data
extract.
● If OpenGov is unable to access the data per requirements, provide .csv data files via OpenGov
SFTP
Location.
●
Any charges for the data from the ERP system will be the customer's responsibility. ● Broker OpenGov’s access to Customer’s source accounting data if hosted by any third vendor.
● Provide a summary export data to validate against. ● Validate and provide sign off on the integrated data and reports. ●
Changes to the underlying data after project closure will be the responsibility of the customer
to
update.
●
Maintenance of the integration file on an ongoing basis is the responsibility of the customer.
Completion Criteria ● Customer sign-off that the Integration has been configured.
Train
Budgeting & Planning Working Sessions
OpenGov will: ● Per the agreed upon Project Plan, schedule working sessions with Customer’s system administrators
to:
○ Review configurations; ○ Provide training on system functionality; PS-10707.5 10
○ Gain feedback; and ○ Answer questions regarding configured system functionality. Customer will: ● Per the agreed upon Project Plan, attend working sessions to: ○ Understand configurations; ○ Gain training on system functionality; ○ Give feedback; and ○ Ask questions regarding configured system functionality Completion Criteria ● Budgeting & Planning Working Sessions have been conducted.
Budget and Workforce Administrator Training
OpenGov will: ● Provide training to Customer system administrators on how to: ○ Create and manage Budgets ○ Prepare to set up Next Year’s Budget ○ Create and manage Workforce Plans including Cost Elements and Position Upload Templates
○ Export Budget Data for use in OpenGov Reports. Customer will: ● Identify relevant participants and attend scheduled training sessions. Completion Criteria ● Budget & Workforce Training has been conducted.
Publication Training
OpenGov will: ● Provide one (1) 60- Minute System Training designed for OBB Administrators on how to: ○ Use and copy OBB Templates ○ Add Reports Views to Stories ○ Add Customer content including: narrative, images, and external data to Stories ○ Publish Stories ○ Update and maintain Stories Customer will: ● Identify relevant participants and attend scheduled training sessions. Completion Criteria ● Publication Training has been conducted.
End-User Training
OpenGov will: ● Provide two (2), 60-Minute training session(s) to Customer’s Internal Users on how to: ○ Navigate Opengov Budgets and Reports ○ How to enter Budget data ○ How to run and use reports Customer will:
PS-10707.5 11
● Identify relevant participants and attend scheduled training sessions. Completion Criteria ● End User Training has been conducted.
Launch
HyperAdopt OpenGov will: ● Provide up to eight (8) hours of working sessions to answer any questions following solution acceptance.
Customer will: ● Identify issues and attend sessions. Completion Criteria ● Customer sign-off that the project has been completed.
Government App Builder:
Capital Budget & Project Management
Initiate
OpenGov Responsibilities
● Host kickoff with all stakeholders. ● Provision Government App Builder instance and access. ● Launch project workspace and backlog.
Customer Responsibilities
● Identify and invite all relevant stakeholders. ● Confirm environment access and provide existing documentation on grant/project workflows.
Boundaries & Assumptions
● Standard templates and frameworks to be used unless otherwise agreed. ● City will provide required inputs within 5 business days.
PS-10707.5 12
Completion Criteria
● Kickoff complete. ● Environment provisioned. ● Access validated and backlog initiated.
Validate
OpenGov Responsibilities
● Lead validation session. ● Finalize configuration backlog. ● Confirm system access, technical readiness.
Customer Responsibilities
● Validate and sign off on backlog and project plan. ● Provide any outstanding field mappings, sample forms, or process flows.
Boundaries & Assumptions
● All validation feedback due within 2 business days. ● Significant new requirements will be subject to Change Order.
Completion Criteria
● Sign-off on scope, tools, and backlog. ● No blocking prerequisites.
Configure
Forms Configuration
OpenGov Responsibilities
● Design and deploy forms in App Builder. ● Apply conditional logic, validation, field types, and role-based permissions.
PS-10707.5 13
Customer Responsibilities
● Provide all field-level requirements and form examples. ● Review and test forms; approve final configurations.
Boundaries & Assumptions
● Standard form components only. ● No external custom development.
Completion Criteria
● All forms tested and approved. ● Internal and external visibility confirmed.
Reports Configuration
OpenGov Responsibilities
● Configure templates (table, calendar, chart). ● Train staff on report use and export.
Customer Responsibilities
● Submit sample reports and KPI definitions. ● Validate output meets internal and regulatory needs.
Boundaries & Assumptions
● Built from configured data only. ● City consolidates requests upfront.
Completion Criteria
● Reports live and validated. ● Exports functional and shared.
Workflow & Process Automation
PS-10707.5 14
OpenGov Responsibilities
● Configure approval and task routing logic. ● Implement automation per documented rules.
Customer Responsibilities
● Provide decision trees, escalation triggers, approval roles. ● Participate in testing.
Boundaries & Assumptions
● Standard workflow tools only. ● Delays in decision logic will delay timeline.
Completion Criteria
● Workflows deployed and tested. ● Notifications operating correctly.
Integration: B&P to GAB
OpenGov Responsibilities
● Configure intake connection, map fields. ● Validate imports.
Customer Responsibilities
● Provide scoring rubric, mapped fields, and sample test data.
Boundaries & Assumptions
● File-based handoff unless otherwise scoped. ● No real-time bi-directional sync.
Completion Criteria
PS-10707.5 15
● Validated, tested, and documented integration.
Data Migration
OpenGov Responsibilities
● Create templates and run data imports. ● Validate mapped fields and normalized outputs.
Customer Responsibilities
● Provide clean datasets with mapping guidance. ● Approve samples.
Boundaries & Assumptions
● One round of validation. ● OpenGov is not responsible for cleansing data.
Completion Criteria
● Records loaded and signed off. ● Dataset ready for launch.
Train
Administrative User Training
OpenGov Responsibilities
● Deliver hands-on virtual training. ● Provide access to documentation.
Customer Responsibilities
● Ensure attendance of key users. ● Validate understanding through exercises.
Boundaries & Assumptions
PS-10707.5 16
● Delivered virtually. ● Attendance is required to maintain timeline.
Completion Criteria
● Users trained and validated on core tasks.
Launch
OpenGov Responsibilities
● Deliver hypercare support. ● Resolve final questions. ● Transition to Customer Success.
Customer Responsibilities
● Identify open issues. ● Complete stakeholder review and solution acceptance.
Boundaries & Assumptions
● All work must be completed for go-live support to begin.
Completion Criteria
● Sign-off from City on project completion. ● Final support delivered and logged.
Grants Management
Validate
OpenGov will:
● Provide Customer with the Grants Set Up Workbook. ● Facilitate validation workshop to confirm requirements and dependencies.
PS-10707.5 17
● Present refined project plan, timeline, and resource plan for sign ‑ off. ● Validate user access, permissions, and environment readiness. ● Update artifacts based on feedback prior to configuration.
Customer will:
● Attend validation with decision ‑ makers and SMEs. ● Confirm access to needed systems and tools for 3rd party integrations in scope ● Review and sign off on the project plan. ● Resolve internal dependencies that could block configuration.
Assumptions
● Any additional requirements identified will be assessed for scope and schedule impact. ● Integration methods (file/API) will be proposed in this phase for approval in Configure.
Completion Criteria
● Customer sign ‑ off on plan and backlog. ● Access validated. ● No outstanding blockers to start Configure. ● Readiness checkpoint logged in project documentation.
Configure Module and Submodule Configuration
OpenGov will:
● Configure data tables, fields, validations, conditional logic, and layouts for Pre-award, Award,
and
Post-award
modules
including
the
following
sub
modules:
○ Pre-award: ■ Federal Grant Search tool ■ State Grant Search tool ■ Donor Capital Search tool ○ Award: ■ Budgets PS-10707.5 18
■ Compliance ■ Documents ■ Metrics ■ Applications ■ Expenses ■ Projects ■ Reimbursements ■ Subrecipient (up to 2) ○ Post-award ■ Out of the Box compliance reports (FFRs, CFR 200) ● Conduct review sessions and iterate to finalize.
Customer will:
● Provide field ‑ level requirements, examples of existing forms, and regulatory data elements. ● Participate in reviews; provide consolidated feedback. ● Validate permissions, logic, and layouts for internal and public users. ● Approve final form configurations.
Assumptions
● Designs leverage standard form capabilities and controls. ● OpenGov will provide good faith efforts to accommodate Accessibility, Translation, and ADA considerations
identified
by
Customer
in
advance.
However,
we
do
not
commit
to
formal
adherence
to
WCAG
AAA
2.1 guidelines.
● Public portal content and branding assets provided by Customer.
Completion Criteria
● Forms/tables configured and tested. ● Visibility/permissions validated. ● Required data capture confirmed. ● Customer approval received.
Reports and Dashboard Configuration
OpenGov Responsibilities
PS-10707.5 19
● Configure up to five (5) reports for each submodule in the Configuration section of this SOW,
filters,
and
visualizations;
enable
exports
suitable
for
audit/board/grantor
submissions.
● Provide enablement on managing report parameters.
Customer will:
● Define KPIs, compliance metrics, and reporting needs (e.g., HUD/FEMA/ARPA). ● Review layouts and logic; test exports; designate owners for ongoing reporting.
Assumptions
● Reports rely on data available in configured tables or approved workbook imports.
Completion Criteria
● Reports and dashboards live with accurate data. ● Permissions verified; export formats tested. ● Customer approval received.
Workflow & Process Automation
OpenGov will:
● Implement role ‑ based visibility and permissions for: ○ Internal roles ○ Subrecipient external roles ● Configure routing, task queues, deadline reminders, conditional approvals, and status transitions
for
one
(1)
workflow
with
up
to
ten
(10)
approval
steps
for
each
of
the
following
modules:
○ Pre-Award ○ Award ● Document workflows and test with Customer.
Customer will:
● Provide current process maps, approvers, timelines, and escalation criteria. ● Participate in testing and refinement; approve final logic.
Assumptions
PS-10707.5 20
● Automation will use standard workflow options. ● SLA timers and escalations are based on Customer ‑ provided policies.
Completion Criteria
● Workflows live with notifications functioning. ● All stages mapped with associated logic. ● Approval received from Customer.
OpenGov Budgeting & Planning to OpenGov Government App Builder OpenGov will:
● OpenGov Procurement ○ Implement an one-way API or flatfile transfer from OpenGov Budgeting & Planning. ○ Map fields for[insert] Customer will:
● Provide[insert] ● Validate mapped fields.
Completion Criteria
● Working integration is live. ● Customer approval received.
Train Administrative User Training
OpenGov will:
● Deliver live virtual training; provide documentation and recordings. ● Cover core admin tasks (form edits, report creation, workflow adjustments, permission controls).
● Assign practice scenarios.
Customer will:
PS-10707.5 21
● Identify admin users; attend training; complete practice exercises; confirm understanding of
admin
responsibilities.
Completion Criteria
● Admin training completed; access confirmed for relevant users. ● Practice scenarios validated. ● Customer confirms readiness to manage configuration post ‑ launch.
Public/User-facing Collateral
OpenGov will:
● Draft how ‑ to guides with screenshots and FAQs; deliver PDF and web ‑ optimized formats. ● Review drafts with Customer for accuracy; finalize collateral.
Customer will:
● Review and provide feedback; approve final content; handle distribution and any localization.
Assumptions
● Content reflects current forms and processes at go ‑ live. ● Accessibility/translation needs identified by Customer.
Completion Criteria
● Guides finalized and approved; published via Customer channels.
Launch
OpenGov will:
● Provide eight (8) hours of Hyperadopt including: Monitor adoption and resolve configuration
questions
and
issues.
● Conduct final stakeholder review. ● Transition to Customer Success.
Customer will:
● Monitor usage and report issues
PS-10707.5 22
● Attend final review ● Sign solution acceptance.
Completion Criteria
● Stakeholder review completed; solution acceptance signed.
Exhibit 2: Technical Requirements
Budgeting & Performance Technical Requirements Chart of Accounts ● Flat file ● .csv, .xls, .xlsx with headers ● Active Accounts and Accounts with activity in the years of data being loaded into OpenGov. Financial Data Files (Transactional Export) ● Flat file ● .csv, .xls, .xlsx with headers ● 3-5 Years of Data Financial Data Files (Summary Revenue and Expense Export) ● PDF export Current Budget ● Flat file ● .csv, .xls, .xlsx with headers ● Operating Budget Personnel Calculations and Tables ● PDF, Word, csv, .xls, .xlsx with headers Logo Image ● .jpg or .png format ● Transparent Branding Guidelines ● Hex codes Government App Builder Technical Requirements
● Migration
PS-10707.5 23
○ All data must be accessible to OpenGov in Excel or CSV format ○ Maximum historical record count: 500 ● Flat File Integrations ○ Customer must ■ Provide OpenGov with the export file (a delimited file) from the external system
■ Automate the export and/or import of data into and out of the external system.
● API Integrations ○ Customer is responsible for: ■ Fees associated with purchasing the external system ■ Providing OpenGov with access to the API and/or access to technical staff from
that
vendor.
■ Access to a test instance of the third party API including a URL, authentication
credentials,
and
relevant
documentation.
■ Changes to scope resulting from a change in the third-party vendor’s API. ■ Testing expected workflows and data in both test and production environments
○ To display a location on a map, the third party system must be able to provide location
data
via
their
API,
as
shapes
or
coordinates.
Text
addresses
are
limited
to
populating
address
fields.
PS-10707.5 24