Protocols – Data Provider Sample Clauses

Protocols – Data Provider. The OnTime data source is the so called Data Provider and, in this case, it is not used the standard events publish/subscribe mechanism. All data requests/responses are synchronous and don’t provide a standard data struc- ture. It depends on the nature of the request/response. When required, the related payload is referred as DataRequestPayload and DataResponsePayload. The complete data requests/responses list is presented in the following table. DisruptionsListRequest HMI=>Sys To request the disruptions list to the system (see DisruptionsLis- tResponse) Yes SlowdownsListRequest HMI=>Sys To request the slowdowns list to the system (see SlowdownsLis- tResponse) Yes LinksListRequest HMI=>Sys To request the slowdowns list to the system (see LinksLis- tResponse) Yes ConstraintsListRequest HMI=>Sys To request the slowdowns list to the system (see ConstraintsLis- tResponse) Yes PossibleTrainPathsRequest HMI=>Sys To request a list of possible train path (see PossibleTrainPathsRe- sponse) Next PossibileConflictSolu- tionsRequest HMI=>Sys To request a list of possible con- flict solutions (see PossibileCon- flictSolutionsResponse) Next DisruptionsListResponse Sys=>HMI To send the list of disruptions (see DisruptionsListRequest) Yes SlowdownsListResponse Sys=>HMI To send the list of slowdowns (see SlowdownsListRequest) Yes LinksListResponse Sys=>HMI To send the list of links (see LinksListRequest) Yes ConstraintsListResponse Sys=>HMI To send the list of constraints (see ConstraintsListRequest) Yes PossibleTrainPathsResponse Sys=>HMI To send a list a possible paths for a train (see PossibleTrain- PathsRequest) Next PossibileConflictSolu- tionsResponse Sys=>HMI To send a list of possible conflict solutions (see PossibileConflictSo- lutionsRequest) Next The meaning of the “type” column is the same of the previous table. Because of the importance of cost functions in the OnTime project, the description of the requests/responses related to them are described in a separate paragraph (3.3.2).
View Source

Related to Protocols – Data Provider

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Clinical Data and Regulatory Compliance The preclinical tests and clinical trials, and other studies (collectively, “studies”) that are described in, or the results of which are referred to in, the Registration Statement or the Prospectus were and, if still pending, are being conducted in all material respects in accordance with the protocols, procedures and controls designed and approved for such studies and with standard medical and scientific research procedures; each description of the results of such studies is accurate and complete in all material respects and fairly presents the data derived from such studies, and the Company and its subsidiaries have no knowledge of any other studies the results of which are inconsistent with, or otherwise call into question, the results described or referred to in the Registration Statement or the Prospectus; the Company and its subsidiaries have made all such filings and obtained all such approvals as may be required by the Food and Drug Administration of the U.S. Department of Health and Human Services or any committee thereof or from any other U.S. or foreign government or drug or medical device regulatory agency, or health care facility Institutional Review Board (collectively, the “Regulatory Agencies”); neither the Company nor any of its subsidiaries has received any notice of, or correspondence from, any Regulatory Agency requiring the termination, suspension or modification of any clinical trials that are described or referred to in the Registration Statement or the Prospectus; and the Company and its subsidiaries have each operated and currently are in compliance in all material respects with all applicable rules, regulations and policies of the Regulatory Agencies.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Contractor Key Personnel ‌ The Contractor shall assign a Corporate OASIS SB Program Manager (COPM) and Corporate OASIS SB Contract Manager (COCM) as Contractor Key Personnel to represent the Contractor as primary points-of-contact to resolve issues, perform administrative duties, and other functions that may arise relating to OASIS SB and task orders solicited and awarded under OASIS SB. Additional Key Personnel requirements may be designated by the OCO at the task order level. There is no minimum qualification requirements established for Contractor Key Personnel. Additionally, Contractor Key Personnel do not have to be full-time positions; however, the Contractor Key Personnel are expected to be fully proficient in the performance of their duties. The Contractor shall ensure that the OASIS SB CO has current point-of-contact information for both the COPM and COCM. In the event of a change to Contractor Key Personnel, the Contractor shall notify the OASIS SB CO and provide all Point of Contact information for the new Key Personnel within 5 calendar days of the change. All costs associated with Contractor Key Personnel duties shall be handled in accordance with the Contractor’s standard accounting practices; however, no costs for Contractor Key Personnel may be billed to the OASIS Program Office. Failure of Contractor Key Personnel to effectively and efficiently perform their duties will be construed as conduct detrimental to contract performance and may result in activation of Dormant Status and/or Off-Ramping (See Sections H.16. and H.17.).