Bruce Power

OLAV successfully completed the largest PassPort (now Asset Suite) data conversion of the year for Bruce Power. The entire project – including data mapping, data conversion programming, six pre-production full data loads, production data load, informal testing, and full closeout CD documentation – was completed by two full-time-equivalent employees in sixteen months, a full two months ahead of schedule. The size can be demonstrated by fifty million TIDBLOB records being converted and moved, and the final data conversion production load was completed in twenty hours. The conversion took an IBM platform running PassPort© Version 6 to a Unix platform running PassPort© Version 10. A significant amount of data required modification prior to uploading. Data from the following PassPort areas was converted:

• System administration
• Catalog, material request and bills of material data
• Work management data
• Financial data

The OLAV JumpStart process not only converted the PassPort data shown above, but achieved the following objectives as well:

• Removed and archived obsolete and non-associated data from the base system.[1]
• Rearranged primary and associated facility data to meet business process review requirements.
• Loaded converted data to the production system in 20 hours, thus minimizing client down-time.[2]

The project relied heavily on OLAV’s custom load programs and proprietary SQL code to cleanse and consolidate the data. These OLAV tools – used on many previous PassPort conversions — provided a significant technical advantage resulting in lower project costs, shortened conversion schedules, and higher quality. For example, this conversion project was completed in 5,500 staff hours with minimal post-completion issues noted. This compares to some data conversion times of 30,000 hours or more for projects of this size. OLAV also delivered complete data mapping specifications and a fully-auditable record of the data conversion (data & process) at the close of the project. Two copies of the CD were provided to the client and two copies were retained by OLAV. [1] Obsolete data included non-current catalog id’s, obsolete manufacturer and vendor data, and shared data such as associated documents in TIDBLOB. [2] Fixed data was pre-loaded as required. One example would be the TIDBLOB data. Only incrementals needed to be covered at the production load.