Input Data Requirements Sample Clauses

Input Data Requirements. 3.1.1 Event Processing requires a list of Camera IDs that are linked to a Scheme. 3.1.2 Each Camera ID may be linked to more than one Scheme. 3.1.3 The Scheme List will need to include the following data fields:  Scheme,  Date(s) for which valid,  Time,  Camera ID.
Sample 1
AutoNDA by SimpleDocs
Input Data Requirements. 7.1.1 Event Processing needs to understand what Chargeable Items are to be identified as being Compliant with LEZ Scheme 7.1.2 The Compliant Vehicle List will be created using VOSA Data. 7.1.3 The Compliant Vehicle List will need to include the following data fields:  VRM,  Scheme,  Date(s) for which valid,  Compliant Product Identifier.
Sample 1
Input Data Requirements. 10.1.1 Event Processing needs to understand what Chargeable Items have an associated payment. 10.1.2 The Settlement List will need to include the following data fields:  VRM,  Scheme,  Payment Product,  Date(s) for which valid,  Notes where appropriate.
Sample 1
Input Data Requirements. 5.1.1 Event Processing needs to determine which Vehicles are exempt from the Scheme. 5.1.2 The Exempt Vehicle List will need to include the following data fields:  VRM,  Scheme,  Date(s) for which valid,  Exempt Product Identifier. 5.1.3 Previous Exempt Vehicle Lists should be retained for audit purposes. 5.1.4 As a result of Enforcement Notice Processing, newly identified exempt Vehicles should be added to the Exempt Vehicle List. 5.1.5 On refreshing the Exempt Vehicle List, the Service Provider will validate that all newly identified exempt Vehicles identified by the Enforcement Operation Service Provider are included within the Exempt Vehicle List. 5.1.6 Where Vehicles provided by the Enforcement Operation Service Provider are not included in the refreshed Exempt Vehicles List these should be reported as exceptions to TfL. 5.1.7 Vehicles on the list of newly identified exempt Vehicles must be able to be added/removed as per instruction from TfL. 5.1.8 Currently UK Vehicles are exempted from the Congestion Charging Scheme based on tax class which is currently sourced from the DVLA in the UK. In the future this may also include data for Northern Ireland vehicles. Vehicle exemptions are subject to change based on changes to the tax class data. 5.1.9 The table below details Vehicle exemptions based on tax class under the current Scheme. 1 Motorbikes and mopeds This category consists of all Vehicles registered in DVLA Taxation class TC 17 (Motorcycle) and TC 19 (Electric Motorcycle) 2 NHS Vehicles currently Exempt from Vehicle Excise Duty This category consists of all Vehicles registered in DVLA Taxation class TC 87 (NHS Vehicles). 3 Disabled passenger carrying Vehicles currently exempt from VED This category consists of all Vehicles registered in DVLA Taxation class TC 85 (Disabled Passenger Carrying Vehicle). 4 Vehicles used by disabled persons exempt from VED This category consists of all Vehicles registered in DVLA Taxation class TC 78 (Disabled). 5 Licensed Buses with nine (9) or more seats This category consists of all Vehicles registered in DVLA Taxation class TC 34 (Bus) and TC 38 (Reduced Pollution Bus).
Sample 1
Input Data Requirements. 4.1.1 Event Processing needs to understand which Detection Events are to be discarded 4.1.2 The Override Identification List will need to include the following data fields:  Camera ID,  Zone of cameras,  Scheme,  Date(s) for which valid,  Time from,  Time to,  Reason.
Sample 1
Input Data Requirements. 2.1.1 Event Processing requires a daily list of Vehicle Registration Marks that are required to be flagged as VOSI Vehicles. 2.1.2 This list (VOSI List) needs to be loaded daily. 2.1.3 The list will need to include the following data fields:  VRM,  Date(s) for which valid.
Sample 1
Input Data Requirements. 6.1.1 Event Processing needs to determine which Vehicles are not subject with the Scheme.
Sample 1
AutoNDA by SimpleDocs
Input Data Requirements. 8.1.1 Event Processing needs to understand what Chargeable Items are to be identified as Discounted. 8.1.2 The Discount Vehicle List will need to include the following data fields:  VRM,  Scheme,  Date(s) for which valid,  Discount Product Identifier.
Sample 1
Input Data Requirements. 9.1.1 Event Processing needs to understand what Chargeable Items are to be identified as TfL Filter Products. 9.1.2 The TfL Filter Vehicle List will need to include the following data fields:  VRM,  Scheme,  Date(s) for which valid,  TfL Filter Product Identifier,  Notes where appropriate.
Sample 1

Related to Input Data Requirements

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

  • Specific Requirements compensation insurance with statutory limits required by South Dakota law. Coverage B-Employer’s Liability coverage of not less than $500,000 each accident, $500,000 disease-policy limit, and $500,000 disease-each employee.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Technical Requirements Signaling Link Transport shall consist of full duplex mode 56 kbps transmission paths and shall perform in the following two ways:

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

  • Match Requirements There is no match required on the part of the Grantee under this 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.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • Interface Requirements 2.4.5.1 The NID shall be equal to or better than all of the requirements for NIDs set forth in the applicable industry standard technical references.

  • Customer Requirements Customer will be required to maintain complex passwords for their User accounts where applicable. For any such passwords LightEdge will provide a secure URL that any User can access to change passwords. All User passwords are set to a ninety (90) day password expiration schedule by default. LightEdge is not responsible for unexpected use of Services whether by ex-employees, compromised User passwords or any other misuse of Customer accounts. Customer shall be responsible for all costs incurred by such unexpected use of Service. Customer shall be fully responsible for providing to LightEdge at Customer’s own expense and in a timely manner the following: - All security for its Services and systems used or accessible in connection with Service; - Cooperative testing of all Customer-provided hardware, software, and Services for compatibility with Service; - Designating an Authorized Contact(s) to be the point of contact to interface with LightEdge Technical Support; - All cabling necessary to support Service; and - Physical and remote management access to any and all Servers onto which Service is installed.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!