Actors, roles and functions Sample Clauses

Actors, roles and functions. The main actors involved in the model have been classified as:IM / RU Rail Security Teams (RSTs): are the key participating members of the CSIRT community. Formed as a CSIRT, CERT, SOC or any other existing operational form operating at the national level. • The CHIRP4Rail Platform Operator (CPO): is the EU level Rail CSIRTs Threat Intelligence coordinator, thus operating at EU level with an intelligence coordination role. • The XX-XXXX within the UIC: is the natural steerer of the model as the current initiative hosting the rail CSIRT community discussion, thus providing the ideal framework for the hosting of the CPO.
Sample 1
AutoNDA by SimpleDocs

Related to Actors, roles and functions

  • MANAGEMENT FUNCTIONS B.1 The Association recognizes that the management of the Hospital and the direction of working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement and, without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to: (a) maintain order, discipline and efficiency; (b) hire, assign, retire, discharge, direct, promote, demote, classify, transfer, lay- off, recall, and suspend or otherwise discipline nurses, provided that a claim of discharge or discipline without just cause may be the subject of a grievance and dealt with as hereinafter provided; (c) determine, in the interest of efficient operation and high standards of service, job rating and classification, the hours of work, work assignments, methods of doing the work, and the working establishment for the service; (d) generally to manage the operation that the Hospital is engaged in and, without restricting the generality of the foregoing, to determine the number of personnel required, methods, procedures, and equipment in connection therewith; (e) make, enforce, and alter from time to time reasonable rules and regulations to be observed by the nurses which are not inconsistent with the provisions of this Agreement. B.2 These rights shall not be exercised in a manner inconsistent with the provisions of this Agreement.

  • Duties and functions 23.2.1 The Independent Engineer shall discharge its duties and functions substantially in accordance with the terms of reference set forth in Schedule 16. 23.2.2 The Independent Engineer shall submit regular periodic reports (at least once every month) to the Authority in respect of its duties and functions set forth in Schedule 16.

  • CUSTOMER SERVICE FUNCTIONS The Servicer shall handle all Customer inquiries and other Customer service matters according to the same procedures it uses to service Customers with respect to its own charges.

  • Contractor’s Responsibilities Unless stated specifically to the contrary in the tender with full supporting explanations, the contractor will be deemed to have concurred as a practical manufacturer with the design and layout of the works as being sufficient to ensure reliability and safety in operation, freedom from undue stresses and satisfactory performance in all other essentials as a working material.

  • MIXED FUNCTIONS An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

  • CONTRACTOR’S REPRESENTATIONS In order to induce the City to enter into this Work Order, the Contractor makes the following representations: 7.1 Contractor has familiarized itself with the nature and extent of the Contract Documents including this Work Order, work, site, locality, and all local conditions and laws and regulations that in any manner may affect cost, progress, performance or furnishing of the work. 7.2 Contractor has obtained at his/her own expense and carefully studied, or assumes responsibility for obtaining and carefully studying, soil investigations, explorations, and test reports which pertain to the subsurface conditions at or contiguous to the site or otherwise may affect the cost, progress, performance or furnishing of the work as Contractor considers necessary for the performance or furnishing of the work at the stated work order price within the Work Order stated time and in accordance with the other terms and conditions of the Contract Documents, including specifically the provisions of the IFB; and no additional examinations, investigations, explorations, tests, reports, studies or similar information or data are or is deemed necessary by Contractor for such purposes. 7.3 Contractor has reviewed and checked all information and data shown or indicated on the Contract Documents with respect to existing Underground Facilities at or contiguous to the site and assumes responsibility for the accurate location of said Underground Facilities. No additional examinations, investigations, explorations, tests, reports, studies or similar information or data in respect of said Underground Facilities are or is deemed necessary by the Contractor in order to perform and furnish the work under this Work Order price, within the Work Order time and in accordance with the other terms and conditions of the Contract Documents. 7.4 Contractor has correlated the results of all such observations, examinations, investigations, explorations, tests, reports and studies with the terms and conditions of the Contract Documents. 7.5 Contractor has given the City’s Contract Administrator written notice of all conflicts, errors or discrepancies that he or she has discovered in the Contract Documents and the written resolution thereof by City or its designee is acceptable to the Contractor.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Contractor’s Project Manager and Key Personnel Contractor shall appoint a Project Manager to direct the Contractor’s efforts in fulfilling Contractor’s obligations under this Contract. This Project Manager shall be subject to approval by the County and shall not be changed without the written consent of the County’s Project Manager, which consent shall not be unreasonably withheld. The Contractor’s Project Manager shall be assigned to this project for the duration of the Contract and shall diligently pursue all work and services to meet the project time lines. The County’s Project Manager shall have the right to require the removal and replacement of the Contractor’s Project Manager from providing services to the County under this Contract. The County’s Project manager shall notify the Contractor in writing of such action. The Contractor shall accomplish the removal within five (5) business days after written notice by the County’s Project Manager. The County’s Project Manager shall review and approve the appointment of the replacement for the Contractor’s Project Manager. The County is not required to provide any additional information, reason or rationale in the event it The County is not required to provide any additional information, reason or rationale in the event it requires the removal of Contractor’s Project Manager from providing further services under the Contract.

  • Sub-Contractors Transfer Agent may, without further consent on the part of Customer, subcontract with other subcontractors for telephone and mailing services as may be required from time to time; provided, however, that the Transfer Agent shall be as fully responsible to the Customer for the acts and omissions of any subcontractor as it is for its own acts and omissions.

  • Additional Functions Upon receipt of Proper Instructions, the Custodian shall take all such other actions as specified in such Proper Instructions and as shall be reasonable or necessary with respect to Repurchase Agreement transactions and the Securities and funds transferred and received pursuant to such transactions, including, without limitation, all such actions as shall be prescribed in the event of a default under a Repurchase Agreement.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!