Update for D6 Sample Clauses

Update for D6. 2bis At the time of writing this update, the first two entries in the above table have become of less relevance to the COSIGN consortium. The first, ETSI Grid and Cloud Computing has stopped to be active publishing new developments and goals. The second, ETSI Next-Generation Network has stabilized on its focus on evolution towards 5G and is not currently impacting the DCN developments. The ETSI NFV ISG and all of its WGs are very active and of great relevance to COSIGN. Although the driving use cases and the majority of ETSI NFV focus are in Telco networks, data centre, and thus COSIGN, the relation is obvious. The COSIGN consortium will therefore continue to follow the activities of this ISG and its publications, looking for opportunities to present COSIGN ideas and outcomes to the ISG members and influencers. The IBM team participating in COSIGN follows the group and its results – documentation, white papers, proofs of concepts. Due to team’s Data Centre focus, it cannot commit to attending the meetings and/or giving presentations there. NXW is participant and observing member - non voting - in ETSI NFV ISG and, as such, the team involved in COSIGN is following the latest NFV outcomes about architectural specifications of the Virtual Infrastructure Management and Orchestration components. Their impact on DC requirements and functionalities will be continuously analysed and taken into account in COSIGN architectural choices for network control and cloud orchestration. The updated ETSI liaisons plan is summarised in Table 3: ETSI Standardization element Type of Interaction Schedule Priority Partners NFV ISG; Architecture of the Virtualisation Infrastructure Defining architectural role of virtual network functions as part of overall data centre IT and network resources. Observation of and alignment with the ISG developments Year 2 / Year 3 High NXW, IBM NFV ISG; Management & Orchestration Defining interfaces required for management and orchestration of virtual network functions as part of overall IT and network resources. Observation of and alignment with the ISG developments Year 2 / Year 3 High IBM Table 3 – Updated overview of potential COSIGN standardization topics in ETSI
Sample 1Sample 2See All (4)
AutoNDA by SimpleDocs
Update for D6. 2bis Assigned partners continue to monitor the outcomes and participate in ONF activities related to SDN architecture in general and to SDN for optical transport in particular. UNIVBRIS presented SDN activity of COSIGN in Transport WG Group meeting in ONF 2015 member meeting (Feb. 2015) (including the extension we implemented with OF protocol and OpenDaylight controller) and was very well received. Also, UNIVBRIS attended a day-long joint workshop on ‘Programmable Cities’ by Bristol Is Open (BIO) and the Open Networking Foundation (ONF) (in 7th July 2015) to discuss Software Defined Networking (SDN) deployment in the new and exciting use case of Smart Cities where SDN enabled optical technology will be employed. UNIVBRIS helped to organize this event and Xxxx. Xxxxxxx Xxxxxxxxxx from UNIVBRIS (as BIO Chief Technology Officer) gave a keynote talk. IBM and NXW will continue to monitor the ONF activities in the areas of SDN architecture, OF specifications, and Northbound Interfaces. During the project duration, IBM team members participating in COSIGN have already attended numerous ONF presentations and events. The updated ETSI liaisons plan is summarised in Table 5: ONF WG Standardization elements Type of Interaction Schedule Priority Partners Architecture & Framework WG Requirements/use cases for SDN controlled hybrid optical data centres Collaborate with industrial entities, presenting and reflecting COSIGN point of view and achievements. Contributes on Framework and Architecture documents. Year 2 / Year 3 High UNIVBRIS IBM Optical Transport WG SDN-based architectures for supporting heterogeneous optical infrastructures Contributes on specifications. Recommend solutions and extensions to the OF protocols that address the identified requirements for SDN and the OpenFlow Standard control of COSIGN DCN. Year 2 / Year 3 High UNIVBRIS OF extensions for low loss beam steering switches, InP Fast optical switches, 3D-stacked transceivers and ToR Northbound Interface WG Interface requirements and specifications. Monitor WG activities to ensure proper alignment of COSIGN outcomes Year 2 / Year 3 High NXW, IBM Table 5 – Updated overview of potential COSIGN standardization topics in ONF.
Sample 1Sample 2

