We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Design Level Sample Clauses

Design Level. On design level an overview of the overall System Design of the Comfort Range Balancer is given. For some selected subsystem the integration and internal components are also modelled in detail. As a sample below, the detailed view on the integration and internal view of the Range Problem Solver is given. The behaviour of some subsystems will be worked out on design level using ModelicaML and Modelica, in order to be able to perform simulations and verifications on design level. Besides the software systems the HW is modelled in the PrEEvision tooling.
Sample 1Sample 2
Design Level. The design level architecture further details the analysis level design by taking the software and hardware resources into consideration. (See also D6. 1.1 for an overview the related design concept). Functional Design Architecture Figure 2-44 shows the FunctionalDesignArchitecture. This model is focusing on base braking and does not include energy regeneration functionality.
Sample 1
Design Level. Functional Design Architecture A step forward in the design of the case study have been done using the “Functional Design Architecture”, that in this specific case refine the preliminary design of the system adding further details in terms of functional decomposition, flow ports and provides implementation details of functional mapping on HW items through allocations. Hardware Design Architecture The following Hardware Design Architecture shown in Error! Reference source not found. 1.1. For all parts only the connectors relevant for this model are shown. The battery system, delivers the energy which is guided though the High voltage junction box to the power electronic. The power electronic transforms the DC voltage to be provided to the EV motor. The electric vehicle controller is the main controller for many powertrain functions of an electric vehicle. All functions of this model run at this controller. The sensors in this model are needed for the selection of the driving mode.
Sample 1
Design Level. The design level architecture further details the analysis level design by taking the software and hardware resources into consideration. (See also D6. 1.1 for an overview the related design concept). Functional Design Architecture Figure 2-44 shows the FunctionalDesignArchitecture. This model is focusing on base braking and does not include energy regeneration functionality. Figure 2-45 shows the period times of the included functions. Figure 2-46 (close-up) and Figure 2-47 (overall) shows timing constraints for end-to-end response requirements of the brake functionality. Figure 2-47 also show synchronization requirements and a brake-down of the end-to-end timing budget. Hardware Design Architecture Figure 2-48 shows an initial HardwareDesignArchitecture. Allocation Allocation on design level is represented in Figure 2-49, where function prototypes of the FunctionalDesignArchitecture are allocated to nodes in the HardwareDesignArchitecture.
Sample 1
Design Level. Functional Design Architecture The following Functional Design Architecture describes one realization of the features explained in chapter 2.1.1 Both features are implemented on the EVC. Please refer to the comment fields within Figure 2-2 for further details of each function.
Sample 1
Design Level. The design level architecture further details the analysis level design by taking the software and hardware resources into consideration. (See also D6. 1.1 for an overview the related design concept). Currently, the documentation correspond to a single wheel brake by wire model. Work is under way to extend to a full four-wheel model. Functional Design Architecture Figure 19 shows the FunctionalDesignArchitecture. The model is preliminary, as there is only one wheel and the full details of sensors and actuators are not represented.
Sample 1
Design Level. Functional Design Architecture The following Functional Design Architecture describes one realization of the features explained in chapter 2.1.1 Both features are implemented on the EVC. Please refer to the comment fields within Figure 3 for further details of each function. Figure 3: Functional Design Architecture of the EV Demo‌ Hardware Design Architecture The following Hardware Design Architecture shown in Figure 4 describes the hardware realization for the features explained in chapter Error! Reference source not found.. For all parts only the connectors relevant for this model are shown. The battery system, delivers the energy which is guided though the High voltage junction box to the power electronic. The power electronic transforms the DC voltage to be provided to the EV motor. The electric vehicle controller is the main controller for many powertrain functions of an electric vehicle. All functions of this model run at this controller. The sensors in this model are needed for the selection of the driving mode. Figure 4: Hardware Design Architecture of the EV Demo‌
Sample 1

