System Specification Sample Clauses

System Specification. The system specification for TULIPP use cases is based on the above analysis: Scalability: different types of MPSoCs (computing power/energy consumption) should be available The specification contains many more or less “hard” requirements, but it does not select the hardware components definitely in all cases. In complex cases, additional parameters must be analysed to make a decision: costs, availability, reliability, support, etc.
View Source
System Specification. CorporateSMS Server: Contents: CorporateSMS Administration Interface: Features: MAILSMS Features: Contents: EASYSMS Features: Contents:
View Source
System Specification. RCC has commissioned, during 2015.16, the installation of an expanded and upgraded CCTV system across Uppingham town centre. This system will remain in the ownership of RCC. This system now comprises 8 cameras, each in a separate location, each strategically positioned to maximise the coverage and being mindful of known areas of crime and disorder. Appendix 1 identifies each camera location. These cameras are all linked via a wireless network and feed into a server for storage of data and further links to monitoring agents. The required broadband connection utilises an existing line provided by UTC. As such, RCC will make an annual contribution to UTC, in the form of an adjustment to the other contributions owed (see section 6 below). All of the cameras are high definition and pan/tilt/zoom (i.e. movable), with ‘white light’ and infra-red capabilities.
View Source
System Specification. A Deontic Approach. PhD thesis, Imperial College of Science and Technology, University of London.
View Source
System Specification. A Deontic Ap- proach. PhD thesis, Imperial College of Science and Technology, University of London. ▇▇▇▇▇▇, ▇. (1999). Communicating and Mobile Systems: the π-Calculus. Cambridge University Press.
View Source
System Specification. The procurement and supplies management department at Princess Alexandra Hospital NHS Trust (the trust), is embarking on a modernisation agenda to transform procurement and sourcing. Central to the procurement strategy framework of the trust is implementation of strategic sourcing and contracts management to enhance visibility of its expenditure landscape and deliver supply chain excellence. The contract authority therefore seeks offers from providers of e-sourcing systems to enable the attainment of this strategic goal. The Princess Alexandra Hospital NHS Trust seeks to enter into contract with the successful supplier. The Contract shall run for a period of 2 years with an option to extend for a further 2x12months.
View Source
System Specification. The system specification must be clearly defined and reflect characteristics of the chosen application.
View Source
System Specification. The webserver has all the business logic written in PHP scripts. The customer details including bid details and auction details are held in the PostgreSQL database also on the webserver. Customers are notified of auction and bid details by email or by logging into their account.
View Source
System Specification 
View Source

Related to System Specification

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

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

  • Technical Specifications The purpose of the Technical Specifications (TS), is to define the technical characteristics of the Goods and Related Services required by the Procuring Entity. The Procuring Entity shall prepare the detailed TS consider that:

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