Tagging Attachments Sample Clauses

Tagging Attachments. For an Attachment placed after this Agreement's effective date, a party will place an identification tag on the pole or Attachment. The parties acknowledge that an Attachment placed prior to this Agreement's effective date may not have an identifying pole tag. But if a party performs work on a joint-use pole or Attachment, it will tag the pole or Attachment. If Licensee removes all of its Attachments from a joint-use pole, it also will remove all of its identifying tags.
AutoNDA by SimpleDocs

Related to Tagging Attachments

  • Requested                           Attachments Pricing Form 1 (Part 1) 230104 Pricing Form 1 (Part 1).xlsx Pricing Form 2 (Part 1) 230104 Pricing Form 2 (Part 1).xlsx

  • Attachments This contract consists of 7 pages including the following attachments which are incorporated herein: Attachment A - Statement of Work Attachment B - Payment Provisions Attachment C – “Standard State Provisions for Contracts and Grants” a preprinted form (revision date 12/15/2017)

  • Alterations and Attachments Student and Parent may not make any alterations in or add attachments, hardware, or software to the mobile device computer absent express permission from M-DCPS, which permission is at the sole option of M-DCPS.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • Attachment  C_ CONTRACT AFFIRMATIONS For purposes of these Contract Affirmations, HHS includes both the Health and Human Services Commission (HHSC) and the Department of State Health Services (DSHS). System Agency refers to HHSC, DSHS, or both, that will be a party to this Contract. These Contract Affirmations apply to all Contractors and Grantees (referred to as “Contractor”) regardless of their business form (e.g., individual, partnership, corporation). By entering into this Contract, Contractor affirms, without exception, understands, and agrees to comply with the following items through the life of the Contract:

  • LIST OF ATTACHMENTS Attachment 1: Acronyms and Abbreviations Attachment 2: Cost/Price – Government Site (Contractor’s Cost/Price- Government Site – Contractor’s Proposal dated 11/17/06 is incorporated herein by reference.) Attachment 3: Cost/Price – Contractor Site (Contractor’s Cost/Price-Contractor Site – Contractor’s Proposal dated 11/17/07 is incorporated herein by reference.) Attachment 4: Labor Category Descriptions Attachment 5: Federal Enterprise Architecture/Department. of Defense Enterprise Architecture Overview Attachment 6: Past Performance Tables (Not Applicable) ACO Administrative Contracting Officer ADR Alternative Dispute Resolution ATM Asynchronous Transfer Mode CAF Contract Access Fee CAS Cost Accounting Standards CAV Contractor Assisted Visits CCR Central Contractor Registration CDA Contract Disputes Act of 1978 CFE Contractor Furnished Equipment CLIN Contract Line Item Number CO Contracting Officer CONUS Continental United States COR Contracting Officer’s Representative COTR Contracting Officer’s Technical Representative CPS Contractor Performance System CRM Customer Relationship Management CSO Cognizant Security Office D&F Determination and Findings DBA Xxxxx Xxxxx Act DCAA Defense Contract Audit Agency DCMA Defense Contract Management Agency DOL Department of Labor DPA Delegation of Procurement Authority DSL Digital Subscriber Line DUNS Data Universal Numbering System EAI Enterprise Application Integration EDI Electronic Data Interchange EEO Equal Employment Opportunity EFT Electronic Funds Transfer eSRS Electronic Subcontracting Reporting System EVMS Earned Value Management System FEA Federal Enterprise Architecture; also Department of Defense Enterprise Architecture (DoDEA). FAS Federal Acquisition Service FOIA Freedom of Information Act FPDS-NG Federal Procurement Data System-Next Generation FTP File Transfer Protocol FTR Federal Travel Regulations G&A General and Administrative GFE Government Furnished Equipment GFM Government Furnished Material GFP Government Furnished Property GPS Global Positioning Systems GSA General Services Administration GWAC Government Wide Acquisition Contract HCA Head of Contracting Activity HTTP HyperText Transfer Protocol ITMRA Information Technology Management Reform Act J&A Justification and Approval JTR Joint Travel Regulations L-H Labor Hour MA/IDIQ Multiple Award Indefinite-Delivery Indefinite-Quantity MOM Messaging-Oriented Middleware MOU Memorandum of Understanding MPIN Marketing Partner Identification Number NAICS North American Industrial Classification System OCI Organizational Conflict of Interest OCO Ordering Contracting Officer OCONUS Outside of Continental United States OCR Optical Character Recognition ODBC Open DataBase Connectivity ODC Other Direct Cost OLAP OnLine Analytical Processing OMB Office of Management and Budget ORB Object Request Broker ORCA Online Representations and Certifications Application PBSOW Performance-Based Statement of Work PCO Procuring Contracting Officer PMO Program Management Office POC Point of Contact PPIRS Past Performance Information Retrieval System PWS Performance Work Statement QASP Quality Assurance Surveillance Plan RADIUS Remote Authentication Dial-In User Service RDF Resource Description Framework RFP Request for Proposal SCA Service Contract Act SMTP Simple Mail Transfer Protocol SOAP Simple Object Access Protocol SOO Statement of Objectives SOW Statement of Work SRM Service Component Reference Model SQL Structured Query Language T&M Time & Materials TOR Task Order Request TRM Technical Reference Model UDDI Universal Description, Discovery and Integration VPN Virtual Private Network VSC Vendor Support Center WSDL Web Services Description Language XML EXtensible Markup Language DD254 Contract Security Classification Specification GSA 527 Contractor’s Qualifications and Financial Information Many functional labor categories below (marked with “#”) are further subdivided by knowledge/skill level. Definitions of these knowledge/skill levels are shown in this chart: Entry-Level Applies fundamental concepts, processes, practices, and procedures on technical assignments. Performs work that requires practical experience and training. Work is performed under supervision. Journeyman Possesses and applies expertise on multiple complex work assignments. Assignments may be broad in nature, requiring originality and innovation in determining how to accomplish tasks. Operates with appreciable latitude in developing methodology and presenting solutions to problems. Contributes to deliverables and performance metrics where applicable. Senior Possesses and applies a comprehensive knowledge across key tasks and high impact assignments. Plans and leads major technology assignments. Evaluates performance results and recommends major changes affecting short-term project growth and success. Functions as a technical expert across multiple project assignments. May supervise others. Master Provides technical/management leadership on major tasks or technology assignments. Establishes goals and plans that meet project objectives. Has domain and expert technical knowledge. Directs and controls activities for a client, having overall responsibility for financial management, methods, and staffing to ensure that technical requirements are met. Interactions involve client negotiations and interfacing with senior management. Decision making and domain knowledge may have a critical impact on overall project implementation. May supervise others. The “G” in the labor identification (ID) numbers below indicate Government-Site Work (see Section J, Attachment 2). The “C” in the labor ID numbers below indicate Contractor-Site Work (see Section J, Attachment 3).

  • DELIVERY SCHEDULES In accordance with the "Non-State Agencies Participation in Centralized Contracts” and “Extension of Use” clauses herein, this Contract is extended to local governments, political subdivisions and others authorized by law as well as State agencies. The Delivery Schedules (based on Requirement Letter RL182) are available as a guide to indicate proposed delivery points and estimated annual requirements. Delivery Schedules may be revised or clarified as necessary. Any specific questions regarding the site conditions should be directed to the end-user at the telephone number shown on the Delivery Schedule. The Delivery Schedules are available upon request. Contractors shall be obligated to deliver under the Contract to any State agency which places a purchase order under the Contract, whether or not such delivery location is identified in the Delivery Schedules. Any political subdivision or other non-State entity which has not filed a requirement with OGS as of the date of the bid opening shall be eligible to receive deliveries at Contractor's option only, upon placement of a valid purchase order to the Contractor's address as indicated in the award. Contracts created by OGS in response to receipt of Filed Requirements are considered to be binding. At Contractor's request, Contractor will be advised in writing regarding political subdivisions or other Non-State entities which have filed on a timely basis but do not appear on the Delivery Schedule. Where “Standby” is indicated in the Delivery Schedule, this reflects those facilities which normally use a fuel supply (i.e. natural gas) other than fuel oil and will only use fuel oil when alternate fuel is unavailable.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Exhibits and Attachments The following exhibits and attachments are included hereto and incorporated by reference herein: Exhibit A—Services Exhibit B—Payments and rates Attachment I—§504 Compliance

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

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