All requirements for E. 91 also apply to the use of SS7 as a type of signaling used on the interconnection trunks from the local switch to an end office or a selective router.
All requirements for E Sample Clauses
Related to All requirements for E
Additional Requirements for Sleeping Rooms The Contractor shall provide departing Attendees a secured area for storing belongings.
Requirements for E- Bidders 3.1. For Individual/ Joint E-Bidders, the following documents shall be uploaded during online registration; 3.1.1. Copy of Identification Documents (both sides) 3.1.2. Evidence of deposit payment 3.2. For Agent acting for Individual/ Joint Online Bidders, the following documents shall be uploaded during online registration; 3.2.1. Copy of Identification Documents (both sides) of Individual/ Joint Online Bidder 3.2.2. Copy of Identification Documents (both sides) of Agent 3.2.3. Copy of letter of authorization to bid 3.2.4. Evidence of deposit payment 3.3. For Company, the following documents shall be uploaded during online registration: 3.3.1. Copy of Identification Documents (both sides) of the representative. 3.3.2. Copy of letter of authorization to bid under the Company’s Letter Head 3.3.3. Form 24; Form 44; Form 49 (or their equivalent forms under the Companies Act 2016)
Certain State Law Requirements for Contracts The contents of this Section are required by Texas Law and are included by County regardless of content. For purposes of Sections 2252.152, 2271.002, and 2274.002, Texas Government Code, as amended, C&T hereby verifies that C&T and any parent company, wholly owned subsidiary, majority-owned subsidiary, and affiliate: a. Unless affirmatively declared by the United States government to be excluded from its federal sanctions regime relating to Sudan or Iran or any federal sanctions regime relating to a foreign terrorist organization, is not identified on a list prepared and maintained by the Texas Comptroller of Public Accounts under Sections 806.051, 807.051, or 2252.153 of the Texas Government Code. b. If employing ten (10) or more full-time employees and this Agreement has a value of
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.
Requirements for Protection In compliance with NPCC requirements and Good Utility Practice, Developer shall provide, install, own, and maintain relays, circuit breakers and all other devices necessary to remove any fault contribution of the Large Generating Facility to any short circuit occurring on the New York State Transmission System not otherwise isolated by Connecting Transmission Owner’s equipment, such that the removal of the fault contribution shall be coordinated with the protective requirements of the New York State Transmission System. Such protective equipment shall include, without limitation, a disconnecting device or switch with load- interrupting capability located between the Large Generating Facility and the New York State Transmission System at a site selected upon mutual agreement (not to be unreasonably withheld, conditioned or delayed) of the Developer and Connecting Transmission Owner. Developer shall be responsible for protection of the Large Generating Facility and Developer’s other equipment from such conditions as negative sequence currents, over- or under-frequency, sudden load rejection, over- or under-voltage, and generator loss-of-field. Developer shall be solely responsible to disconnect the Large Generating Facility and Developer’s other equipment if conditions on the New York State Transmission System could adversely affect the Large Generating Facility.
Minimum Site Requirements for TIPS Sales (when applicable to TIPS Sale). Cleanup: When performing work on site at a TIPS Member’s property, Vendor shall clean up and remove all debris and rubbish resulting from their work as required or directed by the TIPS Member or as agreed by the parties. Upon completion of work, the premises shall be left in good repair and an orderly, neat, clean and unobstructed condition. Preparation: Vendor shall not begin a project for which a TIPS Member has not prepared the site, unless Vendor does the preparation work at no cost, or until TIPS Member includes the cost of site preparation in the TIPS Sale Site preparation includes, but is not limited to: moving furniture, installing wiring for networks or power, and similar pre‐installation requirements. Registered Sex Offender Restrictions: For work to be performed at schools, Vendor agrees that no employee of Vendor or a subcontractor who has been adjudicated to be a registered sex offender will perform work at any time when students are, or reasonably expected to be, present unless otherwise agreed by the TIPS Member. Vendor agrees that a violation of this condition shall be considered a material breach and may result in the cancellation of the TIPS Sale at the TIPS Member’s discretion. Vendor must identify any additional costs associated with compliance of this term. If no costs are specified, compliance with this term will be provided at no additional charge. Safety Measures: Vendor shall take all reasonable precautions for the safety of employees on the worksite, and shall erect and properly maintain all necessary safeguards for protection of workers and the public. Vendor shall post warning signs against all hazards created by the operation and work in progress. Proper precautions shall be taken pursuant to state law and standard practices to protect workers, general public and existing structures from injury or damage. Smoking: Persons working under Agreement shall adhere to the TIPS Member’s or local smoking statutes, codes, ordinances, and policies.
Minimum Shipping Requirements for TIPS Sales Vendor shall ship, deliver, or provide ordered goods and services within a commercially reasonable time after acceptance of the order. If a delay in delivery is anticipated, Vendor shall notify the TIPS Member as to why delivery is delayed and provide an updated estimated time for completion. The TIPS Member may cancel the order if the delay is not commercially acceptable or not consistent with the Supplemental Agreement applicable to the order.
SERVICE REQUIREMENTS FOR REFERRED CLIENTS A. Agent agrees to respond to any communications from a Referred Client within two (2) hours after receipt if such communication is received between 9:00am to 5:00pm local time. For communications received outside of these hours, Agent agrees to respond by 10:00am the next day. B. Agent agrees to update XXXX.xxx with status updates within 48 hours after initial communication with a Referred Client and upon every significant status change until closing or abandoned. Updates shall be made by Agent via email to xxxxxxxxxxxx@xxxx.xxx. C. Vacations or extended absences shall be reported, with length of pause, to XXXX.xxx via email to D. Agent will not add Referred Client to any email list or calling list without the express permission of Referred Client. E. Agent agrees XXXX.xxx has the right to survey the Referred Client at any time. F. If Agent is contacted by a Referred Client that Agent is unwilling or unable to assist, Agent shall direct such Referred Client back to XXXX.xxx for assistance and notify XXXX.xxx at xxxxxxxxxxxx@xxxx.xxx. G. Agent agrees that XXXX.xxx has no obligation to provide Agent with any number of referrals and that prospective clients are free to select the agent they wish to work with for any particular real estate transaction.
Minimum Condition and Warranty Requirements for TIPS Sales All goods quoted or sold through a TIPS Sale shall be new unless clearly stated otherwise in writing. All new goods and services shall include the applicable manufacturers minimum standard warranty unless otherwise agreed to in the Supplemental Agreement.
Functional Requirements Applications must implement controls that protect against known vulnerabilities and threats, including Open Web Application Security Project (OWASP) Top 10 Risks and denial of service (DDOS) attacks.
