Revision	Effective Date	Summary of Changes
NC	01/10/2002	Initial release
1.0	05/06/2003	Revision 1.0 release
2.0	10/17/2003	Revision 2.0 release 1. Introduction. Revised text to be consistent with newer domain documents. Added a graphic, references to applicable policies and standards, and footnote containing link to Enterprise Architecture Trends document. Expanded EWTA Domains graphic to be consistent with the one on the EA website. 4. Target Network Architecture. Updated the recommended implementation approach to clarify that the implementation of Target Network Architecture is the responsibility of each Agency and, when undertaken, shall be in accordance with Statewide Policy P700, Enterprise Architecture, and Statewide Policy P340, Project Investment Justification (PIJ). Removed implementation information relative to the roles and responsibilities for incorporation of the recommended principles, standards, and best practices into statewide IT contracts. The alignment of EWTA standards and best practices with statewide and agency IT contracts is presented in the Framework and Strategies document and Statewide Policy P700, Enterprise Architecture, to consistently address all EWTA domains. Replaced Network Architecture Table with Target Technology Table encompassing all EWTA domains, available at http://www.azgita.gov/enterprise_architecture/AZ_EA_Target_Technology_Table.htm. 5. Network Architecture Standards. Incorporated all Recommended Standards into the current, published version of Statewide Standard P710- S710, Network Infrastructure, available at http://www.azgita.gov/policies_standards. 6. Network Architecture Purpose. Removed the description of Enterprise Architecture Strategic Alignment with FY2002-03 State IT Plan. It is available at: http://www.azgita.gov/enterprise_architecture/. 8. Network Architecture Recommended Best Practices. Updated section to reflect the incorporation of certain Best Practices into Statewide Standard P710- S710, Network Infrastructure. Added several new recommended best practices. 9. Network Architecture Technology Trends. Removed entire section since reference to the location of the document it referenced has been added to the footnote in Section 1, Introduction. Appendix A. OSI Reference Model. Removed. Content has been replaced by the Target Technology Table, available at http://www.azgita.gov/enterprise_architecture/AZ_EA_Target_Technology_Table.htm. Appendix B. Agency Network Architecture “As-Is.” Removed. High-level and detailed network/system diagrams are maintained and collected in accordance with Statewide Standard P800-S815, Configuration Management. Appendix C. Internet Protocol Services Version Summary. Removed. IPv6 has been ratified as an industry standard and incorporated into Statewide Standard P700-S710, Network Infrastructure.

TABLE OF CONTENTS

3. NETwork Architecture DEFINITION.. 2

4. target network architecture.. 2

5. Network Architecture Standards.. 3

6. Network Architecture PURPOSE.. 4

7. Network Architecture GENERAL Principles.. 5

8. Network Architecture recommended Best Practices.. 7

1. introduction

The State of Arizona’s Enterprise Architecture (EA) describes a comprehensive framework for information technology (IT)[1] and business that supports the Arizona State government strategic plan. EA facilitates the application of information technology to business initiatives and objectives and subsequent change in an orderly, efficient manner by describing a direction for current and future activities, supported by underlying principles, standards, and best practices.

EA effectively supports and enhances the business of government and improves the ability to deliver responsive, cost-effective government functions and services. Effective utilization of technology to achieve business functions and services, increasing citizen access to those services, sharing information and resources at all levels of government, and maximizing IT resources investment are major motivating factors for the development and implementation of EA.

The implementation of EA presents opportunities for State agencies to interoperate together to deliver a higher level of courteous, efficient, responsive, and cost-effective service to the citizen owners and employees of State government. Individually, each State agency can independently implement EA components that are interoperable, however, e-government initiatives, economies of scale, consolidation, and cross-agency savings may best be realized not just through interoperability, but also by working together in partnership and sharing.

EA includes important business, governance, and technical components. The technical components, collectively referred to as Enterprise Wide Technical Architecture (EWTA), provide technical guidance to State agencies. That guidance is supported by principles correlated to agency business functions, recommended standards, applicable recommended best practices, and technology trends[2]. Each component, or domain, of the EWTA is a separate but interrelated, architectural discipline. EA is the glue that integrates each of these technical disciplines into a cohesive framework having the potential to transform government by improving service delivery, reducing costs, simplifying and streamlining requirements and services, and increasing efficiency and effectiveness.

EA applies to all agencies. The agency director, working in conjunction with the agency CIO, is responsible for ensuring the implementation of EA within the agency’s “sphere of influence,” as designated by statute or rule. The EA Target Domain Architecture documents define an overall strategy and technical framework; however, by design, the capital planning, process approach and timeframes for transition, project management, and investment control for the implementation of the target architectures are the responsibility of the agency[3]. Implementing EA requires significant capital investments. Arizona, like most states, does not have unlimited capital to invest in implementing EA, therefore, migrating to EA within available budgets is the only viable method.

2. Network Architecture Vision

The State of Arizona’s Network Architecture delineates a reliable, scalable, resilient set of agency infrastructures that economically support the State’s business functions in an efficient and effective manner. Network Architecture describes a network infrastructure that supports converged services, as well as accommodating traditional data, voice, and video services, providing the framework and foundation to enable budget unit business processes, new business opportunities, and new methods for delivering service.