Скачать презентацию November 2006 Enterprise Architecture Overview November 2006 Скачать презентацию November 2006 Enterprise Architecture Overview November 2006

4eac582b6c3d55ba3efc559bdb56ff12.ppt

  • Количество слайдов: 19

November 2006 November 2006

Enterprise Architecture Overview November 2006 Enterprise Architecture Overview November 2006

Our Areas of Interest • Business – HE Functional Reference Models • Platform Standards Our Areas of Interest • Business – HE Functional Reference Models • Platform Standards – Taxonomy • Architecture Governance • What other Universities are doing in this space • Methods/Tools being used to achieve goals of EA November 2006 3

Where we have come from • Organisational change – 2005 restructure • Legacy Technology Where we have come from • Organisational change – 2005 restructure • Legacy Technology unable to support the business going forward • Little or No standards / methodology • No one overseeing the “bigger picture” across the organisation • Decentralised IT November 2006 4

Enterprise Architecture and Uo. N • Very early stages • Major business and systems Enterprise Architecture and Uo. N • Very early stages • Major business and systems change § Organisation Restructure completed early 2006 § Centralised IT § Program of Works (EPMO) within IT § Formation of roles/groups (AAG, CAB, Po. W, Change Office, IT Governance Committee) • Introduction of Groups and Processes § Start of ITIL implementation, Change Office (PMO), “formalised” Project Methodology and SDLC, Architecture Governance, Standards • Enterprise Architecture Consultant – “EA in a box” § Light inventory across Business, Information, Applications, Technology § Provided principals, some mapping between inventories, gap analysis § Current Activities/Changes/Lack of Ownership made this difficult – “hitting a moving target” § Tool - System Architect November 2006 5

Enterprise Architecture and Uo. N • 2006 Program of Works § 50+ Projects with Enterprise Architecture and Uo. N • 2006 Program of Works § 50+ Projects with IT underpinning them § Infrastructure (network, server consolidation, etc) § Information Management (BI, ECMS) § Business (HR, Finance, Research, Students, Facilities, etc) § Teaching / Learning (Blackboard/LOMS, Academic Support) § Operational (ID Mngt, Integration, adopt mainstream technology) § Client Services (“ 17000” Centralised Service Desk, MOE, ITIL rollout) § NUWays: Focussed on Business Process Improvement and EPMO • Formed § Change Office § AAG – Architecture Advisory Group § CAB – Change Advisory Board § Project Portfolio’s – Program of Works November 2006 6

Enterprise Architecture and Uo. N • Currently only used by IT § Covers Po. Enterprise Architecture and Uo. N • Currently only used by IT § Covers Po. W and operations § Reaction to the amount of project work being undertaken, realisation for EA out of Po. W • AAG Membership § Enterprise Applications § Solutions Architect § Infrastructure § Security § Data Services § Client Services § Web Group § (Note: No Business Representation) • Bottom up approach to EA – driven by IT November 2006 7

Challenges Experienced • Current IT Inventory = 100+ Main Applications § ~65% in-house developed Challenges Experienced • Current IT Inventory = 100+ Main Applications § ~65% in-house developed – mainly “gap fillers” around the enterprise applications § Current upgrades will supersede some but still expected to be significant § Mixed blend of technology: Ø ERP, disparate systems Ø old and new technology Ø “islands of data” and “the spider web” of integration (point to point) • Time / Resources / Size of Work for Enterprise Architecture • Standards / Guidelines • Expectations of Business and IT • Implementation, Acceptance and Understanding of Enterprise Architecture within IT • Seen as a hold up for existing processes / projects November 2006 8

Our Enterprise Architecture Framework Business Model • Business Direction • Stakeholders • Functions • Our Enterprise Architecture Framework Business Model • Business Direction • Stakeholders • Functions • Information Business Architecture • Data Model • Information Flows • Databases • Applications Information Architecture Application Architecture • Application Integration • Application Technology • Server Technology • Network / Communications • Platforms / Operating Systems Technology Architecture • Database Systems • Security Technologies • etc. November 2006 9

Architecture Development Process Business and IT Strategies ensure that architectures align with business needs Architecture Development Process Business and IT Strategies ensure that architectures align with business needs and priorities Business Strategy IT Strategy Policies Principles give high level direction to enable decision making Enterprise Architecture Principles Technical Application Information Business ig h High-level context diagrams present broader picture Detailed models describe the subject matter at a project level et ai le d M ed iu Subject area models provide the linkage between the global context and projects D Target Model T 2 T 1 November 2006 Current Model Transition Plans provide the implementation “roadmap” m H Architecture layers provide linkage between business models and technical architecture Technology Standards and Guidelines Standards and guidelines provide specific direction on implementing 10 architectures

Uo. N Service Delivery Model / Value Chain Develop services Get New Business ATTRACT Uo. N Service Delivery Model / Value Chain Develop services Get New Business ATTRACT STUDENTS Student DESIGN PROGRAM ADMIT STUDENTS ENROL STUDENTS Support services Research SCOPE RESEARCH PROJECT CORPORATE INFORMATION MARKETING/ PUBLIC RELATIONS FINANCE MANAGEMENT HR MANAGEMENT November 2006 MARKET RESEARCH PROJECT RESEARCH SERVICES IT MANAGEMENT Get paid INVOICE STUDENTS PROCESS PAYMENT or FUNDING PROCESS FUNDING ACADEMIC REGISTRAR FACILITIES MANAGEMENT Deliver services NUWAYS Project TRANSFER LEARNING ASSESS LEARNING Degree VALIDATE LEARNING CONDUCT AND PUBLISH RESEARCH GRADUATE STUDIES Research outputs, papers INTERNATIONAL LEGAL COUNSEL 11

