Report on Workshop Findings and Outcomes Sample Clauses

Report on Workshop Findings and Outcomes. The aim of this workshop has been to define and build a number of tools that can be used to share and federate information about eGovernment resource themselves, with the overall objective to facilitate access to and hence (re-)use of eGovernment resources. Current obstacles to widespread access to and reuse of eGovernment resources include:  Lack of a comprehensive, yet easy to use standardized metadata schema for their description;  Lack of easily accessible administrative terminology for use in these descriptions;  Lack of awareness of cultural diversity issues including users' language skills and other semiotic faculties. This workshop has concentrated on addressing the obstacles above by specifying  a standardized minimum description of eGovernment resources (leveraging existing federated terminological assets);  mechanisms for the exchange and notification of new/updated information about eGovernment resources;  common agreed approaches to facilitate the discovery of, query of, access to, and information about eGovernment resources. Those specifications have been performed in part 1, 2 and 3 of the CWA with the goal of keeping practical needs in mind and with the focus on providing hand-on specifications that are build on widely applied but nevertheless modern formats and technologies. The CWA has specified interfaces and has provided practical examples in order to make the usage as easy as possible and in order to avoid problems in implementations of the specifications. The eGov-Share workshop has also implemented two demonstrator applications that can be used to validate the capabilities of the system although the demonstrators have been limited in scope and functionality in order to concentrate on the main principles. The specifications that have been described by the workshop such as the ATOM based protocol or the terminological resource description can be used without modification. The more partners are participating in implementing and using the workshop outcome, the more beneficial the results will be. This is especially true for the Terminological Resource Network which is based on the participation of many different participants.
Sample 1
AutoNDA by SimpleDocs

Related to Report on Workshop Findings and Outcomes

  • Office of Inspector General Investigative Findings Expert Review In accordance with Senate Bill 799, Acts 2021, 87th Leg., R.S., if Texas Government Code, Section 531.102(m-1)(2) is applicable to this Contract, Contractor affirms that it possesses the necessary occupational licenses and experience.

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

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

  • Annual Evaluations The purpose of the annual evaluation is to assess and communicate the nature and extent of an employee's performance of assigned duties consistent with the criteria specified below in this Policy. Except for those employees who have received notice of non-reappointment pursuant to the BOT- UFF Policy on Non- reappointment, every employee shall be evaluated at least once annually. Personnel decisions shall take such annual evaluations into account, provided that such decisions need not be based solely on written faculty performance evaluations.

  • Presentation of Potential Target Businesses The Company shall cause each of the Initial Shareholders to agree that, in order to minimize potential conflicts of interest which may arise from multiple affiliations, the Initial Shareholders will present to the Company for its consideration, prior to presentation to any other person or company, any suitable opportunity to acquire an operating business, until the earlier of the consummation by the Company of a Business Combination or the liquidation of the Company, subject to any pre-existing fiduciary obligations the Initial Shareholders might have.

  • MANAGEMENT OF EVALUATION OUTCOMES 12.1 Where the Employer is, any time during the Employee’s employment, not satisfied with the Employee’s performance with respect to any matter dealt with in this Agreement, the Employer will give notice to the Employee to attend a meeting; 12.2 The Employee will have the opportunity at the meeting to satisfy the Employer of the measures being taken to ensure that his performance becomes satisfactory and any programme, including any dates, for implementing these measures; 12.3 Where there is a dispute or difference as to the performance of the Employee under this Agreement, the Parties will confer with a view to resolving the dispute or difference; and 12.4 In the case of unacceptable performance, the Employer shall – 12.4.1 Provide systematic remedial or developmental support to assist the Employee to improve his performance; and 12.4.2 After appropriate performance counselling and having provided the necessary guidance and/or support as well as reasonable time for improvement in performance, the Employer may consider steps to terminate the contract of employment of the Employee on grounds of unfitness or incapacity to carry out his or her duties.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Annual Evaluation The Partnership will be evaluated on an annual basis through the use of the Strategic Partnership Annual Evaluation Format as specified in Appendix C of OSHA Instruction CSP 00-00-000, OSHA Strategic Partnership Program for Worker Safety and Health. The Choate Team will be responsible for gathering required participant data to evaluate and track the overall results and success of the Partnership. This data will be shared with OSHA. OSHA will be responsible for writing and submitting the annual evaluation.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

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