System Modes Sample Clauses

The 'System Modes' clause defines the various operational states or configurations in which a system can function. It typically outlines the conditions or triggers for switching between modes, such as normal operation, maintenance, or emergency shutdown, and may specify the permissions or restrictions associated with each mode. By clearly delineating these modes, the clause ensures that all parties understand how the system should behave under different circumstances, thereby promoting safety, consistency, and effective management of the system.
System Modes. This is a very generic concept and deemed to be relevant for most robotics systems. The present implementation is even largely independent of ROS but assumes some basic runtime component lifecycle only, which can be found in many component frameworks. The system modes concept reduces the complexity in robotics deliberation significantly and allows the developer of the deliberation layer of a robotic system to focus on the overall platform instead of the many individual software components. On the part of Bosch Corporate Research, the exploitation of this technology is fostered by internal trainings and consulting. In 2019, a first transfer to a business unit project has been prepared. A second will follow in 2020. In addition, this technology is exploited in the Integrated Technical Project (ITP) Metacontrol for ROS 2 (MROS) in the second open call of the EU project RobMoSys, cf. Deliverable D7.5.
View SourceView Similar (2)
System Modes. System modes extend the activate state of the ROS 2 lifecycle and allow to specify different configurations of nodes and (sub-)systems: • Modes of nodes consist of parameter values. • Modes of (sub-)system) consist of modes of their parts. For example, a node representing an actuator might provide different modes that specify certain maximum speed or maximum torque values. An actuation sub-system, grouping several actua- tor nodes, might provide modes that activate/deactivate certain contained actuator nodes and/or change their modes based on its own modes. Both, the system hierarchy as well as the system modes are specified in a system modes and hierar- chy model file (SHM file, yaml format) that can be parsed by the mode inference mechanism. The SMH file adheres to the following format: {system}: ros parameters: type: system parts: {node} […] modes: DEFAULT : {node}: {state}[.{MODE}] […] {MODE}: {node}: {state}[.{MODE}] […] […] […] {node}: ros parameters: type: node modes: DEFAULT : ros parameters: {parameter}: {value} […] {MODE}: ros parameters: {parameter}: {value} […] […] […] The system_modes_examples package shows a simple example consisting of modes for one system and two nodes. The model file of the example can be found here.
View Source
System Modes. ‌ The parser for the system modes model and the mode inference mechanisms (including the ex- tended lifecycle) are provided in a repository named system_modes, together with two ROS nodes for mode management and mode monitoring. • Git repository: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/micro-ROS/system_modes Package name: system_modes Package path: ./system_modes Fixed bugs: #9, #11, #13, #14, #24, #25, #26, #42, #44, #45 Demo of system modes concept and implementation in same repository: • Git repository: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/micro-ROS/system_modes Package name: system_modes_examples Package path: ./system_modes_examples The system modes package and the system modes example package were bloomed and released for the ROS 2 distributions Dashing, Eloquent, Foxy, and Rolling: • Git repository: ▇▇▇▇▇://▇▇▇▇▇▇.▇▇▇/micro-ROS/system_modes-release Releases: ROS 2 Dashing (0.4.1-1), ROS 2 Eloquent (0.4.1-1), ROS 2 Foxy (0.4.1-1), ROS 2 Rolling (0.4.1-1)
View Source
System Modes. Essentially, the cruise control system can be in one of the following three modes.
View Source
System Modes. 2.3.1 Power-off: dual-fault-tolerant inhibits While in the power off/restart mode, the satellite shall have [***] inhibits to the following hazards: • [***] [***] • [***] • [***] • [***] 2.3.2 Net power positive while in Safe Mode While in the safe mode, but without GPS lock, the satellite shall be [***] 2.3.3 Remain in Safe Mode The satellite shall remain [***]
View Source