Related to Design Level

  • Service Level In the event that League InfoSight discovers or is notified by you of the existence of Non-Scheduled Downtime, we will use commercially reasonable efforts to determine the source of the problem and attempt to resolve it as quickly as possible.

  • Service Level Expectations Without limiting any other requirements of the Agreement, the Service Provider shall meet or exceed the following standards, policies, and guidelines:

  • Formal Level A. Level I: 1. Within five (5) work days of the oral response, if the grievance is not resolved, it shall be stated in writing on the "Academic Grievance" form as provided by the District (and shown as Exhibit "A" of this Agreement), signed by the grievant (or Federation Representative), and presented to his/her supervisor (or designee) at the xxxx level or above. 2. The supervisor or designee shall communicate his/her decision to the unit member in writing within five (5) days after receiving the grievance. 3. Within the above time limits, either the grievant (or Federation Representative) or the immediate supervisor (or designee) may request a personal conference with the other party. B. Level II: 1. In the event the grievant is not satisfied with the decision at Level I, he/she may appeal the decision on the appropriate form to the college/campus president, or his/her designee, within five (5) days. 2. This statement shall include a copy of the original grievance and a written copy of the decision rendered by the unit member's supervisor or designee. 3. The college/campus president, or his/her designee, shall communicate the decision to the grievant in writing within seven (7) days of receiving the appeal. Either the grievant (or Federation Representative) or the college/campus president (or his/her designee) may request a personal conference within the above time limits. C. Level III 1. If the grievant is not satisfied with the decision at Level II, he/she may within five (5) days appeal the decision on the appropriate form to the Chancellor, or his/her designee. 2. This statement shall include copies of the original grievance and appeal and written copies of the decisions rendered. 3. The Chancellor, or his/her designee, shall communicate his/her decision in writing to the grievant within fifteen (15) days. D. Level IV--Advisory Arbitration 1. Within fifteen (15) work days after receipt of the decision of the Chancellor, the Federation may, upon written notice to the Associate Vice Chancellor, Human Resources, submit the grievance to arbitration under and in accordance with the prevailing rules of the California State Mediation and Conciliation Services. Only the Federation (exclusive representative) may demand arbitration.

  • Power Factor Design Criteria Developer shall design the Large Generating Facility to maintain an effective power delivery at demonstrated maximum net capability at the Point of Interconnection at a power factor within the range established by the Connecting Transmission Owner on a comparable basis, until NYISO has established different requirements that apply to all generators in the New York Control Area on a comparable basis. The Developer shall design and maintain the plant auxiliary systems to operate safely throughout the entire real and reactive power design range. The Connecting Transmission Owner shall not unreasonably restrict or condition the reactive power production or absorption of the Large Generating Facility in accordance with Good Utility Practice.

  • Performance Levels (a) The Performance Levels which apply to the performance by the respective Parties of their obligations under this Agreement are set out in Part 1 of Schedule 5. A failure by either Party to achieve the relevant Performance Level will not constitute a breach of this Agreement and the only consequences of such failure as between the Parties shall be the consequences set out in this Clause 6.6. (b) If the Operator does not comply with the Operator Performance Level then the Operator must pay to Aurizon Network the amount determined in accordance with Schedule 5 as part of the invoice issued by Aurizon Network for charges for the Billing Period immediately following Aurizon Network becoming entitled to that amount. Where there is no next Billing Period, the Operator must pay such amount to Aurizon Network within fourteen (14) days after receipt of a Tax Invoice from Aurizon Network. (c) If Aurizon Network does not comply with the Aurizon Network Performance Level then Aurizon Network will credit to the Operator the amount determined in accordance with Schedule 5 by way of a deduction from the invoice issued by Aurizon Network for Access Charges and other charges for the Billing Period immediately following the Operator becoming entitled to that amount. Where there is no next Billing Period, Aurizon Network must pay such amount to the Operator within fourteen (14) days after receipt of a Tax Invoice from the Operator. (d) The Parties must, if requested by either Party, meet to review the Performance Levels subject to such review not occurring within six (6) Months after the Commitment Date or any previous review of the Performance Levels. If either Party notifies the other that it considers that the Performance Levels are no longer appropriate, the Parties may, but only with the written consent of the relevant End User, agree on varied Performance Levels and any associated variations to the Agreement including [the Base Access Charges and]

  • Design Criteria A/E shall prepare all work in accordance with the latest version of applicable County’s procedures, specifications, manuals, guidelines, standard drawings, and standard specifications. A/E shall prepare each Plans, Specifications, and Estimates (PS&E) package in a form suitable for letting through County’s construction contract bidding and awarding process.

  • Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.

  • Level II In the event the grievance is not resolved in Level I, the decision rendered may be appealed to the Superintendent of Schools, provided such an appeal is made in writing within ten (10) days after receipt of the decision in Level I. If a grievance is properly appealed to the Superintendent, the Superintendent or his/her designee shall meet regarding the grievance within fifteen (15) days after receipt of the appeal. Within ten (10) days after the meeting, the Superintendent or his/her designee shall issue a decision, in writing, to the parties involved.

  • Registry-­‐Level Fees (a) Registry Operator shall pay ICANN a registry-­‐level fee equal to (i) the registry fixed fee of US$6,250 per calendar quarter and (ii) the registry-­‐level transaction fee (collectively, the “Registry-­‐Level Fees”). The registry-­‐level transaction fee will be equal to the number of annual increments of an initial or renewal domain name registration (at one or more levels, and including renewals associated with transfers from one ICANN-­‐accredited registrar to another, each a “Transaction”), during the applicable calendar quarter multiplied by US$0.25; provided, however that the registry-­‐level transaction fee shall not apply until and unless more than 50,000 Transactions have occurred in the TLD during any calendar quarter or any consecutive four calendar quarter period in the aggregate (the “Transaction Threshold”) and shall apply to each Transaction that occurred during each quarter in which the Transaction Threshold has been met, but shall not apply to each quarter in which the Transaction Threshold has not been met. Registry Operator’s obligation to pay the quarterly registry-­‐level fixed fee will begin on the date on which the TLD is delegated in the DNS to Registry Operator. The first quarterly payment of the registry-­‐level fixed fee will be prorated based on the number of calendar days between the delegation date and the end of the calendar quarter in which the delegation date falls. (b) Subject to Section 6.1(a), Registry Operator shall pay the Registry-­‐Level Fees on a quarterly basis to an account designated by ICANN within thirty (30) calendar days following the date of the invoice provided by ICANN.

  • Mileage Measurement Where required, the mileage measurement for LIS rate elements is determined in the same manner as the mileage measurement for V&H methodology as outlined in NECA Tariff No. 4.

Most Referenced Clauses

Most Referenced Definitions