Design Objectives Sample Clauses

The Design Objectives clause defines the specific goals, requirements, and standards that the design work must achieve in a project. It typically outlines the intended functionality, aesthetic considerations, performance criteria, and any regulatory or client-specific requirements that the design must satisfy. For example, it may specify energy efficiency targets, accessibility standards, or integration with existing infrastructure. This clause ensures that all parties have a clear understanding of the expectations for the design, helping to prevent misunderstandings and disputes by providing a concrete benchmark against which the completed design can be evaluated.
Design Objectives. The WSLA language is designed to capture service level agreements in a formal way to enable automatic configuration of both the service implementing system of the service providing organization as well as the system that is used to supervise the agreed quality of service. To facilitate automatic configuration the WSLA comprises: A description of the parties , their roles (provider, customer, third parties) and the action interfaces they expose to the other parties of the contract. A detailed specification of the service level parameters (SLA parameters) guarantees are applied to. SLA parameters are specified by metrics. Metrics define how to measure an item, in the case of Resource metrics, or how to aggregate metrics to composite metrics. A metric description also includes which party is in charge of measuring and aggregating and how the metrics can be retrieved. A representation of the parties obligations. Service level objectives contain a formal expres- sion of the guaranteed condition of a service in a given period. Action guarantees represent promises of parties to do something, for example, to send a notification in case the guarantees are not met. The specification of the service level parameters and metrics represents the common understanding of the parties. The implementation of the service within the service provider can be more complex in a way that the view in the WSLA is an abstraction of the real underlying system. The language must be extensible to capture services from particular domains using specific types of service parameters. The WSLA language uses the mechanism of type derivation by XML schema to introduce new types (i.e. syntactical elements with semantics derived from the high- level type) to describe domain specific concepts. The language should be immediately useful to SLA authors. The standard extensions are part of the WSLA specification. While the core syntax is deliberately kept slim, the standard extensions provide a set of type definitions that cover many usual concepts related to a Web Service SLA. In order to protect the confidentiality of the service customer, an SLA must be decomposable into the configuration information that is needed for third parties to perform their role in the SLA supervision without having access to the complete SLA.
View Source
Design Objectives. The design goals of the proposed USAF-IoD are as follows:
View Source
Design Objectives. Under the above threat model, the proposed key agreement protocols are expected to achieve the following objectives: V. LEAKAGE-RESILIENT ID-BASED KEY AGREEMENT This section presents two ID-based key agreement proto-
View Source
Design Objectives. 12.4.1 Contractor shall ensure that the Engineering Services and the Results of Work, achieves, inter alia, the following: 12.4.1.1 operational safety with respect to protection of individuals and property; 12.4.1.2 optimal operability, efficiency and maintenance conditions; and 12.4.1.3 compliance with warranties required by the Agreement.
View Source
Design Objectives. The property is zoned as commercial with an auto dealership being allowed as a conditional use permit. The developer will be held to the highest standards per the City general plan, planning and zoning ordinances, and other applicable building codes and ordinances of the City. As a new auto dealership they will be subject to each manufacturer’s own guidelines and building standards. In most instances these standards are as high if not higher than Lehi City standards. All development will be submitted to the City via the normal development approval process, which includes site plans to include development data and any other appropriate material describing the development, land coverage, setbacks, heights, off-street parking to be provided, and any other information as deemed appropriate by the City. The agency may have the right to approve any and all design and construction plans for any development within the Project Area to ensure any and all development within the Project Area is consistent with the Project Area Plan.
View Source
Design Objectives. 3.1.1 The REGIONAL RADIO SYSTEM design objectives for the performance of portable and mobile voice and the quality of coverage provided shall be determined by the OVERSIGHT COMMITTEE 3.1.1.1 Unless otherwise decided by the OVERSIGHT COMMITTEE it is understood that the REGIONAL RADIO SYSTEM shall be designed, operated, managed, and maintained to achieve 95% street level coverage reliability measured to and from typical portable radios, used in the system, while on the wearer’s belt and within the area depicted in APPENDIX A. Methodology for both prediction and measurement of such performance shall be in accordance with TIA standard TSB88. 3.1.1.2 In the event that the REGIONAL RADIO SYSTEM encounters a sustained degradation of service below the standards set forth in Section 3.1.1.1, the County Chief Information Officer will be responsible for evaluating the issue and proposing a solution(s) to the satisfaction of the OVERSIGHT COMMITTEE. 3.1.2 The REGIONAL RADIO SYSTEM shall be designed to meet the loading requirements of the anticipated busiest hour for all planned users over the life of the system. 3.1.2.1 Unless otherwise decided by the Oversight committee, the system shall be designed, operated, managed, and maintained to achieve a 2% grade of service (GOS) or better during average daily busy hours, without invoking priority access. 3.1.2.2 A 2% grade of service is a standardized method of quantifying the throughput of the REGIONAL RADIO SYSTEM. For every 100 attempts to transmit during the busy hour, no more than 2 attempts are blocked for more than 5 seconds. 3.1.3 A list of all features currently supported by the REGIONAL RADIO SYSTEM will be incorporated into APPENDIX B.
View Source
Design Objectives. Client Goals, Vision & Intentions: Design a single prototype building that communicates the vision of 5 existing schools, merging into the 2 new buildings. Design to be as efficient as possible to maximize the project budgets. Site Goals: Separate bus, car and pedestrian traffic to the greatest extent possible. Image Goals: None specifically stated. Performance Goals: Meet minimum IECC code requirements; some District standards exceed 2009 IECC (which is required) Main Project Challenges: Design of single prototype building for 2 new elementary schools on 2 different sites; merging 5 schools into 2 buildings Third Party Certification (i.e. LEED Platinum): None
View Source
Design Objectives. The AMENCA2 Program Design, Concept Paper and Guidelines document presents a comprehensive approach to the development of the design of the AMENCA Phase 2 Cooperation Agreement, as prescribed in the Terms of Reference (TORs) presented in Attachment 1. The design process builds on the AMENCA Review (April 2007) and has included further consultations with staff in AusAID IMEA Section; Community and Business Partnerships (CBP) Section; staff at the Australian representative Office in Ramallah; and the Australian Council for International Development (ACFID). The objective of the AMENCA Program design process is to assist AusAID to establish the AMENCA 2 NGO Cooperation Agreement by undertaking two main tasks. ▪ Developing AMENCA2 Concept Paper/ Guidelines for NGOs, including a management framework of the AMENCA2 suitable for the request to Australian NGOs to submit a capacity statement for the AMENCA2; and ▪ Provide input into the assessment of the NGO design documents and subsequently prepare a program implementation description, including a synthesis of the NGO design documents (submitted through the above tender process) under the agreed management framework and suitable for AusAID peer review. This document represents the completion of Task 1. The document is structured to reflect a program design approach to the CA and therefore includes the following key sections: o Section 2: Situation Analysis and Rationale o Section 3: AMENCA2 Program Description: Goal, Objectives and Components o Section 4: Program Management: Management Structure and Timeframes, Capacity Statement Process, Design Process, Resources, Program Performance (including proformas for design and reporting) o Section 5: Risk, Sustainability and Feasibility Attachment 2 provides the overall timeline for the AMENCA2 Program from Draft document stage through to AMENCA2 project implementation.
View Source

