Timing for Prior Consultation Sample Clauses

Timing for Prior Consultation. 5.5.1 The timeframe for Prior Consultation shall be six months from the date of receiving documents on Prior Consultation.
AutoNDA by SimpleDocs

Related to Timing for Prior Consultation

  • Prior consultation It is expected that the Parents, or duly authorised education guardian, will consult personally with the Head or with the Head's authorised deputy before Notice of Withdrawal is given by the Parents.

  • Data Protection Impact Assessment and Prior Consultation Processor shall provide reasonable assistance to the Company with any data protection impact assessments, and prior consultations with Supervising Authorities or other competent data privacy authorities, which Company reasonably considers to be required by article 35 or 36 of the GDPR or equivalent provisions of any other Data Protection Law, in each case solely in relation to Processing of Company Personal Data by, and taking into account the nature of the Processing and information available to, the Contracted Processors.

  • Notification and Consultation 1. A Party shall promptly notify the other Party, in writing, on:

  • HHS Single Audit Unit will notify Grantee to complete the Single Audit Determination Form If Grantee fails to complete the form within thirty (30) calendar days after receipt of notice, Grantee maybe subject to sanctions and remedies for non-compliance.

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers.

  • Independent Review Contractor shall provide the Secretary of ADS/CIO an independent expert review of any Agency recommendation for any information technology activity when its total cost is $1,000,000.00 or greater or when CIO requires one. The State has identified two sub-categories for Independent Reviews, Standard and Complex. The State will identify in the SOW RFP the sub-category they are seeking. State shall not consider bids greater than the maximum value indicated below for this category. Standard Independent Review $25,000 Maximum Complex Independent Review $50,000 Maximum Per Vermont statute 3 V.S.A. 2222, The Secretary of Administration shall obtain independent expert review of any recommendation for any information technology initiated after July 1, 1996, as information technology activity is defined by subdivision (a) (10), when its total cost is $1,000,000 or greater or when required by the State Chief Information Officer. Documentation of this independent review shall be included when plans are submitted for review pursuant to subdivisions (a)(9) and (10) of this section. The independent review shall include: • An acquisition cost assessment • A technology architecture review • An implementation plan assessment • A cost analysis and model for benefit analysis • A procurement negotiation advisory services contract • An impact analysis on net operating costs for the agency carrying out the activity In addition, from time to time special reviews of the advisability and feasibility of certain types of IT strategies may be required. Following are Requirements and Capabilities for this Service: • Identify acquisition and lifecycle costs; • Assess wide area network (WAN) and/or local area network (LAN) impact; • Assess risks and/or review technical risk assessments of an IT project including security, data classification(s), subsystem designs, architectures, and computer systems in terms of their impact on costs, benefits, schedule and technical performance; • Assess, evaluate and critically review implementation plans, e.g.: • Adequacy of support for conversion and implementation activities • Adequacy of department and partner staff to provide Project Management • Adequacy of planned testing procedures • Acceptance/readiness of staff • Schedule soundness • Adequacy of training pre and post project • Assess proposed technical architecture to validate conformance to the State’s “strategic direction.” • Insure system use toolsets and strategies are consistent with State Chief Information Officer (CIO) policies, including security and digital records management; • Assess the architecture of the proposed hardware and software with regard to security and systems integration with other applications within the Department, and within the Agency, and existing or planned Enterprise Applications; • Perform cost and schedule risk assessments to support various alternatives to meet mission need, recommend alternative courses of action when one or more interdependent segment(s) or phase(s) experience a delay, and recommend opportunities for new technology insertions; • Assess the architecture of the proposed hardware and software with regard to the state of the art in this technology. • Assess a project’s backup/recovery strategy and the project’s disaster recovery plans for adequacy and conformance to State policy. • Evaluate the ability of a proposed solution to meet the needs for which the solution has been proposed, define the ability of the operational and user staff to integrate this solution into their work.

  • CREDIT FOR PREVIOUS EXPERIENCE All employees shall be classified according to previous comparable supermarket experience. Previous comparable experience shall be granted on the following basis:

  • Credit for Prior Experience Credit shall be given new employees in initial step placement of the wage scale set forth in Appendix A for prior experience directly related to the same classification. Credit for prior experience which is somewhat related to the position for which the applicant applies will be granted on a basis of one (1) year credit for two (2) years’ experience.

  • Technical Feasibility of String While ICANN has encouraged and will continue to encourage universal acceptance of all top-­‐level domain strings across the Internet, certain top-­‐level domain strings may encounter difficulty in acceptance by ISPs and webhosters and/or validation by web applications. Registry Operator shall be responsible for ensuring to its satisfaction the technical feasibility of the TLD string prior to entering into this Agreement.

  • Tribal Consultation 1. For FEMA Undertakings on Tribal lands or potentially affecting properties of religious and cultural significance to Tribes, and where no tribe-specific consultation agreements or protocols are in place, FEMA shall consult with affected Tribe(s) or in accordance with 36 CFR Part 800. In determining who the affected Tribe(s) may be, FEMA will first establish that it is a type of Undertaking with potential to affect historic properties with religious and cultural significance and may consult with the SHPO and Tribe(s), and may access the National Park Service (NPS) Native American Consultation Database or other tools to identify geographic tribal interests.

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