Drafting Job Descriptions and Person Specifications Sample Clauses

Drafting Job Descriptions and Person Specifications. All vacant posts must have a job description outlining the tasks and responsibilities of the role to ensure that applicants are informed of the duties. The job description will inform the person specification. The aims of a job description are to:
AutoNDA by SimpleDocs

Related to Drafting Job Descriptions and Person Specifications

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Changes to Specifications All Specifications and any changes thereto agreed to by the Parties from time to time shall be in writing, dated and signed by the Parties. No change in the Specifications shall be implemented by Cardinal Health, whether requested by Reliant or requested or required by any Regulatory Authority, until the Parties have agreed in writing to such change, the implementation date of such change, and any increase or decrease in costs, expenses or fees associated with such change. Cardinal Health shall respond promptly to any request made by Reliant for a change in the Specifications, and both Parties shall use commercially reasonable, good faith efforts to agree to the terms of such change in a timely manner. If after initial Product qualification, Reliant requests a change in the Specifications for its own benefit or to comply with the requirements of a Regulatory Authority, the Specifications shall be amended as soon as [***]: Certain information on this page has been omitted and filed separately with the Commission. Confidential treatment has been requested with respect to the omitted portions. possible after a request is made for any change in Specifications, and Cardinal Health shall notify Reliant of the costs associated with such change and shall provide such supporting documentation as Reliant may reasonably require. Reliant shall pay all costs associated with such Reliant-requested changes or changes required by a Regulatory Authority as may be agreed upon by the Parties. Changes, agreed to between the Parties, for the benefit of Cardinal Health, shall be at the expense of Cardinal Health. If there is a conflict between the terms of this Agreement and the terms of the Specifications, this Agreement shall control.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Technical Specifications 1. A procuring entity shall not prepare, adopt or apply any technical specification or prescribe any conformity assessment procedure with the purpose or effect of creating an unnecessary obstacle to trade between the Parties.

  • Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.

  • Modifications/Add-ons 6.3.1 Licensee shall comply with SAP’s registration procedure prior to making Modifications or Add-ons. All Modifications and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. All Add-ons developed by SAP (either independently or jointly with Licensee) and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. Licensee agrees to execute those documents reasonably necessary to secure SAP’s rights in the foregoing Modifications and Add-ons. All Add-ons developed by or on behalf of Licensee without SAP’s participation (“Licensee Add-on”), and all rights associated therewith, shall be the exclusive property of Licensee subject to SAP’s rights in and to the Software and SAP Materials; provided, Licensee shall not commercialize, market, distribute, license, sublicense, transfer, assign or otherwise alienate any such Licensee Add-ons. SAP retains the right to independently develop its own Modifications or Add-ons to the Software, and Licensee agrees not to take any action that would limit SAP’s sale, assignment, licensing or use of its own Software or Modifications or Add-ons thereto.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Software Modifications Company may request that BNYM, at Company’s expense, develop modifications to the software constituting a part of the Licensed System that BNYM generally makes available to customers for modification (“Software”) that are required to adapt the Software for Company’s unique business requirements. Such requests, containing the material features and functionalities of all such modifications in reasonable detail, will be submitted by Company in writing to BNYM in accordance with the applicable, commercially reasonable procedures maintained by BNYM at the time of the request. Company shall be solely responsible for preparing, reviewing and verifying the accuracy and completeness of the business specifications and requirements relied upon by BNYM to estimate, design and develop such modifications to the Software. BNYM shall have no obligation to develop modifications to the Licensed System requested by Company, but may in its discretion agree to develop requested modifications which it, in its sole discretion, reasonably determines it can accomplish with existing resources or with readily obtainable resources without disruption of normal business operations provided Company agrees at such time in writing to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification. BNYM shall be obligated to develop modifications under this Section 2.16 only upon the execution of and in accordance with a writing containing, to BNYM’s reasonable satisfaction, all necessary business and technical terms, specifications and requirements for the modification as determined by BNYM in its sole judgment (“Customization Order”) and Company’s agreement to pay all costs and expenses, including out-of-pocket expenses, associated with the customized modification (“Customization Fee Agreement”). All modifications developed and incorporated into the Licensed System pursuant to a Customization Order are referred to herein as “Company Modifications”. BNYM may make Company Modifications available to all users of the Licensed System, including BNYM, at any time after implementation of the particular Company Modification and any entitlement of Company to reimbursement on account of such action must be contained in the Customization Fee Agreement.

  • Contract Modifications It is understood that changes are inherent in operations of the type covered by this contract. The number of changes, the scope of those changes, and the impact they have on the progress of the original operations cannot be defined at this time. The PURCHASER is notified that changes are anticipated and that there will be no compensation made to the PURCHASER directly related to the number of changes made. Each change will be evaluated for extension of contract time and increase or decrease in compensation based on its own merit. STATE reserves the right to make, at any time during the contract, such modifications as are necessary or desirable; provided such modifications shall not change the character of the operations to be done nor increase the cost, unless such operations or cost increase is approved in writing by PURCHASER. Any modifications so made shall not invalidate this contract nor release PURCHASER of obligations under the performance bond. PURCHASER agrees to do the modified operations as if it had been a part of the original contract. If any change under this section causes an increase or decrease in the PURCHASER's cost of, or the time required for the performance of any part of the operations, the PURCHASER must submit a written statement setting forth the nature and specific extent of the claim. Such claim shall include all time and cost impacts against the contract and be submitted as soon as possible, but no later than 30 days after receipt of any written notice of modification of the contract. If the PURCHASER discovers site conditions which differ materially from what was represented in the contract or from conditions that would normally be expected to exist and be inherent to the activities defined in the contract, the PURCHASER shall notify the STATE's Authorized Representative immediately and before the area has been disturbed. The STATE's Authorized Representative will investigate the area and make a determination as to whether or not the conditions differ materially from either the conditions stated in the contract or those which could reasonably be expected in execution of this particular contract. If it is determined that a differing site condition exists, any compensation or credit will be determined based on an analysis by STATE's Authorized Representative. If the PURCHASER does not concur with the decision of the STATE's Authorized Representative and/or believes that it is entitled to additional compensation, the PURCHASER may proceed to file a claim. Claims Review Process. All PURCHASER claims shall be referred to the STATE's Authorized Representative for review. All claims shall be made in writing to the STATE's Authorized Representative not more than ten days from the date of the occurrence of the event which gives rise to the claim or not more than ten days from the date that the PURCHASER knew or should have known of the problem. Unless the claim is made in accordance with these time requirements, it shall be waived. All claims shall be submitted in writing and shall include a detailed, factual statement of the basis of the claim, pertinent dates, contract provisions which support or allow the claim, reference to or copies of any documents which support the claim, the exact dollar value of the claim, and specific time extension requested for the claim. If the claim involves operations to be completed by subcontractors, the PURCHASER will analyze and evaluate the merits of the subcontractor's claim. PURCHASER shall forward the subcontractor's claim and PURCHASER's evaluation of such claim to STATE's Authorized Representative. The STATE's Authorized Representative will not consider direct claims from subcontractors, suppliers, manufacturers, or others not a party to this contract. The decision of the STATE shall be final and binding unless the PURCHASER requests mediation.

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