Header Sample Clauses

Header. Optional: You may enter a description in the Document Name or Document Description fields to help you identify this receivable. The Document Description will be displayed in various inquires.
Sample 1
AutoNDA by SimpleDocs
Header. The header to this Agreement is hereby deleted and replaced in its entirety with the following: THIS AGREEMENT is made effective as of the last date of execution set forth below and is between NephroGenex, Inc., hereinafter referred to as COMPANY, a corporation of the State of Delaware and having offices at 200 Xxxxxxxx Xxxxx, Xxxx, Xxxxx Xxxxxxxx 00000, U.S.A., and the University of Kansas Medical Center Research Institute, Inc., hereinafter referred to as RESEARCH INSTITUTE, located at 39th and Rxxxxxx Xxxx., Xxxxxx Xxxx, Xxxxxx 00000, X.X.X.
Sample 1
Header. The header on the first page of the Security Agreement is hereby amended and restated in its entirety as follows: “REFERENCE IS MADE TO (A) THAT CERTAIN AMENDED AND RESTATED INTERCREDITOR AND SUBORDINATION AGREEMENT, DATED AS OF JULY 20, 2023 (AS AMENDED, RESTATED, AMENDED AND RESTATED, SUPPLEMENTED OR OTHERWISE MODIFIED AND IN EFFECT FROM TIME TO TIME, THE “SENIOR INTERCREDITOR AGREEMENT”), AMONG U.S. BANK TRUST COMPANY, NATIONAL ASSOCIATION, AS COLLATERAL AGENT FOR THE SECURED PARTIES REFERRED TO THEREIN (BY REFERENCE TO THE DEFINITION IN THE ORIGINAL SENIOR NIA AS DEFINED THEREIN); APPGATE FUNDING, LLC, AS ORIGINAL SECOND LIEN AGENT, SIS HOLDINGS, L.P., AS ORIGINAL THIRD LIEN AGENT; APPGATE, INC., A DELAWARE CORPORATION; AND CERTAIN SUBSIDIARIES PARTY THERETO, AND (B) THAT CERTAIN INTERCREDITOR AND SUBORDINATION AGREEMENT, DATED AS OF JULY 20, 2023 (AS AMENDED, RESTATED, AMENDED AND RESTATED, SUPPLEMENTED OR OTHERWISE MODIFIED AND IN EFFECT FROM TIME TO TIME, THE “JUNIOR INTERCREDITOR AGREEMENT” AND, COLLECTIVELY WITH THE SENIOR INTERCREDITOR AGREEMENT, THE “INTERCREDITOR AGREEMENT”), AMONG APPGATE FUNDING, LLC, AS ORIGINAL SENIOR AGENT, SIS HOLDINGS, L.P., AS ORIGINAL SUBORDINATED AGENT; APPGATE, INC., A DELAWARE CORPORATION; AND CERTAIN SUBSIDIARIES PARTY THERETO. NOTWITHSTANDING ANY OTHER PROVISION CONTAINED HEREIN, THE LIENS CREATED HEREBY AND THE RIGHTS, REMEDIES, DUTIES AND OBLIGATIONS PROVIDED FOR HEREIN ARE SUBJECT IN ALL RESPECTS TO THE PROVISIONS OF THE INTERCREDITOR AGREEMENT. IN THE EVENT OF ANY CONFLICT OR INCONSISTENCY BETWEEN THE PROVISIONS OF THIS AGREEMENT AND THE INTERCREDITOR AGREEMENT, THE PROVISIONS OF THE INTERCREDITOR AGREEMENT SHALL CONTROL. IN THE EVENT OF ANY CONFLICT OR INCONSISTENCY BETWEEN THE PROVISIONS OF THE SENIOR INTERCREDITOR AGREEMENT AND THE JUNIOR INTERCREDITOR AGREEMENT, THE PROVISIONS OF THE SENIOR INTERCREDITOR AGREEMENT SHALL CONTROL.” 2. Section 1.02 (Additional Definitions).
Sample 1
Header. The header of the MCS community Building Platform is visible from all areas of the website and provides the following functionality:  Direct access to the login functionality of the website  A link to the social network group LinkedIn  Search functionality The header is depicted in Figure 11.
Sample 1
Header. Articulation Agreement/Memorandum of Understanding Full titles of the partnering institutions Branding logos of the partnering institutions
Sample 1
Header. The METS header element <metsHdr> describes metadata about the creator, contact persons, etc. of the submission information package as seen in Figure 5. 23 This element is not used for representation METS XML files. These are the elements that give information about the submission of the SIP in the METS header element. Date and time*24 Time of creation of package Date and time for creation of the package must be described according to the XML-standard ("YYYY-MM- DDThh:mm:ssZ").25 This timestamp states when the whole package and the package file was created.26 Example: "2012-04-26T12:45:00+01:00" 1 <metsHdr: CREATEDATE=”[Da te and time]”> Status* Package status A way of indicating the status of the package for making it easier to know how to handle the package (allows package status specific processing or rendering) if for example an identical package is being submitted replacing the previous one sent. Example: ”NEW” Example: ”TEST” Example: ”REPLEACEMENT” 0..1 <metsHdr: RECORDSTATUS=”[ Status]”> 24 Header elements marked with an asterisk * represent elements which are required only for the root METS.xml. All other elements can be recorded in the representation METS.xml files.
Sample 1

