System Documentation. The Contractor shall update documentation on its system(s) within 30 days of implementation of the changes. The Contractor’s documentation must include a system introduction, program overviews, operating environment, external interfaces, and data element dictionary. For each of the functional components, the documentation should include where applicable program narratives, processing flow diagrams, forms, screens, reports, files, detailed logic such as claims pricing algorithms and system edits. The documentation should also include job descriptions and operations instructions. The Contractor shall have available current documentation on-site for State audit as requested.
System Documentation. The Supplier will provide the following documentation as minimum in due course to be requested by the Customer:
i. Base Station Specifications ii. Base Station Infrastructure requirements specifications iii. Vehicle Location Unit Specifications iv. Vehicle Location Unit general installation instructions v. Fleet Management post Operating Manual (optional) vi. Personal Location Unit Specifications vii. NCC Diagrams viii. NCC Infrastructure requirements specifications ix. NCC Operating Procedures x. VLU and PAL Registration and Activation Procedure xi. System Acceptance Test Procedures xii. Monthly progress reports xiii. Design Reviews documentation xiv. Project Organization Chart Vision Plant Inc. Telematics Wireless Ltd. The above documentation will be in English. The Customer or local contractors if applicable, responsible for NCC and Base Station infrastructure preparation, will maintain documentation for each site to be established. The documentation of NCC will include a detailed description of the electricity system, including all interim boards and the main electricity board, specifying the types of cables and automatic switches. The markings of the switches in the documentation will be identical to their markings on electricity boards. The documentation of the System will include diagrams of the connections of all components of the System, specifying numbers of cables, types of cables, and names of connectors. The markings in the diagrams will be identical to the markings on cables and connectors. For each Base Station the Customer will prepare a booklet, indicating the site on a map with a scale of 1:100,000. The booklet will also contain a descriptive diagram of the site and the mast, specifying the disposition of the dedicated equipment, and digital photographs of the interior and exterior of the site. The documentation will include a complete address of the site, precise coordinates of the antennas, the name and telephone numbers of the site owner, the name and telephone numbers of the contractor's liaison, details of electricity feeding up to the structure's main board, and the paths of communication and grounding lines. The Customer will provide a detailed description of the connections between components of the system, including types of cables, their length, and types of connectors. The Customer will specify the manufacturer's number of each of the items of equipment installed at the site, including air-conditioner, electricity board, and co...
System Documentation. Upon receipt of the Notice to Proceed, TSP shall commence preparation of the System Documentation listed in TR Section TP, in accordance with the time frames listed in such Section TP or such shorter time frames as may otherwise be specified in the approved Project Schedule. The System Documentation shall be based on and demonstrate compliance with the parameters set forth in the TR, shall contain sufficient detail so they can reasonably be approved by an engineer registered in the discipline to which such plans, drawings and specifications pertain, shall contain sufficient detail to permit inspection and approval of the Work by the Joint Board, and shall comply with the following Configuration Work Requirements):
(a) Applicable INDOT standards for work in Indiana OR applicable KYTC standards for work in Kentucky;
(b) All applicable Laws;
(c) All Regulatory Approvals; and
(d) All applicable provisions of the Contract Documents.
System Documentation. Ceres shall maintain documentation of and for the a/c/e System, including but not limited to providing CBOT with user manuals, source and object code for system programs, flow charts and the necessary narrative to permit reasonably competent programmers, conversant in the language in which the system programs are written, to maintain and modify such programs. Ceres shall keep all documentation current to reflect all changes made in the a/c/e System. CBOT is granted the right to copy the documentation as may be necessary to support CBOT's use of the System program
System Documentation. At the completion of the implementation/installation, the Contractor shall provide to each Department facility, the Contract Manager, and the Local Contract Coordinator–Operations, a complete set of service reference manuals that shall include information specific to the installation at the respective facility. In addition, after installation at each respective institution, the Contractor shall supply documentation containing service request contact numbers, instructions on reporting and escalation procedures to the Local Contract Coordinator - Operations and Assistant Warden for Programs at the respective institution.
System Documentation. Contractor agrees to provide to the County as part of any new version release, upgrade or enhancement of Licensed Software, updated versions of applicable manuals and other associated printed materials in electronic format. Contractor further agrees that the County may create hard copy reproductions of the updated materials in quantities sufficient to satisfy the County's own intemal needs for the operation/use and maintenance of the Verity Voting System. The County agrees to include the Contractor's copyright notice and all other proprietary rights notices on all such documentation reproduced as they appear on the original or in accordance with written copyright instructions provided to County by the Contractor.
System Documentation. Vendor will update existing system material such as system documentation, troubleshooting guide, and system administration manuals and deliver to the County during each iteration and at project end. In addition, Vendor’s Blu Age tool will generate additional code documentation to facilitate maintenance of the converted system.
System Documentation. All system documentation currently in existence and that is developed in the future relative to the applications in Table 1 will be made available to Buyer at the same time it becomes available to Tyson employees. Tyson will provide at least one copy per location of all pertinent documentation, and deliver each copy to the individual location. All documentation relevant to Tyson owned systems will be returned promptly following the transition period. COMPUTER LICENSES All licenses, contracts, bills of sale, and any other written proof of ownership, right to do business with, right to access, etc., associated with computer hardware, vendor support, telecommunications, written materials, or any other aspect of business associated with Buyer and its acquired assets will be transferred and/or made available to Buyer on date of Closing.
System Documentation. After the Both Party Completion Date (or, with respect to the New Orleans Lateral after the New Orleans Lateral Completion Date) and upon thirty (30) days prior notice from the other party, each party shall provide the other party with documentation ("Deliverables") which shall consist of the following:
1. As-built drawings as set forth in Exhibit D as available for the IXC System or the Vyvx System, as the case may be.
2. Technical specifications of the optical fiber cable and associated splices, regenerators and other equipment placed in the IXC System or the Vyvx System, as the case may be.
System Documentation. Upon at least fifteen (15) Business Days’ notice from OCA (but no more than twice in a Contract Year), Contractor will meet with representatives of OCA and any of its designee to (i) explain how the Services are provided, and (ii) provide such training and documentation as OCA may require for OCA to (A) provide services that interact with or interface with the Services, and (B) understand and operate the Software. Upon OCA’s request from time to time, Contractor will deliver to OCA a full description of the processes, tools and environmental configuration related to the Services.
