Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx.
(2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this clause
(i) Within one business day from the date of such identification or notification: the contract number; the order number(s), if applicable; supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended.
(ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this clause: any further available information about mitigation actions undertaken or recommended. In addition, the Contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.
Scope of Services The specific scope of work for each job shall be determined in advance and in writing between TIPS Member, Member’s design professionals and Vendor. It is permitted for the TIPS Member to provide a general scope description, but the awarded vendor should provide a written scope of work, and if applicable, according to the TIPS Member’s design Professional as part of the proposal. Once the scope of the job is agreed to, the TIPS Member will issue a PO and/or an Agreement or Contract with the Job Order Contract Proposal referenced or as an attachment along with bond and any other special provisions agreed by the TIPS Member. If special terms and conditions other than those covered within this solicitation and awarded Agreements are required, they will be attached to the PO and/or an Agreement or Contract and shall take precedence over those in this base TIPS Vendor Agreement.
Reporting Requirements The Company, during the period when the Prospectus is required to be delivered under the 1933 Act or the 1934 Act, will file all documents required to be filed with the Commission pursuant to the 1934 Act within the time periods required by the 1934 Act and the 1934 Act Regulations.
Payment Terms DXC agrees to pay Supplier the undisputed amount of an invoice within ninety (90) days after the receipt of a valid, complete and properly documented invoice. Any prompt payment discount will be calculated from the date a conforming invoice is received by DXC. Payment will be in U.S. currency unless otherwise stated. Payment will not constitute acceptance of Products and/or Services or impair DXC’s right to inspect. Acceptance shall be when DXC deems the Products and/or Services to meet its specified criteria (“Acceptance”). DXC, at its option, and without prior notice to Supplier, shall have the right to set off or deduct from any Supplier’s invoice, any credits, refunds or claims of any kind due DXC.
Subcontractors The Contractor will not subcontract any work under the Contract without prior written consent of the Department. The Contractor is fully responsible for satisfactory completion of all its subcontracted work. The Department supports diversity in its procurements and contracts, and requests that the Contractor offer subcontracting opportunities to certified woman-, veteran-, and minority-owned small businesses. The Contractor may contact the OSD at xxxxxxx@xxx.xxxxxxxxx.xxx for information on certified small business enterprises available for subcontracting opportunities.
Subcontracting 6.1 The Grantee is responsible for the performance of its obligations under this Agreement, including in relation to any tasks undertaken by subcontractors.
6.2 The Grantee agrees to make available to the Commonwealth the details of any of its subcontractors engaged to perform any tasks in relation to this Agreement upon request.
Representations and Warranties Borrower represents and warrants as follows:
GRIEVANCE PROCEDURE 36.01 It is agreed that neither the Employer, its representatives and supervisors, nor the Union, will attempt to bring about the settlement of any contractual issue by means other than the grievance procedure.
36.02 A grievance is a dispute or difference between the Employer and the employee covered by this Bargaining Agreement, concerning the interpretation and/or application of this contract. The following procedures shall apply to the administration of all grievances filed under this Agreement, and shall be presented in accordance with the steps outlined below:
Step 1 An employee who believes he may have a grievance shall notify his immediate supervisor(s) of the possible grievance within seven (7) calendar days of the occurrence of the facts giving rise to the grievance. This notification shall be in writing, and shall state the aggrieved employee's name, position, date of alleged grievance, and the portion of the Agreement in question giving rise to this grievance. The presentation of this grievance shall be in the employee's own hand. The supervisor will schedule an informal meeting within seven (7) calendar days after the receipt of the grievance, with the employee, and his associate if requested by the employee, to discuss the issues in dispute with the objective of resolving the matter informally, with a written reply of the meeting to be given to the employee, the Union xxxxxxx, and the Employer.
Step 2 If no satisfactory settlement is reached at the step 1, the grievance may be appealed to the Division Head, or other Employer designate, and the Local Union Staff Representative within seven (7) calendar days after receiving the reply of the step 1. The appeal shall restate the grievance, and shall include proposed remedy sought by the aggrieved party. A step 2 answer, reduced to writing, will be given to the aggrieved party within seven (7) calendar days of receiving the written appeal.
Step 3 If no satisfactory answer is reached at step 2, the grievance may be appealed to the City Manager and the Union Staff Representative or their designated alternates within seven (7) calendar days after the reply is rendered in step 2. The appeal shall be reduced to writing, shall contain the original grievance and all subsequent answers/decisions, and be in the employee's own hand. A meeting will be held within 14 calendar days after the receipt of the Step 2 reply. A written reply will be issued as a result of this meeting within fourteen
NOTE For Community-‐Based TLDs Only] Obligations of Registry Operator to TLD Community. Registry Operator shall establish registration policies in conformity with the application submitted with respect to the TLD for: (i) naming conventions within the TLD, (ii) requirements for registration by members of the TLD community, and (iii) use of registered domain names in conformity with the stated purpose of the community-‐based TLD. Registry Operator shall operate the TLD in a manner that allows the TLD community to discuss and participate in the development and modification of policies and practices for the TLD. Registry Operator shall establish procedures for the enforcement of registration policies for the TLD, and resolution of disputes concerning compliance with TLD registration policies, and shall enforce such registration policies. Registry Operator agrees to implement and be bound by the Registry Restrictions Dispute Resolution Procedure as set forth at [insert applicable URL] with respect to disputes arising pursuant to this Section 2.19. Registry Operator shall implement and comply with the community registration policies set forth on Specification 12 attached hereto.]
Termination for Convenience TIPS may, by written notice to Vendor, terminate this Agreement for convenience, in whole or in part, at any time by giving thirty (30) days’ written notice to Vendor of such termination, and specifying the effective date thereof.
