Cs3 Controls

[Tamar Navratil]

Eliminationremoves the hazard at the source. This could include changing the work process to stop using a toxic chemical, heavy object, or sharp tool. It is the preferred solution to protect workers because no exposure can occur.

When considering a substitute, it's important to compare the potential new risks of the substitute to the original risks. This review should consider how the substitute will combine with other agents in the workplace. Effective substitutes reduce the potential for harmful effects and do not create new risks.

Elimination and substitution can be the most difficult actions to adopt into an existing process. These methods are best used at the design or development stage of a work process, place, or tool. At the development stage, elimination and substitution may be the simplest and cheapest option. Another good opportunity to use elimination and substitution is when selecting new equipment or procedures. Prevention through Design is an approach to proactively include prevention when designing work equipment, tools, operations, and spaces.

Engineering controls reduce or prevent hazards from coming into contact with workers. Engineering controls can include modifying equipment or the workspace, using protective barriers, ventilation, and more. The NIOSH Engineering Controls Database has examples of published engineering control research findings.

Engineering controls can cost more upfront than administrative controls or PPE. However, long-term operating costs tend to be lower, especially when protecting multiple workers. In addition, engineering controls can save money in other areas of the work process or facility operation.

PPE is equipment worn to minimize exposure to hazards. Examples of PPE include gloves, safety glasses, hearing protection, hard hats, and respirators. When employees use PPE, employers should implement a PPE program. While elements of the PPE program depend on the work process and the identified PPE, the program should include:

Employers should not rely on PPE alone to control hazards when other effective control options are available. PPE can be effective, but only when workers use it correctly and consistently. PPE might seem to be less expensive than other controls, but can be costly over time. This is especially true when used for multiple workers on a daily basis.

Administrative controls and PPE require significant and ongoing effort by workers and their supervisors. They are useful when employers are in the process of implementing other control methods from the hierarchy. Additionally, administrative controls and PPE are often applied to existing processes where hazards are not well controlled.

This publication provides a catalog of security and privacy controls for information systems and organizations to protect organizational operations and assets, individuals, other organizations, and the Nation from a diverse set of threats and risks, including hostile attacks, human errors, natural disasters, structural failures, foreign intelligence entities, and privacy risks. The controls are flexible and customizable and implemented as part of an organization-wide process to manage risk. The controls address diverse requirements derived from mission and business needs, laws, executive orders, directives, regulations, policies, standards, and guidelines. Finally, the consolidated control catalog addresses security and privacy from a functionality perspective (i.e., the strength of functions and mechanisms provided by the controls) and from an assurance perspective (i.e., the measure of confidence in the security or privacy capability provided by the controls). Addressing functionality and assurance helps to ensure that information technology products and the systems that rely on those products are sufficiently trustworthy.

Access Control; Awareness and Training; Audit and Accountability; Assessment, Authorization and Monitoring; Configuration Management; Contingency Planning; Identification and Authentication; Incident Response; Maintenance; Media Protection; Physical and Environmental Protection; Planning; Program Management; Personnel Security; PII Processing and Transparency; Risk Assessment; System and Services Acquisition; System and Communications Protection; System and Information Integrity; Supply Chain Risk Management

The maps displayed through the Maps JavaScript API contain UI elements to allow user interaction with the map. These elements are known as controls and you can include variations of these controls in your application. Alternatively, you can do nothing and let the Maps JavaScript API handle all control behavior.

You don't access or modify these map controls directly. Instead, you modify the map's MapOptions fields which affect the visibility and presentation of controls. You can adjust control presentation upon instantiating your map (with appropriate MapOptions) or modify a map dynamically by calling setOptions() to change the map's options.

You may wish to turn off the API's default UI buttons entirely. To do so, set the map's disableDefaultUI property (within the MapOptions object) to true. This property disables any UI control buttons from the Maps JavaScript API. It does not, however, affect mouse gestures or keyboard shortcuts on the base map, which are controlled by the gestureHandling and keyboardShortcuts properties respectively.The following code disables the UI buttons:

You may wish to tailor your interface by removing, adding, or modifying UI behavior or controls and ensure that future updates don't alter this behavior. If you wish to only add or modify existing behavior, you need to ensure that the control is explicitly added to your application.

Some controls appear on the map by default while others will not appear unless you specifically request them. Adding or removing controls from the map is specified in the following MapOptions object's fields, which you set to true to make them visible or set to false to hide them:

By default, all the controls disappear if the map is smaller than 200x200px. You can override this behavior by explicitly setting the control to be visible. For example, the following table shows whether the zoom control is visible or not, based on the map size and the setting of the zoomControl field:

The following example sets the map to hide the Zoom control and display the Scale control. Note that we do not explicitly disable the default UI, so these modifications are additive to the default UI behavior.

Several controls are configurable, allowing you to alter their behavior or change their appearance. The Map Type control, for example, may appear as a horizontal bar or a dropdown menu.

Note that if you do modify any control options, you should explicitly enable the control as well by setting the appropriate MapOptions value to true. For example, to set a Map Type control to exhibit the DROPDOWN_MENU style, use the following code within the MapOptions object:

Most of the control options contain a position property (of type ControlPosition) which indicates where on the map to place the control. Positioning of these controls is not absolute. Instead, the API will lay out the controls intelligently by flowing them around existing map elements, or other controls, within given constraints (such as the map size).

Note that these positions may coincide with positions of UI elements whose placements you may not modify (such as copyrights and the Google logo). In those cases, the controls will flow according to the logic noted for each position and appear as close as possible to their indicated position.

As well as modifying the style and position of existing API controls, you can create your own controls to handle interaction with the user. Controls are stationary widgets which float on top of a map at absolute positions, as opposed to overlays, which move with the underlying map. More fundamentally, a control is a element which has an absolute position on the map, displays some UI to the user, and handles interaction with either the user or the map, usually through an event handler.

How you draw your control is up to you. Generally, we recommend that you place all of your control presentation within a single element so that you can manipulate your control as one unit. We will use this design pattern in the samples shown below.

For responding to user input, use addEventListener(), which handles supported DOM events. The following code snippet adds a listener for the browser's 'click' event. Note that this event is received from the DOM, not from the map.

Custom controls are positioned on the map by placing them at appropriate positions within the Map object's controls property. This property contains an array of google.maps.ControlPositions. You add a custom control to the map by adding the Node (typically the ) to an appropriate ControlPosition. (For information on these positions, see Control Positioning above.)

3a8082e126