Methods of Compliance Sample Clauses

The "Methods of Compliance" clause defines the acceptable ways in which a party can fulfill specific obligations or requirements set out in an agreement. It typically outlines the standards, procedures, or documentation that must be followed or provided to demonstrate compliance, such as adhering to industry regulations, submitting reports, or passing inspections. By clearly specifying how compliance is to be achieved and verified, this clause ensures both parties have a mutual understanding of expectations and reduces the risk of disputes over whether obligations have been properly met.
Methods of Compliance. 9.1 Where there is no precedent, i.e. for new technology, novel applications of existing technology or MOC, novel MOC, or product use is unconventional, the VA will work closely with the CA and the applicant during Phase II of the program to establish an acceptable VA Certification Basis and MOC. 9.2 Once a MOC for a given rule has been accepted by the VA on any program with the CA, the expectation is that the VA will accept that MOC in the future as long as the assumptions made in the MOC are applicable. An exception is where an MOC has been determined not to be sufficient. This determination must be discussed between the VA and the CA. 9.3 When the VA determines there is a need to evaluate or review a MOC with the CA and the applicant, in accordance with the concepts in this document, the VA will confine its evaluation or review to the general, overall methodology to be used by the applicant, including assumptions, boundary conditions, and critical parameters of that methodology that are essential to the technical adequacy of the MOC. Details in the form of test plans, test parameters and other MOC steps should be left up to the CA to further define and approve.
View SourceView Similar (6)
Methods of Compliance. Lessee shall keep and maintain a complete summary listing of all modifications performed after the Commencement Time (it being understood and agreed that nothing set forth in this Annex shall derogate from Lessee's rights and obligations with respect to the alteration and ▇▇▇▇▇▇cation of the Aircraft as set forth in the Lease).
View Source

Related to Methods of Compliance

  • Standards Compliance Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • S▇▇▇▇▇▇▇-▇▇▇▇▇ Compliance As soon as it is legally required to do so, the Company shall take all actions necessary to obtain and thereafter maintain material compliance with each applicable provision of the S▇▇▇▇▇▇▇-▇▇▇▇▇ Act of 2002 and the rules and regulations promulgated thereunder and related or similar rules and regulations promulgated by any other governmental or self-regulatory entity or agency with jurisdiction over the Company.

  • DBE/HUB Compliance The Engineer’s subcontracting program shall comply with the requirements of Attachment H of the contract (DBE/HUB Requirements).

  • PCI Compliance Company shall not connect to or utilize any computer network or systems of the Aviation Authority, including, without limitation, for transmission of credit card payments. Company shall be solely responsible for providing and maintaining its own computer networks and systems and shall ensure its system ensure its system used to collect, process, store or transmit credit card or customer credit card and/or personal information is compliant with all applicable Payment Card Industry (“PCI”) Data Security Standard (“DSS”). 1. Company shall, within 5 days, notify the Aviation Authority of any security malfunction or breach, intrusion or unauthorized access to cardholder or other customer data, and shall comply with all then applicable PCI requirements. 2. Company, in addition to notifying the Aviation Authority and satisfying the PCI requirements, will immediately take the remedial actions available under the circumstances and provide the Aviation Authority with an explanation of the cause of the breach or intrusion and the proposed remediation plan. Company will notify the Aviation Authority promptly if it learns that it is no longer PCI DSS compliant and will immediately provide the Aviation Authority with a report on steps being taken to remediate the non-compliance status and provide evidence of compliance once PCI DSS compliance is achieved. 3. Company, its successor’s and assigns, will continue to comply with all provisions of this Agreement relating to accidents, incidents, damages and remedial requirements after the termination of this Agreement. 4. Company shall ensure strict compliance with PCI DSS for each credit card transaction and acknowledges responsibility for the security of cardholder data. Company will create and maintain reasonable detailed, complete and accurate documentation describing the systems, processes, network segments, security controls and dataflow used to receive, process transmit store and secure Customer’s cardholder data. Such documentation shall conform to the most current version of PCI DSS. 5. Company must maintain PCI Certification as a bankcard merchant at the Airport. Company is responsible, at Company’s own expense, to contract and pay for all quarterly, annual or other required assessments, remediation activities related to processes within Concessionaire’s control, analysis or certification processes necessary to maintain PCI certification as a bankcard merchant. 6. PCI DSS - Company shall make available on the Premises, within 24 hours upon request by the Aviation Authority, such documentation, policies, procedures, reports, logs, configuration standards and settings and all other documentation necessary for the Aviation Authority to validate Company’s compliance with PCI DSS as well as make available to the individuals responsible for implementing, maintaining and monitoring those system components and processes. Requested logs must be made available to the Aviation Authority in electronic format compatible with computers used by the Aviation Authority. 7. Evidence of PCI DSS Compliance – Company agrees to supply their PCI DSS compliance status and evidence of its most recent validation of compliance upon execution of the Contract. Company must supply to the Aviation Authority evidence of validation of compliance at least annually to be delivered along with the Annual Certification of Fees in accordance with Article 5.C. of this Agreement.

  • Privacy Compliance The Provider shall comply with all applicable federal, state, and local laws, rules, and regulations pertaining to Student Data privacy and security, all as may be amended from time to time.