Strategic Technology Architecture for Maine State Government What does it mean for Maine State IT?

1. Strategic Technology ArchitectureforMaine State GovernmentWhat does it mean for Maine State IT? Nancy Armentrout B. Victor Chakravarty

2. Strategic Architecture Committee Charter • Ad-hoc committee, chartered by the CIO. Members & Chair appointed by the CIO. • Set and communicate architectural directions for critical IT infrastructure and applications. • Examine emerging issues and develop architecture road-maps for guiding day-to-day decisions and new projects. • Horizon is two bienniums, rolling.

3. Committee Members • Core Tech: Greg McNeal, Jon Richard, Wayne Gallant, Sheldon Bird, Mark Kemmerle, Mike Pomerleau. • Agencies: Kevin Jones, Nancy Armentrout (Chair), David Blocher, Art Henry. • OCIO: Kathy Record, Victor Chakravarty, Paul Sandlin.

4. Many existing one-off solutions to support. Use our limited resources wisely. Be cost-effective. Orderly sunset and support of legacy products/technologies. Guide RFPs and purchases. Develop appropriate skills to properly support our services, technologies, products. Why Common Architecture?

5. Why Strategic Architecture? • Facilitate the Governor’s interoperability and integration initiatives. • Support agencies and programs as they proceed to improve service delivery and reduce costs. • Provide integration of services, improved access, and higher availability. These are now routine expectations of agencies and programs.

6. Committee Strategy • Iterative approach • Urgent need to limit the buffet of technology options and increase interoperability. • First Pass • Identify mainstream technologies that move us forward in the direction believed to be correct • Standardize • Second Pass • More strategic • More input from the business community • Refine standards where necessary

7. The First Pass • Review 2002 Strategic Plan. • Start with categories identified in the old plan, modify and add where applicable. • For each category describe where we want to be in four years – using To-Be Roadmaps. • Identify technologies and products that help us get there and those that don’t – using Gartner Brick format • Put To-Be Roadmaps and associated Bricks out for vetting. • Hold focus group sessions to help get feedback • Update the bricks as standards • Publish internally. Incorporate in RFPs, etc.

8. The Second Pass • Engage the IT Executive Committee. • Talk to leaders in agencies and programs, to understand where they are headed with service delivery, information management, tools, connectivity, etc. • Develop the technology directions to support such plans. • Refine & finalize the To-Be Roadmaps. • Refine & finalize the Bricks to support them. • Publish externally. Link to RFPs, etc.

9. Committee Outputs to Date • Intranet Site for Internal Publishing • General Architectural Principles - Guidelines for Every Day Decision-making • Database Brick • Newsletter Articles • Meager feedback so far. Request more!

10. To-Be Roadmaps & Brick Categories Identified to Date • Single Sign On: Identity & Authentication Management • Web Publishing • Database, Reporting & Data Warehousing • Client Provisioning • Server Infrastructure • Applications Architecture • Network Services • Security

11. Criteria used to make selections • Installed base within the State • Customer Value (ROI) –discussed this criteria having the most weight • Supportability • Sustainability, (or Viability) • Market Position • Training Effectiveness • Scalability • Alignment w/ the long-term architecture vision • General excellence (Enterprise-class product)

12. Today’s Agenda • Describe the Brick format and the DB Brick. • You are the focus group for the DB Brick (both format and content). • What is the best way to reach you in the vetting cycle? • Introduce the Single Sign On and Web Publishing drafts (both To-Be Roadmaps & Bricks).

13. Brick Format