Reference Model Sample Clauses

The Reference Model clause establishes a standard or baseline document, specification, or system that parties agree to use as a point of comparison or guidance throughout their agreement. In practice, this clause may specify that all deliverables, processes, or products must conform to the features, quality, or performance outlined in the designated reference model, such as a particular industry standard or previously approved prototype. Its core function is to ensure consistency and clarity by providing an objective benchmark, thereby reducing ambiguity and potential disputes over expectations or requirements.
Reference Model the PoF Framework
View SourceView Similar (3)
Reference Model. The PoF Reference Model has been created from scratch collecting the inputs from all work packages, taking into account the recommendations after the first project review, mainly for what concerns the role of OAIS in the PoF Framework and the need to go beyond such model to support the novel ForgetIT approach to preservation. The model reflects the common knowledge and the new ideas of all partners to represent the For- getIT approach in a coherent framework based on a reference model. The reference model includes a functional model and an information model. The functional model has been described in detail and can be considered almost complete. Further details could be still added in the future, but the three proposed layers cover all aspects of ForgetIT ap- proach to digital preservation. The information model is still under definition and requires
View SourceView Similar (2)
Reference Model. This implementation agreement provides two types of interface-based multilink support for frame relay: the User-to-Network interface (UNI) and the Network-to-Network interface (NNI). A MFR interface consists of one or more bundle links bound together to form a bundle. The bundle operates as a logical interface function that emulates a single physical interface. Each type of bundle is described below. The two types of bundles use identical message formats and protocol procedures.
View SourceView Similar (2)
Reference Model. A reference model is an abstract framework for understanding significant relationships among the entities of some environment. It enables the development of specific reference or concrete architectures using consistent standards or specifications supporting that environment. A reference model consists of a minimal set of unifying concepts, axioms and relationships within a particular problem domain, and is independent of specific standards, technologies, implementations, or other concrete details [4].
View Source
Reference Model. When used between DTEs, as shown in Figure 1, the privacy procedure is transparent to Frame Relay network(s) between the transmitting and receiving DTEs. Note that the functionality specified in this Implementation Agreement has been illustrated as an integrated privacy function, but stand-alone implementations are not prohibited. This section defines the frame formats and procedures common to all facilities.
View Source
Reference Model. This annex describes the flow of information from the network to the user from the perspective of the user device. Refer to Figure 1for an illustration of the message terminology.
View Source
Reference Model. The PoF Reference Model has been created from scratch collecting the inputs from all work packages while taking into account the recommendations after each project review, mainly for what concerns the role of OAIS in the PoF Framework and the need to go beyond such model to support the novel ForgetIT approach to preservation. After the first year only some preliminary ideas and a draft approach were available. During the second year the model foundations were identified and the functional part was specified. During the third year the functional part was improved (although the core ideas of the three layers were not affected) and a new information part was introduced and implemented in the framework, providing a complete and coherent definition of the preservation objects, their interaction and evolution within the PoF Framework. The PoF Framework architecture described in D8.1 is compliant to the model. The PoF Reference Model is available as expected in this indicator and is based on the contributions from all work packages, as described for example in the model foundations.
View Source
Reference Model. Framework for understanding significant relationships among the entities of some environment, and for the development of consistent standards or specifications supporting that environment. A reference model is based on a small number of unifying concepts and may be used as a basis for education and explaining standards to a non- specialist (ISO). Service: Distinct part of the functionality that is provided by an entity through interfaces (ISO 19119).
View Source

Related to Reference Model

  • Calculation Any figure or percentage referred to in this Agreement shall be carried to seven decimal places.

  • Selection Under a Fixed Budget Services for assignments which the Association agrees meet the requirements of paragraph 3.5 of the Consultant Guidelines may be procured under contracts awarded on the basis of a Fixed Budget in accordance with the provisions of paragraphs 3.1 and 3.5 of the Consultant Guidelines.

  • Methodology 1. The price at which the Assuming Institution sells or disposes of Qualified Financial Contracts will be deemed to be the fair market value of such contracts, if such sale or disposition occurs at prevailing market rates within a predefined timetable as agreed upon by the Assuming Institution and the Receiver. 2. In valuing all other Qualified Financial Contracts, the following principles will apply:

  • Pro Forma Calculations (a) Notwithstanding anything to the contrary herein, financial ratios, tests and covenants, including the Leverage Ratio and the Fixed Charge Coverage Ratio shall be calculated in the manner prescribed by this Section 1.9. (b) For purposes of calculating any financial ratio, covenant or test, Specified Transactions (with any incurrence or repayment (excluding voluntary repayments) of any Debt in connection therewith to be subject to Section 1.9(c)) that have been made (i) during the applicable measurement period and (ii) subsequent to such period and prior to or simultaneously with the event for which the calculation of any such ratio is made shall be calculated on a pro forma basis assuming that all such Specified Transactions (and any increase or decrease in EBITDA and the component financial definitions used therein attributable to any Specified Transaction) had occurred on the first day of the applicable measurement period. If, since the beginning of any applicable period any Person that subsequently became a Subsidiary or was merged, amalgamated or consolidated with or into Borrower or any of its Subsidiaries since the beginning of such period shall have made any Specified Transaction that would have required adjustment pursuant to this Section 1.9, then such financial ratio or test shall be calculated to give pro forma effect thereto in accordance with this Section 1.9. (c) In the event that Borrower or any Subsidiary incurs (including by assumption or guarantees) or repays (including by redemption, repayment (other than voluntary repayments), retirement or extinguishment) any Debt included in the calculations of any financial ratio, covenant or test (in each case, other than Debt incurred or repaid under any revolving credit facility), (i) during the applicable period or (ii) subsequent to the end of the applicable period and prior to or simultaneously with the event for which the calculation of any such ratio is made, then such financial ratio or test shall be calculated giving pro forma effect to such incurrence or repayment of Debt, to the extent required, as if the same had occurred on the last day of the applicable period.

  • RDO Schedule/ Working Day Calendar (a) The Employer recognises that hours accrued in accordance with clause 38 create a bank of hours to be drawn upon by the Employee, as a paid RDO. The Employer recognises that Employees are entitled to take off days accrued in accordance with this clause. (b) The agreed indicative RDO/Working Day Calendars for 2024 to 2029 are attached at Appendix D of this Agreement. (c) For the avoidance of doubt, nothing in the arrangement for an indicative RDO / Working Day Calendar is intended to impose a limit on the ability of the Employer to determine with its Employees when and where work can be performed to meet operational requirements or otherwise limit the Employer’s right to manage its business and improve productivity.