Anonymous, bureaucrat, administrator
7,528
edits
Changes
From All n One's bxp software Wixi
no edit summary
In designing a database infrastructure it is important to build a solution that is capable of handling the requirements of current implementations and also expandable to handle the requirements of planned / projected requirements.
With data protection and up to date record management now a vital part of every businesses central data management plan, solutions for legacy systems can present enormous challenge.
Take for instance a large central customer list which is loaded into a big CRM system. A sample of records are taken to allow a limited marketing campaign. There are loads of updates of data to make. A second campaign for a different product includes overlaps. How do you ensure no double calling of customers? How to updates from one campaign up date the central and other campaign. bxp facilitates management of all and central campaigns and includes a wrap around for central update of a big CRM system or data warehouse.
If as part of the first campaign, someone opts of out marketing messages, it is the company's responsibility to update all the other campaigns and programs not to contact that person again. Given the speed of change and potential volumes of users, bxp is ideally positioned to remove this challenge in real time.
# The contact list is loaded with whatever data is available into a new campaign databaseform. (The green campaign form image in the diagram)# The campaign form is refined to make it useable usable for contact operations
# A data cleaning exercise is performed to remove dud records e.g. no name, test records, etc.
# The fields in the new campaign database form are aligned with the fields available in the Person database.# A further cleaning exercise is performed which allows information in the central Person database to filter into the campaign databaseform, especially regarding contact permissions.# A clean is done on the campaign database form removing all non-contactable records (i.e. data based removal, existing customers and customers where contact is not appropriate)
# Depending on the age of the campaign data, a feed into the central person database can also be performed.
# A two way comparison of fields is performed to update the campaign form and the central person records to see if extra information is required in the person database or could be captured during the performing of the campaign. (This steps ensures an evolving and growing Person database) Live link systems enable using AJAX in the campaign database form will allow a record to display person information and facilitate further linking and central updating.
# Where extra information such name, contact detail and key date information is to be updated, this can be done in real time.
# The ability to add link information linking a one person record as a child / relation to another person record will increase the value of the person stored information. This also allows for ever increasing information gathering on the person.
This process can be applied to any batch loading / availability of information. It does also allow a campaign form to be built and operated in complete isolation of the person database thus ensuring the quick turn around and flexibility of campaign where required. A campaign template can be developed with these primary links in it which would enable a copy process to speed up new campaign integration.
=== Testing ===
