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.
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.
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.
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.
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‌
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.
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-30 shows the FunctionalDesignArchitecture. This model is focusing on base braking and does not include energy regeneration functionality.

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 (1) Level I - within fifteen (15) days after the occurrence of the alleged violation, misinterpretation, or misapplication of a provision of this Agreement, the grievant must present the grievance in writing on the approved form or lose the right to grieve. The form shall contain a clear, concise statement of the grievance, including the provision or provisions of this Agreement alleged to have been violated, misinterpreted, or misapplied; the circumstances involved, the decision rendered at the informal level, and the specific remedy sought. The immediate supervisor shall hold a hearing with the grievant, and shall communicate the decision in writing to the grievant within seven (7) days after receiving the grievance. In the event the immediate supervisor fails to conduct a hearing and render a decision in writing within seven days, the grievant shall notify the Superintendent, who shall convene a hearing with the immediate supervisor and the grievant within seven (7) days after notification, and direct the immediate supervisor to render a decision in writing. Such a directed decision shall be made within three (3) days. (2) Level II - In the event the grievant is not satisfied with the decision at Level I, the grievant may appeal the decision on the approved form to the Superintendent or his/her designee within seven (7) days of the receipt of the Level I decision. The form shall include a copy of the original grievance, the decision at Level I, and a clear and concise statement of the reason for the appeal. The Superintendent or his designee shall hold a hearing with the parties and render a written decision within ten (10) days of the receipt of the appeal. (3) Level III - In the event the grievant is not satisfied with the decision at Level II, the Association may advise the District within seven (7) days of receipt of the Level II decision of its intent to request a mediator from the California State Conciliation Mediation Service.

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

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