TYPES OF DOCUMENTS Sample Clauses

TYPES OF DOCUMENTS. Documentation describing the various applications related to BSO can be divided into the following types of documents: - FUNCTIONAL SPECIFICATIONS The functional specifications document contains a complete description of the functionality provided by the subsystem or application described. Special logic, considerations, , information handling processes, must be included in the document. The specification does not, however, describe how this functionality is to be implemented. For example, the functional specification might describe the user input required to perform a particular transaction; but it does not show the screen image or determine how different fields will look or behave at the user interface. The Business processes documents describe in high level and in details how would Nextel use the system to conduct its business. The processes describe the function to be achieved (e.g. activation, name/address change, etc.), and how would an end-to-end flow work, including inputs, steps conducted within the system, outputs and specific instructions related to this activity. - APPLICATION AND REFERENCE DATA MODEL (DB ENTITIES) This set of documents include the following: - Data Model General Description - This document provides a high level description of the logical DB structure. It provides a description of the key entities in each area of the Data Model, the relationships among these key entities and a diagram reflecting these relationships. It is intended to provide a high level explanation of how the data model is organized to meet the business needs. - Application Entities - These documents provide a detailed description of the physical entities within the DB. This includes all tables and all fields within a table. It also includes the field type and length (e.g. Char, Numeric etc.) ,valid values, foreign keys. - Reference Table Entities - Same as application entities for the system's reference tables. - DETAILED ARCHITECTURAL DESIGN This document contains the architecture and configuration for the Nextel system. This includes the following: - Nextel Production Hardware Configuration Solution, including servers, disks space and terminal servers - Nextel non-Production Hardware Configuration Solution - LAN,WAN in the Data Center - DRP - Capacity projections supported (questioner) - High availability guidelines - Network configuration within Data Center(s) and into the Data Center - Nextel cellular network topology Note: The last two bullets to be provi...
AutoNDA by SimpleDocs
TYPES OF DOCUMENTS. For a good understanding of this deliverable, the differences in types of documents applicable to smart grids related to strategy, legislation, norms, standards, good practices, as well as their scope need to be understood. Some documents are binding, others are not. Some apply to all EU Member States, others to just a few, or are specific to the energy / smart grid sector and the manufacturers of Smart Grid components. To ensure consistency throughout this docu- ment, without having to specify the exact document type each time, the term policy will be used to refer to any document fitting any of the descriptions below. When required, a more specific term will be used. The descriptions of documents are grouped according to the fol- lowing scopes: - International intergovernmental agreements; - EU general and legislative documents; - (Energy/Smart Grid) standards and sector-specific frameworks; - Framework of national laws and regulations.

