SYSTEM FUNCTIONALITY REQUIREMENTS Sample Clauses

SYSTEM FUNCTIONALITY REQUIREMENTS. Contractor shall meet the following system functionality requirements:
AutoNDA by SimpleDocs
SYSTEM FUNCTIONALITY REQUIREMENTS. The software provided should include the ability to do the following: Supports the Registration of all Programme Participants, Using forms suitable for Android tablets which will also work offline Upload programme participants lists provided by Concern Ability to add, edit, delete, filter and re-filter participants from the list by Concern users both in batches and individually Export function for whole lists or filtered items into CSV / Excel file Information of security procedures for the e-voucher platform to easily identify cases of fraud Ability for Concern staff to block a card if suspicious activity is detected Ability for Concern to control the upload value onto voucher including a description of how this function works i.e. offline or online Description of how a programme participant will know their balance or be notified of a ‘Top-Up’ including the designated fund allocation (as per below point) E-voucher cards shall have multiple fund entry features (i.e. funds can be loaded more than once and designated exclusively for different purposes e.g. x amount for food and y amount for hygiene kits) The system will be regularly updated with data showing which amounts have been redeemed on e-Vouchers cards User/Admin profiles, with specific user permissions (set up by Concern) and ☐ ☐ ☐ ☐ ☐ Provide Software for the ☐ management and monitoring of the E-Voucher Payment System ☐ ☐ ☐ ☐ ☐ ☐ ability to delete accounts remotely; if required User Manuals for both hardware (i.e. tools and equipment for merchants and Programme participants) and software (i.e. training in person, support via skype and/or technical assistance with the platform) in the required languages Ability to handle multiple projects (i.e. different donors), funds and assets during different periods and redeemed from numerous vendors Primary language settings must be available in English and Arabic, As well as supporting materials The platform must be able to function offline with only occasional internet access The E-Voucher can accept all levels of beneficiary transactions with no limits on minimum amounts spent Data information should include information on the following: Robust and secure back up system which minimizes the risk of losing data ☐ System offers an option for Programme participant verification (ID/PIN ☐ Number) Adheres to relevant national and international legislation for data ☐ Data Integrity and Data Protection protection including GDPR regulation. Company has a data protect...

Related to SYSTEM FUNCTIONALITY REQUIREMENTS

  • 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

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

  • Minimum System Requirements The following summarizes the minimum office system requirements for all Contractors and Architect/Engineer to possess in order to participate. It is the responsibility of all Contractors and Architect/Engineer to possess these minimum requirements at no additional cost to Princeton University.

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

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

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

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

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.

  • Technology Requirements The Customer is required to obtain and maintain, at the Customer’s own expense, compatible Electronic Channels, hardware, operating systems, and software approved for such use by Royal Bank, and which are up-to-date and unaltered from manufacturer specifications. Royal Bank is not responsible for, and makes no representations or warranties of any nature, with respect to any such Electronic Channels, hardware, operating systems, and software provided by any other Person. Royal Bank has the right, in its sole discretion, without notice, to make changes to this Service from time to time which may result in the Customer’s Electronic Channels, hardware, operating systems, and software no longer being compatible with this Service, and in such event, Royal Bank will have no responsibility or liability to the Customer or any other Person.

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