Presentation to IT Directional Meeting

1. Presentation to IT Directional Meeting June 7, 2006 Pioneer Room, State Capitol

2. Agenda • Introduce New CIO – Lisa Feldner (Mike Ressler) • Mainframe Migration Project – Pay-off Note Early (Mike Ressler) • IT Planning Update (Nancy Walz) • Service Desk Update (Gary Vetter) • Budgeting Cost Estimate – Time Line (Vern Welder) • Staffing Challenges – (Vern Welder) • Views of Work Management System Database (Vern Welder) • Overview of Service Oriented Architecture (Vern Welder) • Mainframe Status (Dean Glatt) • 2nd Data Center (Dean Glatt) • PDA’s (Jerry Fossum) • Network Presentation (Glen Rutherford) • Security Update (Dan Sipes) • Rates (Dan Sipes)

3. Introduction of New CIO Mike Ressler, Deputy CIO Administration

4. Mainframe Migration Project Mike Ressler, Deputy CIO Administration

5. Agency Pay-Offof Migration Costs • Estimated Savings is 35% of Current Costs • ITD Borrowed $6,000,000 • Final Payment is December 2010 • Early Payments can be made by Agencies if Funds are Available at June 30, 2007 or during the 2007-09 Biennium • If Interested Call Greg Hoffman 8-4006

6. IT Planning Update Nancy Walz, Division Director IT Policy & Planning Division

7. IT Planning • Agency meetings are underway • Time and Labor “Proof of Concept” presentation June 28 or 29 • Business intelligence study findings presented May 22, report is available • Guidelines for budgeting are not yet available for these systems

8. New Standards Standard DIT003-06.1 Enterprise Database Security Purpose: Prevent unauthorized access to data in databases and achieve efficiencies in database consolidation. Adherence to this standard will ensure data consistency, proper management of disaster recovery, backups, point in time recovery processes and application testing. Standard DMT003-04.2 Document Management Purpose: To share knowledge and data, coordinate training, promote user groups and reduce cost of training and purchase of development tools/languages. Standard DT003-06.1 Desktop Operating Systems Purpose: To provide a secure, stable, and supported operating system on all personal computers (PC) within the Enterprise.

9. Existing Standards with Changes Standard EGT003-04.5 Web Development Summary of Changes: In previous versions of this standard, Appendix A included “Banner Implementation Instructions” that listed the code that is used to add the North Dakota State Banner to all agency web sites. These implementation instructions have been changed to list a URL where banner implementation instructions can be found, rather than listing the actual code in the standard. Standard EGT005-04.2 Web Domain Name Summary of Changes: The wording of the standard was changed to clarify that third level domains must “uniquely identify the state agency” in order to ensure that any individual agency doesn’t register a domain that could be deemed as belonging to the enterprise as a whole (ie. egov.nd.gov).

10. Existing Standards with Changes Standard OAT002-04.3 Groupware System Configuration and Usage Summary of Changes: Changes were made to Appendix A stating that the exclusively published, enterprise-wide email domain shall be @nd.gov. Standard OAT003-04.2 Desktop Application Suite Summary of Changes: The list of standard desktop publishing software in Appendix A was changed. Standard AST003-05.2 Public Online Services User Authentication Summary of Changes: Additional wording was added to the standard to ensure that all applications using the State’s login id for authentication will assign the login id to at least one security group within the State’s login id system. Changes were also made to ensure that all applications that use individual user accounts will reference those accounts by their Globally Unique Identifier (GUID).

11. Service Desk Update Gary J. Vetter, Division Director Customer Services

12. Service Desk Update • Service Desk Relocated to Northbrook Mall • Incident Management Process • Single Point of Contact • Priority Matrix • Resolved vs. Closed • Incident vs. Problem • Service Level Objectives • Customer Feedback

13. Budgeting Cost Estimate – Time Line Vern Welder, Division Director Software Development

14. Budgeting Cost Estimates • 2007 - 2009 Biennium IT Plans • July 15th deadline • Please request next Biennium planning cost estimates soon

15. Staffing Challenges Vern Welder, Division Director Software Development

