Component Architecture Safety Folder Sample Clauses

Component Architecture Safety Folder. Under this folder, safety specification of components (DREAMS software Component entities) is given. It is important to note that this model contains only safety relevant software components (i.e., software components which are part of safety functions and have defined safety requirements components that have safety requirements). Non safety software components do not appear here. In the same way that a DREAMS system model can have multiple Component Architecture models, this folder can have multiple roots which correspond to different logical component models (see Figure 3.25). Figure 3.25: Component Architecture Safety Components Folder Figure 3.26: Safety Properties of a Safety Component For each component, the following safety relevant properties (see Figure 3.26) may be defined:  RefComponent: Reference to the Component of the project.  Safety Standard and Safety Integrity Level: SIL level claimed for the Component.  RefCore: if the safety engineer wants to make sure that any deployments involving this component deploys the component into a given core, this field contains a reference to the core. For example: The safety engineer in Wind Turbine demonstrator (WP7) wants to ensure (for whatever reason) that for any Deployment (determined automatically using the design-space exploration (provided by WP4) or even manually defined) the Supervision(D) software Component in Figure 3.26 always is deployed into a Partition that is finally deployed into a given Core of a given Tile. The consistency rules will check that for any deployment the Partition is finally deployed into that core.  RefTile: if the safety engineer wants to make sure that any deployments involving this component deploys the component in a given tile, this field contains a reference to the tile. A similar example as above can be given here. However, in this case, the engineer wants to ensure that Component is deployed into a Partition that is deployed to the given Tile (without specifying a particular Core).  Isolated in One Partition (Boolean): True if the safety engineer wants to make sure (for whatever reason) that any deployments involving this component deploys the component “alone” in one partition (i.e., not shared with any other component). In other words, the Partition will contain only this Component.  NeedAccessListHWResources: List of hardware resources (watchdogs, clocks, tiles, etc.) to which the component need access rights. This is for example needed for a software Com...
Sample 1
AutoNDA by SimpleDocs

Related to Component Architecture Safety Folder

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • Drug and Alcohol Testing – Safety-Sensitive Functions A. Employees required to have a Commercial Driver’s License (CDL) are subject to pre-employment, post-accident, random and reasonable suspicion testing in accordance with the U.S. Department of Transportation rules, Coast Guard Regulations (46 CFR Part 16) or the Federal Omnibus Transportation Employee Testing Act of 1991. The testing will be conducted in accordance with current Employer policy.

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Physical Architecture 59.2.1 CenturyLink's network architecture in any given local exchange area and/or LATA can vary markedly from another local exchange area/LATA. Using one or more of the NIMs herein, the Parties will agree to a physical architecture plan for a specific LATA, or if appropriate based on other requirements in Section 59, Local Calling Area. The physical architecture plan, as described in the Local Interconnection POI Profile, will be discussed during joint implementation planning. CLEC and CenturyLink agree to Interconnect their networks through existing and/or new Interconnection Facilities between CLEC switch(es) and CenturyLink's End Office Switch(es) and/or Tandem Switch(es). The physical architecture plan will be in accordance with Forecasting and Planning requirements in Article IV.

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Drug-Free Workplace Certification As required by Executive Order No. 90-5 dated April 12, 1990, issued by the Governor of Indiana, the Contractor hereby covenants and agrees to make a good faith effort to provide and maintain a drug-free workplace. The Contractor will give written notice to the State within ten (10) days after receiving actual notice that the Contractor, or an employee of the Contractor in the State of Indiana, has been convicted of a criminal drug violation occurring in the workplace. False certification or violation of this certification may result in sanctions including, but not limited to, suspension of contract payments, termination of this Contract and/or debarment of contracting opportunities with the State for up to three (3) years. In addition to the provisions of the above paragraph, if the total amount set forth in this Contract is in excess of $25,000.00, the Contractor certifies and agrees that it will provide a drug-free workplace by:

  • Schematic Design Phase Services § 3.2.1 The Architect shall review the program and other information furnished by the Owner, and shall review laws, codes, and regulations applicable to the Architect’s services.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

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