Essential Characteristics Clause Samples

The Essential Characteristics clause defines the fundamental features or attributes that a product, service, or subject matter must possess under the agreement. It typically outlines specific qualities, standards, or functionalities that are considered non-negotiable, such as technical specifications for equipment or core capabilities of a software application. By clearly identifying these key requirements, the clause ensures that both parties have a mutual understanding of what is being provided, reducing the risk of disputes over whether contractual obligations have been met.
Essential Characteristics. On-demand self-service - A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider. Broad network access - Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations). Resource pooling - The provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, and network bandwidth. Rapid elasticity - Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. Measured service - Cloud systems automatically control and optimize resource use by leveraging a metering capability1 at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
View SourceView Similar (6)
Essential Characteristics. On‐demand self‐service ‐ A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider. Broad network access ‐ Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., Resource pooling ‐ The provider’s computing resources are pooled to serve multiple consumers using a multi‐tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence in that the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter). Examples of resources include storage, processing, memory, and network bandwidth. Rapid elasticity ‐ Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. Measured service ‐ Cloud systems automatically control and optimize resource use by leveraging a metering capability1 at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service.
View SourceView Similar (4)
Essential Characteristics. Essential characteristic(s) of Educational Program, to be evaluated as School- Specific Measures within the OPSB Academic Performance Framework, if applicable, shall be as follows: N/A
View SourceView Similar (2)
Essential Characteristics. Treaty shopping typically involves three features:
View Source

Related to Essential Characteristics

  • Individual Characteristics Each Receivable has the following individual characteristics as of the Cut-Off Date: (i) each Receivable is secured by a new or used automobile, minivan or sport utility vehicle; (ii) each Receivable has a Contract Rate of no less than 0.00%; (iii) each Receivable had an original term to maturity of not more than 72 months and not less than 12 months and each Receivable has a remaining term to maturity, as of the Cut-Off Date, of 3 months or more; (iv) each Receivable has an Outstanding Principal Balance as of the Cut-Off Date of greater than or equal to $1,000.00; (v) no Receivable has a scheduled maturity date later than July 31, 2027; Schedule I-1 Schedule I to the Purchase Agreement (vi) no Receivable was more than 30 days past due as of the Cut-Off Date; (vii) as of the Cut-off Date, no Receivable was noted in the records of VCI or the Servicer as being the subject of any pending bankruptcy or insolvency proceeding; (viii) no Receivable is subject to a force-placed Insurance Policy on the related Financed Vehicle; and (ix) each Receivable is a Simple Interest Receivable.

  • Characteristics The Contracts have the following characteristics: (i) all the Contracts are secured by Motorcycles; (ii) no Contract has a remaining maturity of more than 84 months; and (iii) the final scheduled payment on the Contract with the latest maturity is due no later than September 6, 2031. Approximately 74.40% of the Pool Balance as of the Cutoff Date is attributable to loans for purchases of new Motorcycles and approximately 25.60% is attributable to loans for purchases of used Motorcycles. No Contract was originated after the Cutoff Date. No Contract has a Contract Rate less than 0.010%.

  • Physical File Characteristics 6.2.1 The Optional Daily Usage File will be distributed to CLEC-1 via an agreed medium with CONNECT:Direct being the preferred transport method. The Daily Usage Feed will be a variable block format (2476) with an LRECL of 2472. The data on the Daily Usage Feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis (Monday through Friday except holidays). Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. 6.2.2 Data circuits (private line or dial-up) may be required between BellSouth and CLEC-1 for the purpose of data transmission. Where a dedicated line is required, CLEC-1 will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with BellSouth. CLEC-1 will also be responsible for any charges associated with this line. Equipment required on the BellSouth end to attach the line to the mainframe computer and to transmit successfully ongoing will be negotiated on a case by case basis. Where a dial-up facility is required, dial circuits will be installed in the BellSouth data center by BellSouth and the associated charges assessed to CLEC-1. Additionally, all message toll charges associated with the use of the dial circuit by CLEC-1 will be the responsibility of CLEC-1. Associated equipment on the BellSouth end, including a modem, will be negotiated on a case by case basis between the parties. All equipment, including modems and software, that is required on CLEC-1 end for the purpose of data transmission will be the responsibility of CLEC-1.

  • ODUF Physical File Characteristics 6.2.1 ODUF will be distributed to TWTC via Secure File Transfer Protocol (FTP). The ODUF feed will be a variable block format. The data on the ODUF feed will be in a non-compacted EMI format (175 byte format plus modules). It will be created on a daily basis Monday through Friday except holidays. Details such as dataset name and delivery schedule will be addressed during negotiations of the distribution medium. There will be a maximum of one dataset per workday per OCN. If AT&T determines the Secure FTP Mailbox is nearing capacity levels, AT&T may move the customer to CONNECT: Direct file delivery. 6.2.2 If the customer is moved, CONNECT: Direct data circuits (private line or dial-up) will be required between AT&T and TWTC for the purpose of data transmission. Where a dedicated line is required, TWTC will be responsible for ordering the circuit, overseeing its installation and coordinating the installation with AT&T. TWTC will also be responsible for any charges associated with this line. Equipment required on the AT&T end to attach the line to the mainframe computer and to transmit messages successfully on an ongoing basis will be negotiated on an individual case basis. Any costs incurred for such equipment will be TWTC's responsibility. Where a dial-up facility is required, dial circuits will be installed in the AT&T data center by AT&T and the associated charges assessed to TWTC. Additionally, all message toll charges associated with the use of the dial circuit by TWTC will be the responsibility of TWTC. Associated equipment on the AT&T end, including a modem, will be negotiated on an individual case basis between the Parties. All equipment, including modems and software, that is required on TWTC end for the purpose of data transmission will be the responsibility of TWTC. 6.2.3 If TWTC utilizes FTP for data file transmission, purchase of the FTP software will be the responsibility of TWTC.

  • Configuration The configuration for the Purchase Right Aircraft will be the Detail Specification for Model 767-3S2F aircraft at the revision level in effect at the time of the Supplemental Agreement. Such Detail Specification will be revised to include (i) changes required to obtain required regulatory certificates and (ii) other changes as mutually agreed upon by Boeing and Customer.