16. Project Staffing Challenges • The Challenge is …… • In early May, we were 15 people short of our staffing needs • Advertising has produced mostly inexperienced applicants • The Software Developer market • Large companies are starting the large projects • Developer satisfaction with their jobs has risen • From 12/05 to 03/06 job satisfaction rose from 22% - 28% • Government pay

17. Project Staffing Challenges • The short-term fix • Allow developers to work overtime • Hiring contractors from vendor pool • Long-term • Continue advertising • Hire and train

18. Project Staffing Challenges • Impact on Customers • Higher project costs • Longer waits to start projects • Cautionary Measures we’re taking • ITD personnel lead as many projects as possible • New developers’ work is closely monitored

19. Views of Work Management System Database Vern Welder, Division Director Software Development

20. Work Management System Database Views • Customized look at the database • Relieves database complexity • You don’t need to be a technical person to understand the data • Why a view • Allows flexibility for reporting purposes • Data access is confined to your agency • View will be designed to meet your reporting needs • Data is protected from update

21. Work Management System Database Views • What will it cost? • Simplest ones we’ve done - $1,000 • The most complex one we’ve done - $2,000 • No on-going costs to access the data • Is it worth it? • Yes, Customers who have done this are pleased • References can be made available

22. Overview of Service Oriented Architecture Vern Welder, Division Director Software Development

23. Service Oriented Architecture (SOA) • Definition • From a Business Perspective • SOA is a construct and discipline whereby new business requirements are evaluated holistically against a backdrop of processes and functions that are currently in use by other business solutions. A common process or SERVICE that has been previously created and paid for is re-used, in whole or in part to create a new or improved process • From an IT Perspective • SOA is a software architecture model where loosely coupled software components representing granular, but complete technical or business functionality are accessible through known platform independent interfaces and transports over a network

24. Service Oriented Architecture (SOA) • It’s about the business • Not an IT issue • Technology is key, but…… • Business insight and emerging IT best practices must combine to make SOA successful • Break the business down into it’s components • Determine which components to move into the SOA architecture

25. Service Oriented Architecture (SOA) • Entry Points • People • Extend the ability to collaborate • Enhance People to People collaboration • Support multi-channel delivery • Process • Business model and process innovation • Seamless coordination between automated and people/information driven business process • Increase organizational effectiveness • Information • Must be separated from Process • Build an information strategy • Deliver trusted information in real-time and in context • Reduce risk and improve visibility into business operations

26. Service Oriented Architecture (SOA) • Governance Definition • Generic Governance • The responsibility, authority and communications to empower people. • Measurement, policy and control mechanisms to enable people to do their jobs. • SOA Governance • Extension of IT governance focused on the entire lifecycle of services to ensure the business value of SOA. Cradle-to-grave management of services.

27. Service Oriented Architecture (SOA) • Governance Cradle-to-Grave • Publish (in a SOA registry) • Promote • Deploy • Operate • Retire

28. Service Oriented Architecture (SOA) • Governance • Center of Excellence • SOA experts who maintain a knowledgebase of best practices • Drive SOA policies and processes • Can unify approaches across a large organization

29. Service Oriented Architecture (SOA) • Sample strategy (copied from Wachovia) • Wachovia Retail and Channel Technology will design, construct or acquire solutions with reusable assets within a Service Oriented Technology. • A business reference model will be used to drive requirements and identify services. • Services will be manageable, discoverable, shared, reused and available to Wachovia applications in all our execution environments. • Services will be identified and prescribed for use during the project feasibility and planning phase.

30. Service Oriented Architecture (SOA) • Recap • Defined SOA (Business and IT) • Explained that it is not about IT, it’s about business • Discussed entry points (People, Processes, and Information) • Explained Governance • Reviewed a Sample Strategy

31. Mainframe Status L. Dean Glatt, Division Director Computer Systems Division

32. 2nd Data Center L. Dean Glatt, Division Director Computer Systems Division

38. Wireless & PDA’s Jerry Fossum, Division Director Telecommunications Division

39. Wireless

40. PDA’s • Point of Contact • Tim Frederick • 328-2280 • tfrederick@nd.gov

41. PDA’s

42. Network Presentation Glen Rutherford, Network Architect Telecommunications Division

43. Security Update & Rate Update Dan Sipes, Division Director Administrative Services Division

44. Security Update • Rates

46. Thank you!