Version 1 Page 1 of 24 CISPro Global (SQL Server) to BIOVIA CISPro/CISPro Cloud Data Migration Service Overview This document outlines the scope and process for migrating data from the CISPro Global SQL Server to BIOVIA CISPro or BIOVIA CISPro Cloud. This service assumes the customer has purchased a separate BIOVIA CISPro or BIOVIA CISPro Cloud standard implementation service for the installation, configuration, and training for the core CISPro application. It is also assumed that the same customer subject matter experts for the migrating CISPro Global installation and the BIOVIA CISPro/CISPro Cloud standard deployment service will also be involved as a part of this data migration service. Specific timing of the data migration tasks will be coordinated by the BIOVIA Project Lead as a part of the overall implementation project. Appendix A provides a listing of main data migration service steps that are included as a part of the data migration service. The sections below provide a high level overview of the key difference between CISPro application versions. CISPro product names used in this document are: Current Versions o BIOVIA CISPro – installed locally o BIOVIA CISPro Cloud – hosted by BIOVIA Previous Versions o CISPro Global – installed locally Note: BIOVIA Global is available in two configurations. One running on a Oracle database and the second running on a SQL Server database. All references of BIOVIA Global in this document refer to the SQL Server version. A separate migration service is available for CISPro Global (Oracle). Key Data Architecture Conversion Differences It is important to understand that there are structural differences between the CISPro Global and the BIOVIA CISPro/CISPro Cloud application. In many cases there are direct translations between data fields between versions. Appendix B provides a full listing of standard fields that are included as a part of the data migration. User defined container and material properties are also migrated to the new platform which are not included in Appendix B due to the custom nature of the fields. The following sections outline specific changes in the data model and related migration behavior that customers should be aware of: Chemicals In the CISPro Global platform, chemicals are considered unique based on the chemical name only, with multiple packages to define vendor specific information as a child record. In the new BIOVIA
Transcript
Version 1 Page 1 of 24
CISPro Global (SQL Server) to BIOVIA CISPro/CISPro Cloud Data Migration Service
Overview
This document outlines the scope and process for migrating data from the CISPro Global SQL Server to
BIOVIA CISPro or BIOVIA CISPro Cloud. This service assumes the customer has purchased a separate
BIOVIA CISPro or BIOVIA CISPro Cloud standard implementation service for the installation, configuration,
and training for the core CISPro application. It is also assumed that the same customer subject matter
experts for the migrating CISPro Global installation and the BIOVIA CISPro/CISPro Cloud standard
deployment service will also be involved as a part of this data migration service. Specific timing of the
data migration tasks will be coordinated by the BIOVIA Project Lead as a part of the overall
implementation project. Appendix A provides a listing of main data migration service steps that are
included as a part of the data migration service.
The sections below provide a high level overview of the key difference between CISPro application
versions.
CISPro product names used in this document are:
Current Versions
o BIOVIA CISPro – installed locally
o BIOVIA CISPro Cloud – hosted by BIOVIA
Previous Versions
o CISPro Global – installed locally
Note: BIOVIA Global is available in two configurations. One running on a Oracle database and the
second running on a SQL Server database. All references of BIOVIA Global in this document refer to
the SQL Server version. A separate migration service is available for CISPro Global (Oracle).
Key Data Architecture Conversion Differences
It is important to understand that there are structural differences between the CISPro Global and the
BIOVIA CISPro/CISPro Cloud application. In many cases there are direct translations between data fields
between versions. Appendix B provides a full listing of standard fields that are included as a part of the
data migration. User defined container and material properties are also migrated to the new platform
which are not included in Appendix B due to the custom nature of the fields.
The following sections outline specific changes in the data model and related migration behavior that
customers should be aware of:
Chemicals In the CISPro Global platform, chemicals are considered unique based on the chemical name only, with
multiple packages to define vendor specific information as a child record. In the new BIOVIA
Version 1 Page 2 of 24
CISPro/CISPro Cloud version, chemicals are unique based on a combination of the chemical name, supplier
name, and part number values.
These images outline the main changes between the CISPro Global platform and BIOVIA CISPro/CISPro
Cloud:
CISPro Global material to container hierarchy:
Material Material Name Packages Manufacturer, Supplier, Product Number, SDS Packdetail (Sizes) Initial Quantity/Capacity, Unit of measure, Catalog Number, Container Description Containers Barcode, Location, Owner, Received Date, Expiration Date
BIOVIA CISPro/CISPro Cloud material to container hierarchy:
Material Material Trade name + Supplier + Part Number, SDS Sizes Initial Quantity/Capacity, Unit of measure, Catalog Number Containers Manufacturer, Barcode, Location, Owner, Received Date, Expiration Date
As a result of the change, customers can expect the number of materials in BIOVIA CISPro/CISPro Cloud to
directly correspond to the number of unique packages in the CISPro Global system. The illustration
below shows examples of chemical records and the converted data model between both platforms with
the same chemical highlighted for easier comparison:
Material Packages Packdetail Containers
Material Sizes Containers
Version 1 Page 3 of 24
Site Specific Records In BIOVIA CISPro/CISPro Cloud, sites are simply an additional location tree layer and do not control or
segregate access. This means that there is no longer a need for distinct location trees for each site, and
container access continues to be controlled by inventory group access. All sites also share a single set of
materials across the entire BIOVIA CISPro/CISPro Cloud database.
Roles and Permissions While user role names are migrated, due to the underlying feature and object permission changes
between systems, user defined role permissions are not directly migrated to BIOVIA CISPro/CISPro Cloud.
These will require customer review prior to migration. The migration process will copy permissions from
the standard BIOVIA CISPro/CISPro Cloud “CISPro_Admin” default role for any CISPro Global role marked
as an administrator. Any other roles created in the new platform as a part of the data migration will
have permissions copied from the default “CISPro_General” role.
Action: Customers must review all roles after the migration is complete to validate and provide
any needed permission updates within the new version.
Inventory Group Access Locations are assigned to the same inventory groups after migration. In BIOVIA CISPro/CISPro Cloud, role
access is assigned by role and/or current work unit instead of by individual user account, and can be
provided in a “wildcard” type setup. Users will not have access to inventory groups created as a part of
the migration by default.
Action: Customers will need to review the inventory group permissions to setup appropriate
access as required.
Version 1 Page 4 of 24
Historic Data Due to incompatibilities between platforms, historic data is not migrated as a part of the service. This
includes recorded audit events, container dispense history, and logically deleted records.
Action: It is recommended that customers create and run reports and/or create a backup of the
CISPro Global data to retain access to historic information.
Migration Process Information
The primary objective of this migration service is to accurately translate non-deleted/disposed CISPro
Global inventory data into a new BIOVIA CISPro/CISPro Cloud installation.
SQL scripts and procedures will be used by BIOVIA to help automate data preparation and clean-up
whenever possible. The scripts and clean-up processes help avoid core data issues transferring into the
new platform, as well as managing data conflicts between sites.
Action: The customers will review, clean-up and approve all key CISPro Global data prior to the
migration into BIOVIA CISPro/CISPro Cloud to help ensure a clean transition.
Database Platform Conversion BIOVIA CISPro and BIOVIA CISPro Cloud use Oracle exclusively as a database platform. In order to
perform a data migration from CISPro Global SQL Server, customers will be required to send a copy of a
full CISPro database export to BIOVIA for conversion to Oracle and migration into BIOVIA CISPro/BIOVIA
CISPro Cloud. This conversion will need to be performed for the first non-production test migration and
again for the final production environment migration.
Customer Action:
Export CISPro Global SQL Server database and deliver files to BIOVIA
(For BIOVIA CISPro) Restore Oracle schema data
BIOVIA Action:
(For BIOVIA CISPro) Provide migration complete Oracle schema data to customer
(For BIOVIA CISPro Cloud) Restore Oracle schema data to hosted environment
Production Cutover During the production migration, the CISPro Global SQL Server data cannot be altered as any changes to
the CISPro Global data after delivery to BIOVIA will not be incorporated into the final BIOVIA
CISPro/BIOVIA CISPro Cloud data. BIOVIA advises customers to manually log receipts for entry in the
new BIOVIA CISPro/BIOVIA CISPro Cloud system once they are live in the new system. Customers are
also able to store move, owner, and dispose scan information from the CISPro Mobile (Janam) scanners,
uploading the scan changes text files into BIOVIA CISPro/BIOVIA CISPro Cloud after go-live.
It is a goal for BIOVIA to keep the amount of production server downtime to a minimum during the data
migration project. Customers should expect approximately 4 days for the production migration to be
completed. More accurate migration timing will be provided as the conclusion of the non-production
migration steps.
Version 1 Page 5 of 24
Once BIOVIA verification on the final BIOVIA CISPro/CISPro Cloud production system is complete, users
can begin training and start using BIOVIA CISPro/CISPro Cloud.
Focus Areas
This data migration process is divided into three focus areas. These include:
1. Data Preparation
2. Data Migration
3. Report and Label Conversion
Each area is an integral part of the project and requires the customers dedicated time and resources to
ensure successful completion.
Action: Customer participation includes input, feedback, review, and approval. The more active
the involvement will result in a shorter completion time.
Focus Area One – Data Preparation
The first step in the migration process is a preparation of the CISPro Global data to be converted to the
new system. The following are the specific steps used to prepare the CISPro Global data for data
migration:
Review of Data Extract The data migration project is an excellent time for customers to review their current CISPro Global data
and apply clean-up and record merging. This will greatly contribute to a cleaner and less redundant post-
migration data result. BIOVIA provides to the customer several reports or SQL queries that run against
the CISPro Global data to generate spreadsheet (Typically Microsoft Excel) based content. See Appendix
C for more detailed information on the types of data that will be reviewed, and the recommended
customer activities for each data type.
Action: Customer review of the resulting data is required to determine if any record merges
should take place, such as addressing multiple similar instances or misspellings of the same
vendor name. Examples would be names such as “JT Baker” and “J.T. Baker”. In this case,
customers can select a specific target ID to merge a given record into.
BIOVIA will use this target ID information to generate SQL scripts to perform these actions in the CISPro
data in the next steps of the data preparation.
Manual Customer Merge and Clean-up of Data Once the customers review is complete and any clean-up items have been identified and marked in the
resulting customer review Excel files, customers will also need to review the entire dataset to determine if
there are any chemicals that should be merged together, for example: “Acetone” and “Dimethyl Ketone”.
The BIOVIA CISPro Global data should also be reviewed by customers to correct and update packages that
do not have product numbers where this information is available. Packages without product numbers
are treated separately as a part of the migration process to BIOVIA CISPro/CISPro Cloud; a chemical with
two packages using the same manufacturer/supplier and only one product number will result in two
chemicals within BIOVIA CISPro/CISPro Cloud.
Version 1 Page 6 of 24
Customer Action:
Review BIOVIA provided data for consolidation or removal
Merge chemical records as required
Update packages to provide product numbers
BIOVIA Actions:
Provide extraction SQL scripts and/or reports for customer review
Provide suggestions and guidance for recommended clean-up activities
Focus Area Two – Data Migration
Once the data review process is completed, the next focus area is applying updates to the CISPro Global
data and performing the data migration into BIOVIA CISPro/CISPro Cloud. This process is repeated twice,
first in the non-production environment with a user acceptance approval, then again for the final
migration in the production environment. The following sections outline the components of the data
migration process:
Application of CISPro Global SQL Data Preparation Scripts During the data migration process, BIOVIA will run SQL scripts that will implement data merges as a result
of the customer review of the data extractions in Appendix C. These changes normally can’t be performed
from within the CISPro Global user interface.
The final script that is executed in the CISPro Global data performs a material “roll-up” that combines
chemicals from all sites into a single set of Global materials. It is possible for customers to select a
specific site as a primary target, or master, data site to start the roll-up process. This allows customers to
designate which particular target site has better quality and/or more complete content to merge other
matching chemicals into. Appendix D shows the flowchart process for the roll-up script and the specific
material merge actions the script performs.
The following images demonstrate how a specific chemical name that exists in multiple CISPro Global sites
as local materials are merged together in the roll-up script. The blue highlighted areas shows the
relationships between the parent and child records for all the examples.
The first step is roll-up/merge of chemical records using the process from Appendix D, repeated for each
distinct material name until only a single set of Global materials remain:
Version 1 Page 7 of 24
Next, duplicate packages are merged for each distinct chemical to remove record redundancy:
As a final merge step, Packdetail/size data is then merged for each individual package to combine
duplicate size information:
Version 1 Page 8 of 24
Action: After completion, customers will review and approve the final merged data.
Data Migration Tool Execution BIOVIA will perform steps that includes first converting the customer provided SQL Server based CISPro
data to CISPro Global Oracle, run the data preparation scripts, and finally use migration tools to upgrade
the data to BIOVIA CISPro/BIOVIA CISPro Cloud.
For BIOVIA CISPro customers, BIOVIA will provide an export of the completed Oracle data to restore into
the customer’s BIOVIA CISPro environments. With customers that are moving to BIOVIA CISPro Cloud,
access will be provided to a non-production hosted environment containing the completed data for
review, updates, and user acceptance testing. The final data migration will be applied to the customer’s
hosted production environment.
Customer Actions:
Provide the “master” target site ID of records to use.
Edit inventory group access to control permissions.
Update user role permissions in BIOVIA CISPro/CISPro Cloud as required
BIOVIA Actions:
Create SQL scripts to apply customer provided data consolidation/removal tasks
Execute migration tool steps
Data Migration Verification Process
To ensure a proper transfer and translation of data between the two environments, three separate
methods are used by the BIOVIA Project Lead as a part of the data verification process:
Migration Tool Reported Error Investigation As a part of the migration tools, logs are generated for any records that are not able to be converted to
BIOVIA CISPro/CISPro Cloud. The migration tool log files are reviewed by the BIOVIA Project Lead
throughout the migration process to ensure that no errors take place as a part of the export and import
processes. Should errors be encountered, the BIOVIA Project Lead will provide steps on how to resolve
any issues.
Manual Comparison on Data Samples between Systems The second part of the post-migration checks involve opening similar records in both the CISPro Global
system and BIOVIA CISPro/CISPro Cloud in parallel. Checks are performed to ensure that data is
migrated as expected based on the field mapping in Appendix B. This step also ensures that records are
viewable in the new platform and there are no unexpected large scale data issues such as a specific record
type not loading within BIOVIA CISPro/CISPro Cloud.
Key Inventory Data Comparison on Representative Data Sample The final step in the verification process is a detailed field value comparison between systems for the core
inventory data. A report or SQL script is run in both the CISPro Global system and against the BIOVIA
CISPro/CISPro Cloud system to verify the data is the same between systems, accounting for any cosmetic
Version 1 Page 9 of 24
conversion differences. These reports/scripts pull a selection of container and related material
information for a comparison of data between environments. Discrepancies will be noted as either
expected/cosmetic, or that a problem has been encountered and requires corrective action.
Customer Action:
Perform user acceptance testing on the final converted data
BIOVIA Action:
Execute verification testing processes
Focus Area Three – Report and Label Conversion
Included with the data migration service, the customer may select up to four reports for conversion to the
newer BIOVIA CISPro/CISPro Cloud format. In addition to the four reports, the customer may select up
to eight label templates to convert to the new system. All selected reports and labels must be reviewed
by BIOVIA to ensure output compatibility between systems. Additional report/label changes may fall
outside the scope of this migration. BIOVIA will provide a service quote for this additional work.
As a part of the conversion process, some changes to the output data may occur based on the new
system. For example, this is a typical text location path value from each system:
CISPro Global Building,Room,Cabinet,Shelf
BIOVIA CISPro/CISPro Cloud Site > Building > Room > Cabinet > Shelf
The primary goals in the conversion process is to ensure previous reports and labels are replicated in the
new application. The new database platform, data storage format, and application differences between
CISPro Global and BIOVIA CISPro/CISPro Cloud may necessitate changes to the report output or data
filtering behavior. These are generally cosmetic in nature and the content of the output is typically still
preserved. There may also be some modifications needed to customer workflows to support new feature
enhancements. Specific information will be provided by the BIOVIA Project Lead as a part of the review
process prior to conversion work taking place.
Customer Actions:
Select up to four reports for conversion
Select up to eight label templates for conversion
Perform user acceptance testing on converted reports
BIOVIA Actions:
Analyze selected reports and labels for forward compatibility
Create new reports/views as appropriate to represent prior data content under the BIOVIA CISPro/CISPro Cloud system
Assist with the installation of converted reports and labels
Version 1 Page 10 of 24
Project Sign-off
The final step of the data migration project is the sign-off. This is a notice from BIOVIA that:
Focus Area One is complete - (Data Preparation)
Focus Area Two is complete (Data has successfully been converted)
Focus Area Three is complete - (New reports and labels have been verified)
Transition to the new CISPro application is complete
Change Order Process
If it becomes necessary to amend these deliverables for any reason, a Change Order Form will be prepared
by the BIOVIA Project Lead and submitted to the customer. The customer’s primary contact will obtain the
necessary approvals, signatures and a purchase order for any additional costs prior to commencement of
any work by BIOVIA.
Version 1 Page 11 of 24
Appendix A: Data Migration Project Task Outline
CISPro Global SQL Server to BIOVIA CISPro/CISPro Cloud Data Migration Service
Project Kick-off
Focus Area 1 - Data Preparation
Extraction of CISPro Global Data for Review
Conversion of CISPro Global SQL Server data to Oracle
Data Review and Feedback
Applying Data Cleanup from Feedback
Automatic Roll-up Merge Scripting
Review of Data Preparation Results
Focus Area 2 - Data Migration
Non-Production Migration
Interconnecting CISPro Global to BIOVIA CISPro
Extraction of CISPro Global data
Injection of extracted data to BIOVIA CISPro
Setup and enable data synchronization task
Verification of data migration
Delivery/Installation of test BIOVIA CISPro/Cloud data
Implementing Role Permissions
Production Migration
Delivery of Final CISPro Global Data for Migration
Conversion of CISPro Global SQL Server data to Oracle
Interconnecting CISPro Global to BIOVIA CISPro
Extraction of CISPro Global data
Injection of extracted data to BIOVIA CISPro
Setup and enable data synchronization task
Verification of data migration
Delivery/Installation of production BIOVIA CISPro/Cloud data
Implementing Role Permissions
Focus Area 3 - Report and Label Conversion
Conversion of up to 4 reports
Conversion of up to 8 labels
Installation of Converted reports and labels
User Acceptance Testing of Reports and Labels
Project Sign-Off
Version 1 Page 12 of 24
Appendix B: List of data fields mapped/included in the standard data migration
CISPro Global Column BIOVIA CISPro/CISPro Cloud Object Type
Object Property Object Property Type
Workunitid Work Unit Legacy Id
Workunitname Work Unit Name Text
inventorygroupid Inventory Group Legacy Id
inventorygroupname Inventory Group Name Text
Packageid Chemical Legacy Id
aqueous_solubility Chemical Aqueous Solubility Text
Casno Chemical CAS No Text
boiling_point Chemical Boiling Point Text
Formula Chemical Formula Text
Materialname Chemical Tradename Text
melting_point Chemical Melting Point Text
molecular_weight Chemical Molecular Weight Text
Ph Chemical pH Text
physical_description Chemical Physical Description Text
Ppe Chemical PPE Value
specific_gravity Chemical Specific Gravity Value
vapor_density Chemical Vapor Density Text
vapor_pressure Chemical Vapor Pressure Text
storage_conditions Chemical Storage and Handling Text
istier2 Chemical Is Tier II Checked
Productno Chemical Part Number Text
Einecs Chemical EC Number Text
compressed_gas Chemical Compressed Gas Checked
dot_code Chemical DOT Code Value
Subclassname Chemical Subclass Name Text
Expireinterval Chemical Expiration Interval Value
expireintervalunits Chemical Expiration Interval Name
openexpireinterval Chemical Open Expire Interval Value
openexpireintervalunits Chemical Open Expire Interval Name
Firecode Chemical NFPA Flammability
Healthcode Chemical NFPA Health
Reactivecode Chemical NFPA Reactivity
Nfpacode Chemical NFPA Special
Vendorid Chemical Supplier NodeID
physical_state_trans Chemical Physical State Value
nonhazardous3e_trans Chemical Hazardous Checked
ppe_trans Chemical PPE Value
struct_pict Chemical Structure Mol
Disposal Chemical Disposal Instructions Text
Smiles Chemical SMILES Text
Labelcodes Chemical Add Label Codes Text
Pictograms Chemical Pictograms Value
storagecompatibility Chemical Storage Compatibility Value
Packdetailid Size Legacy Id
packagedescription Size Description Text
Packageid Size Material NodeID
Version 1 Page 13 of 24
Catalogno Size Catalog No Text
Capacity Size Initial Quantity Value
unitofmeasureid Size Initial Quantity NodeID
Containertype Size Container Type Value
Acquisitiondate SDS Document Acquired Date Value
Description SDS Document Title Text
Captureddate SDS Document Revision Date Value
Packageid SDS Document Material NodeID
language_trans SDS Document Language Value
fileextension_trans SDS Document File Type Value
content_type SDS Document File ContentType
Filename SDS Document File Name
Document SDS Document File Blob
Href SDS Document Link Href
Description SDS Document Link Text
Legacyid SDS Document Legacy Id
Acquisitiondate Material Document Acquired Date Value
Description Material Document Title Text
Packageid Material Document Material NodeID
fileextension_trans Material Document File Type Value
content_type Material Document File ContentType
Filename Material Document File Name
Document Material Document File Blob
Href Material Document Link Href
Description Material Document Link Text
Legacyid Material Document Legacy Id
Receiptlotid Receipt Lot Legacy Id
ReceiptLotNo Receipt Lot Receipt Lot No Text
CreatedDate Receipt Lot Manufactured Date Value
PackageId Receipt Lot Material NodeID
Receiptlotid C of A Document Legacy Id
ReceiptLotId C of A Document Receipt Lot NodeID
CA_FileName C of A Document Title Text
CA_AcquisitionDate C of A Document Acquired Date Value
CA_Content_Type C of A Document File ContentType
CA_Document C of A Document File Blob
ContainerGroupId Container Group Legacy Id
ContainerGroupCode Container Group Name Text
Containerid Container Legacy Id
BarcodeId Container Barcode Barcode
PackDetailId Container Size NodeID
ParentId Container Source Container NodeID
ContainerGroupId Container Container Group NodeID
OwnerId Container Owner NodeID
ContainerStatus Container Status Value
ReceiptLotId Container Receipt Lot NodeID
PackageId Container Material NodeID
NetQuantity Container Quantity Value
UnitOfMeasureId Container Quantity NodeID
ExpirationDate Container Expiration Date Value
Version 1 Page 14 of 24
LocationId Container Location NodeID
StorPress Container Storage Pressure Value
StorTemp Container Storage Temperature Value
UseType Container Use Type Value
ReceivedDate Container Date Created Value
OpenedDate Container Opened Date Value
Concentration Container Concentration Text
HomeLocation Container Home Location NodeID
Notes Container Notes Comments
ProjectId Container Project Text
SpecificActivity Container Specific Activity Text
TareQuantity Container Tare Quantity Value
UnitOfMeasureId Container Tare Quantity NodeID
inventorybasicid Material Inventory Level Legacy Id
inventorybasicid Material Inventory Level Legacy Id
Inventorylevel Material Inventory Level Level Value
unitofmeasureid Material Inventory Level Level NodeID
Locationid Material Inventory Level Location NodeID
Packageid Material Inventory Level Material NodeID
PHYSICAL_STATE Finished Product Physical State Value
REACTIVECODE Finished Product NFPA Reactivity
Version 1 Page 20 of 24
SPECIFIC_GRAVITY Finished Product Specific Gravity Value
STORAGE_CONDITIONS Finished Product Storage and Handling Text
SUPPLIERID Finished Product Supplier NodeID
TARGET_ORGANS Finished Product Target Organs Name
MATERIALNAME Finished Product Tradename Text
PH Finished Product pH Text
Legacyid Certificate Definition SPR
Legacy Id
Material Certificate Definition SPR
Material NodeID
Obsolete Certificate Definition SPR
Obsolete Value
Name Certificate Definition SPR
Name Text
Version Certificate Definition SPR
Version Value
Approvalstatus Certificate Definition SPR
Approval Status Value
Approvalstatus Certificate Definition SPR
Approval Status Text
approved_date Certificate Definition SPR
Approved Date Value
Legacyid Certificate Definition EP Legacy Id
Legacyid Certificate Definition EP Legacy Id
Obsolete Certificate Definition EP Obsolete Text
Approvalstatus Certificate Definition EP Approval Status Value
Approvalstatus Certificate Definition EP Approval Status Text
Approvaldate Certificate Definition EP Approved Date Value
Name Certificate Definition EP Name Text
Version Certificate Definition EP Version Value
Ep Certificate Definition EP EP NodeID
Legacyid Certificate Legacy Id
Receiptlot Certificate Receipt Lot NodeID
Certdef Certificate Cert Def NodeID
assigned_date Certificate Assigned Date Value
approved_until Certificate Approved Until Value
Status Certificate Status Text
Status Certificate Status Value
Certificateno Certificate Certificate No Text
Legacyid Enterprise Part Legacy Id
Epno Enterprise Part EP No Text
Description Enterprise Part Description Text
Version Enterprise Part Version Text
legacy_tradename Receipt Lot Legacy TradeName Text
LOTCONTROLLED Container Lot Controlled Checked
legacy_mfr_site_id Manufacturing Site Legacy Id
MATERIALID Manufacturing Site Material NodeID
MANUFACTURERID Manufacturing Site Manufacturer NodeID
Ep Manufacturing Equivalent Part
Enterprise Part NodeID
manufacturingsite Manufacturing Equivalent Part
Manufacturing Site NodeID
Version 1 Page 21 of 24
Legacyid Manufacturing Equivalent Part
Legacy Id
Vendorid Vendor Manufacturing Legacy Id
Accountno Vendor Manufacturing Account No Text
City Vendor Manufacturing City Text
Contactname Vendor Manufacturing Contact Name Text
Fax Vendor Manufacturing Fax Text
Phone Vendor Manufacturing Phone Text
state1 Vendor Manufacturing State Text
street1 Vendor Manufacturing Street1 Text
street2 Vendor Manufacturing Street2 Text
Vendorname Vendor Manufacturing Vendor Name Text
Zip Vendor Manufacturing Zip Text
state1 Vendor State Text
allows_certdefs Chemical Material Allows Cert Defs Value
allows_certdefs Chemical Material Allows Cert Defs Text
allows_certdefs Supply Material Allows Cert Defs Text
allows_certdefs Supply Material Allows Cert Defs Value
material_finish Assembled Component Finish Text
allows_certdefs Biological Material Allows Cert Defs Value
SMILES Finished Product SMILES Text
Signal GHS Signal Word NodeID
Color Assembled Component Material Color Text
allows_certdefs Biological Material Allows Cert Defs Text
Version 1 Page 22 of 24
Appendix C: Data Extract Output and Usage Recommendations
Data Type Provided Description Recommended Use
Inventory Groups
Inventory group ID
Inventory Group Name
Site Name for Group
Merge Target (Optional)
A listing of all inventory groups and the sites they belong to.
This list is provided to review the inventory groups currently in use to eliminate unwanted groups. If an inventory group is no longer required, add a target inventory group ID value from column A into the merge target (column D). For example, to merge inventory group ID 5 into 10 (Eliminating group 5), add the value of 10 to column D for inventory group ID 5.
Locations Location ID (ID is prefixed with LS for printed/scanable location barcodes)
Site Name of location
Location level 1 name
location level 2 name
Location level 3 name
Location level 4 name
Location level 5 name
Inventory Group Name
A listing of all non-deleted locations and the sites/inventory groups they belong to.
The listing is provided as a chance to view the location structure to review how locations are defined at all sites. No action items are required in the Excel file, although this gives a chance for Global administrators of CISPro to review the various location trees and make changes as desired prior to the migration to BIOVIA CISPro.
Material Classes Material Sublass ID
Material Class/Type Name
Class Name
A listing of all non-deleted Class dropdown values for materials that reside on the Identity tab for materials.
This value does not match to a standard field in the new BIOVIA CISPro platform. If there is information/classes assigned that have not been captured via other means, such as properties, a new field can be added to preserve this data for all chemicals. This field is greatly impacted by material merges prior to migration in that only the target/main chemical value will be preserved. Typically this data field is not used by customers and can be discarded/omitted in the migration to BIOVIA CISPro.
Properties Property ID
Property name
Property Type
Object Type Target
Display Tab (Material properties only)
Required property value
A listing of all properties created for materials, containers, users, and lots. This listing provides a chance to review all created properties, most properties generally require additional fields to be added to the BIOVIA CISPro platform as properties are user defined in nature.
Customers can select which properties (if any) to preserve moving forward for inclusion in the data migration project, giving an opportunity to review and eliminate any unused, test, or abandoned field values. All preserved property fields will be visible to all users on all chemicals in the BIOVIA CISPro system.
Version 1 Page 23 of 24
Regulatory Lists Regulatory List ID
Display Name
Regulatory List Code
List Mode (CISPro or Ariel driven)
Sites using regulatory list
A listing of all non-deleted regulatory lists and the sites that subscribe to the list.
All lists and CAS values are preserved automatically moving to the BIOVIA CISPro platform. The listing provides an opportunity to review the currently configured regulatory lists should any lists no longer be needed and can be removed prior to migration to BIOVIA CISPro.
Roles Role ID
Role Name
Count of user accounts leveraging roles
A listing of all non-deleted roles in CISPro. Role permissions are not listed as they are not compatible with the new BIOVIA CISPro system and therefore are not migrated.
This is an important review step as inventory group access in BIOVIA CISPro is based on role and workunit combination instead of individually assigned per user account. It is more efficient for administrators to have users with the same role and different work units in BIOVIA CISPro to segregate inventory group access instead of duplicated roles between sites.
Units of Measure Unit of measure ID
unit of measure name
unit type
conversion factor (base, exp, target unit)
merge into
A listing of all units of measure shared by all sites for package creation.
“Each” units of measure type units are no longer available on chemical materials in BIOVIA CISPro and should be eliminated. To remove a unit of measure as a part of the merge process, add a value from column A into the merge into field (column G) for a unit of measure that should be removed. For example, to merge unit of measure ID 3 into 14 (Eliminating unit of measure id 3), add the value of 14 to column G for unit of measure ID 3.
Vendors Vendor ID
Vendor name
Division
Target vendor ID
Site Name
Provides a listing of all active Vendor records. Vendors may be duplicated if more than one site has a package that uses the vendor ID, or may have a null sitename if the vendor is not used on active packages.
This is a key set of records to evaluate as this will directly impact the quality and number of chemicals that are created in the new BIOVIA CISPro platform. Chemicals in BIOVIA CISPro are unique based on a compound set of the material name, supplier (vendor), and part number. Reducing the number of vendors used will reduce the number of “duplicate” chemicals in the new BIOVIA CISPro environment after migration. To remove a vendor as a part of the merge process, add a value from column A into the target vendor ID field (column D) for a vendor that should be removed. For example, to merge vendor ID 12 into 46 (Eliminating vendor id 12), add the value of 46 to column D for unit of measure ID 12.
Version 1 Page 24 of 24
Appendix D: Automatic Material Merge Behavior Flowchart
