Data Collection Procedures and Data Analysis Sample Clauses

Data Collection Procedures and Data Analysis. Before the data collection procedure, the researcher developed interview protocols for directing the participants with the questions (see Appendix B). Next, the research’s permission was taken at two levels: gatekeeper permission (instructor) and participants’ permission. The recording was essential for collecting detailed and accurate data on participants’ experiences. Therefore, following the research protocol, the online interviews were recorded with the participants’ permission. As the study involved semi-structured interviews, the researcher asked participants follow-up questions. Due to participants’ preference and convenience, the interview applied Kazakh and Russian languages. For further data analysis, all interview recordings were transcribed and translated into English. The transcribed interview recordings underwent preliminary exploratory analysis to organize the results into appropriate categories and subtopics. As a result, the researcher identified possible links between the categories by following the research purpose and the research questions. Since the research comprises epistemological research questions, the first cycle coding method applied descriptive coding to categorize the data. After sorting the identified categories, the researcher uses pattern coding for the second cycle of coding. According to Xxxxx (2002), pattern coding focuses on the similarities, differences, causes, frequency, sequence, and correspondence of initially examined codes and identifies their relationship. Therefore, the researcher synthesized the trends to combine participants’ reflections on the process, context, and content into connected patterns. The researcher started analyzing the data after identifying the patterns. According to Xxxxxx et al. (2019), reliability and generalizability are considered as a benchmark for evaluating research outcomes. However, since the research focused on the qualitative data and interprets the unique case of entrepreneurship course in fall term 2020, the case cannot be replicated, and the research findings cannot be generalized (Xxxxxx et al., 2000; Merriam, 1988, as cited in Xxxxxx et al., 2019). Thus, in the context of current research, the assessment of reliability and generalizability cannot be applicable and would be irrelevant.
Sample 1
AutoNDA by SimpleDocs

Related to Data Collection Procedures and Data Analysis

  • Data Analysis In the meeting, the analysis that has led the College President to conclude that a reduction- in-force in the FSA at that College may be necessary will be shared. The analysis will include but is not limited to the following: ● Relationship of the FSA to the mission, vision, values, and strategic plan of the College and district ● External requirement for the services provided by the FSA such as accreditation or intergovernmental agreements ● Annual instructional load (as applicable) ● Percentage of annual instructional load taught by Residential Faculty (as applicable) ● Fall Full-Time Student Equivalent (FFTE) inclusive of dual enrollment ● Number of Residential Faculty teaching/working in the FSA ● Number of Residential Faculty whose primary FSA is the FSA being analyzed ● Revenue trends over five years for the FSA including but not limited to tuition and fees ● Expenditure trends over five years for the FSA including but not limited to personnel and capital ● Account balances for any fees accounts within the FSA ● Cost/benefit analysis of reducing all non-Residential Faculty plus one Residential Faculty within the FSA ● An explanation of the problem that reducing the number of faculty in the FSA would solve ● The list of potential Residential Faculty that are at risk of layoff as determined by the Vice Chancellor of Human Resources ● Other relevant information, as requested

  • DATA COLLECTION AND ANALYSIS The goal of this task is to collect operational data from the project, to analyze that data for economic and environmental impacts, and to include the data and analysis in the Final Report. Formulas will be provided for calculations. A Final Report data collection template will be provided by the Energy Commission. The Recipient shall: • Develop data collection test plan. • Troubleshoot any issues identified. • Collect data, information, and analysis and develop a Final Report which includes: o Total gross project costs. o Length of time from award of bus(es) to project completion. o Fuel usage before and after the project.

  • Data Collection Some downloaded software included in the Materials may generate and collect information about the software and usage and transmit it to Intel to help improve Intel’s products and services. This collected information may include product name, product version, time of event collection, license type, support type, installation status, hardware and software performance, and use. 9.

  • Induction Procedures a) The parties to this Agreement acknowledge that it is in the interests of the industry that all new employees and employers on a building project understand their obligations to this Agreement and are introduced to their jobs in a manner which will help them work safely and efficiently.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

  • Third Party Verification 4.8.1 The SPD shall be further required to provide entry to the site of the Power Project free of all encumbrances at all times during the Term of the Agreement to SECI and a third Party nominated by any Indian Governmental Instrumentality for inspection and verification of the works being carried out by the SPD at the site of the Power Project.

  • Billing and Collection Customers BellSouth currently has in effect numerous billing and collection agreements with various interexchange carriers and billing clearing houses and as such these billing and collection customers (“B&C Customers”) query BellSouth’s LIDB to determine whether to accept various billing options from End Users. Until such time as BellSouth implements in its LIDB and its supporting systems the means to differentiate Comm South’s data from BellSouth’s data, the following shall apply:

  • Data Collection and Reporting 1. Grantee shall develop and use a local reporting unit that will provide an assigned location for all clients served within the Hospital. This information shall also be entered into Client Assignment and Registration (CARE)when reporting on beds utilized at the Hospital.

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