Mixed-Criticality Sample Clauses

Mixed-Criticality. The architecture of embedded systems in multiple domains commonly follows a federated architecture paradigm where a system is composed of interconnected subsystems with well-defined functionalities. The ever increasing demand for additional functionalities is a growing trend in several domains such as transportation and industrial control. For example, the control systems of the modern off-shore wind turbines manage up to three thousand inputs / outputs and several hundred functions. The integration of additional functionalities with different criticality also leads to the increase in the number of subsystems, connectors and wires, increasing the overall cost-size- weight factor and reducing the overall reliability of the system. For example, in automotive domain, between 30 - 60 % of electrical failures are attributed to connector problems. A mixed-criticality system is referred as the integration of the HW (HW), operating system, middleware services and application software (SW) with different levels of criticality into the same embedded computing platform [8]. The integrated approach improves scalability and reliability by reducing the amount of systems-wires-connectors, which in turn reduces the overall cost-size- weight factor. However, safety certification according to industrial standards poses many challenges as provide sufficient evidences to demonstrate that the resulting system is safe for its purpose [8, 9].
AutoNDA by SimpleDocs

Related to Mixed-Criticality

  • Non-Grievability No dispute over a claim for any benefits extended by this Health and Welfare Fund shall be subject to the grievance procedure.

  • Revenue Metering The Connecting Transmission Owner’s revenue metering will be located on the generator side of the 115kV breaker at the Xxxxx Solar Collector Substation and will consist of: • three (3) combination current/voltage transformer (“CT/VT”) units (manufacturer and model ABB/Xxxxxxx KXM-550, GE Grid Solutions KOTEF 000.XX, or other equivalent specified by Connecting Transmission Owner); and • one (1) revenue meter. The ratios of the CTs and VTs will be provided by Connecting Transmission Owner upon its review of the Interconnection Customer’s design documents. (Note: Connecting Transmission Owner’s revenue metering CTs and VTs cannot be used to feed the Interconnection Customer’s check meter.) SERVICE AGREEMENT NO. 2556

  • CORRECTIVE MEASURE The contractor shall repair any deficiencies in excess of the performance guideline.

  • Corrective Measures If the Participating Generator fails to meet or maintain the requirements set forth in this Agreement and/or the CAISO Tariff, the CAISO shall be permitted to take any of the measures, contained or referenced in the CAISO Tariff, which the CAISO deems to be necessary to correct the situation.

  • Geometric visibility The visibility of the illuminating surface, including its visibility in areas which do not appear to be illuminated in the direction of observation considered, shall be ensured within a divergent space defined by generating lines based on the perimeter of the illuminating surface and forming an angle of not less than 5° with the axis of reference of the headlamp. The origin of the angles of geometric visibility is the perimeter of the projection of the illuminating surface on a transverse plane tangent to the foremost part of the lens of the headlamp.

  • Aggravating and Mitigating Factors The penalties in this matter were determined in consideration of all relevant circumstances, including statutory factors as described in CARB’s Enforcement Policy. CARB considered whether the violator came into compliance quickly and cooperated with the investigation; the extent of harm to public health, safety and welfare; nature and persistence of the violation, including the magnitude of the excess emissions; compliance history; preventative efforts taken; innovative nature and the magnitude of the effort required to comply, and the accuracy, reproducibility, and repeatability of the available test methods; efforts to attain, or provide for, compliance prior to violation; action taken to mitigate the violation; financial burden to the violator; and voluntary disclosure. The penalties are set at levels sufficient to deter violations, to remove any economic benefit or unfair advantage from noncompliance, to obtain swift compliance, and the potential costs, risks, and uncertainty associated with litigation. Penalties in future cases might be smaller or larger depending on the unique circumstances of the case.

  • Usage Measurement Usage measurement for calls shall begin when answer supervision or equivalent Signaling System 7 (SS7) message is received from the terminating office and shall end at the time of call disconnect by the calling or called subscriber, whichever occurs first.

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

  • For Product Development Projects and Project Demonstrations  Published documents, including date, title, and periodical name.  Estimated or actual energy and cost savings, and estimated statewide energy savings once market potential has been realized. Identify all assumptions used in the estimates.  Greenhouse gas and criteria emissions reductions.  Other non-energy benefits such as reliability, public safety, lower operational cost, environmental improvement, indoor environmental quality, and societal benefits.  Data on potential job creation, market potential, economic development, and increased state revenue as a result of the project.  A discussion of project product downloads from websites, and publications in technical journals.  A comparison of project expectations and performance. Discuss whether the goals and objectives of the Agreement have been met and what improvements are needed, if any.

  • Remedial Measures Upon becoming aware of an alleged security breach, Contractor’s Contract Manager must set up a conference call with the Department’s and the Customer’s Contract Manager. The conference call invitation must contain a brief description of the nature of the event. When possible, a thirty (30)- minute notice will be given to allow Department personnel to be available for the call. If the designated time is not practical for the Customer, an alternate time for the call will be scheduled. Contractor must share all available information on the call. The Contractor must answer all questions based on the information known at that time and answer additional questions as additional information becomes known. The Contractor must provide the Department and Customer with final documentation of the incident including all actions that took place. If the Contractor becomes aware of a security breach or security incident outside of normal business hours, the Contractor must notify the Department’s and the Customer’s Contract Manager and in all events, within one business day.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!