Licensed Documentation If commercially available, Licensee shall have the option to require the Contractor to deliver, at Contractor’s expense: (i) one (1) hard copy and one (1) master electronic copy of the Documentation in a mutually agreeable format; (ii) based on hard copy instructions for access by downloading from the Internet
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
Design Review
(a) Where so specified in Schedule A (Scope of Goods and Services) or as otherwise instructed by the City, the Supplier shall submit design-related Documentation for review by the City, and shall not proceed with work on the basis of such design Documentation until the City’s approval of such Documentation has been received in writing.
(b) None of:
(i) the submission of Documentation to the City by the Supplier;
(ii) its examination by or on behalf of the City; or
(iii) the making of any comment thereon (including any approval thereof) shall in any way relieve the Supplier of any of its obligations under this Agreement or of its duty to take reasonable steps to ensure the accuracy and correctness of such Documentation, and its suitability to the matter to which it relates.
Design Development Documents See Section 2, Part 1, Article 2.1.5.
MSAA Indicator Technical Specification Document This Agreement shall be interpreted with reference to the MSAA Indicator Technical Specifications document.
Statement of Work The Statement of Work to which Grantee is bound is incorporated into and made a part of this Grant Agreement for all purposes and included as Attachment A.
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.
Program Overview Microsoft extends to eligible partners the opportunity to participate in the Program referenced above subject to these Program Terms & Conditions (“Program Terms”). Each entity participating in the Program is hereinafter referred to as a “Participant.” Participation in the Program is voluntary. The Program is governed by the Program Terms, which incorporate by reference the Microsoft Partner Network Agreement (as in effect between Microsoft and Participant, the “MPN Agreement”). Capitalized terms used but not defined in these Program Terms have the meanings assigned to them in the MPN Agreement. These Program Terms are subject to local requirements and may vary by jurisdiction, and Participant retains sole discretion to set pricing for sales of applicable products.
Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.
Statistical Sampling Documentation a. A copy of the printout of the random numbers generated by the “Random Numbers” function of the statistical sampling software used by the IRO.
b. A description or identification of the statistical sampling software package used by the IRO.
