Mortality Functions Sample Clauses

Mortality Functions. As discussed previously, Canfor proposed that mortality functions implemented by Weyerhaeuser in its 2007 FMP also be used for Canfor’s 2012 FMP. ASRD has since approved implementation of Weyerhaeuser’s mortality functions for use in Canfor’s 2012 FMP.43 The deciduous mortality function was applied to NSYTs after adjustments for volume bias removal. The conifer mortality function was applied to NSYTs after adjustments for volume bias removal, as well as for the LT component volume reduction. Since yield groups 15 and 16 were based on a single combined NSYT, the conifer mortality termination age was computed as an average of these two yield groups combined. The result was a set of adjusted NSYTs that included all three adjustment factors applied incrementally: volume bias removal, LT reduction, and mortality. 43 ASRD approval received from Xxxxxxxx Nunifu, ASRD via email on January 16, 2012.
AutoNDA by SimpleDocs

Related to Mortality 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.

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

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

  • Money Market Fund Compliance Testing and Reporting Services Subject to the authorization and direction of the Trust and, in each case where appropriate, the review and comment by the Trust’s independent accountants and legal counsel, and in accordance with procedures that may be established from time to time between the Trust and the Administrator, the Administrator will:

  • Nondiscretionary Functions The Custodian shall attend to all nondiscretionary details in connection with the sale, exchange, substitution, purchase, transfer or other dealings with securities or other assets of each Portfolio held by the Custodian, except as otherwise directed from time to time pursuant to Proper Instructions.

  • Commercially Useful Function A prime consultant can credit expenditures to a DBE subconsultant toward DBE goals only if the DBE performs a Commercially Useful Function (CUF). A DBE performs a CUF when it is responsible for execution of the work of a contract and carries out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the DBE must also be responsible, with respect to materials and supplies on the contract, for negotiating price, determining quality and quantity, ordering the material, and installing (where applicable) and paying for the material itself that it uses on the project. To determine whether a DBE is performing a commercially useful function, the Department will evaluate the amount of work subcontracted, industry practices, whether the amount the firm is to be paid under the contract is commensurate with the work it is actually performing and the DBE credit claimed for its performance of the work, and other relevant factors. A DBE will not be considered to perform a commercially useful function if its role is limited to that of an extra participant in a transaction, contract, or project through which funds are passed in order to obtain the appearance of DBE participation. In determining whether a DBE is such an extra participant, the Department will examine similar transactions, particularly those in which DBEs do not participate. If a DBE does not perform or exercise responsibility for at least 30 percent of the total cost of its contract with its own work force, or if the DBE subcontracts a greater portion of the work of a contract than would be expected on the basis of normal industry practice for the type of work involved, the Department will presume that the DBE is not performing a commercially useful function. When a DBE is presumed not to be performing a commercially useful function as provided above, the DBE may present evidence to rebut this presumption. The Department will determine if the firm is performing a CUF given the type of work involved and normal industry practices. The Department will notify the consultant, in writing, if it determines that the consultant’s DBE subconsultant is not performing a CUF. The consultant will be notified within seven calendar days of the Department’s decision. Decisions on CUF may be appealed to the ADOT State Engineer. The appeal must be in writing and personally delivered or sent by certified mail, return receipt requested, to the State Engineer. The appeal must be received by the State Engineer no later than seven calendar days after the decision of XXXX. XXXX’s decision remains in place unless and until the State Engineer reverses or modifies BECO’s decision. ADOT State Engineer will promptly consider any appeals under this subsection and notify the consultant of ADOT’s State Engineer findings and decisions. Decisions on CUF matters are not administratively appealable to USDOT. The BECO may conduct project site visits on the contract to confirm that DBEs are performing a CUF. The consultant shall cooperate during the site visits and the BECO’s staff will make every effort not to disrupt work on the project.

  • 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

  • Performance of Government Functions Nothing contained in this contract shall be deemed or construed so as to in any way estop, limit, or impair the City from exercising or performing any regulatory, policing, legislative, governmental, or other powers or functions.

  • Function of Joint Health and Safety Committee All incidents involving aggression or violence shall be brought to the attention of the Joint Health and Safety Committee. The Employer agrees that the Joint Health and Safety Committee shall concern itself with all matters relating to violence to staff.

  • Market Fund Services BNY Mellon shall provide the following information in a mutually agreed upon electronic format to support the website disclosure requirements of the Funds, subject to BNY Mellon’s timely receipt of all necessary information related thereto that is not maintained on the BNY Mellon systems. The Funds acknowledge that BNY Mellon is not responsible for the Funds’ website, for any servicing on the Funds’ website, or for uploading, downloading or maintaining any information on or required to be on the Funds’ website. o Date. o Fund identifier. o Share class. o Market NAV (rounded to four (4) decimal places). o Daily liquid assets. o Weekly liquid assets. o Shareholder inflows and outflows. · Assist with the preparation and filing with the SEC of Form N-CR as requested by the Fund or Adviser. · BNY Mellon shall, or shall cause the Vendor, to: (i) prepare, on a monthly basis, Form N-MFP, subject to BNY Mellon’s timely receipt of all necessary information related thereto that is not maintained on the BNY Mellon systems; and (ii) file Form N-MFP with the SEC, on a monthly basis; and · Prepare and provide an electronic file of the portfolio holdings information required by Rule 2a-7(h)(10) to the Fund or, at the Fund’s written direction, to an identified third party (the deliverables for the above money market fund services collectively referred to as, the “Money Market Fund Services Reports”). · Neither BNY Mellon nor the Vendor, in connection with a particular Money Market Fund Services Report, will prepare, provide or generate any reports, forms or files not specifically agreed to by BNY Mellon in advance. · The applicable Fund acknowledges that it shall be responsible for the retention of any Money Market Fund Services Reports in accordance with Rule 2a-7 promulgated under the 1940 Act or any other applicable rule or regulation. · Unless mutually agreed in writing between BNY Mellon and a Fund, solely with respect to typesetting of the Money Market Fund Services Reports, BNY Mellon will use the same layout and format for every successive reporting period for the Money Market Fund Services Reports. At the request of a Fund and upon the mutual written agreement of BNY Mellon and the Fund as to the scope of any changes and additional compensation of BNY Mellon, BNY Mellon will, or will cause the Vendor to, customize Money Market Fund Services Reports from time to time.

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