Asset Specificity Sample Clauses

Asset Specificity. Asset specificity of a transaction refers to the degree to which assets are tailored to a specific transaction. It can be physical or human assets (Xxxxx and Xxxxxxxxx, 2002), refer to the transferability of assets that support a given transaction. An asset is said to be transaction specific if it cannot be redeployed in an alternative use without significant loss in value. It might be physical or human assets. (Xxxxx and Xxxxxxxxx, 2002) Highly asset-specific investments (also called relationship-specific investments) represent costs that have little or no value outside the exchange relationship. These costs are mainly in the form of human specificity (e.g. training of salespeople specifically for a certain partner) or physical specificity (e.g. investment by a supplier in equipment, tools, jigs, and fixtures to cater to idiosyncratic needs of a manufacturer). Investments in information systems that primarily serve the needs of one unique customer and cannot be leveraged across other external parties would also be another form of asset-specific investment. Xxxxxx and Xxxxxxxxxxx (1994) suggest that, using proprietary systems increases business process asset specificity. Inducement of Information Technology into the relationship reconfigures the existing processes and creates procedural specificity (Mukhopadhyay and Xxxxx, 2002), whereby firms develop processes (with or without Information Technology, Just in Time etc.) that are unique to the relationship and which may require learning time if developed with other suppliers.
AutoNDA by SimpleDocs

Related to Asset Specificity

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-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.

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Project Specific Milestones In addition to the milestones stated in Section 212.5 of the Tariff, as applicable, during the term of this ISA, Interconnection Customer shall ensure that it meets each of the following development milestones:

  • Product Specifications The Company agrees that all Products sold to Xxxx hereunder shall conform to the respective specifications set forth on Schedule A or to such other specifications as are from time to time agreed upon by the Parties.

  • Health plan specification The Employer will require health plans participating in the Group Insurance Program to develop and implement health promotion and health education programs for State employees and their dependents.

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

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • Product Specific Terms these terms apply to specific Products referenced in this section.

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

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