Customer Requirements ▪ Seller shall comply with the applicable terms and conditions of any agreements between Buyer and Xxxxx’s Customer (the “Customer Purchase Orders”) pursuant to which Buyer agreed to sell to Buyer’s Customer products or assemblies which incorporate the goods provided by Seller hereunder. This provision specifically includes costs and obligations imposed by warranty programs instituted by the original equipment manufacturer that ultimately purchases Buyer’s products that incorporate the goods sold by Seller if applicable to Buyer under the terms of the Customer Purchase Order. ▪ If Buyer is not acting as a Tier One supplier, the defined term “Customer Purchase Order” shall also include the terms and conditions of the original equipment manufacturer that ultimately purchases Buyer’s product that incorporates the goods or services sold by Seller. ▪ Seller will be responsible to ascertain how the disclosed terms affect Seller’s performance under the Purchase Order. ▪ By written notice to Seller, Buyer may elect to disclose and have the provisions of the Customer’s Purchase Orders prevail over any term of the Purchase Order at any time.
Computer Requirements You are responsible for obtaining, installing, maintaining and operating all software, hardware, or other equipment necessary (collectively, “Access Device Systems”) necessary for you to access and use the Service. This responsibility includes, without limitation, your utilizing up to date web-browsers and Access Devices and the best commercially available encryption, antivirus, anti-spyware, and Internet security software. You are additionally responsible for obtaining Internet service via an Internet service provider of your choice, for any and all fees imposed by such Internet service provider, and any associated communications service provider charges. You acknowledge that there are certain security, corruption, transmission error and access availability risks associated with using open networks such as the Internet and you hereby expressly assume such risk, including, but not limited to those we may disclose in our educational materials. You acknowledge that you are responsible for data security of the Systems used to access the Service, and for the transmission and receipt of information using such System. You acknowledge that you have requested the Service for your convenience, have made your own independent assessment of the adequacy of the Internet and Systems and that you are satisfied with that assessment. The Bank shall have no responsibility for failures, interruption or other defects in the Services, which arise from the malfunction or failure of the Internet or your Systems nor are we responsible for notifying you of any upgrades, fixes, or enhancements to, or for providing technical or other support for your Systems. The Bank may add to, modify, or replace software programs used in conjunction with providing the Services under this Agreement at its sole discretion and without notice, provided Services rendered to you are not substantially negatively affected or obligations altered.
PJM Requirements The DS Supplier acknowledges and agrees that, as a member of PJM, the Company is bound by all PJM operating instructions, policies and procedures as are currently set forth in the PJM Operating Manual, which are available through the Internet on the PJM Home Page (xxxx://xxx.xxx.xxx), as may be revised from time to time, which are needed to maintain the integrity of the PJM system. The DS Supplier acknowledges and agrees that it will cooperate with the Company so that the Company will be in compliance with all PJM Emergency Operations Procedures, which include, but are not limited to, those procedures pertaining to minimum and maximum generation Emergencies, and measures requiring involuntary Customer participation, such as supply voltage reduction or full interruption of Customer load by either manual or automatic means.
Network Requirements (A) The Contractor shall maintain and monitor a network of appropriate Network Providers that is supported by written agreements and is sufficient to provide adequate access to all Covered Services for all Enrollees, including those with limited English proficiency or physical or mental disabilities. In establishing and maintaining the network of Network Providers the Contractor shall consider:
Contractor Requirements The Contractor shall—
System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.
Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. Item Not Received additional requirements To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.
Power Factor Requirement Consistent with Section 4.7 of Appendix 2 to this ISA, the power factor requirement is as follows: The Generation Interconnection Customer shall design its non-synchronous Customer Facility with the ability to maintain a power factor of at least 0.95 leading to 0.95 lagging measured at the high-side of the facility substation transformers.
TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
