Interviews with Key EU Railway Security Stakeholders Sample Clauses

Interviews with Key EU Railway Security Stakeholders. As a further triangulation point concerning European railway cyber security stakeholders, a sample of high-level stakeholders were invited for interview (DG MOVE, ERA, ENISA, XX-XXXX, ERTMS, X2RAIL-3, ALSTOM, Infrabel, DB-Netz and DB-Systel). The set was chosen to include views from the main types of stakeholders and leaders in rail security development (European Commission, Agencies, Suppliers, XX-XXXX, Complementary project in Shift2Rail, Leaders in rail cyber security). A standard set of topics was used to allow comparison (structure of this section), followed by open discussion to encourage sharing of ideas. The results are integrated and summarised as follows, including only commonly shared views. Alternate views will be explored at the workshop stage.
AutoNDA by SimpleDocs

Related to Interviews with Key EU Railway Security Stakeholders

  • Stakeholders ‌ The following Service Provider(s) and Customer(s) will be used as the basis of the Agreement and represent the primary stakeholders associated with this SLA: IT Service Provider(s): Company name. (“Provider”) IT Customer(s): Customer (“Customer”)

  • Business Associate’s Subcontractors and Agents BA shall ensure that any agents and subcontractors that create, receive, maintain or transmit Protected Information on behalf of BA, agree in writing to the same restrictions and conditions that apply to BA with respect to such Protected Information and implement the safeguards required by paragraph 3.4 above with respect to Electronic PHI [45 C.F.R. Section 164.504(e)(2)(ii)(D); 45 C.F.R. Section 164.308(b)] BA shall implement and maintain sanctions against agents and subcontractors that violate such restrictions and conditions and shall mitigate the effects of any such violation [45 C.F.R. Sections 164.530(f) and 164.530(e)(1)].

  • Clients in this context, clients are people who are dependent upon the caring skills and services of the local authority, for example, the elderly, mentally infirm, those with mental or physical impairments. Clients in this context also include those whose needs are identified and catered for in settings such as schools and nurseries, that is, young children and school pupils dependent on the organisation for their educational and developmental welfare. Clients exclude internal authority customers (as in client departments) or external customers (for example, members of the public with planning applications), because neither are dependent on the local authority for their care and welfare. The exceptional needs of clients refer to those which are exceptionally demanding, not to those which are out of the ordinary.

  • Visitors to and Conduct on School Property Petitions or written correspondence to the Board shall be presented to the Board in the next regular Board packet. LEGAL REF.: 5 ILCS 120/2.06, Open Meetings Act. 105 ILCS 5/10-6 and 5/10-16. CROSS REF.: 2:220 (School Board Meeting Procedure), 8:10 (Connection with the Community), 8:30 (Visitors to and Conduct on School Property) Adopted: September 5, 2019 Meridian CUSD 223 2:240 Board Policy Development The School Board governs using written policies. Written policies ensure legal compliance, establish Board processes, articulate District ends, delegate authority, and define operating limits. Board policies also provide the basis for monitoring progress toward District ends. Policy Development Anyone may propose new policies, changes to existing policies, or elimination of existing policies. Staff suggestions should be processed through the Superintendent. Suggestions from all others should be made to the Board President or the Superintendent. A Board Policy Committee will consider all policy suggestions, and provide information and recommendations to the Board. The Superintendent is responsible for: (1) providing relevant policy information and data to the Board,

  • Member Access to Vendor Proposal Notwithstanding any other information provided in this solicitation or Vendor designation of certain documentation as confidential or proprietary, Vendor’s acceptance of this TIPS Contract constitutes Vendor’s consent to the disclosure of Vendor’s comprehensive proposal, including any information deemed confidential or proprietary, to TIPS Members. The proposing Vendor agrees that TIPS shall not be responsible or liable for any use or distribution of information or documentation by TIPS Members or any other party. By submitting this proposal, Vendor certifies the foregoing.

  • Public Outreach The Sponsor is responsible for development and administration of a public outreach effort to ensure public awareness and involvement in the Project development and delivery process. The Sponsor shall provide a copy of the public outreach plan and all materials documenting the public outreach activities, including public notices, press releases, flyers, etc. to the Authority. The public outreach plan must accompany the first invoice for payment from Sponsor. The materials documenting the public outreach activities must accompany the final invoice for payment from Sponsor.

  • MANAGEMENT OF EVALUATION OUTCOMES 12.1 The evaluation of the Employee’s performance will form the basis for rewarding outstanding performance or correcting unacceptable performance.

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

  • Foreign-Owned Companies in Connection with Critical Infrastructure If Texas Government Code, Section 2274.0102(a)(1) (relating to prohibition on contracts with certain foreign-owned companies in connection with critical infrastructure) is applicable to this Contract, pursuant to Government Code Section 2274.0102, Contractor certifies that neither it nor its parent company, nor any affiliate of Contractor or its parent company, is: (1) majority owned or controlled by citizens or governmental entities of China, Iran, North Korea, Russia, or any other country designated by the Governor under Government Code Section 2274.0103, or (2) headquartered in any of those countries.

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

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