Student Service Delivery Model Develop services Get paid Get New Business Deliver services Identify Student Service Delivery Model Develop services Get paid Get New Business Deliver services Identify new program need ATTRACT STUDENTS INVOICE STUDENTS PROCESS PAYMENT or FUNDING TRANSFER LEARNING ASSESS LEARNING VALIDATE DEGREE Set up/verify Program Set up/verify charges Receive payment Design learning(1) Design exams (2) Verify degree requirements met Apply admission rules Set up/verify courses Publish fee charges Apply payment against student debt Organise learning Organise exams Organise ceremony Make offer Publish program/courses Configure fees and rules (Nustar) Deliver learning Conduct exams Conduct ceremony Set up/verify timetable (lectures) Run tuition calculation process (Nustar) Mark exams Run billing process Validate and publish results ADMIT STUDENTS Understand Set/verify target markets admission rules Design program Promote university Evaluate Provide program information (program review) Redesign program ENROL STUDENTS Set up/verify timetable (tutorials) DESIGN PROGRAM Provide scholarships Reconcile for compliance Program revised, new program outlined Events hosted, materials distributed Offer/No Offer produced Program/courses /timetables published Bill sent November 2006 (1) learning includes: courses, lab, tutorial, placements Payments received Learning(1) delivered Grade published Degree conferred 12 (2) exams: includes all forms of evaluation (lab, tutorial, course work)

Architecture Governance Model Senior Executive level IT Governance Committee IT Management level IT Policy, Architecture Governance Model Senior Executive level IT Governance Committee IT Management level IT Policy, Standards & Architecture Review Subject matter experts Architecture Adhoc Advisory working groups Group IT service delivery teams IT development teams Vendors and consultants November 2006 13

Architecture Principles Information Architecture Principles Application Architecture Principles Single Customer Identification Common Use Applications Architecture Principles Information Architecture Principles Application Architecture Principles Single Customer Identification Common Use Applications Consistent Definition of Products Business Ease of Use Identification of Customer Contact Points Re-use Before Buying Architecture Data Accessible Across University of Buy Before Building Newcastle Minimise Package Modifications Timely Information Component-based Architecture Reuse Data Channel and Device Independence Use One Data Master Integration Services Independence Information Application External Environment Single Algorithm for Each Business Interfaces to Architecture Measure Adopt Web-based Technologies Data Security Common Vocabulary and Data Definitions Technology Architecture Principles Centralised Analytical Data Repositories Technical Environment for the Future Consistent Office Environment Use Proven Technologies Technology Architecture Ensure Enterprise-Wide Integration of IT Disaster Recovery / Business Continuity Security Interoperability Non-Repudiation Control Technical Diversity Deploy a Perimeter Layer Protecting A Single Integrated WAN based on IP Internal Network Access Protocol Security Infrastructure to Support Distributed Users November 2006 Use Portals to Provide Security at a Higher Level 14

Enterprise Architect Solutions Architect Project Management Architecture Services for Projects 2. Design 1. Discovery Enterprise Architect Solutions Architect Project Management Architecture Services for Projects 2. Design 1. Discovery Business idea Business Case Preliminary advice re: solution options & architectural implications 1. Preliminary consultation Project Charter Business Requirements Specification Advice regarding implementation (eg cost/time) of technology solutions 2. Project planning advice Ongoing advice to refine project shape 3. Detailed architectural analysis (environmental scanning; gap analysis; assessment of options etc) New/changed architectural components required by project Business trends and strategies Technology trends November 2006 New/changed architectural components required due to external factors Functional PROJEC T PATH Specification Enterprise Architecture Model Technical Design Specification PTO Recommended technology solution Solution Options Enterprise Architecture Principles Implementation of new/changed architecture components (those not project specific) 15

Architecture Services for Projects Technical Design Specification Cont’d 3. Deployment Issues Register PROJEC T Architecture Services for Projects Technical Design Specification Cont’d 3. Deployment Issues Register PROJEC T PATH Go Live Escalation of architectural issues 4. Architectural compliance review Enterprise Architect Solutions Architect Project Management 2. Design cont’d Implementation of new/changed architecture components (project specific) Resolution of architectural issues 5. Architectural issues management Incorporate new/changed elements into the Enterprise Architecture Model Enterprise Architecture Principles Enterprise Architecture Model November 2006 16

Technology Architecture Components November 2006 17 Technology Architecture Components November 2006 17

Where to from Now? • Adoption of Use of Enterprise Architecture outside of IT Where to from Now? • Adoption of Use of Enterprise Architecture outside of IT • Establish an EA group with a business focus • Learn and improve • Work collaboratively • Continual Development of Enterprise Architecture with alignment to the strategic direction of Uo. N • Become proactive rather than reactive November 2006 18

Thankyou • David Hall Program Director – Project Office David. Hall@newcastle. edu. au • Thankyou • David Hall Program Director – Project Office David. [email protected] edu. au • Stephen Bosworth Enterprise Applications Stephen. [email protected] edu. au • Carey Steller Solutions Architect Carey. [email protected] edu. au November 2006 19