Address Improvement Program: Challenges and Opportunities
Data Migration
The AddressImprovementProgram? (AIP) presents MajorMailUsers? and Vendors with significant challenges and opportunities with regard to the migration of data from pre- to post- AIP Address Management Systems (AMS).
The Simplest Case
In the simplest case, data from the existing AMS will be archived while the system is modified to AIP standards. Using DataMigrationTools?, a copy of the archived data will be also be modified, and, after successful testing of data and system (individually and together), repopulated into the 'new' production AMS.
Added Complexity
A substantial complication to implementation of AIP is that most MajorMailUsers? have address information imbedded across multiple legacy systems, not just in their mail system. The user must identify all instances of such data, the AddressDependentSystems? involved and the impact of AIP upon them. The user must have a DataMigrationProgram? that takes care of all impacts of the AIP and ensures continuing availability of all business systems.
The Fortunate Few
Depending upon their impacted systems, some users may find adjustment to AIP an exercise in DataMigration? within only a few databases and applications; and with only minor ProgrammingImplications?. With assistance from Vendors with state-of-the art DataMigrationTools? and extensive experience with DataMigration? and DataProcessingforAddressManagement?, they should be able meet the challenge of AIP within the tight timeframes imposed and without excessive cost.
They will take the opportunity of DataMigration? to improve their databases by, for example: archiving to reduce the size of active databases, culling unneeded records, eliminating redundancies, and ensuring synchronization of systems using common data elements. Add your own items . . .
They will meet the mandatory requirements to operate under AIP well within the established timeframe. And they will be positioned to further update and improve their databases, systems and BusinessMethods? to take full advantage of the enhanced capabilities afforded by AIP.
The Difficult Cases
Some MajorMailUsers? will have complex interfaces between multiple legacy systems impacted by AIP.
A very large organization may have mail systems interfacing with sales, marketing and customer management systems; interfacing with vendor and supply management systems; interfacing with legacy accounting and payroll systems (COBOL?) for a variety of businesses and locations (for a start). And they may (or may not!) be sharing address data.
Such an organization may find it challenging just to define the scope of its problem and allocate resources to its solution within the "grandfather" period. It is in some ways analogous to the Y2K problem - without the century long notice.
DataMigration? in these circumstances will be a major challenge involving complex DataAnalysis? and DataProcessing? on the one hand; and perhaps SystemAnalysis? and reprogramming and recompiling of LegacySystems? as well.
Vendors Role
If they are to overcome the most difficult AIP implementation problems, it will be vital for MajorMailUsers? to work with Vendors with the best DataMigrationTools? and extensive experience with DataMigration? and DataProcessingforAddressManagement? in very large environments.
Software Vendors will have a vital role too. They will go beyond the simple release of 'new version x.n' conformable to AIP standards. They will work in partnership with MajorMailUsers?, Vendors providing DataMigration? and other services, and CanadaPost to understand the full implications of AIP for MajorMailUsers?, and develop and install products to take full advantage of its potential.
Success
By coordinating systems change with a DataMigrationProgram?, MajorMailUsers? can meet the challenge of updating their AddressDependentSystems? and populating them with clean, formatted data in response to the AddressImprovementProgram?.
/priorPageHistory