Why have an Information Systems Architecture
- First and foremost - Ensure information is stored securely, processed, integrated and available
- Improve efficiencies in business processes through enforcement of business rules, efficient approvals, and transparency in process status
- Minimise overlapping application capability to improve collaboration
- Reduce 'dark' data - PDF files, Raster scanned files without OCR
- Ensure clear ownership of Intellectual Property
Levels of Maturity
1. Application List - single live version
2. Categorised Application Catalogue - generated from a view of AppList
3. Integration Landscape (API/Integration Capability)
4. Data Flow, Data formats/schemas and System of Records defined
5. Process, Rules, and Approvals defined
Collaboration
1. Changes are always planned and communicated via live channels (portal)
2. Decisions and approvals are defined according to agreed roles & responsibility
No comments:
Post a Comment