Other Non-Functional Requirements Sample Clauses

Other Non-Functional Requirements. A National Fire and Protection Association (NFPA) System installation shall be performed in compliance with NFPA standards. B Federal Communications Commission (FCC) Rules, Part 15 and Part 101 System shall be compliant with all applicable FCC rules C Institute of Electrical and Electronic Engineers (IEEE) System shall be compliant with all applicable IEEE standards. D American National Standards Institute (ANSI) System shall be compliant with all applicable ANSI standards. E Electronics Industry Association (EIA) • System shall be compliant with all applicable EIA standards. F Telecommunications Industry Association (TIA) System shall be compliant with all applicable TIA standards. G Association of Public‐Safety Communications Officials International, Inc. (APCO) System shall be compliant with all applicable APCO standards. H System shall be compliant with all applicable Project 25 (P25) standards which refers to a suite of standards for digital radio communications that has become the “de facto” standard for public safety radio systems in North America. The P25 standards suite was developed under the guidance of the LMR AND THE P25 SUITE OF STANDARDS Interoperable, Wireless Communications for the Public Safety Industry APCO (Association of Public Safety Communications Officials) organization and is published and administered by the Telecommunications Industry Association (TIA) standards body. The P25 suite of standards was developed to address a number of spectrum and interoperability issues related LMR radio communications. • The Federal Communications Commission’s (FCC) mandate to improve radio spectrum efficiency • The need to implement voice processing and advances in digital technologies and modulation techniques that improve voice quality The many proprietary implementations of APCO Project 16 and earlier LMR solutions that restricted component interoperability and competition • The requirement for effective, efficient, and reliable intra‐ and inter‐agency communications • The growing emphasis on encryption and data. I System shall be compliant with all applicable Project 25 (P25) standards including Open Interfaces: The growing emphasis P‐ 25 Open Interfaces ‐ An open P25 interface connects one network component with another. The P25 standard defines the electrical characteristics the connection must have, the signals that will be sent between the components over the connection, and what each signal will mean. The P25 suite of standards specifies ...
Sample 1
AutoNDA by SimpleDocs
Other Non-Functional Requirements. The aim of the project is to build an efficient and sustainable aggregation infrastructure. Therefore it is necessary to define qualitative requirements to specify what efficiency means.
Sample 1

Related to Other Non-Functional Requirements

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

  • Additional Requirements As a condition precedent to the execution and Delivery, the registration of issuance, transfer, split-up, combination or surrender, of any ADS, the delivery of any distribution thereon, or the withdrawal of any Deposited Property, the Depositary or the Custodian may require (i) payment from the depositor of Shares or presenter of ADSs or of an ADR of a sum sufficient to reimburse it for any tax or other governmental charge and any stock transfer or registration fee with respect thereto (including any such tax or charge and fee with respect to Shares being deposited or withdrawn) and payment of any applicable fees and charges of the Depositary as provided in Section 5.9 and Exhibit B, (ii) the production of proof reasonably satisfactory to it as to the identity and genuineness of any signature or any other matter contemplated by Section 3.1, and (iii) compliance with (A) any laws or governmental regulations relating to the execution and Delivery of ADRs or ADSs or to the withdrawal of Deposited Securities and (B) such reasonable regulations as the Depositary and the Company may establish consistent with the provisions of the representative ADR, if applicable, the Deposit Agreement and applicable law.

  • Operational Requirements 4 At-Sea Monitors are deployed, in accordance with coverage rates developed by 5 NMFS and as assigned through the Pre-Trip Notification System (PTNS), to 6 vessels. Due to availability of funding, changes in the fishery management, 7 such as emergency closures, court ordered closures, weather, and unforeseen 8 events must remain flexible. Additional funding for sea days may be added to 9 the contract within the scope and maximum allowable sea days. 10 The following items define the operational services to be provided by the 11 contractor under this contract.

  • General Requirements The Contractor hereby agrees:

  • Closet/Urinal Requirements 6.1 Employees Closets Urinals 1-5 1 Nil 6-10 1 1 11-20 2 2 21-35 3 4 36-50 4 6 51-75 5 7 76-100 6 8

  • FEDERAL REQUIREMENTS In the event this Contract is paid in whole or in part from any federal government agency or source, the specific terms, regulations and requirements governing the disbursement of these funds shall be specified herein and become a part of this clause.

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

  • HIPAA Requirements The Parties agree that the provisions under HIPAA Rules that are required by law to be incorporated into this Amendment are hereby incorporated into this Agreement.

  • General Requirement Any notice, election, demand, request, consent, approval, or other communication required or permitted to be given under this Contract shall be in writing signed by an officer or duly authorized representative of the party making same and shall be delivered personally or shall be sent by certified or statutory mail, postage prepaid, return receipt requested, shall be effective as of the date on which it is received or would have been received but for the refusal of the addressee to accept delivery, and shall be addressed as shown in the Contract. The persons and addresses to which notices should be given may be changed by notice given in accordance with this Article.

  • Procedural and Operational Requirements By accepting and using the Financial Assistance awarded under this Agreement and for this Program Element, LPHA agrees to conduct activities in accordance with the following requirements:

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