Data Sharing Process Sample Clauses

Data Sharing Process. The data sharing process is as follows: In addition to the documentary evidence provided prior to the inspection, inspectors will look at detention records such as observation books, detainee management systems, performance data, daily wing entries, care plans and detention and training orders, to corroborate their findings. The inspection team may also gather photographic evidence to illustrate conditions that cannot be adequately described or to emphasise a finding, governed by protocols agreed with the Home Office departments in their respective MoUs. The majority of HO data shared with HMI Prisons will be sent via secure, auditable email accounts - either from HO email mailboxes or from those of contracted commercial suppliers who run HO detention facilities or provide other support services under contract. Where personal data is shared in other ways, either in hard-copy or in other media such as encrypted USB storage devices to share CCTV footage, each party should ensure that a written record is made of the information that has been shared and taken off site by HMI Prisons’ inspectors. In most instances the written record will be in the form of an email between the parties confirming that specific personal data has been requested, shared or received. The manner in which inspections are conducted is set out in an inspection framework published on the HMI Prisons website. The inspection team will ask the establishment to make available a range of information to assist the inspection process and the documentation will be delivered to the team’s base room for the first day of the inspection. Inspectors will be familiar with the information provided which relates to their inspection areas. The documents will be checked before further information is requested from the establishment. Every effort is made to keep requests for documentary evidence and data to a minimum.
AutoNDA by SimpleDocs
Data Sharing Process. The information relating to the business enquiry will be recorded and shared on an ongoing basis.
Data Sharing Process. This section details how the data sharing will be carried out, including how the data will be collected from the adoption agencies. 4.2.1 Transferring Data to the Register
Data Sharing Process. Immediate Urgent Referral Where a young person comes to police notice as a consequence of a live proactive operation, initial referrals are made to R & R verbally (by telephone) for reasons of expedience. This is because the young person may be in need of immediate support and assistance. R & R operate a service where they will attend the location where the young person has been found and assist them to get home. Other referrals In all other circumstances, information will be shared by the MPS file system ‘Box’. Box is a cloud based storage system utilised by the MPS. Sharing will be given at ‘viewer’ level only and access will only be given to those who require it via the Trusted Partner element. It is envisaged that there will be monthly meetings between Operation Orochi and R & R, and information will be shared in advance of these meetings to enable an informed discussion. All MPS data to be shared by box. Data will only be shared on the authority of the Operation Orochi SPOC (Lead Responsible Officer), who will be responsible for reviewing data prior to it being shared Data will be shared with a SPOC in R & R (Operations Manager) Operation Orochi analysts will be responsible for interrogating indices to identify relevant data to be shared. This will be primarily sourced from Merlin (to be replaced by CONNECT) and Operation Orochi’s Box folder containing details of operations in which exploited young people were encountered Information shared by the MPS will be recorded on CrimInt (to be replaced by CONNECT) by the analyst compiling the data to be shared once authority for sharing has been granted All data will be handled in accordance with the requirements of the relevant Government Security Classificationno data with a classification higher than OFFICIAL will be shared. Data will only be retained by partners for as long it is necessary to do so, in all cases remaining compliant with both organisational policy and legislation regarding the retention of data. The R & R SPOC (Operations Manager) will be responsible for notifying the Operation Orochi SPOC of any changes or perceived inaccuracies in the data provided, and the Orochi SPOC is responsible for ensuring that MPS systems are updated where appropriate. No data will be shared outside the EEA at any time.

Related to Data Sharing Process

  • Data Sharing The GRANTEE BENEFICIARY agrees to share data with the AGENCY as deemed necessary by AGENCY, in its sole discretion, for expenditure validation, trend review, and performance monitoring.

  • Data shared with Subcontractors If DSHS Data provided under this Contract is to be shared with a subcontractor, the Contract with the subcontractor must include all of the data security provisions within this Contract and within any amendments, attachments, or exhibits within this Contract. If the Contractor cannot protect the Data as articulated within this Contract, then the contract with the sub- Contractor must be submitted to the DSHS Contact specified for this contract for review and approval.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

  • Computer Equipment Recycling Program If this Contract is for the purchase or lease of computer equipment, then Contractor certifies that it is in compliance with Subchapter Y, Chapter 361 of the Texas Health and Safety Code related to the Computer Equipment Recycling Program and the Texas Commission on Environmental Quality rules in 30 TAC Chapter 328.

  • Improvement Plan A detailed, written plan collaboratively developed between the teacher and evaluator, utilized when a teacher receives an Evaluation Rating of ineffective. The approved form for the Improvement Plan is attached to this agreement as Appendix .

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Implementation of Corrective Action Plan After the Corrective Action Plan is finalized, the Purchasers shall use reasonable best efforts to implement the finalized Corrective Action Plan on the timeline set forth therein and provide periodic reports (as provided for therein) to the Sellers on the status of their implementation of the Corrective Action Plan.

  • Emergency Mode Operation Plan Contractor must establish a documented plan to enable continuation of critical business processes and protection of the security of electronic County PHI or PI in the event of an emergency. Emergency means any circumstance or situation that causes normal computer operations to become unavailable for use in performing the work required under this Agreement for more than twenty-four (24) hours.

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