Enterprise Architecture Office of Technology

Transcript:Enterprise Architecture Office of Technology:
Enterprise Architecture Office of Technology Services Matthew Vince, PMO Overview What is Enterprise Architecture? Governance Technology Team Appendix What is Enterprise Architecture? Benefits Decreased time and cost for procurements with standardized hardware and software requirements and specifications Can work with custom built or Commercial of the Shelf (COTS) software Decreased administrative costs with available cost-allocation tools delivered as part of the solution Improved SLA metrics and enforcement Reduced overall operating costs for software and hardware Improved, standardized security and event monitoring Increased reliability and performance by using reusable components LDH Modernization – How we arrived here Required for Federal compliance with Medicaid standards Guidance and rules from CMS and other Federal partners provide for: Service Oriented Architecture (SOA) Modular Development – No “Monoliths”, no “Big Bang” implementations Agile procurement, development, and release methodologies Needed to support the Medicaid Modernization (replacement of their core Medicaid systems: Eligibility/Enrollment, Provider Management, MMIS, et al.) What is Enterprise Architecture? It is an organizational, operational, and system design framework Service oriented approach – Service provider model Service oriented architecture (SOA) – Break systems down into modules with specific responsibility Business requirements drive technical decisions Overall design roadmaps and strategic planning Cost allocation, billing, and reporting Guidelines and support for all methods of system development – custom, hosted, COTS, Software as a Service (Saas) EA is the future vision for the State based on open standards. EA puts the State in a position to provide improved service and flexibility. “Silo” or “Monolith” systems can no longer be supported. Governance IT Governance Value can be recaptured through shared-service initiatives such as consolidating data centers, modernizing the IT infrastructure, better utilizing capacity, pooling IT staff, sharing best practices, consolidating procurement, and managing demand through central governance. IT service management must continue to align itself with the attitude of generating the maximum benefit for the agency and State as a whole. Operations lifecycle - Information Technology Infrastructure Library (ITIL): Problem and Incident Management, Change Management, Onboarding, Release Management, Request Fulfillment, Availability Management Federal cio Digital services playbook Today, too many of our digital services projects do not work well, are delivered late, or are over budget. Playbook of 13 “plays” drawn from successful private sector and government practices https://playbook.cio.gov/ “The American people expect to interact with government through digital channels such as websites, email, and mobile applications. By building digital services that meet their needs, we can make the