IT Architecture Development @Cardiff Not the MWE !

Current Architecture Major Systems Rests on IT Infrastructure (needs 24X7) New User Support Structure (TEG) Problems – architecture perspective Too Few ‘Maps’ (apart from in heads) Too Many Platforms - Mainly SW Too Many Boxes – Mainly HW Too complex linkages

Future Architecture Principles (1) Simpler (fewer different systems) Lower Cost (commodity products) More Flexible (rationalised architecture) More documentation (modelling) More Strategically aligned More controlled change

Future Architecture How do we get there ? Principles (2) Business need must drive IT People know, so use that Develop Architecture first, not designs Communicate it Pilots Quick wins Agile, iterative development

What new stuff do we need ? More understanding of what goes where (Architecture maps and models) More linkages to support new services Mesh vs Spoke and Hub Data hub ? Workflow and Process Control Useful metadata (why ?)

Where now ? Architecture Initiative Pilot Projects Consolidation SW - Linux distributions HW - Servers (e.g. use VMWare ?) Simplification Links – Reduce/Simplify Modelling Document processes, information and systems

Modelling Modelling Iterate to new Architectures 3 mth – Model type and depth 3 mth – Modelling tool choice (budget & effort needed) 3 mth iterations Iterate to new Architectures