2. EA @ CSU 2006 Resources & Strategy

3. 2006 A balancing act to survive Understand what we need to do Promote what we do & our outputs Do Stuff / Get results

4. Stakeholder Model

5. Process Model

6. Org Model Project Management Records Management

7. The Team Architects (4) –Infrastructure (What it sits on) –Integration (How it’s shared) –Application (How we build it) –Information (What goes on/in it)

8. The Team Liaison (1) –Teaching & Learning –Community –Research –Business Director (herd the tanks) Lauren (the real boss)

9. The Team Others for WPI (3) –Contract Process Analyst –Contract BA –Trainee BA

10. Liaison Architecture is two way Gathering intelligence, getting feedback Educating, explaining, communicating back >>> Liaison Role

11. Architecture Vs Liaison FocusArchitectLiaison 1ArchitectureLiaison 2 Architecture

12. Pre Strategy Independently, the team all worried about the same things What is architecture? Education of what we do, why, how we’ve helped Be seen as professional, valued, made a difference It’s a big job Consistent advice based on a quality models We don’t sit in a room pulling ideas from the sky – we coordinate and facilitate the brains in the business and the IT division

13. A&L Customers CSU IT Operations

14. Strategy 2006 Don’t build architecture for architecture’s sake - prioritise it for best benefit So trap what’s going on – CSU & Industry Put them on the table and weigh up common, best benefits > ALIGN … then do something about it

15. Internal Positives @ month 2 Team interaction and perspectives > light bulbs coming on > real and obvious multi-disciplinary benefits > Passion Greater understanding amongst team of architecture really is Realisation that liaison and architecture are intrinsically linked Early models and roadmaps being developed We are experiencing pain where we guessed

16. First Alignment Experience

19. This is going on & where its headed So we should do these things Because … So “heads up everyone”

20. The List 300 things that are going on that we’ve got to do something with / worry about Approved projects, un-approved projects, unsuccessful project bids, interviews, committee decisions, working party outputs, rumours, innuendo, strategic plans, vendors, sector, technology trends, …

21. The List Explains why people are busy Exposes prioritisation process Of great interest to many Out of date, never ends

22. This is going on & where its headed So we should do these things Because … So “heads up everyone” & “let us explain”

23. 1 ----- 2 ----- 3 ----- 4 ----- 5 ----- 6 ----- 7 ----- 8 ----- STRATEGY LIST THEMES ACTIONS

24. The Junee Protocol (Actions) 1.Critical Technology roadmaps [ITOps] 2.Data governance & App Integration [Bus, ITOps] 3.Assist with infras projects underway [ITOps] 4.IDM [Bus, ITOps] 5.Assist legacy paths [ITOps] 6.App Rational’n / Portfolio Mgmt [Bus / ITOps] 7.Stds to assist operations [ITOps, Bus] 8.Collaboration roadmaps [Bus] “When” [Bus]

25. The Alignment Process Green & relatively insular Relies on the Division’s ability to communicate with the business Alignment becomes much clearer / relational But presumes CSU initiatives are a manifestation of CSU Strategy – not in a position nor enough evidence or models to influence

26. Current Fronts UniversityIT What Assets / ThingsData How ProcessCode S/W Applications Where LocationTechnology, H/W, N/W Who Org / StakeholdersRoles When Key Dates / CyclesEvents Why - Strategy / LegislationBusiness Rules

27. Measurements ComplexityData flows Data Centre Models Portfolio Known IssuesData Process review list StrategicSnapshots A&L Survey UnderstandingNo Off or % Time spent with business BlindersIssues hitting ITOps not heard of before

28. 2006 A balancing act to survive Understand what we need to do Promote what we do & our outputs Do Stuff / Get results More presentations today & tomorrow

29. Do Stuff Today – predominantly Data & Process But you can talk to my team about …

30. VOIP Data centre roadmaps Server replacement n-tier J2EE AREN Middleware / Integration Project technology stds Early SOA & BPM IDM direction Security Project EIS [Enterprise Impact Statements] Online Learning Env Innovation issues Collaboration strategy Digital Object Rep “CSU | When” (Central Events)