Generic Requirements Sample Clauses

Generic Requirements. 2.1.1 This section provides generic requirements that are applicable to all of the service Lots. Requirements that are Lot-specific can be found in the following sections of this document:
Sample 1Sample 2Sample 3See All (8)
Generic Requirements.  All feeds should be in JSON format  Each feed should have a [unique URL], which can accept parameters Required screens and feeds from Kew CMS:  Dashboard screen and feed. Configuration items: AR load radius (metres) Special message title Special message body Homescreen image identifier Names of Flickr collections to be used in Collections section. There will not be a fixed number of collections, but there will be at least 1. Price and opening time details on support screen Map/filter categories (e.g. „Off the beaten track‟), subcategories (e.g. „hidden gems‟) and default items (e.g. „Duke‟s Garden‟) Section and sub-section intro, where not pulled from Flickr Define default order for items in See Today section.  News feed - feed of all [news and blog articles] marked with „for mobile‟. Feed should include [image URL, title, caption and description] Fields are slightly different between news and blog items – to be finalised by Kew and supplier.  Attractions feed. Fields to be finalised by Kew and supplier.  Species page feed. Fields to be finalised by Kew and supplier.  Tree profile feed. Fields to be finalised by Kew and supplier.  AR screen and feed. Fields to be finalised by Kew and supplier.  Plant code feed – short URLs for Flickr sets and video URLs  Content hard-coded into app  Loader image  Section intro text – for each section and sub-section  Intro blurb on all other screens  Map base layer – and if possible all tiles  All screen graphics
Sample 1Sample 2
Generic Requirements. The SIA shall undertake detailed site survey immediately after award of the contract, to address the various requirements such as space, identification of input terminals, and availability of air- conditioning, spare contacts etc for completion of engineering, site installation, testing and commissioning of the project. The type and number of hardware and software elements (Bill of Quantity) within the scope of the project to be supplied for the various sites are identified in the Appendices. The individual functions to be performed by the hardware and software and system sizing criteria are described in the relevant sections. The specification defines requirements on functional basis and does not intend to dictate a specific design. On the other hand certain minimum requirements must be met in accordance with the particular details provided elsewhere in the specification. The items, which are not specifically identified but are required for completion of the project within the intent of the specification, shall also be supplied & installed without any additional cost implication to the Purchaser. The Bidder's proposal shall address all functional, availability and performance requirements within this specification and shall include sufficient information and supporting documentation in order to determine compliance with this specification without further necessity for enquiries. An analysis of the functional , availability and performance requirements of this specification and/or site surveys, design, and engineering may lead the Contractor to conclude that additional items and services are required that are not specifically mentioned in this specification. The Contractor shall be responsible for providing at no added cost to the employer all such additional items and services such that a viable and fully functional system is implemented that meets or exceeds the capacity, and performance requirements specified. Such materials and services shall be considered to be within the scope of the contract. To the extent possible, the Bidders shall identify and include all such additional items and services in their proposal. All equipment provided shall be designed to interface with existing equipment (if any) and shall be capable of supporting all present requirements and spare capacity requirements identified in this specification. The offered items shall be designed to operate in varying environments. Adequate measures shall be taken to provide protection agai...
Sample 1
Generic Requirements. Tandem Switching ---------------- Bellcore TR-TSY-000540, Issue 2R2, Tandem Supplement, 6/1/90 GR-905-CORE GR-1429-CORE GR-2863-CORE GR-2902-CORE Performance Standards --------------------- Bellcore FR-64, LATA Switching Systems Generic Requirements (LSSGR) Sch. 2.3 - 4 Bellcore TR-NWT-000499, Issue 5, Rev 1, April 1992, Transport Systems Generic Requirements (TSGR): Common Requirements Bellcore TR-NWT-000418, Issue 2, December 1992, Generic Reliability Assurance Requirements For Fiber Optic Transport Systems Bellcore TR-NWT-000057, Issue 2, January 1993, Functional Criteria for Digital Loop Carriers Systems Bellcore TR-NWT-000507, Issue 5, December 1993, LSSGR - Transmission, Section 7 Bellcore TR-TSY-000511, Issue 2, July 1987, Service Standards, a Module (Section 11) of LATA Switching Systems Generic Requirements (LSSGR, FR-NWT-000064) BELLCORE TR-NWT-000393, January 1991, Generic Requirements for ISDN Basic Access Digital Subscriber Lines Bellcore TR-NWT-000909, December 1991, Generic Requirements and Objectives for Fiber In The Loop Systems Bellcore TR-NWT-000505, Issue 3, May 1991, LSSGR Section 5, Call Processing Bellcore LSSGR TR-TSY-000511 Bellcore TR-NWT-001244, Clocks for the Synchronized Network: Common Generic Criteria ANSI T1.105 -1995 Network Interface Device ------------------------ Bellcore Technical Advisory TA-TSY-000120, "Customer Premises or Network Ground Wire" Bellcore Generic Requirement GR-49-CORE, "Generic Requirements for Outdoor Telephone Network Interface Devices" Bellcore Technical Requirement TR-NWT-00239, "Indoor Telephone Network Interfaces" Bellcore Technical Requirement TR-NWT-000937, "Generic Requirements for Outdoor and Indoor Building Entrance" Interconnection --------------- Trunking Interconnection ------------------------- GR-317-CORE, Switching System generic requirements for Call Control Using the Integrated Services Digital Network User Part (ISDNUP), Bellcore, February, 1994 GR-394-Core, Switching System generic requirements for Interexchange Carrier Interconnection Using the Integrated Services Digital Network User Part (ISDNUP), Bellcore, February, 1994 FR-NWT-000064, LATA Switching Systems Generic Requirements (LSSGR), Bellcore, 1994 Edition ANSI T1. 111 ANSI T1. 112 ANSI T1. 113 Sch. 2.3 - 5 Bellcore GR-905-CORE, Common Channel Signaling Network Interface Specification (CCSNIS) Supporting Network Interconnection, Message Transfer Part (MTP), and Integrated Services Digital Network User Part (ISDNUP) Bellcore...
Sample 1
Generic Requirements. Tandem Switching ---------------- Bellcore TR-TSY-000540, Issue 2R2, Tandem Supplement, 6/1/90 GR-905-CORE GR-1429-CORE GR-2863-CORE GR-2902-CORE
Sample 1

