Core Client Functions Sample Clauses

Core Client Functions 
AutoNDA by SimpleDocs

Related to Core Client Functions

  • MANAGEMENT FUNCTIONS 6.01 The Union acknowledges that it is the exclusive function of the Employer to:

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

  • Primary Function The primary function of the Program Manager is to provide strategic guidance and direction to the Project Team and to manage the Project on behalf of the Owner. Program Manager agrees that the services provided by the Program Manager are intended to coordinate and complement the activities of the Project Team, but not to diminish, alter or substitute for any of the services, authority, obligations or responsibilities being provided by the Design Professional and CM/GC under their respective contracts. Nothing herein shall be deemed to impose upon the Program Manager any responsibilities to provide any services constituting the practice of architecture, engineering, or any related design profession, or to provide any services constituting construction or means and methods of construction. The Program Manager should seek to exercise its authority through sound principles of leadership and persuasion to achieve effective coordination of the design and construction of the Project. The Program Manager should use its authority to direct the activities of the Design Professional and CM/GC within the requirements of their respective contracts; or in unusual or ambiguous situations, after consultation with the Owner and under the specific direction of the Owner.

  • Commercially Useful Function a Small Local Business Enterprise or Emerging Local Business Enterprise (SLBE/ELBE) performs a commercially useful function when it is responsible for execution of the work and is carrying out its responsibilities by actually performing, managing, and supervising the work involved. To perform a commercially useful function, the SLBE/ELBE shall also be responsible, with respect to materials and supplies used on the contract, for negotiating price, determining quantity and quality, ordering the material, and installing (where applicable) and paying for the material itself. To determine whether an SLBE/XXXX is performing a commercially useful function, an evaluation will be performed of the amount of work subcontracted, normal industry practices, whether the amount the SLBE/ELBE firm is to be paid under the contract is commensurate with the work it is actually performing and the SLBE/ELBE credit claimed for its performance of the work, and other relevant factors. Specifically, a SLBE/ELBE does not 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 meaningful and useful SLBE/ELBE participation, when in similar transactions in which SLBE-ELBE firms do not participate, there is no such role performed. Disadvantaged Business Enterprise (DBE): a certified business that is (1) at least fifty-one (51%) owned by socially and economically Disadvantaged Individuals, or, in the case of a publicly owned business at least fifty-one percent (51%) of the stock is owned by one or more socially and economically Disadvantaged Individuals; and (2) whose daily business operations are managed and directed by one or more socially and economically disadvantaged owners. Disadvantaged Individuals include Black Americans, Hispanic Americans, Asian Americans, and other minorities, or individual found to be disadvantaged by the Small Business Administration pursuant to Section 8 of the Small Business Reauthorization Act. Disabled Veteran Business Enterprise (DVBE): a certified business that is (1) at least fifty-one percent (51%) owned by one or more disabled veterans; and (2) business operations must be managed and controlled by one or more disabled veterans. Disabled Veteran is a veteran of the U.S. military, naval, or air service; the veteran must have a service-connected disability or at least 10% or more; and the veteran must reside in California. The firm shall be certified by the State of California’s Department of General Services, Office of Small and Minority Business. Emerging Business Enterprise (EBE): a business whose gross annual receipts do not exceed the amount set by the City Manager, and which meets all other criteria set forth in the regulations implementing the City’s Small and Local Business Preference Program. The City Manager shall review the threshold amount for EBEs on an annual basis, and adjust as necessary to reflect changes in the marketplace. Emerging Local Business Enterprise (ELBE): a Local Business Enterprise that is also an Emerging Business Enterprise. Local Business Enterprise (LBE): a firm having a Principal Place of Business and a Significant Employment Presence in San Diego County, California, that has been in operation for 12 consecutive months and a valid business tax certificate. This definition is subsumed within the definition of Small Local Business Enterprise. Minority Business Enterprise (MBE): a certified business that is (1) at least fifty-one percent (51%) owned by one or more minority individuals, or, in the case of a publicly owned business at least fifty- one percent (51%) of the stock is owned by one or more minority individuals; and (2) whose daily business operations are managed and directed by one or more minorities owners. Minorities include the groups with the following ethnic origins: African, Asian Pacific, Asian Subcontinent, Hispanic, Native Alaskan, Native American, and Native Hawaiian. Other Business Enterprise (OBE): any business which does not otherwise qualify as Minority, Woman, Disadvantaged or Disabled Veteran Business Enterprise. Principal Place of Business: a location wherein a firm maintains a physical office and through which it obtains no less than fifty percent (50%) of its overall customers or sales dollars. Significant Employee Presence: no less than twenty-five percent (25%) of a business’s total number of employees are domiciled in San Diego County. Small Business Enterprise (SBE): a business whose gross annual receipts do not exceed the amount set by the City Manager, and that meets all other criteria set forth in regulations implementing the City’s Small and Local Business Preference Program. The City Manager shall review the threshold amount for SBEs on an annual basis, and adjust as necessary to reflect changes in the marketplace. A business certified as a DVBE by the State of California, and that has provided proof of such certification to the City Manager, shall be deemed to be an SBE. Small Local Business Enterprise (SLBE): a Local Business Enterprise that is also a Small Business Enterprise. Women Business Enterprise (WBE): a certified business that is (1) at least fifty-one percent (51 %) owned by a woman or women, or, in the case of a publicly owned business at least fifty-one percent (51%) of the stock is owned by one or more women; and (2) whose daily business operations are managed and directed by one or more women owners.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation as Local Traffic under the Interconnection Attachment.

  • 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: Field # Field Name Description 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

  • Hosted Services We shall use commercially reasonable efforts to make the Hosted Services you have purchased available 24 hours a day, 7 days a week, except for: (a) planned downtime under our direct control (of which we shall give at least 8 hours notice via the Hosted Services and which we shall schedule to the extent practicable during the weekend hours from 6:00 p.m. Pacific time Friday to 3:00 a.m. Pacific time Monday), (b) to the extent we are notified by third party service providers of planned downtime (of which we shall provide such notice to you via the Hosted services as soon we can reasonably do so), or (c) any unavailability caused by circumstances beyond our reasonable control, including, without limitation, acts of God, acts of government, flood, fire, earthquakes, civil unrest, acts of terror, strikes or other labor problems, internet service or third party hosting provider failures or delays ("Force Majeure"). Hosted Services are provided in accordance with applicable laws and government regulations.

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

  • Future Functionality You agree that Your purchases are not contingent on the delivery of any future functionality or features, or dependent on any oral or written public comments made by Us regarding future functionality or features.

  • THIRD-PARTY CONTENT, SERVICES AND WEBSITES 10.1 The Services may enable You to link to, transfer Your Content or Third Party Content to, or otherwise access, third parties’ websites, platforms, content, products, services, and information (“Third Party Services”). Oracle does not control and is not responsible for Third Party Services. You are solely responsible for complying with the terms of access and use of Third Party Services, and if Oracle accesses or uses any Third Party Services on Your behalf to facilitate performance of the Services, You are solely responsible for ensuring that such access and use, including through passwords, credentials or tokens issued or otherwise made available to You, is authorized by the terms of access and use for such services. If You transfer or cause the transfer of Your Content or Third Party Content from the Services to a Third Party Service or other location, that transfer constitutes a distribution by You and not by Oracle.

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