Technical Architecture Quick Guide

DTS Technology Brief

Context

Technical Architecture (TA) exists in the context of the overall Department of Technolgy Services (DTS) business process, which incorporates TA in context with project and portfolio management, project management, product management, development life cycles, and operations. The key technical architecture business processes include:

• Technical Architecture Review for proposed and ongoing IT projects, including business case and alternative analysis.
• Architecture Development includes architecture and specific architecture component development through collaborative cross agency team activities with defined objectives and priorities.
• Standards Development includes new standards and reviews of existing technology standards.
• Research into emerging technologies that may have future benefit to agencies.

Questions and Answers

1. How do agencies participate in the four basic TA processes? 
   • Agencies suggest projects for TA Review and can participate in TA Review activities.
   • Agencies participate on teams developing specific and component architectures.
   • Agencies participate on Standards development teams and related review processes.
   • Agencies suggest areas for research into new and emerging technologies.
2. Who are the members of the Architecture Review Board (ARB) and how often does it meet?
   • The voting members of the board include the CIO, COO, and CTO, supported by designated technical architecture and management personnel.
   • The board meets once a month.
3. How can agencies place agenda items with the ARB for consideration?
   Send suggested agenda items to the ARB e-mail group at ARB@utah.gov. Please include a brief description of the project or other request, a required response date, and any other supporting information as appropriate. Agencies will be contacted to confirm the request and for further information as needed.
4. What kind of response can agencies expect from the ARB on technical architecture review requests?
   The time required is subject to the complexity of the review. After the request has been received, the standard target for TA review is a minimum of three weeks prior to the following ARB.
5. Where will TA documentation and ARB decisions be made available?
   All TA documentation and associated ARB decisions will be posted on the Standards Website. Links are provided to the TA Wiki, Document Repository, and all ARB documents.
6. What other resources are available for keeping informed on TA activities within the State?
   The TA Program Office provides a Technical Architecture list serve.
7. Is this just another bureaucratic activity, or does it add value?
   • TA is designed to be simple, responsive, and integrated with existing business case, project management, and planning activities.
   • TA provides an opportunity for agencies to get an objective look at specific project architectures and analysis for new areas of development by adding resources to agency efforts.
   • TA provides an opportunity to share resources and maintain an enterprise view when it is appropriate to do so.
   • TA provides clearly defined decision points in support of agency architecture and infrastructure requirements.

Summary

TA is focused on the technology and IT infrastructure required to support agency missions, goals, business objectives, tasks and processes. TA is focused on data and information, application, and technology architectures.

Outcome

Establish the evolving technical blueprint and accompanying standards and guidelines to manage the integration and interoperability of the old with the new across DTS and agency resources.

Mission

Develop and use the Technical Architecture to improve government efficiency and effectiveness.

Vision

The Technical Architecture is the cornerstone for the design, development, and implementation of information resources across State government.

Goals

• Improve utilization of government information resources to focus on core agency missions and service delivery to Utah citizens.
• Enhance cost savings and cost avoidance through use of Technical Architecture on a statewide basis.
• Increase cross agency and intergovernmental collaboration.
• Develop and maintain the TA and related architecural standards. • Review, reconcile, and approve architectures for agency core Lines of Business (LOB) and common IT services.
• Establish an effective lifecycle management relationship with the DTS Project Management Office (PMO) and implementation groups within DTS.