Related to Generic 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:

  • FINRA Requirements (A) You represent that you are a member in good standing of FINRA, or a non-U.S. bank, broker, dealer, or institution not eligible for membership in FINRA or a Bank.

  • Compliance with Regulatory Requirements Upon demand by Lender, Borrower shall reimburse Lender for Lender’s additional costs and/or reductions in the amount of principal or interest received or receivable by Lender if at any time after the date of this Agreement any law, treaty or regulation or any change in any law, treaty or regulation or the interpretation thereof by any Governmental Authority charged with the administration thereof or any other authority having jurisdiction over Lender or the Loans, whether or not having the force of law, shall impose, modify or deem applicable any reserve and/or special deposit requirement against or in respect of assets held by or deposits in or for the account of the Loans by Lender or impose on Lender any other condition with respect to this Agreement or the Loans, the result of which is to either increase the cost to Lender of making or maintaining the Loans or to reduce the amount of principal or interest received or receivable by Lender with respect to such Loans. Said additional costs and/or reductions will be those which directly result from the imposition of such requirement or condition on the making or maintaining of such Loans.

  • 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

  • Compliance with Requirements Any investment program furnished, and any activities performed, by the Manager or by a Sub-Adviser under this Section shall at all times conform to, and be in accordance with, any requirements imposed by: (1) the Act and any rules or regulations in force thereunder; (2) any other applicable laws, rules and regulations; (3) the Declaration of Trust and By-Laws of the Fund as amended from time to time; (4) any policies and determinations of the Board of Trustees of the Fund; and (5) the fundamental policies of the Fund, as reflected in its Registration Statement under the Act or as amended by the shareholders of the Fund.

  • Compliance with Reporting Requirements The Company is subject to and in full compliance with the reporting requirements of Section 13 or Section 15(d) of the Exchange Act.

  • Securities Law Requirements If at any time the Board or Committee determines that issuing Stock pursuant to this Agreement would violate applicable securities laws, the Corporation will not be required to issue such Stock. The Board or Committee may declare any provision of this Agreement or action of its own null and void, if it determines the provision or action fails to comply with applicable securities laws. The Corporation may require Participant to make written representations it deems necessary or desirable to comply with applicable securities laws.

  • Securities Laws Requirements The Company shall not be obligated to transfer any Common Stock to the Participant free of the restrictive legend described in Section 4 hereof or of any other restrictive legend, if such transfer, in the opinion of counsel for the Company, would violate the Securities Act of 1933, as amended (the "Securities Act") (or any other federal or state statutes having similar requirements as may be in effect at that time).

  • ERISA Requirements (a) Borrower will not engage in any transaction which would cause an obligation, or action taken or to be taken under this Loan Agreement (or the exercise by Lender of any of its rights under the Note, this Loan Agreement or any of the other Loan Documents) to be a non-exempt prohibited transaction under ERISA or Section 4975 of the Tax Code.

  • Additional Regulatory Requirements Notwithstanding anything contained in this Agreement to the contrary, it is understood and agreed that the Bank (or any of its successors in interest) shall not be required to make any payment or take any action under this Agreement if:

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