Related to TYPES OF DOCUMENTS

  • Copies of Documents Each Trust will furnish CMISC with copies of the following documents: the Declaration of Trust of the Trust and all amendments thereto; and the Trust’s registration statement (the “Registration Statement”) as in effect on the date hereof under the Securities Act of 1933, as amended, and the Investment Company Act of 1940, as amended, and all amendments or supplements thereto hereafter filed. The prospectus(es) and statement(s) of additional information contained in each such Registration Statement, as from time to time amended and supplemented, together are herein collectively referred to as the “Prospectus.”

  • Precedence of Documents In the event of any conflict between the body of this Agreement and any Exhibit or Attachment hereto, the terms and conditions of the body of this Agreement shall control and take precedence over the terms and conditions expressed within the Exhibit or Attachment. Furthermore, any terms or conditions contained within any Exhibit or Attachment hereto which purport to modify the allocation of risk between the parties, provided for within the body of this Agreement, shall be null and void.

  • Numbers of Documents All statements, notices, closing documents, and requests hereunder shall be furnished to the Administrative Agent with sufficient counterparts so that the Administrative Agent may furnish one to each of the Lenders.

  • Review of Documents Borrower has reviewed: (a) the Note, (b) the Security Instrument, (c) the Commitment Letter, and (d) all other Loan Documents.

  • Inspection of Documents Consulting Engineer/Architect shall maintain all Project records for inspection by City during the contract period and for three (3) years from the date of final payment.

  • Reuse of Documents Notwithstanding anything contained in this Agreement or any Document referenced herein to the contrary, the drawing, specifications and other documents prepared by the PA/E for this Project are instruments of the PA/E’s service, but the drawings and specifications shall be owned by the Board. The PA/E shall assign to the Board all common law, statutory and other reserved rights, including the copyright. The Board shall be permitted to retain copies, including reproducible copies, of the PA/E’s drawings, specifications and other documents for information and reference in connection with the Board’s use and occupancy of the Project. The Board may reuse the drawings, specifications or other documents on other projects in accordance with Sec. 1013.45(4), F.S.

  • Execution of Documents Unless otherwise specified, all Credit Documents and all other certificates executed in connection therewith must be signed by a Responsible Officer.

  • Reproduction of Documents This Agreement and all schedules, exhibits, attachments and amendments hereto may be reproduced by any photographic, photostatic, microfilm, micro-card, miniature photographic or other similar process. The parties hereto each agree that any such reproduction shall be admissible in evidence as the original itself in any judicial or administrative proceeding, whether or not the original is in existence and whether or not such reproduction was made by a party in the regular course of business, and that any enlargement, facsimile or further reproduction shall likewise be admissible in evidence.

  • USE OF DOCUMENTS All documents, including but not limited to drawings, specifications and data or programs stored electronically, (hereinafter referred to as “Engineering Work Products”) prepared by Engineer and its subcontractors/subconsultants are related exclusively to the services described in this Contract and are intended to be used with respect to this Project. However, it is expressly understood and agreed by and between the parties hereto that all of Engineer’s designs under this Contract (including but not limited to tracings, drawings, estimates, specifications, investigations, studies and other documents, completed or partially completed), shall be the property of County to be thereafter used in any lawful manner as County elects. Any such subsequent use made of documents by County shall be at County’s sole risk and without liability to Engineer. By execution of this Contract and in confirmation of the fee for services to be paid under this Contract, Engineer hereby conveys, transfers and assigns to County all rights under the Federal Copyright Act of 1976 (or any successor copyright statute), as amended, all common law copyrights and all other intellectual property rights acknowledged by law in the Project Designs and work product developed under this Contract. Copies may be retained by Engineer. Engineer shall be liable to County for any loss or damage to any such documents while they are in the possession of or while being worked upon by Engineer or anyone connected with Engineer, including agents, employees, Engineers or subcontractors/subconsultants. All documents so lost or damaged shall be replaced or restored by Engineer without cost to County. Upon execution of this Contract, Engineer grants to County permission to reproduce Engineer’s work and documents for purposes of constructing, using and maintaining the Project, provided that County shall comply with its obligations, including prompt payment of all sums when due, under this Contract. Engineer shall obtain similar permission from Engineer’s subcontractors/subconsultants consistent with this Contract. If and upon the date Engineer is adjudged in default of this Contract, County is permitted to authorize other similarly credentialed design professionals to reproduce and, where permitted by law, to make changes, corrections or additions to the work and documents for the purposes of completing, using and maintaining the Project. County shall not assign, delegate, sublicense, pledge or otherwise transfer any permission granted herein to another party without the prior written consent of Engineer. However, County shall be permitted to authorize the contractor, subcontractors and material or equipment suppliers to reproduce applicable portions of the Engineering Work Products appropriate to and for use in the execution of the Work. Submission or distribution of Engineering Work Products to meet official regulatory requirements or for similar purposes in connection with the Project is permitted. Any unauthorized use of the Engineering Work Products shall be at County's sole risk and without liability to Engineer and its Engineers. Prior to Engineer providing to County any Engineering Work Products in electronic form or County providing to Engineer any electronic data for incorporation into the Engineering Work Products, County and Engineer shall by separate written contract set forth the specific conditions governing the format of such Engineering Work Products or electronic data, including any special limitations not otherwise provided in this Contract. Any electronic files are provided by Engineer for the convenience of County, and use of them is at County’s sole risk. In the case of any defects in electronic files or any discrepancies between them and any hardcopy of the same documents prepared by Engineer, the hardcopy shall prevail. Only printed copies of documents conveyed by Engineer shall be relied upon. Engineer shall have no liability for changes made to the drawings by other engineers subsequent to the completion of the Project. Any such change shall be sealed by the engineer making that change and shall be appropriately marked to reflect what was changed or modified.

  • Resealing of Documents Once the work has been sealed and accepted by the State, the State, as the owner, will notify the party to this contract, in writing, of the possibility that a State engineer, as a second engineer, may find it necessary to alter, complete, correct, revise or add to the work. If necessary, the second engineer will affix his seal to any work altered, completed, corrected, revised or added. The second engineer will then become responsible for any alterations, additions or deletions to the original design including any effect or impacts of those changes on the original engineer’s design.

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