Overview of System Requirements Sample Clauses

Overview of System Requirements. In each canteen operated under this Contract, the Contractor shall provide its own turnkey point-of-sale system, including all software and equipment for transactions, receipt printing and inventory control. Existing Department canteen point-of- sale, file server and/or other computer equipment shall be retired from service and will not be available for Contractor’s use. Under no circumstances shall the Contractor’s point-of-sale equipment be configured in such a way as to allow for user access to the greater Internet. The system must be capable of the following: supporting inventory transactions, on-line point-of-sale and manual sales, receipt printing, maintaining detailed transaction records and audit trails and providing all necessary reports. To avoid potential for abuse of the system by inmates working with the Contractor, the system must not use a keyboard or other easily manipulated input device to support operations. The Contractor’s point- of-sale system must be on a data network provided by the Contractor and separate from the Department’s systems. The local area network infrastructure provided by the Contractor must include buried fiber optic cabling between buildings to isolate all devices from lightning strikes or an alternative acceptable to the Department. All Contractor equipment must be installed and secured, both physically and technically, in accordance with Department requirements. The Contractor will be responsible for securing access to the canteen system. The Department must be able to deactivate (“lock-down”) and reactivate the canteen system at each location as needed for security or if a job or system fails. In addition, the Contractor’s telecommunications and server equipment must be collocated with the Department’s equipment to enable strict control of institutional and computer-related security. The Contractor and its telecommunications provider must provide an easily identified “quick disconnect” method to enable the Department’s staff to immediately terminate contact between the Contractor’s canteen system and outside communications whenever institutional security is threatened.
Sample 1
AutoNDA by SimpleDocs

Related to Overview of System Requirements

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

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

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

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

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

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

  • Contractor Requirements The Firm shall be construed, during the entire term of this contract, to be an independent contractor. Nothing in this contract is intended to nor shall be construed to create an employer- employee relationship, or a joint venture relationship. The Firm represents that it is qualified to perform the duties to be performed under this contract and that it has, or will secure, if needed, at its own expense, applicable personnel who are qualified to perform the duties required under this contract. Such personnel shall not be deemed in any way, directly or indirectly, expressly or by implication, to be employees of the District. Any person assigned by the firm to perform the services hereunder shall be the employee or a subcontractor of the Firm, who shall have the sole right to hire and discharge its employee or subcontractors. The Firm or its subcontractors shall pay, when due, all salaries and wages of their employees and accepts exclusive responsibility for the payment of federal income tax, social security, unemployment compensation and any other withholdings that may be required. Neither the Firm, its subcontractors nor their employees are entitled to state retirement or leave benefits. It is further understood that the consideration expressed herein constitutes full and complete compensation for all services and performance hereunder, and that any sum due and payable to the Firm shall be paid as a gross sum with no withholdings or deductions being made by the District for any purpose from said contract sum, except as permitted in paragraphs 16, 17 and 18.

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

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Accessibility Requirements Under Tex. Gov’t Code Chapter 2054, Subchapter M, and implementing rules of the Texas Department of Information Resources, the System Agency must procure Products and services that comply with the Accessibility Standards when those Products are available in the commercial marketplace or when those Products are developed in response to a procurement solicitation. Accordingly, Grantee must provide electronic and information resources and associated Product documentation and technical support that comply with the Accessibility Standards.

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