Computer Sciences Corporation
Work Order
March 8, 2022 - Prices Valid Until 03/31/22
Agreement No. 01-STE-0106 Work Order No. 5
Sisense Reporting Assumptions
Sisense End User training includes training for those who will be creating and modifying dashboards.
Sisense System Admin training includes training for those who will be administering the Sisense system. It
covers topics such as adding and managing users and maintaining elasticubes.
To allow for an integration of Sisense dashboard within the UX version of RISKMASTER/Assure Claims,
Customer must PURCHASE and enable single sign-on (SSO).
Single sign-on (SSO) is required if Customer wants to see a Sisense Dashboard within RISKMASTER/Assure
Claims, otherwise SSO is not required.
Linux server is required for on-premise. Customer is opting for SAAS AWS so this is not required.
Configuration Training Assumptions
Assure Claims Configuration training should always be done at Customer's site and not via web session.
Assure Claims Configuration training includes training on system configuration and customization options
as well as training on system administration and maintenance activities. This should be conducted with no
more than 5 individuals in the training class.
Assure Claims Configuration consulting provides as-needed assistance with configuring the Assure Claims
system to reflect desired business processes. It does not include CSC staff completing the actual
configuration.
Data Services Assumptions
Duplicate Employee Names: A list of duplicate employees can be extracted and the duplicate record marked
as soft deleted in Riskmaster so it won’t impact any existing claim/event. New claims entered in Riskmaster
will not see duplicate employees while selecting an employee.
Employee “Department” - Customer should provide a list of employee numbers along with their correct
department. CSC will write a SQL script to attach the employee with the required correct department.
Customer will provide a copy of its Riskmaster production database to start the data cleanup process in CSC
development environment.
Customer will provide Riskmaster database to CSC via SFTP.
CSC will write SQL scripts to clean up the data in Customer’s existing Riskmaster database.
Any changes needed to the existing BI reports is out of scope. Customer has the responsibility to update its
existing BI reports with these changes as needed.
CSC will soft delete the duplicate employees. Criteria for duplicity will be same employee number, name,
and address unless customer wants to add or exclude a name and address. Legacy data will not be updated.
Customer will ensure that the ‘manual weekly upload’ of employees matches the existing records on
employee numbers to maintain uniformity. The weekly upload should not create a new employee if the
employee number exists already in Riskmaster. It should also ensure that if it is updating the employee
department that the correct employee department should be updated by the weekly upload. This activity
is out of scope of this Work Order.
There will be two (2) cycles of delivery: first Test/Training environment, and then Production. Should
Customer want additional delivery, the additional delivery hours will require a change control order and be
subject to additional fees.
Database Analysis Assumptions
Customer will share or provide a copy of its RISCMASTER Production database, View database, Session
database, TaskMaster database and Security database.
Rhodes — SR-0020110506 - GDC