DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.
DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A.
b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915.
c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.
Data Subject Requests To the extent legally permitted, Okta shall promptly notify Customer if Okta receives a request from a Data Subject to exercise the Data Subject's right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, object to the Processing, or its right not to be subject to an automated individual decision making (“Data Subject Request”). Factoring into account the nature of the Processing, Okta shall assist Customer by appropriate organizational and technical measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Service, does not have the ability to address a Data Subject Request, Okta shall, upon Customer’s request, provide commercially- reasonable efforts to assist Customer in responding to such Data Subject Request, to the extent that Okta is legally authorized to do so, and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Okta’s provision of such assistance.
Interconnection Request The Interconnection Customer’s request, in accordance with the Tariff, to interconnect a new Small Generating Facility, or to materially increase the capacity of, or make a material modification to the operating characteristics of, an existing Small Generating Facility that is interconnected with the New York State Transmission System or the Distribution System. For the purposes of this Agreement, this definition of Interconnection Request shall supersede the definition of Interconnection Request set out in Attachment X to the ISO OATT. Interconnection Study – Any study required to be performed under Sections 32.2 or 32.3 of the SGIP. Material Modification – A modification that has a material impact on the cost or timing of any Interconnection Request with a later queue priority date. New York State Transmission System – The entire New York State electric transmission system, which includes: (i) the Transmission Facilities under ISO Operational Control; (ii) the Transmission Facilities Requiring ISO Notification; and (iii) all remaining transmission facilities within the New York Control Area. NYISO Deliverability Interconnection Standard – The standard that must be met, unless otherwise provided for by Attachment S to the ISO OATT, by (i) any generation facility larger than 2MW in order for that facility to obtain XXXX; (ii) any Class Year Transmission Project proposing to interconnect to the New York State Transmission System and receive Unforced Capacity Delivery Rights; (iii) any entity requesting External XXXX Rights, and (iv) any entity requesting a XXXX transfer pursuant to Section 25.9.5 of Attachment S to the ISO OATT. To meet the NYISO Deliverability Interconnection Standard, the Interconnection Customer must, in accordance with the rules in Attachment S to the ISO OATT, fund or commit to fund any System Deliverability Upgrades identified for its project in the Class Year Deliverability Study. NYISO Minimum Interconnection Standard – The reliability standard that must be met by any generation facility or Class Year Transmission Project that is subject to NYISO’s Large Facility Interconnection Procedures in Attachment X to the ISO OATT or the NYISO’s Small Generator Interconnection Procedures in this Attachment Z, that is proposing to connect to the New York State Transmission System or Distribution System, to obtain ERIS. The Minimum Interconnection Standard is designed to ensure reliable access by the proposed project to the New York State Transmission System or to the Distribution System. The Minimum Interconnection Standard does not impose any deliverability test or deliverability requirement on the proposed interconnection. Operating Requirements – Any operating and technical requirements that may be applicable due to Regional Transmission Organization, Independent System Operator, control area, or the Connecting Transmission Owner’s requirements, including those set forth in the Small Generator Interconnection Agreement. Operating Requirements shall include Applicable Reliability Standards. Party or Parties – The NYISO, Connecting Transmission Owner, Interconnection Customer or any combination of the above. Point of Interconnection – The point where the Interconnection Facilities connect with the New York State Transmission System or the Distribution System. Reasonable Efforts – With respect to an action required to be attempted or taken by a Party under this Agreement, efforts that are timely and consistent with Good Utility Practice and are otherwise substantially equivalent to those a Party would use to protect its own interests. Small Generating Facility – The Interconnection Customer’s facility, no larger than 20 MW for the production and/or storage for later injection of electricity identified in the Interconnection Request if proposing to interconnect to the New York State Transmission System or Distribution System, but shall not include (i) facilities proposing to simply receive power from the New York State Transmission System or the Distribution System; (ii) facilities proposing to interconnect to the New York State Transmission System or the Distribution System made solely for the purpose of generation with no wholesale sale for resale nor to net metering; (iii) facilities proposing to the New York State Transmission System or the Distribution System made solely for the purpose of net metering; (iv) facilities proposing to interconnect to LIPA’s distribution facilities; and (v) the Interconnection Customer’s Interconnection Facilities. A facility will be treated as a single Small Generating Facility if all units within the facility are behind a single facility meter, even if such units are different technology types. System Deliverability Upgrades – The least costly configuration of commercially available components of electrical equipment that can be used, consistent with Good Utility Practice and Applicable Reliability Requirements, to make the modifications or additions to the existing New York State Transmission System that are required for the proposed project to connect reliably to the system in a manner that meets the NYISO Deliverability Interconnection Standard for Capacity Resource Interconnection Service. System Upgrade Facilities – The least costly configuration of commercially available components of electrical equipment that can be used, consistent with Good Utility Practice and Applicable Reliability Requirements to make the modifications to the existing transmission system that are required to maintain system reliability due to: (i) changes in the system, including such changes as load growth and changes in load pattern, to be addressed in the form of generic generation or transmission projects; and (ii) proposed interconnections. In the case of proposed interconnection projects, System Upgrade Facilities are the modification or additions to the existing New York State Transmission System that are required for the proposed project to connect reliably to the system in a manner that meets the NYISO Minimum Interconnection Standard. Tariff – The NYISO’s Open Access Transmission Tariff, as filed with the FERC, and as amended or supplemented from time to time, or any successor tariff. Trial Operation shall mean the period during which Interconnection Customer is engaged in on- site test operations and commissioning of the Small Generating Facility prior to Commercial Operation. Upgrades – The required additions and modifications to the Connecting Transmission Owner’s portion of the New York State Transmission System or the Distribution System at or beyond the Point of Interconnection. Upgrades may be System Upgrade Facilities or System Deliverability Upgrades Distribution Upgrades. Upgrades do not include Interconnection Facilities.
Authorized Sub-processors Customer agrees that MailChimp may engage Sub-processors to process Customer Data on Customer's behalf. The Sub-processors currently engaged by MailChimp and authorized by Customer are listed in Annex A.
Customer Materials Subject to Section 4(a), all right, title and interest (including all Intellectual Property Rights) in and to the Customer Materials are owned by Customer or Customer’s suppliers.
Unauthorized Access Notification XXX shall notify Provider promptly of any known unauthorized access. XXX will assist Provider in any efforts by Provider to investigate and respond to any unauthorized access.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
Submittals Submittals required by the Contract Documents shall be prepared specifically for the Work by the Contractor to illustrate some portion of the Work. Submittals are not Contract Documents.
Contract Task Order A- E shall be assigned work via a task order by COUNTY which shall subsequently be referred to as the “Contract Task Order” (hereinafter “CTO”). A CTO for each project shall be developed by A-E in conjunction with COUNTY Project Management staff. The County Project Manager shall manage all A-E’s work including monitoring the CTO work schedule, quality of deliverables, review of invoiced amounts, adherence to set budget, and internal review of submittal packages. A-E shall follow all requirements as outlined in the CTO; this general Scope of Work, the project specific Scope Statement, and the Architect-Engineer Guide (Rev July 2018). The CTO shall include a detailed Scope Statement, describing tasks to be performed with a specific list of deliverables for each task, schedule of work and cost to complete the work. The schedule of work shall allow enough time for meetings with County Management staff to review the work progress, provide technical and policy direction, resolve problems and ensure adherence to the work completion schedule. The CTO shall include a cover sheet provided by County Project Management staff with the appropriate signature blocks and contract information. Once both Parties agree, and all Parties have signed the CTO, County Management staff shall provide A-E with a Notice to Proceed (NTP) to begin work. A-E shall submit all plans, reports and other documents produced under the CTO to the assigned County Project Manager within the timeframe indicated in the CTO or as directed by County Project Management staff.
