Skip to main content link. Accesskey S

CAM2 Wiki

All users on the internet can see this document



Home > Data Migration Engine

Data Migration Engine
ShowTable of Contents

Description

The data migration will be as automated as is practicable. This will allow the process to be re-run at different stages fo the project
 

Data Migration Scheme

The old Database

 
The old database will be retained indefinetley for the piping and vessel gasket specs.
We would also recommend that the old database is retained on the server in its full form for at least 6 months
and that DVD copies are made available indefinetley
 

Data Migration Error Reporting

Each migrated document will have a Data Migration Error Field
Errors will also be reported through the Error Logging module
 

Data Migration Notes Field

 
Data Migration Notes Field
 

Link back to source


There will be a action menu option ( not button ) to open the source document in CAM1
 

Rough notes from telecon 9th March

 
Use a keyword document to define a migration step
Run the process against selected records
keyword document world look as follows
 
dryrun=yes
oldform=motors
newform=f_motors
template=notetofile++blah
filter=form=lhglsdfh  - not necessary a boolean filter although that could be useful
parentrule=Use_Equipment_Header
defaultstatus=kgtlehglj
targetdatabase=this  ( or a named database, using "this" means not having to keep changing it )
targetdatabase=d:/Focllhglthlj.nsf
skipmarkeditems=true   * field called donotmigrate_tx
computewithform=yes
displayunmappedfields=yes ( see later - will dump unmapped fields into a simple field  )

plant#plant_tx#ruleA
area#area_tx#rulea~rulec

migrationfield RT template = mignotes1_rtx#keywordhookforemailtemplate1
migrationfield RT template = mignotes2_rtx#keywordhookforemailtemplate2
migrationfield RT template = mignotes3_rtx#keywordhookforemailtemplate2

use $meta scheme to create links and populate data - SO NO HIERARCHICAL DATA SHOULD BE IMPORTED

migration history field
old and new need each others docunid - note need to overwrite this potentiially
consider doclink to old form would be useful - in migration notes field which is on a "lower priority tab"
consider an option to write unmigrated fields to new doc in a dedicated field

don't assume child and parent are in same database
 

History

The history filed will be updated for each import
 

Specific Forms

 
See the Field Mapping Spreadsheet
 
Mechanical Item Top Sheet Data Migration
Maintenance Policies
Potted Vessel History
Technical Notes
ALP Actions
Materials Notes
Failures ( Mechanical)
Pipe Specs
ALP Spend Plan

Fitness for Purpose
Motor Data Sheets
Protective System Schedule/Register 
 

General Notes on  Functional Areas

Meeting Notes - 2010-02-26 - PES Discussion with MV
 

Assumptions/Notes

 
1. When combining Item Top Sheets (where there is more than one berth) the highets criticality is to be migrated to CAM2.
 
2. Criticality migrated from CAM1 will be appended with [CAM1]
 
3. The Initiator needs to be displayed on all Note To Files under brief title - should be migrated from CAM1.

4. There are layout regions in the ruch text field on many Tech Notes - these can not be migrated into the standard Note To File as the rich text field is within a table.
 
5, All Failures will be migrated into the Complete status (currently have no staus in CAM1).

6.  A migration area has been included in the administratikon section of the application.
 
7. Protective Equipment Schedules. A matching routine has been written to match Schedules in CAM1 with the corresponding Register.
The matching logic is as follows.
For each Schedule in Cam1 :-
i. Check for any regsiters under the same Equipment ID?
ii. Match on Trip/Alarm, Node, Category, Match Type
iii. Match on Trip/Alarm, Category and Match Type
iv. Match on Trip/Alarm, Node, Category
v. Match on Trip/Alarm and Match Type
vi. Match on Trip/Alarm and Node
vii. Match on Trip/Alarm and Category
vii. Match on Trip/Alarm
At each stage if a one to one match is found the match is deemed successful.  If multiple schedules or registers are found with the corresponding matching criteria then a fail is recorded.
 
8. Mick Albrecht has provided a current list of areas/plants (see Reds).  Need to do some cleansing/mapping during migration.
Impact Modifier  --> plant under Methacs
Infrastructure --> Services

 

Migrations Queries
 
1.  IE Top Sheets?

 
 ==Queries==