Related to Header

  • Headers Headings and captions used in the Agreement are for reference purposes only and will not have any effect on the interpretation of the Agreement.

  • Layout a. Estimate and quantity sheet (1) List of all bid items (2) Bid item quantities (3) Specification item number (4) Paid item description and unit of measure b. Basis of estimate sheet (list of materials) c. General notes and specification data. d. Condition diagram (1) Highway and intersection design features (2) Roadside development (3) Traffic control including illumination e. Plan sheet(s) (1) Existing traffic control that will remain (signs and markings) (2) Existing utilities (3) Proposed highway improvements (4) Proposed installation (5) Proposed additional traffic controls (6) Proposed illumination attached to signal poles. (7) Proposed power pole source f. Notes for plan layout g. Phase sequence diagram(s) (1) Signal locations (2) Signal indications (3) Phase diagram (4) Signal sequence table (5) Flashing operation (normal and emergency) (6) Preemption operation (when applicable) (7) Contact responsible Agency to obtain interval timing, cycle length and offset h. Construction detail sheets(s) (1) Poles (State standard sheets) (2) Detectors (3) Pull Box and conduit layout (4) Controller Foundation standard sheet (5) Electrical chart i. Marking details (when applicable)

  • Searchability Offering searchability capabilities on the Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section. 1.10.1 Registry Operator will offer searchability on the web-­‐based Directory Service. 1.10.2 Registry Operator will offer partial match capabilities, at least, on the following fields: domain name, contacts and registrant’s name, and contact and registrant’s postal address, including all the sub-­‐fields described in EPP (e.g., street, city, state or province, etc.). 1.10.3 Registry Operator will offer exact-­‐match capabilities, at least, on the following fields: registrar id, name server name, and name server’s IP address (only applies to IP addresses stored by the registry, i.e., glue records). 1.10.4 Registry Operator will offer Boolean search capabilities supporting, at least, the following logical operators to join a set of search criteria: AND, OR, NOT. 1.10.5 Search results will include domain names matching the search criteria. 1.10.6 Registry Operator will: 1) implement appropriate measures to avoid abuse of this feature (e.g., permitting access only to legitimate authorized users); and 2) ensure the feature is in compliance with any applicable privacy laws or policies.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.

  • Formatted Font: 12

  • ELECTRONIC WORKFLOW SYSTEM OGS reserves the right to incorporate an electronic workflow system that may include elements of the Authorized User RFQ process. OGS reserves the right to post Authorized User Contract usage of Centralized Contracts. For Lot 4 only, when provided for in the RFQ and resultant Authorized User Agreement, the Authorized Users may reimburse travel expenses. All rules and regulations associated with this travel can be found at xxxx://xxx.xxxxx.xx.xx/agencies/travel/travel.htm. In no case will any travel reimbursement be charged that exceeds these rates. All travel will be paid only as specified within the Authorized User Agreement and must be billed with the associated services on the same Invoice with receipts attached. The Contractor shall receive prior approval from the Authorized User for any travel that occurs during the term of an Authorized User Agreement. Parking fees and/or parking tickets shall not be paid by an Authorized User. Unless otherwise specified in writing by the Authorized User, a vehicle will not be provided by Authorized User to the Contractor for travel. Therefore, the Contractor will be responsible for ensuring that the Contractor has access to an appropriate vehicle (e.g., personal vehicle or rental vehicle) or common carrier with which to carry out any necessary travel. For the Contractor to obtain reimbursement for the use of a rental vehicle, such use must be justified as the most cost- effective mode of transportation under the circumstances (including consideration of the most effective use of time). The Contractor is responsible for keeping adequate records to substantiate any claims for travel reimbursement. All services provided under the resultant Authorized User Agreement must be performed within CONUS. There are no BONDS for this Contract. However, an Authorized User may require in an RFQ a performance, payment or Bid bond, or negotiable irrevocable letter of credit or other form of security for the faithful performance for the resultant Authorized User Agreement. Pursuant to New York State Executive Law Article 15-A and Parts 140-145 of Title 5 of the New York Codes, Rules and Regulations (“NYCRR”), the New York State Office of General Services (“OGS”) is required to promote opportunities for the maximum feasible participation of New York State-certified Minority- and Women-owned Business Enterprises (“MWBEs”) and the employment of minority group members and women in the performance of OGS contracts.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Workstation/Laptop encryption All workstations and laptops that process and/or store DHCS PHI or PI must be encrypted using a FIPS 140-2 certified algorithm which is 128bit or higher, such as Advanced Encryption Standard (AES). The encryption solution must be full disk unless approved by the DHCS Information Security Office.

  • Query a search query initiated from the Search Box or a Hyperlink, or a request for Matched Ads initiated by the Ad Code on an Ad Page. Results: Paid Search Results, Hyperlink Results, Domain Match Results, Web Search Results and/or Matched Ads, to the extent included in this Agreement and as appropriate to the context. Search Box: a graphical area in which a user can enter a Query. SO: the Service Order.

  • Synchronous Generation The Interconnection Customer shall design its Small Generating Facility to maintain a composite power delivery at continuous rated power output at the Point of Interconnection at a power factor within the range of 0.95 leading to 0.95 lagging, unless the NYISO or the Transmission Owner in whose Transmission District the Small Generating Facility interconnects has established different requirements that apply to all similarly situated generators in the New York Control Area or Transmission District (as applicable) on a comparable basis, in accordance with Good Utility Practice.

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