1 Determining the High-level Direction of Information Systems Part 2

2 Computing Architecture  Looking at the IS mission, objectives, and goals, you can determine what technical requirements (computing architecture) are necessary to meet the IS objectives.

3 IS Objectives and Computing Architecture

4 A Detailed Description of The Computing Architecture  5.23

5

6

7

8

9

10 Information Architecture  For an organization with various locations, the question is often raised as to: * what information resides at each site, * what information is necessary at a corporate level, and * what information must be shared across sites.

11 Tabl e 5.1

12 Tabl e 5.1

13 Tabl e 5.1

14 CRUD Criteria  You can further clarify Table 5.1 with: C = Create R = Replace U = Update D = Delete

15 Policies and Responsibilities  You need to identify IS’s policies and responsibilities.  Having policies and responsibilities well documented can save hours of frustration for both users and IS personnel.  Be sure to update this information frequently and provide all users with convenient access to it.

16 Find out Policies and Responsibilities  What is the standard PC hardware that ISU supports ?  What is the standard PC software that ISU supports ?  Who is responsible for budgeting acquisition of PCs ? To whom does the PC belong?  Who is responsible for ensuring optimum pricing on PC hardware and software ?  Who is responsible for budgeting PC software ?

17 Find out Policies and Responsibilities  How does the organization manage PC retirement and who is responsible ? What methods do you utilize for PC disposal ?  What standards does the organization follow for user - developed PC applications ?  What is the company policy regarding PC games and Internet access ?

18 Find out Policies and Responsibilities  Who is responsible for organizing and funding PC training ?  What is the responsibility of any remote sites of ISU ? And what is the responsibility of the central ISU ?  What is the responsibility of the users and ISU for new business applications or projects ?

19 Annual Objectives  Clearly state what ISU will do and will not do in the coming year so that everyone has common expectations.  This is done through agreed-upon and prioritized annual objectives.  ISSC is the one doing the prioritization process.

20 Annual Objectives  Complete the prioritization only for projects above a certain level of effort or cost. * This hard level should be done by ISSC.  Small projects can be handled by ISU itself.

21 Different Prioritization Processes  Prioritization by business objective.  Prioritization by forced ranking.  Prioritization by performance impact criteria.

22 Prioritizing by Business Objective A) List the business objectives. (Identified in Phase 1 : Conceptual Business Level) B) Rank the importance of each business objective on a scale of 5 to 15, with 15 being the most important. C) List all IS projects. * If the list is too long, have ISSC identify any low-priority projects that will not be prioritized and just list the projects to be prioritized.

23 Prioritizing by Business Objective D) Identify the impact (1-10) each project will have on the business objectives. E) Multiply the impact with the business objective importance and total the score for each project. F) List projects in descending total score for a prioritized list of projects.

24 Prioritizing by Forced Ranking A) List all IS projects (Cut low - priority projects by ISSC). B) Go through a forced ranking process by comparing the first project with the second, the first project with the third, fourth, and so on through the entire list to find out the project with highest ranking. Then compare the second project with the third, fourth, fifth, and so on to find out the project with second highest ranking. The projects with highest ranking will bubble up on the top.

25 Prioritizing by Performance Impact Criteria A) Identify performance impact criteria, such as: * impact on customers * impact on quality of service/product * impact on reduction of business costs * impact on employees * impact on the speed of the process

26 Prioritizing by Performance Impact Criteria B) Rank the importance of the performance impacts (0-10). This number will become the project multiplier. C) List all IS projects. D) Through ISSC, agree on the impact an IS project will have on each of the performance impact criteria. Rate that impact on a scale of 0-10.

27 Prioritizing by Performance Impact Criteria E) Multiply the project multiplier in B with the rating for the project in D. Add up the total points for a project score. F) List the projects in descending score order for a prioritized list of projects.

28 IS Service Architecture  Service architecture is the blueprint that specifies which IS processes ( งานอะไรบ้าง ) and what kinds of people are required to support the business systems and computing architecture.  The service architecture should include: processes, people, organization, culture, technology, metrics.

29 Service Architecture  Processes : Major functions of ISU.  People : Hiring, skill development, and compensation practices.  Organization : Internal structure of ISU.  Culture : Values/beliefs held within ISU.  Technology : Characteristics of implemented and supported technology.  Metrics : Methods of providing and ensuring quality.

30 People  Business Area Experts * Specialization by business processes * Specialized knowledge of business systems that support those business processes * General knowledge of technology

31 People  Application Experts * Specialization by type of business system * Specialized knowledge of business systems capabilities, operations, and supporting tools * General knowledge of technology and business processes

32 People  Technology Experts * Specialization by technology component * Specialized knowledge of technology component capabilities, operations, and supporting tools * General knowledge of business systems and business processes

33 Processes  Projects * Deployment of new systems * Substantial additions to existing system capabilities * Substantial revisions to existing system capabilities

34 Processes  Enhancements * Minor revisions to existing system capabilities * Minor additions to existing system capabilities

35 Processes  Support * Operations * Maintenance * Troubleshooting * Consulting

36 Questions that May Help Improve ISU  Is ISU providing all the IS functions that are necessary? Are users providing support that ISU should?  Are the IS processes efficient? Are user inquiries handled quickly and efficiently? Are user satisfied with the support? Why or why not?

37 Questions that May Help Improve ISU  Are you hiring people with the skill set you require? Are you providing the proper development/learning for employees? Can employees cross into other areas of Information Systems and obtain cross-training?  What has been the turnover within ISU? What have been some of the reasons for leaving?

38 Questions that May Help Improve ISU  Are compensation policies aligned with market demands? Have you had significant turnover due to salaries?  Is the organization structured efficiently? Do you have the functions you will need in the future? Do job descriptions and titles accurately depict the functions that are needed today as well as in the future?

39 Questions that May Help Improve ISU  Are the values reflected through daily decisions?  Does the organization understand the direction?  How do you measure ISU’s efficiency and effectiveness?

40 Plan Contents VII. Information Systems Direction A. Mission B. Vision C. Strategic Objectives D. Strategies E. Information Systems and the Business Goals F. Computing Architecture

41 Plan Contents G. Information Architecture H. Policies and Responsibilities I. Information Systems Annual Objectives J. Service Architecture