Get documents about "PTW_Data_Interchange_Plan
Document Sample
PTW Data Interchange Plan
Document title: Tarong Energy CAR Project
PTW Data Interchange Plan
Document code: QSDM0492.001.doc
Process authorisation
Nik Lalic Date
Tarong SI Team Leader
Aaron Hall Date
Mincom SI Team Leader
Principal authorisation
Linda Jackman Date
Mincom Project Director
Stephen Kovacs Date
Tarong Project Manager
Copy:
Commercial in confidence
Tarong Energy CAR Project Data Interchange Plan
Confidentiality and disclosure of information
Tarong Energy retains ownership of this document. However, the
methodology or format used to derive this document is confidential to
Mincom Limited. This document must be treated as confidential, as
disclosure of the document will disclose the methodology.
This document can be used and copied within Tarong Energy for use
in relation to this project. However, this document, including copies of
it, must not be disclosed to any person who is not a director, officer,
employee, consultant or agent of Tarong Energy without the prior
written approval of Mincom Limited and such person or agent has
signed a non-disclosure agreement satisfactory to Mincom Limited.
Document control
This document is deemed to be controlled only as long as the project
to which it relates is active. Controlled copies will be automatically
updated.
Once the project is completed or terminated, this document will revert
to an uncontrolled document status. No further advice will be
provided, and each recipient may either destroy the document or mark
it as obsolete and retain it for future personal reference.
QSDS0063.012 4 December 2011 Mincom Limited Page 2 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Amendment history
Amendment number Updated by (signature) Date updated
QSDS0063.012 4 December 2011 Mincom Limited Page 3 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Distribution
Copies of this document will be distributed to each of the people
specified below.
Title Person Copy
Project Library 1.
Tarong Energy IT Manager 2.
Tarong Energy Maintenance Team Leader 3.
Tarong Energy HR Team Leader 4.
Tarong Energy PTW Team Leader 5.
Mincom Maintenance Team Leader 6.
Mincom HR Team Leader 7.
Mincom PTW Team Leader 8.
Tarong Energy IT Software Production 9.
Manager
Tarong Energy Project Manager 10.
Mincom Project Manager 11.
Mincom Implementation Manager 12.
Mincom Quality Manager 13.
Mincom IT Team Leader 14.
Tarong Energy Software Project Manager 15.
Tarong Energy Quality Manager 16.
Tarong Energy Implementation Manager 17.
Tarong Energy Planning Manager 18.
Tarong Energy MIS Manager 19.
QSDS0063.012 4 December 2011 Mincom Limited Page 4 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Revision history
Updates to this document will be in the form of a complete reissue.
Therefore, when a newer version is received, destroy the older version
completely or clearly mark the older version as superseded.
Date Version Comment
29 Sept 2000 001 Initial draft by Mincom Technical Consultant - Paul Duggan
10 Oct 2000 002 Review by Mincom Technical Consultant - Peter Hodgins
11 Oct 2000 003 Completed by Mincom Technical Managing Consultant - Paul Duggan
6 March 2001 004 Review by PTW Team Leader – Joanne Taylor
29 May 2001 005 Amend Tasks in DIP, Appendix B
QSDS0063.012 4 December 2011 Mincom Limited Page 5 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Table of contents
1. Introduction ............................................................................................................................... 7
1.1 Purpose .................................................................................................................................. 7
1.2 Scope ..................................................................................................................................... 7
1.3 References ............................................................................................................................. 8
1.4 Project evolution ................................................................................................................... 8
1.5 Definitions and acronyms ...................................................................................................... 8
2. Managerial process ................................................................................................................. 10
2.1 Roles and responsibilities .................................................................................................... 10
2.2 Resourcing ........................................................................................................................... 13
2.3 Risk management ................................................................................................................ 14
2.4 Monitoring and controlling ................................................................................................. 16
3. Technical process..................................................................................................................... 17
3.1 Conversion Iterations .......................................................................................................... 17
3.2 Conversion Process ............................................................................................................. 18
3.3 Data source analysis ............................................................................................................ 18
3.4 Historical data capture ......................................................................................................... 19
3.5 Data transfer ........................................................................................................................ 19
3.6 Data verification .................................................................................................................. 22
3.7 Error handling ..................................................................................................................... 23
3.8 Audit Controls ..................................................................................................................... 24
4. Environment control ............................................................................................................... 25
4.1 Backups ............................................................................................................................... 25
4.2 Security................................................................................................................................ 25
4.3 Storage allocation ................................................................................................................ 26
4.4 Rollback strategy ................................................................................................................. 26
5. Conversion Outcomes ............................................................................................................. 27
6. Appendix A .............................................................................................................................. 28
7. Appendix B............................................................................................................................... 29
8. Appendix C .............................................................................................................................. 32
QSDS0063.012 4 December 2011 Mincom Limited Page 6 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
1. Introduction
1.1 Purpose
The Tarong Energy CAR Business Project requires strategies for the
conversion and interchange of data. This is identified in the Tarong
Energy Data Interchange Plan.
The data conversion and interchange requirements of the Permit to
Work (PTW) system were not included in the initial Data Interchange
Plan and thus requires a separate Data Interchange Plan dedicated the
PTW.
This PTW Data Interchange Plan identifies existing data and identifies
actions required upon that data to interchange with or be converted to
Ellipse. Strategies and tactics provided will be used as reference to
any activities in relation to conversion/interchange during project
implementation.
1.2 Scope
The Data Interchange Plan will document:
The data conversion requirements (from legacy and manual
systems)
The loading to Ellipse of components identified by Tarong Energy
Dependencies for loading between various tables and files
Any other data requirements or concerns (eg data integrity
measures)
The detailed tasks associated with the development and execution
of the cutover schedule to support the implementation of Ellipse
within Tarong Energy.
A description of the PTW interface requirements are documented in
the Interface Plan.
This plan has identifies the following existing database applications in
use at Tarong Energy Corporation for the administration and
management of the PTW system that will require conversion to
Ellipse.
QSDS0063.012 4 December 2011 Mincom Limited Page 7 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
1.2.1 PTW
EnGarde system - Tarong
EnGarde system – Wivenhoe
Switching Sheets Access database – Tarong
Switching Sheets Access database – Wivenhoe
PTW Report Writer
1.3 References
a) \\Tmds00\Tarcopub\Information Systems\Projects\APO24IT –
Core Application Replacement\31 Implementation\31d Data
Conversion\Plan\DCP\Data Conversion Plan.doc
b) \\Tmds00\Tarcopub\Information Systems\Projects\APO24IT –
Core Application Replacement\31 Implementation\31d Data
Conversion\Plan\DCP\PTW_Data_Conversion_Plan.doc
1.4 Project evolution
This Plan will need to be revised after delivery of Iteration of the
Permit to Work system which is currently under development.
1.5 Definitions and acronyms
BRS Business Requirement Study
BSD Business Solution Design
Connector COM enabled tool developed by Mincom
CorVu EIS tool by Mincom
Ellipse Mincom Information Management System
Fixed length record One record per line with fields delimited by
position in the line
Fox Pro PC based database
FTP File Transfer Program
LAN Local Area Network
MINT Screen Emulation Program by Mincom
Oracle Database
PTW Permit to Work
Perl Programming language
RDBMS Relational Database Management System
QSDS0063.012 4 December 2011 Mincom Limited Page 8 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
RDL Report Definition Language
UAT User Acceptance Testing
UNIX Operating System
Visual Basic Programming language for PC
Xtrieve SSQL database file analysis tool
QSDS0063.012 4 December 2011 Mincom Limited Page 9 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
2. Managerial process
2.1 Roles and responsibilities
Key Project Roles Responsibilities Assigned To
Functional Team Manage domain project tasks during cutover.
Leaders
Identify necessary Ellipse batch, RDL and online programs,
associated subroutines, user exits, macros and advise IT
Support Team Leader to load into production.
TEC System Provide system administration support for TEC production
Administration system.
Tarong Energy CAR Responsible for preparing database definitions for all current
Project Team software identified in the scope. This definition includes tables,
columns, descriptions of columns, and type of columns.
Sample values should also be available along with an
indication of which columns are not used.
Responsible for providing any data deemed to be missing from
the existing tables and for deciding the necessity of any extra
information stored in the current system. Missing data should
be input into a format specified by Tarong Energy IT, and
could be recorded/entered by clerical staff, or staff from the
relevant team.
Data cleansing is the primary responsibility of TEC. The task
involved is to investigate/correct data errors found during trial
conversion(s) and production load and sign-off acceptance of
state of data.
Tarong Energy Application Team Leaders are responsible for
designing acceptance tests to ensure that the conversion was
performed correctly.
Develop, test and run programs to extract data from legacy
applications to produce intermediate files in a suitable format
necessary for Mincom Applications Consultants to perform the
migration of data to Ellipse.
Assist with preparation of data for conversion/migration.
Execute allocated tasks in the cutover schedule, provide and
validate the converted data, as agreed for the various trial and
production runs.
Ensure the TEC production systems are disabled to all but
authorised project and user staff during the cutover period
(method to be determined).
Assist with data validation following conversion &
implementation of production system.
Mincom CAR Project Develop the DIP.
Team
Pre-data conversion review.
Develop the detailed cutover schedule, with TEC, and manage
the associated technical tasks.
Provide appropriate load scripts and upload programs where
required.
QSDS0063.012 4 December 2011 Mincom Limited Page 10 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Responsible for setting up any necessary environments for
conversion/interfaces.
Perform data loading via scripts and/or upload programs.
Assist Mincom Technical/Tequinox to:
Provide appropriate environment and technical support for
UAT.
Assist in configuring the Ellipse production environment.
Install into production all necessary Elllipse batch, RDL
and online programs, associated subroutines, macros and
job control, together with client (server) based software.
Develop and run backup and recovery services during
development and early implementation.
Provide Help Desk support during Business Support
phase.
Mincom Customer Load Ellipse software.
SupportTechnical
Undertake volume testing.
/Tequinox(Brisbane)
Provide technical, operations and programming support during
UAT, trail conversion(s) and cutover.
Performance and capacity planning during development.
TEC LAN 24 hour technical and hardware support for LAN and
Administrator associated hardware and software, and necessary connections
to Unix system during conversion, UAT and cutover phases.
Provision of sufficient equipment (PCs, printers, etc),
appropriately configured, to undertake the conversion and
cutover activities.
Arrange building security and access for project staff during
the conversion and cutover periods (including out of hours).
Internal Audit Provision of Audit advice and conduct of activities as
appropriate.
QSDS0063.012 4 December 2011 Mincom Limited Page 11 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
2.1.1 Joint Responsibilities
The following points highlight those responsibilities that Mincom and
Tarong Energy Project members will share:-
Mincom Functional Team Leaders along with Tarong Energy
Functional Team Leaders are responsible for specifying the
required conversion for Tarong Energy IT to implement. This will
be detailed on standard specification templates.
Tarong Energy IT will primarily own the Tarong data and will be
responsible for the extraction process.
Mincom Functional Team Leaders are responsible, with assistance
of Tarong Energy IT, for the mapping of the current software into
Ellipse tables.
Tarong Energy Functional Team Leaders are responsible for
developing appropriate test plans/verification reports for the data
conversion.
The Mincom Project Manager is responsible for
scheduling/obtaining all necessary resources excluding Tarong
Energy SI team which is the responsibility of Tarong Energy
Project Manager.
Mincom staff can assist in areas above where deemed necessary.
QSDS0063.012 4 December 2011 Mincom Limited Page 12 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
2.2 Resourcing
Facilities required are as per normal Ellipse Business Project
personnel PC and access to the UNIX Server.
For testing purposes Tarong Energy IT is required to provide a testing
environment containing the third party systems.
Personnel required as per Project Schedule.
Some additional facilities will be required to support the activities of
the implementation project, as noted below:
Item Equipment
PCs/terminals The Project Team will require a minimum of 6 PCs running WinNT, Mincom
Connector and Ellipse Client Software to allow the loading of data via scripts.
Multiple databases Multiple databases required for production, development, testing and training.
Printers Connected to the site of each implementation group during loading
LAN facilities Technology Manager to ensure (in association with TEC support staff) that
backup utilities are not running while scripts and other loads occur as this may
degrade performance
Access to system admin in The team loading the production system will need full access to the production
production system system to complete setup and validation activities. Key users will need access
for validation and error correction.
Out of hours building Tarong Energy to arrange access for all implementation team members for
access during the trial each load.
conversion and production
loads
24 Hour technical support TEC Technology Manager to arrange for appropriate technical support staff to
during the trial conversion be on call during the nominated loading periods in the event of system failure.
and production loads
QSDS0063.012 4 December 2011 Mincom Limited Page 13 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
2.3 Risk management
Refer to the Risk Management Plan and the Project Manual for all
details of the risk management activities.
Risks in relation to PTW data interchange include but are not limited
to:-
Risk Prob Mitigation
1. Delivery of the PTW system, as per the Low The Project Manager and Director will liase with
delivery schedule. Austech, a division of Mincom Ltd (the
developers) on an on-going basis to ensure the
Delivery timetable is adhered to.
2. Access to the PTW system, while under Low The Project Manager will request of Austech, a
development, for the development and division of Mincom Ltd (the developers) that the
testing of upload programs. Mincom TEC Programmers access the PTW
system, while still under development, to prepare
and test upload programs.
3. Availability and quality of data: Med Functional teams to request that all data is
available in a timely manner. Project Manager to
All data may not be identified in a ensure that empowered users are available to
timely manner and may be quickly follow up and to assist in the case of
incomplete/inaccurate. errors or omissions. All data to be validated prior
to any conversion loads.
There is the potential for corruption
in the existing data source (eg
cleansing stage) that will not be
detected by the conversion process
and will be replicated in the Ellipse
system.
A risk exists of mis-designing or
mis-implementing conversion rules
and consequently changing the
meaning of data through the data
conversion process.
4. Program errors, readiness and Low With quality defined conversion documents, this
availability risk can be minimised. All programs should be
fully tested and verified prior to any loads.
Project Manager to ensure that programmers are
fully supported to deliver conversion programs on
time.
5. Establishment of security profiles – Low System administrator to ensure appropriate
lack of access to converted data by (nominated) users have access to assist in data
users for testing/validation could cause validation after conversion occurs.
delays in validating data loads.
6. Inadequate system performance from Med Planning and availability of new system on line to
the enterprise system to meet the support conversion should mitigate risks in this
requirements of users area.
7. Inability to access or availability (eg Med Tequinox to provide/arrange 24 hour support
down-time) to the enterprise system during the period of the conversion and
will severely impact the agreed production loads.
schedule.
QSDS0063.012 4 December 2011 Mincom Limited Page 14 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Risk Prob Mitigation
8. Insufficient or unavailable resources to High All relevant groups to ensure sufficient resources
complete conversion tasks within the are available during the period of trial and
required timeframe. production conversions. Project Manager to
coordinate and plan validation tasks.
9. Not adhering to the agreed and High Project Manager will constantly monitor
approved implementation schedule completion of each stage of the implementation
by the scheduled date and time, and take
immediate action where slippage occurs
10. Business Process Redesign accruing Med Benefit/cost of charges to be formally justified,
concurrently with conversion planning after initial signoffs of data-mapping.
and execution can result in changes to
extraction or load programs. Such
changes may need synchronisation.
11. Legacy systems include multi version Med Tarong Data Conversion team to provide version
unsupported Oracle instances control mechanisms for extract programs from
Oracle instances.
12. Engarde legacy system program High Tarong Data Conversion application
complexity and customisation may programmers have Engarde knowledge as well as
impact on the time required to build experience in the Tarong Energy customised
extract programs version. Tarong Functional team members can
provide experience in the required stream to assist
in data identification, mapping and cleansing.
13. Competing project work with creation High Project Manager will monitor progress and
of data conversion specifications may prioritisation of activities. Action will be taken as
affect timely delivery to data required.
conversion teams.
QSDS0063.012 4 December 2011 Mincom Limited Page 15 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
2.4 Monitoring and controlling
Each task of the PTW data interchange work package has defined
goals/objectives, so completion can be determined. Some tasks have a
quantifiable scope (e.g. defining the current data) so a percentage
complete is easy to obtain. Other tasks such as developing programs
are harder to quantify, so percentage complete can only be
approximated by the people involved.
The progress of the entire project is monitored by the completion of
the identified tasks. Each task has a defined objective, and on
completion, proof of completion (presentation/report/signing off
document) should be given to the Tarong Energy Information Services
Manager.
When Tarong Energy/Mincom staff are required, who are not from
Tarong Energy IT CAR Project, the resource is organised by the
Project Manager.
QSDS0063.012 4 December 2011 Mincom Limited Page 16 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
3. Technical process
3.1 Conversion Iterations
It has been proposed that the number of conversion iterations will be
two (2). The iterations are:
Iteration Task Start
Data Conversion No.1 Test 21/05/01
Timed
Acceptance
Data Conversion No.2 Production 18/06/01
NOTE
Data conversion Number 1 will be specifically dedicated to the
conversion of PTW information, on an integrated Ellipse system.
However, Data Conversion Number 2 will be incorporated into the
larger data conversion for the entire Ellipse system for Go Live.
The following data will be converted:-
Data Method
PTW Standard Text Types Electronic
PTW Attribute Text Electronic
Permit User Group Electronic
Soft Status Progression Electronic
Generic OIC’s Electronic
Standard Steps Electronic
Isolation Guides Electronic
Application for Permit to Work Electronic
Permit to Work Manual
Isolation Sheets Manual
System and District Control File, Table Files and impacts on Work
Orders and Employee Core Details is data also impacting on the PTW
data conversion.
For more information, please refer to Appendix B.
QSDS0063.012 4 December 2011 Mincom Limited Page 17 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
3.2 Conversion Process
Summary of the conversion process:
1. Completion of PTW data conversion plan to determine scope of
conversion requirements.
1. Data-mapping exercise is made to determine source and
destination of data elements. This is a joint exercise between
Mincom and Tarong Energy. Both functional and technical teams
are involved.
2. Tarong Energy IT will generate a file in a standard format
determined by Mincom. The procedures, process and tools to
extract the data from legacy systems should be managed (ie
determined, developed and extracted) by Tarong Energy.
However, Mincom staff can offer advice or support where
required and from past experience this is a recommended strategy.
When the data is not already computerised, it should be entered in
a format suitable for the transfer to Ellipse, usually in the form of a
comma separated file (CSV). A CSV file (e.g. by using Excel)
should be generated with the required data. Data may also be
entered into Ellipse manually.
3. The extract files must be cleansed by Tarong Energy IT. Pre-load
record counts need to be confirmed at this stage, to aid in the
reconciliation in the later stages of the conversion.
4. Cleansed extract file delivered to Mincom IT to upload into
Ellipse.
5. Extract files uploaded into Ellipse using Mincom scripts. Pre-
written/modified or new scripts will be used to load the data into
Ellipse. Where scripts must be developed or modified, coding will
commence once step 1 has been confirmed and completed.
6. Data load report logs are analysed to verify the status of the load.
This includes logs of errors/exceptions, audit trails and record
counts.
7. Record counts are compared. If there are errors with the source, a
decision is made whether to cleanse the data and reload or discard.
8. Ellipse loaded data is verified by the functional teams.
9. Exceptions are corrected either manually or by reloading data.
3.3 Data source analysis
Conversion Data Sources comprise of the following categories:
1. EnGarde system – Tarong
2. EnGarde system – Wivenhoe
QSDS0063.012 4 December 2011 Mincom Limited Page 18 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
3. Switching Sheets Access database – Tarong
4. Switching Sheets Access database – Wivenhoe
Tarong Energy IT staff have access to the data dictionaries of the
above applications. These data dictionaries include information on:-
Type of data in each table
Record structure.
3.4 Historical data capture
Tarong Energy has indicated that the majority of historical data will
be archived. Consequently, this means that this historical data will not
need to be loaded into Ellipse.
It is assumed that relational data will be held in an alternative source
to Ellipse.
Based on discussions with TEC, the following is an indicative
breakdown, by functional stream, of how historical data will be
managed.
3.4.1 PTW
Historical data will not be loaded into Ellipse. Current records only
will be migrated.
3.5 Data transfer
Data Transfer Process
Typically, data will be extracted from Tarong’s legacy systems,
converted and migrated through the use of one or more of the
following methods:
Connector Scripts
Standard Cobol batch load programs
Table Files
Direct database load
Manual entry
Refer diagram Appendix B.
QSDS0063.012 4 December 2011 Mincom Limited Page 19 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Connector Scripts
The preferred option, and the option that will be primarily employed
on the Tarong Energy PTW data conversion, will be the use of
Connector scripts.
Connector scripts are a method for simulating data entry via Ellipse
screens and objects, thus performing every validation and confirming
data relationships, to ensure integrity in the resulting data.
A script uses a file in a format determined in the data-mapping phase
and is usually in a CSV format. A large percentage of applications can
produce files in this format (eg Access, VB, etc). The format also has
the added bonus of easily being maintained in products such as Excel.
After the extract file has been produced, the data is then loaded into
Ellipse with a Mincom script. The scripts are written in a proven
Mincom developed tool; either Connector or Mint.
The scripting process will load data into Ellipse in a concise neat
format that is quick and highly efficient. Importantly, this ensures that
data relationship rules are adhered to and the integrity of the data is
maintained.
An important determinate to the success of using scripts is managing
the quality of the data that is extracted from the legacy system. A
thorough analysis and a well-developed data-mapping plan will aid to
the success of this process.
Cobol Batch Programs
Cobol programs will primarily be used where Connector scripts are
not suitable. As the script process emulates data entry through a PC
and transfers data across the network, volumes of data above
approximately 5000 should be loaded by a Cobol program.
The standard Ellipse install includes a Cobol load program for each
table in the Ellipse. The load programs use COBOL inserts into
appropriate relational tables, one load program for each base-table and
its related sub-tables. They simply take a record, dissect the
information along sub-table lines and inserts rows into the appropriate
tables.
The only validation that the standard load program performs is a check
for a duplicate primary key which gets reported and the duplicate
discarded. Most relational databases will also inherently check
numeric fields as containing correctly formatted numeric data.
QSDS0063.012 4 December 2011 Mincom Limited Page 20 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
As part of the migration exercise additional validation will be coded
into a copy of the standard load program. The amount of validation is
a trade-off between time available to code and run the extra validation
and the amount of system testing that will be performed in the testing
phases after migration has been completed.
Similarly, each standard load program contains code to perform
standard auditing (e.g. number of records read, number of records
written) however, it is anticipated additional auditing will be required.
Table Files
Ellipse employs a significant amount of table file data (different types
of information that do not deserve their own file because of their
simple nature). The equivalent of these codes is often found in other
systems albeit not with exactly the same length of code as Ellipse. In
fact there may be quite a few fields that on first inspection would tend
not to fit into its corresponding Ellipse field.
To resolve this problem, a translation table strategy is employed where
the old code is mapped to a new code. An unused field (in the same
download file) of appropriate size is used as a transport field. The data
in this field is then translated and moved to the to the target field via
the translation table and then the transport field is cleared. The
translation tables, stored in MSF010, are named uniquely to identify
them as being conversion data only and are deleted subsequent to the
conversion process. The file will be prefixed by a dot (.), followed by
the first letter of the functional stream. For example, the PTW
conversion tables will be prefixed by ‘.P’.
Direct Database Loads
It is important to note that there are instances where an extract file can
be loaded into Ellipse by using a direct database load. A typical
example is the loading of validation codes table data through SQLPlus.
Discussions with Tarong Energy have indicated that a team shall be
put together to cleanse data before any conversions begin. The
purpose is to improve the quality of the Production data.
It is planned that conversions will be made by functional stream, in a
sequence determined during the initial stages of the project.
The following data sources have been identified for conversion:
QSDS0063.012 4 December 2011 Mincom Limited Page 21 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
3.5.1 Transfer from EnGarde
It is planned that the Tarong and Wivenhoe EnGarde databases will
have data extracted from them separately requiring two data uploads
for the relevant PTW files.
The following Ellipse HR/Payroll modules have been identified for
conversion:
PTW
3.5.2 Transfer from Switching Sheets Access
Databases
It is intended that the data held in the Switching Sheets Access
databases (Tarong and Wivenhoe) associated with Standard Steps will
be transferred to EnGarde prior to data conversion as part of the PTW
data cleansing process. Switching Guides will be built in EnGarde
from the migrated Standard Steps. These Guides will be transferred
from EnGarde as per section3.5.1.
3.6 Data verification
Verification of the conversion will be done by counting the records
before and after the conversion, viewing reports from each system and
comparing the results and by using the online system in Ellipse to
verify that selected data has been converted correctly.
Log files of the conversion programs will contain any indication of
failure. Various log reports can be produced to highlight exceptions,
record counts and auditing information. With these log reports, errors
can be cleansed and reloaded through the same quick and easy
process.
Using products such as Excel in conjunction with Connector
incorporates the additional feature of highlighting exceptions as they
occur in real-time rather that waiting for the script to complete the
entire load. This means that load exceptions can be quickly
maintained and reloaded from within Excel.
The current reports from Tarong Energy applications need to be
compared with the standard reports available from Ellipse and where
there is a lack of reporting functionality, Client Specific Reports, SQL
or CorVu queries will need to be defined and written.
The method of acceptance for individual conversions will be detailed
in the Data Conversion Specification for each conversion area.
QSDS0063.012 4 December 2011 Mincom Limited Page 22 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
3.7 Error handling
3.7.1 For data conversion
Connector scripts automatically use Ellipse business logic.
Therefore, any invalid data will be detected as part of that logic
process. Rejected records are reported and will need to be corrected
and either reloaded or entered manually.
Cobol batch upload programs are built to use Ellipse business logic
and validate the data prior to the upload. As with scripting, bad
records are reported and will need to be corrected and either reloaded
or entered manually.
Connector and Cobol upload programs will produce a log file
containing:-
Record Count on each record line
Input record
Whether the record was successfully loaded
Ellipse error message if not successfully loaded.
Total of Records Read
Total of Records Loaded
Total of Records Rejected
Connector and Cobol upload programs will produce an error file
containing:
Record count on each record line
Input record
Ellipse error message
Total of Records Read
Total of Records Loaded
Total of Records Rejected
QSDS0063.012 4 December 2011 Mincom Limited Page 23 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
3.8 Audit Controls
Throughout the PTW data interchange process, checks and balances
will be undertaken to form the basis of an audit trail.
Such a mechanism is designed to satisfy the following core objectives:
1. Ensuring that records supplied for data interchange are correctly
accounted for following processing tasks undertaken on that data;
2. Reporting of exceptions whereby data is excluded from further
processing as a result of redundancy or errors;
3. Historical record of data migration iterations and outcomes of each
iteration (at a summary level);
4. Accumulation of time based estimates as to overall data
conversion duration to be used as inputs into the Live Cutover
planning.
Tarong Energy should advise, prior to project commencement, of any
specific auditing requirements that are necessary to satisfy their own
corporate objectives. Where Tarong Energy requires an independent
audit of the Data Interchange activity, necessary notification and
involvement from Mincom personnel is desirable.
QSDS0063.012 4 December 2011 Mincom Limited Page 24 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
4. Environment control
4.1 Backups
Normal Backups on the UNIX machine will be performed nightly.
The Tarong Energy backup strategy is to have a 14-tape cycle, so the
system status at any day in the last two weeks is possible. Every
month, one of these 14 tapes is archived (different tape each month, so
that after 14 months, all tapes have been changed) so Tarong Energy
is able to obtain the status any month for the life of the project. The
backup strategy is defined fully in the Project Manual.
The initial conversions will be done in a separate Ellipse instance, so
in the event of a failure, that instance can be restored from the
previous night, without affecting training/development etc.
For interface, a copy of the data being transferred should be kept on
the UNIX system, so that it can be backed up at night, and hence re-
used at a later stage if necessary.
4.2 Security
Security of the data, particularly during interchange will be addressed.
Security is a major issue, and a Tarong Energy Security policy should
be developed to cover all forms of data/network security and
acceptable use of any data or information.
Specifically data interchange initiatives should consider the following
security aspects:
Ellipse Security being setup properly
CorVu Security being setup properly
UNIX Security
Database Administration Security
Security of Temporary files on UNIX
Network Security
Security of Data Backup devices (e.g. tape or diskette)
Physical Security
Security of temporary file on PC
Security of Application on PC
Security of Verification Process
Authentication of key tasks.
QSDS0063.012 4 December 2011 Mincom Limited Page 25 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
4.3 Storage allocation
Storage space for temporary files needs to be made available on both
PC network and UNIX. These temporary files are in both initial
conversion and for data interfaces. Tarong Energy IT staff should
include monitoring of this space as part of the regular administration.
This will ensure that there will always be sufficient so that it is not
filled.
Minimum storage space at any time during the data interchange
process is THREE (3) times the total storage of all source data to be
converted and/or migrated.
Specific estimates for physical storage are included in the
Configuration Management Plan.
4.4 Rollback strategy
The roll back strategy for PTW will be the same as the roll back
strategy for the larger CAR Project.
QSDS0063.012 4 December 2011 Mincom Limited Page 26 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
5. Conversion Outcomes
Based on the completion of each task identified in the Work
Breakdown Schedule, the following outcomes will be delivered as part
of the data conversion process.
Task Description Outcomes
Data Source Analysis Each package contains a data dictionary for all tables including column
names, descriptions of each column, sizes and type of each column,
number of records in each table and approximate growth. Also a
description of the table.
Environment Setup Ellipse environment ready to load data.
UNIX environment setup ready for transfer.
Necessary PC Infrastructure.
Data Mapping Exercise Mapping of Initial Database to Ellipse Database.
Specification of Conversion Requirements.
Specification of Interface Requirements.
Identification of Missing Mandatory Ellipse Values.
Identification of where bad data affects Ellipse implementation, and
action plan for that data.
Specification of necessary data purification.
Identification of Extra data in existing databases and action plan for that
data.
Identification of Verification Procedures (Reports) for software.
Obtain Missing Data All mandatory data for conversion is identified.
Data Entry All mandatory data for conversion is already input into the required
format.
Write Conversion Programs All programs related to:
dumping data from original database
converting data into correct loading form
loading data into Ellipse
are completed.
Run Conversion Programs All conversion programs are run, and data is inside Ellipse.
Verify Conversion Programs All identified verification are run and data matches.
Identify Source Inconsistencies Check All necessary Checks for data consistency are documented including
what to check and possibly how to check.
Perform Consistency Checks All Checks are done, and the inconsistencies identified.
Data Purification All required Source databases are fixed correctly.
QSDS0063.012 4 December 2011 Mincom Limited Page 27 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
6. Appendix A
Scripts
Audit Ellipse
Reports
Audit
Conversion MSL Load Reports
CSV Files Tables
MSN
Files
Extract Program
Legacy Systems
QSDS0063.012 4 December 2011 Mincom Limited Page 28 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
7. Appendix B
Load Task Parent Task Ellipse Module Ellipse Stream Or Count Comple Program Data Comments
Order ID /Add xity (l – Source
Low, M
–
Mediu
m, H –
High)
1 PTW System and MSF001 1 L Connector Data Awaiting details of System
1 District Control Extract and District Control file
File (PTW) System requirements.
Administration
Option to Load details Via
Connector is being
investigated
2^ PTW MSO010 System 1 L Connector Data Table Files Include:-
2 Administration Extract
Table Files Table File (Mincom
and Client
maintained)
3 PTW PTW2 Table Files MSO096 System 1 L Manual Manual
3 Standard Text Administration Entry
Types Attribute Comment Text to
be loaded using MSO64E
4 PTW PTW2 Table Files MSF64L System 1 M Manual Manual Site Isolation Attribute
4 Attribute Administration Entry documents to be loaded
Documents using MSO64E
5 PTW O&M2 3620 Work Operations and 1 L Work Order Flag
5 Orders Maintenance
COBOL Conver Specific requirements are
sion still being developed.
Script
MSC620 to initialise PTW
flags on MSF620 and
MSF623 to ‘N’.
6 PTW HR1 Employee 3760 Personnel Human 1 L Connector Data Employee Site Code
6 Core Details Administration Resources / Extract details
Payroll
(Modify) This is a new field to be
added to the MSO810.
UAT
6.1 PTW HR1 Employee 3760 Personnel Human 1 L Connector Data
6.1 Core Details Administration Resources / Extract
Payroll
(Create)
Conversion 4
7 PTW Table Files MSF64N Permit to Work 1 L Connector Data
7 Extract
Permit User
Groups
8 PTW Table Files MSF64K Permit to Work 1 L Connector Data
8 Extract
Soft Status
Progression
9* PTW Table Files MSF64M Permit to Work 1 L Connector Data
9 Extract
Generic OICs
10* PTW Table Files Standard Steps Permit to Work 2 M Connector Data Approximately 20000
QSDS0063.012 4 December 2011 Mincom Limited Page 29 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Load Task Parent Task Ellipse Module Ellipse Stream Or Count Comple Program Data Comments
Order ID /Add xity (l – Source
Low, M
–
Mediu
m, H –
High)
10 O&M1 Extract records
Equipment
Register Standard Steps include:-
MSF64A Standard
Steps
MSF64H Standard
Steps Equipment
(approx 68000
equipmnt links to
PTWs in EnGarde)
Audit Trail will be created
via the loading for this
information.
11 PTW Table Files MSF64B 2 H COBOL Data Approximately 1000
11 Extract records
PTW8 Standard Isolation Guides
Steps Isolation Guides include:-
MSF64B Isolation
Guide
MSF64J Isolation
Guide Equipment
MSF64C Isolation
Guide Blocks
MSF64D Isolation
Guide Steps
Attributes
Category Comments
Audit Trail will be created
via the loading for this
information.
11.1 PTW PTW 11 MSF64B L COBOL Data To be loaded by an
11.1 Extract existing COBOL program
Isolation Guide (TGB096.cbl)
Attribute Text
11.2 PTW PTW11 MSF64B L Manual Manual Isolation Guide Attribute
Entry documents to be linked.
11.2 PTW4 Isolation Guide
Attribute
Documents
12 PTW Table Files MSF645 Permit to Work 2 M COBOL Data MSF645 Application for
12 Extract Permit to Work
O&M 2 Work Application for
Orders Permit to Work Audit Trail will be created
via the loading for this
PTW4 Employee information.
Site Code Details
PTW6 Soft Status
Progression
PTW9 Generic
OIC
13 PTW Table Files Permit to Work Permit to Work 2 M Manual Manual Permit to Work inlcudes:-
13 entry
O&M 2 Work MSF646 Permit to
Orders Work
PTW6 Soft Status MSF648 Permit to
Progression
QSDS0063.012 4 December 2011 Mincom Limited Page 30 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
Load Task Parent Task Ellipse Module Ellipse Stream Or Count Comple Program Data Comments
Order ID /Add xity (l – Source
Low, M
–
Mediu
m, H –
High)
PTW9 Generic Works Links
OIC
MSF648 Permit to
PTW10 APTW Work OIC
14 PTW Table Files Isolation Sheets Permit to Work 2 M Manual Manual Isolation Sheets include:-
14 entry
PTW8 Soft Status MSF64E Isolation
Progression Sheets
MSF64F Isoaltion
Sheet Sheet Blocks
MSF64G Isolation
Sheet Steps
^ and * The potential for amalgamating this data for a consolidated upload is being discussed
with David Morgan, Project Team Leader, Austech, a division of Mincom Ltd. If this data is
unable to be amalgamated, separate data loads will need to be undertaken.
PTW will be using the Document Manager and this will need to be incorporated in the strategy.
QSDS0063.012 4 December 2011 Mincom Limited Page 31 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
8. Appendix C
PC 1 PC2 PC3
Task Id Ellipse Module Program Comments Task Id Ellipse Module Program Comments Task Id Ellipse Module Program Comments
PRE CONVERSION START
G1 3001 General Pearl Script P' Type
Profiles Pearl
Script Upload
G6 Table Codes Script Generic Table G2 3920 Chart of Script 1) MSO920 - G3 3920 Chart of Script 2) MSO930 -
File Upload Accounts CC Segment Accounts Exp Element
Detail Detail
CONVERSION START
O&M13 3610 Equipment Script MSF610 HR45 HR Table Files Script 8FAB - Terms of HR36 HR Table Files Script 801B - Earnings
Group Identifiers Employment Payroll Details
HR1 3760 Personnel Script 1) 810 Employee HR51 HR Table Files Script 819 - Leave wait G6
Administration Core Details Accruals
F12 3680 Fixed Assets Script (TC1 1) 680 Asset HR46 HR Table Files Script 8FAC - Terms of O&M17 3601 Equipment Script MSF602/000
Manual Load Header Detail Employment Structure
1 row)
F13 3680 Fixed Assets Script (TC1 2) 685 Sub- O&M1 3601 Equipment Cobol MSF600/601 HR40 HR Table Files Script 801C - Earnings
Manual Load Asset Detail Register Reporting Details
1 row)
F11 3660 Project Control Script Requried to load O&M5 3720 Work Manual Load by Hand, HR37 HR Table Files Script 8AC - Earnings
project detail. Groups 40 groups only Component
MSF720 Details
HR27 3870 Establishment Script 1) 870 Position O&M14 3401Operating Manual Load by Hand, HR38 HR Table Files Script 8AL - Earnings
Attributes and Statistics small number of Leave Details
PRCs equipment
involved -
includes Equip
Profile Setup
HR2 3760 Personnel Script 2) 760 Employee O&M12 Application Parts Script Includes Loading Wait HR42
Administration Personnel Details Lists of WGS APLs,
BOMS and
Servicing APLs
MSF 130/131
HR58 3760 Personnel Script 76T - Employee O&M3 3690 Standard Script Standard Job HR43 HR Table Files Script 803C -
Administration Position Transfer Jobs Header MSF690 Deductions
MSF693 Reporting Details
QSDS0063.012 4 December 2011 Mincom Limited Page 32 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
Tarong Energy CAR Project Data Interchange Plan
PC4 PC5 PC6
Task Id Ellipse Module Program Comments Task Id Ellipse Module Program Comments Task Id Ellipse Module Program Comments
G4 3920 Chart of Script 3) MSO940 - Wait G4
Accounts GL Code Detail
G5 3920 Chart of Script 4) MSO960 -
Accounts Posting Account
Load
HR57 HR Table Files Script 80P - Primary M6 3101 Catalogue Script Load Group Classes
Reporting MSF160
Codes
HR42 HR Table Files Script 803B - Wait M5 3101 Catalogue Script Load Item Name
Deductions M6,M5 on Codes MSF105
Payroll Details PC6
HR53 HR Table Files Script 8R1 - Roster M1 3101 Catalogue Script Required to load Wait M1
Work Codes catalogue for
Tarong &
Wivenhoe.
Catalog to
include BOMs
and Used On
APLs MSF100
MSF110
HR35 3730 Resourcing Script 1) 732 Resource M4 3108 Catalogue Script Load M7 3140 Stores Script Load to TARONG.
Types CURRENT. Required to load
Required to load inventory details
2500 WGS items MSF170
into catalogue
and inventory for
existing stock
items (Tarong &
Wivenhoe)
MSF170
HR41 HR Table Files Script 8CA - Earnings M4 3108 Catalogue Script Load NEW. M7 3140 Stores Script Load to
Costing Details Required to load WIVENHOE.
2500 WGS items Required to load
into catalogue inventory MSF170
and inventory for
existing stock
items (Tarong &
Wivenhoe)
MSF170
HR39 HR Table Files Script 8AA - M8 3140 Stores Script Required to load M12 3201 Supplier Script Required to load
EarningsAccum Warehouse Information Supplier Global and
ulator Details details (6 business
Warehouses) information
MSF180 MSF200/203
HR55 HR Table Files Script 8C1 - Time and Wait M7 on PC6 M13 3210 Purchasing Script Load to
Attendance TARONG.Required
Controls to load msf210
records for 25000
Stock codes
MSF210
HR56 HR Table Files Script 8C2 - Daily M11 3140 Stores Script Load MAIN. M13 3210 Purchasing Script Load to
Awards Required to load WIVENHOE.Requi
MSF175 usage red to load msf210
for the past 24 records for 25000
months MSF175 Stock codes
MSF210
QSDS0063.012 4 December 2011 Mincom Limited Page 33 of 33
7704EFD1-9FAF-4671-9F7F-CC47EA64F5D9.DOC
