Integration with legacy systems, databases and line of business applications is a tricky at the same time an interesting assignment for an Enterprise Architect. And amidst all, the complexity involved in introducing any new product and seamlessly trying to make it a part of the existing enterprise ecosystem is well known. One could argue that technology is at the core of the problem here. As in when these systems were designed it was the technical limitation that lead to the design of an application landscape often not productive, unstable, poorly received and at times misused by the business community. These issues then become part of a never ending mitigation activity that introduces newer and advanced products as per the market trends.
In case of Enterprise Content Management systems these typically take an upgrade/migration path. So would this assimilation effort be a non-issue if an organization was to start up today and plans to set up an ECM infrastructure conforming to the Legal, Compliance and Governance needs aspired at the Enterprise level? The latest Social, Cloud, Mobile and Big Data technology could theoretically be set up for a solution that works for the business community as seamlessly as the modern consumer apps that we crave and can’t live without. In reality technology alone is not the solution to such needs. The answer lies in getting a consensus on at least the following factors that influence the key Architectural decisions –
1. Organizational culture – mission, vision and values. It is the most significant aspect to keep in mind before designing an ECM architectural landscape where adherence to organizational culture in terms of its mission, vision and values should be given utmost importance. This enables the critical backing needed for the IT staff from the Stakeholders for a successful implementation.
2. Business prospects – use cases and scenarios. This is obvious as only after a thorough understanding of the business requirements, the planning and implementation can begin. The requirement gathering is an evolving process where changes have to be adopted at various levels but these have to be reviewed and approved by the appropriate committee that oversees the Corporate Governance.
3. Strategic milestones - The decision makers involved should understand the goal of such an implementation and its influence on the enterprise in a long run and the changes it could bring in the business processes. Clear milestones should be discussed and agreed upon that aligns with the Enterprise wide goals.
4. Legal and Compliance needs- The various legal and compliance requirements have to be discussed as per the industry sector e.g. Code of Federal Regulations for Food and Drugs.
5. End User - Involvement, Contribution and Adoption. Often sidelined this is an important aspect where the users (especially power users) have to be involved right from the beginning to participate and contribute towards the development of a solution that is close to their needs. They play a broader role as their approval is significant for an enterprise wide adoption.
#InformationGovernance #EnterpriseContentManagement