Common Data Environment (CDE Sample Clauses

Common Data Environment (CDE. 8.1 It is required that Common Data Environment is utilised on all projects through the development, construction and operation and is capable of transfer to the Authority on Handback, at the end of the Project Term (or on early termination).
Sample 1
AutoNDA by SimpleDocs
Common Data Environment (CDE. The exchange, control, sharing and coordinating of delivered information will depend on a Common Data Environment (CDE) which, supported by technology, provides the process and mechanisms for BIM information. The CDE process is outlined in the “BIM Strategy Framework” which sets out principles of collaboration and the various states of control required. The Common Data environment is the essential core of the BIM Strategy. It must be designed for and be capable of managing all the information and data related to the planning, design, construction, supervision, operations and maintenance of the whole of the Rail Baltica Global Project. The CDE will contain information in shareable, useable format from previous Rail Baltic Project Stages. The “Detailed BIM Strategy” should review existing file formats and make recommendations for standards to be adopted.
Sample 1
Common Data Environment (CDE. SYSTEM A design and recommended technology for the delivery of the Rail Baltica CDE defined in the “Detailed BIM Strategy”. The CDE should be based on a set of cloud based technologies capable of local global and local synchronisation. Ideally it should ensure that information is distributed effectively to each user location but available globally. Communication should be login and password controlled and connected via internet connection. The CDE must be capable of using and distributing individually granted access rights based on project role and responsibilities and file status. Management of access rights must respect the rules of the CDE process and be simply managed using access matrices. The solution should have secure client software available on users local devices for access to the CDE. Design should include: • Systems Architecture – an architectural design for the proposed system including information desktop integration, servers, information distribution, connectivity and synchronisation. • System Functional requirements – the functional requirements that deliver the detailed CDE process. • Systems Non-Functional requirements – system capacity, communication capacity, performance, security, resilience and availability. • Recommended Solutions – potential technology solutions with itemising strengths and weaknesses.
Sample 1
Common Data Environment (CDE. Single source of information for any given project, used to collect, manage and disseminate all relevant approved project documents for multi-disciplinary teams in a managed process. NOTE 1 A CDE may use a project server, an extranet, a file-based retrieval system or other suitable toolset. NOTE 2 Note CDE as defined in the BS 1192:2007.
Sample 1

Related to Common Data Environment (CDE

  • Periodic Review of Costs of Environmental Compliance In the ordinary course of its business, the Company conducts a periodic review of the effect of Environmental Laws on the business, operations and properties of the Company and its subsidiaries, in the course of which it identifies and evaluates associated costs and liabilities (including, without limitation, any capital or operating expenditures required for clean-up, closure of properties or compliance with Environmental Laws or any permit, license or approval, any related constraints on operating activities and any potential liabilities to third parties). On the basis of such review and the amount of its established reserves, the Company has reasonably concluded that such associated costs and liabilities would not, individually or in the aggregate, result in a Material Adverse Change.

  • Global Safety Database Licensee shall establish, hold and maintain (at Licensee’s sole cost and expense) the global safety database for Licensed Products.

  • Compliance Policies and Procedures To assist the Fund in complying with Rule 38a-1 of the 1940 Act, BBH&Co. represents that it has adopted written policies and procedures reasonably designed to prevent violation of the federal securities laws in fulfilling its obligations under the Agreement and that it has in place a compliance program to monitor its compliance with those policies and procedures. BBH&Co will upon request provide the Fund with information about our compliance program as mutually agreed.

  • REMOTE ACCESS SERVICES ADDENDUM The Custodian and each Fund agree to be bound by the terms of the Remote Access Services Addendum hereto.

  • Customer Data 5.1 The Customer shall own all right, title and interest in and to all of the Customer Data and shall have sole responsibility for the legality, reliability, integrity, accuracy and quality of the Customer Data.

  • Site Access Dell requires the right to access the APEX System in a timely way and as provided in the Service Offering Description to provide the Support Services. Failure to ensure that Customer provides Dell with timely access to a Site will relieve Dell of the Support Services obligations and Dell may also, at Dell’s discretion, suspend the APEX Service.

  • Data Loss Prevention Transfer Agent shall implement a data leakage program that is designed to identify, detect, monitor and document Fund Data leaving Transfer Agent’s control without authorization in place.

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