Exporting and importing engineering data

Posted by

a083c-4fc13-image-asset

Hi all,
What is the best way to export data from an engineering firm’s document management systems and import that data into the client’s document management system?

——————————
Todd Morden
Sr. Draftperson
Husky Energy
—————————–


Todd,

I will kick things off with the same statement you get when you ask an SAP person any sort of “how do I…” question: it depends��.

What are the systems involved?

 

Aria

Aria Business Card-0۸
Aria Business Card-۱۰


a083c-4fc13-image-asset

As Lorne writes – that depends…
Generally I would use the step guide like this

  1. Make a list of all the fields/information in the exporting solution that you want included – technical field as well as user available informations.
  2. Check whether the supplier out-of-the-box support an exporting solution – and whether this fullfills your requirement list made in step 1.
    Next whether some others on the marked have some exporting solutions.
    And if not – is API’s available so someone could develop an exporting setup.
  3. Make a mapping list where exported content should be targeted field by field in the new solution – where to import the information
  4. Agree on a format that the exported metadata and documents should be delievered in.
  5. Agree on a method to ensure that all documents have been exported – simpliest way is a simple document count but that is not sufficient in all cases
    Do the same for the importing – how and who to check that all data have been imported fine – and how many and which types of sample controls is going to be performed and whi is going to perform them when (involved business representatives to check content/metadata to be appropriate)
  6. If the export and import is not on the same location – agree on a secure delivery method from export location to import location.
  7. Set up an importing solution for the new solution – that takes the agreed format and mapping information list into consideration.
  8. Perform an export test + an import test – and check whether you got the information migrated satisfactory (preferable in a testing environment – so rehearsals can be done – again and again until everything is optimized)
  9. When all seems to be fine
    • perform a performance test on the export – how long does export takes per 1.000 or per 1.000.0000 documents
    • perform a performance test on import –  – how long does import takes per 1.000 or per 1.000.0000 documents
  10. Make a calendar plan
  11. Perform – and have frequent follow-up meetings to see if plan is followed incl. that all verification activities are performed and reported successfully done with no issues to report.

Have followed this step plan for lots of migration involving multi-million document migrations. And yes – all migrations should be expected to have some loss of information – the important thing is that you are aware of which informations could be/is lost – and the value they had: Like a userid logged in the old system migth not be of any value in the new system if you haven’t got a full list of all userid’s in the old system – that my experience probably would be too heavy to migrate as well.
And if specific systems are involved in export/import – then there migth exist a (almost) standard tool for this. But then be sure to check that what they supports on migration is compatible with your requirement list – or that the missing informations represent so little value that a standard migration is acceptable to perform.

——————————
Hans Kofoed
ECM Lead
Danske Bank
——————————

 

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.