Y2K Compliance definition

Y2K Compliance or “Y2K Compliant” means hardware, software, firmware, or other systems or processes (hereafter “systems and processes”) that correctly manage, calculate, compare and sequence date data from, into and between the 20th and 21st centuries, including leap year calculations, without human intervention. Y2K Compliant systems and processes must utilize input and output date formats that are compatible with the ISO’s systems and processes, must conform to the International Organization for Standardization ISO 8601:1988 standards for representation of dates and must not cause incorrect date calculations.
Y2K Compliance the ability of a computer program to (i) record, store, process, calculate, present and, where appropriate, insert time and accurate dates and calculations for calendar dates falling on or after (and, if applicable, spans of time including) January 1, 2000, (ii) record, store, process, calculate and present any information and/or data dependent on or relating to such dates in the same manner, and with the same functionality, data integrity and performance, as the Software records, stores, processes, calculates and presents calendar dates on or before December 31, 1999 and in such fashion as to respond to two-digit date input in a way that eliminates all ambiguities as to the century of concern, and treats the year 2000 as a leap-year and correctly and accurately regards and processes data and information with respect thereto, and (iii) lose no functionality with respect to the introduction of records, including but not limited to back-up and archived information and/or data, containing dates falling on or after January 1, 2000 and "Y2K Compliant" has the correlative meaning.
Y2K Compliance. - means Year 2000 compliance and has the meaning set forth in subsection 13.05(c) of this Agreement.

