Design Principles Sample Clauses

Design Principles. The Committee recognizes the complexity and fragmented nature of our nation’s ever-changing health care system. To the extent practical, the Committee will seek to implement each Plan in a manner consistent with the guidelines set out below, subject to both the financial requirements of such Plan and its Purpose.

Design Principles. 10.4.1 The Parties must comply with the following design principles during the Detailed Site Design process: (a) Parties to adhere to any process agreed and documented for the conduct of the negotiations and any further commitments made in relation to the protection of Confidential Information; (b) Parties to consider, and respond to, any proposals made by the other Party promptly; (c) where a Party does not accept a proposal, state the reason or reasons for its non-acceptance; (d) work together to identify barriers to agreement and actively explore ways to overcome those differences; However, the Parties are not required to continue to meet and discuss matters which have been considered and responded to; and (e) not behave in ways which may undermine the good faith nature of the negotiations.

Design Principles. The Districts acknowledge that general administration of the Design Principles is assigned by the Declaration to the Design Review Committee (“DRC”), as such committee is more particularly described in the Declaration and Covenant Enforcement Rules and Regulations. The CAB shall appoint the members of the DRC in accordance with the Declaration and Covenant Enforcement Rules and Regulations.

Design Principles. The remuneration system is designed to: • Reflect the skills, knowledge, behaviours and responsibilities of each position; • Take into account and be responsive to changes in the environment in which the Ministry operates; • Reward performance; • Be fair and equitable; and • Contribute to enhancing the capability of the Ministry.

Design Principles. The Revize Web Application Developers will be responsible for the look, functionality, and performance of the City’s website. Revize will be responsible for the security of the web content and web-based applications they create. Revize must ensure that the code supports secure authentication and authorization and provides access control mechanisms as required. Good design principles will be based on readability, taking into consideration appropriate font type and size for headlines and text area, as well as line height – ensuring all page elements are balanced. ▇▇▇▇▇▇’s designers will also pay meticulous attention to their use of shadows and gradients. Revize designers must take the City’s preferences, official brand colors, and pictures into consideration to create a color scheme consisting of no more than three colors. Revize will use variants and hues to create visual appeal, contrast, eye-catching allure and invoke the overall feeling that the client desires. Revize must effectively use page elements such as call-to-action buttons, social sharing icons, email newsletter sign-up, and promotion areas, and provide an easy to navigate webpage that is informative without being overwhelming. Therefore, it is the designer’s job to guide the City in making appropriate placement choices for needed items.

Design Principles. The ESB acts as a standards-based distributed integration platform, combining various types of messaging paradigms, transformation, routing and web services. The initial intention is to support REST (REpresentational State Transfer) as well as implementation of the Remote Procedure Call (RPC) i.e. Simple Object Access Protocol (SOAP). REST is an architectural style that defines a set of constraints to be used for creating web services commonly used in the development of Web services. Web Services that conform to the REST architectural style, (RESTful web services) allow the requestor to access and manipulate textual representations of web resources by using a uniform and predefined set of stateless operations. This allows a decoupled architecture and lightweight communications between communicating parties. SOAP is a messaging protocol specification allowing different systems to communicate, typically using Hypertext Transfer Protocol (HTTP) and the Extensible Markup Language (XML). Commonly regarded as the protocol of the choice for inter-application and business-to-business communications, many ESBs in the past were based on combination of SOAP/XML for information exchange. Aiming to achieve interoperability both with legacy systems as well as the future services implementation, both technologies shall be supported. Toward this scope, functionalities of legacy applications will be “wrapped” as services if necessary. As already mentioned, the ESB will follow the specification described in IEC 61968. Each flow related to data exchange from/to the ESB with the legacy systems shall be in a CIM compliant data format. In the occasion where the system communicating with the ESB does not support the format, an adapter will be responsible for translating it. Furthermore, “Part 100: Implementation profiles” [7] of the standard’s series, specifies an implementation profile for the application of the other parts of IEC 61968 using common integration technologies, including Java Message Service (JMS) and web services. This standard also provides guidance with respect to the use of Enterprise Service Bus (ESB) technologies. As presented in Figure 5, the integration layer, enables different technologies between receiver and transmitter, as well as provides support for one-to-many information exchanges (publish/subscribe integration patterns) and key functionality such as delivery guarantees. Java Message Service is an API for message-oriented middleware concerning mess...

Design Principles. Advancement The system shall adopt leading & proven techniques to ensure the effectiveness and continuity of investment. · Reliability · The system shall be able to work properly. · The system shall operate 7x24hrs nonstop and reliably. · The upgrade or improvement of software versions shall proceed without affecting business operations and with steady & smooth system transition. · Maintainability · System administrators can configure, monitor, control and diagnose the entire system in a centralized and simple manner, and monitor & control operating conditions, improve working efficiency and remove hazards. · The configuration, control, monitoring and diagnosis of all functional modules of the system can be done by using professional system management tools without need for specialized encoding. · Security · Information security shall be guaranteed. In other words, information can be transmitted and stored securely within the system, and there shall be good data backup and quick restoration schemes. · A rigorous security system shall be adopted to ensure data security in processing and transmission. · The system shall be able to work properly without being attacked or damaged. · Information in the system shall not be subject to unauthorized access, and the authorization of operation personnel shall be defined according to organization structure. Application software modules to be used by operation personnel at different levels of authorization can be freely combined and subject to centralized configuration by system administrators. · When the security system is damaged, the system shall automatically remind the operators of such damage, detect abnormalities and offer correct operating methods. The bidder shall list the alarm methods that the system offers. · Manual resetting or system startup is enabled without causing data loss or damage. · High performance The system shall have the performance required for user access, and offer consistent & predictable response. · Flexible & convenient development and deployment After the construction of data center platform, the system can address business requirement change and data source change flexibly and facilitate the customization, development, deployment and management of functions. · Scalability Open, standard and adaptable architecture is used to meet various new requirements on the system with expanded business volume and additional types of business. Packaged modular design idea is adopted to guarantee str...

Design Principles. There is nothing we do that is worth getting hurt for.

Design Principles. PPR and PBOT will lead and be responsible for preparation of the Design Principles, which will guide the further design and engineering of the North Green Loop (to be constructed by one or more future private developers). The Design Principles will address and include: general design parameters that ensure that the Green Loop looks and functions as a coherent single element across the USPS Property and is consistent with applicable guiding documents; construction guidelines that require uninterrupted public street and park access during North Green Loop construction; and operations and maintenance parameters that describe an ownership construct for the North Green Loop that protects public resources while facilitating successful asset management and site activation, and which may include resources such as revenue from the existing parking garage and/or revenue from parking built in excess of programmatic ratios. PPR and PBOT will ensure they obtain feedback from Prosper Portland so that the Design Principles result in viable development scenarios for the North Green Loop Lots, including feasible integration of the North Green Loop (through elevated plazas and skybridges accessible from adjacent structures) with the improvements private developer(s) will construct on the North Green Loop Lots.‌