HomeMy WebLinkAboutTAB FUSION RMSN-2023-219
INSURANCE NOT REQUIRED
WORK MAY PROCEED
CITY CLERK
DATE:
0:cc? tc9)
(Y q;vvf�,5. N9 tab
FUSIONRMS
DEDICATED UPGRADE & WEB -ACCESS SOW
Prepared for: CITY OF SANTA ANA
July 271h, 2023
CLIENT CONTACT
Ethan Meyer jPrincipal Programmer Analyst
City of Santa Ana I Information Technology
20 Civic Center Plaza, M-42 I Santa Ana, CA 92701
714-647-6533 1 emeyer@santa-ana.org
TAB CONTACT
Robert Clark
Solutions Consultant
857-406-5378
rclark(@tab.com
Statement of Confidentiality, Liability and Validity
This Statement of Work ("SOW") forms a part of and authorizes TAB Products CO., LLC to perform
Services pursuant to the terms in Appendix B between City of Santa Ana. ("Client") and TAB
Products CO., LLC. ("TAB") effective as of August 18th, 2020 (the "Agreement").
This Statement of Work is effective as of the July 27, 2023 (the "SOW Effective Date") between the
Client and TAB pursuant to which the Client engages TAB to perform certain Services and TAB
agrees to provide such Services for the Fees, all in accordance with the provisions of the
Agreement and this Statement of Work, consisting of the following documents:
a) this Service Order;
b) the Exhibits, Appendices and Attachments listed herein and attached; and
c) Change Orders approved by the Client in accordance with the Agreement.
Unless specifically defined herein, capitalized words and phrases used herein have the meaning
ascribed to them in the Agreement.
The parties (the "Parties") to this Service Order shall not be bound by or be liable for any
representation or warranty not set forth in the Agreement.
This document has been prepared specifically for the Client and is proprietary to TAB Products CO.,
LLC ("TAB"). Any dissemination or distribution of this proposal or copies thereof to any third party
without TAB's prior written consent is strictly prohibited.
Page 2 of 19
Overview
Current Situation:
City of Santa Ana is currently using FusionRMS V 9.3 to manage their records throughout the
course of their lifecycle. To improve performance and refresh the user experience City of Santa Ana
has requested costs for having TAB's professional services team roll out and configure web -access.
TAB will work to upgrade and configure the solution based on the scope and phases below.
Scope
FusionRMS Upgrade
TAB will provide project management, staff and supplies to:
1. Receive a recent backup of the Client's Production Database
2. Upgrade the existing FusionRMS system from 9.3 to V1 1 in TAB's Development
Environment
a. Configure the solution for FusionRMS Web -Access
3. Deployment of the FusionRMS V11 solution to the Client's Test Environment
4. Provide up to 1 hour of live Training to educate client assigned Super Users to
a. Test and confirm all Functional Specifications have been delivered to the Test
Environment.
5. Learn Management System Train for all end users on the new FusionRMS system
6. Following Systems Acceptance, assist the Client in deploying the accepted FusionRMS
system into the Client's Production Environment
Work not within scope includes, but is not limited to:
1. Enabling features not similar to those in V9.3.
2. Integration of FusionRMS VI with any other client applications
3. Training End Users
4. Setting up the Client's Test or Production Environments to accept the deployment of
the upgraded FusionRMS system.
5. Provisioning and/or addressing any gaps in the Client's technical environment(s)
required to properly install FusionRMS to comply with Client's internal policies and
desired response time of functionality within FusionRMS for End Users.
TAB welcomes the opportunity to assist the client on items not in scope through the Change
Management Process outlined in Appendix A. Upon mutual execution of a Change Order,
additional work will be added and executed to the scope noted.
Page 3 of 19
Deliverables
The key deliverables for this project are:
The deliverables are:
1. Documented Functional Specifications mutually accepted by both parties.
2. Configured FusionRMS system to Functional Specifications deployed to the Client's Test
Environment.
3. Up to 1 hour of Live Training Sessions for the Client's Super Users as part of enabling User
Acceptance Testing (UAT) and LMS Training.
4. System Acceptance certificate of the configured FusionRMS system in the Development
Environment.
5. Assistance to support the Client push the accepted FusionRMS system in Development into
the Client's Production Environment.
Success Criteria
Sign -off for the stated deliverables by client will be provided and not be unduly delayed
upon the following success criteria:
Sign -off for the deliverables and project will be as follows:
1. Functional Specifications are signed off by both parties.
2. Systems Acceptance will be granted by the Client when:
a. Client testing of the configured FusionRMS system in the Test Environment has no
material defects identified.
b. Client has provided TAB with written notice of material defects within 10 business
days of configured system delivery to the Client for testing by TAB.
Key Assumptions
Both parties acknowledge that many details are yet to be determined and therefore, despite the
information shared by the Client and gathered by TAB in the development of this Statement of
Work, many assumptions must be made. The key assumptions used, but not limited to:
1. End User experience of the FusionRMS service performance or access to enabled features can be
materially impacted based on the client's use of equipment, internal network and security policies.
The client will work in good faith with TAB to optimize its environment to provide the optimal
experience for its End Users.
2. Features or performance issues impacted by the client's environment are not considered defects and
will be remedied at the client's sole expense in a timely manner in support of the mutually
established project timeline at the onset of the project.
Page 4 of 19
Key Assumptions (continued)
3. Only features materially similar to V9.3 will be enabled to minimize change/risk to the affected End
Users and current workflows. TAB welcomes the opportunity to collaborate with Client on features
available within V10.2 that maybe of further benefit under a Change Order to this SOW or another
SOW at a later date
4. The Client will be able to upload a SQL Backup of their current Production Environment to a TAB
Provisioned sharefile or sFTP site. It is recommended that the backup be archived using WinRAR or
similar, separating the archive into 500MB volumes, including a 3% recovery record.
5. The Client maintains a Testing Environment that is in alignment with the technical specifications of
the Production Environment, including the restoration of a recent backup from the Client's
Production Environment into the Test Environment, confirming and testing it.
6. If users are to print TabQUIk color labels from the web -client, communication to/from
tabquik.com/.ca website is required. Any required networking and IT tasks associated with meeting
this prerequisite is the responsibility of the client.
7. If users are to print black & white labels from the web -client a supported print driver will be installed
and configured on the IS server. Any required networking and IT tasks associated with meeting this
prerequisite is the responsibility of the client.
8. TAB will have administrator access with dedicated remote (Microsoft Remote Desktop Access -
"RDP") credentials to all of the Fusion Environments hosted by the Client, including "sa" or "DB
Owner' permissions on the FusionRMS Database Server. TAB will always defer to the IT security
policies of the Client, but in scenarios where the above assumptions cannot be met, additional
efforts outside the scope of this project may be required.
9. TAB will document the solution design in the form of a Visio document describing the existing
structure notating interface points and key business process use cases.
Should any material deviation from the approach or the assumptions listed above present itself
during the course of this project, a change order "may" be issued as per our Change Management
Process (see Appendix A).
Page 5 of 19
Project Team Structure
Role
Key Responsibilities/Accountabilities
Client Project Sponsor•
Overall project success for Client.
•
Escalation and commercial contact for Client.
•
Responsible for escalating issues within Client organization and communicating challenges.
•
Timely approval of invoices in accordance to payment terms.
Client Project Manager•
Reports to Client's Project Sponsor.
•
Ensures all required resources are available to execute the work and/or address matters that
may arise, in a timely manner to effectively and efficiently manage timeline or cost changes.
•
Collaborate on and review FusionRMS Security Matrix
•
Review and approve FusionRMS Functional Specification document
•
Review and provide authorized sign -off on all project deliverables.
•
Single point of contact for TAB's Project Manager.
TAB Project Sponsor•
Overall project success for TAB in support of the Client.
Evan McSham— •
Escalation contact for TAB.
•
Timely execution of all contractual matters in collaboration with Client Project Sponsor.
TAB Client Services•
Delivery of all commercial aspects of this Proposal, SOW and potential Change Orders.
Robbie Clark •
Attends Team meetings as appropriate.
TAB Project Manager•
Single point of contact for Client to collaborate and proactively manage and resolve project
related matters to ensure that all success criteria are met.
•
Ensure that all required TAB resources are available to execute the work and/or address
matters that may arise, in a timely manner, to effectively and efficiently manage timeline
impacts or cost changes.
•
Leads the planning, execution of all deliverables.
•
Attains timely sign -off on TAB deliverables from Client's Project Manager.
•
Issues recurring Client Status Reports on the progress of work against plan.
•
Manages any scope change through the Change Management Process.
•
Chairs all project meetings with Client and TAB team.
•
Develops the Functional Specifications.
•
Configures the system in accordance to the confirmed Functional Specifications.
•
Tests the reconfigured system to confirm Functional Specifications.
•
Trains target Client staff to test the reconfigured system.
•
Performs other consulting services as defined in the scope or mutually executed Change
Orders.
Page 6 of 19
Investment Summary and Timeline
The following investment and timeline summary are based on the parameters noted in this SOW.
All pricing is based on a continuous project with no stoppages or interruptions.
Upgrade Project
Phase 1, 2 & 3: Kick -Off and Confirm Functional Specifications
• IGck-Off
• Confirm Functional Specifications (FS)
o Delivery of draft Functional Specifications by TAB
o Review with Client
o Update FS based on review.
o Mutually sign -off (TAB and Client)
o Follow Change Management Process if required
• Prepare for the configuration of FusionRMS
Phase 4: Configuration in Development Environment
• Configure FusionRMS to confirmed Functional Specifications (Phase 2).
• Testing of configured FusionRMS system in Development Environment by TAB.
Phase 5 & 6: Systems Acceptance
• TAB completes Super User Training Plan and Documentation
• TAB provides up to 1 hour of Super User Training to up to 2 Client Super Users.
• Client Super Users performs User Acceptance Testing (UAT) of configured FusionRMS system in
Development Environment.
• Iterate until no written defects by Client against confirmed FS
(estimate 2 iterations required).
• Client issues System Acceptance sign -off
Phase 7: Deployment of Accepted System into Production
Professional Services Total: $17,150.00 USD
Please note:
1. 100% of Configuration Fees will be invoiced upon SOW signature.
2. No refunds will be provided on these services, all efforts expended in accordance with this SOW
3. Applicable taxes will be added to invoices.
Timeline Summary
The specific timeline to complete the above work will be determined as part of the first Phase of
the project, following the acceptance of this SoW.
Page 8 of 19
N-2023-219
Authorization
Client commits to engage TAB Products CO., L-C, to undertake the project outlined in this Statement of Work
dated July 271h, 2023. Upon receiving this Statement of Work, signed by Client, TAB agrees to schedule
this project for kick-off.
In agreeing to work with TAB, Client acknowledges that the project scope, deliverables, and methodology
outlined in the Statement of Work are satisfactory and agrees to accept the project fees as specified in this
document. Client also acknowledges that the Terms and Conditions set in Appendix B are accepted.
CITY OF SANTA ANA
Kristine Ridge, City Manager
Date
TAB Products CO., LLC
�'a� yS�u�ied
Authorized Sign re
Sara Hughes Director of Admin
Name, Title
7131123
Date
Timeline
Once this document has been fully endorsed by both parties, defined timelines for the project will be
established.
APPROVED AS 70 FORM
-- M. Pmk, Auiwnt City Amoroty
c �'//7
Michael Garcia, Executive Director
Community Development
Date: I7i3 7 J
ass"'
City Clerk:
Page 9 of 19
Appendix A: Change Management Process
The Change Management Process will be used to formally discuss, document and approve any
changes to the specifications stated in this SOW that alters scope, deliverables, success criteria,
approach, assumptions, timeline and/or pricing. The Change Management Process steps include:
1. Either parry may initiate/request a discussion to alter specifications stated in this SOW.
2. Upon mutual agreement, the agreed changes will be documented in a Change Order as shown
below.
3. Once signed by both parties, the Change Order will be authorized for execution.
4. Upon completion of the Change Order, official sign -off must be attained from the requestor.
[Change Order Title]
Change Order #:
A unique number identifying this Change Order. Will start with "1" and go
to N.
Date:
The date the Change Order was written.
Description:
Brief description of the Change.
Scope:
The scope of this change includes:
Lists scope of the change (similar to the scope section of the SOW).
Etc...
Deliverable:
State the deliverable.
Success Criteria:
State the success criteria that must be met to attain sign -off.
Assumptions:
State the assumptions applicable to this Change Order.
Risks:
State the risks associated with this Change Order.
Timeline:
State the timeline in which the Change Order. Will start and be completed.
Price and Terms:
Project Impact:
State the price of the Change Order and payment terms.
State the impact to the original SOW by executing this change (i.e. timeline
extension).
Per: Per:
F
Date:
Date:
TAB Products
Page 10 of 19
Appendix B: General Terms and Conditions
The License and Maintenance portion of this SOW is governed by terms and conditions of Software License
Agreement between the Client and TAB Products CO., LLC ("TAB").
This Configuration Services of this SOW is governed by the following:
GENERAL TERMS AND CONDITIONS — For All Services
For and in consideration of the payments made by Customer, TAB Products CO. LLC., (hereafter
"Contractor"), agrees to provide, as an independent contractor, the services (the "Services") described in the
attached Proposal and Services Agreement, as applicable, subject to the provisions, terms and conditions
hereof (collectively, the "Agreement").
1. Description of Project - The project and related Services shall be as described in the Services Agreement
and related Schedules. All Proposals, unless otherwise expressly stated therein, are deemed withdrawn by
the Contractor at the end of (30) thirty days from the date offered.
2. Itemization - Each item on order by a Customer shall be treated as a separate Service and billing may be
issued thereon for partial or full completion of such items.
3. Billing Method for Labor and/or Services - Contractor may bill Customer monthly for Services performed
during the month.
4. Payment Terms are net thirty (30) days - Invoices outstanding for more than forty-five (45) days are
subject to a late payment fee and reasonable cost of collection, including attorney's fees. If payments are
not made in accordance with Contractor's standard terms, the unpaid balance shall be subject to interest
rate of 2% per month, or 24% per year.
5. Conflicts with Purchase Order - In the event that the Customer issues a purchase order, which contains
terms, and or conditions which conflict with the Proposal and these terms contained herein, such conflicting
terms shall be rejected and null and void. Acceptance of any conflicting terms contrary to those stated herein
requires a specific written notice of acceptance by the Contractor. Otherwise, conflicting terms are deemed
rejected. All non -conflicting terms shall remain in force and the tender of a purchase order shall be deemed
acceptance of such terms.
6. Claims - All claims against Contractor must be made in writing and delivered to Contractor within thirty
(30) calendar days after delivery of work product to Customer, and if not so made, any liability of Contractor
with respect thereto will cease and terminate, and if not so made, shall be deemed waived.
7. Prices and Job Estimates- The prices for Services are shown in the Proposal and/or Fees Schedule
attached to the Proposal or Services Agreement, as applicable. Estimated volumes, which may be shown
therein, are based upon information approved by Customer. Payments by Customer to Contractor shall be
based on the Fees Schedule on actual quantities as measured by Contractor.
8. Risk of Loss - Unless otherwise specified in the Proposal or Services Agreement, if the Services to be
provided are performed at other than the Customer's place of business, Customer is responsible for delivery
of records/documents to, and their return from the location designated for the performance of the Services,
Customer shall bear all risk of loss while such documents are in transit and until the documents are accepted
in writing by Contractor at the designated service location. Contractor shall be responsible for Customer's
Media while it is in its possession and its responsibility shall end a reasonable time after notice by Customer
to Contractor of an acceptance of the new media or data.
9. Special Delivery -All costs of transportation, including freight, postage, overnight courier, UPS, pick-up,
delivery, and local courier charges incurred by Contractor in connection with the Agreement will be prepaid
and will be billed to Customer as incurred unless special terms and conditions are specified in the Fees
Schedule.
10. Subcontracting -Contractor reserves the right to perform its obligations hereunder by means of
subcontracts with qualified third parties and to enter into such subcontracts as it deems expedient and
proper under the circumstances without the requirement of notification to Customer. Notwithstanding such
subcontract, Contractor shall nevertheless remain responsible to Customer for Services provided and to be
provided hereunder.
Page 11 of 19
11. Non Solicitation -Customer acknowledges and agrees that during the term of the Agreement, and for a
period of six (6) months following the termination or expiration of the Agreement for any reason, neither it
nor any employee or agent of Customer shall, either directly or indirectly, without the prior written consent of
Contractor: solicit, influence or induce or attempt to solicit, influence or induce, any employee or
subcontractor of Contractor who has become known to Customer as a result of the provision of Services
pursuant to the Agreement, to become an employee or contractor of Customer, or to provide services to
Customer in any manner, including without limitation, as an officer, director, owner, partner, employee,
independent contractor, consultant, advisor or representative; or solicit, influence or induce or attempt to
solicit, influence and induce, any employee or subcontractor of Contractor who has become known to
Customeras a result of the provision of Services, to leave their employmentwith Contractor for any reason.
12. Limitation of Liability -In no event shall either party be liable to the other for any indirect, incidental,
exemplary, special or consequential damages of any kind or nature (including with respect to loss or
destruction or damage to any Customer documents, loss of any information or data contained in any
Customer documents, costs of recreating Customer documents or loss of revenue or profits or business
interruption or other non -direct commercial or economic loss or damage of any kind) suffered by Customer
howsoever caused and regardless of the form or cause of action, even if such damages are foreseeable or
the first party has been advised of the possibility of such damages.(A) Subject to Section 12(B), in the event
of any failure or breach by Contractor in the performance of the Services or its obligations under the
Agreement, Contractor's total liability and obligation to Customer, in the aggregate for any and all such
failures or breaches, shall be limited to the actual direct damages suffered and shall not exceed an amount
that is equivalent to the flat monthly fee portion of the fees multiplied by twelve. (B)Notwithstanding section
12(A), in the event of any loss or destruction or damage to any Customer documents, Contractor's liability in
respect of such loss or destruction or damage shall be limited to $1.00 per Customer file. The foregoing
limitations of liability shall apply in respect of any expense, damage, loss, injury, or liability of any kind,
regardless of the form of action or theory of liability (including for breach of contract, tort, negligence, strict
liability, by statute or otherwise) and shall survive a fundamental breach or breaches or the failure of the
essential purpose of the Agreement or of any remedy contained herein. Customer agrees that the limitations
and exclusions contained in this section are reasonable based upon the commercial circumstances, including
the quantum of fees, of the Agreement, and Contractor would not have entered into the Agreement but for
Customer's agreement to the limitations contained herein. Customer acknowledges that Contractor does not
and shall not insure any Customer documents against loss, damage, destruction or any other injury of any
kind or nature whatsoever.
17. Confidentiality -Contractor agrees to exercise caution and discretion in safeguarding Customer's
materials, information and data which are confidential and are clearly so designated. Contractor also agrees
not to divulge or communicate in any manner any financial, marketing or any information learned performing
work for Customer which would be considered confidential or the nature of trade secrets. Contractor shall
be responsible to Customer only in the event of a willful and material disclosure of such information or data.
14. Default - Each party has the right to terminate the Agreement if the other party breaches or is in default
of any obligation under the Agreement which default is incapable of cure or which, being capable of cure,
has not been cured within thirty (30) days after receipt of notice of such default (or such additional cure
period as the non -defaulting party may authorize).
15. Termination -Each party has the right to terminate the Agreement, for any reason, by providing thirty
days (30)written notice of termination.
16. Notices - All notices or other communications which are required or may be given to Contractor pursuant
to the terms of the Agreement, shall be in writing, shall be effective upon receipt, and shall be delivered by
Federal Express or a similar courier, personal delivery or certified or registered air mail, addressed as written
below.
TAB PRODUCTS Co. LLC
605 Fourth Street
Mayville, Wisconsin 53050
Attn: Betsy Streblow
Page 12 of 19
17. Governing Law - This Agreement shall be construed, governed and enforced in accordance with the laws
of the State of California and the parties irrevocably submit to the exclusive jurisdiction of the state and
federal courts located in Orange County, California.
10. Integration and Entire Agreement - The Agreement together with Customer's Letter of Commitment and
the other documents (if any) referred to herein set forth the entire understanding between the parties and
supersede all previous and contemporaneous, written or oral negotiations, commitments, understandings
and agreements relating to the subject matter hereof and merge all prior and contemporaneous discussions
between the parties. All capitalized terms used but not defined herein have the meaning ascribed to them in
the Proposal and Services Agreement, as applicable. No party shall be bound by any definition, condition,
representation, warranty, covenant or provision other than as contained in the Agreement.
19. Assignment - The Agreement shall be binding on the parties hereto and their respective successors and
assigns, but neither party may, or shall have the power to, assign this Agreement without the prior written
consent of the other, which consent shall not be unreasonably withheld.
20. Amendment -Any amendment or modification to the Agreement must be in writing and signed by the
party against whom enforcement is sought.
21. General Provisions - Any provision of the Agreement, which shall prove to be invalid, void,
unenforceable, or illegal shall in no way affect, impair or invalidate any other provision and all such other
provisions of the Agreement shall remain in full force and effect.
22. Force Majeure - A party shall not be liable for any failure of or delay in the performance of the
Agreement (excluding payment obligations) for the period that such failure or delay is due to causes beyond
its reasonable control, including but not limited to earthquake, flood, fire and other acts of God, war,
terrorism, strikes or labor disputes, embargoes, government orders or any other force majeure event. If a
force majeure event extends for a period in excess of 60 days in the aggregate, either parry may immediately
terminate the Agreement upon written notice.
23. Language of Agreement- The parties agree that the Agreement and all notices, instruments and other
documents pertaining thereto and to the Services, be drawn up in the English language.
Page 13 of 19
Appendix C: Milestone Sign -Offs
The FusionRMS application has been reviewed and tested according to the Client documented test plan
The application passed all tests and is considered complete as described within the Statement of Work and
Functional Specification documents, as well as any related documents or attachments, and hereby accept the
application as functional and complete.
TAB Products is hereby authorized to proceed with this TAB FusionRMS application implementation as
specified within the Statement of Work document.
For The Client
Authorized Signature
Printed Name
Title
Date
►"N' i
For TAB Products CO., LLC
Authorized Signature
Printed Name
Title
Date
MI i
Page 14 of 19
Appendix D: Sample Super User Training Agenda
Execution of learning management system and "train the trainer" strategy for both End User and System
Administrator functionality will be completed as part of "Go -Live" Preparation. The following training topics
will be covered during the training activities.
Super User Training
• Application Navigation
• Searching
o Query, Filter, Sorting
• Creating Records
• Editing Existing Data
• Printing Labels
• Electronic Record Keeping
• Document Viewer
• Scanning into the document viewer
• Physical Record Tracking
o Transfers/Requests
Administrator Training
• Record Retention Maintenance & Workflows
• Bulk Data Importing
• Reporting
• Security & Permissions
• Dictionary Maintenance
• View Maintenance
• User Experience Link Script differences
Documentation
• To be drafted and provided as part of the Training task including:
o Web Access Documentation
o Desktop Client Documentation
o Administrators Documentation
Page 15 of 19
Appendix E Functional Specifications
Functional Specifications ("FS") will be documented for each key area of modification: Security &
Permissions, User Interface, Search, Access, Label/Printing/Reporting, Data and Integration.
TAB typically accomplishes completion of the Functional Specifications through the following steps:
1. Providing the client with a draft Functional Specifications (this Appendix) by area capturing:
a. Functional Specifications from previous discussions with the client and/or information
provided by the client.
b. Typical assumption on Functional Specifications most likely relevant given client provided
information.
c. Identification of gap(s) in the draft requiring client attention in addition to the assumptions
utilized.
d. An approach to test the confirmed FS noted above.
e. Key success criteria which must be met in order to attain sign -off on the FS for a given area.
2. TAB hosting a one hour review session on a screen share for the Client Project Manager and key
subject matter experts with the authority to confirm the FS.
a. Walk through FS and confirm all FS items are understood.
3. TAB will then provide the Functional Specifications as an artifact to the project and a reference to
the User Acceptance Testing Phase of the project.
Page 16 of 19
Technical Environment & Access
Desired FS from previous
1
discussions or client provided
All users will access the solution via web -access.
information
Typical FS assumptions related to
TAB will be enabling web -access, the desktop client will
2
the above items
remain in use on the server and for administrative
purposes only.
3
Typical Testing Approach
Confirm ability to access functionality in the newversion
of the client previously used.
Configuration Taxonomy
Desired FS from previous
1
discussions or client provided
NA
information
2
Typical FS assumptions related to
NA
the above items
3
Typical Testing Approach
NA
Security & Permissions: The security model utilized within FusionRMS is group based. Users are placed into
one or more groups, inheriting the security permissions of the group(s). User and Group maintenance is
performed within the application, utilizing the standard FusionRMS Security module. Security permissions of
groups (view, add, edit, etc.) are also handled directly within the FusionRMS application.
1
Desired FS from previous discussions
Existing User Groups and Users will be imported to the
or client provided information
new version of Fusion.
2
Typical FS assumptions related to the
Existing login structure will remain as is.
above items
3
Typical Testing Approach
Ensure log in abilities of testing users; ensure users
are able to execute all business -critical activities
Reports
1
Desired FS from Previous Discussions
N/A
or Client Provided Information
2
Typical FS assumptions related to the
N/A
above items
3
Typical Testing Approach
NIA
Page 17 of 19
Search
,I
Desired FS from Previous Discussions
The ability to search records and the location of
or Client Provided Information
records via desktop and web -access.
2
Typical FS assumptions related to the
N/A
above items
3
Typical Testing Approach
N/A
Labels/Printing/Exporting
1
Desired FS from Previous Discussions
N/A
or Client Provided Information
2
Typical FSassumptions relatedtothe
N/A
above items
3
Typical Testing Approach
N/A
Linkscripts I Workflow Integration
Typical FS assumptions related to the
There are a number of known linkscripts that will
1
above items
require review/ upgrading the custom code.Assumed
5 Linkscri ts.
2
Current gap(s) remaining if the above
Potentially additional Llinkscripts may need to be
is accurate
reviewed. TBD during solution review
3
Typical Testing Approach
TBD
Data
1
Typical FS assumptions related to the
TAB will confirm, transform and migrate existing data
above items
as part of the upgrade process.
2
Current gap(s) remaining if the above
N/A
is accurate
3
Typical Testing Approach
N/A
Integration
1
Typical FS assumptions related to the
No third -party connectors or APIs to be integrated in
above items
this phase
2
Typical Testing Approach
N/A
On behalf of City of Santa Ana I On behalf of TAB Products CO., LLC
Authorized
Printed
Authorized
Printed
Page 18 of 19
Appendix F: Terms and Definitions
Test Environment
The Test Environment is a single server or dedicated virtual machine that holds all the components of the FusionRMS
solution. This includes the Slim Server, Desktop Image Server, Web Image Server, IIS and SQL Servers. The Test
Environment can be low in comparison to the Production Environment as there will be a small numberof users accessing
the system at a time. It is identical in versioning to the Production Environment, having the same operating system,
component versions, hotfix levels, etc. This ensures consistency in performance and testing of the solution.
The Test Environment will act as a test bed for the Client to execute User Acceptance Testing (UAT), solution verification
and continued solution management. Given that the records management solution is a business -critical application, TAB
highly recommends that the Test Environment be maintained by the Client through the entire lifetime of the solution,
allowing for the proofing and solutioning of future changes to the software.
Development Environment
A TAB hosted dedicated and secure environment in which TAB's technical team will perform the developmental and
configuration services prior to delivery to the Client. Similar to the Test Environment, it will be identical in versioning to
the Production Environment
Production Environment
The live technical environment integrated into the Client's business critical processes and systems. This is the
environment the userbase will connect to during operation of the business.
Readiness Checklist
A TAB authored list of solution dependent services and applications to be installed and configured by the Client prior to
engagement of TAB's technical team. By signing -off on this checklist, the Client confirms that the environment will meet
the needs of the FusionRMS solution and is properly prepared for TAB's team. TAB will of course be available to support
in the installation of non -TAB software but may need to engage in services outside the scope of the project described
here to do so.
LinkScript
A proprietary tool and scripting language inside the FusionRMS solution allowing for rule -based workflow logic to be
integrated into the solution.
Super User Training Session
TAB's training is structured to provide FusionRMS subject matter experts and power users inside the Client organization
with the knowledge to use FusionRMS and the features and enhancements described in this document. These trainings
are intended to allow the project leads to train the userbase in preparation of the user acceptance testing and for day
forward operation of the solution.
Functional Requirements
Detailed workflow -based needs of the software solution. These are typically the responsibility of the Client to describe
and detail.
Functional Specifications
The translation of the Functional Requirements into deliverable configurations for the software solution. This will be the
responsibility of TAB to describe.
User Acceptance Testing
Also called beta testing, application testing, and end user testing - is the phase of the project in which the software is
tested by the intended audience.
Page 19 of 19