AV Technology - June 2008 - (Page 54)

A M X GUIDE TO SY S T E M IN T E G R AT I O N PR A C T I C E S Letter of Transmittal – this form is used whenever documents, drawings, samples, or submittals are sent. It clearly indicates the addressee sender, contact information, a list of what is sent (including date or revision number), and any action expected to be taken by the receiving party. This form “We used AMX NetLinx Integrated Controllers because of its advanced programming capabilities and how easy it is to integrate with other manufacturer’s protocols. Since the exhibit’s completion, the system has required little servicing. AMX is solid as a rock.” Academy of Natural Sciences of Philadelphia, becomes a change order. Change Orders (CO) - Despite extensive due diligence during the design and bidding processes to ensure an appropriate system design, design and contract changes, requested with a change order (CO), may be needed as the project unfolds. Because of its ability to change the contract scope and pricing, this is arguably the most important form used is used whether the items are sent by mail, courier, overnight carrier, or fax. Request for Interpretation (RFI) - As the project progresses, questions inevitably arise about the project. They generally revolve around three basic types of issues: Design issue Site issue Owner change or request during the construction phase. A few of the many reasons for AV system COs are: Changes or clariﬁcations in anticipated use by end-user personnel. Architectural, millwork, ﬁnish, or other physical changes to the installation site. Design conﬂicts, omissions, or errors. The structure normally set in place for this process is the request for interpretation (RFI). This process is usually based on a paper or electronic form established for the project and that includes the RFI originator, the RFI receiver, and a space to enter the question and the response. Change in product availability or speciﬁcations. Availability of new products or technologies. Discovery of hidden site conditions. Budget adjustments. Schedule changes and delays by others. Some RFIs are simply resolved by a clariﬁcation from the recipient of the RFI without a change in anyone’s contract. Others may need resolution through a change in the construction contract. In the latter case, other structured communications, such as a change order, may be generated. Punch Lists - The punch list is a key element in the project process, because it becomes the ﬁnal checklist for a complete installation and contract closeout. Depending on the contract language and relationships, the punch list may be created by the AV consultant, the ow he owner’s AV project manager or the AV integrator’s project manager, or other internal personnel personnel. Request for Change (RFC) - A request for change (RFC) is submitted (ultimately to be approved by the owner) if the integrator or consultant wants to change contractual obligations, equipment models or speciﬁcations, or system design. When eciﬁc an RFC is generated (or answered) by the integrator, pricing and impact throughout the project must be included. The preliminary punch list may be internal to the integra ist integrator under many design-build projects, but is us y usually required for distribution to various design and owner team members desig under most other methods. The ﬁnal punch list generated he after the ﬁnal commissioning tes and alignment is usually disssioning test tributed to the designated projec team stakeholders under project Issues that can trigger an RFC ar are: Change in intended use of th system. the Discontinued product. Architectural, mechanical, or millwork change changes. Discovery of system or product in ystem incompatibilities or function. During the preliminary checkout, a preliminary punch list that includes all of the discovered system deﬁciencies, along des with the possible resolution of each deﬁciency and the party e responsible for each item, should be developed. This punch onsible list should be distributed to the responsible parties for Any member of the project team can submit the RFC, subm although on an AV project, the integrator o consultant most or commonly creates the document. An approved RFC then ov completion and should include due dates for completion of each item. any method. 10 800.222.0193 +1.469.624.7400 w w w. a m x . c o m © June 2008 AMX. All rights reserved. AMX does not assume responsibility for any errors or omissions. oes http://www.amx.com http://www.amx.com

Table of Contents Feed for the Digital Edition of AV Technology - June 2008

AV Technology - June 2008 Contents Precedent Corporate: Global Standardization Government: Strategic Technology Planning Education: It’s All Just a Click Pre-Empting Projector Breakdown Dealing With Technophobes Keeping Ahead of Technology Obsolescence Understanding Video Codecs Rules of Engagement Network, See & Learn Sound From the Heart Sportsbook Makes an Impact Upgrading an AV Image Product Review: Polycom’s RealPresence Experience HD Tech Horizons: A True AV Networking Standard? Product Spotlight: Digital Media Servers; Flat Panel New Products Ad Index AV MO: Calculating Fiber Optic Transmission Distance

AV Technology - June 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.