Data Collection and Storage. Participate Australia collects personal and statistical data of Participants for internal use and to report to the NDIA and other government agencies that require such data. This data is depersonalised and encoded when transmitted to those agencies, and all data is handled and stored in accordance with our Privacy and Confidentiality Policy. See clause 2.11.
Data Collection and Storage. The software shall record test data in a means compatible with the software’s report system and automatic testing routines. In manual mode, the operator is in control of when to store data points, unless the technical manual (see 3.
1.1) requires data recording at specific intervals. If the technical manual (see 3.
1.1) requires data storage at intervals, the software shall automatically store data at these intervals without operator intervention. In automatic mode, the developed software shall be in control of data storage/collection and intervals without operator intervention.
Data Collection and Storage. State Data and Output Data may be collected by the Contractor for the purpose of performance under this Agreement. Output Data, including but not limited to Solution Input Data, Solution Output Data, log data, etc., shall be stored exclusively within CDT’s managed cloud environments.
Data Collection and Storage. Data privacy and security obligations are implemented in Noona Healthcare procedures so that data processing is carried out according to statutory and regulatory requirements. Noona Healthcare has entered in written agreements with sub-processors regarding data privacy and security obligations in accordance with statutory and regulatory requirements. Appropriate process and technical controls are used in processing and storage of customer data according to information security risk assessment (ISO27001). Security is part of Noona Service system architecture on all levels: software architecture, data center architecture and network architecture. Noona service is secured with application level controls, firewalls, application firewalls and denial of service protection mechanisms. Identity and message information is encrypted on application level with rotating and patient specific symmetric encryption keys. Patient data audit log is collected and archived. All data is encrypted in rest and in transit. System components are segregated to dedicated subnets according to component security level. Noona Service is hosted in multitenant architecture. Access to customer data is restricted with authentication, authorization, cryptographic access controls, role access controls and customer user group access controls. Noona Service system components are deployed in redundant configuration to ensure availability in case of system component failure. System data storages are backed up daily. In the event of storage failure customer data can be recovered from backups. Noona healthcare has disaster recovery procedure to recover from system wide technical failure or data corruption. The following sub-contractors are used to provide Noona Service: - Noona mobile service is hosted in Amazon AWS in Europe, Ireland. - User Analytics are processed in Microsoft Azure in Europe, Ireland. - Log processing services are provided by Sumologic in Europe Data will be collected by Xxxxx and stored centrally by FORTH, cleaned-homogenized, and shared with ICCS and NHG to jointly conduct analyses. Data will be extracted at different time phases during the project (i.e. after the M6 data is complete) to conduct interim analyses and quality checks. Requests for data sharing by other partners to perform additional analyses should be directed to the PCC.
Data Collection and Storage. A. The NAC shall have the ability to collect data for any property of any object and store this data for future use.
B. The data collection shall be performed by log objects, resident in the NAC that shall have, at a minimum, the following configurable properties:
1. Designating the log as interval or deviation.
2. For interval logs, the object shall be configured for time of day, day of week and the sample collection interval.
3. For deviation logs, the object shall be configured for the deviation of a variable to a fixed value. This value, when reached, will initiate logging of the object.
4. For all logs, provide the ability to set the maximum number of data stores for the log and to set whether the log will stop collecting when full, or rollover the data on a first-in, first- out basis.
5. Each log shall have the ability to have its data cleared on a time-based event or by a user-defined event or action.
C. All log data shall be stored in a relational database in the NAC and the data shall be accessed from the Web Supervisor Server or a standard Web browser.
D. All log data, when accessed from the Web Supervisor Server, shall be capable of being manipulated using standard SQL statements.
Data Collection and Storage. MOTI collects, stores, and uses System User data on an on-going basis and in strict accordance with the MOTI Privacy Policy. MOTI reserves the right to in the future commercialize such data, subject to it being anonymised and always subject to the provisions of the MOTI Privacy Policy.
Data Collection and Storage. As per the agreement between the OCE and the APMA, the APMA is subject to the Data and Information Sharing Protocol (“DISP”). The Supplier confirms that they have read and understood the DISP and its appendices, attached herein and marked as Appendix 1 to this Agreement.
Data Collection and Storage. The case unit will be analysed through the collection of primary and secondary data. Primary data sources are interviews, direct observation, and informal discussions. Secondary data sources will mainly be a set of documents of the firm that are produced as a consequence of the DiDIY transformation. Before starting the collection of primary data (Xxxxx et al. 1998), some preliminary background information will be collected in order to help the interviewer during the data collection process. The preliminary information will come from the Internet web site of the firm and some supplementary information will be given by the organizational interviewee. Together with a representative of each firm, the names and the positions of all the potential participants will be identified and contacted for an interview (Xxxxx et al. 1998). The interviews will be semi-structured interviews (Xxxxxxxxx 1964; Emory 1980). In order to operationalise the theoretical constructs and ground the findings, whenever possible, will be interviewed key representatives of a “worker”. The interview will be focused on introducing the main themes and sub-themes to discuss together with the interviewee. At the beginning of each interview an introduction on the reasons and the objects of the interview will be performed (Xxxxxxxx & Xxxxxx 1992, p. 75; Xxxxx & Xxxxxxxx 1994). This explanation will reduce the researcher effects at the site, which could bias the data collection (Xxxxx et al. 1998, Xxxxx & Xxxxxxxx 1994). The interview guide will be designed to gather the characteristics of the interviewee and what is her/his view. In fact, the interview guide will include a first draft measure of IT capability and a list of questions about the other constructs under investigation. Since the research will be highly exploratory, a pilot-case will be generated and subsequently a multiple case study, involving other firms (Yin 2003; Xxxx & Xxxx 2003), will follow. To build a triangulation and to give rigor to the study other sources of evidence will be included: direct observations, historical archive records, physical artefacts. The quantitative data will be collected directly on a copy of the interview guide by the interviewer, while the qualitative data produced by the interview will be synthesized in a report, immediately after each interview. These reports, the quantitative data collected on the direct observation and the collected secondary data will be archived in a repository. To increase homo...
Data Collection and Storage. For each “ABCT Driver,” the Clearinghouse shall obtain the “Required Data” upon each of the “Triggering Events.”
Data Collection and Storage. § 15.1 For security reasons, the access data (ID of the key which allows conclusions to be drawn about the tenant, access time and date are stored. The tenant agrees to this.
§ 15.2 For security reasons, the wine storage facilities are video-monitored and the footage is stored. The tenant agrees to this.
