DSA Field Trip Notes Sample Clauses

DSA Field Trip Notes. At the conclusion of the site visit, the DSA field engineer issues a field trip note (form DSA 135) as described in PR 13-01. The field trip note indicates any findings by the field engineer that require action by the project inspector and/or the design professional(s) to ensure project compliance with Field Act requirements. The field trip note may include informational comments, including construction status and guidance given to the project inspector. The field trip note becomes a part of the DSA project records. REFERENCES: California Code of Regulations (CCR) Title 24 Part 1: California Administrative Code (CAC) Sections 4-211, 4-212, 4-214, 4-219, 4-240, 4-241, 4-242, 4-333, 4-333.1, 4-334, 4-336, 4-337, and 0-000 Xxxxxxxxxx Health and Safety Code, Sections 16017 and 16021 California Education Code, Sections 17309, 17311, 81141 and 81143 This This IR is intended for use by DSA staff and by design professionals to promote statewide consistency for review and approval of plans and specifications as well as construction oversight of projects within the jurisdiction of DSA, which includes State of California public schools (K‒ 12), community colleges and state-owned or state-leased essential services buildings. This IR indicates an acceptable method for achieving compliance with applicable codes and regulations, although other methods proposed by design professionals may be considered by DSA.
AutoNDA by SimpleDocs

