Data Management System Sample Clauses

Data Management System. The M&E Plan shall describe the information system that shall be used to collect data, store, process and deliver information to relevant stakeholders in such a way that the Program information collected and verified pursuant to the M&E Plan is accessible and useful to those who wish to use it.
AutoNDA by SimpleDocs
Data Management System. The Contractor must: i. Verify the accuracy and reliability of data entry. ii. Use data for monitoring purposes on compliance and quality indicators. iii. Use data for program improvement. iv. Support provider agencies in adding new users. v. Ensure eligibility and IFSP events are entered in the DMS within ten (10) business days of the completed activity and no later than the fifth (5th) of the following month. vi. Ensure that all EIS Providers complete the COS Decision Tree Survey on a quarterly basis.
Data Management System. To ensure consistent and effective XXX management, SADES-K will use an online data management hub to gather, process, and report on data. In coordination with key technical staff and partners, the remote XXX team will be responsible for ensuring all indicator data is entered into a SharePoint-based online data management system that FHI 360 has effectively used for multiple civil society and media programs. The system will allow SADES-K activities to be coded against SCS Global cross-cutting themes, funding streams, and objectives; map relevant indicators and interventions; and generate automated disaggregation reports. This will contribute to the DRG Center’s information sharing and learning across programs of similar thematic focus, allowing SADES-K to pull best practices and lessons learned from other programs. Data uploaded through SharePoint is aggregated on a project dashboard which will allow SADES-K to provide real-time updates on the programs progress. Moreover, it will allow program staff to monitor key performance indicators, analyze and visualize data to make management decisions, and communicate progress to stakeholders. Partners and grantees will receive varying levels of access to the database, allowing them to submit indicator data and view data based on differing restrictions.
Data Management System. 2.2.1 All licensees will be required to sign up with ICIX North America, LLC. This service is utilized for maintenance of QA documentation including but not limited to plant audits, product specifications, letters of guarantee and certificates of insurance. 2.2.2 The current annual cost of the program to the licensee is approximately $299. Program membership includes the ability to upload requested documentation to all participating ICIX customers as allowed by vendor.
Data Management System. If a study consists of different parts which are in the responsibility of different partners it may be advisable to establish a data management system, this should be described here as well as the main functionalities and access rights. Timing of data transfer between the partners should also be described here.
Data Management System. The Other Party must: 1) Enter accurate, valid, and reliable data in the DMS no later than ten (10) business days following an event and in no case later than the fifth (5th) of the following month. 2) Enter the following required data in the DMS to maintain each child’s Part C of IDEA electronic record: i. All referrals; ii. All evaluation/assessments; iii. All Eligibility criteria; iv. Identification of FRC in the DMS at least one (1) business day prior to the FRC’s first meeting with the family; v. IFSPs, including documenting programmatic reasons and exceptional family circumstances resulting in delay in holding timely IFSP meetings (e.g. Initial IFSP meeting within forty-five (45) days from referral; IFSP review at least once every six
Data Management System. The Contractor must ensure subcontractors: (1) Enter accurate, valid, and reliable data in the DMS no later than ten (10) business days following an event and in no case later than the fifth (5th) of the following month.
AutoNDA by SimpleDocs
Data Management System. The Contractor must ensure subcontractors: (1) Enter accurate, valid and reliable data in the DMS no later than ten (10) business days following an event and in no case later than the fifth (5th) of the following month. (2) Enter the following required data in the DMS to maintain each child’s Part C of IDEA electronic record: (a) All referrals; (b) All evaluation/assessments; (c) All Eligibility criteria; (d) Identification of FRC in the DMS at least one (1) business day prior to the FRC’s first meeting with the family; (e) IFSPs, including documenting programmatic reasons and exceptional family circumstances resulting in delay in holding timely IFSP meetings (e.g. Initial IFSP meeting within forty-five (45) days from referral; IFSP review at least once every six (6) months or more frequently as needed; annual IFSP within 365 days of initial IFSP), and IFSP amendment when adding or changing services, including frequency, intensity, or duration; Initiation of services within thirty (30) days of the parent’s signature, including documenting programmatic reasons and exceptional family circumstances resulting in reasons for delay; (f) Initiation of services within thirty (30) calendar days of the parent’s signature, or the planned start date, including documenting programmatic reasons and exceptional family circumstances resulting in reasons for delay; (g) Child Outcome Summary (COS) entry and exit data reporting; (h) Transition activities: i. Transition steps and services in the IFSP Transition plan; ii. Date transition conference was held or declined; iii. Potential eligibility for Part B services in the child’s transition tab in the DMS by the first (1st) and fifteenth (15th) of every month for children between twenty-four (24) and thirty- two (32) months of age. If the child turns 32 months old after the fifteenth (15th) of the month, potential eligibility must be indicated before the first (1st) of the following month; and (i) Verify quarterly, and update as needed, the name of the local school district(s) contact person who needs to receive the school district(s) notification. (j) Enter data in the DMS to maintain a current list of all EIS staff and subcontractors including which discipline they represent, if they have current licensure/certification, and their FTE, and submit quarterly to the CLA on the form provided by the DCYF. (k) Ensure all EIS staff and subcontractors using the DMS receive the required training before assuming these duties and that...
Data Management System 

Related to Data Management System

  • Data Management Contractor will not use State data, including production data, for testing or development purposes unless authorized in writing by the State Chief Information Security Officer or delegate. Contractor will implement and maintain procedures to physically and logically segregate State data, unless otherwise explicitly authorized by the State Chief Information Security Officer or delegate.

  • 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.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Data Mining 4.1. Provider agrees not to use GLO Data for unrelated commercial purposes, advertising or advertising-related services, or for any other purpose not explicitly authorized by the GLO in this Contract or any document related thereto. 4.2. Provider agrees to take all reasonably feasible physical, technical, administrative, and procedural measures to ensure that no unauthorized use of GLO Data occurs.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • System and Data Access Services a. System. Subject to the terms and conditions of this Addendum and solely for the purpose of providing access to Fund Data as set forth herein, State Street hereby agrees to provide the Fund, or certain third parties approved by State Street that serve as the Fund`s investment advisors, investment managers or fund accountants (the "Fund Accountants") or as the Fund`s independent auditors (the "Auditor"), with access to State Street`s Multicurrency HORIZONR Accounting System and the other information systems described in Attachment A (collectively, the "System") on a remote basis solely on the computer hardware, system software and telecommunication links described in Attachment B (the "Designated Configuration") or on any designated substitute or back-up equipment configuration consented to in writing by State Street, such consent not to be unreasonably withheld.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Data Access Services State Street agrees to make available to the Fund the Data Access Services subject to the terms and conditions of this Addendum and such data access operating standards and procedures as may be issued by State Street from time to time. The Fund shall be able to access the System to (i) originate electronic instructions to State Street in order to (a) effect the transfer or movement of cash or securities held under custody by State Street or (b) transmit accounting or other information (the transactions described in (i)(a) and (i)(b) above are referred to herein as “Client Originated Electronic Financial Instructions”), and (ii) access data for the purpose of reporting and analysis, which shall all be deemed to be Data Access Services for purposes of this Addendum.

  • 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.

  • OGS Centralized Contract Terms and Conditions have been renumbered as depicted in the following chart: Current Amended Section Title 4.25 4.26 Severability 4.26 4.27 Entire Agreement

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