|
- Content reuse
- You will have a consolidated list of new content required
for generating correspondence. Much of the content such as headers,
footers, disclaimers, and introductions are common to many letters
and can be reused across various letters. All such common content
can be created and approved by experts once and then reused in many
pieces of correspondence.
- Building the data dictionary
- There will be data values such as "Customer Id" and "Customer
Name" that are common to many letters. You can prepare a consolidated
list of all such data values. Typically someone from the enterprise middleware
team is consulted when planning the structure. This forms the basis for
building the Data Dictionary.
- Sourcing data from backend enterprise systems
- You will also know all of the data values that are needed
and from where the enterprise system data is obtained. You can then
architect the implementation to extract the data from the enterprise
system and feed to the correspondence management solution.
- Estimating the complexity of letters
- It is important to determine how complex it will be to create
a particular correspondence. This analysis helps in determining
the amount of time and skill sets that will be required to create
the letter templates. This in turn will help in estimating the resources
and cost of implementing the correspondence management solution.
|
|
|