Examples of Y2K Compliance in a sentence

  • In order to protect and maintain the integrity of the ISO’s systems and processes, the ISO shall have the authority to immediately disconnect the systems or processes of any Scheduling Coordinator or other entity that is believed by the ISO to be passing Y2K related erroneous data; i.e., data from systems and processes that do not meet the Section 30.1 standards for Y2K Compliance.

  • All adaptations and replacements of software and hardware required to achieve full Y2K Compliance will be completed on or before September 30, 1999, except where a failure to achieve full Y2K Compliance will not have a Materially Adverse Effect.

  • If Software fails to so function as a consequence of Y2K Compliance, Buyer's sole remedy and Seller's sole obligation under this warranty is for Seller to correct such failure through the replacement or modification of the Software or such other actions as the Parties reasonably determine to be appropriate within sixty (60) days of such failure.

  • Further comments were made that opening and closing this part of the road was often confusing for local residents and visitors alike.

  • All Software Programs that are not designated with a "check" as currently being Year 2000 Compliant will be Year 2000 Compliant on the date indicated in the Y2K Compliance Table.

  • The Parties agree that the above constitutes being year 2000 compliant ("Y2K" Compliance").

  • Such non-exclusive service, as more particularly described in Attachment B (the "Services Profile"), attached hereto and incorporated by reference, includes, but is not limited to, mainframe operations, payroll processing and support, technical staff support, data center operations and floorspace, special processing requirements, system backups, network services, telephone services and Enterprise services including Help Desk, IT Sourcing and Y2K Compliance Program (the "Services" or "Service").

  • However, if Seller is unable to correct such Y2K Compliance failure through replacement or modification of the Software, then the Parties shall negotiate a commercially reasonable solution.

  • Public Listed Companies – Y2K Status Based on the disclosures received up to October 1999, the state of readiness of Public Listed Companies is as follows:- Public Listed Companies’ Y2K Compliance Status Main Board Second BoardOctober 1999Note:- For the 746 public listed companies comprising 462 Main Board companies and 284 Second Board companies, full compliance is expected by December 1999.

  • The URL is: http://www.tex-an.net.- TEX-AN 2000- Web News- Training - Updates/News- Phones/Pagers- Administrative Programming - Y2K Compliance Web NewsFaculty and staff may now view students' transcripts and degree plans via the web.


More Definitions of Y2K Compliance

Y2K Compliance. The computer systems and other equipment containing embedded microchips. which employ, store, exchange or process date/time information, in either case owned or operated by the Borrower or the Subsidiaries or used in the conduct of the Business, and the Borrowers and the Subsidiaries' products and services are Y2K Compliant; and
Y2K Compliance means the ability of a computer program to (i) record, store, process, calculate, present and, where appropriate, insert time and accurate dates and calculations for calendar dates falling on or after (and, if applicable, spans of time including) January 1, 2000, (ii) record, store, process, calculate and present any information and/or data dependent on or relating to such dates in the same manner, and with the same functionality, data integrity and performance, as the software records, stores, processes, calculates and presents calendar dates on or before December 31, 1999 and in such fashion as to respond to two-digit date input in a way that eliminates all ambiguities as to the century of concern, and treats the year 2000 as a leap- year and correctly and accurately regards and processes data and information with respect thereto, and (iii) lose no functionality with respect to the introduction of records, including but not limited to back-up and archived information and/or data, containing dates falling on or after January 1, 2000 and "Y2K Compliant" has the correlative meaning. Any accounting term used in this Agreement shall have, unless otherwise specifically provided herein, the meaning customarily given such term in accordance with GAAP, and all financial computations hereunder shall be computed, unless otherwise specifically provided herein, in accordance with GAAP consistently applied. That certain terms or computations are explicitly modified by the phrase "in accordance with GAAP" shall in no way be construed to limit the foregoing. All other undefined terms contained in this Agreement shall, unless the context indicates otherwise, have the meanings provided for by the U.C.C. to the extent the same are used or defined therein. The words
Y2K Compliance means the ability of a computer program to (i) record, store, process, calculate, present and, where appropriate, insert accurate dates and calculations for calendar dates falling on or after (and, if applicable, spans of time including) January 1, 2000, (ii) record, store, process, calculate and present any information and/or data dependent on or relating to such dates with the same functionality, data integrity and performance, as the software records, stores, processes, calculates and presents calendar dates on or before December 31, 1999 and in such fashion as to respond to two-digit date input in a way that eliminates all ambiguities as to the century of concern, and treats the year 2000 as a leap-year and correctly and accurately regards and processes data and information with respect thereto, and (iii) lose no functionality with respect to the introduction of records, including but not limited to back-up and archived information and/or data, containing dates falling on or after January 1, 2000 and "Y2K Compliant" has the correlative meaning.
Y2K Compliance means that: (i) the functions, calculations, and other computing processes of the software used by LRC in its business (the "Software") (collectively, the "Processes") performs in an accurate manner regardless of the date in time on which the Processes are actually performed and regardless of the date input to such Software, whether before, on, or after January 1, 2000, and whether or not the dates are affected by leap years; (ii) the Software accepts, stores, sorts, extracts, sequences and otherwise manipulates date inputs and date values, and returns and displays date values, in an accurate manner regardless of the dates used, whether before, on, or after January 1, 2000; (iii) the Software will function without interruptions caused by the date in time on which the Processes are actually performed or by the date input to the Software, whether before, on, or after January 1, 2000; (iv) the Software accepts and responds to two (2) digit year and four (4) digit year date input in a manner that resolves any ambiguities as to the century in a defined, predetermined, and accurate manner; (v) the Software displays, prints, and provides electronic output of date information in ways that are unambiguous as to the determination of the century; and (vi) the Software has been tested by LRC to determine whether it is Y2K compliant or it has been represented to LRC that the Software is Y2K compliant; and

Related to Y2K Compliance

  • Non-Compliance means failure/refusal to comply the terms and conditions of the tender;

  • Year 2000 Compliance has the meaning set forth in section 17.29 of the Management Agreement.

  • Export Compliance You acknowledge that Licensor’s products and/or technology are subject to the U.S. Export Administration Regulations (the “EAR”) and You agree to comply with the EAR. You will not export or re-export Licensor’s products, directly or indirectly, to: (1) any countries that are subject to US export restrictions; (2) any end user who You know or have reason to know will utilize Licensor’s products in the design, development or production of nuclear, chemical or biological weapons, or rocket systems, space launch vehicles, and sounding rockets, or unmanned air vehicle systems; or (3) any end user who has been prohibited from participating in the US export transactions by any federal agency of the US government. By downloading or using the Software, You are agreeing to the foregoing and You are representing and warranting that You are not located in, under the control of, or a national or resident of any such country or on any such list. In addition, You are responsible for complying with any local laws in Your jurisdiction which may impact Your right to import, export or use Licensor’s products. Please consult the Bureau of Industry and Security web page xxx.xxx.xxx.xxx before exporting items subject to the EAR. Upon request, Licensor's International Trade Services Department can provide information regarding applicable export restrictions for Licensor products. Licensor assumes no responsibility for Your failure to obtain any necessary export approvals.

  • Assessment of Compliance As defined in Section 3.21.

  • Statement of Compliance means the statement forming part of a Tender indicating the Bidders compliance with the Specification.

  • LEGAL COMPLIANCE This Agreement and any transaction with, or payment to, you pursuant to the terms hereof is conditioned on your representation to us that, as of the date of this Agreement you are, and at all times during its effectiveness you will be, a bank as defined in Section 3(a)(6) of the Securities Exchange Act of 1934 (or other financial institution) and not otherwise required to register as a broker or dealer under such Act. You agree to notify us promptly in writing if this representation ceases to be true. You also agree that, regardless of whether you are a member of the NASD, you will comply with the rules of the NASD, including, in particular, Sections 2310, IM 2310-2, and 2830 of the NASD Conduct Rules, and that you will maintain adequate records with respect to your customers and their transactions, and that such transactions will be without recourse against you by your customers. We recognize that, in addition to applicable provisions of state and federal securities laws, you may be subject to the provisions of the Xxxxx-Xxxxxxxx Act and other laws governing, among other things, the conduct of activities by federal and state chartered and supervised financial institutions and their affiliated organizations. As such, you may be restricted in the activities that you may undertake and for which you may be paid, and, therefore, we recognize that you will not perform activities that are inconsistent with your statutory and regulatory obligations. Because you will be the only one having a direct relationship with the customer, you will be responsible in that relationship for insuring compliance with all laws and regulations, including those of all applicable federal and state regulatory authorities and bodies having jurisdiction over you or your customers to the extent applicable to securities purchases hereunder.

  • HIPAA Compliant means that a Loan Party to the extent legally required (i) is or will use commercially reasonable efforts to be in compliance in all material respects with each of the applicable requirements of the so-called “Administrative Simplification” provisions of HIPAA on and as of each date that any part thereof, or any final rule or regulation thereunder, becomes effective in accordance with its or their terms, as the case may be (each such date, a “HIPAA Compliance Date”) and (ii) is not and could not reasonably be expected to become, as of any date following any such HIPAA Compliance Date, the subject of any civil or criminal penalty, process, claim, action or proceeding, or any administrative or other regulatory review, survey, process or proceeding (other than routine surveys or reviews conducted by any government health plan or other accreditation entity) that could result in any of the foregoing or that has or could reasonably be expected to have a Material Adverse Effect.

  • Annual Statement of Compliance As defined in Section 3.13.

  • Compliance Review means an inspection of the home, grounds, and files to determine compliance with these regulations.

  • Document of Compliance has the meaning given to it in the ISM Code.

  • Safety compliance facility means a licensee that is a commercial entity that receives marihuana from a marihuana facility or registered primary caregiver, tests it for contaminants and for tetrahydrocannabinol and other cannabinoids, returns the test results, and may return the marihuana to the marihuana facility.

  • Compliance schedule means a schedule of events, by date, which will result in compliance with these regulations.

  • Substantial compliance means a level of compliance with these rules where any deficiencies pose no greater risk to resident health or safety than the potential for causing minor harm.

  • Trading Compliance Policy means the written policy of the Company pertaining to the purchase, sale, transfer or other disposition of the Company’s equity securities by Directors, Officers, Employees or other service providers who may possess material, nonpublic information regarding the Company or its securities.

  • Labor compliance agreement means an agreement entered into between a contractor or subcontractor and an enforcement agency to address appropriate remedial measures, compliance assistance, steps to resolve issues to increase compliance with the labor laws, or other related matters.

  • Compliance as used in this clause, means compliance with:

  • Compliance Audit means the procedure (in a form advised by the GLA from time to time) by which an auditor independent of the Grant Recipient certifies (at the Grant Recipient's cost) whether the Named Projects developed or Rehabilitated pursuant to this Agreement satisfy the GLA's procedural compliance requirements (as described in the Affordable Housing Capital Funding Guide);

  • Covenant Compliance Worksheet means a fully completed worksheet in the form of Attachment A to Exhibit C.

  • Reportable Compliance Event means that any Covered Entity becomes a Sanctioned Person, or is charged by indictment, criminal complaint or similar charging instrument, arraigned, or custodially detained in connection with any Anti-Terrorism Law or any predicate crime to any Anti-Terrorism Law, or has knowledge of facts or circumstances to the effect that it is reasonably likely that any aspect of its operations is in actual or probable violation of any Anti-Terrorism Law.

  • Operational requirements means the need to ensure that the Agency is to be operated as effectively, efficiently and economically as possible.

  • Environmental Compliance Reserve means any reserve which the Agent establishes in its reasonable discretion after prior written notice to the Borrower from time to time for amounts that are reasonably likely to be expended by the Borrower in order for the Borrower and its operations and property (a) to comply with any notice from a Governmental Authority asserting material non-compliance with Environmental Laws, or (b) to correct any such material non-compliance identified in a report delivered to the Agent and the Lenders pursuant to Section 7.7.

  • Material Compliance Matter has the same meaning as the term defined in Rule 38a-1, and includes any compliance matter that involves: (1) a violation of the federal securities laws by Distributor (or its officers, directors, employees, or agents); (2) a violation of Distributor's Rule 38a-1 policies and procedures; or (3) a weakness in the design or implementation of Distributor's Rule 38a-1 policies and procedures.

  • Reporting Requirements As defined in Section 11.15.

  • Repeat compliance period means any subsequent compliance period after the initial compliance period.

  • Environmental and Social Standards or “ESSs” means, collectively: (i) “Environmental and Social Standard 1: Assessment and Management of Environmental and Social Risks and Impacts”; (ii) “Environmental and Social Standard 2: Labor and Working Conditions”; (iii) “Environmental and Social Standard 3: Resource Efficiency and Pollution Prevention and Management”;

  • Reporting Requirement By January 31, 2017, the District will provide for OCR’s review and approval the Web Accessibility Policy drafted consistent with Item 1.