Supplier Compliance Expectations Sample Clauses

Supplier Compliance Expectations. Supplier has responsibility to ensure security requirements are adhered to and remain consistent throughout the duration of the project/support. Below is a sample of a minimum compliance checklist. This can be tailored in order to fit business requirements. Completed checklists should be posted to the Intel ODC portal. Any changes in ODC location, size, controls status or ODC additions must be communicated to Intel ODC Governance and Compliance program in advance. Intel ODC Minimum Controls Compliance Checklist Company: ODC Ref #: Audit Date: Audit item Yes No Details Physical Entry Points have access controls to the granularity of each authorized person Access logs retained for min of 3 months All entry door sound alarm when propped open for > 30 seconds (tested) All emergency door activate alarm when opened All windows locked and include tamper proof sensors Incidence response to alarm activation for all sensors, (doors and windows) Unauthorized access prevention (e.g. false ceilings, wall not true floor to ceiling) Perimeter glass obscured, includes windows if ODC is a ground floor location ODC is not labeled or identified as Intel CCTV monitoring ODC entry doors Security monitoring 24 x 7 Access Management Visitor policy in place No tours policy ODC authorized access list scrubbed at least once per quarter Authorized access based on need to know basis for Intel business support only Network Only one network distributed in the ODC Network equipment in locked access controlled location and restricted If Intel network is distributed in ODC – air gap isolation implemented If Intel managed network is accessed - network enclave or segregated VLAN Firewall documented / configured / monitored (refer to Intel’s Firewall Tech- nical Design Review (FTDR) documentation)
Sample 1
AutoNDA by SimpleDocs

Related to Supplier Compliance Expectations

  • Contractual and Operational Compliance Audits (a) ICANN may from time to time (not to exceed twice per calendar year) conduct, or engage a third party to conduct, contractual compliance audits to assess compliance by Registry Operator with its representations and warranties contained in Article 1 of this Agreement and its covenants contained in Article 2 of this Agreement. Such audits shall be tailored to achieve the purpose of assessing compliance, and ICANN will (a) give reasonable advance notice of any such audit, which notice shall specify in reasonable detail the categories of documents, data and other information requested by ICANN, and

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

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

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

  • Requirement to Utilize HUB Compliance Reporting System Pursuant to Texas Administrative Code, Title 34, Part 1, Sections 20.285(f) and 20.287(b), TFC administers monthly administration HSP-PAR compliance monitoring through its HUB Compliance Reporting System commonly known as B2G. PSP and PSP’s subcontractors/subconsultants shall submit required PAR information into the B2G system. Any delay in the timely submission of PAR information into the B2G system will be treated as an invoicing error subject to dispute under Texas Government Code Section 2251.042.

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Testing/Trouble Reporting 1.15.1 TWTC will be responsible for testing and isolating troubles on Network Elements. TWTC must test and isolate trouble to the AT&T network before reporting the trouble to the Network Elements Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from AT&T at the time of the trouble report, TWTC will be required to provide the results of the TWTC test which indicate a problem on the AT&T network. Version: 4Q06 Standard ICA 11/30/06

  • Loop Testing/Trouble Reporting 2.1.6.1 Think 12 will be responsible for testing and isolating troubles on the Loops. Think 12 must test and isolate trouble to the BellSouth portion of a designed/non- designed unbundled Loop (e.g., UVL-SL2, UCL-D, UVL-SL1, UCL-ND, etc.) before reporting repair to the UNE Customer Wholesale Interconnection Network Services (CWINS) Center. Upon request from BellSouth at the time of the trouble report, Think 12 will be required to provide the results of the Think 12 test which indicate a problem on the BellSouth provided Loop.

  • Specification and Service Levels The Specification sets out the Services that the Contractor has undertaken to provide. The Specification includes Service Levels setting out particular levels of service that the Contractor has undertaken to meet.

  • 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: For Calendar Quarter Ending Master Contract Sales Report Due 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 0.74 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 .0074. 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.

Time is Money Join Law Insider Premium to draft better contracts faster.