General System Requirements Sample Clauses

General System Requirements a. Ability to create employee groups. These employee groups should have the ability to aid in tracking across multiple agencies and departments.
AutoNDA by SimpleDocs
General System Requirements. Available Partially Meets Future Release Not Available Comments REQUIREMENTS ü ü ü ü
General System Requirements. Available Partially Meets Future Release Not Available Comments REQUIREMENTS ü ü ü ü 20. **Process ACH payments per Office of State Treasurer (OST) and NACHA Operating rules Industry Standards; a. ACH payments will be processed through the OST concentration account banking services contract. b. Vendor / product will adhere to the NACHA ACH Operating Rules c. Vendor/ product will produce a NACHA formatted file and transmit to State Treasurer’s Office for further processing by the state’s concentration bank. ü
General System Requirements. Available Partially Meets Future Release Not Available COMMENTS REQUIREMENTS ü ü ü ü 57. Capture export transactions for audit purposes [SR4.8.3.2 and SR 4.8.4.2] ü LOGGING
General System Requirements 

Related to General System Requirements

  • Minimum Requirements Consultant shall, at its expense, procure and maintain for the duration of the Agreement insurance against claims for injuries to persons or damages to property which may arise from or in connection with the performance of the Agreement by the Consultant, its agents, representatives, employees or subconsultants. Consultant shall also require all of its subconsultants to procure and maintain the same insurance for the duration of the Agreement. Such insurance shall meet at least the following minimum levels of coverage:

  • Quality Requirements Performance Indicator Heading Indicator (specific) Threshold Method of Measurement Frequency of monitoring Consequence of Breach QUALITY Patient Safety - Incidents I1 Number of incidents Adverse incidents include the following: clinical or non clinical adverse events that have potential to cause avoidable harm to a patient, including medical errors or adverse events related to medical devices or other equipment. Clinical or non- clinical accidents, accidental injuries to staff and members of the public, verbal, physical or psychological abuse or harassment, unusual or dangerous occurrences, damage to trust property, plant or equipment, fire or flood, security, theft or loss, near misses are identified as any event where under different circumstances significant injury or loss may have occurred Number of recorded incidents in the contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed I2 Number of Sis Definition of SUI according to trust policy and national guidance Number of Serious Untoward Incidents reported in contract month Monthly Remedial Action Plan brought to Performance Meeting following breach; action under Module C Clause 32 if needed S1 Percentage of eligible staff received child safeguarding training at level 2 (as identified in LSCB training strategy) 95% Number received training/ Number of identified staff requiring training Monthly S2 Percentage of eligible staff received adult safeguarding awareness training at level 2 ( as identified in K&M Safeguarding Vulnerable Adults training strategy) 95% Number of staff trained/ Number of identified staff requiring training Monthly

  • Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.

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

  • General Requirements The Contractor hereby agrees:

Time is Money Join Law Insider Premium to draft better contracts faster.