Objectives / Policy Statement Sample Clauses

Objectives / Policy Statement. The TJPA hereby establishes a Small Business Enterprise (SBE) Program. It is the policy of the TJPA to ensure that SBEs, as defined above, have an equal opportunity to receive and participate in TJPA contracts. It is also the TJPA’s intention to: • create a level playing field on which SBEs can compete fairly for TJPA contracts; • remove barriers to SBE participation in the bidding, award and administration of TJPA contracts; • assist SBEs to develop and compete successfully outside of the Program • ensure that only SBEs meeting the eligibility requirements are allowed to participate as SBEs • identify business enterprises that are qualified as SBEs and are qualified to provide TJPA with required materials, equipment, supplies and services; and to develop a good rapport with the owners, managers and sales representatives of those enterprises The Contract Compliance Manager has been designated the SBE Liaison Officer (SBELO). In that capacity, the Contract Compliance Manager is responsible for implementing all aspects of the SBE Program. Implementation of the SBE Program is accorded the same priority as compliance with the TJPA DBE Program. The Contract Compliance Manager has disseminated this policy statement to the TJPA Board of Directors and all components of the TJPA’s organization. The TJPA has made the draft SBE Program and final SBE program available to SBE and non-SBE business communities that perform work for it by publishing an announcement of availability in general circulation, woman/minority-focused, and trade association publications.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Objectives / Policy Statement. (26.1, 26.23) The City of San Antonio Aviation Department (hereafter known as the City) has established a Disadvantaged Business Enterprise (DBE) Program in accordance with regulations of the U.S. Department of Transportation (DOT), 49 CFR Part 26. The City has received Federal financial assistance from the Department of Transportation, and as a condition of receiving this assistance, the City has signed an assurance that it will comply with 49 CFR Part 26. It is the policy of the City to ensure that DBEs, as defined in Part 26, have an equal opportunity to receive and participate in DOT-assisted contracts. It is also our policy:
Sample 1
Objectives / Policy Statement. The City of Inglewood and the Los Angeles Metropolitan Transportation Authority (LA Metro) have entered into a Joint Powers Agreement (JPA), a single purpose governmental entity tasked with owning, managing, and overseeing the design, construction, financing, operation, and maintenance of the Inglewood Transit Connector (ITC) Project. The Inglewood Transit Connector Joint Powers Authority (Owner), and its Administrator, the City of Inglewood, which is leading procurement efforts for a Design-Build-Finance-Operate-and- Maintenance Contractor, has established a Disadvantaged Business Enterprise (DBE) Program in accordance with regulations of the U.S. Department of Transportation (DOT), 49 Code of Federal Regulation (CFR) Part 26 (DBE Program). As a recipient of Federal financial assistance from the DOT and as a condition of receiving this assistance, Owner has signed an assurance that it will comply with 49 CFR Part 26. It is Owner’s policy to provide equal opportunity for (DBE) firms, as defined in 49 CFR Part 26, which will enable the receipt and participation in DOT–assisted contracts. It is also the Owner’s policy:
Sample 1
Objectives / Policy Statement. The City of Inglewood and the Los Angeles Metropolitan Transportation Authority (LA Metro) have entered into a Joint Powers Agreement (JPA), a single purpose governmental entity tasked with owning, managing, and overseeing the design, construction, financing, operation, and maintenance of the Inglewood Transit Connector (ITC) Project. The (ITC Joint Powers Authority (Owner), and its Administrator, the City of Inglewood, which is leading procurement efforts for a Design-Build-Finance-Operate-and-Maintenance Contractor, has established a Disadvantaged Business Enterprise (DBE) Program in accordance with regulations of the U.S. Department of Transportation (DOT), 49 Code of Federal Regulation (CFR) Part 26. As a recipient of Federal financial assistance from the DOT and as a condition of receiving this assistance, Owner has signed an assurance that it will comply with 49 CFR Part 26. It is Owner’s policy to provide equal opportunity for Disadvantage Business Enterprises (DBE) firms, as defined in 49 CFR Part 26, which will enable the receipt and participation in DOT–assisted contracts. It is also the Owner’s policy:
Sample 1
Objectives / Policy Statement. 1.1 The internet provides an opportunity to enhance students’ learning experiences by providing access to vast amounts of information across the globe. Online communication links students to provide a collaborative learning environment and is intended to assist with learning outcomes. Today’s students are exposed to online communication tools and the internet in their community. They have the right to expect secure access to these services as part of their learning experiences with the NSW Department of Education and Communities.
Sample 1

Related to Objectives / Policy Statement

  • Policy Statement The RSU Award grant the Company is making under the Plan is unilateral and discretionary and, therefore, the Company reserves the absolute right to amend it and discontinue it at any time without any liability. The Company, with registered offices at Xxx Xxxxxx Xxxxxxxxx, #00-00, Xxxxxxxxx 000000, is solely responsible for the administration of the Plan, and participation in the Plan and the grant of the RSU Award do not, in any way, establish an employment relationship between the Participant and the Company since he or she is participating in the Plan on a wholly commercial basis and the sole employer is Availmed Servicios S.A. de C.V., Grupo Flextronics S.A. de C.V., Flextronics Servicios Guadalajara S.A. de C.V., Flextronics Servicios Mexico S. de X.X. de C.V. and Flextronics Aguascalientes Servicios S.A. de C.V., nor does it establish any rights between the Participant and the Employer. Plan Document Acknowledgment. By accepting the RSU Award, the Participant acknowledges that he or she has received copies of the Plan, has reviewed the Plan and the Agreement in their entirety, and fully understands and accepts all provisions of the Plan and the Agreement. In addition, the Participant further acknowledges that he or she has read and specifically and expressly approves the terms and conditions in the Nature of Grant section of the Agreement, in which the following is clearly described and established: (i) participation in the Plan does not constitute an acquired right; (ii) the Plan and participation in the Plan is offered by the Company on a wholly discretionary basis; (iii) participation in the Plan is voluntary; and (iv) the Company and any Parent, Subsidiary or Affiliates are not responsible for any decrease in the value of the Shares acquired upon vesting of the RSU Award. Finally, the Participant hereby declares that he or she does not reserve any action or right to bring any claim against the Company for any compensation or damages as a result of his or her participation in the Plan and therefore grants a full and broad release to the Employer, the Company and any Parent, Subsidiary or Affiliates with respect to any claim that may arise under the Plan.

  • SPAM POLICY You are strictly prohibited from using the Website or any of the Company's Services for illegal spam activities, including gathering email addresses and personal information from others or sending any mass commercial emails.

  • CONTRACT SALES ACTIVITY REPORT Each calendar quarter, Vendor must provide a contract sales activity report (Report) to the Sourcewell Contract Administrator assigned to this Contract. A Report must be provided regardless of the number or amount of sales during that quarter (i.e., if there are no sales, Vendor must submit a report indicating no sales were made). The Report must contain the following fields: • Customer Name (e.g., City of Staples Highway Department); • Customer Physical Street Address; • Customer City; • Customer State/Province; • Customer Zip Code; • Customer Contact Name; • Customer Contact Email Address; • Customer Contact Telephone Number; • Sourcewell Assigned Entity/Participating Entity Number; • Item Purchased Description; • Item Purchased Price; • Sourcewell Administrative Fee Applied; and • Date Purchase was invoiced/sale was recognized as revenue by Vendor.

  • 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

  • Project Objectives The Program consists of the projects described in Annex I (each a “Project” and collectively, the “Projects”). The objective of each of the Projects (each a “Project Objective” and collectively, the “Project Objectives”) is to:

  • Standards of Conduct Whenever the Member is required or permitted to make a decision, take or approve an action, or omit to do any of the foregoing, then the Member shall be entitled to consider only such interests and factors, including its own, as it desires, and shall have no duty or obligation to consider any other interests or factors whatsoever. To the extent that the Member has, at law or in equity, duties (including, without limitation, fiduciary duties) to the Company or other person bound by the terms of this Agreement, the Member acting in accordance with the Agreement shall not be liable to the Company or any such other person for its good faith reliance on the provisions of this Agreement. The provisions of this Agreement, to the extent that they restrict the duties of the Member otherwise existing at law or in equity, replace such other duties to the greatest extent permitted under applicable law.

  • DIRECTORS’ RESPONSIBILITY STATEMENT The Directors collectively and individually accept full responsibility for the accuracy of the information given in this announcement and confirm after making all reasonable enquiries that, to the best of their knowledge and belief, this announcement constitutes full and true disclosure of all material facts about the Proposed Acquisition, the Company and its subsidiaries, and the Directors are not aware of any facts the omission of which would make any statement in this announcement misleading. Where information in this announcement has been extracted from published or otherwise publicly available sources or obtained from a named source, the sole responsibility of the Directors has been to ensure that such information has been accurately and correctly extracted from those sources and/or reproduced in this announcement in its proper form and context.

  • BUSINESS ETHICS EXPECTATION 13.1 During the course of pursuing contracts with Owner and while performing contract work in accordance with this Agreement, Architect/Engineer agrees to maintain business ethics standards aimed at avoiding any impropriety or conflict of interest which could be construed to have an adverse impact on the Owner’s best interests.

  • Consensus Policies (i) At all times during the term of this Agreement and subject to the terms hereof, Registry Operator will fully comply with and implement all Consensus Policies found at xxxx://xxx.xxxxx.xxx/general/consensus- policies.htm, as of the Effective Date and as may in the future be developed and adopted in accordance with ICANN’s Bylaws and as set forth below.

  • Overpayment Policies and Procedures Within 90 days after the Effective Date, Xxxxx shall develop and implement written policies and procedures regarding the identification, quantification and repayment of Overpayments received from any Federal health care program.

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