Documentation Listing (CDIL PM-5 Sample Clauses

Documentation Listing (CDIL PM-5. BATC shall develop and maintain a Documentation Listing that identifies all deliverable reports, analyses, drawings, software items, etc., that are developed on the project. The Documentation Listing shall include a naming convention that uniquely identifies the documents for electronic access where applicable. The List shall also indicate spacecraft name, a short title/description of the document, subsystem affected, the latest revision number and date, planned completion date, and status information. The List shall indicate those WV1 and WV2 documents that are also applicable to WV3. Document updates are required to reflect content changes. Document updates are not required if the sole purpose is to reflect applicability to WV3.
AutoNDA by SimpleDocs

Related to Documentation Listing (CDIL PM-5

  • Documentation License Subject to the terms of this Agreement, Flock hereby grants to Agency a non- exclusive, non-transferable right and license to use the Documentation during the Term in connection with its use of the Services as contemplated herein, and under Section 2.5 below.

  • Closing Documentation, etc For purposes of determining compliance with the conditions set forth in §12, each Lender that has executed this Credit Agreement shall be deemed to have consented to, approved or accepted, or to be satisfied with, each document and matter either sent, or made available, by any Agent or any Co-Lead Arranger to such Lender for consent, approval, acceptance or satisfaction, or required thereunder to be consented to or approved by or acceptable or satisfactory to such Lender, unless an officer of the Administrative Agent active upon the Borrowers’ account shall have received notice from such Lender prior to the Closing Date specifying such Lender’s objection thereto and such objection shall not have been withdrawn by notice to the Administrative Agent to such effect on or prior to the Closing Date.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet

  • Documentation and compliance (a) The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses. (b) The Parties shall be able to demonstrate compliance with these Clauses. In particular, the data importer shall keep appropriate documentation on the processing activities carried out on behalf of the data exporter. (c) The data importer shall make available to the data exporter all information necessary to demonstrate compliance with the obligations set out in these Clauses and at the data exporter’s request, allow for and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or audit, the data exporter may take into account relevant certifications held by the data importer.

  • Required Documentation The AGENCY is responsible for ensuring that all documents required by this Contract are current and available for the COUNTY’S review upon request. These documents may include, but are not limited to, certificate(s) of insurance, job descriptions and background check confirmations of staff.

  • Project Documentation All documentation provided to the City other than Project drawings shall be furnished on a Microsoft compatible compact disc.

  • DTC DIRECT REGISTRATION SYSTEM AND PROFILE MODIFICATION SYSTEM (a) Notwithstanding the provisions of Section 2.04, the parties acknowledge that the Direct Registration System (“DRS”) and Profile Modification System (“Profile”) shall apply to uncertificated American Depositary Shares upon acceptance thereof to DRS by DTC. DRS is the system administered by DTC pursuant to which the Depositary may register the ownership of uncertificated American Depositary Shares, which ownership shall be evidenced by periodic statements issued by the Depositary to the Owners entitled thereto. Profile is a required feature of DRS which allows a DTC participant, claiming to act on behalf of an Owner of American Depositary Shares, to direct the Depositary to register a transfer of those American Depositary Shares to DTC or its nominee and to deliver those American Depositary Shares to the DTC account of that DTC participant without receipt by the Depositary of prior authorization from the Owner to register such transfer. (b) In connection with and in accordance with the arrangements and procedures relating to DRS/Profile, the parties understand that the Depositary will not verify, determine or otherwise ascertain that the DTC participant which is claiming to be acting on behalf of an Owner in requesting a registration of transfer and delivery as described in subsection (a) has the actual authority to act on behalf of the Owner (notwithstanding any requirements under the Uniform Commercial Code). For the avoidance of doubt, the provisions of Sections 5.03 and 5.08 shall apply to the matters arising from the use of the DRS. The parties agree that the Depositary’s reliance on and compliance with instructions received by the Depositary through the DRS/Profile System and in accordance with this Deposit Agreement shall not constitute negligence or bad faith on the part of the Depositary.

  • Documentation and Record Keeping 1. Records to be Maintained Subrecipient shall maintain all records required by the Federal regulations specified in 24 CFR 570.506 that are pertinent to the activities to be funded under this Contract. Such records shall include, but not be limited to: a. Records providing a full description of each activity undertaken; b. Records demonstrating that each activity undertaken meets the one of the National Objectives of the CDBG program; c. Records required to determine the eligibility of activities; d. Records required to document the acquisition, improvement, use, or disposition of real property acquired or improved with CDBG assistance; e. Records documenting compliance with the fair housing and equal opportunity components of the CDBG program; f. Financial records as required by federal regulations 24 CFR 570.502, and 24 CFR 84.21-28; and g. Other records necessary to document compliance with Subpart K of 23 CFR.

  • White Pages Listings 5.1 BellSouth shall provide <<customer_name>> and their customers access to white pages directory listings under the following terms:

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