Related to Design Objectives

  • Goals & Objectives The purpose of this Agreement is to ensure that the proper elements and commitments are in place to provide consistent IT service support and delivery to the Customer by the Service Provider. The goal of this Agreement is to obtain mutual agreement for IT service provision between the Service Provider(s) and Customer(s). The objectives of this Agreement are to: • Provide clear reference to service ownership, accountability, roles and/or responsibilities. • Present a clear, concise and measurable description of service provision to the customer. • Match perceptions of expected service provision with actual service support & delivery.

  • Program Objectives Implement a rigorous constructability program following The University of Texas System, Office of Capital Projects Constructability Manual. Identify and document Project cost and schedule savings (targeted costs are 5% of construction costs). Clarification of Project goals, objectives.

  • Safety Objectives 55.1 The Parties recognise the potentially hazardous nature of the construction industry. To this end, the Parties to the Agreement are committed to continuous improvement in occupational health and safety standards through the implementation of an organisational framework which involves all Parties in protecting Employees’ health and safety. 55.2 In meeting these objectives, the Parties have agreed to consider a broad agenda through the consultative processes established by this Agreement. Such an agenda will include: (a) measures designed to include the safe operation of plant and equipment; (b) training issues including specific hazards, health and safety systems, and site induction; (c) management of occupational health and safety through a comprehensive approach which aims to control hazards at their source, reduce the incidence and costs of occupational injuries and illnesses; and (d) risk of fatigue (see clauses 38.5 and 38.6). 55.3 The Employer will comply with all relevant work health and safety legislation, including the OHS Act, workers compensation legislation, regulations, codes of practice and relevant and appropriate Australian and Industry Standards produced or recognised by WorkSafe Victoria.

  • Project Objectives 1.1 (Type the Project objectives)

  • PERFORMANCE OBJECTIVES 4.1 The Performance Plan (Annexure A) sets out- 4.1.1 the performance objectives and targets that must be met by the Employee; and 4.1.2 the time frames within which those performance objectives and targets must be met. 4.2 The performance objectives and targets reflected in Annexure A are set by the Employer in consultation with the Employee and based on the Integrated Development Plan, Service Delivery and Budget Implementation Plan (SDBIP) and the Budget of the Employer, and shall include key objectives; key performance indicators; target dates and weightings. 4.2.1 The key objectives describe the main tasks that need to be done. 4.2.2 The key performance indicators provide the details of the evidence that must be provided to show that a key objective has been achieved. 4.2.3 The target dates describe the timeframe in which the work must be achieved. 4.2.4 The weightings show the relative importance of the key objectives to each other. 4.3 The Employee’s performance will, in addition, be measured in terms of contributions to the goals and strategies set out in the Employer’s Integrated Development Plan.