The central idea is the implementation of a ECM solution on a common collaboration and communication platform. In this way, advanced mobile and user requirements can also be combined and implemented. Central functions of such a ECM are:
» Metadata: These include creation date, storage date, storage location, current version and much more
» Context/Schema: Documents are usually created in a context. For example, a process instruction is based on previous versions. The basis for this is a process manual, which in turn corresponds to the internal process specifications and at the same time is based on legal regulations. This context should be documented in a transparent manner
» Information security and risk management: value, confidentiality, risk and need for protection
» Aggregation – dossiers: In addition to metadata, dossiers should also be available. This includes the direct context. For example all contracts, accounts, loans and additional notes with a customer of a financial service provider
» Change tracking: In the comparison of past and current versions, the changes should be highlighted and documented
» Signature: Documents should be genuine, i.e. signed. This ensures that no unauthorized changes have taken place
» Publishing process: Appropriate publication processes should be available, including multi-stage approval and follow-up
» Integration: Further solutions should be easy to integrate. For example, solutions for different levels of storage, the capture of printed documents, and more
» Extensibility and flexibility: The solution should be extensible to accommodate changed processes or regulatory requirements.
» Activation: All these functions should be available with a single click.