Program Evaluation The School District and the College will develop a plan for the evaluation of the Dual Credit program to be completed each year. The evaluation will include, but is not limited to, disaggregated attendance and retention rates, GPA of high-school-credit-only courses and college courses, satisfactory progress in college courses, state assessment results, SAT/ACT, as applicable, TSIA readiness by grade level, and adequate progress toward the college-readiness of the students in the program. The School District commits to collecting longitudinal data as specified by the College, and making data and performance outcomes available to the College upon request. HB 1638 and SACSCOC require the collection of data points to be longitudinally captured by the School District, in collaboration with the College, will include, at minimum: student enrollment, GPA, retention, persistence, completion, transfer and scholarships. School District will provide parent contact and demographic information to the College upon request for targeted marketing of degree completion or workforce development information to parents of Students. School District agrees to obtain valid FERPA releases drafted to support the supply of such data if deemed required by counsel to either School District or the College. The College conducts and reports regular and ongoing evaluations of the Dual Credit program effectiveness and uses the results for continuous improvement.
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.
FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-‐xxxxxx-‐icann-‐registry-‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).
TECHNICAL EVALUATION (a) Detailed technical evaluation shall be carried out by Purchase Committee pursuant to conditions in the tender document to determine the substantial responsiveness of each tender. For this clause, the substantially responsive bid is one that conforms to all the eligibility and terms and condition of the tender without any material deviation. The Institute’s determination of bid’s responsiveness is to be based on the contents of the bid itself without recourse to extrinsic evidence. The Institute shall evaluate the technical bids also to determine whether they are complete, whether required sureties have been furnished, whether the documents have been properly signed and whether the bids are in order. (b) The technical evaluation committee may call the responsive bidders for discussion or presentation to facilitate and assess their understanding of the scope of work and its execution. However, the committee shall have sole discretion to call for discussion / presentation. (c) Financial bids of only those bidders who qualify the technical criteria will be opened provided all other requirements are fulfilled. (d) AIIMS Jodhpur shall have right to accept or reject any or all tenders without assigning any reasons thereof.
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.
Diversity Report The Contractor shall report to each Customer, spend with certified and other minority business enterprises. These reports shall include the period covered, the name, minority code and Federal Employer Identification Number of each minority business utilized during the period, Commodities provided by the minority business enterprise, and the amount paid to each minority business on behalf of each purchasing agency ordering under the terms of this Contract.
Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
CMI/RAI MDS Report Recognizing the mutual objective of quality resident care, the Employer agrees to meet through the Union Management Committee with the Union as soon as practicable after the receipt of the annual CMI/RAI MDS report. The Employer agrees to provide the Union with staffing levels, and staffing mix information; the impact of related payroll costs on staffing levels and a written notice of the CMI/RAI MDS report for the facility. The purpose of this meeting is to discuss the impact of the CMI/RAI MDS report on the staffing levels in the Home, quality resident care, and provide the Union with an opportunity to make representation in that regard. The parties shall meet as necessary to discuss other changes or workload issues. The parties may invite additional participants to attend the meeting to support constructive review and discussion.
Monthly MWBE Contractor Compliance Report A. In accordance with 5 NYCRR § 142.10, Contractor is required to report Monthly MWBE Contractor Compliance to OGS during the term of the Contract for the preceding month’s activity, documenting progress made towards achievement of the Contract MWBE goals. OGS requests that all Contractors use the New York State Contract System (“NYSCS”) to report subcontractor and supplier payments made by Contractor to MWBEs performing work under the Contract. The NYSCS may be accessed at xxxxx://xx.xxxxxxxxxxxxxx.xxx/. This is a New York State- based system that all State agencies and authorities will be implementing to ensure uniform contract compliance reporting throughout New York State. B. When a Contractor receives a payment from a State agency, it is the Contractor’s responsibility to pay its subcontractors and suppliers in a timely manner. On or after the first day of each month, the Contractor will receive an email or fax notification (“audit notice”) indicating that a representative of its company needs to log-in to the NYSCS to report the company’s MWBE subcontractor and supplier payments for the preceding month. The Contractor must also report when no payments have been made to a subcontractor or supplier in a particular month with entry of a zero dollar value in the NYSCS. Once subcontractor and supplier payments have been entered into the NYSCS, the subcontractor(s) and supplier(s) will receive an email or fax notification advising them to log into the NYSCS to confirm that they actually received the reported payments from the Contractor. It is the Contractor’s responsibility to educate its MWBE subcontractors and suppliers about the NYSCS and the need to confirm payments made to them in the NYSCS. C. To assist in the use of the NYSCS, OGS recommends that all Contractors and MWBE subcontractors and suppliers sign up for the following two webinar trainings offered through the NYSCS: “Introduction to the System – Vendor training” and “Contract Compliance Reporting - Vendor Training” to become familiar with the NYSCS. To view the training schedule and to register visit: xxxxx://xx.xxxxxxxxxxxxxx.xxx/events.asp D. As soon as possible after the Contract is approved, Contractor should visit xxxxx://xx.xxxxxxxxxxxxxx.xxx and click on “Account Lookup” to identify the Contractor’s account by company name. Contact information should be reviewed and updated if necessary by choosing “Change Info.” It is important that the staff member who is responsible for reporting payment information for the Contractor be listed as a user in the NYSCS. Users who are not already listed may be added through “Request New User.” When identifying the person responsible, please add “- MWBE Contact” after his or her last name (i.e., Xxxx Xxx – MWBE Contact) to ensure that the correct person receives audit notices from the NYSCS. NYSCS Technical Support should be contacted for any technical support questions by clicking on the links for “Contact Us & Support” then “Technical Support” on the NYSCS website. E. If Contractor is unable to report MWBE Contractor Compliance via the NYSCS, Contractor must submit a Monthly MWBE Contractor Compliance Report on Form MWBE 102 to OGS, by the 10th day of each month during the term of the Contract, for the preceding month’s activity to: OGS MWBE Office, 00xx Xxxxx Xxxxxxx Xxxxx, Xxxxxx Xxxxx Xxxxx, Xxxxxx, XX 00000. Phone: 000-000-0000; Fax: 000-000-0000. F. It is the Contractor’s responsibility to report subcontractor and supplier payments. Failure to respond to payment audits in a timely fashion through the NYSCS, or by paper to OGS, may jeopardize future payments pursuant to the MWBE liquidated damages provisions in clause IX below.
Student Evaluation a. The President of the College or the President’s designee shall be responsible for administering the student evaluation process. b. Student evaluation packets for each class containing instruments and instructions shall be distributed to each faculty member by the first week of December during the fall semester and by the last week in April during the spring semester. c. It is expressly agreed that the faculty member being evaluated shall not be present in the classroom when the student evaluation is being administered and that all instruction to students with regard to such student evaluation shall be included in writing on the instrument, provided further that the designated unit or non-unit professional shall return the student evaluation directly to the President of the College or the President’s designee. The administering of the student evaluation shall be the responsibility of the President of the College or the President’s designee who shall determine who among unit or non-unit professionals shall administer such student evaluation. Student evaluations shall be valid only if signed by the student; provided, however, that faculty members shall not be entitled to the identity of the student responding unless such student evaluation is used as a basis for dismissal or other disciplinary action and such will be communicated to the students. d. The data from the student evaluation shall be tabulated and copies sent to the President of the College or the President’s designee. The raw data shall be retained by the College for a period of one (1) year during which time the faculty member shall have access thereto upon written request. e. The President of the College or the President’s designee shall review the tabulated data and shall forward a data summary to the faculty member by January 23 for the fall semester and by June 15 for the spring semester. f. The faculty member shall have seven (7) working days in which to respond to such data.