Requirements of the system Sample Clauses

Requirements of the system. To develop the use case mentioned before we need two embedded devices with Android+WebRTC support and a HDMI connection, two external cameras with microphone, two monitors or TV with this interface available and a PC/laptop with a WebRTC-enabled browser. To run the WebRTC Application Controller we will use a general purpose virtual machine based on VMware that will host an OVA with this element ready. As embedded device we have chosen the XXXXX NEO X7 Mini, a device that was released in September 2013. It is the scaled-down version of the NEO X7 but with similar capacities in terms of CPU and RAM. This element is part of the family of Android TVs (linked with elements like HDMI dongles, AppleTV or ChromeCasts). It runs an Android 4.2.2 with different web browsers that can run WebRTC applications. This element has an HDMI interface (thought to be plugged into a TV) with 1080p HD video. Supports mouse and keyboard, and it’s easy to add a camera a microphone to have a complete WebRTC session. In addition, it has been designed to support Android games, so video processing capacities is enough to deal with video contents over WebRTC. The main features of this device are: Processor Quad-Core Cortex A9 Processor GPU Quad-Core Mali 400 Memory 2GB DDR3 Internal Storage 8GB NAND Flash Wireless Connectivity 802.11n Wi-Fi, Bluetooth 4.0 OS Android™ Jelly Bean 4.2.2 The WebRTC Application Controller will run on a virtual machine based on VMware with following minimum requirements:  Architecture Intel x86 processors, 64 bits  Number of CPU cores 1x CPU core  Processor speed 2.0 GHz or higher  RAM At least 1 GB memory  Disk space 18 GB hard drive or higher  Network Interfaces Single Ethernet 1000base-TX NICs  IP Addressing One (1) IP address The rest of the elements like PC/laptop and TV/monitor will be generic, as they are not critical to evaluate the results of this use case. The cameras for the embedded devices will be HD 1280*720 from Logitech (model c920) with embedded microphone. It is important to mention that WebRTC is supporting this media quality: For audio it uses Opus codec. This is a royalty free codec defined by IETF RFC 6176. It supports constant and variable bitrate encoding from 6 kbit/s to 510 kbit/s, frame sizes from 2.5 ms to 60 ms, and various sampling rates from 8 kHz (with 4 kHz bandwidth) to 48 kHz (with 20 kHz bandwidth, where the entire hearing range of the human auditory system can be reproduced). For video it uses VP8 or H264. We will w...
AutoNDA by SimpleDocs
Requirements of the system. The main requirements of the envisioned use cases may be categorized as follows.  Development of an interconnection possibility for systems of mixed-criticality over open net- works  Integration possibility for existing, heterogeneous devices and systems into the mixed-criticality network infrastructure  Co-existence of messages belonging to different traffic classes on one physical network (time- and space partitioning)  Compliance to established standards of the Internet world, in particular of the IEEE 802.1 family  Definition of mechanism that allow the dynamic integration of new devices or new messages on the network. For the tactical voice communication system demonstrator the key requirements are:  Mixed criticality applications shall be separated on different cores and/or on different operating systems on the same platform.  The Frequentis Linux distribution shall be ported to a multicore architecture.  A concept for the utilization of a hypervisor shall be developed.
Requirements of the system. The main requirements of the envisioned system may be categorized as follows. The system should be:  Pervasive, in the terms of becoming as much unnoticed by the user as possible, while fulfilling all his needs  Autonomous, in the terms of being able to (i) Operate with as less human interaction as possible, (ii) Incorporate context - awareness with respect to the knowledge of the environment (iii) Incorporate context – awareness with respect to the knowledge of the user’s state (iv) Apply self – healing and self – optimization procedures  Secure  Energy – aware, ensuring that the system leads to less energy consumption when compared to a typical home’s operation  Efficient, in terms of data gathering within wireless network  Service oriented, developing WPAN/LAN Gateway which will provide SoA platform.
Requirements of the system. The current demonstrator inherits the requirements already addressed on WP1, WP4 and WP6. Because these requirements have been properly addressed and explained on those workpackets and for the sake of concretion, on this deliverable we focus only on the requirements strictly assigned to this use case. They are listed on the next table 2. These requirements address three EMC2 and energy domain topics. The first one is related with the effective use of the multicore processor for this market. The open possibilities of such devices allowing integration on the same devices much functionality with reduced power and enhanced performance. Moreover, if the proper critical design rules are followed and proper arbitration mechanism are used for the shared resources, multicore architectures allows the utilization on a single devices for mixed critically applications, reducing system power, space and cost. The effective utilization of these architectures for the Smart Grid market is here provided by Telvent`s RTU while the enhanced synchronization capabilities is provided by Seven Solutions. The second requirement focuses on the utilization of a redundant network topology. This can be easily asserted by the ring-like topology of the demonstrator and significantly is related with the determinism of the solution here proposed. Finally, the last requirement is related with the proper distribution of the high accurate time information. As commented this is a key property for many operations of the Smart Grid and particularly for the PMUs. Table 2: High level requirements for the demonstrator of the Synchronized low-latency deterministic networks use case. Requirement ID: <Participant>-<Req. ID> Category <Functional / non- Functional> Sub Category <HW, SW, …> Short Description:<Req. Name> Description:<Req. Description> Verification Method<Description how to verify> Rationale:<The rationale behind this req.> HL-REQ-WP11-002 Non-Functional Safety Effective use of multicore embedded systems in the energy domain. Enable the effective use of multicore embedded systems in the energy domain with special attention to synchronization and safety as defined in the relevant standards. Validated in the use case UC11.5 Tackle challenges in the energy domain posed by multi-core embedded systems, by applying new low latency networks with high accuracy time synchronization, and safety concepts. HL-REQ-WP11-005 Functional System Redundant topology networks based on HSR/PRP configurations. A...

Related to Requirements of the system

  • Activities of the Subadviser Except to the extent necessary to perform its obligations hereunder, nothing herein shall be deemed to limit or restrict the Subadviser's right, or the right of any of the Subadviser's directors, officers or employees to engage in any other business or to devote time and attention to the management or other aspects of any other business, whether of a similar or dissimilar nature, or to render services of any kind to any other corporation, trust, firm, individual or association.

  • Procurement of the Site (i) The Authority Representative, the Contractor and Authority’s Engineer shall, within 10 (ten) days of the date of this Agreement, inspect the Site and prepare a detailed memorandum containing an inventory of the Site including the vacant and unencumbered land, buildings, structures, road works, trees and any other immovable property on or attached to the Site (hereinafter referred to as the “Handover Memorandum”). Subject to the provisions of Clause 8.2 (iii), the Handover Memorandum shall have appended thereto an appendix (the “Appendix”) specifying in reasonable detail those parts of the Site to which vacant access and Right of Way has not been given to the Contractor along with details of hindrances in the Construction Zone. For sake of clarity the Handover Memorandum shall clearly specify the parts of Site where work can be executed. Signing of the Handover Memorandum, in three counterparts (each of which shall constitute an original), by the authorized representatives of the Authority, Contractor and Authority’s Engineer shall be deemed to constitute a valid evidence of giving the Right of Way to the Contractor for discharging its obligations under and in accordance with the provisions of this Agreement and for no other purpose whatsoever. (ii) Whenever the Authority is ready to hand over any part or parts of the Site included in the Appendix, it shall inform the Contractor, by notice, of the proposed date and time such of hand over. The Authority Representative and the Contractor shall, on the date so notified, inspect the specified parts of the Site, and prepare a memorandum containing an inventory of the vacant and unencumbered land, buildings, structures, road works, trees and any other immovable property on or attached to the Site so handed over. The signing of the memorandum, in three (3) counterparts (each of which shall constitute an original), by the authorised representatives of the Parties shall be deemed to constitute a valid evidence of giving the relevant Right of Way to the Contractor. If the contractor fails to join for site inspection or disputes the parts of the site available for work, the Authority’s Engineer shall decide the parts of the site where work can be executed and notify to both the parties within 3 days of the proposed date of inspection. The parties agree that such notification of the Authority’s Engineer as mentioned hereinabove shall be final and binding on the parties. (iii) The Authority shall provide the Right of Way to the Contractor in respect of all land included in the Appendix by the date specified in Schedule-A for those parts of the Site referred to therein, and in the event of delay for any reason other than Force Majeure or breach of this Agreement by the Contractor, it shall pay to the Contractor, Damages in a sum calculated in accordance with Clause 8.3. The Contractor agrees that it shall not be entitled to claim any other damages on account of any such delay by the Authority. (iv) Notwithstanding anything to the contrary contained in this Clause 8.2, the Authority shall specify the parts of the Site, if any, for which Right of Way shall be provided to the Contractor on the dates specified in Schedule-A. Such parts shall also be included in the Appendix prepared in pursuance of Clause 8.2 (i). (v) The Authority further acknowledges and agrees that prior to the Appointed Date, it shall have procured issuance of the statutory notification under Applicable Laws for vesting of all the land comprising the Project in the Authority and has taken possession of area for Construction Zone for at least 90% (ninety per cent) of the total length of the Project Highway. The Parties also acknowledge and agree that the conditions specified in this Clause 8.2 (iii) shall not be modified or waived by either Party. (vi) For the avoidance of doubt, the Parties expressly agree that the Appendix shall in no event contain sections of the Project Highway the cumulative length of which exceeds 10% (ten percent) of the total length of the Project Highway. (vii) Pursuant to signing of Handover Memorandum under clause 8.2 (i), Contractor shall submit to the Authority’s Engineer, a monthly land possession report till expiry of 180 (one hundred and eighty) days from Appointed Date, in respect of those parts of the site to which vacant access and right of way was not given to the contractor and included in Appendix to the memorandum signed under clause 8.2 (i), duly specifying the part of the site, if any, for which the right of way is yet to be handed over.

  • Obligations of the Service Provider 3.1. The Service Provider undertakes to provide the services as set out online within the dedicated Hoople Schools portal to this Agreement (the ‘Services’), in consideration of the payment as set out in the dedicated Hoople Schools portal. The Service Provider has undertaken Payment calculation based on the following terms: 3.1.1. payment for services relating to employee numbers has been calculated based on the number of employees at each Establishment as at January 2020. Included in the calculation is a 5% tolerance. If employee numbers rise above this 5% tolerance Hoople reserves the right to charge incremental fees 3.1.2. payment for the Payments Management service has been based on the number of payment vouchers raised in 2018/19, within a 10% tolerance level. The Service Provider reserves the right to increase pricing if volumes increase by more than the stated tolerance level 3.1.3. should the Establishment request an additional service during the duration of the term, the Service Provider reserves the right to charge the full, annual cost of the requested service 3.1.4. payment for services relating to pupil numbers has been calculated based on the number of pupils at each Establishment as at October 2019. Included in the calculation are sixth form and nursery pupil numbers, where applicable 3.1.5. The Service Provider will provide digital order confirmation of the services ordered and associated fees by means of the functionality of the Hoople Schools portal 3.2. Should the Establishment request and the Service Provider agrees to provide services additional to those specified within the schools buying portal order, the fees for those additional services shall be mutually agreed between the parties, but otherwise for all purposes of this Agreement, the additional services shall be deemed to be included within the definition of Services. 3.3. The Services shall be carried out by the Service Provider with all reasonable skill and care, and in full compliance of relevant established current professional standards. The Service Provider undertakes to provide a detailed service level agreement (SLA), outlining the responsibilities of both parties with regard to each service. The SLA for each service will be provided as a downloadable document on the Hoople Schools portal. 3.4. The Service Provider shall indemnify the Establishment from all claims, actions or demands made by third parties against the Establishment, and all liabilities of the Establishment to third parties (collectively ‘Third Party Liabilities’) and from all damage, losses, costs, expenses and payments whatsoever suffered or incurred by the Establishment either directly or in relation to Third Party Liabilities in respect of (a) personal injury to or the death of any person and any loss or destruction of or damage to property (not attributable to any default or neglect of the Establishment or of any person for whom the Establishment is responsible) which shall have occurred in connection with the provision of the Services under this Agreement, (b) any defect in the Services, and (c) any breach by the Service Provider of any terms of this Agreement, including without limitation, clause

  • Responsibilities of the Seller (a) Anything herein to the contrary notwithstanding, the Seller shall: (i) perform all of its obligations, if any, under the Contracts related to the Pool Receivables to the same extent as if interests in such Pool Receivables had not been transferred hereunder, and the exercise by the Administrator, the Purchaser Agents or the Purchasers of their respective rights hereunder shall not relieve the Seller from such obligations, and (ii) pay when due any taxes, including any sales taxes payable in connection with the Pool Receivables and their creation and satisfaction. The Administrator, the Purchaser Agents or any of the Purchasers shall not have any obligation or liability with respect to any Pool Asset, nor shall any of them be obligated to perform any of the obligations of the Seller, Servicer, WESCO or the Originators thereunder. (b) WESCO hereby irrevocably agrees that if at any time it shall cease to be the Servicer hereunder, it shall act (if the then-current Servicer so requests) as the data-processing agent of the Servicer and, in such capacity, WESCO shall conduct the data-processing functions of the administration of the Receivables and the Collections thereon in substantially the same way that WESCO conducted such data-processing functions while it acted as the Servicer.

  • Obligations of the Seller The obligations of the Seller under this Agreement will not be affected by reason of any invalidity, illegality or irregularity of the 2024-B Exchange Note or any 2024-B Lease or 2024-B Vehicle allocated to the 2024-B Reference Pool.

  • Covenants of the Subadviser (a) Subadviser will promptly notify the Trust and Manager in writing of the occurrence of any event which could have a material impact on the performance of its obligations pursuant to this Agreement, including without limitation: (i) the occurrence of any event which could disqualify Subadviser from serving as an investment adviser of a registered investment company pursuant to Section 9(a) of the Investment Company Act or otherwise; (ii) any material change in the Subadviser’s overall business activities that may have a material adverse effect on the Subadviser’s ability to perform under its obligations under this Agreement; (iii) any event that would constitute a change in control of Subadviser; (iv) any change in the portfolio manager(s) of the Fund; (v) any proposed change or change in the representations made by Subadviser concerning the nature of the Subadviser’s business plan; and (vi) the existence of any pending or threatened audit, investigation, complaint, examination or other inquiry (other than routine regulatory examinations or inspections) relating to the Fund conducted by any state or federal governmental regulatory authority. (b) Subadviser agrees that it will promptly supply Manager with copies of any material changes to any of the documents provided by Subadviser pursuant to Section 3.1.

  • Liability of the Subadviser (a) In the absence of willful misfeasance, bad faith, gross negligence or reckless disregard of obligations or duties ("disabling conduct") hereunder on the part of the Subadviser (and its officers, directors/trustees, agents, employees, controlling persons, shareholders and any other person or entity affiliated with the Subadviser) the Subadviser shall not be subject to liability to the Adviser (and its officers, directors/trustees, agents, employees, controlling persons, shareholders and any other person or entity affiliated with the Adviser) or to the Trust (and its officers, directors/trustees, agents, employees, controlling persons, shareholders and any other person or entity affiliated with the Trust) for any act or omission in the course of, or connected with, rendering services hereunder, including without limitation, any error of judgment or mistake of law or for any loss suffered by any of them in connection with the matters to which this Agreement relates, except to the extent specified in Section 36(b) of the Act concerning loss resulting from a breach of fiduciary duty with respect to the receipt of compensation for services. Except for such disabling conduct, the Adviser shall indemnify the Subadviser (and its officers, directors, partners, agents, employees, controlling persons, shareholders and any other person or entity affiliated with the Subadviser) from any and all losses, claims, damages, liabilities or litigation (including reasonable legal and other expenses) arising from Subadviser's rendering of services under this Agreement. (b) The Subadviser agrees to indemnify and hold harmless the Adviser (and its officers, directors/trustees, agents, employees, controlling persons, shareholders and any other person or entity affiliated with the Adviser) and/or the Trust (and its officers, directors/trustees, agents, employees, controlling persons, shareholders and any other person or entity affiliated with the Trust) against any and all losses, claims, damages, liabilities or litigation (including reasonable legal and other expenses), to which the Adviser and/or the Trust and their affiliates or such directors/trustees, officers or controlling person may become subject under the Act, the 1933 Act, under other statutes, common law or otherwise, which arise from the Subadviser's disabling conduct, including but not limited to any material failure by the Subadviser to comply with the provisions and representations and warranties set forth in Section 1 of this Agreement; provided, however, that in no case is the Subadviser's indemnity in favor of any person deemed to protect such other persons against any liability to which such person would otherwise be subject by reasons of willful misfeasance, bad faith, or gross negligence in the performance of his, her or its duties or by reason of his, her or its reckless disregard of obligations and duties under this Agreement.

  • Conditions to Obligations of the Seller The obligations of the Seller to consummate the transactions contemplated by this Agreement shall be subject to the fulfillment or written waiver, at or prior to the Closing, of each of the following conditions:

  • Covenants of the Sellers Each Seller, severally and not jointly, covenants with each Underwriter as follows: (a) Each Seller will deliver to each Underwriter (or its agent), prior to or at the Closing Date, a properly completed and executed Internal Revenue Service (“IRS”) Form W-9 or an IRS Form W-8, as appropriate, together with all required attachments to such form.

  • Grading systems of the institutions [It is recommended that receiving institutions provide the statistical distribution of grades according to the descriptions in the ECTS users’ guide7. A link to a webpage can be enough. The table will facilitate the interpretation of each grade awarded to students and will facilitate the credit transfer by the sending institution.]

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