Solution Specification Clause Samples

The Solution Specification clause defines the detailed requirements, features, and standards that the delivered product or service must meet. It typically outlines technical parameters, performance criteria, and any specific deliverables expected from the provider, often referencing attached documents or schedules for clarity. By clearly setting out what is to be provided, this clause ensures both parties have a mutual understanding of expectations, reducing the risk of disputes over whether contractual obligations have been fulfilled.
Solution Specification. ‌ The following sections describe the solution specifications. 3.1. System Architecture‌ NiceVision Offload Server Inform The Nice solution includes the following components: • NiceVision Offload Server – service that manages the queue of offload tasks from the time the operator added new task to the queue, during the offload from the bus, until the point the new case is available on the Inform. • NiceVision Offload application – application for the operator to add new requests to offload video form the busses, and monitor the status of each request. • NiceVision SVR – total recording of 8 video channels with fixed retention on the bus, with external interface for exporting video from all channels upon network connectivity.
Solution Specification. Single server/site SEMAP+ with Operator Services, Messenger+, Mobility and Business Continuity, to provide North Yorkshire Police with an automated call routing and voicemail solution (for non emergency calls) capable of handling 600 calls per hour. And an additional replicated single server/site ‘hot standby’ system (a multi-site replicated solution is subject to a suitable VoIP and data network connection between sites).
Solution Specification. The solution specification will be agreed by both the Licensee and Licensor prior to the commencement of this agreement. The section below is to be completed based on the agreed scope of the project, with the details, timelines, and any associated costs or requirements for/from either the Licensee and/or Licensor captured in Appendix XXXX ‘The Statement of Work’. Within the current scope and statement of work defined within this document, additional integration to third-party software is required and listed below: The initial Territory for the use of the Solution will be defined as the United Kingdom.

Related to Solution Specification

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-▇▇▇▇▇-▇▇▇▇▇▇▇-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-▇▇▇▇▇-▇▇▇▇▇▇▇-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.