Project Initiation i - Upon final execution of the Agreement with the DISTRICT, the ARCHITECT shall: ♦ Review the Program Management Plan (PMP) with the DISTRICT and its representatives to familiarize them with the proposed tasks and schedule and develop necessary modifications. The PMP defines the Program Master Schedule and Budgets and each Project scope and budget.
ii - Within the first week following execution of the Agreement, meet with the DISTRICT and its representatives to prepare a detailed task analysis and work plan for documentation in a computer-generated project schedule.
iii - This task analysis and work plan will identify specific tasks including, but not limited to: ♦ interviews, ♦ data collection ♦ analysis, ♦ report preparation, ♦ planning, ♦ Architectural programming, concepts and schematic design preparation and estimating that are part of the work of the Project. Also identified will be milestone activities or dates, specific task responsibilities, required completion times necessary for the review and approval by the DISTRICT and by all regulatory agencies and additional definition of deliverables.
iv - Participate in a general Project kick-off meeting to include the ARCHITECT, appropriate sub-consultants, and DISTRICT staff.
v - The project kick-off meeting will introduce key team members from the DISTRICT and the ARCHITECT to each other, defining roles and responsibilities relative to the Project.
vi - Identify and review pertinent information and/or documentation necessary from the DISTRICT for the completion of the Project.
vii - Review and explain the overall project goals, general approach, tasks, work plan and procedures and deliverable products of the Project.
viii - Review and explain the task analysis and Project work plan for all parties present; determine any adjustments or fine tuning that needs to be made to the work plan.
ix - Review documentation of the Project kick-off meeting prepared by the DISTRICT’S representative and comment prior to distribution.
x - Base Drawings and Site Survey Information
Approval Process Tenant shall notify Landlord whether it approves of the submitted working drawings within three business days after Landlord’s submission thereof. If Tenant disapproves of such working drawings, then Tenant shall notify Landlord thereof specifying in reasonable detail the reasons for such disapproval, in which case Landlord shall, within five business days after such notice, revise such working drawings in accordance with Tenant’s objections and submit the revised working drawings to Tenant for its review and approval. Tenant shall notify Landlord in writing whether it approves of the resubmitted working drawings within one business day after its receipt thereof. This process shall be repeated until the working drawings have been finally approved by Landlord and Tenant. If Tenant fails to notify Landlord that it disapproves of the initial working drawings within three business days (or, in the case of resubmitted working drawings, within one business day) after the submission thereof, then Tenant shall be deemed to have approved the working drawings in question. Any delay caused by Tenant’s unreasonable withholding of its consent or delay in giving its written approval as to such working drawings shall constitute a Tenant Delay Day (defined below). If the working drawings are not fully approved (or deemed approved) by both Landlord and Tenant by the 15th business day after the delivery of the initial draft thereof to Tenant, then each day after such time period that such working drawings are not fully approved (or deemed approved) by both Landlord and Tenant shall constitute a Tenant Delay Day.
Initiation (i) Seller shall deliver a Transaction Request or Purchase Price Increase Request, as applicable, to Buyer on or prior to the date and time set forth in Section 4(b)(vii) prior to entering into any Transaction. Such Transaction Request or Purchase Price Increase Request shall include an Asset Schedule with respect to the Underlying Assets to be sold in such requested Transaction. Buyer shall confirm the terms of each Transaction by issuing a written confirmation to the Seller promptly after the parties enter into such Transaction in the form of Exhibit A attached hereto (a “Confirmation”). Such Confirmation shall set forth (A) the Purchase Date, (B) the Purchase Price, (C) the Repurchase/Release Date, (D) the Pricing Rate applicable to the Transaction, (E) the applicable Purchase Price Percentages, and (F) additional terms or conditions not inconsistent with this Agreement. Seller shall execute and return the Confirmation to Buyer via facsimile or electronic mail on or prior to 5:00 p.m. (New York time) on the date one (1) Business Day prior to the related Purchase Date.
(ii) The Repurchase/Release Date for each Transaction shall not be later than the Termination Date.
(iii) Each Confirmation, together with this Agreement, shall be conclusive evidence of the terms of the Transaction(s) covered thereby.
(iv) Subject to the terms and conditions of this Agreement, during such period Seller may sell, repurchase and resell Purchased Assets, Pledged Assets, Underlying Assets and Eligible Assets hereunder.
(v) No later than the date and time set forth in the Custodial Agreement, Seller shall deliver to the Custodian the Asset File pertaining to each Eligible Asset to be purchased by Buyer.
(vi) Upon Buyer’s receipt of the Trust Receipt in accordance with the Custodial Agreement and subject to the provisions of this Section 4, the Purchase Price may then be made available to Seller by Buyer transferring, via wire transfer to the account designated by the Seller, in the aggregate amount of such Purchase Price in funds immediately available.
DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK
Initiation of TIPS Sales When a public entity initiates a purchase with Vendor, if the Member inquires verbally or in writing whether Vendor holds a TIPS Contract, it is the duty of the Vendor to verify whether the Member is seeking a TIPS purchase. Once verified, Vendor must include the TIPS Contract Number on all purchase communications and sales documents exchanged with the TIPS Member.
Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may
(i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014.
(b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”).
(c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.
(d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website.
(i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i).
(ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute.
(iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator.
(iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator.
(v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below.
(e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e).
(i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2.
(ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11.
(iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions.
(iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors.
(v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder.
(f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6.
(g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).
Clinical 1.1 Provides comprehensive evidence based nursing care and individual case management to a specific group of patients/clients including assessment, intervention and evaluation.
1.2 Undertakes clinical shifts at the direction of senior staff and the Nursing Director including participation on the on-call/after-hours/weekend roster if required.
1.3 Responsible and accountable for patient safety and quality of care through planning, coordinating, performing, facilitating, and evaluating the delivery of patient care relating to a particular group of patients, clients or staff in the practice setting.
1.4 Monitors, reviews and reports upon the standard of nursing practice to ensure that colleagues are working within the scope of nursing practice, following appropriate clinical pathways, policies, procedures and adopting a risk management approach in patient care delivery.
1.5 Participates in xxxx rounds/case conferences as appropriate.
1.6 Educates patients/carers in post discharge management and organises discharge summaries/referrals to other services, as appropriate.
1.7 Supports and liaises with patients, carers, colleagues, medical, nursing, allied health, support staff, external agencies and the private sector to provide coordinated multidisciplinary care.
1.8 Completes clinical documentation and undertakes other administrative/management tasks as required.
1.9 Participates in departmental and other meetings as required to meet organisational and service objectives.
1.10 Develops and seeks to implement change utilising expert clinical knowledge through research and evidence based best practice.
1.11 Monitors and maintains availability of consumable stock.
1.12 Complies with and demonstrates a positive commitment to Regulations, Acts and Policies relevant to nursing including the Code of Ethics for Nurses in Australia, the Code of Conduct for Nurses in Australia, the National Competency Standards for the Registered Nurse and the Poisons Act 2014 and Medicines and Poisons Regulations 2016.
1.13 Promotes and participates in team building and decision making.
1.14 Responsible for the clinical supervision of nurses at Level 1 and/or Enrolled Nurses/ Assistants in Nursing under their supervision.
Clinical Studies The animal and other preclinical studies and clinical trials conducted by the Company or on behalf of the Company were, and, if still pending are, to the Company’s knowledge, being conducted in all material respects in compliance with all Applicable Laws and in accordance with experimental protocols, procedures and controls generally used by qualified experts in the preclinical study and clinical trials of new drugs and biologics as applied to comparable products to those being developed by the Company; the descriptions of the results of such preclinical studies and clinical trials contained in the Registration Statement and the Prospectus are accurate and complete in all material respects, and, except as set forth in the Registration Statement and the Prospectus, the Company has no knowledge of any other clinical trials or preclinical studies, the results of which reasonably call into question the clinical trial or preclinical study results described or referred to in the Registration Statement and the Prospectus when viewed in the context in which such results are described; and the Company has not received any written notices or correspondence from the FDA, the EMA, or any other domestic or foreign governmental agency requiring the termination, suspension or modification of any preclinical studies or clinical trials conducted by or on behalf of the Company that are described in the Registration Statement and the Prospectus or the results of which are referred to in the Registration Statement and the Prospectus.
Deployment (a) In filling a position vacancy at a location NAV CANADA may proceed by the transfer of an employee at the same level.
(b) For the purposes of this Article, a “transfer” shall be considered to be a lateral change in position.
(c) Transfer requiring relocation under the NCJC Travel Program shall be subject to the employee’s written consent.
Clinical Trials The studies, tests and preclinical and clinical trials conducted by or on behalf of, or sponsored by, the Company, or in which the Company has participated, that are described in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus, or the results of which are referred to in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus, were and, if still pending, are being conducted in all material respects in accordance with protocols, procedures and controls pursuant to, where applicable, accepted professional and scientific standards for products or product candidates comparable to those being developed by the Company and all applicable statutes, rules and regulations of the FDA, the EMEA, Health Canada and other comparable drug and medical device (including diagnostic product) regulatory agencies outside of the United States to which they are subject; the descriptions of the results of such studies, tests and trials contained in the Registration Statement, the Time of Sale Disclosure Package or the Prospectus do not contain any misstatement of a material fact or omit a material fact necessary to make such statements not misleading; the Company has no knowledge of any studies, tests or trials not described in the Disclosure Package and the Prospectus the results of which reasonably call into question in any material respect the results of the studies, tests and trials described in the Registration Statement, the Time of Sale Disclosure Package or Prospectus; and the Company has not received any notices or other correspondence from the FDA, EMEA, Health Canada or any other foreign, state or local governmental body exercising comparable authority or any Institutional Review Board or comparable authority requiring or threatening the termination, suspension or material modification of any studies, tests or preclinical or clinical trials conducted by or on behalf of, or sponsored by, the Company or in which the Company has participated, and, to the Company’s knowledge, there are no reasonable grounds for the same. Except as disclosed in the Registration Statement, the Time of Sale Disclosure Package and the Prospectus, there has not been any violation of law or regulation by the Company in its respective product development efforts, submissions or reports to any regulatory authority that could reasonably be expected to require investigation, corrective action or enforcement action.
