Vacancy Database Access Sample Clauses

Vacancy Database Access. 19.5.1 Both the excess employee and their case manager will have pre-publication access to the xxxxxxxx.xx.xxx.xx (for employment classifications to which this Enterprise Agreement applies), including during any period when the excess employee is in a temporary assignment.
AutoNDA by SimpleDocs
Vacancy Database Access. 1.12.5.1 Both the excess employee and their case manager will have pre-publication access to the
Vacancy Database Access. 14.12.5.1 Both the excess employee and their case manager will have priority pre-publication access to the Jobs SA and SA Health xxxx.xxxxxxxxxxxxxxx.xxx.xx (for employment classifications to which this Enterprise Agreement applies) databases, including during any period when the excess employee is in a temporary assignment.
Vacancy Database Access. 14.12.5.1 Both the excess employee and their case manager will have priority pre-publication access to the Jobs SA and SA Health xxxx.xxxxxxxxxxxxxxx.xxx.xx (for employment classifications to which this Enterprise Agreement applies) databases, including during any period when the excess employee is in a temporary assignment. This clause ensures a reasonable time frame to assess suitability for a vacancy before it is published and provide genuine access to opportunity. This anticipates and accommodates volume/traffic for work injured, declared excess and NDIS materially affected employees with pre-publication access. PSA What You Have Told Us - 1. Job Protection Protection.

Related to Vacancy Database Access

  • 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.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Physical Access Control Unauthorized persons are prevented from gaining physical access to premises, buildings or rooms where data processing systems that process and/or use Personal Data are located.

  • 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.

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

  • WORK ACCESS The Association shall provide a current, written list of its Association Representatives to all heads of departments, offices, or bureaus represented herein and the CAO. The Association shall be responsible for keeping the list current. An Association Representative shall have access to department, office, or bureau facilities where Unit members are employed during regular working hours to assist employees covered under this MOU in addressing grievances when such Association assistance is requested by a grievant(s) or to investigate matters arising out of the application of the provisions of this MOU. The Association Representative shall request authorization for such visits by contacting the designated Management representative of the head of the office, department, or bureau. In the event immediate access cannot be authorized, the designated Management representative shall inform the Association Representative as to the earliest time when access can be granted. This Article shall not be construed as a limitation on the power of the head of a department, office, or bureau to restrict access to areas designated for security or confidential purposes.

  • Physical Access PROVIDER agrees to allow the Office of Early Learning and COALITION staff or sub-contractors immediate access to the facilities and spaces used to offer the VPK Program during normal business hours.

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • EU Access SAP will use only European Subprocessors to provide support requiring access to Personal Data in the Cloud Service and SAP shall not export Personal Data outside of the EEA or Switzerland unless expressly authorized by Customer in writing (e-mail permitted) on a case by case basis; or as excluded under Section 9.4.

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