Related to Update for D6

  • Update Each year the Plant Training Committee shall prepare an Update that reviews the Findings and modifies them based on changed circumstances, measures the success of the Training Program against its objectives and modifies the Training Program accordingly.

  • Updates “Updates” are changes that do not require a change to the established Centralized Contract terms and conditions. Updates may include: Centralized Contract changes and updates made in accordance with the previously approved pricing formula (e.g. discount from list price); adding new products or services within the established, previously approved pricing structure; lowering pricing of products or services already on Contract, deleting products or services available through the Centralized Contract, adding product or service that do not fall under the previously established price structure or discounts under the Contract, re-bundled products, and other updates not listed above that are deemed to be in the best interest of the State and do not result in a change to the established Centralized Contract terms and conditions. Updates must be submitted to OGS for review, and must be accompanied by a justification of reasonableness of price if the change results in a change in pricing methodology. OGS will notify Contractor in writing if approved.

  • SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO.

  • How to Update Your Records You agree to promptly update your registration records if your e-mail address or other information changes. You may update your records, such as your e-mail address, by using the Profile page.

  • Monthly Updates The Contractor must provide the Design Professional and the Owner with monthly updates of the Overall Project Schedule indicating completed activities and any changes in sequencing or activity durations. (See also Articles 2.1.2 and 2.1.5).

  • DATA FOR CALCULATIONS The initial calculations for any payments owing under this Agreement shall be based upon the valuations placed upon the Qualified Property by the Appraisal District in its annual certified appraisal roll submitted to the District pursuant to § 26.01 of the TEXAS TAX CODE in or about July of each year of this Agreement. The certified appraisal roll data shall form the basis from which any and all amounts due under this Agreement are calculated, and the data utilized by the Consultant will be adjusted as necessary to reflect any subsequent adjustments by the Appraisal District to the District’s appraisal roll. Any estimates used by the Consultant to make calculations as required by this Agreement shall be based on the best and most current information available. The Consultant shall from time to time adjust the data utilized to reflect actual amounts, subsequent adjustments by the Appraisal District to the District’s certified appraisal roll, or any other relevant changes to material items such as student counts or tax collections.

  • Corrections to Factual Inaccuracies In the event that the LEA determines that the Provider is maintaining Student Data that contains a factual inaccuracy, and Provider cooperation is required in order to make a correction, the LEA shall notify the Provider of the factual inaccuracy and the correction to be made. No later than 90 calendar days after receiving the notice of the factual inaccuracy, the Provider shall correct the factual inaccuracy and shall provide written confirmation of the correction to the LEA.

  • Schedule Updates the Contractor agrees to maintain the Work duration schedule updates on an ongoing basis and, when the County requests it, include the updates in its payment request. The Contractor may be required to submit a narrative report with each monthly update which shall include a description of current and anticipated problem areas, delaying factors and their impact, and an explanation of corrective action taken or proposed. Failure to do so may be considered a material breach of the Contract. Any additional or unanticipated costs or expense required to maintain the schedules shall be solely the Contractor’s obligation and Contractor agrees not to charge the County.

  • Xxxxxxx to Meet Timelines Failure by the Union to comply with the timelines will result in the automatic withdrawal of the grievance. Failure by the Employer to comply with the timelines will entitle the Union to move the grievance to the next step of the procedure.

  • CONTENT UPDATES If You purchase a Symantec maintenance/support offering consisting of or including Content Updates, as indicated on Your Support Certificate, You are granted the right to use, as part of the Licensed Software, such Content Updates as and when they are made generally available to Symantec’s end user customers who have purchased such maintenance/support offering and for such period of time as indicated on the face of the applicable Support Certificate. This License Agreement does not otherwise permit You to obtain and use Content Updates.

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