150 likes | 231 Views
Shared Technical Architecture’s Role within the ECIO Organization. “Arkansas Shared Technical Architecture”. Executive CIO responsibilities pertaining to Shared Technical Architecture.
E N D
Shared Technical Architecture’s Role within the ECIO Organization “Arkansas Shared Technical Architecture”
Executive CIO responsibilities pertaining to Shared Technical Architecture • ECIO has the authority to define IT standards, policies and procedures to manage the information resources within the state. • This is accomplished through the Arkansas Shared Technical Architecture. • Shared Technical Architecture Team directs the formulation and publication of policies, standards, specifications, and guidelines for IT in the state. Act 1042-Section 4-a(2)(A) & a(2)(B)
What is a shared technical architecture? • A shared technical architecture is policies, standards, and best practices that have been agreed on, publicized and periodically reviewed by domain working groups. • Domain working groups represent a cross-section of state, legislative and judicial agencies, institutions of higher education, as well as the Information Network of Arkansas.
Shared Technical Architecture Program has existed for 5 years • A component of the Office of Information Technology (OIT) which was charged with creating standards to facilitate electronic access to government information and enable interoperability.
Current Examples • Information Architecture set standards for preservation, protection and disposition of electronic records for state agencies; • Accessibility Architecture set standards for hardware, application development and web design to comply with state accessibility laws.
Current Examples (continued) • Network Architecture group has reviewed the trouble areas on the state network and drafted network requirements for agencies which would aid in reducing these trouble areas. • Video Network Architecture is providing a framework for how agencies will deploy video conferencing technology that is compatible with Arkansas video network system.
Current Examples (continued) • Data Architecture group is finalizing standardizing data throughout state government. Benefits of data standardization include: • Information sharing across agency boundaries • Enterprise system interoperability • Reduces redundant data
Current Examples (continued) • Desktop Operating System & Application Suite Architecture has recently delivered the following: • Software License Management Guidelines (supporting the Governor’s Software Piracy Proclamation); • Recommendations for Upgrading Desktop Operating System and Application Software; • Considerations for Implementing Alternative Desktop OS and Application Suites;
Current Examples (continued) • Security Architecture: - Created the State Agency Security Policy Guidelines which contain minimum requirements concerning IT security measures • Actively creating security policies through the larger security working group as well as in the three smaller working groups • Public Key Infrastructure working group • Business Continuity working group • Disaster Recovery working group
Current Examples (continued) • Application Architecture: • Incorporating existing application development standards created in the security and accessibility working groups • Identifying application development best practices • Project Management Architecture
Process for Agency Contribution to Technical Policy and Standards • A policy has been recently drafted that defines the process to facilitate state agency participation in the development of IT policies, standards and best practices. • Present the plan (policy) to the Governor and to the General Assembly. Act 1042-Section 4-a(3); • The IT architecture domain working groups represent a cross-section of state agencies
Issues of Compliance with Enterprise Architecture • Agency IT projects will be evaluated on the basis of the ROI of the project, the value-added services, and the compatibility with state Shared Technical Architecture. Act 1042-Section 5-e(2) & e(3)
Issues of Compliance with Enterprise Architecture • In the event a state agency proposes an information technology project which does not comply with the state shared technical architecture: • Submit concerns related to noncompliance to the ECIO, who shall seek review and advice of the CIO Council [Act 1722-Section 17-f(1) & f(2) – amending Act 1042-Section 4-f(1) and f(2)] • A policy related to compliance with State’s Shared Architecture is currently in being developed.
Arkansas’ Approach to the Portfolio Management Model • Based on the Washington State portfolio management model • Links IT investments to business plans • Facilitates IT investment risk analysis • Provides for agency and statewide technology reporting • Promotes technology integration and interoperability • Compiles information about each agency’s IT investment portfolio from biennial plans
Act 1042 Web Pagehttp://www.cio.state.ar.us/Legislation/Legis_status.htm