WP2 – Standardisation and interoperability Sample Clauses

WP2 – Standardisation and interoperability. Objectives: There are many good reasons to introduce standards for installing and operating ocean observatory systems. For instance standards allow for easy interchange of individual instruments between different installations and platforms. The depth and extent of the standardisation process depends on the needs of the users and the technical feasibility. The process should begin at the sensor level as this will ensure the seamless integration of the information flow originating from a multitude of sensor systems, in quantity and quality. In present observation systems with limited number of instruments it is always possible to individually integrate and match each instrument into the systems. With the future heterogeneous, dynamic changing ocean observatory systems in mind this is no longer a practical concept. A modular approach with each module possessing defined, standardised software and hardware interfaces has to be established. In contrast to terrestrial systems underwater observatories are not easily accessible and servicing can prove difficult. A similar planning and logistic effort, as seen in space sciences, needs to be implemented for these observatories. This is the main reason for having standards, as instruments can be tested and integrated in a defined procedure before deployment. It lends itself to the concept of introducing quality management or mission assurance procedures. Standards make interoperability possible which not only means interchange-ability of instruments but that the collected information is comprehensible for all subsequent data processing units. The sensor information must be accompanied with an exhaustive description of the data in the form of standardised metadata schemes. In other words the standards on a lower level should be translatable to a higher level as for instance has presently been put on track with Sensor ML and IEEE-1451. This will then provide a base to make the data available for automated information retrieval. On top of that schemes of sensor information metadata will facilitate the interoperability in particular under the aspect that information from different observatory sites have to be integrated into a common system. Last but not least the standardisation processes are expected to generate added value and benefits in an economic context: - Enhanced product quality and reliability - Reduction in costs - Increased efficiency and ease of maintenance - Simplify and improve usability - Greater compati...
AutoNDA by SimpleDocs

Related to WP2 – Standardisation and interoperability

  • Interoperability To the extent required by applicable law, Cisco shall provide You with the interface information needed to achieve interoperability between the Software and another independently created program. Cisco will provide this interface information at Your written request after you pay Cisco’s licensing fees (if any). You will keep this information in strict confidence and strictly follow any applicable terms and conditions upon which Cisco makes such information available.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Registry Interoperability and Continuity Registry Operator shall comply with the Registry Interoperability and Continuity Specifications as set forth in Specification 6 attached hereto (“Specification 6”).

  • Technical and Interconnection Requirements 2.1 Consumer agrees that his Rooftop Solar PV System and Net Metering System will conform to the standards and requirements specified in the Policy, Regulations and Supply Code as amended from time to time.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

  • Access to Network Interface Device (NID 2.4.3.1. Due to the wide variety of NIDs utilized by BellSouth (based on subscriber size and environmental considerations), Mpower may access the on-premises wiring by any of the following means: BellSouth shall allow Mpower to connect its loops directly to BellSouth’s multi-line residential NID enclosures that have additional space and are not used by BellSouth or any other telecommunications carriers to provide service to the premise. Mpower agrees to install compatible protectors and test jacks and to maintain the protection system and equipment and to indemnify BellSouth pursuant to Section 8 of the General Terms and Conditions of this Agreement.

  • Equipment and Software Requirements In order to view and retain electronic communications that we make available to you, you must have: • A PC or other device with an Internet browser that has “cookies” enabled and supports 128 bit encryption • An Internet connection • An email address • A PDF viewer (such as Adobe Reader) • A printer or computer with sufficient electronic storage space All communications shall be delivered to the last address we have on file for you. These notices will be sent through electronic delivery (email) and will be considered delivered the same day as sent. If you have opted out of electronic delivery, communications sent to you through the United States Postal Service are considered delivered 5 business days after the postmark date. It is your responsibility to notify the Custodian of any email address change or residential address change. We will not be held liable for any losses or damages if you have not provided Custodian with the most current address information. The electronically signed copy of this document should be considered equivalent to a printed hard copy form. It is considered a true and complete record of the document, admissible in arbitration and/or administrative hearings or proceedings. Your electronic signature on the Application and other electronic forms such as the Investment Direction are considered valid and the same as if the paper form or Application were signed.

  • Maintenance Scheduling The NTO shall schedule maintenance of its facilities designated as NTO Transmission Facilities Under ISO Operational Control and schedule any outages (other than forced transmission outages) of said transmission system facilities in accordance with outage schedules approved by the ISO. The NTO shall comply with maintenance schedules coordinated by the ISO, pursuant to this Agreement, for NTO Transmission Facilities Under ISO Operational Control. The NTO shall be responsible for providing notification of maintenance schedules to the ISO for NTO Transmission Facilities Requiring ISO Notification. The NTO shall provide notification of maintenance schedules to affected Transmission Owners for NTO Transmission Facilities Requiring ISO Notification and Local Area Transmission Facilities pursuant to Section 3.5.3 of the ISO Services Tariff.

  • MAINTENANCE OF STANDARDS The Employer agrees, subject to the following provisions, that all conditions of employment in his/her individual operation relating to wages, hours of work, overtime differentials and general working conditions shall be maintained at not less than the highest standards in effect at the time of the signing of this Agreement, and the conditions of employment shall be improved whenever specific provisions for improvement are made elsewhere in this Agreement.

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