Communication & Network Clause Samples

Communication & Network. Describe how your management team will have a communication network sufficient to insure that accurate information about issues and challenges regarding program operation or child, youth and family needs are noted and responded We will use the RBS Oversight Committee and the RBS Steering Committee as our two primary forums for communication. Information will feed into these groups from the ▇▇▇▇▇▇‟s care management system and the family observations, concerns and satisfaction feedback system. The RBS Steering Committee will include representatives from the advocacy community, the schools, the courts, and the broader service network and will thus be able to gather information from those perspectives. By combining operational and CCT data from ▇▇▇▇▇▇ with the qualitative data from the family feedback system, and administrative data tracking of youth outcomes the RBS Oversight Committee will be able to continually adjust the structure, operations and services of the RBS demonstration to better meet youth and family needs.

Communication & Network. SUBSCRIBER EXPRESSLY UNDERSTANDS AND AGREES THAT IT HAS NO CONTRACTUAL RELATIONSHIP WHATSOEVER WITH THE UNDERLYING WIRELESS TELECOMMUNICATIONS SERVICE PROVIDER OR ITS AFFILIATES OR CONTRACTORS AND THAT SUBSCRIBER IS NOT A THIRD PARTY BENEFICIARY OF ANY AGREEMENT BETWEEN CALAMP AND THE UNDERLYING SERVICE PROVIDER. IN ADDITION, SUBSCRIBER ACKNOWLEDGES AND AGREES THAT THE UNDERLYING WIRELESS TELECOMMUNICATIONS SERVICE PROVIDER AND ITS AFFILIATES AND CONTRACTORS SHALL HAVE NO LEGAL, EQUITABLE, OR OTHER LIABILITY OF ANY KIND TO SUBSCRIBER AND SUBSCRIBER HEREBY WAIVES ANY AND ALL CLAIMS OR DEMANDS THEREFOR.

Communication & Network a. The SPV shall empanel 3 ICT service providers, any of whom the Developer may choose to enter into a commercial agreement as per their choice.

Communication & Network. Describe how your management team will have a communication network sufficient to insure that accurate information about issues and challenges regarding program operation or child, youth and family needs are noted and responded to in a timely and effective We will use the Open Doors Roundtable as our central forum for programmatic communication. The purpose of the Roundtable is to review implementation progress, advise, share successes, problem-solve, review evaluation data, and recommend changes to the program during the pilot and for scale-up. Information will feed into this group from the Wraparound Operations Group which includes DMH and DCFS Wraparound staff, Wraparound Quality Improvement and Training Section, ISCs, parent partners, provider quality/management entities as well as family focus groups and satisfaction feedback systems. The Open Doors Advisory Group will include DCFS, DMH, parent partners and providers as well as representatives from the advocacy community, and the broader service, oversight and community network and will thus be able to gather information from those perspectives. By combining operational data from with the qualitative data from the family feedback system and observational input from the Roundtable, the Open Doors Advisory Group will be able to continually recommend adjustments to the structure, operations and services of the Open Doors Project to better meet child and family needs and to better align with other local initiatives. On a provider level, the CFT communication structure is based on the principles of portability and nimbleness. The CFT should be small enough, yet representative enough, to be able to assemble quickly, particularly, in emergency situations and get treatment decisions made and implemented promptly. The CFT‟s operational connection with the Open Doors Roundtable is via the ISC representative and provider Wraparound management.

Communication & Network. Arbitrary point-to-point connections among the prin- cipals are assumed to be available. The network is considered to be non-private and fully asynchronous. It is controlled by the adversary. A i i ∈ { } A ƒ A i

Communication & Network. All hardware and software associated --------------------- with the PES, Satellite and certain common hub and baseband equipment, and other communication systems and devices.

Communication & Network. The availability of a communication network is in many of the SEGRID use cases important to ensure the stakeholder’s interests. Therefore we have defined the following specific security goal: CN_SG01 Ensure robustness and resilience of the Smart Grid communication network. 5 Privacy goals This chapter presents the set of privacy goals for the SEGRID use cases. In three of the SEGRID use cases personal data is collected, transferred, processed and/or stored: use case 1, use case 3, and use case 4. For these use case the steps described in section 2.4 were followed. In addition to the use case specific privacy goals, we would like to point the reader to the list of privacy and data protection targets in the annex of the DPIA Template for Smart Grid and Smart Metering Systems [21] as they present good comprehensive generic set of the privacy goals for Smart Grid developments. These targets are4: • Safeguarding quality of personal data • Legitimacy of processing sensitive personal data • Compliance with the data subject’s right to be informed • Compliance with the data subject’s right of access to data, correct and erase data • Compliance with the data subject’s right to object • Safeguarding confidentiality and security of processing • Compliance with notification requirements • Compliance with contractual requirements between data controller and data processor • Compliance with data retention requirements • Privacy by design • Privacy by default 5.1 UC1: Smart meter used for on-line reading of consumption and technical data The following information assets are considered personal data: • measurement data at short intervals from the smart meter with an identifier that can be related to a specific household customer (UC1 - scenario 1); and • switch data (switch on/off and identifier) (UC 1 – scenario 2) Data subject Customer Customer Controller DSO Energy supplier Processor DSO, Data Hub Energy supplier, DSO, Data Hub Recipient Energy supplier - The following privacy goals have been identified: UC1_PG01 Ensure that minimal measurement data is collected, transferred, processed, stored, and/or disclosed. UC1_PG02 Ensure that measurement data is hidden from plain view. 4 The authors have been informed that DPIA template will be updated based comments received during the test phase. The updated list of privacy targets has been included. See for more information: ▇▇▇▇▇://▇▇.▇▇▇▇▇▇.▇▇/energy/en/test-phase-data-protection-impact-assessment-dpia-template-smart-grid-an...

Communication & Network. On board the robot we will use CAN bus to enable communication among the nodes and the central computer. The complexity of the node can range from a simple I/O device up to an embedded computer with a CAN interface and sophisticated software. The node may also be a gateway allowing a standard computer to communicate over a USB or Ethernet port to the devices on a CAN network. Since, the environment will be electrically noisy, all microcontrollers are not on the same PCB and the bit rate is low, then each node should be equipped with a: • Central processing unit, microprocessor, or host processor o The host processor decides what the received messages mean and what messages it wants to transmit. o Sensors, actuators and control devices can be connected to the host processor. • CAN controller; often an integral part of the microcontroller o Receiving: the CAN controller stores the received serial bits from the bus until an entire message is available, which can then be fetched by the host processor (usually by the CAN controller triggering an interrupt). o Sending: the host processor sends the transmit message(s) to a CAN controller, which transmits the bits serially onto the bus when the bus is free. • Transceiver Defined by ISO 11898-2/3 Medium Access Unit [MAU] standards o Receiving: it converts the data stream from CANbus levels to levels that the CAN controller uses. It usually has protective circuitry to protect the CAN controller. o Transmitting: it converts the data stream from the CAN controller to CANbus levels. If the PLCs have embedded CAN controllers then they do not need additional electronics to interface the CAN bus.