PROGRAMMING AND CONCEPTS Clause Samples

The "Programming and Concepts" clause defines the requirements and expectations regarding the development, structure, and delivery of programming content or conceptual frameworks within an agreement. It typically outlines the standards, formats, and approval processes for any programs, schedules, or conceptual materials to be provided, ensuring that both parties are aligned on the scope and quality of deliverables. This clause serves to clarify responsibilities and prevent misunderstandings about what constitutes acceptable programming or conceptual work, thereby ensuring that the final outputs meet the agreed-upon objectives and standards.
PROGRAMMING AND CONCEPTS. The Programming shall commence with the execution of the Agreement and shall be complete with the Owner’s approval and acceptance of the Programming Documents. The Programming effort shall meet the “Programming” section of the Owner’s “Performance and Document Submission Requirements” document posted under the A/E Services area of the Owner’s web site at ▇▇▇▇://▇▇▇▇▇▇▇▇▇▇▇▇.▇▇.▇▇▇/ unless otherwise modified by the Initial Information document. Should certain disciplines identified in the “Performance and Document Submission Requirements” not apply to the Project, those specific portions of the “Programming” section shall not be applicable under the terms of this Agreement. Disciplines shall be defined as architecture, structural engineering, mechanical engineering, electrical engineering, civil engineering, and commissioning. The Architect/Engineer shall provide [number] set(s) of Programming Documents including Estimate of Construction for review and approval to the Agency point of contact and [number] set(s) to the Owner.
View SourceView Similar (3)
PROGRAMMING AND CONCEPTS. 2.5.1 The Programming shall commence with the execution of the Agreement and shall be complete with the Owner’s approval and acceptance of the Programming Documents. 2.5.2 The Programming effort shall meet the “Programming” section of the Owner’s “Performance and Document Requirements” document posted under the Consultant Section of the Owner’s web site at ▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇.▇▇▇/pdc/ unless otherwise modified by the Initial Information document or MSU supplied information. Should certain disciplines identified in the “Performance and Document Requirements” not apply to the Project, those specific portions of the “Programming” section shall not be applicable under the terms of this Agreement. Disciplines shall be defined as architecture, structural engineering, mechanical engineering, electrical engineering, civil engineering, and commissioning. 2.5.3 The Architect/Engineer shall provide (2) set(s) and electronic .pdf & MSWord files of Programming Documents including Estimate of Construction for review and approval to the Owner.
View SourceView Similar (2)
PROGRAMMING AND CONCEPTS. 1.1.1 The Programming shall commence with the execution of the Agreement and shall be complete with the Owner’s approval and acceptance of the Programming Documents. 1.1.2 The Programming effort shall provide the following: 1.1.2.1 develop and define the needs for the Project based upon the Owner’s preliminary project program, the recommendations of a Library Consultant retained by the selected firm and any other information obtained through the data gathering process, interviews, charettes, surveys and operational parameters; 1.1.2.2 review, develop, and document detailed requirements for the project, covering items such as project goals and objectives, design objectives, limitations, and criteria; gross area and space requirements; spatial relationships; needs and options for flexibility or expandability; identifying the need for special equipment and systems; site requirements; project schedule and budget requirements; 1.1.2.3 space concepts and flow diagrams, functional relationships, access, circulation, and flow patterns within the building and on the site; 1.1.2.4 define and develop programmatic and conceptual level documents consistent with the following:
View Source

Related to PROGRAMMING AND CONCEPTS

  • Programming Processor is not responsible for programming or reprogramming of fuel dispensers.

  • Software Development Software designs, prototypes, and all documentation for the final designs developed under this agreement must be made fully transferable upon direction of NSF. NSF may make the software design, prototype, and documentation for the final design available to competitors for review during any anticipated re-competition of the project.

  • Programming Phase Schematic Design Phase: 2.2.1.3. Design Development Phase:

  • Architecture The Private Improvements shall have architectural features, detailing, and design elements in accordance with the Project Schematic Drawings. All accessory screening walls or fences, if necessary, shall use similar primary material, color, and detailing as on the Private Improvements.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.