Communication Protocols. The Parties shall agree to the communication protocols outlined in Exhibit H to facilitate the exchange of information between them and Owner shall comply with the System Operation Procedures provided in Exhibit H.
Communication Protocols. The communication protocols outlined in Binding Protocol 4 - Exception Protocol for Events Level 1 shall be used.
Communication Protocols. Recognising the importance of common key messages both parties agree to the following: ♦ nominating a set of agreed key spokespersons for the project's regional benefits who can present a series of common key messages about the benefits the project can deliver for the region; ♦ neither party to this MOU has the authority to speak publicly on behalf of the other party without prior consent; and ♦ where one of party wishes to issue a public statement about the MOU, including the cooperation arrangements between the two parties via press release, newsletter or other communications means, any such statements will be approved by both parties, prior to release.
Communication Protocols. The Parties agree that prior to either Party making a separate public statement about this third five-yearly review that they will consult the other Party.
Communication Protocols. The Parties shall agree to the communication protocols outlined in Appendix 20.05 to facilitate the exchange of information between the Parties. Writing Requirements. In documenting and confirming Dispatch Notices, conversations between the Parties’ personnel and contractors may be recorded by tape or other electronic means and any such recording will satisfy any “writing” requirements under Applicable Laws. METERING, COMMUNICATIONS AND TELEMETRY SDG&E Access. All communication, metering, telemetry, and associated operation equipment will be centralized into the Project’s Distributed Control System (“DCS”). Seller shall configure the Project’s DCS so that SDG&E may access it. Seller shall ensure that the access link will provide a monitoring and control interface to enable automatic control for charging and discharging of the Project and provide real-time information regarding the to SDG&E. Seller shall link the systems via an approved SDG&E communication network, utilizing existing industry standard network protocol, as approved by SDG&E. The connection will be bidirectional in nature and used by the Parties to exchange all data points to and from the SDG&E monitoring system. Control Logic [NOTE TO BIDDERS: To be modified based on technology type] Seller will ensure that the Project’s DCS control logic will be configured to control the Project in multiple configurations. The Project’s control logic will incorporate control signals from multiple locations to perform dispatch, charging and Ancillary Services functions. Control logic will perform all coordinated megawatt control and Automatic Generation Control (“AGC”) independently for the Project. Delivery of Data. At least thirty (30) days prior to the Expected Initial Delivery Date, Seller shall provide SDG&E with all facility and metering information necessary to communicate with SDG&E as may be requested by SDG&E, including, but not limited to, the information set forth in Appendix 21.03. Satellite Communication System. Seller is responsible for installing, testing, commissioning and maintaining the Satellite Communications System (“SCS”) at the Project in accordance with instructions provided by SDG&E and the SCS vendor. Seller shall grant SDG&E reasonable access to the Site for routine calibration and maintenance of the SCS during the Delivery Period. SDG&E Access. Seller shall take all actions and execute all documents reasonably necessary to grant SDG&E access to the metering, communications, and t...
Communication Protocols. The Parties shall agree to the communication protocols outlined in Exhibit G to facilitate the exchange of information between them.
Communication Protocols. This section focuses on two communications protocols: Title 21 and ISO 18000-6C. Title 21 is currently in use at all of the tolling facilities in the Denver Metro Area. However, E-470 is in the process of procuring 18000-6C tags and tag readers. The Colorado Legislature requires interoperability between tolling facilities within the State. As a result, multi-protocol Radio Frequency Identification (RFID) tag readers will need to be used to allow for the deployment of different communications protocols within RFID tags while still keeping interoperability intact between facilities. Both these types of RFID tags operate in the 860 MHz to 960 MHz Industrial, Scientific, and Medical band. • Title 21 Protocol - The Title 21 protocol was developed by Caltrans in the early 1990’s. Caltrans identified a frequency band that would be utilized strictly for electronic toll transponders and readers. Title 21 refers to the related section of the California Code of Regulations which describes compatibility requirements and data format for Automatic Vehicle Identification (AVI) equipment between vehicle-mounted tags and fixed-position roadside readers. Caltrans continues to use the Title 21 frequencies for electronic toll collection. Colorado followed suit and all toll facilities within the State currently operate under the Title 21 protocol. This is changing though, as discussed in the following section. • ISO 18000-6C – Similar to the Title 21 protocol, this International Standards Organization (ISO) protocol defines the air interface between the readers and the tags. E-470 is procuring ISO 18000-6C sticker-type tags to replace the existing hard case Title 21 transponders. 6C is an open standard; however some manufacturers have developed modified versions that are proprietary. 6C-type tags can be manufactured as both sticker tags and hard case tags, and both are passive and do not require batteries. As mentioned previously, there are not currently any switchable 6C sticker tags currently in use in the industry.
Communication Protocols. Xxxxxx agrees that for purposes of communications with Landlord hereunder, as well as with any designees of Landlord and/or appropriate Government agencies or authorities, it will refer at all times and comply with the protocols set forth on the communications protocols as set forth on Exhibits L and L-1 attached hereto and made a part hereof, as same may be amended from time to time upon Notice to Tenant (the "Communications Protocols"). The Communications Protocols shall set forth which specific agencies or individuals within those agencies shall be designated as contacts with respect to particular responsibilities including, without limitation, the granting of consents hereunder, guidance in connection with contract compliance and compliance with the other Exhibits of this Lease, general communication and communication and procedures in the event of emergencies affecting the Center. Tenant shall address all inquiries and communications to those entities or individuals set forth on the Communications Protocols set forth on Exhibits L and L-1 attached hereto and made a part hereof. Security.
Communication Protocols. The Parties shall agree to the communication protocols outlined in Appendix 20.05 to facilitate the exchange of information between the Parties. Writing Requirements. In documenting and confirming Dispatch Notices, conversations between the Parties’ personnel and contractors may be recorded by tape or other electronic means and any such recording will satisfy any “writing” requirements under Applicable Laws. ARTICLE TWENTY-ONE METERING, COMMUNICATIONS, AND TELEMETRY (PUT DELIVERY PERIODS) SCE Access. All communication, metering, telemetry, and associated generation operation equipment will be centralized into the Project’s Distributed Control System (“DCS”). Seller shall configure each Generating Unit’s DCS so that SCE may access it during any Put Delivery Period via the Generation Management System (“GMS”) from SCE’s Generation Operations Center (“GOC”). Seller shall ensure that the access link will provide a monitoring and control interface to enable automatic dispatch of each Generating Unit. Seller shall link the systems via an approved SCE communication network, utilizing existing industry standard network protocol, as approved by SCE. The connection will be bidirectional in nature and used by the Parties to exchange all data points to and from the GOC.
Communication Protocols. All publicity and strategic communications for the Legacy Project will be coordinated through the TAC, so that the parties can deliver unified direction and messages to outside parties. Each party commits to working within Legacy Project channels and the structure set forth in this Agreement, especially with respect to any potential conflicts, disagreements, external events, or pressures. The parties shall consult with each other first, prior to outreach to third parties, at emergency TAC or Partners Group meetings, as necessary. The parties commit to attendance at emergency meetings.