Related to System Modes

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • System Use (a) An electronic site access system may be used on site, subject to the requirements of this statement. (b) The system operates via: (i) a facial recognition device; and (ii) an electronic gate. (c) The system will be installed at the access and egress point/s of the site and will only be utilised to identify presence on site. (d) The purpose for which the electronic site access system will be implemented is to ensure: (i) avoiding unauthorised access to site; (ii) confirmation and co-ordination of effort in emergency situations; and (iii) confirmation that all entrants to site have received a site specific induction; (e) The only personal data collected by the system is a site entrant’s: (i) image; (ii) first & last name; (iii) mobile phone number; (iv) email address; and (v) employer’s name. (the Collected Data) (f) The Collected Data will only be held or used for the purposes specified above, unless otherwise by consent or required by law. (g) The Employer will not use the electronic site access control system to verify who was on a site at a particular time for the purpose of: (i) evaluating whether a variation claim regarding labour costs made by a subcontractor can be substantiated; (ii) taking disciplinary action against an Employee, or assisting a subcontractor to take disciplinary action against its own employees, regarding their start and finish times; or (iii) otherwise generally tracking a worker’s movements whilst on the site.

  • System Upgrades The Connecting Transmission Owner shall procure, construct, install, and own the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement. To the extent that design work is necessary in addition to that already accomplished in the Class Year Interconnection Facilities Study for the Interconnection Customer, the Connecting Transmission Owner shall perform or cause to be performed such work. If all the Parties agree, the Interconnection Customer may construct System Upgrade Facilities and System Deliverability Upgrades. 5.2.1 As described in Section 32.3.5.3 of the SGIP in Attachment Z of the ISO OATT, the responsibility of the Interconnection Customer for the cost of the System Upgrade Facilities and System Deliverability Upgrades described in Attachment 6 of this Agreement shall be determined in accordance with Attachment S of the ISO OATT, as required by Section 32.3.5.3.2

  • System Access CUSTOMER agrees to provide to PROVIDER, at CUSTOMER’S expense, necessary access to the mainframe computer and related information technology systems (the “System”) on which CUSTOMER data is processed during the times (the “Service Hours”) specified in the PSAs, subject to reasonable downtime for utility outages, maintenance, performance difficulties and the like. In the event of a change in the Service Hours, CUSTOMER will provide PROVIDER with at least fifteen (15) calendar days written notice of such change.

  • Contract Database Metadata Elements Title: Sayville Union Free School District and Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU), Local 424 (2011) Employer Name: Sayville Union Free School District Union: Sayville Union Free School Custodial and Maintenance Employees Unit, United Public Service Employees Union (UPSEU) Local: 424 Effective Date: 07/01/2011 Expiration Date: 06/30/2015 PERB ID Number: 6131 Unit Size: 55 Number of Pages: 24 For additional research information and assistance, please visit the Research page of the Catherwood website - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/library/research/ For additional information on the ILR School - ▇▇▇▇://▇▇▇.▇▇▇.▇▇▇▇▇▇▇.▇▇▇/ 55 People TABLE OF CONTENTS ARTICLE Page XXII ANNUAL LEAVE DAYS 14 XXV BREAKS 18 XXVI CIVIL SERVICE LAW ARTICLE SECTION 75 18 XXVIII DURATION 19 XIV EMERGENCY WORK 11 XXI FOUL WEATHER CLOTHING 14 XI GRIEVANCE PROCEDURE 9 XVI HIGHER JOB CLASSIFICATION 12 XVIII HOLIDAYS 13 XV HOLIDAY AND WEEKEND BUILDING CHECKS 12 V INSURANCE 4 X LAYOFF, DISPLACEMENT AND RECALL ORDER 8 VII MANAGEMENT RIGHTS 7 XXVII MISCELLANEOUS 19 XVII NOTICES OF PROMOTIONS 13 XIII OVERTIME 10 II PAYROLL DEDUCTIONS 1 III PERSONNEL FILES 2 XXIV PHYSICAL EXAMINATIONS 18 XXIII RETIREMENT 16 IX STRIKES AND LOCKOUTS 7 XIX VACATIONS 13 XX VISITATION 14 IV WAGES 3 VI WORKERS' COMPENSATION 6 XII WORKWEEK 10 VIII WRITTEN BOARD POLICY 8 APPENDIX A 20 4/20/2016 AGREEMENT made and entered into this day of November 2013 between the SAYVILLE UNION FREE SCHOOL DISTRICT (hereinafter referred to as the “District”) and United Public Service Employees Union, ▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇, ▇▇▇▇▇▇▇▇▇▇, N.Y. 11779 (hereinafter referred to as the “Union”).