Log Reviews All systems processing and/or storing PHI COUNTY discloses to 11 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY 12 must have a routine procedure in place to review system logs for unauthorized access.
Project Review A. Programmatic Allowances
1. If FEMA determines that the entire scope of an Undertaking conforms to one or more allowances in Appendix B of this Agreement, with determinations for Tier II Allowances being made by SOI-qualified staff, FEMA shall complete the Section 106 review process by documenting this determination in the project file, without SHPO review or notification.
2. If the Undertaking involves a National Historic Landmark (NHL), FEMA shall notify the SHPO, participating Tribe(s), and the NPS NHL Program Manager of the NPS Midwest Regional Office that the Undertaking conforms to one or more allowances. FEMA shall provide information about the proposed scope of work for the Undertaking and the allowance(s) enabling FEMA’s determination.
3. If FEMA determines any portion of an Undertaking’s scope of work does not conform to one or more allowances listed in Appendix B, FEMA shall conduct expedited or standard Section 106 review, as appropriate, for the entire Undertaking in accordance with Stipulation II.B, Expedited Review for Emergency Undertakings, or Stipulation II.C, Standard Project Review.
4. Allowances may be revised and new allowances may be added to this Agreement in accordance with Stipulation IV.A.3, Amendments.
B. Expedited Review for Emergency Undertakings
Review Scope The parties confirm that the Asset Representations Review is not responsible for (a) reviewing the Receivables for compliance with the representations and warranties under the Transaction Documents, except as described in this Agreement or (b) determining whether noncompliance with the representations and warranties constitutes a breach of the Eligibility Representations. For the avoidance of doubt, the parties confirm that the review is not designed to determine why an Obligor is delinquent or the creditworthiness of the Obligor, either at the time of any Asset Review or at the time of origination of the related Receivable. Further, the Asset Review is not designed to establish cause, materiality or recourse for any Test Fail (as defined in Section 3.05).
Exclusion Review Notwithstanding any provision of Title 42 of the United States Code or Title 42 of the Code of Federal Regulations, the only issues in a proceeding for exclusion based on a material breach of this CIA shall be whether Good Shepherd was in material breach of this CIA and, if so, whether:
a. Good Shepherd cured such breach within 30 days of its receipt of the Notice of Material Breach; or
b. the alleged material breach could not have been cured within the 30-day period, but that, during the 30-day period following Good Shepherd’s receipt of the Notice of Material Breach: (i) Good Shepherd had begun to take action to cure the material breach; (ii) Good Shepherd pursued such action with due diligence; and (iii) Good Shepherd provided to OIG a reasonable timetable for curing the material breach. For purposes of the exclusion herein, exclusion shall take effect only after an ALJ decision favorable to OIG, or, if the ALJ rules for Good Shepherd, only after a DAB decision in favor of OIG. Good Shepherd’s election of its contractual right to appeal to the DAB shall not abrogate OIG’s authority to exclude Good Shepherd upon the issuance of an ALJ’s decision in favor of OIG. If the ALJ sustains the determination of OIG and determines that exclusion is authorized, such exclusion shall take effect 20 days after the ALJ issues such a decision, notwithstanding that Good Shepherd may request review of the ALJ decision by the DAB. If the DAB finds in favor of OIG after an ALJ decision adverse to OIG, the exclusion shall take effect 20 days after the DAB decision. Good Shepherd shall waive its right to any notice of such an exclusion if a decision upholding the exclusion is rendered by the ALJ or DAB. If the DAB finds in favor of Good Shepherd, Good Shepherd shall be reinstated effective on the date of the original exclusion.
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: 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 1.50 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 .0150. 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. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.
Independent Review Contractor shall provide the Secretary of ADS/CIO an independent expert review of any Agency recommendation for any information technology activity when its total cost is $1,000,000.00 or greater or when CIO requires one. The State has identified two sub-categories for Independent Reviews, Standard and Complex. The State will identify in the SOW RFP the sub-category they are seeking. State shall not consider bids greater than the maximum value indicated below for this category. Standard Independent Review $25,000 Maximum Complex Independent Review $50,000 Maximum Per Vermont statute 3 V.S.A. 2222, The Secretary of Administration shall obtain independent expert review of any recommendation for any information technology initiated after July 1, 1996, as information technology activity is defined by subdivision (a) (10), when its total cost is $1,000,000 or greater or when required by the State Chief Information Officer. Documentation of this independent review shall be included when plans are submitted for review pursuant to subdivisions (a)(9) and (10) of this section. The independent review shall include: • An acquisition cost assessment • A technology architecture review • An implementation plan assessment • A cost analysis and model for benefit analysis • A procurement negotiation advisory services contract • An impact analysis on net operating costs for the agency carrying out the activity In addition, from time to time special reviews of the advisability and feasibility of certain types of IT strategies may be required. Following are Requirements and Capabilities for this Service: • Identify acquisition and lifecycle costs; • Assess wide area network (WAN) and/or local area network (LAN) impact; • Assess risks and/or review technical risk assessments of an IT project including security, data classification(s), subsystem designs, architectures, and computer systems in terms of their impact on costs, benefits, schedule and technical performance; • Assess, evaluate and critically review implementation plans, e.g.: • Adequacy of support for conversion and implementation activities • Adequacy of department and partner staff to provide Project Management • Adequacy of planned testing procedures • Acceptance/readiness of staff • Schedule soundness • Adequacy of training pre and post project • Assess proposed technical architecture to validate conformance to the State’s “strategic direction.” • Insure system use toolsets and strategies are consistent with State Chief Information Officer (CIO) policies, including security and digital records management; • Assess the architecture of the proposed hardware and software with regard to security and systems integration with other applications within the Department, and within the Agency, and existing or planned Enterprise Applications; • Perform cost and schedule risk assessments to support various alternatives to meet mission need, recommend alternative courses of action when one or more interdependent segment(s) or phase(s) experience a delay, and recommend opportunities for new technology insertions; • Assess the architecture of the proposed hardware and software with regard to the state of the art in this technology. • Assess a project’s backup/recovery strategy and the project’s disaster recovery plans for adequacy and conformance to State policy. • Evaluate the ability of a proposed solution to meet the needs for which the solution has been proposed, define the ability of the operational and user staff to integrate this solution into their work.
Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.
Claims Review Population A description of the Population subject to the Claims Review.
Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.
Utilization Review NOTE: The Utilization Review process does not apply to Services that are not covered by Blue Shield because of a coverage determination made by Medicare. State law requires that health plans disclose to Subscribers and health plan providers the process used to authorize or deny health care services un- der the plan. Blue Shield has completed documen- tation of this process ("Utilization Review"), as required under Section 1363.5 of the California Health and Safety Code. To request a copy of the document describing this Utilization Review pro- cess, call the Customer Service Department at the telephone number indicated on your Identification Card.
