Future Approach to Access, Success and Progression Sample Clauses

Future Approach to Access, Success and Progression. At the time of writing this Access Agreement, the University is undertaking a review of our Widening Participation Strategy, the outcomes of which will drive our targets in the years to come. It is our intention to publish our new Widening Participation Strategy by Autumn 2017 with final approval from Academic Board in December 2017. In identifying our future priorities, we have undertaken analysis of our past performance and considered both the internally and externally available evidence on the effectiveness of different forms of financial support; we have also considered the external environment within which we are likely to be operating, including the competitive environment, the likely impact on student numbers and on the potential for growth. On the basis of this analysis, we have identified our future strategic priorities and, through our Performance Indicators, those areas where we feel we can make the most significant contribution.
AutoNDA by SimpleDocs

Related to Future Approach to Access, Success and Progression

  • System Access Control Data processing systems used to provide the Cloud Service must be prevented from being used without authorization. Measures: • Multiple authorization levels are used when granting access to sensitive systems, including those storing and processing Personal Data. Authorizations are managed via defined processes according to the SAP Security Policy • All personnel access SAP’s systems with a unique identifier (user ID). • SAP has procedures in place so that requested authorization changes are implemented only in accordance with the SAP Security Policy (for example, no rights are granted without authorization). In case personnel leaves the company, their access rights are revoked. • SAP has established a password policy that prohibits the sharing of passwords, governs responses to password disclosure, and requires passwords to be changed on a regular basis and default passwords to be altered. Personalized user IDs are assigned for authentication. All passwords must fulfill defined minimum requirements and are stored in encrypted form. In the case of domain passwords, the system forces a password change every six months in compliance with the requirements for complex passwords. Each computer has a password-protected screensaver. • The company network is protected from the public network by firewalls. • SAP uses up–to-date antivirus software at access points to the company network (for e-mail accounts), as well as on all file servers and all workstations. • Security patch management is implemented to provide regular and periodic deployment of relevant security updates. Full remote access to SAP’s corporate network and critical infrastructure is protected by strong authentication.

  • Access Control Supplier will maintain an appropriate access control policy that is designed to restrict access to Accenture Data and Supplier assets to authorized Personnel. Supplier will require that all accounts have complex passwords that contain letters, numbers, and special characters, be changed at least every 90 days, and have a minimum length of 8 characters.

  • Data Access Control Persons entitled to use data processing systems gain access only to the Personal Data that they have a right to access, and Personal Data must not be read, copied, modified or removed without authorization in the course of processing, use and storage. Measures: • As part of the SAP Security Policy, Personal Data requires at least the same protection level as “confidential” information according to the SAP Information Classification standard. • Access to Personal Data is granted on a need-to-know basis. Personnel have access to the information that they require in order to fulfill their duty. SAP uses authorization concepts that document grant processes and assigned roles per account (user ID). All Customer Data is protected in accordance with the SAP Security Policy. • All production servers are operated in the Data Centers or in secure server rooms. Security measures that protect applications processing Personal Data are regularly checked. To this end, SAP conducts internal and external security checks and penetration tests on its IT systems. • SAP does not allow the installation of software that has not been approved by SAP. • An SAP security standard governs how data and data carriers are deleted or destroyed once they are no longer required.

  • Start-Up and Synchronization Consistent with the mutually acceptable procedures of the Developer and Connecting Transmission Owner, the Developer is responsible for the proper synchronization of the Large Generating Facility to the New York State Transmission System in accordance with NYISO and Connecting Transmission Owner procedures and requirements.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Parent Right to Access and Challenge Student Data The LEA shall establish reasonable procedures pursuant to which a parent, as that term is defined in 105 ILCS 10/2(g), may inspect and/or copy Student Data and/or challenge the accuracy, relevance or propriety of Student Data, pursuant to Sections 5 and 7 of ISSRA (105 ILCS 10/5; 105 ILCS 10/7) and Section 33 of SOPPA (105 ILCS 85/33). The Provider shall respond to any request by the LEA for Student Data in the possession of the Provider when Provider cooperation is required to afford a parent an opportunity to inspect and/or copy the Student Data, no later than 5 business days from the date of the request. In the event that a parent contacts the Provider directly to inspect and/or copy Student Data, the Provider shall refer the parent to the LEA, which shall follow the necessary and proper procedures regarding the requested Student Data.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Alignment with Modernization Foundational Programs and Foundational Capabilities The activities and services that the LPHA has agreed to deliver under this Program Element align with Foundational Programs and Foundational Capabilities and the public health accountability metrics (if applicable), as follows (see Oregon’s Public Health Modernization Manual, (xxxx://xxx.xxxxxx.xxx/oha/PH/ABOUT/TASKFORCE/Documents/public_health_modernization_man ual.pdf):

  • Union Access to Premises Representatives of the Union shall have access to the Company’s premises to carry on inspections or investigations pertaining to the terms and conditions of this Agreement, upon reasonable advance notice to the Company. Such access shall be carried on at reasonable hours and in such a manner so as not to interfere with the normal operations of the Company. The Union will advise the Company of its designated representatives who wish to gain access to the premises and the Union agrees to comply with all reasonable Company security precautions as may be in force from time to time.

  • Use of Interconnection Facilities by Third Parties 6551 Error! Hyperlink reference not valid.9.9.1 Purpose of Interconnection Facilities. 6551

Time is Money Join Law Insider Premium to draft better contracts faster.