Technical Policy and Standards Andy Gorton – Senior Architect: Institutional Networks

Becta objectives for priority 6 Agree standards and specifications –clearly defined conceptual architecture understood and accepted by stakeholders Establish procurement agreements –aggregate and recognise national demand, delivering improved VFM whilst retaining appropriate local choice Adoption by customers and provision of support mechanisms

Connectivity Conceptual Architecture Institutional Infrastructure Data Services Learning Services (Archive > Infrastructure Seminar > Stephen Lucey)

Infrastructure process Set up procurement agreements/ ongoing mgt. Adopted by customers /provide support mechanisms Institutions Agree standards / specifications Stakeholder Input

Strategy and choice National Strategy –‘Joined up thinking’ –Minimum requirements –Procurement benefits –Accreditation Regional strategy/choice Local strategy/choice “Decisions should continue to be made at local level, but within a national framework of aims, priorities, responsibilities and standards” - Harnessing Technology, DfES

Local/regional requirements Institution Infrastructure Implementation Becta’s Technical Specification Becta’s Functional Specification Local/regional Functional Specification Becta’s Framework for ICT Technical Support Becta’s LANs matrix tool Becta’s Functional Specification Procurement guidance Institution Supplementary resources Required resources Supports the functional specification by giving institutions supplementary advice on questions to ask before implementation of a requirement takes place (available from December 2005) A tool that an institution can use for self evaluation processes against the requirements set out in the Functional specification. Sets out the functional requirements for institutions to aim to achieve within the next 3-5 years. Supports the Functional Specification by setting out the technical specifications and requirements for an institution’s infrastructure Best-practice Framework for ICT Technical Support (FITS) and is available to support the delivery of ICT in schools

Basic Principles and Prerequisites Reliability Coherence Affordability and Sustainability Planning Management and Support

Purpose of Functional Specification to be learner/educator centric to describe the issues that should be considered when designing and building school networks not technology specific details the functions that infrastructure should provide supported by technical documents, standards and specifications

Functional specification Using ICT to: –offer a wide range of choice and access Learners shall have access to remote learning tools, a learning platform, curriculum resources via a hosting service, Institutions should discuss with their LA/RBC decisions concerning choice and locations of access devices –support flexible working Learners and educators shall be able to access appropriate curriculum resources and administration data from all computers in the institution and from all learning spaces within the institution The institution’s network services shall be available for use by authorised users at all times within locally/regionally agreed service hours, unless scheduled maintenance is taking place

Functional specification Using ICT to: –manage data and improve efficiency The institution should implement a network that gives priority to data associated with particular learning activities Data gathering between LA and the institution should be via an automated process –secure data and protect the user All institutions and Local Authorities shall use a content and filtering system and this should be managed by LAs/RBCs in discussions with relevant institutions. Filtering should be able to be refined at an institutional level Institutions shall maintain ongoing documentation regarding their security requirements and should readdress this before extending or altering their network

Technical Specification Provides the technical details to provide the network required to meet the demands of the Functional Specification The document is designed to apply equally to a primary school and a secondary educational institution. The specification currently covers –Network Design –Application and Information Services –Security And will cover –System hardware (Nov 2005)

Technical Specification : Network Design This section covers: Wired networks Wireless networking Connecting multiple buildings Network Types Prioritising traffic Flexible Access Institutions shall install 802.3ab or 802.3z Ethernet in their backbone, between their servers and key network hardware. NAT should be applied at LA level IP addresses should be allocated by the institution’s RBC or LA. New wireless networking equipment shall conform to IEEE a or g standards. For distances between buildings of greater than 200m: –Optical fibre should be used. Where device usage are low, or less than 10 devices are to be networked, and cabling is not possible/favoured: –802.11a/g or Powerline technologies may be used. Institutions shall use a client/server network architecture. Institutions shall implement a repository with functionality for allowing mirroring of data and redundancy of physical media. Institutions should identify and applications or areas of their network where prioritising traffic via CoS would increase performance. Institutions shall give due consideration to implementing web interfaces for RAS, and should refer to Becta’s ongoing work in this area.

Technical Specification: Services and Applications This section covers: Office productivity, web based content and multimedia. Learning Platforms Communications Access to content. Collaborative learning tools Minimising Administration Pedagogical and administrative applications shall support open standards that allow the import and export of data in a range of commonly used formats that are independent of a particular platform. Learning platforms should link to the institution’s Management Information System. Institutions shall use an H.323- aware Firewall/NAT device or H.323 Proxy (this may be at the LA or RBC level. Infrequently accessed or frequently changing content should be located at a central location (or small number of mirror locations), such as at the LA or RBC. If implemented, IM should be managed, secured, and monitored. Institutions should implement an electronic facilities management system.

Technical Specification : Security This section covers: ICT security policies and procedures Physical ICT security Data Security Network security Internet and Remote access security Procedures shall be developed to record all devices and software in a detailed ICT resource register Institutions shall have a backup strategy that includes details of what is backed up, the frequency of backup, ……… Institution’s shall use as high a standard of authentication for WLANs as they do for their wired networks

Technical Specification : Network Technologies This section covers: Functions and standards for individual network segments (edge, core, ….) Device requirements and specifications for each segment Examples: The core shall provide server functions for the institution, including, but not limited to, data storage, application services, and security management. Core switches: –shall have forwarding bandwidth of at least 4Gbps. –shall have the capacity to be managed both directly and remotely

Links and contacts – Local strategy manager

Questions ?