Related to DSA Field Trip Notes

  • Field Trips Orange COUNTY funds may not be used to support any overnight and/or out of Central Florida travel, unless approved by the COUNTY’S Manager of the CCC or designee in advance. The AGENCY must have on file for field trip(s) that each participant, adult or minor, must have a signed release of liability form releasing the COUNTY from any liability. If the participant is a minor, the release must be signed by a parent/guardian. Central Florida is defined as Orange, Osceola, Seminole, Brevard, Lake, Polk, and Volusia Counties.

  • Licensed Products Lessee will obtain no title to Licensed Products which will at all times remain the property of the owner of the Licensed Products. A license from the owner may be required and it is Lessee's responsibility to obtain any required license before the use of the Licensed Products. Lessee agrees to treat the Licensed Products as confidential information of the owner, to observe all copyright restrictions, and not to reproduce or sell the Licensed Products.

  • AUDIT OF LICENSED PRODUCT USAGE Contractor shall have the right to periodically audit, no more than annually, at Contractor’s expense, use of licensed Product at any site where a copy of the Product resides provided that: (i) Contractor gives Licensee(s) at least thirty (30) days advance written notice, (ii) such audit is conducted during such party’s normal business hours, (iii) the audit is conducted by an independent auditor chosen on mutual agreement of the parties. Contractor shall recommend a minimum of three (3) auditing/accounting firms from which the Licensee will select one (1). In no case shall the Business Software Alliance (BSA), Software Publishers Association (SPA), Software and Industry Information Association (SIIA) or Federation Against Software Theft (FAST) be used directly or indirectly to conduct audits, or be recommended by Contractor; (iv) Contractor and Licensee are each entitled to designate a representative who shall be entitled to participate, and who shall mutually agree on audit format, and simultaneously review all information obtained by the audit. Such representatives also shall be entitled to copies of all reports, data or information obtained from the audit; and (v) if the audit shows that such party is not in compliance, Licensee shall be required to purchase additional licenses or capacities necessary to bring it into compliance and shall pay for the unlicensed capacity at the NYS Net Price in effect at time of audit, or if none, then at the Contractor’s U.S. Commercial list price. Once such additional licenses or capacities are purchased, Licensee shall be deemed to have been in compliance retroactively, and Licensee shall have no further liability of any kind for the unauthorized use of the software.

  • Existing Products 1. Hardware - Title and ownership of Existing Hardware Product shall pass to Authorized User upon Acceptance.

  • New Products You agree to comply with NASD Notice to Members 5-26 recommending best practices for reviewing new products.

  • SHIPPING/RECEIPT OF PRODUCT a. Packaging Product shall be securely and properly packed for shipment, storage and stocking in appropriate, clearly labeled shipping containers and according to accepted commercial practice, without any extra charges for packing materials, cases or other types of containers. The container shall become and remain the property of the Authorized User unless otherwise specified in the Contract documents.

  • Geographical Indications 1. Each Party shall recognise that geographical indications may be protected through a trade xxxx or sui generis system or other legal means in accordance with its laws and regulations.

  • SOURCE CODE ESCROW FOR LICENSED PRODUCT If Source Code or Source Code escrow is offered by either Contractor or Product manufacturer or developer to any other commercial customers, Contractor shall either: (i) provide Licensee with the Source Code for the Product; or (ii) place the Source Code in a third party escrow arrangement with a designated escrow agent who shall be named and identified to the State, and who shall be directed to release the deposited Source Code in accordance with a standard escrow agreement acceptable to the State; or (iii) will certify to the State that the Product manufacturer/developer has named the State, acting by and through the Authorized User, and the Licensee, as a named beneficiary of an established escrow arrangement with its designated escrow agent who shall be named and identified to the State and Licensee, and who shall be directed to release the deposited Source Code in accordance with the terms of escrow. Source Code, as well as any corrections or enhancements to such source code, shall be updated for each new release of the Product in the same manner as provided above and such updating of escrow shall be certified to the State in writing. Contractor shall identify the escrow agent upon commencement of the Contract term and shall certify annually that the escrow remains in effect in compliance with the terms of this clause. The State may release the Source Code to Licensees under this Contract who have licensed Product or obtained services, who may use such copy of the Source Code to maintain the Product.

  • Product Technical Support & Maintenance Licensee shall have the option of electing the Product technical support and maintenance (“maintenance”) set forth in the Contract by giving written notice to Contractor any time during the Centralized Contract term. Maintenance term(s) and any renewal(s) thereof are independent of the expiration of the Centralized Contract term and will not automatically renew. Maintenance shall include, at a minimum, (i) the provision of error corrections, updates, revisions, fixes, upgrade and new releases to Licensee, and (ii) Help Desk assistance with locally accessible “800” or toll free, local telephone service, or alternatively on-line Help Desk accessibility. Contractor shall maintain the Products so as to provide Licensee with the ability to utilize the Products in accordance with the Product documentation without significant functional downtime to its ongoing business operations during the maintenance term. Authorized User shall not be required to purchase maintenance for use of Product, and may discontinue maintenance at the end of any current maintenance term upon notice to Contractor. In the event that Authorized User does not initially acquire or discontinues maintenance of licensed Product, it may, at any time thereafter, reinstate maintenance for Product without any additional penalties or other charges, by paying Contractor the amount which would have been due under the Contract for the period of time that such maintenance had lapsed, at then current NYS net maintenance rates.

  • Research Use The Requester agrees that if access is approved, (1) the PI named in the DAR and (2) those named in the “Senior/Key Person Profile” section of the DAR, including the Information Technology Director and any trainee, employee, or contractor1 working on the proposed research project under the direct oversight of these individuals, shall become Approved Users of the requested dataset(s). Research use will occur solely in connection with the approved research project described in the DAR, which includes a 1-2 paragraph description of the proposed research (i.e., a Research Use Statement). Investigators interested in using Cloud Computing for data storage and analysis must request permission to use Cloud Computing in the DAR and identify the Cloud Service Provider (CSP) or providers and/or Private Cloud System (PCS) that they propose to use. They must also submit a Cloud Computing Use Statement as part of the DAR that describes the type of service and how it will be used to carry out the proposed research as described in the Research Use Statement. If the Approved Users plan to collaborate with investigators outside the Requester, the investigators at each external site must submit an independent DAR using the same project title and Research Use Statement, and if using the cloud, Cloud Computing Use Statement. New uses of these data outside those described in the DAR will require submission of a new DAR; modifications to the research project will require submission of an amendment to this application (e.g., adding or deleting Requester Collaborators from the Requester, adding datasets to an approved project). Access to the requested dataset(s) is granted for a period of one (1) year, with the option to renew access or close-out a project at the end of that year. Submitting Investigator(s), or their collaborators, who provided the data or samples used to generate controlled-access datasets subject to the NIH GDS Policy and who have Institutional Review Board (IRB) approval and who meet any other study specific terms of access, are exempt from the limitation on the scope of the research use as defined in the DAR.

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