Advanced applications and tools provided through the Web platform should follow the general Web standards as far as possible, but may have some special requirements.
Summary
When you develop or give access to an application or a software tool, you should use the ABB Web standards as your standard for colors, graphic design, navigation and interaction, as well as the page structure on the application.
A consistent design helps to brand ABB as one company and strengthen the ABB community feeling across nations and units. A common user interface with consistent navigation, interaction and page structure also makes it easier for users to access the information they are looking for, or to learn how to use a new application.
By introducing these standards we seek to reduce the complexity of ABB's Web application and ensure ease of use. If the existing standards do not cover all the aspects of your particular application, please contact Global Web Management, and they will work out appropriate standards for your case.
As a general rule, all ABB Web applications should be designed according to the Web standards. There are, however, some situations where this might not be feasible. Below is a description of the types of applications that should follow ABB Web standards and what the exceptions are. If your particular application does not fit in to any of these descriptions, please contact Global Web Management for an evaluation of your application. For description of interaction elements to be used in the application, refer to the section about interactions elements.
Applications on the ABB Internet or intranet
An application that is, or will be related to ABB's intranet or one of ABB's external Web sites, should be designed according to ABB's Web standards. The application can be integrated in the frameset's content area of one of the Web sites. This means that the application appears as an integrated part of the whole Web site, using the standard navigation on the Web site.
In this case, it is particularly important that you follow the standards for interaction, typography, colors, etc. for the Web site or section it relates to (e.g. inside.abb.com or Products & Services on www.abb.com). The ABB Image Bank - inside.abb.com/imagebank - is an example of this kind of application.
The application can also be related more indirectly to one of the Web sites. It can be available through a link or through login on one of the Web sites, but displayed in a separate window. However, it will still be associated with the Web site that links to it. Therefore the application should represent the ABB look & feel, and follow the applicable standards (colors, interaction, typography, interaction) for the Web site it relates to. If menus are required, you should use the CAWP menu system.
Applications with a Web-based user interface
Applications with a Web-based user interface should in general follow the standards. This is particularly important if it is available for external users, or a large amount of internal users, to ensure brand building and communicating ABB as one company.
Consistent user interfaces that are based on common guidelines for page structure, interaction, colors, etc., also help the users to understand or learn how to use the various ABB applications. Since the users utilize some of the applications only occasionally, usability and consistency is of significant importance.
Third party applications
Applications that are provided as ready-to-use applications from a third party, and that are either Web-based or related to one of the ABB Web sites, should, if possible, be tailored to suit ABB's Web standards. However, this is only required when it is possible to adapt the application's navigation and interaction elements to ABB's standards.
If this is not possible, the whole application should be implemented without being adjusted to ABB's look & feel. It is not sufficient to add a few visual elements from ABB's visual design. The reason for this is that an application with the ABB design gives the user the expectation that the application works the same way as other ABB applications, which is not the case. This will confuse our users.
Stand-alone or non Web-based tools
Stand-alone applications with no relation to any of the Web sites do not need to follow the standards, unless they have a Web user interface. This also applies to applications that are purely functional or practical working tools, such as a content management system, a timekeeping application or an accounting system. Nevertheless, it is still important to ensure ease of use.
How to evaluate an application
Despite the requirement that all applications should follow ABB's Web guidelines, it is always necessary to estimate the costs and the benefits of implementing the ABB design on an application.
In some cases redesign or adjustments on the interface are technically complex, and imply considerable costs. In such cases it is important to look into the consequences of reduced brand building and inconsistent usability if you don't implement the ABB design. The following aspects should be considered:
- Number of users
- Internal/external users
- Frequency of use (low frequency of use implies that consistency is even more important)
- Consistency of design and interaction elements
- Upgrade issues
Application checklist
- Will the application be Web-based?
- Will the application have a Web user interface?
- Will the application be related to the intranet?
- Will the application be related to other external ABB Web sites?
- Will it be integrated with one of the Web sites?
- How many users will it have?
- Will it be available for external users?
- Will it be available for internal users?
- How often will it be used?
- If the application is provided from a third party, is it possible to tailor it to ABB's standards for design, navigation and interaction?
- If the application is provided from a third party, is it a general tool, or is it available for ABB only?
- Is the application a functional or practical working tool?
- Is the interface integrated with the technical solution, or are they separated?
- Can the interface easily be updated if the software is upgraded?