addendum no. 1 specifications

ADDENDUM NO. 1

IPERS FY17 Project Des Moines, Iowa

June 21, 2016

ARCHITECT: PROJECT NO: 216026 Design Alliance, Inc. BID DATE: 06.30.2016 ________ This Addendum No. 1 is issued this date, prior to receiving bids, and shall supplement, amend and become part of the contract documents. Bids shall be based on these modifications.

SPECIFICATIONS

Item No. 1 Section 00 0110 Table of Contents Add the following sections: 21 0500 COMMON WORK RESULTS FOR FIRE SUPPRESSION 21 1300 FIRE SUPPRESSION SPRINKLERS 23 0553 IDENTIFICATION FOR HVAC PIPING AND EQUIPMENT 23 0593 TESTING, ADJUSTING, AND BALANCING FOR HVAC 23 0713 DUCT INSULATION 23 0719 HVAC PIPING INSULATION 23 2113 HYDRONIC PIPING 23 2300 REFRIGERANT PIPING 23 3100 HVAC DUCTS AND CASINGS 23 3300 AIR DUCT ACCESSORIES 23 8129 VARIABLE REFRIGERANT VOLUME (VRV) HVAC SYSTEM 27 1005 STURCTURED CABLING FOR VOICE AND DATA – INSIDE-PLANT 28 1600 INTRUSION DETECTION 28 2100 UNIFIED SECURITY SYSTEM Item No. 2 Section 00 2100 Instructions to Bidders Change Part 7-7.4 to read “7401 Register Drive, Des Moines, Iowa 50321” Mechanical: Item No. 3 Add Mechanical specification Division 21. Refer to attachment. Item No. 4 Add Mechanical specification Division 23. Refer to attachment.

Electrical: Item No. 5 Add Electrical specification Division 27. Refer to attachment. Item No. 6 Add Electrical specification Division 28. Refer to attachment.

DRAWINGS Drawing M1.0 Partial First Floor Plan - Mechanical Item No. 6

The condensate from FCU-1 will be rerouted. The condensate line will penetrate through the exterior wall of the existing building into the chase constructed for sprinkler and refrigerant piping. The condensate line will run down the chase, exit the chase exposed, and run south until it has clearance to penetrate back out through the building exterior to discharge outside the building. (see attached M1.0A) Referenced Note #4 is to be deleted and replaced by the following verbiage: “CONDENSATE PIPING TO PENETRATE EXISTING BUILDING FOR ROUTING THROUGH NEW CHASE AND DISCHARGE TO THE EXTERIOR OF THE BUILDING. MAINTAIN CONDENSATE PIPING IN VESTIBULE AS HIGH AS FEASIBLE WHILE MAINTAINING APPROPRIATE SLOPE FOR DRAINAGE. CORRDINATE PENETRATION INTO BUILDING WITH SPRINKLER AND REFRIGERANT LINE PENETRATIONS, TAKING CARE NOT TO OBSTRUCT SPRINKLER HEAD CLEARANCE. EXPOSED CONDENSATE PIPE AT BOTTOM OF CHASE IS TO BE AS CLOSE TO THE GROUND AS FEASIBLE WHILE MAINTAINING APPROPRIATE SLOPE FOR DRAINAGE. KEEP EXPOSED CONDENSATE PIPE RUN AT BOTTOM OF CHASE AS SHORT AS IS FEASIBLE. CONDENSATE LINE SHOULD PENETRATE TO THE BUILDING EXTERIOR AS SOON AS THE ROUTE IS CLEAR OF THE VESTIBULE.

Attachments: 1. Pre-Bid Sign-In sheet 2. Mechanical Specification Divisions 21 & 23 3. Electrical Specification Division 27 4. Electrical Specification Division 28 5. Drawing M1.0A

END OF ADDENDUM #1

21 0500 - 1216026 / IPERS FY17 Project COMMON WORK RESULTS FOR FIRE SUPPRESSION

SECTION 21 0500COMMON WORK RESULTS FOR FIRE SUPPRESSION

PART 1 GENERAL1.01 SECTION INCLUDES

A. Pipe, fittings, sleeves, escutcheons, seals, and connections for sprinkler, standpipe and fire hose, andcombination sprinkler and standpipe systems.

1.02 REFERENCE STANDARDSA. ASME A112.18.1 - Plumbing Supply Fittings; The American Society of Mechanical Engineers; 2012.B. ASME BPVC-IX - Boiler and Pressure Vessel Code, Section IX - Welding, Brazing, and Fusing

Qualifications; The American Society of Mechanical Engineers; 2015.C. ASME B16.1 - Gray Iron Pipe Flanges and Flanged Fittings: Classes 25, 125, and 250; The American

Society of Mechanical Engineers; 2010.D. ASME B16.3 - Malleable Iron Threaded Fittings: Classes 150 and 300; The American Society of Mechanical

Engineers; 2011.E. ASME B16.4 - Gray Iron Threaded Fittings; The American Society of Mechanical Engineers; 2011.F. ASME B16.5 - Pipe Flanges and Flanged Fittings; The American Society of Mechanical Engineers; 2013

(ANSI/ASME B16.5).G. ASME B16.9 - Factory-made Wrought Steel Buttwelding Fittings; The American Society of Mechanical

Engineers; 2012.H. ASME B16.11 - Forged Steel Fittings, Socket-welding and Threaded; The American Society of Mechanical

Engineers; 2011.I. ASME B16.25 - Buttwelding Ends; The American Society of Mechanical Engineers; 2012.J. ASME B36.10M - Welded and Seamless Wrought Steel Pipe; The American Society of Mechanical

Engineers; 2004.K. ASTM A47/A47M - Standard Specification for Ferritic Malleable Iron Castings; 1999 (Reapproved 2014).L. ASTM A53/A53M - Standard Specification for Pipe, Steel, Black and Hot-Dipped, Zinc-Coated, Welded and

Seamless; 2012.M. ASTM A135/A135M - Standard Specification for Electric-Resistance-Welded Steel Pipe; 2009 (Reapproved

2014).N. ASTM A234/A234M - Standard Specification for Piping Fittings of Wrought Carbon Steel and Alloy Steel for

Moderate and High Temperature Service; 2015.O. ASTM A536 - Standard Specification for Ductile Iron Castings; 1984 (Reapproved 2009).P. ASTM A795/A795M - Standard Specification for Black and Hot-Dipped Zinc-Coated (Galvanized) Welded

and Seamless Steel Pipe for Fire Protection Use; 2013.Q. AWWA C606 - Grooved and Shouldered Joints; 2015 (ANSI/AWWA C606).R. FM Approval Guide; current edition.S. ITS (DIR) - Directory of Listed Products; Intertek Testing Services NA, Inc.; current edition.T. NFPA 13 - Standard for the Installation of Sprinkler Systems; National Fire Protection Association; 2016.U. UL (DIR) - Online Certifications Directory; Underwriters Laboratories Inc.; current listings at database.ul.com.

1.03 SUBMITTALSA. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide manufacturers catalogue information. Indicate valve data and ratings.C. Shop Drawings: Indicate pipe materials used, jointing methods, supports, floor and wall penetration seals.

Indicate installation, layout, weights, mounting and support details, and piping connections.D. Project Record Documents: Record actual locations of components and tag numbering.E. Operation and Maintenance Data: Include installation instructions and spare parts lists.

1.04 QUALITY ASSURANCEA. Manufacturer Qualifications: Company specializing in manufacturing the Products specified in this section

with minimum three years documented experience.


B. Installer Qualifications: Company specializing in performing the work of this section with minimum five yearsexperience.

C. Conform to UL, FM, and Warnock Hersey requirements.D. Valves: Bear UL, FM, and Warnock Hersey product listing label or marking. Provide manufacturer's name

and pressure rating marked on valve body.E. Products Requiring Electrical Connection: Listed and classified as suitable for the purpose specified and

indicated.1.05 DELIVERY, STORAGE, AND HANDLING

A. Deliver and store valves in shipping containers, with labeling in place.B. Provide temporary protective coating on cast iron and steel valves.C. Provide temporary end caps and closures on piping and fittings. Maintain in place until installation.

PART 2 PRODUCTS2.01 FIRE PROTECTION SYSTEMS

A. Sprinkler Systems: Conform to NFPA 13.B. Welding Materials and Procedures: Conform to ASME BPVC-IX.

2.02 ABOVE GROUND PIPINGA. Steel Pipe: ASTM A795 Schedule 10, ASME B36.10M Schedule 5, ASTM A53 Schedule 40, ASTM

A135/A135M Schedule 10, ASTM A135/A135M UL listed light wall type, or ASTM A795 Schedule 40, black.1. Steel Fittings: ASME B16.9, wrought steel, buttwelded, ASME B16.25, buttweld ends, ASTM

A234/A234M, wrought carbon steel or alloy steel, ASME B16.5, steel flanges and fittings, or ASMEB16.11, forged steel socket welded and threaded.

2. Cast Iron Fittings: ASME B16.1, flanges and flanged fittings and ASME B16.4, threaded fittings.3. Malleable Iron Fittings: ASME B16.3, threaded fittings and ASTM A47/A47M.4. Mechanical Grooved Couplings: Malleable iron housing clamps to engage and lock, "C" shaped

elastomeric sealing gasket, steel bolts, nuts, and washers; galvanized for galvanized pipe.5. Mechanical Formed Fittings: Carbon steel housing with integral pipe stop and O-ring pocked and

O-ring, uniformly compressed into permanent mechanical engagement onto pipe.2.03 ESCUTCHEONS

A. Manufacturers:1. Fire Protection Products, Inc: www.fppi.com.com.2. Tyco Fire Protection Products: www.tyco-fire.com.3. Viking Group Inc: www.vikinggroupinc.com.4. Engineer approved equivalent.5. Substitutions: See Section 01 6000 - Product Requirements.

B. Material:1. Fabricate from nonferrous metal.2. Chrome-plated.3. Metals and Finish: Comply with ASME A112.18.

C. Construction:1. One-piece for mounting on chrome-plated tubing or pipe and one-piece or split-pattern type elsewhere.2. Internal spring tension devices or setscrews to maintain a fixed position against a surface.

2.04 PIPE HANGERS AND SUPPORTSA. Hangers for Pipe Sizes 1/2 to 1-1/2 inch: Malleable iron, adjustable swivel, split ring.B. Hangers for Pipe Sizes 2 inches and Over: Carbon steel, adjustable, clevis.C. Multiple or Trapeze Hangers: Steel channels with welded spacers and hanger rods.D. Wall Support for Pipe Sizes to 3 inches: Cast iron hook.E. Wall Support for Pipe Sizes 4 inches and Over: Welded steel bracket and wrought steel clamp.F. Vertical Support: Steel riser clamp.G. Floor Support: Cast iron adjustable pipe saddle, lock nut, nipple, floor flange, and concrete pier or steel

support.


2.05 MECHANICAL COUPLINGSA. Manufacturers:

1. Victaulic Company; FireLock Style 009H: www.victaulic.com.2. Engineer approved equivalent.3. Substitutions: See Section 01 6000 - Product Requirements.

B. Rigid Mechanical Couplings for Grooved Joints:1. Dimensions and Testing: Comply with AWWA C606.2. Minimum Working Pressure: 300 psig.3. Housing Material: Fabricate of ductile iron conforming to ASTM A536.4. Housing Coating: Factory applied orange enamel.5. Gasket Material: EPDM suitable for operating temperature range from minus 30 degrees F to 230

degrees F.6. Bolts and Nuts: Hot dipped galvanized or zinc electroplated steel7. Product:

PART 3 EXECUTION3.01 PREPARATION

A. Ream pipe and tube ends. Remove burrs. Bevel plain end ferrous pipe.B. Remove scale and foreign material, from inside and outside, before assembly.C. Prepare piping connections to equipment with flanges or unions.

3.02 INSTALLATIONA. Install sprinkler system and service main piping, hangers, and supports in accordance with NFPA 13.B. Route piping in orderly manner, plumb and parallel to building structure. Maintain gradient.C. Install piping to conserve building space, to not interfere with use of space and other work.D. Group piping whenever practical at common elevations.E. Sleeve pipes passing through partitions, walls, and floors.F. Install piping to allow for expansion and contraction without stressing pipe, joints, or connected equipment.G. Pipe Hangers and Supports:

1. Install hangers to provide minimum 1/2 inch space between finished covering and adjacent work.2. Place hangers within 12 inches of each horizontal elbow.3. Use hangers with 1-1/2 inch minimum vertical adjustment. Design hangers for pipe movement without

disengagement of supported pipe.4. Support vertical piping at every other floor. Support riser piping independently of connected horizontal

piping.5. Where several pipes can be installed in parallel and at same elevation, provide multiple or trapeze

hangers.6. Prime coat exposed steel hangers and supports. Hangers and supports located in crawl spaces, pipe

shafts, and suspended ceiling spaces are not considered exposed.H. Slope piping and arrange systems to drain at low points. Use eccentric reducers to maintain top of pipe

level.I. Prepare pipe, fittings, supports, and accessories for finish painting. Where pipe support members are

welded to structural building framing, scrape, brush clean, and apply one coat of zinc rich primer to welding.J. Do not penetrate building structural members unless indicated.K. Provide sleeves when penetrating footings, floors, walls, and partitions and seal pipe and sleeve penetrations

to achieve fire resistance equivalent to fire separation required.L. Escutcheons:

1. Install and firmly attach escutcheons at piping penetrations into finished spaces.2. Provide escutcheons on both sides of partitions separating finished areas through which piping passes.3. Use chrome plated escutcheons in occupied spaces and to conceal openings in construction.

M. When installing more than one piping system material, ensure system components are compatible andjoined to ensure the integrity of the system. Provide necessary joining fittings. Ensure flanges, union, andcouplings for servicing are consistently provided.

N. Install valves with stems upright or horizontal, not inverted. Remove protective coatings prior to installation.


O. Provide gate valves for shut-off or isolating service.P. Provide drain valves at main shut-off valves, low points of piping and apparatus.

END OF SECTION

21 1300 - 1216026 / IPERS FY17 Project FIRE SUPPRESSION SPRINKLERS

SECTION 21 1300FIRE SUPPRESSION SPRINKLERS


A. Wet-pipe sprinkler system.B. System design, installation, and certification.

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 07 8400 - Firestopping.D. Section 28 3100 - Fire Detection and Alarm.E. Section 21 0500 - COMMON WORK RESULTS FOR FIRE SUPPRESSION: Pipe, fittings, and valves.

1.03 REFERENCE STANDARDSA. FM (AG) - FM Approval Guide; Factory Mutual Research Corporation; current edition.B. NFPA 13 - Standard for the Installation of Sprinkler Systems; National Fire Protection Association; 2016.C. UL (DIR) - Online Certifications Directory; Underwriters Laboratories Inc.; current listings at database.ul.com.

1.04 ADMINISTRATIVE REQUIREMENTSA. Preinstallation Meeting: Convene one week before starting work of this section.

1.05 SUBMITTALSA. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide data on sprinklers, valves, and specialties, including manufacturers catalog

information. Submit performance ratings, rough-in details, weights, support requirements, and pipingconnections.

C. Shop Drawings:1. Indicate hydraulic calculations, detailed pipe layout, hangers and supports, sprinklers, components and

accessories. Indicate system controls.2. Submit shop drawings to Authority Having Jurisdiction for approval. Submit proof of approval to

Engineer.D. Project Record Documents: Record actual locations of sprinklers and deviations of piping from drawings.

Indicate drain and test locations.E. Operation and Maintenance Data: Include components of system, servicing requirements, record drawings,

inspection data, replacement part numbers and availability, and location and numbers of service depot.F. Maintenance Materials: Furnish the following for Owner's use in maintenance of project.

1. See Section 01 6000 - Product Requirements, for additional provisions.2. Extra Sprinklers: Type and size matching those installed, in quantity required by referenced NFPA

design and installation standard.3. Sprinkler Wrenches: For each sprinkler type.

1.06 QUALITY ASSURANCEA. Maintain one copy of referenced design and installation standard on site.B. Conform to UL (DIR) requirements.C. Designer Qualifications: Design system under direct supervision of a Professional Engineer experienced in

design of this type of work and licensed in Iowa.D. Manufacturer Qualifications: Company specializing in manufacturing the Products specified in this section

with minimum three years documented experience.E. Installer Qualifications: Company specializing in performing the work of this section with minimum five years

experience approved by manufacturer.F. Equipment and Components: Provide products that bear UL (DIR) label or marking.G. Products Requiring Electrical Connection: Listed and classified by UL (DIR) as suitable for the purpose

specified and indicated.

21 1300 - 2216026 / IPERS FY17 Project FIRE SUPPRESSION SPRINKLERS

1.07 DELIVERY, STORAGE, AND HANDLINGA. Store products in shipping containers and maintain in place until installation. Provide temporary inlet and

outlet caps. Maintain caps in place until installation.1.08 EXTRA MATERIALS

A. See Section 01 6000 - Product Requirements, for additional provisions.B. Provide extra sprinklers of type and size matching those installed, in quantity required by referenced NFPA

design and installation standard.C. Provide suitable wrenches for each sprinkler type.D. Provide metal storage cabinet located adjacent to alarm valve.

PART 2 PRODUCTS2.01 MANUFACTURERS

A. Sprinklers, Valves, and Equipment:1. Tyco Fire Protection Products, a Tyco Business: www.tyco-fire.com.2. Viking Corporation: www.vikinggroupinc.com.3. Engineer approved equivalent4. Substitutions: See Section 01 6000 - Product Requirements.

2.02 SPRINKLER SYSTEMA. Sprinkler System: Provide coverage for areas affected by the renovation of the existing building.B. Occupancy: Light hazard; comply with NFPA 13.C. Storage Cabinet for Spare Sprinklers and Tools: Steel, located adjacent to alarm valve.

2.03 SPRINKLERSA. Sidewall Type: Semi-recessed horizontal sidewall type with matching push on escutcheon plate.

1. Response Type: Standard.2. Coverage Type: Standard.3. Finish: Enamel, color as selected.4. Escutcheon Plate Finish: Enamel, color as selected.5. Fusible Link: Glass bulb type temperature rated for specific area hazard.

PART 3 EXECUTION3.01 INSTALLATION

A. Install in accordance with referenced NFPA design and installation standard.B. Install equipment in accordance with manufacturer's instructions.C. Place pipe runs to minimize obstruction to other work.D. Place piping in concealed spaces above finished ceilings.E. Center sprinklers in two directions in ceiling tile and provide piping offsets as required.F. Apply masking tape or paper cover to ensure concealed sprinklers, cover plates, and sprinkler escutcheons

do not receive field paint finish. Remove after painting. Replace painted sprinklers.G. Flush entire piping system of foreign matter.H. Hydrostatically test entire system.I. Require test be witnessed by Fire Marshal.

3.02 INTERFACE WITH OTHER PRODUCTSA. Ensure required devices are installed and connected as required to fire alarm system.

3.03 SCHEDULESA. System Hazard Areas:

1. Vestibule: Light Hazard. (New Additions)END OF SECTION

23 0501 - 1216026 / IPERS FY17 Project MINOR HVAC DEMOLITION

SECTION 23 0501MINOR HVAC DEMOLITION


A. Mechanical demolition.1.02 RELATED SECTIONS

A. Division 00 - Introductory Information, Bidding, and Contracting RequirementsB. Division 01 - General Requirements

PART 2 PRODUCTS2.01 MATERIALS AND EQUIPMENT

A. Materials and equipment for patching and extending work: As specified in individual sections.PART 3 EXECUTION3.01 EXAMINATION

A. Verify field measurements, piping arrangements and ducting arrangements are as shown on Drawings.B. Verify that abandoned piping, ductwork and equipment serve only abandoned facilities.C. Demolition drawings are based on casual field observation and existing record documents.D. Report discrepancies to Architect/Engineer before disturbing existing installation.E. Beginning of demolition means installer accepts existing conditions.

3.02 PREPARATIONA. Disconnect mechanical systems in walls, floors, and ceilings to be removed.B. Coordinate utility service outages with utility company.C. Existing Mechanical Systems: Maintain existing systems in service until new system is complete and ready

for service. Disable system only to make switchovers and connections. Minimize outage duration.1. Obtain permission from Owner at least 24 hours before partially or completely disabling system.2. Make temporary connections to maintain service in areas adjacent to work area.

3.03 DEMOLITION AND EXTENSION OF EXISTING MECHANICAL WORKA. Remove, relocate, and extend existing installations to accommodate new construction.B. Remove abandoned piping and ductwork to source of supply.C. Remove exposed abandoned piping, including abandoned piping above accessible ceiling finishes. Cut

piping flush with walls and floors and cap, and patch surfaces.D. Disconnect abandoned ductwork and air outlets. Remove abandoned outlets if ductwork servicing them is

abandoned and removed. Patch and seal air tight all duct mains that remain.E. Disconnect and remove abandoned mechanical and plumbing equipment as indicated on the drawings.F. Disconnect and remove mechanical devices and equipment serving utilization equipment that has been

removed.G. Repair adjacent construction and finishes damaged during demolition and extension work.H. Maintain access to existing mechanical installations which remain active. Modify installation or provide

access panel as appropriate.I. Extend existing installations using materials and methods compatible with the existing mechanical

installations, or as specified.3.04 CLEANING AND REPAIR

A. Clean and repair existing materials and equipment which remain or are to be reused.END OF SECTION

23 0553 - 1216026 / IPERS FY17 Project IDENTIFICATION FOR HVAC PIPING AND EQUIPMENT

SECTION 23 0553IDENTIFICATION FOR HVAC PIPING AND EQUIPMENT


A. Nameplates.B. Pipe markers.

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General Requirements

1.03 REFERENCE STANDARDSA. ASME A13.1 - Scheme for the Identification of Piping Systems; The American Society of Mechanical

Engineers; 2007 (ANSI/ASME A13.1).1.04 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements for submittal procedures.B. List: Submit list of wording, symbols, letter size, and color coding for mechanical identification.C. Chart and Schedule: Submit valve chart and schedule, including valve tag number, location, function, and

valve manufacturer's name and model number.D. Product Data: Provide manufacturers catalog literature for each product required.E. Manufacturer's Installation Instructions: Indicate special procedures, and installation.F. Project Record Documents: Record actual locations of tagged valves.


A. Brady Corporation: www.bradycorp.com.B. Champion America, Inc: www.Champion-America.com.C. Seton Identification Products: www.seton.com/aec.D. Brimar Industries: www.brimar.comE. Engineer approved equivalent.F. Substitutions: See Section 01 6000 - Product Requirements.

2.02 NAMEPLATESA. Description: Laminated three-layer plastic with engraved letters.

1. Letter Color: White.2. Letter Height: 1/4 inch.3. Background Color: Black.

2.03 PIPE MARKERSA. Color: Conform to ASME A13.1.B. Plastic Tape Pipe Markers: Flexible, vinyl film tape with pressure sensitive adhesive backing and printed

markings.C. Underground Plastic Pipe Markers: Bright colored continuously printed plastic ribbon tape, minimum 6

inches wide by 4 mil thick, manufactured for direct burial service.D. Color code as follows:

1. Heating, Cooling, and Boiler Feedwater: Green with white letters.2. Toxic and Corrosive Fluids: Orange with black letters.3. Compressed Air: Blue with white letters.


A. Degrease and clean surfaces to receive adhesive for identification materials.

23 0553 - 2216026 / IPERS FY17 Project IDENTIFICATION FOR HVAC PIPING AND EQUIPMENT

3.02 INSTALLATIONA. Install nameplates with corrosive-resistant mechanical fasteners, or adhesive. Apply with sufficient adhesive

to ensure permanent adhesion and seal with clear lacquer.B. Install plastic pipe markers in accordance with manufacturer's instructions.C. Identify furnaces, condensing units, air handling units, pumps, heat transfer equipment, tanks, and water

treatment devices with plastic nameplates. Small devices, such as in-line pumps, may be identified withtags.

D. Identify control panels and major control components outside panels with plastic nameplates.E. Identify thermostats relating to terminal boxes or valves with nameplates.F. Tag automatic controls, instruments, and relays. Key to control schematic.G. Identify piping, concealed or exposed, with plastic pipe markers. Use tags on piping 3/4 inch diameter and

smaller. Identify service, flow direction, and pressure. Install in clear view and align with axis of piping. Locate identification not to exceed 20 feet on straight runs including risers and drops, adjacent to each valveand Tee, at each side of penetration of structure or enclosure, and at each obstruction.

END OF SECTION

23 0593 - 1216026 / IPERS FY17 Project TESTING, ADJUSTING, AND BALANCING FOR HVAC

SECTION 23 0593TESTING, ADJUSTING, AND BALANCING FOR HVAC


A. Testing, adjustment, and balancing of air systems.B. Testing, adjustment, and balancing of refrigerating systems.C. Measurement of final operating condition of HVAC systems.

1.02 RELATED REQUIREMENTSA. Division 0 - Introductory Information, Bidding, and Contracting RequirementsB. Division 1 - General RequirementsC. Section 23 0800 - Commissioning of HVAC.

1.03 REFERENCE STANDARDSA. AABC MN-1 - AABC National Standards for Total System Balance; Associated Air Balance Council; 2002.B. ASHRAE Std 111 - Measurement, Testing, Adjusting, and Balancing of Building HVAC Systems; American

Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc.; 2008.C. NEBB (TAB) - Procedural Standard for Testing Adjusting and Balancing of Environmental Systems; National

Environmental Balancing Bureau; 2005, Seventh Edition.D. SMACNA (TAB) - HVAC Systems Testing, Adjusting, and Balancing; Sheet Metal and Air Conditioning

Contractors' National Association; 2002.1.04 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Installer Qualifications: Submit name of adjusting and balancing agency and TAB supervisor for approval

within 30 days after award of Contract.C. Control System Coordination Reports: Communicate in writing to the controls installer all setpoint and

parameter changes made or problems and discrepancies identified during TAB that affect, or could affect,the control system setup and operation.

D. Progress Reports.E. Final Report: Indicate deficiencies in systems that would prevent proper testing, adjusting, and balancing of

systems and equipment to achieve specified performance.1. Submit to the the Commissioning Authority within two weeks after completion of testing, adjusting, and

balancing.2. Revise TAB plan to reflect actual procedures and submit as part of final report.3. Submit draft copies of report for review prior to final acceptance of Project. Provide final copies for

Engineer and for inclusion in operating and maintenance manuals.4. Provide reports in soft cover, letter size, 3-ring binder manuals, complete with index page and indexing

tabs, with cover identification at front and side. Include set of reduced drawings with air outlets andequipment identified to correspond with data sheets, and indicating thermostat locations.

5. Include actual instrument list, with manufacturer name, serial number, and date of calibration.6. Form of Test Reports: Where the TAB standard being followed recommends a report format use that;

otherwise, follow ASHRAE Std 111.7. Units of Measure: Report data in I-P (inch-pound) units only.8. Include the following on the title page of each report:

a. Name of Testing, Adjusting, and Balancing Agency.b. Address of Testing, Adjusting, and Balancing Agency.c. Telephone number of Testing, Adjusting, and Balancing Agency.d. Project name.e. Project location.f. Project Architect.g. Project Engineer.h. Project Contractor.i. Report date.

F. Project Record Documents: Record actual locations of balancing valves and rough setting.


PART 2 PRODUCTS - NOT USEDPART 3 EXECUTION3.01 GENERAL REQUIREMENTS

A. Perform total system balance in accordance with one of the following:1. AABC MN-1, AABC National Standards for Total System Balance.2. NEBB Procedural Standards for Testing Adjusting Balancing of Environmental Systems.3. SMACNA (TAB).

B. Begin work after completion of systems to be tested, adjusted, or balanced and complete work prior toSubstantial Completion of the project.

C. Where HVAC systems and/or components interface with life safety systems, including fire and smokedetection, alarm, and control, coordinate scheduling and testing and inspection procedures with theauthorities having jurisdiction.

D. TAB Agency Qualifications:1. Company specializing in the testing, adjusting, and balancing of systems specified in this section.2. Having minimum of three years documented experience.3. Certified by one of the following:

a. AABC, Associated Air Balance Council: www.aabchq.com; upon completion submit AABCNational Performance Guaranty.

b. NEBB, National Environmental Balancing Bureau: www.nebb.org.c. TABB, The Testing, Adjusting, and Balancing Bureau of National Energy Management Institute:

www.tabbcertified.org.E. TAB Supervisor and Technician Qualifications: Certified by same organization as TAB agency.F. Pre-Qualified TAB Agencies:

1. Systems Management & Balancing, Inc., Urbandale, Iowa.2. Precision Test & Balance, Clive, Iowa.3. Integrity Test & Balance, Madrid, Iowa.4. SystemWorks, West Des Moines, Iowa.5. Engineer approved TAB Agency.6. Substitutions: See Section 01 6000 - Product Requirements.

3.02 EXAMINATION A. Verify that systems are complete and operable before commencing work. Ensure the following conditions:

1. Systems are started and operating in a safe and normal condition.2. Temperature control systems are installed complete and operable.3. Proper thermal overload protection is in place for electrical equipment.4. Final filters are clean and in place. If required, install temporary media in addition to final filters.5. Duct systems are clean of debris.6. Fans are rotating correctly.7. Fire and volume dampers are in place and open.8. Air coil fins are cleaned and combed.9. Access doors are closed and duct end caps are in place.10. Air outlets are installed and connected.11. Duct system leakage is minimized.

B. Submit field reports. Report defects and deficiencies that will or could prevent proper system balance.C. Beginning of work means acceptance of existing conditions.

3.03 PREPARATION A. Hold a pre-balancing meeting at least one week prior to starting TAB work.

1. Require attendance by all installers whose work will be tested, adjusted, or balanced.B. Provide instruments required for testing, adjusting, and balancing operations. Make instruments available to

Engineer to facilitate spot checks during testing.C. Provide additional balancing devices as required.

3.04 ADJUSTMENT TOLERANCESA. Air Handling Systems: Adjust to within plus or minus 5 percent of design for supply systems and plus or

minus 10 percent of design for return and exhaust systems.


B. Air Outlets and Inlets: Adjust total to within plus 10 percent and minus 5 percent of design to space. Adjustoutlets and inlets in space to within plus or minus 10 percent of design.

3.05 RECORDING AND ADJUSTING A. Field Logs: Maintain written logs including:

1. Running log of events and issues.2. Discrepancies, deficient or uncompleted work by others.3. Contract interpretation requests.4. Lists of completed tests.

B. Ensure recorded data represents actual measured or observed conditions.C. Permanently mark settings of valves, dampers, and other adjustment devices allowing settings to be

restored. Set and lock memory stops.D. Mark on the drawings the locations where traverse and other critical measurements were taken and cross

reference the location in the final report.E. After adjustment, take measurements to verify balance has not been disrupted or that such disruption has

been rectified.F. Leave systems in proper working order, replacing belt guards, closing access doors, closing doors to

electrical switch boxes, and restoring thermostats to specified settings.G. At final inspection, recheck random selections of data recorded in report. Recheck points or areas as

selected and witnessed by the Owner.H. Check and adjust systems approximately six months after final acceptance and submit report.

3.06 AIR SYSTEM PROCEDUREA. Adjust air handling and distribution systems to provide required or design supply, return, and exhaust air

quantities at site altitude.B. Make air quantity measurements in ducts by Pitot tube traverse of entire cross sectional area of duct.C. Measure air quantities at air inlets and outlets.D. Adjust distribution system to obtain uniform space temperatures free from objectionable drafts and noise.E. Use volume control devices to regulate air quantities only to extend that adjustments do not create

objectionable air motion or sound levels. Effect volume control by duct internal devices such as dampersand splitters.

F. Vary total system air quantities by adjustment of fan speeds. Provide drive changes required. Vary branchair quantities by damper regulation.

G. Provide system schematic with required and actual air quantities recorded at each outlet or inlet.H. Measure static air pressure conditions on air supply units, including filter and coil pressure drops, and total

pressure across the fan. Make allowances for 50 percent loading of filters.I. Adjust outside air automatic dampers, outside air, return air, and exhaust dampers for design conditions.J. Measure temperature conditions across outside air, return air, and exhaust dampers to check leakage.K. Where modulating dampers are provided, take measurements and balance at extreme conditions. Balance

variable volume systems at maximum air flow rate, full cooling, and at minimum air flow rate, full heating.L. Measure building static pressure and adjust supply, return, and exhaust air systems to provide required

relationship between each to maintain approximately 0.05 inches positive static pressure near the buildingentries.

3.07 SCOPEA. Test, adjust, and balance the following:

1. VRF Fan Coil Unit2. Air Inlets and Outlets

3.08 MINIMUM DATA TO BE REPORTEDA. Electric Motors:

1. Manufacturer 2. Model/Frame 3. HP/BHP 4. Phase, voltage, amperage; nameplate, actual, no load


5. RPM 6. Service factor7. Starter size, rating, heater elements8. Sheave Make/Size/Bore

B. Cooling Coils:1. Identification/number 2. Location 3. Service 4. Manufacturer 5. Air flow, design and actual6. Entering air DB temperature, design and actual7. Leaving air DB temperature, design and actual8. Saturated suction temperature, design and actual9. Air pressure drop, design and actual

C. Heating Coils:1. Identification/number 2. Location 3. Service 4. Manufacturer 5. Air flow, design and actual6. Entering air temperature, design and actual7. Leaving air temperature, design and actual8. Air pressure drop, design and actual

D. Air Distribution Tests:1. Air terminal number2. Room number/location3. Terminal type4. Terminal size5. Area factor6. Design velocity7. Design air flow8. Test (final) velocity9. Test (final) air flow10. Percent of design air flow

END OF SECTION

23 0713 - 1216026 / IPERS FY17 Project DUCT INSULATION

SECTION 23 0713DUCT INSULATION


A. Duct insulation.1.02 RELATED REQUIREMENTS

A. Division 0 - Introductory Information, Bidding, and Contracting RequirementsB. Division 1 - General RequirementsC. Section 22 0553 - Identification for Plumbing Piping and Equipment.D. Section 23 3100 - HVAC Ducts and Casings

1.03 REFERENCE STANDARDSA. ASTM B209 - Standard Specification for Aluminum and Aluminum-Alloy Sheet and Plate; 2014.B. ASTM B209M - Standard Specification for Aluminum and Aluminum-Alloy Sheet and Plate [Metric]; 2014.C. ASTM C518 - Standard Test Method for Steady-State Thermal Transmission Properties by Means of the

Heat Flow Meter Apparatus; 2010.D. ASTM C553 - Standard Specification for Mineral Fiber Blanket Thermal Insulation for Commercial and

Industrial Applications; 2013.E. ASTM E84 - Standard Test Method for Surface Burning Characteristics of Building Materials; 2015a.F. ASTM E96/E96M - Standard Test Methods for Water Vapor Transmission of Materials; 2014.G. NFPA 255 - Standard Method of Test of Surface Burning Characteristics of Building Materials; National Fire

Protection Association; 2006.H. SMACNA (DCS) - HVAC Duct Construction Standards Metal and Flexible; 2005 (Rev. 2009).I. UL 723 - Standard for Test for Surface Burning Characteristics of Building Materials; Underwriters

Laboratories Inc.; Current Edition, Including All Revisions.1.04 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide product description, thermal characteristics, list of materials and thickness for each

service, and locations.C. Manufacturer's Instructions: Indicate installation procedures necessary to ensure acceptable workmanship

and that installation standards will be achieved.1.05 QUALITY ASSURANCE

A. Manufacturer Qualifications: Company specializing in manufacturing products of the type specified in thissection with not less than three years of documented experience.

B. Applicator Qualifications: Company specializing in performing the type of work specified in this section, withminimum three years of experienceand approved by manufacturer.

1.06 DELIVERY, STORAGE, AND HANDLINGA. Accept materials on site in original factory packaging, labelled with manufacturer's identification, including

product density and thickness.B. Protect insulation from weather and construction traffic, dirt, water, chemical, and mechanical damage, by

storing in original wrapping.1.07 FIELD CONDITIONS

A. Maintain ambient temperatures and conditions required by manufacturers of adhesives, mastics, andinsulation cements.

B. Maintain temperature during and after installation for minimum period of 24 hours.PART 2 PRODUCTS2.01 REGULATORY REQUIREMENTS

A. Surface Burning Characteristics: Flame spread index/Smoke developed index of 25/50, maximum, whentested in accordance with ASTM E84 or UL 723.

23 0713 - 2216026 / IPERS FY17 Project DUCT INSULATION

2.02 GLASS FIBER, FLEXIBLEA. Manufacturer:

1. Johns Manville Corporation "Microlite": www.jm.com.2. Knauf Insulation: www.knaufinsulation.com.3. Owens Corning Corporation: www.ocbuildingspec.com.4. CertainTeed Corporation: www.certainteed.com.5. Engineer approved equal6. Substitutions: See Section 01 6000 - Product Requirements.

B. Insulation: ASTM C553; flexible, noncombustible blanket.1. 'K' value: 0.27 at 75 degrees F, when tested in accordance with ASTM C518.2. Maximum Service Temperature: 450 degrees F.3. Maximum Water Vapor Absorption: 5.0 percent by weight.

C. Vapor Barrier Jacket:1. Kraft paper with glass fiber yarn and bonded to aluminized film.2. Moisture Vapor Permeability: 0.029 ng/Pa s m (0.02 perm inch), when tested in accordance with ASTM

E96/E96M.3. Secure with pressure sensitive tape.

D. Vapor Barrier Tape:1. Kraft paper reinforced with glass fiber yarn and bonded to aluminized film, with pressure sensitive

rubber based adhesive.PART 3 EXECUTION3.01 EXAMINATION

A. Verify that ducts have been tested before applying insulation materials.B. Verify that surfaces are clean, foreign material removed, and dry.

3.02 INSTALLATIONA. Install in accordance with manufacturer's instructions.B. Install in accordance with NAIMA National Insulation Standards.C. Insulated ducts conveying air below ambient temperature:

1. Provide insulation with vapor barrier jackets.2. Finish with tape and vapor barrier jacket.3. Continue insulation through walls, sleeves, hangers, and other duct penetrations.4. Insulate entire system including fittings, joints, flanges, fire dampers, flexible connections, and

expansion joints.D. Insulated ducts conveying air above ambient temperature:

1. Provide with or without standard vapor barrier jacket.2. Insulate fittings and joints. Where service access is required, bevel and seal ends of insulation.

E. External Duct Insulation Application:1. Secure insulation with vapor barrier with wires and seal jacket joints with vapor barrier adhesive or tape

to match jacket.2. Install without sag on underside of duct. Use adhesive or mechanical fasteners where necessary to

prevent sagging. Lift duct off trapeze hangers and insert spacers.3. Seal vapor barrier penetrations by mechanical fasteners with vapor barrier adhesive.4. Stop and point insulation around access doors and damper operators to allow operation without

disturbing wrapping.3.03 SCHEDULES

A. Supply Ducts:1. Flexible Glass Fiber Duct Insulation: 1-1/2 inches thick.

END OF SECTION

23 0719 - 1216026 / IPERS FY17 Project HVAC PIPING INSULATION

SECTION 23 0719HVAC PIPING INSULATION


A. Piping insulation.1.02 RELATED REQUIREMENTS

A. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 07 8400 - Firestopping.D. Section 23 2113 - Hydronic Piping: Placement of hangers and hanger inserts.

1.03 REFERENCE STANDARDSA. ASTM C177 - Standard Test Method for Steady-State Heat Flux Measurements and Thermal Transmission

Properties by Means of the Guarded Hot Plate Apparatus; 2013.B. ASTM C195 - Standard Specification for Mineral Fiber Thermal Insulating Cement; 2007 (Reapproved 2013).C. ASTM C534/C534M - Standard Specification for Preformed Flexible Elastomeric Cellular Thermal Insulation

in Sheet and Tubular Form; 2014.D. ASTM C547 - Standard Specification for Mineral Fiber Pipe Insulation; 2015.E. ASTM C795 - Standard Specification for Thermal Insulation for Use in Contact with Austenitic Stainless

Steel; 2008 (Reapproved 2013).F. ASTM E84 - Standard Test Method for Surface Burning Characteristics of Building Materials; 2015a.G. ASTM E96/E96M - Standard Test Methods for Water Vapor Transmission of Materials; 2014.H. NFPA 255 - Standard Method of Test of Surface Burning Characteristics of Building Materials; National Fire

Protection Association; 2006.I. UL 723 - Standard for Test for Surface Burning Characteristics of Building Materials; Underwriters

Laboratories Inc.; Current Edition, Including All Revisions.1.04 SUBMITTALS

A. See Section 01 3000 - Submittal Procedures, for submittal procedures.B. Product Data: Provide product description, thermal characteristics, list of materials and thickness for each

service, and locations.C. Samples: Submit two samples of any representative size illustrating each insulation type.D. Manufacturer's Instructions: Indicate installation procedures that ensure acceptable workmanship and

installation standards will be achieved.1.05 QUALITY ASSURANCE

A. Manufacturer Qualifications: Company specializing in manufacturing the Products specified in this sectionwith not less than three years of documented experience.

B. Applicator Qualifications: Company specializing in performing the type of work specified in this section withminimum five years of experience.

1.06 DELIVERY, STORAGE, AND HANDLINGA. Accept materials on site, labeled with manufacturer's identification, product density, and thickness.

1.07 FIELD CONDITIONSA. Maintain ambient conditions required by manufacturers of each product.B. Maintain temperature before, during, and after installation for minimum of 24 hours.

PART 2 PRODUCTS2.01 REGULATORY REQUIREMENTS

A. Surface Burning Characteristics: Flame spread index/Smoke developed index of 25/50, maximum, whentested in accordance with ASTM E84 or UL 723.


2.02 GLASS FIBERA. Manufacturers:

1. Johns Manville Corporation; "Micro-Lok": www.jm.com.2. Knauf Insulation: www.knaufinsulation.com.3. Owens Corning Corp: www.owenscorning.com.4. CertainTeed Corporation: www.certainteed.com.5. Engineer approved equivalent.6. Substitutions: See Section 01 6000 - Product Requirements.

B. Insulation: ASTM C547 and ASTM C795; rigid molded, noncombustible.1. 'K' Value: ASTM C177, 0.24 at 75 degrees F.2. Maximum Service Temperature: 850 degrees F.3. Maximum Moisture Absorption: 0.2 percent by volume.

C. Vapor Barrier Jacket: White kraft paper with glass fiber yarn, bonded to aluminized film; moisture vaportransmission when tested in accordance with ASTM E96/E96M of 0.02 perm-inches.

D. Vapor Barrier Lap Adhesive: Compatible with insulation.1. Compatible with insulation.

E. Insulating Cement/Mastic: ASTM C195; hydraulic setting on mineral wool.1. ASTM C195; hydraulic setting on mineral wool.

2.03 FLEXIBLE ELASTOMERIC CELLULAR INSULATIONA. Manufacturer:

1. Armacell International; "Armaflex": www.armacell.com.2. K-Flex USA LLC: www.kflexusa.com.3. Engineer approved equivalent4. Substitutions: See Section 01 6000 - Product Requirements.

B. Insulation: Preformed flexible elastomeric cellular rubber insulation complying with ASTM C534/C534MGrade 3; use molded tubular material wherever possible.1. Minimum Service Temperature: Minus 40 degrees F.2. Maximum Service Temperature: 220 degrees F.3. Connection: Waterproof vapor barrier adhesive.

C. Elastomeric Foam Adhesive: Air dried, contact adhesive, compatible with insulation.PART 3 EXECUTION3.01 EXAMINATION

A. Verify that piping has been tested before applying insulation materials.B. Verify that surfaces are clean and dry, with foreign material removed.

3.02 INSTALLATIONA. Install in accordance with manufacturer's instructions.B. Install in accordance with NAIMA National Insulation Standards.C. Exposed Piping: Locate insulation and cover seams in least visible locations.D. Insulated pipes conveying fluids below ambient temperature; insulate entire system including fittings, valves,

unions, flanges, strainers, flexible connections, and expansion joints.E. Glass fiber insulated pipes conveying fluids below ambient temperature:

1. Provide vapor barrier jackets, factory-applied or field-applied; secure with self-sealing longitudinal lapsand butt strips with pressure sensitive adhesive. Secure with outward clinch expanding staples andvapor barrier mastic.

2. Insulate fittings, joints, and valves with molded insulation of like material and thickness as adjacent pipe. Finish with glass cloth and vapor barrier adhesive or PVC fitting covers.

F. Inserts and Shields:1. Application: Piping 1-1/2 inches diameter or larger.2. Shields: Galvanized steel between pipe hangers or pipe hanger rolls and inserts.3. Insert location: Between support shield and piping and under the finish jacket.4. Insert Configuration: Minimum 6 inches long, of same thickness and contour as adjoining insulation;

may be factory fabricated.


5. Insert Material: Hydrous calcium silicate insulation or other heavy density insulating material suitable forthe planned temperature range.

G. Continue insulation through walls, sleeves, pipe hangers, and other pipe penetrations. Finish at supports,protrusions, and interruptions. At fire separations, refer to Section 07 8400.

3.03 SCHEDULEA. Cooling Systems:

1. Condensate Drains from Cooling Coils:a. Glass Fiber Insulation:

1) Pipe size range: 1 inch or less2) Thickness: 1/2 inch3) Pipe size range: 1-1/4 inches to 2 inches4) Thickness: 1 inch

2. Refrigerant Suction:a. Elastomeric Cellular Insulation:

1) Pipe size range: All sizes2) Thickness: 3/4 inches

3. Refrigerant Hot Gas:a. Elastomeric Cellular Insulation:

1) Pipe size range: All sizes2) Thickness: 3/4 inches

END OF SECTION

23 2113 - 1216026 / IPERS FY17 Project HYDRONIC PIPING

SECTION 23 2113HYDRONIC PIPING


A. Pipe and pipe fittings for:1. Equipment drains and overflows.

B. Pipe hangers and supports.C. Unions, flanges, mechanical couplings, and dielectric connections.

1.02 RELATED REQUIREMENTSA. Section 07 8400 - Firestopping.B. Division 00 - Introductory Information, Bidding, and Contracting RequirementsC. Division 01 - General RequirementsD. Section 08 3100 - Access Doors and Panels.E. Section 23 0719 - HVAC Piping Insulation.

1.03 REFERENCE STANDARDSA. ASME B16.18 - Cast Copper Alloy Solder Joint Pressure Fittings; The American Society of Mechanical

Engineers; 2012 (ANSI B16.18).B. ASME B16.22 - Wrought Copper and Copper Alloy Solder-Joint Pressure Fittings; 2013.C. ASME B31.9 - Building Services Piping; 2014 (ANSI/ASME B31.9).D. ASME B16.22 - Wrought Copper and Copper Alloy Solder Joint Pressure Fittings; The American Society of

Mechanical Engineers; 2001 (R2005).E. ASME B31.9 - Building Services Piping; The American Society of Mechanical Engineers; 2008 (ANSI/ASME

B31.9).F. ASTM B32 - Standard Specification for Solder Metal; 2008.G. ASTM B88 - Standard Specification for Seamless Copper Water Tube; 2014.H. ASTM B88M - Standard Specification for Seamless Copper Water Tube (Metric); 2013.I. ASTM F708 - Standard Practice for Design and Installation of Rigid Pipe Hangers; 1992 (Reapproved 2014).J. AWWA C606 - Grooved and Shouldered Joints; 2015 (ANSI/AWWA C606).K. AWWA C606 - Standard Specification for Grooved and Shouldered Joints; American Water Works

Association; 2006.L. MSS SP-58 - Pipe Hangers and Supports - Materials, Design and Manufacture, Selection, Application, and

Installation; Manufacturers Standardization Society of the Valve and Fittings Industry, Inc.; 2009.1.04 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Include data on pipe materials, pipe fittings, valves, and accessories. Provide manufacturers

catalogue information. Indicate valve data and ratings.1.05 QUALITY ASSURANCE

A. Manufacturer Qualifications: Company specializing in manufacturing products of the type specified in thissection, with minimum three years of documented experience.

B. Installer Qualifications: Company specializing in performing work of the type specified in this section, withminimum three years of experience.

1.06 DELIVERY, STORAGE, AND HANDLINGA. Provide temporary end caps and closures on piping and fittings. Maintain in place until installation.B. Protect piping systems from entry of foreign materials by temporary covers, completing sections of the work,

and isolating parts of completed system.1.07 FIELD CONDITIONS

A. Do not install underground piping when bedding is wet or frozen.


PART 2 PRODUCTS2.01 EQUIPMENT DRAINS AND OVERFLOWS

A. Copper Tube: ASTM B88 (ASTM B88M), Type L (B), drawn; using one of the following joint types:1. Solder Joints: ASME B16.18 cast brass/bronze or ASME B16.22 solder wrought copper fittings; ASTM

B32 lead-free solder, HB alloy (95-5 tin-antimony) or tin and silver.2. Grooved Joints: AWWA C606 grooved pipe, fittings of same material, and mechanical couplings.3. Joints: Solder, lead free, ASTM B 32, HB alloy (95-5 tin-antimony), or tin and silver.4. Equipment drains on roof shall be copper.

2.02 PIPE HANGERS AND SUPPORTSA. Provide hangers and supports that comply with MSS SP-58.

1. If type of hanger or support for a particular situation is not indicated, select appropriate type using MSSSP-58 recommendations.

B. Conform to ASME B31.9.C. Hangers for Pipe Sizes 1/2 to 1-1/2 Inch: Malleable iron, adjustable swivel, split ring.D. Hangers for Cold Pipe Sizes 2 Inches and Greater: Carbon steel, adjustable, clevis.E. Hangers for Hot Pipe Sizes 2 to 4 Inches: Carbon steel, adjustable, clevis.F. Hangers for Hot Pipe Sizes 6 Inches and Greater: Adjustable steel yoke, cast iron roll, double hanger.G. Multiple or Trapeze Hangers: Steel channels with welded spacers and hanger rods.H. Wall Support for Pipe Sizes to 3 Inches: Cast iron hook.I. Wall Support for Pipe Sizes 4 Inches and Greater: Welded steel bracket and wrought steel clamp.J. Wall Support for Hot Pipe Sizes 6 Inches and Greater: Welded steel bracket and wrought steel clamp with

adjustable steel yoke and cast iron roll.K. Vertical Support: Steel riser clamp.L. Floor Support for Cold Pipe: Cast iron adjustable pipe saddle, lock nut, nipple, floor flange, and concrete pier

or steel support.M. Copper Pipe Support: Carbon steel ring, adjustable, copper plated.N. Hanger Rods: Mild steel threaded both ends, threaded one end, or continuous threaded.

2.03 UNIONS, FLANGES, MECHANICAL COUPLINGS, AND DIELECTRIC CONNECTIONSA. Unions for Pipe 2 Inches and Less:

1. Ferrous Piping: 150 psig malleable iron, threaded.2. Copper Pipe: Bronze, soldered joints.

B. Flanges for Pipe 2 Inches and Greater:1. Ferrous Piping: 150 psig forged steel, slip-on.2. Copper Piping: Bronze.3. Gaskets: 1/16 inch thick preformed neoprene.

C. Dielectric Connections:1. Waterways:

a. Water impervious insulation barrier capable of limiting galvanic current to 1 percent of short circuitcurrent in a corresponding bimetallic joint.

b. Dry insulation barrier able to withstand 600 volt breakdown test.c. Construct of galvanized steel with threaded end connections to match connecting piping.d. Suitable for the required operating pressures and temperatures.

2. Flanges:a. Dielectric flanges with same pressure ratings as standard flanges.b. Water impervious insulation barrier capable of limiting galvanic current to 1 percent of short circuit

current in a corresponding bimetallic joint.c. Dry insulation barrier able to withstand 600 volt breakdown test.d. Construct of galvanized steel with threaded end connections to match connecting piping.e. Suitable for the required operating pressures and temperatures.



A. Ream pipe and tube ends. Remove burrs. Bevel plain end ferrous pipe.B. Remove scale and dirt on inside and outside before assembly.C. Prepare piping connections to equipment using jointing system specified.D. Keep open ends of pipe free from scale and dirt. Protect open ends with temporary plugs or caps.E. After completion, fill, clean, and treat systems. Refer to Section 23 2500 for additional requirements.

3.02 INSTALLATIONA. Install in accordance with manufacturer's instructions.B. Route piping in orderly manner, parallel to building structure, and maintain gradient.C. Install piping to conserve building space and to avoid interfere with use of space.D. Group piping whenever practical at common elevations.E. Sleeve pipe passing through partitions, walls and floors.F. Install firestopping to preserve fire resistance rating of partitions and other elements, using materials and

methods specified in Section 07 8400.G. Slope piping and arrange to drain at low points.H. Install piping to allow for expansion and contraction without stressing pipe, joints, or connected equipment.I. Pipe Hangers and Supports:

1. Install in accordance with ASME B31.9, ASTM F708, or MSS SP-58.2. Support horizontal piping as scheduled.3. Install hangers to provide minimum 1/2 inch space between finished covering and adjacent work.4. Place hangers within 12 inches of each horizontal elbow.5. Use hangers with 1-1/2 inch minimum vertical adjustment. Design hangers for pipe movement without

disengagement of supported pipe.6. Support vertical piping at every other floor. Support riser piping independently of connected horizontal

piping.a. Where several pipes can be installed in parallel and at same elevation, provide multiple or trapeze

hangers.7. Provide copper plated hangers and supports for copper piping.8. Prime coat exposed steel hangers and supports. Refer to Section 09 9123. Hangers and supports

located in crawl spaces, pipe shafts, and suspended ceiling spaces are not considered exposed.J. Provide clearance in hangers and from structure and other equipment for installation of insulation and access

to valves and fittings. Refer to Section 23 0719.K. Where pipe support members are welded to structural building framing, scrape, brush clean, and apply one

coat of zinc rich primer to welds.L. Prepare unfinished pipe, fittings, supports, and accessories, ready for finish painting. Refer to Section 09

9123.M. Contractor shall immediately thoroghly clean walls to remove "runs" or "drips" after sawcutting or core-drilling

penetrations through CMU or concrete.N. At penetrations through exterior walls, form or core drill for sleeves. Sleeves in new concrete to have integral

water stop. Provide "Link-Seal" and exterior sealant to neatly seal opening or propose alternative for reviewand approval by Owner. Sealant color shall be as per Architect.

O. No loads shall be permiteed to be hung from metal or wood roof decking. All hangers shall be hung directlyfrom the top member of structural steel or supplementary members acceptable to the Structural Engineerand only with prior approval.

3.03 SCHEDULESA. Hanger Spacing for Copper Tubing.

1. 1/2 inch and 3/4 inch: Maximum span, 5 feet; minimum rod size, 1/4 inch.2. 1 inch: Maximum span, 6 feet; minimum rod size, 1/4 inch.3. 1-1/2 inch and 2 inch: Maximum span, 8 feet; minimum rod size, 3/8 inch.4. 2-1/2 inch: Maximum span, 9 feet; minimum rod size, 3/8 inch.


END OF SECTION

23 2300 - 1216026 / IPERS FY17 Project REFRIGERANT PIPING

SECTION 23 2300REFRIGERANT PIPING


A. Piping.B. Refrigerant.

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 08 3100 - Access Doors and Panels.D. Section 22 0719 - Plumbing Piping Insulation.

1.03 REFERENCE STANDARDSA. ASHRAE Std 15 - Safety Standard for Refrigeration Systems; 2013 (ANSI/ASHRAE Std 15).B. ASHRAE Std 34 - Designation and Safety Classification of Refrigerants; 2013 with All Amendments and

Errata.C. ASME BPVC-IX - Boiler and Pressure Vessel Code, Section IX - Welding, Brazing, and Fusing

Qualifications; The American Society of Mechanical Engineers; 2015.D. ASME B16.22 - Wrought Copper and Copper Alloy Solder-Joint Pressure Fittings; The American Society of

Mechanical Engineers; 2013.E. ASME B16.26 - Cast Copper Alloy Fittings For Flared Copper Tubes; The American Society of Mechanical

Engineers; 2013.F. ASME B31.5 - Refrigeration Piping and Heat Transfer Components; The American Society of Mechanical

Engineers; 2013.G. ASME B31.9 - Building Services Piping; The American Society of Mechanical Engineers; 2014 (ANSI/ASME

B31.9).H. ASTM B88 - Standard Specification for Seamless Copper Water Tube; 2014.I. ASTM B88M - Standard Specification for Seamless Copper Water Tube (Metric); 2013.J. ASTM B280 - Standard Specification for Seamless Copper Tube for Air Conditioning and Refrigeration Field

Service; 2013.K. AWS A5.8M/A5.8 - Specification for Filler Metals for Brazing and Braze Welding; American Welding Society;

2011-AMD 1.L. MSS SP-58 - Pipe Hangers and Supports - Materials, Design, Manufacture, Selection, Application, and

Installation; Manufacturers Standardization Society of the Valve and Fittings Industry, Inc.; 2009.1.04 SYSTEM DESCRIPTION

A. Where more than one piping system material is specified ensure system components are compatible andjoined to ensure the integrity of the system is not jeopardized. Provide necessary joining fittings. Ensureflanges, union, and couplings for servicing are consistently provided.

B. Provide pipe hangers and supports in accordance with ASME B31.5 unless indicated otherwise.1.05 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide general assembly of specialties, including manufacturers catalogue information.

Provide manufacturers catalog data including load capacity.C. Shop Drawings: Indicate schematic layout of system, including equipment, critical dimensions, and sizes.D. Design Data: Submit design data indicating pipe sizing. Indicate load carrying capacity of trapeze, multiple

pipe, and riser support hangers.E. Test Reports: Indicate results of leak test, acid test.F. Manufacturer's Installation Instructions: Indicate support, connection requirements, and isolation for

servicing.


G. Project Record Documents: Record exact locations of equipment and refrigeration accessories on recorddrawings.

H. Maintenance Data: Include instructions for changing cartridges, assembly views, spare parts lists.1.06 QUALITY ASSURANCE

A. Installer Qualifications: Company specializing in performing the type of work specified in this section, withminimum five years ofdocumented experience.

B. Design piping system under direct supervision of a Professional Engineer experienced in design of this typeof work and licensed in Iowa.

1.07 REGULATORY REQUIREMENTSA. Conform to ASME B31.9 for installation of piping system.B. Welding Materials and Procedures: Conform to ASME BPVC-IX and applicable state labor regulations.C. Products Requiring Electrical Connection: Listed and classified by UL, as suitable for the purpose indicated.

1.08 DELIVERY, STORAGE, AND HANDLINGA. Deliver and store piping and specialties in shipping containers with labeling in place.B. Protect piping and specialties from entry of contaminating material by leaving end caps and plugs in place

until installation.C. Dehydrate and charge components such as piping and receivers, seal prior to shipment, until connected into

system.PART 2 PRODUCTS2.01 PIPING

A. Copper Tube: ASTM B280, H58 hard drawn or O60 soft annealed.1. Fittings: ASME B16.22 wrought copper.2. Joints: Braze, AWS A5.8M/A5.8 BCuP silver/phosphorus/copper alloy.

B. Copper Tube to 7/8 inch OD: ASTM B88 (ASTM B88M), Type K (A), annealed.1. Fittings: ASME B16.26 cast copper.2. Joints: Flared.

C. Pipe Supports and Anchors:1. Provide hangers and supports that comply with MSS SP-58.

a. If type of hanger or support for a particular situation is not indicated, select appropriate type usingMSS SP-58 recommendations.

2. Conform to ASME B31.5.3. Hangers for Pipe Sizes 1/2 to 1-1/2 Inch: Malleable iron adjustable swivel, split ring.4. Hangers for Pipe Sizes 2 Inches and Over: Carbon steel, adjustable, clevis.5. Multiple or Trapeze Hangers: Steel channels with welded spacers and hanger rods.6. Wall Support for Pipe Sizes to 3 Inches: Cast iron hook.7. Wall Support for Pipe Sizes 4 Inches and Over: Welded steel bracket and wrought steel clamp.8. Vertical Support: Steel riser clamp.9. Copper Pipe Support: Carbon steel ring, adjustable, copper plated.10. Hanger Rods: Mild steel threaded both ends, threaded one end, or continuous threaded.11. Inserts: Malleable iron case of galvanized steel shell and expander plug for threaded connection with

lateral adjustment, top slot for reinforcing rods, lugs for attaching to forms; size inserts to suit threadedhanger rods.

2.02 REFRIGERANTA. Refrigerant: R-410a as defined in ASHRAE Std 34.


A. Ream pipe and tube ends. Remove burrs. Bevel plain end ferrous pipe.B. Remove scale and dirt on inside and outside before assembly.C. Prepare piping connections to equipment with flanges or unions.


3.02 INSTALLATIONA. Install refrigeration specialties in accordance with manufacturer's instructions.B. Route piping in orderly manner, with plumbing parallel to building structure, and maintain gradient.C. Install piping to conserve building space and avoid interference with use of space.D. Group piping whenever practical at common elevations and locations. Slope piping one percent in direction

of oil return.E. Install piping to allow for expansion and contraction without stressing pipe, joints, or connected equipment.F. Pipe Hangers and Supports:

1. Install in accordance with ASME B31.5.2. Support horizontal piping as scheduled.3. Install hangers to provide minimum 1/2 inch space between finished covering and adjacent work.4. Place hangers within 12 inches of each horizontal elbow.5. Support vertical piping at every other floor. Support riser piping independently of connected horizontal

piping.6. Where several pipes can be installed in parallel and at same elevation, provide multiple or trapeze

hangers.7. Provide copper plated hangers and supports for copper piping.

G. Arrange piping to return oil to compressor. Provide traps and loops in piping, and provide double risers asrequired. Slope horizontal piping 0.40 percent in direction of flow.

H. Provide clearance for installation of insulation and access to valves and fittings.I. Provide access to concealed valves and fittings. Coordinate size and location of access doors with Section

08 3100.J. Flood piping system with nitrogen when brazing.K. Insulate piping; refer to Section and Section 22 0716.L. Follow ASHRAE Std 15 procedures for charging and purging of systems and for disposal of refrigerant.M. Fully charge completed system with refrigerant after testing.

3.03 FIELD QUALITY CONTROLA. See Section 01 4000 - Quality Requirements, for additional requirements.B. Test refrigeration system in accordance with ASME B31.5.C. Pressure test system with dry nitrogen to 200 psi. Perform final tests at 27 inches vacuum and 200 psi using

electronic leak detector. Test to no leakage.3.04 SCHEDULES

A. Hanger Spacing for Copper Tubing.1. 1/2 inch, 5/8 inch, and 7/8 inch OD: Maximum span, 5 feet; minimum rod size, 1/4 inch.2. 1-1/8 inch OD: Maximum span, 6 feet; minimum rod size, 1/4 inch.3. 1-3/8 inch OD: Maximum span, 7 feet; minimum rod size, 3/8 inch.4. 1-5/8 inch OD: Maximum span, 8 feet; minimum rod size, 3/8 inch.

END OF SECTION

23 3100 - 1216026 / IPERS FY17 Project HVAC DUCTS AND CASINGS

SECTION 23 3100HVAC DUCTS AND CASINGS


A. Metal ductwork.B. Nonmetal ductwork.

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 23 0713 - Duct Insulation: External insulation and duct liner.D. Section 23 3300 - Air Duct Accessories.E. Section 23 0593 - Testing, Adjusting, and Balancing for HVAC.

1.03 REFERENCE STANDARDSA. ASHRAE (FUND) - ASHRAE Handbook - Fundamentals; 2013.B. ASTM A36/A36M - Standard Specification for Carbon Structural Steel; 2014.C. ASTM A653/A653M - Standard Specification for Steel Sheet, Zinc-Coated (Galvanized) or Zinc-Iron

Alloy-Coated (Galvannealed) by the Hot-Dip Process; 2015.D. ASTM E84 - Standard Test Method for Surface Burning Characteristics of Building Materials; 2015a.E. NFPA 90A - Standard for the Installation of Air-Conditioning and Ventilating Systems; National Fire Protection

Association; 2015.F. SMACNA (DCS) - HVAC Duct Construction Standards Metal and Flexible; 2005 (Rev. 2009).G. SMACNA (LEAK) - HVAC Air Duct Leakage Test Manual; 2012, 2nd Edition.

1.04 PERFORMANCE REQUIREMENTSA. No variation of duct configuration or sizes permitted except by written permission. Size round ducts installed

in place of rectangular ducts in accordance with ASHRAE table of equivalent rectangular and round ducts.1.05 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide data for duct materials.C. Shop Drawings: Indicate duct fittings, particulars such as gages, sizes, welds, and configuration prior to start

of work for 4-inch pressure class and higher systems.D. Project Record Documents: Record actual locations of ducts and duct fittings. Record changes in fitting

location and type. Show additional fittings used.1.06 QUALITY ASSURANCE

A. Manufacturer Qualifications: Company specializing in manufacturing the type of products specified in thissection, with minimum three years of documented experience, and approved by manufacturer.

B. Installer Qualifications: Company specializing in performing the type of work specified in this section, withminimum five years ofdocumented experience.

1.07 REGULATORY REQUIREMENTSA. Construct ductwork to NFPA 90A standards.

1.08 FIELD CONDITIONSA. Do not install duct sealants when temperatures are less than those recommended by sealant manufacturers.B. Maintain temperatures within acceptable range during and after installation of duct sealants.

PART 2 PRODUCTS2.01 DUCT ASSEMBLIES

A. Regulatory Requirements: Construct ductwork to NFPA 90A standards.


2.02 MATERIALSA. Galvanized Steel for Ducts: Hot-dipped galvanized steel sheet, ASTM A653/A653M FS Type B, with

G60/Z180 coating.B. Joint Sealers and Sealants: Non-hardening, water resistant, mildew and mold resistant.

1. Type: Heavy mastic or liquid used alone or with tape, suitable for joint configuration and compatiblewith substrates, and recommended by manufacturer for pressure class of ducts.

2. Surface Burning Characteristics: Flame spread index of zero and smoke developed index of zero,when tested in accordance with ASTM E84.

3. Manufacturers:a. Carlisle HVAC Products; Hardcast Iron-Grip 601 Water Based Duct Sealant:

www.carlislehvac.com.b. Engineer approved equivalent.c. Substitutions: See Section 01 6000 - Product Requirements.

C. Hanger Rod: ASTM A36/A36M; steel, galvanized; threaded both ends, threaded one end, or continuouslythreaded.

D. Insulated Flexible Ducts:1. Manufacturers:

a. Thermaflex Model #M-KE.b. ATCO: www.atcoflex.comc. Engineer approved equivalent.d. Substitutions: See Section 01 6000 - Product Requirements.

2. UL 181, Class 1, aluminum laminate and polyester film with latex adhesive supported by helically woundspring steel wire; fiberglass insulation; polyethylene vapor barrier film.a. Pressure Rating: 10 inches WG positive and 1.0 inches WG negative.b. Maximum Velocity: 5000 fpm.c. Temperature Range: -20 degrees F to 210 degrees F.

2.03 DUCTWORK FABRICATIONA. Fabricate and support in accordance with SMACNA (DCS) and as indicated.B. No variation of duct configuration or size permitted except by written permission. Size round duct installed in

place of rectangular ducts in accordance with ASHRAE Handbook - Fundamentals.C. Provide duct material, gages, reinforcing, and sealing for operating pressures indicated.D. T's, bends, and elbows: Construct according to SMACNA (DCS).E. Increase duct sizes gradually, not exceeding 15 degrees divergence wherever possible; maximum 30

degrees divergence upstream of equipment and 45 degrees convergence downstream.F. Fabricate continuously welded round and oval duct fittings in accordance with SMACNA (DCS).G. Fabricate continuously welded round and oval duct fittings two gages heavier than duct gages indicated in

SMACNA Standard. Joints shall be minimum 4 inch cemented slip joint, brazed or electric welded. Primecoat welded joints.

H. Provide standard 45 degree lateral wye takeoffs unless otherwise indicated where 90 degree conical teeconnections may be used.

I. Where ducts are connected to exterior wall louvers and duct outlet is smaller than louver frame, provideblank-out panels sealing louver area around duct. Use same material as duct, painted black on exterior side;seal to louver frame and duct.

2.04 DUCT MANUFACTURERSA. SEMCO Incorporated: www.semcoinc.com.B. United McGill Corporation: www.unitedmcgill.com.C. Sheet Metal Connectors: www.smcduct.comD. NorlockE. Lindab: www.lindab.comF. Engineer approved equivalent.G. Substitutions: See Section 01 6000 - Product Requirements.


2.05 MANUFACTURED DUCTWORK AND FITTINGSA. Manufacture in accordance with SMACNA HVAC Duct Construction Standards - Metal and Flexible, and as

indicated. Provide duct material, gages,reinforcing, and sealing for operating pressures indicated.B. Flat Oval and Round Ducts: Machine made from round spiral lockseam duct without corrugations; fittings

manufactured of at least two gages heavier metal than duct.1. Manufacture in accordance with SMACNA (DCS).2. Fittings: Manufacture at least two gages heavier metal than duct.3. Provide duct material, gages, reinforcing, and sealing for operating pressures indicated.


A. Install, support, and seal ducts in accordance with SMACNA (DCS).B. Install in accordance with manufacturer's instructions.C. During construction provide temporary closures of metal or taped polyethylene on open ductwork to prevent

construction dust from entering ductwork system.D. Flexible Ducts: Connect to metal ducts with adhesive.E. Install flexible ductwork elbow supports at each diffuser, grille, or register, and elsewhere as indicated.F. Duct sizes indicated are inside clear dimensions. For lined ducts, duct liner thickness needs to be accounted

for in the final duct size.G. Install and seal metal and flexible ducts in accordance with SMACNA HVAC Duct Construction Standards -

Metal and Flexible.H. Provide openings in ductwork where required to accommodate thermometers and controllers. Provide pilot

tube openings where required for testing of systems, complete with metal can with spring device or screw toensure against air leakage. Where openings are provided in insulated ductwork, install insulation materialinside a metal ring.

I. Locate ducts with sufficient space around equipment to allow normal operating and maintenance activities.J. Use crimp joints with or without bead for joining round duct sizes 8 inch and smaller with crimp in direction of

air flow.K. Use double nuts and lock washers on threaded rod supports.L. Connect terminal units to supply ducts directly or with one foot maximum length of flexible duct. Do not use

flexible duct to change direction.M. Connect diffusers or light troffer boots to low pressure ducts directly or with 5 feet maximum length of flexible

duct held in place with strap or clamp.3.02 SCHEDULES

A. Ductwork Material:1. Low and Medium Pressure Supply: Galvanized Steel.

B. Ductwork Pressure Class:1. Low Pressure Supply: 1 inch

END OF SECTION

23 3300 - 1216026 / IPERS FY17 Project AIR DUCT ACCESSORIES

SECTION 23 3300AIR DUCT ACCESSORIES


A. Duct test holes.B. Volume control dampers.

1.02 RELATED REQUIREMENTSA. Section 07 8400 - Firestopping.B. Division 00 - Procurement and Contracting RequirementsC. Division 01 - General RequirementsD. Section 23 3100 - HVAC Ducts and Casings.E. Section 26 2717 - Equipment Wiring: Electrical characteristics and wiring connections.

1.03 REFERENCE STANDARDSA. NFPA 90A - Standard for the Installation of Air-Conditioning and Ventilating Systems; National Fire Protection

Association; 2015.B. SMACNA (DCS) - HVAC Duct Construction Standards Metal and Flexible; 2005 (Rev. 2009).

1.04 SUBMITTALSA. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide for shop fabricated assemblies including volume control dampers. Include electrical

characteristics and connection requirements.C. Shop Drawings: Indicate for shop fabricated assemblies including volume control dampers.D. Project Record Drawings: Record actual locations of access doors and test holes.

1.05 PROJECT RECORD DOCUMENTSA. Record actual locations of access doors and test holes.

1.06 QUALITY ASSURANCEA. Manufacturer Qualifications: Company specializing in manufacturing the type of products specified in this

section, with minimum three years of documented experience.B. Products Requiring Electrical Connection: Listed and classified by Underwriters Laboratories Inc. as suitable

for the purpose specified and indicated.PART 2 PRODUCTS2.01 DUCT TEST HOLES

A. Temporary Test Holes: Cut or drill in ducts as required. Cap with neat patches, neoprene plugs, threadedplugs, or threaded or twist-on metal caps.

B. Permanent Test Holes: Factory fabricated, air tight flanged fittings with screw cap. Provide extended neckfittings to clear insulation.

2.02 VOLUME CONTROL DAMPERSA. Manufacturers:

1. Louvers & Dampers, Inc: www.louvers-dampers.com.2. Nailor Industries Inc: www.nailor.com.3. Ruskin Company: www.ruskin.com.4. Engineer approved equivalent.5. Substitutions: See Section 01 6000 - Product Requirements.

B. Fabricate in accordance with SMACNA (DCS) and as indicated.C. Single Blade Dampers: Fabricate for duct sizes up to 6 x 30 inch.D. Multi-Blade Damper: Fabricate of opposed blade pattern with maximum blade sizes 8 x 72 inch. Assemble

center and edge crimped blades in prime coated or galvanized channel frame with suitable hardware.E. End Bearings: Except in round ducts 12 inches and smaller, provide end bearings. On multiple blade

dampers, provide oil-impregnated nylon, thermoplastic elastomer, or sintered bronze bearings.

23 3300 - 2216026 / IPERS FY17 Project AIR DUCT ACCESSORIES

F. Quadrants:1. Provide locking, indicating quadrant regulators on single and multi-blade dampers.2. On insulated ducts mount quadrant regulators on stand-off mounting brackets, bases, or adapters.

2.03 MISCELLANEOUS PRODUCTSA. Internal Strut End Plugs: Combination end-mounting and sealing plugs for metal conduit used as internal

reinforcement struts for metal ducts; plug crimped inside conduit with outside gasketed washer seal.B. Duct Opening Closure Film: Mold-resistant, self-adhesive film to keep debris out of ducts during

construction.1. Thickness: 2 mils.2. High tack water based adhesive.3. UV stable light blue color.4. Elongation Before Break: 325 percent, minimum.5. Manufacturers:

a. Carlisle HVAC Products; Dynair Duct Protection Film: www.carlislehvac.com.b. Engineer approved equivalent.c. Substitutions: See Section 01 6000 - Product Requirements.

C. For dampers above non-removable ceilings and without ceiling access panels provide Ventloc #667 orequivalent damper regulator with paintable cover plate and interconnecting hardware.

D. Balancing damper above non-removable ceilings shall have volume control dampers, casing and wire, cable,locking gear cable controller and control wrench all as an integrated system. Control dampers shall beopposed blade rectangular or round as required for the specific branch ducts. Cable, casing and wire shallbe routed concealed within duct or above ceiling. Wrench operated controller shall be mounted concealed induct drop on hard ducted diffusers and inside plenum on plenum slot diffusers. Wrench operated controllershall be mounted to frame or back cone of lay-in ceiling diffusers. Provide and install mouting brackets asrequired for operator mounting. Provide stand-off mounting brackets on insulated ductwork and plenums. Controller may also be mounted in accessible mechanical or storage room.


A. Install accessories in accordance with manufacturer's instructions, NFPA 90A, and follow SMACNA (DCS). Refer to Section 23 3100 for duct construction and pressure class.

B. Provide duct test holes where indicated and required for testing and balancing purposes.C. At fans and motorized equipment associated with ducts, provide flexible duct connections immediately

adjacent to the equipment.D. At equipment supported by vibration isolators, provide flexible duct connections immediately adjacent to the

equipment.E. Provide balancing dampers at points on supply, return, and exhaust systems where branches are taken from

larger ducts as required for air balancing. Install minimum 2 duct widths from duct take-off.F. Provide balancing dampers on duct take-off to diffusers, grilles, and registers, regardless of whether

dampers are specified as part of the diffuser, grille, or register assembly.END OF SECTION

23 8129 - 1216026 / IPERS FY17 Project VARIABLE REFRIGERANT VOLUME (VRV) HVAC SYSTEM

SECTION 23 8129VARIABLE REFRIGERANT VOLUME (VRV) HVAC SYSTEM


A. Variable refrigerant volume HVAC system includes:1. Indoor/Evaporator units.2. Branch selector units.3. Refrigerant piping.4. Control panels.5. Control wiring.

1.02 RELATED REQUIREMENTSA. Section 22 1005 - Plumbing Piping: Condensate drain piping.B. Section 22 3000 - Plumbing Equipment: Cooling condensate removal pumps.C. Section 23 0800 - Commissioning of HVAC.D. Section 23 2300 - Refrigerant Piping: Additional requirements for refrigerant piping system.E. Section 26 2717 - Equipment Wiring: Power connections to equipment.

1.03 REFERENCE STANDARDSA. AHRI 210/240 - Standard for Performance Rating of Unitary Air-Conditioning and Air-Source Heat Pump

Equipment; Air-Conditioning, Heating, and Refrigeration Institute; 2008, Including All Addenda.B. ASHRAE Std 90.1 I-P - Energy Standard for Buildings Except Low-Rise Residential Buildings; 2013,

Including All Amendments and Errata (ANSI/ASHRAE/IES Std 90.1).C. ITS (DIR) - Directory of Listed Products; current edition.D. NFPA 70 - National Electrical Code; National Fire Protection Association; Most Recent Edition Adopted by

Authority Having Jurisdiction, Including All Applicable Amendments and Supplements.E. UL 1995 - Heating and Cooling Equipment; Current Edition, Including All Revisions.

1.04 ADMINISTRATIVE REQUIREMENTSA. Preinstallation Meeting: Conduct a preinstallation meeting one week prior to the start of the work of this

section; require attendance by all affected installers.1.05 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Design Data:

1. Provide design calculations showing that system will achieve performance specified.2. Provide design data required by ASHRAE Std 90.1 I-P.

C. Product Data: Submit manufacturer's standard data sheets showing the following for each item ofequipment, marked to correlate to equipment item markings shown in the contract documents:1. Outdoor/Central Units:

a. Refrigerant Type and Size of Charge.b. Cooling Capacity: Btu/h.c. Heating Capacity: Btu/h.d. Cooling Input Power: Btu/h.e. Heating Input Power: Btu/h.f. Operating Temperature Range, Cooling and Heating.g. Air Flow: Cubic feet per minute.h. Fan Curves.i. External Static Pressure (ESP): Inches WG.j. Sound Pressure Level: dB(A).k. Electrical Data:

1) Maximum Circuit Amps (MCA).2) Maximum Fuse Amps (MFA).3) Maximum Starting Current (MSC).4) Full Load Amps (FLA).5) Total Over Current Amps (TOCA).


6) Fan Motor: HP.l. Weight and Dimensions.m. Maximum number of indoor units that can be served.n. Maximum refrigerant piping run from outdoor/condenser unit to indoor/evaporator unit.o. Maximum height difference between outdoor/condenser unit to indoor/evaporator unit, both above

and below.p. Control Options.

2. Indoor/Evaporator Units:a. Cooling Capacity: Btu/h.b. Heating Capacity: Btu/h.c. Cooling Input Power: Btu/h.d. Heating Input Power: Btu/h.e. Air Flow: Cubic feet per minute.f. Fan Curves.g. External Static Pressure (ESP): Inches WG.h. Sound Pressure level: dB(A).i. Electrical Data:

1) Maximum Circuit Amps (MCA).2) Maximum Fuse Amps (MFA).3) Maximum Starting Current (MSC).4) Full Load Amps (FLA).5) Total Over Current Amps (TOCA).6) Fan Motor: HP.

j. Maximum Lift of Built-in Condensate Pump.k. Weight and Dimensions.l. Control Options.

3. Control Panels: Complete description of options, control points, zones/groups.D. Specimen Warranty: Copy of manufacturer's warranties.E. Sustainable Design Documentation: Submit manufacturer's product data on refrigerant used, showing

compliance with specified requirements.F. Shop Drawings: Installation drawings custom-made for this project; include as-designed HVAC layouts,

locations of equipment items, refrigerant piping sizes and locations, condensate piping sizes and locations,remote sensing devices, control components, electrical connections, control wiring connections. Include:1. Detailed piping diagrams, with branch balancing devices.2. Condensate piping routing, size, and pump connections.3. Detailed power wiring diagrams.4. Detailed control wiring diagrams.5. Locations of required access through fixed construction.6. Drawings required by manufacturer.

G. Operating and Maintenance Data:1. Manufacturer's complete standard instructions for each unit of equipment and control panel.2. Custom-prepared system operation, troubleshooting, and maintenance instructions and

recommendations.3. Identification of replaceable parts and local source of supply.

H. Project Record Documents: Record the following:1. As-installed routing of refrigerant piping and condensate piping.2. Locations of access panels.3. Locations of control panels.

1.06 QUALITY ASSURANCEA. Installer Qualifications: Trained and approved by manufacturer of equipment.

1.07 DELIVERY, STORAGE AND HANDLINGA. Deliver, store, and handle equipment and refrigerant piping according to manufacturer's recommendations.

1.08 WARRANTYA. See Section 01 7800 - Closeout Submittals, for additional warranty requirements.



A. Extension of the existing Daikin AC system.B. Systems manufactured by other manufacturers will not be considered.

2.02 HVAC SYSTEM DESIGNA. System Operation: Heating and cooling, simultaneously.

1. Zoning: Provide capability for temperature control for each individual indoor/evaporator unitindependently of all other units.

2. Zoning: Provide heating/cooling selection for each individual indoor/evaporator unit independently of allother units.

3. Provide a complete functional system that achieves the specified performance based on the specifieddesign conditions and that is designed and constructed according to the equipment manufacturer'srequirements. Extension of the existing system shall be an expansion of the existing system. Seedrawing notes on coordination tie-in with existing building controls.

4. Conditioned spaces are shown on the drawings.5. Indoor/Evaporator unit locations are shown on the drawings.6. Branch selector unit locations are shown on the drawings.7. Required equipment unit capacities are shown on the drawings.8. Refrigerant piping sizes are not shown on the drawings.9. Connect equipment to condensate piping provided by others; condensate piping is shown on the

drawings. Coordinate final routing with Architect.B. Refrigerant Piping Lengths: Provide equipment capable of serving system with following piping lengths

without any oil traps:1. Minimum Piping Length from Outdoor/Central Unit(s) to Furthest Terminal Unit: 540 feet, actual; 620

feet, equivalent.2. Total Combined Liquid Line Length: 3280 feet, minimum.3. Maximum Vertical Distance Between Outdoor/Central Unit(s) and Terminal Units: 295 feet.4. Minimum Piping Length Between Indoor Units: 49 feet.5. Maximum pipe length from fan coil unit and connection to existing line shall be 120 feet.

C. Control Wiring Lengths:1. Between Outdoor/Condenser Unit and Indoor/Evaporator Unit: 6,665 feet, minimum.2. Between Outdoor/Condenser Unit and Central Controller: 3,330 feet, minimum.3. Between Indoor/Evaporator Unit and Remote Controller: 1,665 feet.

D. Controls: Provide the following control interfaces:1. For Each Indoor/Evaporator Unit: One wall-mounted wired "local" controller, with temperature sensor;

locate where indicated.2. Tie controls for new unit into existing building system.

E. Local Controllers: Wall-mounted, wired, containing temperature sensor.2.03 EQUIPMENT

A. All Units: Factory assembled, wired, and piped and factory tested for function and safety.1. Refrigerant: R-410A.2. Performance Certification: AHRI Certified; www.ahrinet.org.3. Safety Certification: Tested to UL 1995 by UL or Intertek-ETL, listed in ITS (DIR), and bearing the

certification label.4. Provide outdoor/condensing units capable of serving indoor unit capacity up to 200 percent of the

capacity of the outdoor/condensing unit.5. Provide units capable of serving the zones indicated.6. Thermal Performance: Provide heating and cooling capacity as indicated, based on the following

nominal operating conditions:7. Energy Efficiency: Report EER and COP based on tests conducted at “full load” in accordance with

AHRI 210/240 or alternate test method approved by U.S. Department of Energy.B. Electrical Characteristics:

1. Power - Branch Selector Units: 208 to 230 Volts, single phase, 60 Hz.2. Power - Indoor Units: 208 to 230 Volts, single phase, 60 Hz.3. 208-230 Voltage Range: 187 to 253 volts.


C. Refrigerant Piping:1. Provide three-pipe refrigerant system, including high/low pressure dedicated hot gas, liquid and suction

lines; two-pipe systems utilizing lower temperature mixed liquid/gas refrigerant to perform heat recoveryare not permitted due to reduced heating capabilities.

2. Refrigerant Flow Balancing: Provide refrigerant piping joints and headers specifically designed toensure proper refrigerant balance and flow for optimum system capacity and performance; T-style jointsare prohibited.

3. Insulate each refrigerant line individually between the condensing and indoor units.2.04 BRANCH SELECTOR UNITS

A. Branch Selector Units: Concealed boxes designed specifically for this type of system to controlheating/cooling mode selection of downstream units; consisting of electronic expansion valves, subcoolingheat exchanger, refrigerant control piping and electronics to facilitate communications between unit and mainprocessor and between branch unit and indoor/evaporator units.1. Control direction of refrigerant flow using electronic expansion valves; use of solenoid valves for

changeover and pressure equalization is not permitted due to refrigerant noise; use of multi-port branchselector boxes is not permitted unless spare ports are provided for redundancy.

2. Provide one electronic expansion valve for each downstream unit served, except multipleindoor/evaporator units may be connected, provided balancing joints are used in downstream pipingand total capacity is within capacity range of the branch selector.

3. When branch unit is simultaneously heating and cooling, energize subcooling heat exchanger.4. Casing: Galvanized steel sheet; with flame and heat resistant foamed polyethylene sound and thermal

insulation.5. Refrigerant Connections: Braze type.6. Condensate Drainage: Provide unit that does not require condensate drainage.7. Products:

a. Daikin BSVQ Series.2.05 INDOOR/EVAPORATOR UNITS

A. All Indoor/Evaporator Units: Factory assembled and tested DX fan-coil units, with electronic proportionalexpansion valve, control circuit board, factory wiring and piping, self-diagnostics, auto-restart function,3-minute fused time delay, and test run switch.1. Refrigerant: Refrigerant circuits factory-charged with dehydrated air, for field charging.2. Temperature Control Mechanism: Return air thermistor and computerized

Proportional-Integral-Derivative (PID) control of superheat.3. Coils: Direct expansion type constructed from copper tubes expanded into aluminum fins to form a

mechanical bond; waffle louver fin and high heat exchange, rifled bore tube design; factory tested.a. Braised connctions to refrigerant piping.b. Provide thermistor on liquid and gas lines.

4. Fans: Direct-drive, with statically and dynamically balanced impellers; high and low speeds unlessotherwise indicated; motor thermally protected.

5. Return Air Filter: Washable long-life net filter with mildew proof resin, unless otherwise indicated.6. Condensate Drainage: Built-in condensate drain pan with PVC drain connection.7. Cabinet Insulation: Sound absorbing foamed polystyrene and polyethylene insulation.

B. Ceiling Surface-Mounted Units: White, finished casing, with removable front grille; foamed polystyrene andpolyethylene sound insulation, and mounting brackets; mildew-proof polystyrene drain pan.1. Airflow Control: Auto-swing louver that closes automatically when unit stops; five (5) steps of discharge

angle, set using remote controller; upon restart, discharge angle defaulting to same angle as previousoperation.

2. Sound Pressure Range: Measured at low speed at 3.3 feet below and away from unit.3. Condensate Drain Connection: Side (end), not concealed in wall.4. Fan: Two-speed, direct-drive cross-flow type.5. See drawings for schedule and performance data.

PART 3 EXECUTION3.01 EXAMINATION

A. Verify that required electrical services have been installed and are in the proper locations prior to startinginstallation.

B. Verify that condensate piping has been installed and is in the proper location prior to starting installation.


3.02 INSTALLATIONA. Install in accordance with manufacturer's instructions.B. Install refrigerant piping in accordance with equipment manufacturer's instructions.C. Perform wiring in accordance with NFPA 70, National Electric Code (NEC).D. Coordinate with installers of systems and equipment connecting to this system.E. Adjust refrigerant charge for increased circuit size and capacity.

3.03 FIELD QUALITY CONTROLA. See Section 01 4000 - Quality Requirements, for additional requirements.B. Provide manufacturer's field representative to inspect installation prior to startup.

3.04 SYSTEM STARTUPA. Provide manufacturer's field representative to perform system startup.B. Prepare and start equipment and system in accordance with manufacturer's instructions and

recommendations.C. Adjust equipment for proper operation within manufacturer's published tolerances.

3.05 CLEANINGA. Clean exposed components of dirt, finger marks, and other disfigurements.

3.06 CLOSEOUT ACTIVITIESA. Demonstrate proper operation of equipment to Owner's designated representative.B. Demonstration: Demonstrate operation of system to Owner's personnel.

1. Use operation and maintenance data as reference during demonstration.2. Briefly describe function, operation, and maintenance of each component.

C. Training: Train Owner's personnel on operation and maintenance of system.1. Use operation and maintenance manual as training reference, supplemented with additional training

materials as required.2. Provide minimum of two hours of training.3. Location: At project site.

3.07 PROTECTIONA. Protect installed components from subsequent construction operations.B. Replace exposed components broken or otherwise damaged beyond repair.

END OF SECTION

27 1005 - 1216026 / IPERS FY17 Project STRUCTURED CABLING FOR VOICE AND DATA - INSIDE-PLANT

SECTION 27 1005STRUCTURED CABLING FOR VOICE AND DATA - INSIDE-PLANT


A. Communications system design requirements.B. Communications pathways.C. Copper cable and terminations.D. Communications identification.E. Cabling and pathways inside building(s).F. Distribution frames, cross-connection equipment, enclosures, and outlets.G. Grounding and bonding the telecommunications distribution system.

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 07 8400 - Firestopping.D. Section 26 0526 - Grounding and Bonding for Electrical Systems.E. Section 26 0534 - Conduit.F. Section 26 0537 - Boxes.G. Section 26 2726 - Wiring Devices.

1.03 REFERENCE STANDARDSA. EIA-310 - Cabinets, Racks, Panels, and Associated Equipment; Electronic Industries Association; Revision

D, 1992.B. NECA/BICSI 568 - Standard for Installing Building Telecommunications Cabling; National Electrical

Contractors Association; 2006. (ANSI/NECA/BICSI 568)C. NFPA 70 - National Electrical Code; Most Recent Edition Adopted by Authority Having Jurisdiction, Including

All Applicable Amendments and Supplements.D. TIA-568 (SET) - Commercial Building Telecommunications Cabling Standard Set; Telecommunications

Industry Association; 2015.E. TIA-606-B - Administration Standard for the Telecommunications Infrastructure; Telecommunications

Industry Association; Rev B, 2012.F. TIA-607-B - Generic Telecommunications Bonding and Grounding (Earthing) for Customer Premises;

Telecommunications Industry Association; Rev B, 2012 (with Addenda; 2013).G. ANSI/J-STD-607 - Commercial Building Grounding (Earthing) and Bonding Requirements for

Telecommunications; Rev A, 2002.H. UL 444 - Communications Cables; Current Edition, Including All Revisions.I. UL 1581 - Reference Standard for Electrical Wires, Cables, and Flexible Cords; Current Edition, Including All

Revisions.J. UL 1863 - Communications-Circuit Accessories; Current Edition, Including All Revisions.

1.04 ADMINISTRATIVE REQUIREMENTSA. Coordination:

1. Coordinate the work with other trades to avoid placement of other utilities or obstructions within thespaces dedicated for communications equipment.

2. Coordinate arrangement of communications equipment with the dimensions and clearancerequirements of the actual equipment to be installed.

3. Notify Engineer of any conflicts with or deviations from the contract documents. Obtain direction beforeproceeding with work.

1.05 GENERAL SUMMARYA. The Electrical Contractor shall be responsible for providing conduits, boxes, and wiring pathways to

accommodate the work in this section.


B. A complete Structured Cabling System for the movement of LAN data traffic within the Owner's facilities shallbe provided, installed, tested, and labeled. Design must include a complete and functioning StructuredCabling System including cable routes, interconnect locations, distribution frame locations, building and floorlayouts and any other items associated with the implementation of the complete Structured Cabling Systemfor new outlet locations indicated on the drawings.

C. The Bidder must identify the manufacturer of any and all equipment included in the equal system proposal.This identification must include address, telephone number and contact person. This identification must alsoinclude part numbers, descriptions, submittals, quantities and itemized prices.

D. All equipment and material shall be new and of the highest quality and reliability.E. Upon completion of the Structured Cabling System testing, the Awarded Bidder will provide the Owner with a

complete record of all testing performed on CD-ROM disc, including any proprietary reading software. TheOwner reserves the right to randomly test any cabling, both passive and active. If problems are discovered, itis the responsibility of the Awarded Bidder to make corrections in the time frames outlined within the contractdocuments.

F. It is the responsibility of the Bidder to calculate all actual copper and fiber cable footage required.1.06 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide manufacturer's standard catalog pages and data sheets for each product.

1. Storage and handling requirements and recommendations.2. Installation methods.

C. Shop Drawings: Show compliance with requirements on isometric schematic diagram of network layout,showing cable routings, telecommunication closets, rack and enclosure layouts and locations, serviceentrance, and grounding.

D. Manufacturer Qualifications.E. Evidence of qualifications for installer.F. Test Plan: Complete and detailed plan, with list of test equipment, procedures for inspection and testing, and

intended test date; submit at least 60 days prior to intended test date.G. Field Test Reports.H. Project Record Documents:

1. Record actual locations of outlet boxes and distribution frames.2. Identify distribution frames and equipment rooms by room number on contract drawings.

1.07 QUALITY ASSURANCEA. Manufacturer Qualifications: At least 3 years experience manufacturing products of the type specified.B. Installer Qualifications: A company having at least 3 years experience in the installation and testing of the

type of system specified, and:1. Supervisors and installers factory certified by manufacturers of products to be installed.2. Employing experienced technicians for all work; show at least 3 years experience in the installation of

the type of system specified, with evidence from at least 2 projects that have been in use for at least 18months; submit project name, address, and written certification by user.

3. Testing shall be completed by a Level III or higher field tester.1.08 DELIVERY, STORAGE, AND HANDLING

A. Store products in manufacturer's unopened packaging until ready for installation.B. Keep stored products clean and dry.

1.09 WARRANTYA. See Section 01 7800 - Closeout Submittals, for additional warranty requirements.B. The Contractor shall warrant that all materials and equipment are new, in good working order, and free from

defects. All installed equipment must conform to the manufacturer's official published specifications. Thewarranty shall begin at the acceptance date. The Contractor shall agree to repair, adjust and/or replace (asdetermined by the Owner to be in its best interest) any defective equipment, materials or other parts of theStructured Cable System at the Contractor's sole cost. The Owner will incur no costs for service orreplacement of parts within the channel during the warranty.


C. The warranty for the Structured Cabling System shall begin at the acceptance date and remain in effect for aperiod of fifteen (15) years from that date. The Contractor shall agree to repair, adjust and/or replace (asdetermined by the Owner to be in its best interest) any defective equipment, materials or other parts of theStructured Cabling System at the Contractor's sole cost. The Owner will incur no costs for service orreplacement of parts within the channel during the warranty period of fifteen (15) years.

D. The warranty for the Cable Management and Pathways Products shall begin at the acceptance date andremain in effect for a period of ten (10) years from that date. The Contractor shall agree to repair, adjustand/or replace (as determined by the Owner to be in its best interest) any defective equipment, materials orother parts of the Cable Management and Pathways Products at the Contractor's sole cost. The Owner willincur no costs for service or replacement of parts within the channel during the warranty period of ten (10)years.

E. The Contractor must provide an Network Performance Solutions Warranty for a minimum of fifteen (15)years. The Network Performance Solutions Warranty must guarantee the electrical performance to meet orexceed the Category 6, Category 6A or Category 5e link and channel requirements as outlined in documentsANSI/TIA/EIA-568-B.1, B.2, B.3 and ISO/IEC 11801:2002. The warranty must include complete parts andlabor replacement of defective products. The manufacturer must warrant the products for a minimum offifteen (15) years. The system warranty must have provisions for replacing the contracting organization at nocost to the Owner should the contractor lose his status as an authorized installer or otherwise not fulfill hisobligation to the customer.

F. The Contractor shall warrant and supply evidence that the installation of materials and hardware will be madein strict compliance with all applicable provisions of the National Electric Code, the rules and regulations ofthe Federal Communications Commission, and state and/or local codes or ordinances that may apply.

G. The Contractor shall warrant that the Structured Cabling System will function as specified in the approvedmanufacturer's Technical Description Guide.

H. The Contractor shall warrant that the Structured Cabling System will accommodate traffic at the levelsspecified in all appropriate sections of this Request for Proposal. (ZERO BIT ERROR RATE WITHIN THECHANNEL, as defined by IEEE).


A. Cabling and Equipment:1. Ortronics: www.ortronics.com2. CommScope: www.commscope.com3. ADC TrueNet: www.adc.com4. Panduit: www.panduit.com5. Substitutions: See Section 01 6000 - Product Requirements.

2.02 SYSTEM DESIGNA. Provide a complete permanent system of cabling and pathways for voice and data communications,

including cables, conduits and wireways, pull wires, support structures, enclosures and cabinets, and outlets.1. Comply with TIA-568 (cabling) and TIA-569 (pathways), latest editions (commercial standards).2. Provide fixed cables and pathways that comply with NFPA 70 and TIA-607 and are UL listed or third

party independent testing laboratory certified.3. Provide connection devices that are rated for operation under conditions of 32 to 140 degrees F at

relative humidity of 0 to 95 percent, noncondensing.4. In this project, the term plenum is defined as return air spaces above ceilings, inside ducts, under raised

floors, and other air-handling spaces.B. System Description:

1. Horizontal Cabling: Copper.2. Camera System: Provide data cabling to each new or relocated camera location as indicated on the

drawings.C. Main Distribution Frame (MDF): Centrally located support structure for terminating horizontal cables that

extend to telecommunications outlets, functioning as point of presence to external service provider.1. The MDF is existing. Provide new patch panels as required to accomodate new devices.

D. Cabling to Outlets: Specified horizontal cabling, wired in star topology to distribution frame located at centerhub of star; also referred to as "links".


2.03 PATHWAYSA. Conduit: As specified in Section 26 0534 and as shown on the drawings. Minimum size is 1".

2.04 COPPER CABLE AND TERMINATIONSA. Copper Horizontal Cable for Data: TIA/EIA-568 Category 6 solid conductor unshielded twisted pair (UTP), 24

AWG, 100 ohm; 4 individually twisted pairs; covered with blue jacket and complying with all relevant parts ofand addenda to latest edition of TIA/EIA-568 and UL 444.1. Provide NFPA 70 type CMP plenum-rated cable.2. Testing: Furnish factory reel tests.

B. Cables shall incorporate an oblique elliptical offset filler to minimize alien crosstalk.C. Cables shall be manufactured to with lead-free materials.D. Copper Cable Terminations: Insulation displacement connection (IDC) type using appropriate tool; use

screw connections only where specifically indicated.2.05 JACKS

A. CAT 6 Jacks:1. Meet or exceed TIA/EIA 568-B.2 Category 6 requirements.2. Individual units to allow for maximum flexibility.3. Impedance matched for maximum throughput.4. IDC contacts must be silver-plated.5. Color shall be:

a. Blue for Data.6. Jacks shall be terminated using a 110-style wire termination tool.7. Must be universal T568B wiring.

2.06 FACEPLATESA. Constructed of durable ABS plastic, which meets UL 1863 safety rating and UL 94V-0 rating.B. Available in a variety of port sizes: 2-, 4-, 6-, 8-, & 12-port configurations. Provide blank dust covers on

unused opeings.C. Faceplates color shall be white.D. Labels:

1. Comply with TIA/EIA-606 using encoded identifiers; label each jack on the face plate as to its functionwith a unique numerical identifier.

2.07 IDENTIFICATION PRODUCTSA. Comply with TIA-606.

2.08 CROSS-CONNECTION EQUIPMENTA. Patch Panels for Copper Cabling: Sized to fit EIA standard 19 inch wide equipment racks; 0.09 inch thick

aluminum; cabling terminated on Type 110 insulation displacement connectors; printed circuit boardinterface.1. Jacks: Non-keyed RJ-45, suitable for and complying with same standard as cable to be terminated;

maximum 48 ports per standard width panel.2. Capacity: Provide ports sufficient for cables to be terminated plus 25 percent spare.3. Labels: Factory installed laminated plastic nameplates above each port, numbered consecutively;

comply with TIA/EIA-606 using encoded identifiers.4. Provide incoming cable strain relief and routing guides on back of panel.5. Patch Cords: Provide one patch cord for each terminated patch panel port plus 10% spares.

2.09 ENCLOSURESA. Equipment Racks and Cabinets: CEA-310 standard 19 inch wide component racks.

1. Racks for MDF are existing.B. Outlet Boxes: For flush mounting in walls; depth as required to accommodate cable manufacturer's

recommended minimum conductor bend radius.1. Size, Unless Otherwise Indicated: 4 inches square by 2-1/8 inches deep.2. Wall Plates: Material and finish to match wiring device and wall plate finishes specified in Section 26

2726, complying with system design standards and UL 514C.


3. Labels: Comply with TIA/EIA-606 using encoded identifiers; label each jack on the face plate as to itsfunction with a unique numerical identifier.

PART 3 EXECUTION3.01 INSTALLATION - GENERAL

A. Comply with latest editions and addenda of TIA-568 (cabling), TIA-569 (pathways), TIA-607 (grounding andbonding), NECA/BICSI 568, NFPA 70, and SYSTEM DESIGN as specified in PART 2.

B. Comply with Communication Service Provider requirements.C. Grounding and Bonding: Perform in accordance with TIA-607 and NFPA 70.D. Install structured cabling system wiring in continuous conduit/raceway system in exposed locations of

locations subject to damage. Plenum rated cable may be used without conduit in concealed but accessiblelocations. Properly support cables from structure with J-Hooks or similar support.

E. During the installation process, the Awarded Bidder shall:1. Submit weekly progress reports pertaining to all aspects of the installation program.2. Meet with Owner's personnel on a weekly basis (OR AS NEEDED) to discuss the progress of the

installation.3. The Awarded Bidder shall provide an outline of recommended system administration documentation

and how this documentation shall be kept accurate.3.02 INSTALLATION OF PATHWAYS

A. Install pathways with the following minimum clearances:1. 48 inches from motors, generators, frequency converters, transformers, x-ray equipment, and

uninterruptible power systems.2. 12 inches from power conduits and cables and panelboards.3. 5 inches from fluorescent and high frequency lighting fixtures.4. 6 inches from flues, hot water pipes, and steam pipes.

B. Conduit:1. Do not install more than 2 (two) 90 degree bends in a single horizontal cable run.2. Leave pull cords in place where cables are not initially installed.3. Conceal conduit under floor slabs and within finished walls, ceilings, and floors except where specifically

indicated to be exposed.a. Conduit may remain exposed to view in mechanical rooms, electrical rooms, and

telecommunications rooms.b. Treat conduit in crawl spaces and under floor slabs as if exposed to view.c. Where exposed to view, install parallel with or at right angles to ceilings, walls, and structural

members.d. Under floor slabs, locate conduit at 12 inches, minimum, below vapor retarder; seal penetrations of

vapor retarder around conduit.C. Outlet Boxes:

1. Coordinate locations of outlet boxes provided under Section 26 0537 as required for installation oftelecommunications outlets provided under this section.a. Orient outlet boxes for vertical installation of wiring devices unless otherwise indicated.b. Provide minimum of 24 inches horizontal separation between flush mounted outlet boxes installed

on opposite sides of fire rated walls.c. Unless otherwise indicated, provide separate outlet boxes for line voltage and low voltage devices.d. Locate outlet boxes so that wall plate does not span different building finishes.e. Locate outlet boxes so that wall plate does not cross masonry joints.

D. Grounding and Bonding: Perform in accordance with ANSI/J-STD-607 and NFPA 70.E. Firestopping: Seal openings around pathway penetrations through fire-rated walls, partitions, floors, and

ceilings in accordance with Section 07 8400.3.03 INSTALLATION OF EQUIPMENT AND CABLING

A. Cabling: 1. Do not bend cable at radius less than manufacturer's recommended bend radius; for unshielded twisted

pair use bend radius of not less than 4 times cable diameter.2. Do not over-cinch or crush cables.3. Do not exceed manufacturer's recommended cable pull tension.


4. When installing in conduit, use only lubricants approved by cable manufacturer and do not chafe ordamage outer jacket.

B. Service Loops (Slack or Excess Length): Provide the following minimum extra length of cable, looped neatly:1. At Distribution Frames: 60 inches.2. At Outlets - Copper: 12 inches.

C. Copper Cabling:1. Category 5e and Above: Maintain cable geometry; do not untwist more than 1/2 inch from point of

termination.2. For 4-pair cables in conduit, do not exceed 25 pounds pull tension.3. Use T568B wiring configuration.4. Copper Cabling Not in Conduit: Use only type CMP plenum-rated cable as specified.

D. Identification:1. Use wire and cable markers to identify cables at each end.

E. Field-Installed Labels: Comply with TIA/EIA-606 using encoded identifiers.1. Cables: Install color coded labels on both ends.2. Outlets: Label each jack on its face plate as to its type and function, with a unique numerical identifier.3. Patch Panels: Label each jack as to its type and function, with a unique numerical identifier.

3.04 FIELD QUALITY CONTROLA. See Section 01 4000 - Quality Requirements, for additional requirements.B. Comply with inspection and testing requirements of specified installation standards.C. Visual Inspection:

1. Inspect cable jackets for certification markings.2. Inspect cable terminations for color coded labels of proper type.3. Inspect outlet plates and patch panels for complete labels.4. Inspect patch cords for complete labels.

D. Testing - Copper Cabling and Associated Equipment:1. Test operation of shorting bars in connection blocks.2. Category 5e and Above Links: Perform tests for wire map, length, attenuation, NEXT, and propagation

delay.3. Submit test results with Operation and Maintenance Manuals.

E. Final Testing: After all work is complete, including installation of telecommunications outlets, and telephonedial tone service is active, test each voice jack for dial tone.

3.05 DOCUMENTATIONA. Prior to System acceptance, the Awarded Bidder shall submit the following to the Owner:

1. Two (2) complete sets of system manuals in paper and soft (Microsoft Word or PDF) files includinginstallation, operation and maintenance procedures. The Awarded Bidder agrees to update thesemanuals as updates are published and shall grant the Owner permission to copy any or all portions ofthese documents for internal use.

2. Fully documented drawings in paper and soft (AutoCAD and PDF) files of the entire distribution systemincluding building and floor layouts, distribution frames, cable routes, interconnect locations, maindistribution frame location, riser locations and all other information pertinent to the installation.

3. After installation is complete, drawings must be updated to reflect any as-built modifications.3.06 REJECTED WORK

A. The Owner reserves the following rights to itself or its designated representatives.1. To inspect all work performed.2. To designate patch panel locations.3. To stop work in progress that does not conform to industry standards.

B. The Contractor shall promptly remove from the premises any equipment rejected by the Owner for failure tocomply with the contract documents. The Contractor shall promptly replace any rejected equipment inaccordance with the contract documents and without further expense to the Owner.


C. If the Contractor does not take action to remove and replace all rejected equipment within ten (10) days afterreceipt of written notice, the Owner reserves the right to remove and replace such work at the AwardedBidders expense. The Contractor shall be responsible for shipping, handling, and storage expense of saidmaterials.

END OF SECTION

28 1600 - 1216026 / IPERS FY17 Project INTRUSION DETECTION

SECTION 28 1600INTRUSION DETECTION


A. Intrusion detection system requirements.B. Initiating devices.

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 07 8400 - Firestopping.D. Section 26 0526 - Grounding and Bonding for Electrical Systems - .E. Section 26 0534 - Conduit.F. Section 26 0553 - Identification for Electrical Systems: Identification products and requirements.

1.03 REFERENCE STANDARDSA. NECA 1 - Standard for Good Workmanship in Electrical Construction; National Electrical Contractors

Association; 2010.B. NFPA 70 - National Electrical Code; National Fire Protection Association; Most Recent Edition Adopted by

Authority Having Jurisdiction, Including All Applicable Amendments and Supplements.C. UL 639 - Intrusion-Detection Units; Current Edition, Including All Revisions.

1.04 ADMINISTRATIVE REQUIREMENTSA. Coordination:

1. Coordinate compatibility of devices for the installed locations with work provided under other sections orby others.

2. Coordinate the placement of sensors and keypads with millwork, furniture, equipment, etc. installedunder other sections or by others.


1.05 SUBMITTALSA. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Product Data: Provide manufacturer's standard catalog pages and data sheets for each system component.

Include ratings, configurations, standard wiring diagrams, dimensions, finishes, service conditionrequirements, and installed features.

C. Project Record Documents: Record actual locations of system components and installed wiringarrangements and routing.

1.06 QUALITY ASSURANCEA. Conform to requirements of NFPA 70.

1.07 DELIVERY, STORAGE, AND HANDLINGA. Receive, inspect, handle, and store products in accordance with manufacturer's instructions.B. Store products in manufacturer's unopened packaging, keep dry and protect from damage until ready for

installation.1.08 WARRANTY

A. See Section 01 7800 - Closeout Submittals, for additional warranty requirements.B. Provide minimum two year manufacturer warranty covering repair or replacement due to defective materials

or workmanship.PART 2 PRODUCTS2.01 INTRUSION DETECTION SYSTEM REQUIREMENTS

A. Provide modifications and extensions to existing intrusion detection system consisting of all requiredequipment, conduit, boxes, wiring, connectors, hardware, supports, accessories, software, systemprogramming, etc. as necessary for a complete operating system that provides the functional intent indicated.


B. Alarm Control Unit: Existing control panel located as shown on drawings.C. Initiating Device Requirements:

1. Provide glass break detectors to monitor:a. Designated perimeter windows.

D. Provide products listed, classified, and labeled as suitable for the purpose intended.E. Electromagnetic Interference/Radio Frequency Interference (EMI/RFI) Limits: Comply with FCC

requirements of 47 CFR 15, for Class B, consumer application.2.02 INITIATING DEVICES

A. Manufacturers: Same as manufacturer of alarm control units where possible.B. General Requirements:

1. Provide devices suitable for intended application and location to be installed.C. Glass Break Detectors:

1. Listed and labeled as complying with UL 639.2. Suitable for the glass type to be monitored.3. Accurately discriminates false alarms from true glass break events.4. Furnished with selectable sensitivity.5. Match devices in existing system.


A. Verify that field measurements are as shown on the drawings.B. Verify that ratings and configurations of system components are consistent with the indicated requirements.C. Verify that mounting surfaces are ready to receive system components.D. Verify that branch circuit wiring installation is completed, tested, and ready for connection to system.E. Verify that conditions are satisfactory for installation prior to starting work.

3.02 INSTALLATIONA. Perform work in a neat and workmanlike manner in accordance with NECA 1.B. Install products in accordance with manufacturer's instructions.C. Wiring Method: Unless otherwise indicated, use cables (not in conduit).

1. Use listed plenum rated cables in spaces used for environmental air.2. Install wiring in conduit where required for rough-in, where required by authority having jurisdiction, and

where exposed to damage.3. Conduit: Comply with Section 26 0534.4. Conceal all cables unless specifically indicated to be exposed.5. Route exposed cables parallel or perpendicular to building structural members and surfaces.

D. Provide grounding and bonding in accordance with Section 26 0526.E. Install firestopping to preserve fire resistance rating of partitions and other elements, using materials and

methods specified in Section 07 8400.F. Identify system wiring and components in accordance with Section 26 0553.

3.03 FIELD QUALITY CONTROLA. See Section 01 4000 - Quality Requirements, for additional requirements.B. Prepare and start system in accordance with manufacturer's instructions.C. Inspection and testing to include, at a minimum:

1. Test each initiating device for proper response by alarm control unit.a. Test glass break detectors using only manufacturer's recommended glass break simulation test

units.2. Test for proper operation of output relays.

D. Correct defective work, adjust for proper operation, and retest until entire system complies with contractdocuments.

3.04 ADJUSTINGA. Program system parameters according to requirements of Owner.


3.05 CLEANINGA. Clean exposed surfaces to remove dirt, paint, or other foreign material and restore to match original factory

finish.3.06 CLOSEOUT ACTIVITIES

A. Demonstration: Demonstrate proper operation of system to Owner, and correct deficiencies or makeadjustments as directed.

3.07 PROTECTIONA. Protect installed system components from subsequent construction operations.

END OF SECTION

28 2100 - 1216026 / IPERS FY17 Project UNIFIED SECURITY SYSTEM

SECTION 28 2100UNIFIED SECURITY SYSTEM


A. Video surveillance system requirements.B. Video recording and viewing equipment.C. Cameras.D. Camera Assemblies (camera, lens, housing, mount, etc.)E. Access control system requirements.F. Card readersG. CardsH. Door monitoring switchesI. Hardware/softwareJ. Wiring

1.02 RELATED REQUIREMENTSA. Division 00 - Procurement and Contracting RequirementsB. Division 01 - General RequirementsC. Section 26 0526 - Grounding and Bonding for Electrical Systems.D. Section 26 0529 - Hangers and Supports for Electrical Systems.E. Section 26 0534 - Conduit.F. Section 26 0553 - Identification for Electrical Systems: Identification products and requirements.G. Section 27 1005 - Structured Cabling for Voice and Data - Inside-Plant: Data cables for IP video surveillance

system network connections.1.03 REFERENCE STANDARDS

A. NECA 1 - Standard for Good Workmanship in Electrical Construction; National Electrical ContractorsAssociation; 2010.

B. NECA 303 - Standard for Installing Closed-Circuit Television (CCTV) Systems; National ElectricalContractors Association; 2005.

C. NFPA 70 - National Electrical Code; National Fire Protection Association; Most Recent Edition Adopted byAuthority Having Jurisdiction, Including All Applicable Amendments and Supplements.

D. NFPA 101 - Life Safety Code; 2012.E. UL 294 - Access Control System Units; Current Edition, Including All Revisions.

1.04 SYSTEM DESCRIPTIONA. Description: Provide unified security system for video surveillance system and access control system for

devices as indicated on drawings.B. Design Requirements

1. Contractor Designa. The Project Drawings represent the level of system design to be provided. Contractor shall provide

all additional system design work required, including:1) Conduit layout and sizing.2) Wire and cable layout and sizing.3) Point-to-point wiring and equipment hook-up information.4) Equipment mounting details.5) Design of equipment cabinets.6) Other detailed design work required.

C. Miscellaneous1. Provide of wire, cable, conduit, connectors and junction boxes required for system operation.2. Provide complete testing of all wiring and cables prior to connecting to any equipment or power.


3. Provide complete “as-built” documentation of all security systems, including documentation of existingequipment, wiring, conduits, and raceways.

D. Performance Requirements1. The video signal from all of the cameras to the monitor(s) shall be of sufficient strength to produce a

1-volt peak-to-peak signal at the monitor(s).1.05 ADMINISTRATIVE REQUIREMENTS

A. Coordination:1. Coordinate the placement of cameras with structural members, ductwork, piping, equipment,

luminaires, diffusers, fire suppression system components, and other potential conflicts installed underother sections or by others.

2. Coordinate the work with other installers to provide power for cameras and equipment at requiredlocations.


B. Preinstallation Meetings:1. Conduct meeting with facility representative to review camera and equipment locations and camera field

of view objectives.2. Conduct meeting with facility representative and other related equipment manufacturers to discuss

video surveillance system interface requirements.1.06 SUBMITTALS

A. See Section 01 3000 - Administrative Requirements, for submittal procedures.B. Shop Drawing Documents: Submit all information required fully functioning system, including but not limited

to floor plans, riser diagrams, and description of operation:1. Manufacturer's detailed data sheet for each component, including wiring diagrams, installation

instructions, circuit length limitations, electrical characteristics, and connection requirements for eachcomponent.

2. System zone boundaries and interfaces to other systems.3. Location of all components, circuits, and raceways; mark components with identifiers used in control

unit programming.4. Circuit layouts; number, size, and type of raceways and conductors; conduit fill calculations; spare

capacity calculations; video circuit calculations.5. Description of power supplies; if secondary power is by battery include calculations demonstrating

adequate battery power.C. Project Record Documents: Record actual locations of cameras and equipment including but not limited to:

1. Equipment and devices.2. Conduit and raceways.3. Junction box, splice box, and pull box locations.4. End-of-line resistors or remote relay locations.5. Interfaces to external equipment.6. Connections to power, telephone, network or other communications circuits.7. Routing of cable runs, zone numbers, tamper circuit configuration, panel/circuit breaker numbers from

which equipment is powered, and splice points.8. Upon completion of Work, and prior to Final Acceptance, Contractor shall prepare and submit a final

record set of Project Record Drawings. This set shall consist of all data transferred from the workingset, supplemented by Riser Diagrams and other information.

D. Maintenance contracts.E. Operation Data: Instructions for starting and operating system. System Documentation shall include a

complete collection of all installation, programming, operation, and maintenance manuals and work sheetsrelating to the equipment provided.

F. Maintenance Data: Routine trouble shooting procedures and equipment provider contact informationprovided with closeout submittals.

G. Closeout submittals1. Provide a set of as-built drawings and manuals including:

a. As-Built Drawingsb. Mounting Details


c. Product Datad. Installation Manualse. Operating Manualsf. Maintenance/Service Manuals

2. Provide all programming sheets, keys to the equipment cabinets, as-built drawings, operating manuals,maintenance/repair manuals, spare fuses, all programming sheets and keys to the equipment cabinets,tools for tamper-resistant enclosures and tools for manual resetting devices.

1.07 QUALITY ASSURANCEA. Comply with the following:

1. NFPA 702. Applicable TIA/EIA standards.

B. Conform to requirements of NFPA 70.C. Manufacturer Qualifications: Company specializing in manufacturing the products specified in this section

with minimum five years documented experience and with service facilities within 100 miles of Project.D. Supplier Qualifications: Authorized distributor of specified manufacturer with minimum three years

documented experience.E. Installer Qualifications: Authorized installer of specified manufacturer with service facilities within 100 miles

of Project.1. Installer shall employ a competent Foreman to be in responsible charge of the Work. Foreman shall be

on the project site daily during the execution of the Work.2. Installer's Foreman shall be a regular employee, principle, or officer of Installer, who is thoroughly

experienced in projects of a similar size and type. Installer shall not use contract employees orSubcontractors as Foremen.

3. All electronic systems Work shall be performed by electronic technicians thoroughly trained in theinstallation and service of specialty low-voltage electronic systems.

4. Subject to compliance with the requirements of these specifications, the following installers arepre-qualified to submit on this project:a. Control Installations of Iowa; Des Moines, IA

5. Non pre-qualified installers who intend to submit pricing on the work specified in this section shallprovide qualifying information to the Architect 10 days prior to bid date and may be approved byaddendum up to 5 days prior to bid date. No consideration shall be given to bids from companies,which are not on the pre-qualified installer list.

F. Products: Furnish products listed and classified by Underwriters Laboratories Inc. as suitable for purposespecified and indicated.

1.08 DELIVERY, STORAGE, AND HANDLINGA. Delivery to Job Site: Contractor shall have total responsibility for safe and secure delivery of security

equipment and tools to the job site. Arrange deliveries of Products in accord with construction schedules toavoid conflict.

B. Storage and Protection: Owner is not responsible for the care, storage or security of any of the Contractor'stools or equipment.

1.09 WARRANTYA. Contractor warrants that all Work furnished (material and labor) under this Contract will be of good quality,

free from faults and defects, and in conformance with the Project Drawings and Specifications.B. Contractor shall provide parts and labor guarantee on all Work. Unless otherwise specified herein,

Contractor's guarantee shall be for a period of two (2) years from date of Acceptance, except where anyspecific guarantees from a supplier or equipment manufacturer extends for a longer time.

C. Contractor's guarantee shall cover all costs associated with troubleshooting, repair, and replacement ofdefective Work, including costs of labor, transportation, lodging, materials, and equipment.

D. Guarantee shall not cover any damage to material or equipment caused by accident, misuse, unauthorizedmodification or repair by Owner, or acts of god.

E. Contractor shall promptly respond to Owner's requests for service during the guarantee period. Contractorshall provide repair service as soon as reasonably possible upon request from Owner, but in no case shallservice response exceed 8 hours from time of request.


1.10 MAINTENANCE SERVICEA. Furnish service and maintenance of unified security system for one year from Date of Substantial

Completion.PART 2 PRODUCTS2.01 GENERAL

A. The Unified Security Platform (USP) shall be an enterprise class IP-enabled security and safety softwaresolution.1. Approved software:

a. GenetecB. The USP shall support the seamless unification of IP access control system (ACS), IP video management

system (VMS), and IP automatic license plate recognition system (ALPR) under a single platform. The USPuser interface (UI) applications shall present a unified security interface for the management, configuration,monitoring, and reporting of embedded ACS, VMS, and ALPR systems and associated edge devices.

C. Functionalities available with the USP shall include:1. Configuration of embedded systems, such as ACS, ALPR, and VMS systems.2. Live event monitoring.3. Live video monitoring and playback of archived video.4. Alarm management.5. Reporting, including creating custom report templates and incident reports.6. Federation for global monitoring, reporting, and alarm management of multiple remote and independent

ACS and/or VMS systems spread across multiple facilities and geographic areas.7. Global cardholder management across multiple facilities and geographic areas, each with their own

independent ACS system.8. Microsoft Active Directory integration for synchronizing USP user accounts and ACS cardholder

accounts.9. Intrusion device and panel integration (live monitoring, reporting, and arming/disarming).10. SIP Intercom device integration for bi-directional communication.11. Integration with third party systems and databases via plug-ins (access control, video analytics, point of

sale, and more).12. Dynamic graphical map viewing.13. Asset management system integration.

D. The USP shall be deployed in one or more of the following types of installations:1. Unified access, ALPR, video platform, and any combination thereof.2. Standalone access control, ALPR, or video platform.3. Unified access and video platform that federates multiple remote ACS and VMS.4. Standalone video platform that federates multiple independent remote VMS.5. Standalone access control that federates multiple independent remote ACS.

E. Licensing1. A single central license shall be applied centrally on the configuration server.2. There shall be no requirement to apply a license at every server computer or client workstation.3. Based on selected options, one or more embedded systems shall be enabled or disabled.

2.02 HARDWARE AND SOFTWARE REQUIREMENTSA. The USP and embedded systems (video, license plate recognition, access control) shall be designed to run

on a standard PC-based platform loaded with a Windows operating system. The preferred operating systemshall be coordinated with the Owner following the manufacturer supported operating systems.

B. The core client/server software shall be built in its entirety using the Microsoft .NET software framework andthe C# (C-Sharp) programming language.

C. The USP database server(s) shall be built on Microsoft’s SQL Server. The preferred SQL version shall becoordinated with the Owner and compatible with the USP.

D. The USP shall be compatible with virtual environments, including VMware and Microsoft Hyper-V.E. The USP shall use the latest user interface (UI) development and programming technologies such as

Microsoft WPF (Windows Presentation Foundation), the XAML markup language, and .NET softwareframework.


2.03 ARCHITECTUREA. Overview

1. The USP shall be based on a client/server model. The USP shall consist of a standard Server SoftwareModule (SSM) and Client Software Applications (CSA).

2. The USP shall be an IP-enabled solution. All communication between the SSM and CSA shall be basedon standard TCP/IP protocol and shall use TLS encryption with digital certificates to secure thecommunication channel.

3. The SSM shall be a Windows service that can be configured to start when the operating system isbooted and run in the background. The SSM shall automatically launch at computer startup, regarlessof whether or not a user is logged on the machine.

4. Users shall be able to deploy the SSM on a single server or across several servers for a distributedarchitecture. The USP shall not be restricted in the number of SSM deployed.

5. The USP shall support the concept of Federation whereby multiple independent ACS and VMSinstallations can be merged into a single large virtual system for centralized monitoring, reporting, andalarm management.

6. The USP shall protect against potential database server failure and continue to run through standardoff-the-shelf solutions.

7. The USP shall support one thousand instances of CSA connected at the same time. However, anunrestricted number of CSA can be installed at any time.

8. The USP shall support an unrestricted number of logs and historical transactions (events and alarms)with the maximum allowed being limited by the amount of hard disk space available.

9. The USP shall support uninterrupted video streaming. The CSA shall keep existing video connectionsactive in the event that an SSM (except Archiver) becomes unavailable.

B. Roles-Based Architecture1. The USP shall consist of a role-based architecture, with each SSM hosting one or more roles.2. Each role shall execute a specific set of tasks related to either the core system, automatic license plate

recognition (ALPR), video (VMS), or access control (ACS) functionalities, among many others.Installation shall be streamlined through the ability of the USP to allow administrators to:a. Deploy one or several SSM across the network prior to activating roles.b. Activate and deactivate roles as needed on each and every SSM.c. Centralize role configuration and management.d. Support remote configuration.e. Move roles over from one SSM to another.

3. Each role, where needed, shall have its own database to store events and role-specific configurationinformation.

4. Roles without databases, such as Federation, Active Directory, and Global Cardholder Management,shall support near real-time standby without any third party failover software being required.

C. Standard Roles1. Directory Role

a. The Directory Role shall manage the central database that contains all the system information andcomponent configuration of the USP.

b. The Directory Role shall authenticate users and give access to the USP based on predefined useraccess rights or privileges, and security partition settings.

c. The Directory Role shall support the configuration/management of the following componentscommon to the ACS, ALPR, and VMS sub-systems:1) Security Partitions, users and user groups.2) Areas.3) Zones, input/output (IO) linking rules, and custom output behavior.4) Alarms. Schedules, and scheduled tasks.5) Custom events.6) Macros or custom scripts.

d. The Directory Role shall support the configuration/management of the following componentsspecific to VMS:1) Video servers and their peripherals (e.g. audio, IOs, and serial ports).2) PTZ.3) Camera sequences.4) Recording and archiving schedules.


e. The Directory Role shall support the configuration/management of the following componentsspecific to ACS:1) Door controllers, and input and output (IO) modules.2) Doors, Elevators, and Access rules.3) Cardholders and cardholder groups, credentials, and badge templates.

f. The Directory Role shall support the configuration/management of the following componentsspecific to ALPR:1) ALPR units and cameras.2) Hotlists, permit lists, and overtime rules.

2. The Video Archiver Role shall be responsible for managing cameras and encoders under its control andarchiving video.

3. The Media Router Role shall be responsible for routing video and audio streams across local and widearea networks from the source (e.g. DVS) to the destination (e.g. CSA).

4. The Access Manager Role shall be responsible for synchronizing access control hardware units underits control, such as door controllers and IO modules. This role shall also be responsible for validatingand logging all access activities and events when the door controllers and IO modules are online.

5. The Automatic License Plate Recognition (ALPR) Role shall be responsible for synchronizing fixedALPR units (cameras) and mobile ALPR applications under its control. The ALPR Role shall also beresponsible for logging all ALPR activities and events.

6. The Zone Manager Role shall be responsible for managing all software zones (collection of inputs) andlogging associated zone events. Zones shall consist of inputs from both access control and videodevices.

7. The Health Monitoring Role shall be responsible for monitoring and logging health events and warningsfrom the various client applications, roles, and services that are part of the USP. This role shall also beresponsible for logging events within the Windows Event Log and for generating reports on healthstatistics and health history.

D. Optional Roles1. The Federation Role shall be responsible for creating a large virtual system consisting of hundreds or

thousands of independent and remote ACS and/or VMS systems.2. The Global Cardholder Synchronizer Role shall be responsible for synchronizing cardholder and

credential data between the local site and a central site. Synchronization between remote sites shallalso be supported.

3. The Active Directory Role shall be responsible for synchronizing user accounts and cardholder accountswith a Microsoft Active Directory server.

4. The Intrusion Manager Role shall be responsible for managing third party intrusion devices such asalarm panels and perimeter detection devices. This role shall also be responsible for logging allintrusion events in a database.

5. The Asset Manager Role shall be responsible for integrating and synchronizing with third party assetmanagement systems and for logging asset related events. This role shall also be responsible forsupporting the execution of asset-related reports such as inventory reports and asset activity reports.

6. The Plug-in Manager Role shall be responsible for the communication between the USP and third partysystems such as video analytics, access control and video systems, and building managementsystems.

7. The Point of Sale (POS) Manager Role shall be responsible for integrating the USP with third party POSsystems and for logging transactions.

8. The Web SDK Role shall be responsible for connecting the USP to any application or interfacedeveloped with the Web Service SDK. Applications developed with the Web Service SDK shall beplatform independent and rely on the REST protocol for communications.

9. The Communication Management Role shall be responsible for registering the SIP communicationendpoints and for managing the call routing.

10. The RTSP Role shall be responsible for connecting any video stream of the USP to a third party systemusing standard RTSP protocol.. This role shall provide access to live video.

E. Server Monitoring Service (Watchdog)1. The USP shall include a Server Monitoring Service that continuously monitors the state of the Server

Software Module (SSM) service.2. The Server Monitoring Service shall be a Windows service that automatically launches at system

startup, regardless of whether or not a user is logged on to his account.


3. The Server Monitoring Service shall be installed on all PCs/servers running an SSM. In the event of amalfunction or failure, the Server Monitoring Service shall restart the failed service. As a last resort, theServer Monitoring Service shall reboot the PC/server should it be unable to restart the service.

2.04 CLIENT SOFTWARE APPLICATIONS (CSA)A. Overview

1. The Client Software Applications (CSA) shall provide the user interface for USP configuration andmonitoring over any network and be accessible locally or from a remote connection.

2. The CSA shall consist of the Configuration UI for system configuration and the Monitoring UI formonitoring. The CSA shall be Windows-based and provide an easy-to-use graphical user interface (UI).

3. The Server Administrator shall be used to configure the server database(s). It shall be web-based andaccessible locally on the SSM or across the network.

4. The CSA shall seamlessly merge access control, automatic license plate recognition (ALPR), and videofunctionalities within the same user application.

5. The USP shall use the latest user interface (UI) development and programming technologies, such asMicrosoft WPF (Windows Presentation Foundation), the XAML markup language, and the .NETsoftware framework.

6. All applications shall provide an authentication mechanism, which verifies the validity of the user. Assuch, the administrator (who has all rights and privileges) can define specific access rights andprivileges for each user in the system.

7. Logging on to a CSA shall be done either through locally stored USP user accounts and passwords orusing the operator’s Windows credentials when Active Directory integration is enabled.

8. When integrated with Microsoft’s Active Directory, the CSA and USP shall authenticate users using theirWindows credentials. As a result, the USP will benefit from Active Directory password authenticationand strong security features.

9. The CSA shall support multiple languages, including but not limited to the following: English, French,Arabic, Czech, Dutch, German, Hebrew, Hungarian, Italian, Japanese, Korean, Norwegian, Persian(Farsi), Polish, Portuguese (Brazilian), Simplified and Traditional Chinese, Russian, Spanish, Swedish,Thai, Turkish and Vietnamese.

10. To enhance usability and operator efficiency, the Configuration UI and Monitoring UI shall support manyof the latest UI concepts, such asa. A customizable Home Page that includes favorite and recently used tasks.b. Task-oriented approach for administrator/operator activities where each type of activity

(surveillance, visitor management, individual reports, and more) is an operator task.c. Consolidated and consistent workflows for video, ALPR, and access control.d. Single click functionality for reporting and tracking. The Monitoring UI shall support both single-click

reporting for access control, ALPR, and video, as well as single-click tracking of areas, cameras,doors, zones, cardholders, elevators, ALPR entities, and more. Single-click reporting or trackingshall create a new task with the selected entities to report on or track.

11. Configuration UI and Monitoring UI Home Page and Tasksa. The Configuration UI and Monitoring UI shall be task-oriented.b. A task shall be user interface design patterns whose goal is to simplify the user interface by

grouping related features from different systems, such as video and access, in the same displaywindow. Features shall be grouped together in a task based on their shared ability to help the userperform a specific task.

c. Tasks shall be accessible via the Home Page of either the Configuration or the Surveillance CSA.d. Newly created tasks shall be accessible via the Configuration UI or the Monitoring UI taskbar.e. Similar tasks shall be grouped into the following categories:

1) Operation: Access control management, LRP management, and more.2) Investigation: Video bookmark/motion/archive reports, access control activity reports, visitor

activity reports, alarm reports, ALPR activity reports, and more.3) Maintenance: Access control and video configuration reports, troubleshooters, audit trails,

health-related reports, and more.f. An operator shall be able to launch a specific task only if he or she has the appropriate privileges.g. The Home Page content shall be customizable through the use of privileges to hide tasks that an

operator should not have access to and through a list of favorite and recently used tasks. Inaddition, editing a USP XML file to add new tasks on the fly shall also be possible.

B. Configuration User Interface (UI)


1. The Configuration UI application shall allow the administrator or users with appropriate privileges tochange the system configuration. The Configuration UI shall provide decentralized configuration andadministration of the USP system from anywhere on the IP network.

2. The configuration of all embedded ACS, VMS, and ALPR systems shall be accessible via theConfiguration UI.

3. The Configuration UI shall have a home page with single-click access to various tasks.4. The Configuration UI shall include a variety of tools such as troubleshooting utilities, import tools, and a

unit discover tool, and many more.5. The Configuration UI shall include a static reporting interface to:

a. View historical events based on entity activity. The user shall be able to perform such actions asprinting a report and troubleshooting a specific access event from the reporting view.

b. View audit trails that show a history of user/administrator changes to an entity.6. Common entities, such as users, schedules, alarms and many more, can be reused by all embedded

systems (ACS, VMS, and ALPR).C. Monitoring User Interface (UI)

1. The Monitoring UI shall fulfill the role of a Unified Security Interface that is able to monitor video, ALPR,and access control events and alarms, as well as view live and recorded video.

2. The Monitoring UI shall provide a graphical user interface to control and monitor the USP over any IPnetwork. It shall allow administrators and operators with appropriate privileges to monitor their unifiedsecurity platform, run reports, and manage alarms.

3. To enhance usability and operator efficiency, the Monitoring UI shall support the following UI concepts:a. Dynamically adaptive interface that adjusts in real-time to what the operator is doing.b. A dynamic dashboard loaded with entity-specific widgets (e.g. door and camera widgets).c. Use of transparent overlays that can display multiple types of data in a seamless fashion.d. Display tile menus and quick commands.e. Consolidated and consistent workflows.f. Tile menus and quick commands easily accessible within every display tile of the user workspace.g. Single click functionality for reporting and tracking. The Monitoring UI shall support both single-click

reporting for access control, ALPR, and video, as well as single-click tracking of areas, cameras,doors, zones, cardholders, elevators, ALPR entities, and more. Single-click reporting or trackingshall create a new task with the selected entities to report on or to track.

4. Monitoring UI Home Page and Tasksa. Similar tasks shall be grouped into the following categories:

1) Operation: Access control/LRP/video surveillance, visitor management, mustering, accesscontrol and video alarm monitoring, and more.

2) Investigation: Video bookmark/motion/archive reports, access control activity reports, visitoractivity reports, alarm reports, ALPR activity reports, and more.

3) Maintenance: Access control and video configuration reports, troubleshooters, audit trails, andmore.

5. Dynamically Adaptive UI, Dashboard, and Widgetsa. The Monitoring UI shall dynamically adapt to what the operator is doing. This shall be

accomplished through the concept of widgets that are grouped in the Monitoring UI dashboard.b. Widgets shall be mini-applications or mini-groupings in the Monitoring UI dashboard that let the

operator perform common tasks and provide the operator with fast access to information andactions.

c. With a single click on an entity (e.g. door or camera) the specific widgets associated to that entityappear and other non-relevant widgets disappear dynamically (instantly). Widgets shall bring theoperator information such as door status and camera stream information, as well as user actions,such as door unlock, PTZ controls, and more.

d. Specific widgets include those for a door, camera, alarm, zone, display tile, video stream(statistics), PTZ camera, and more.

6. Operator Workflowsa. A workflow shall be a sequence of operations an operator or administrator shall execute to

complete an activity. The “flow” relates to a clearly defined timeline or sequence for executing theactivity.

b. The Monitoring UI shall be equipped with consistent workflows for the ALPR, video, and accesscontrol systems that it unifies.


c. Generating or printing a report, setting up or acknowledging an alarm, or creating an incident reportshall follow the same process (workflow) whether the operator is working with video, ALPR, oraccess control, or with both video and access control.

7. Each task within the Monitoring UI shall consist of one or more of the following items:a. Event list.b. Logical tree. Doors, cameras, zones, ALPR units, and elevators shall be grouped under Areas in a

hierarchical fashion.c. Entities list of all entities being tracked.d. Display tiles with various patterns (1 x 1, 2 x 2, and more).e. Display tile menu with various commands related to cameras, doors, PTZ, and tile controls.f. Dashboard with widgets.

8. The Monitoring UI shall support multiple event lists and display tile patterns, including:a. Event/alarm list layout only.b. Display tile layout only.c. Display tile and alarm/event list combination.d. ALPR map and alarm/event list combination.

9. User workspace customizationa. The user shall have full control over the user workspace through a variety of user-selectable

customization options. Administrators shall also be able to limit what users and operators canmodify in their workspace through privileges.

b. Once customized, the user shall be able to save his or her workspace.c. The user workspace shall be accessible by a specific user from any client application on the

network.d. Display tile patterns shall be customizable.e. Event or alarm lists shall span anywhere from a portion of the screen up to the entire screen and

shall be resizable by the user. The length of event or alarm lists shall be user-defined. Scroll barsshall enable the user to navigate through lengthy lists of events and alarms.

f. The Monitoring UI shall support multiple display tile patterns (e.g. 1 display tile (1x1 matrix), 16 tiles(8x8 matrix), and multiple additional variations).

g. The Monitoring UI shall support as many monitors as the PC video adapters and WindowsOperating System are capable of accepting.

h. Additional customization options include: show/hide window panes, show/hide menus/toolbars,show/hide overlaid information on video, resize different window panes, and choice of tile displaypattern on a per task basis.

10. The Monitoring UI shall provide an interface to support the following tasks and activities common toaccess control, ALPR, and video:a. Monitoring the events from a live security system (ACS and/or VMS and/or ALPR).b. Generating reports, including custom reports.c. Monitoring and acknowledging alarms.d. Creating and editing incidents and generating incident reports.e. Displaying dynamic graphical maps and floor plans as well as executing actions from dynamic

graphical maps and floor plans.f. Management and execution of hot actions and macros.

11. The Monitoring UI shall be able to monitor the activity of the following entities in real-time: areas, ALPRentities, doors, elevators, cameras, cardholders, cardholder groups, zones (input points), and more.The Monitoring UI shall provide an interface to support the following access control tasks andcapabilities:a. Monitoring and management of access events and alarms.b. Viewing of cardholder picture or badge IDs.c. Verification of cardholder picture IDs against live video.d. Visitor management.e. People counting or mustering, including resetting the people count in an areaf. Door control, including remotely unlocking doors, overriding a door’s unlocking schedules, and

enabling door maintenance mode.g. Forgiving antipassback.h. Generation of ACS configuration and activity reports.i. Viewing of HTML files including alarm instructions.

12. The Monitoring UI shall include advanced video capabilities, including:a. Advanced live video viewing functionality.


b. Advanced archive playing and video playback functionality.c. Monitoring and management of video system events and alarms.d. Intercom or duplex audio.e. Generation of video reports.f. Control of PTZ cameras.g. Creating and Monitoring archive transfer requests.h. Display metadata overlayaid on live or playback video.

13. The Monitoring UI shall leverage the Graphical Processing Unit (GPU) for video decoding.a. The following GPU technologies shall be supported:

1) NVidia CUDA.2) Intek Quck Sync.

b. The Monitoring UI shall have the ability to decode video through the the optimal simultaneous useof the GPU and Computer Processing Unit (CPU).

14. The live video viewing capabilities of the Monitoring UI shall include:a. The ability to display all cameras attached to the USP and all cameras attached to federated

systems.b. Support for live video monitoring on each and every display tile within a task in the user’s

workspace.c. The USP shall support uninterrupted video streaming. The CSA shall keep existing video

connections active in the event that an SSM (except Archiver) becomes unavailable.d. The ability to drag and drop a camera into a display tile for live viewing.e. The ability to drag and drop a camera into a display tile for live viewing on an analog monitor

connected to an IP hardware decoder (converting an IP encoded stream into an analog videosignal).

f. The ability to drag and drop a camera from a map into a display tile for live viewing.g. Support for digital zoom on live camera video streams.h. The ability for audio communication with video units with audio input and output.i. The ability to control pan-tilt-zoom, iris, focus, and presets.j. The ability to bookmark important events for later retrieval on any archiving camera and to uniquely

name each bookmark in order to facilitate future searches.k. The ability to start/stop recording on any camera in the system that is configured to allow manual

recording by clicking on a single button.l. The ability to activate or de-activate viewing of all system events as they occur.m. The ability to switch to instant replay of the video for any archiving camera with the simple click of

button.n. The ability to take snapshots of live video and be able to save or print the snapshots.o. The ability to view the same camera multiple times in different tiles.

15. The video playback (archive playing) capabilities of the Monitoring UI shall include:a. Support for audio and video playback for any time span.b. Support for video playback on each and every display tile.c. The ability to instantly replay the video for any archiving camera with the simple click of a button.d. The ability to select between instant synch of all video streams in playback mode, allowing

operators to view events from multiple angles or across several camera fields, or non-synchronousplayback.

e. The ability to simultaneously view the same camera in multiple tiles at different time intervals.f. The ability to control playback with:

1) Pause.2) Lock Speed.3) Forward and Reverse Playback at: 1x, 2x, 4x, 6x, 8x, 10x, 20x, 40x, 100x.4) Forward and Reverse Playback frame by frame.5) Slow Forward and Reverse Playback at: 1/8x, 1/4x, 1/3x, 1/2x.6) Loop playback between two time markers.

g. The ability to display a single timeline or one timeline for each selected video stream, which wouldallow the operator to navigate through the video sequence by simply clicking on any point in thetimeline.

h. The ability to display the level of motion at any point on a timeline.i. The ability to clearly display bookmarked events on the timeline(s).j. The ability to query archived video using various search criteria, including, but not limited to, time,

date, camera, and area.


k. The tool necessary for searching video and associated audio based on user-defined events ormotion parameters.

l. The ability to define an area of the video field in which to search for motion as well as define theamount of motion that will trigger search results. The Monitoring UI shall then retrieve all archivedvideo streams that contain motion that meets the search parameters. There shall be a graphicaltimeline on which the time of each search hit shall be indicated.

m. The ability to browse through a list of all bookmarks created on the system and select anybookmarked event for viewing.

n. The ability to add bookmarks to previously archived video for easier searching and retrieval.o. Support for digital zoom on playback video streams.p. Still image export to PNG, JPEG, GIF, and BMP format with Date and Time stamp, and Camera

Name on the image (snapshot).q. Tools for exporting video and a self-contained video player on various media such as USB keys or

CD/DVD-ROM. This video player shall be easy to use without training and shall still supportreviewing video metadata, such as bookmark, or navigating the video with functions like panoramiccamera view dewarping.

r. Tools for exporting video sequences in standard video formats, such as ASF.s. The ability to encrypt exported video files.t. The ability for an operator to load previously exported video files from their computer or network.u. The ability for queries to be saved upon closing the CSA and reappear when the application is

reopened.v. The ability to dynamically block, on demand, video stream dynamically to lower level users to

prevent access, for a specific time, to live and recorded video.w. A tool for building and exporting a set of videos into a single container. This tool shall allow the

operator to build sequences of video to create a storyboard and allow the export of synchronouscameras.

x. The ability to store the video export and still image export at a pre-defined storage location.y. An interface with the ability to list, search, and manipulate previously generated video exports.

16. The Monitoring UI shall provide an interface to support the following ALPR tasks and capabilities:a. Monitoring and management of ALPR events and alarms.b. Viewing of license plate picture(s) and context images.c. Viewing of license plate data (e.g. license plate reads).d. Verification of ALPR data against live and recorded video.

17. Trackinga. The USP shall permit the user to select multiple entities to monitor from the Monitoring UI by

adding the entities one by one to the tracking list.b. The Monitoring UI shall provide the option to filter which events shall be displayed in the display tile

layout and/or event list layout.c. It shall be possible to lock a Monitoring UI display tile so that it only tracks the activity of a specific

entity (e.g. a specific door or camera).d. The user shall be able to drag and drop an event from an event list (or an alarm from an alarm list)

onto a display tile to view a license plate read, cardholder picture ID, badge ID, or live/archivedvideo, among other options.

e. Event, alarm, monitoring/tracking, and report lists shall contain cardholder pictures whereapplicable.

f. The user shall be permitted to start or pause the viewing of events within each display tile.18. Display Tile Packing and Unpacking

a. The Monitoring UI shall support single-click unpacking and packing for ALPR hits, ALPR reads,areas, doors, zones, camera sequences, and alarms.

b. The packing and unpacking of entities shall allow operators to quickly obtain additional informationand camera views of a specific entity.

c. The unpacking of an entity shall display associated entities. For example, unpacking a door withmultiple associated cameras shall display all cameras associated with that door. Unpacking shallreconfigure the display tiles to be able to display all associated entities. For example, unpacking adoor (or a zone or alarm) that is currently in a 1 x 1 tile configuration and that has 3 cameras tied toit will create a 1 x 3 display tile arrangement for viewing all associated entities.

d. Packing will return the display to the original tile pattern.19. Visual Tracking


a. The Monitoring UI shall support the ability to manually track a moving target with the single click ofa button.

b. The ability to switch from one camera view to an adjacent camera shall be done within a singledisplay tile.

c. Switching between camera streams shall be accomplished by simply clicking on asemi-transparent shape or overlay.

d. Visual tracking shall be available with both live and recorded video.20. The following additional tools or utilities shall be available from the Monitoring UI: create credentials,

create cardholders, and access control troubleshooter.D. Server Administrator

1. The Server Administrator shall be used to configure the SSM and the Directory Role (mainconfiguration) and its database(s), to apply the license, and more.

2. The Server Administrator shall be a web-based application. Through the Server Administrator, it shallbe possible to access the SSM across the network or locally on the server.

3. Access to the Server Administrator shall be protected via login name, password, and encryptedcommunications.

4. The Server Administrator shall allow the administrator (user) to perform the following functions:a. Manage the system license.b. Configure the database(s) and database server for the Directory Role.c. Activate/Deactivate the Directory Role.d. Manually back up the Directory Role database(s) and/or restore the server database(s), as well as

configure scheduled backups of the databases.e. Define the client-to-server communications security settings.f. Configure the network communications hardware, including connection addresses and ports.g. Configure system SMTP settings (mail server and port).h. Configure event and alarm history storage options.

E. Unified Web Client (UWC)1. The UPS shall support a unified web client (UWC) for access control and video.2. The UWC shall be a truly thin client with no download required other than an internet web browser or

standard web browser plugins.3. The UWC shall be platform independent and run within Microsoft Internet Explorer, Firefox, Safari, and

Google Chrome.4. Web pages for the web client shall be managed and pushed by the Mobile Server. Microsoft IIS or any

other web hosting service shall not be required given that all the web pages shall be hosted by theMobile Server.

5. Functionalities:a. Login using name and password or Active Directory support shall be available.b. Encrypted communications for all transactions.c. Print reports and export to CSV file.d. Customer logo customization shall be available for multi-tenant and hosted services applications.e. Video.

1) Live and playback video at 320 x 240, 640 x 480 or 1280 x 1024 @ 15 fps.2) Video export.3) 1, 4, 6 or 9 tiles.4) Basic PTZ Controls (Pan/Tilt, Zoom, go to presets, start pattern).5) Start/Stop recording.6) Sample web page for customers to see how to view video for their own development.7) Add boomarks

f. Access Control1) Cardholder and group (add/modify/delete).2) Credential management (modify/delete).3) Unlock door.4) Door Activities report.

g. Alarms1) Alarm report.

F. Smartphone and Tablet Apps1. The USP shall support mobile apps for various off-the-shelf smartphones and tablets. The mobile apps

shall communicate with the Mobile Server of the USP over any WiFi or wireless IP connection.


2. Mobile apps shall communicate with the UPS via a Mobile Server (same as the Unified Web Client orUWC). Communication between the mobile device and the Mobile Server shall support optionalencryption.

3. Supported devices shall include (refer to Mobile App specifications for latest compatibility list):a. Apple iPod Touch, iPhone, and iPad.b. Android-compatible smartphones and tablets.c. Windows and Windows Phone 8.1.

4. It shall be possible to download the mobile apps from the Central application store (Apple iTunes AppStore, Google Play, Windows Store).

5. Functionalitiesa. Live monitoring and command and control of the USP.b. Receive alarm push notifications from the Apple Push Notification Server or from the Google

Android push server.c. Alarm management (view and acknowledge alarms, video tied to alarms).d. View USP hierarchy and search for entities.e. Stream video from the mobile device using the built-in camera.

1) Video streams from mobile devices shall be available in the USP to be viewed in live andrecorded on the Archiver.

f. Video1) View live and playback video at 320 x 240, 640 x 480 or 1280 x 1024 @ 15 fps.2) Monitor camera status.3) View up to 6 video feeds.4) Control PTZ functionality of a camera, including access to PTZ presets.5) Save snapshots locally on the device.6) View video tied to access control events and alarms.

g. Access Control1) View cardholder picture with access-related events.2) Monitor door status.3) Unlock door.4) Override unlocking or locking schedule.5) Set door in maintenance mode.

2.05 SYSTEM FUNCTIONALITYA. Unification of Video and Access Control

1. The Monitoring UI shall present a true Unified Security Interface for live monitoring and reporting of theACS and VMS. Advanced live video viewing and playback of archived video shall be available throughthe Monitoring UI.

2. The Configuration UI shall present a true Unified Security Interface for the configuration andmanagement of the ACS and VMS.

3. The user shall be able to associate one or more video cameras to the following entity types: areas,doors, elevators, zones, alarms, intrusion panels, and more.

4. It shall be possible to view video associated to access control events when viewing a report.5. It shall be possible to view video associated to intrusion panel events when viewing a report.

B. Failover and Standby Functionality1. The USP shall support native and off-the-shelf failover options.2. Failover Directory

a. The Standby Directory shall act as a replacement SSM on hot standby, ready to take over as theacting Directory in case the primary Directory fails. The failover shall occur in less than 1 minute.No action from the user shall be required.

b. The USP shall support up to five (5) Directories on standby, lined up to take over as the actingDirectory in a cascading fashion.

c. The Standby Directory shall keep its configuration database synchronized with the primaryDirectory.

d. The Standby Directory shall support synchronization of the configuration databases using a backupand restore mechanism. The synchronization period shall be configurable from 15 minutes to 1week.

e. The Standby Directory shall support real-time synchronization of the configuration databases usingSQL Mirroring mechanism.

3. Standby Archiver.


4. Off-the-shelf standby/failover options (excluding the VMS Archiver) shall include:a. Windows Clustering.b. NEC ExpressCluster X LAN.

C. Third Party System Integration1. The USP shall support multiple approaches to integrating third party systems. These shall include:

Software Development Kits (SDKs), Driver Development Kits (DDKs), REST-based Web Service SDKs,RTSP Service SDKs, and more.

2. The USP architecture shall support the addition of new connectors to integrate to third party systemintegration, such as:a. Video analytics.b. Third party video systems.c. Third party access control systems.d. Point-of-sale (POS) systems.e. Building management systems.f. Human resource management systems (HRMS).

D. Alarm Management1. The USP shall support the following Alarm Management functionality:

a. Create and modify user-defined alarms. An unrestricted number of user-defined alarms shall besupported.

b. Assign a time schedule or a coverage period to an alarm. An alarm shall be triggered only if it is avalid alarm for the current time period.

c. Set the priority level of an alarm and its reactivation threshold.d. Define whether to display live or recorded video, still frames or a mix once the alarm is triggered.e. Provide the ability to display live and recorded video within the same video tile using

picture-in-picture (PiP) mode.f. Define the time period after which the alarm is automatically acknowledged.g. Define the recipients of an alarm. Alarm notifications shall be routed to one or more recipients.

Recipients shall be assigned a priority level that prioritizes the order of reception of an alarm.h. Define the alarm broadcast mode. Alarm notifications shall be sent using either a sequential or an

all-at-once broadcast mode.i. Define whether to display the source of the alarm, one or more entities, or an HTML page.j. Specify whether an incident report is mandatory during acknowledgment.

2. The workflows to create, modify, add instructions and procedures, and acknowledge an alarm shall beconsistent for access control, ALPR, and video alarms.

3. Alarms shall be federated, allowing global alarm management across multiple independent USP, ACS,and VMS systems.

4. The USP shall also support alarm notification to an email address or any device using the SMTPprotocol.

5. The ability to create alarm-related instructions shall be supported through the display of one or moreHTML pages following an alarm event. The HTML pages shall be user-defined and can be interlinked.

6. Alarm unpacking and packing shall be supported where all the entities associated to an alarm can bedisplay in the Monitoring UI with the single click of a button.

7. The user shall have the ability to acknowledge alarms, create an incident upon alarmacknowledgement, and put an alarm to snooze.

8. The user shall be able to spontaneously trigger alarms based on something he or she sees in thesystem.

9. An alarm shall be configured in such a way that it remains visible until the source condition has beenacknowledged.

10. The user shall be able to investigate an alarm without acknowledging it.E. Threat Levels

1. The USP shall support Threat Levels to dynamically change the system behavior to respond to criticalevents.

2. Threat Levels shall be activated and deactivated by the CSA operator with the right privilege.3. Threat Levels shall be set on an area or on the entire system.4. Threat Levels shall affect the system behavior by executing any action available in the USP such as:

trigger output, start recording, block camera, override recording quality, arm zone, set a door inmaintenance mode, and more.

5. The following specific actions shall be available with Threat Level:


a. Set minimum security clearance to restrict or permit acess to cardholders on specific areas on topof the restrictions imposed by the access rules.

b. Set minimum user level to automatically log out user from the USP.c. Set reader mode to change how the doors are accessed (e.g. card and PIN, or card or PIN).

6. A visible notification shall be displayed in all operator CSA when a Threat Level is activatedF. Remote Task

1. The USP shall provide, through a Remote Task, capabilities to remotely monitor and control the contentof other workstations running the CSA (Monitoring UI) that are part of the same system.

2. The USP shall support video wall applications by connecting and controlling multiple workstations andmonitors simultaneously.

3. The Remote Task shall be a graphical interface showing a replication of the remote workstation runningthe CSA (Monitoring UI).

4. The Remote Task shall allow the connection to other workstations using a low bandwidth mode toreceive only snapshots of video viewed remotely.

5. The Remote Task shall allow the connection to other workstations using a spy mode to remain invisibleto the remotely connected workstation.

6. The functionality provided by the remote monitoring and control capability shall include:a. Remote monitoring and control of the monitoring and alarm monitoring tasks.b. Ability to remotely switch cameras, doors and zones into display tiles.c. Ability to remotely control live and playback video.d. Ability to remotely change the tile pattern.e. Ability to remotely create and delete tasks.f. Ability to remotely start/stop task cycling.g. Ability to remotely go into full screen mode.h. Ability to remotely save and reload the workspace.

G. Health Monitoring1. The USP shall monitor the health of the system, log health-related events, and calculate statistics.2. USP services, roles, agents, units, and client apps will trigger health events.3. The USP shall populate the Windows Event Log with health events related to USP roles, services, and

client apps.4. A dedicated role, the Health Monitoring Role, shall perform the following actions:

a. Monitor the health of the entire system and log events.b. Calculate statistics within a specified time frame (hours, days, months).c. Calculate availability for clients, servers, and video/access/ALPR units.

5. A Health Monitoring task and Health History reporting task shall be available for live and historicalreporting.

6. A web-based, centralized health dashboard shall be available to remotely view unit and role healthevents of the USP.

7. Detailed system care statistics will be available through a web-based dashboard providing healthmetrics of USP entities and roles, including Uptime and mean-time-between-failures.

8. Health events shall be accessible via the SDK (can be used to create SNMP traps).H. Advanced Task Management

1. The USP shall support an infrastructure for managing Monitoring UI tasks used for live monitoring, dayto day activities, and reporting.

2. Administrators shall be able to assign tasks and lock the operator`s workspace. The user managementof their workspace shall be limited by their assigned privileges.

3. Operators shall be able save their tasks as either Public Tasks or Private Tasks and in a specificpartition. Public tasks shall be available to all users. Private tasks shall only be available to the owner ofthe task.

4. Operators shall be able to share their tasks by sending them to one or more online users. Recipientsshall have the option to accept the sent task.

I. Reporting1. The USP shall support report generation (database reporting) for access control, ALPR, video, and

intrusion.2. Each and every report in the system shall be a USP task, each associated with its own privilege. A user

shall have access to a specific report task if he or she has the appropriate privilege.3. The workflows to create, modify, and run a report shall be consistent for access control, ALPR, and

video reports.


4. Reports shall be federated, allowing global consolidated reporting across multiple independent USP,ACS, and VMS systems.

5. Access control and ALPR reports shall support cardholder pictures and license plate pictures,respectively.

6. The USP shall support the following types of reports:a. Alarm reports.b. Video-specific reports (archive, bookmark, motion, and more).c. Configuration reports (cardholders, credentials, units, access rules, readers/inputs/outputs, and

more).d. Activity reports (cardholder, cardholder group, visitor, credential, door, unit, area, zone, elevator,

and more).e. ALPR-specific reports (mobile ALPR playback, hits, plate reads, reads/hits per day, reads/hits per

ALPR zone, and more).f. Health activity and health statistics reports.g. Other types of reports, including visitor reports, audit trail reports, incident reports, and time and

attendance reports.7. Generic Reports, Custom Reports and Report Templates

a. The user shall have the option of generating generic reports from an existing list, generatingreports from a list of user-defined templates, or creating a new report or report template.

b. The user shall be able to customize the predefined reports and save them as new reporttemplates. There shall be no need for an external reporting tool to create custom reports and reporttemplates. Customization options shall include setting filters, report lengths, and timeout period.The user shall also be able to set which columns shall be visible in a report. The sorting of reporteddata shall be available by clicking on the appropriate column and selecting a sort order (ascendingor descending).

c. All report templates shall be created within the Monitoring UI.d. These templates can be used to generate reports on a schedule in PDF or Excel formats.e. An unrestricted number of custom reports and templates shall be supported.

8. A reporting task layout shall consist of panes with settings (report length, filters, go and resetcommands, etc.), the actual report data in column format, and a pane with display tiles. The user shallbe able to drag and drop individual records in a report onto one or more display tiles to view acardholder’s picture ID, playback a video sequence, or both.

9. The USP shall support comprehensive data filtering for most reports based on entity type, event type,event timestamp, custom fields, and more.

10. The user shall be able to click on an entity within an existing report to generate additional reports fromthe Monitoring UI.

11. The USP shall support the following actions on a report: print report, export report to a PDF/MicrosoftExcel/CSV file, and automatically email a report based on a schedule and a list of one or morerecipients.

J. Federation: Monitoring of Remote Systems1. The USP shall support the concept of a Federation for access control, video, and license plate

recognition.2. Federation shall allow multiple independent USP systems (Federated systems) to be unified into a

larger virtual system (the Federation). This shall facilitate the global monitoring of multiple independentUSP systems.

3. The Federation shall support the unification of multiple independent video surveillance systems or VMS.4. The Federation shall support the unification of multiple independent access control systems or ACS.5. The Federation shall support the unification of multiple independent license plate recognition systems or

ALPR.6. Entities that shall be federated and monitored centrally from the Federation shall include: alarms, areas,

cameras, cardholders and cardholder groups, credentials, doors, elevators, and zones (monitoredinputs).

7. The Federation shall support a cloud-based deployment, whereby the service and infrastructure will beupdated automatically and provisioned by the service provider, without need for on-site hardware.

8. The Federation shall support Global Alarm Management from the Monitoring UI for both access controland video.

9. The Federation shall support Global Report Generation from the Monitoring UI for both access controland video.


10. The Federation shall support dozens of operator actions on remote (federated) entities from theMonitoring UI (e.g. generating a global report taking into account events from multiple independent sitesor acknowledging remote alarms).

K. Microsoft Active Directory Integration1. The USP shall support a direct connection to one or multiple Microsoft Active Directory servers via the

Active Directory Role(s). Active Directory integration shall enable the synchronization of informationfrom the Active Directory server to the USP.

2. Active Directory integration shall permit the central management of the USP users, user groups,cardholders, and cardholder groups.

3. The USP shall be able to connect to and synchronize data from multiple Active Directory servers (up to10).

4. The USP shall support Microsoft Active Directory encryption using LDAP SSL.5. When enabled, Active Directory shall manage user logon to the USP client applications through the

user’s Windows credentials. Logging to the USP shall utilize native Active Directory passwordmanagement and authentication features.

6. It shall be possible to synchronize the following USP entities and their information from Active Directorywith the USP:a. Users (username, first and last names, email address, and more).b. User groups (user group name, description, and group email address).c. Cardholders (first and last names, description, email, picture and more).d. Cardholder groups (cardholder group name, description, and group email address).e. Active Directory attributes to USP custom fields.

7. When enabled, the addition, removal, or suspension of a user’s Windows account in Active Directoryshall result in the creation, deletion, or disabling of the equivalent user account in the USP.

8. When enabled, the addition, removal, or suspension of a user’s Windows account in Active Directoryshall result in the creation, deletion, or disabling of the equivalent cardholder account in the USP.

9. Supported synchronization methods for additions, modification, and deletions of synchronized entitiesshall include: on first logon (users only), manual synchronization, and scheduled synchronization.

10. The USP shall support user connections across independent organizations by connecting to an externalADFS (Active Directory Federation Services) service using claims-based authentication.

L. Zone Management1. The USP shall support the configuration and management of zones for input point monitoring via the

Zone Manager Role. A user shall be able to add, delete, or modify a zone if he or she has theappropriate privileges.

2. A zone shall monitor the status of one or more inputs points. Zone monitoring or input point monitoringshall be possible through the use of a controller and one or more input modules. Inputs from videocameras or video encoders shall also be accessible via a zone.

3. Depending on the hardware installed, supervised inputs shall be supported. Depending on the inputmodule used, both 3-state and 4-state supervision shall be available.

4. A schedule shall be defined for a zone, indicating when the zone will be monitored.5. Custom Events shall provide full flexibility in creating custom events tailored to a zone. Users shall be

able to associate custom events to state changes in monitored inputs.6. The ACS shall support one or more cameras per zone. Video shall then be associated to zone state

changes.7. Input/Output (IO) Linking.

a. Zone management shall support Input/Output (IO) Linking. IO Linking shall allow one or moreinputs to trigger one or more outputs.

b. IO Linking shall be available in offline mode when communication between the server andhardware is not available.

c. Custom Output Behaviors shall provide full flexibility in creating a variety of complex output signalpatterns: simple pulses, periodic pulses, variable duty-cycle pulses, and state changes.

d. Through the “trigger an output” action, the ACS shall support the triggering of outputs with customoutput behaviors.

M. Intrusion Device Integration1. The USP shall integrate with third party intrusion panels and devices via an Intrusion DDK. The

Intrusion Manager Role shall manage communications with the intrusion panels. Communications withintrusion devices shall be over serial communications and/or an IP network.


2. Integration with intrusion panels shall be possible outside the release cycle of the USP. It shall bepossible to add new integrations at any point in time.

3. Functionality available via the integration of intrusion devices with the USP shall include the following(where supported by the intrusion panel):a. Arm and disarm intrusion devices (manually, on schedule, or following a USP event).b. Activate or trigger intrusion device outputs.c. View intrusion events and alarms.d. Monitor the status, including arming status, of the intrusion devices.e. Video verification of intrusion events and alarms with video panels.f. Create USP zones using intrusion device inputs.

4. Currently supported intrusion panels include:a. Bosch G Series panels.b. DSC Powerseries panels.c. DMP XR Series panels.d. Honeywell Galaxy Dimension panels.

N. Asset Management Integration1. The USP shall integrate with third party asset management systems via the Asset Management Role.2. Communications with asset management solutions shall be over an IP network (via software

communications).3. Functionality available via the integration of asset management systems with the USP shall include the

following (where supported by the asset management systems):a. Synchronize asset management system assets with USP asset entities.b. Live monitoring of asset-related activity events, health events, and activity (asset online, asset

offline, asset moves, or low battery).c. Synchronization of asset management alarms with Security Center alarms.d. Viewing video tied to asset-related activity and alerts within monitoring and reporting tasks.e. Acknowledging alarms in Security Center which acknowledges alerts in the asset management

system and vice versa.f. Real-time tracking of asset locations on a per area basis.g. Asset Management Inventory reporting task that details the current location (area) of an asset.h. Asset Activity reporting task that provides a historical review of asset-related events and activity.

4. Currently supported asset management systems include:a. RF Code Asset Manager.

O. User And User Group Security, Partitions, and Privileges Management1. The USP shall support the configuration and management of users and user groups. A user shall be

able to add, delete, or modify a user or user group if he or she has the appropriate privileges.2. The USP shall support user authentication with claims-based authentication using external providers.

External providers shall include:a. ADFS (Active Directory Federation Services)

3. Common access rights and privileges shared by multiple users shall be defined as User Groups.Individual group members shall inherit the rights and privileges from their parent user groups. Usergroup nesting shall be allowed.

4. User privileges shall be extensive in the USP. All configurable entities for the USP, including accesscontrol/video/ALPR, shall have associated privileges.

5. Specific entities, such as cardholders, cardholder groups, and credentials shall include a more granularset of privileges, such as the right to access custom fields and change the activation or profile status ofan entity.

6. Partitions.a. The USP shall limit what users can view in the configuration database via security partitions

(database segments). The administrator, who has all rights and privileges, shall be allowed tosegment a system into multiple security partitions.

b. All entities that are part of the USP can be assigned to one or more partitions.c. A user who is given access to a specific partition shall only be able to view entities (components)

within the partition to which he or she has been assigned. Access is given by assigning the user asan accepted user to view the entities that are members of a particular partition.

d. A user or user group can be assigned administrator rights over the partition.7. It shall be possible to specify user and user group privileges on a per partition basis.8. Advanced logon options shall be available such as dual logon and more.


9. It shall be possible to specify an inactive period for the Monitoring UI after which time the shallapplication automatically lock, while still preserving access to currently displayed camera feeds.

P. Event/Action Management1. The USP shall support the configuration and management of events for access control, video, and

ALPR. A user shall be able to add, delete, or modify an action tied to an event if he has the appropriateprivileges.

2. The USP shall receive all incoming events from one or more ACS and/or VMS. The USP shall take theappropriate actions based on user-define event/action relationships.

3. The USP shall receive and log the following events:a. System-wide events.b. Application events (clients and servers).c. Area, camera, door, elevator, and ALPR events (reads and hits).d. Cardholder and credential events.e. Unit events.f. Zone events.g. Alarm events.h. First Person In and Last Person Out events and antipassback events.i. Intrusion events.j. Asset management events.

4. The USP shall allow the creation of custom events.5. The USP shall have the capability to execute an action in response to an access control, video, and

ALPR event.6. The USP shall allow a schedule to be associated with an action. The action shall be executed only if it is

an appropriate action for the current time period.Q. Schedules and Scheduled Tasks

1. Schedulesa. The USP shall support the configuration and management of complex schedules. A user shall be

able to add, delete, or modify a schedule if he or she has the appropriate privileges.b. The USP shall provide full flexibility and granularity in creating a schedule. The user shall be able to

define a schedule in 1-minute or 15-minute increments.c. Daily, weekly, ordinal, and specific schedules shall be supported.

2. Scheduled Tasksa. The USP shall support scheduled tasks for access control, video, and ALPR.b. Scheduled tasks shall be executed on a user-defined schedule at a specific day and time.

Recurring or periodic scheduled tasks shall also be supported.c. Scheduled tasks shall support all standard actions available within the USP, such as sending an

email or emailing a report.R. Macros and Custom Scripts

1. The USP shall enable users to automate and extend the functionalities of the system through the use ofmacros or custom scripts for access control, video, and ALPR.

2. Custom macros shall be created with the USP Software Development Kit (SDK).3. A macro shall be executed either automatically or manually.4. In the Monitoring UI, a macro shall be launched through hot actions.

S. Dynamic Graphical Maps (DGM)1. The USP shall support mapping functionality for access control, video surveillance, intrusion detection,

ALPR, and external applications.2. The USP shall provide a map centric interface with the ability to command and control all the UPS

capabilities from a full screen map interface.3. It shall be possible to span the map over all screens of the USP client station. In the scenario where the

map is spanned over all the screens of the USP client station it shall be possible to navigate the mapincluding pan and zoom, and the map’s moves shall be synchronized between all screens. Spanningthe map over multiple screen must provide the same command and control capabilities than in a singlescreen display.

4. The DGM shall support the following file format and protocol for importing map background:a. PDFb. JPGc. PNGd. Web Map Service (WMS) defined by the Open Geospatial Consortium (OGC)


e. BeNomad5. The DGM shall provide the following online map providers for use as map background and provide the

ability to manage their service license if they require one:a. Google Map, aerial, terrain (Licensed)b. Bing Map, aerial, satellite, hybrid (Licensed)c. OpenStreet Map aeriald. OVI hybrid

6. It shall be possible to configure a mixed set of maps made of GIS, online providers and private importedfiles and link them together.

7. The DGM shall provide the ability to display all native entities of the UPS including:a. Cameras, fix and PTZ.b. Doors.c. Camera sequences.d. Areas.e. Intrusion areas.f. Intrusion zones.g. License Plate Recognition cameras.h. Digital inputs.i. Digital outputs.j. Intercoms.k. Alarms.l. Macros.m. Police Car Patrollers.

8. The DGM shall provide the ability to draw and display information over the map in the form of:a. Vectoriel shapes: line, rectangles, polygones, ellipse.b. Pictures.c. Text.

9. The DGM shall provide the ability to display any type of third party entities integrated through an SDK.10. The DGM shall provide the ability to display layer of information in Keyhole Markup Language (KML)

format.11. The DGM shall provide the ability to the operator to manage layers of entities diplay over the map, being

able to turn them on and off and changing the superposition order.12. The DGM shall offer built-in map data backup and restore for both map background and layers of

entities.13. The DGM shall offer failover capabilities.14. The DGM shall scale up to sevral thousand of entities on a single map and hundreds of maps.15. The DGM shall provide a means to update a map background without affecting the map object

configuration.16. The DGM shall offer a user friendly graphical map designer to configure the maps.17. The DGM shall provide a user friendly and intuitive navigation that includes:

a. The ability to create hierarchies of maps to facilitate navigation within and between various sitesand buildings.

b. The ability to define favorites for recurrent position recall.c. The possiblity to create links between maps. The map links shall allow the link from one map to

multiple map representing the floors of a building.d. A common user experience regarding navigation into the map for both GIS or private maps.e. An history log of positions.

18. It shall be possible to monitor the state of entities on the map. It shall be possible to customize the iconeof any entities represented on the map.

19. The DGM shall display the actual video Field Of View of camera . It shall be possible to configure theFOV of a camera by entering the specification of the camera installation or graphically by moving theboundaries of the Field of View.

20. For PTZ cameras offering position feedback capabilitiy, the DGM shall:a. Dynamically represent the accurate Field Of View of the camera.b. Allow the user to act on the PTZ by moving its field of view.

21. The DGM shall offer the ability to optionaly set a graphical display notification of the motion detection22. The DGM shall offer a smart selection tool to access the video simply by clicking the location the user

wants to see, the DGM will atomatically select the cameras that can see this location and move the PTZ


towards that location. This smart selection tool shall take into consideration the obstacle and not displaycameras that can not see the location because of a wall.

23. It shall be possible to select a location by drawing a zone of interest on the DGM and display all theentities that are part of that zone of interest at once.

24. The user shall be able to select and display the countent of multiple USP entities on the map in popupwindows.

25. It shall be possible to access live and playback video from the map.26. It shall be possible to monitor from the DGM all entities event notification. User shall be able to turn on

and off the notification per entitiy.27. The DGM shall offer the ability to fully operate alarm monitoring. It shall be possible to:

a. Center the map on entities related to the alarm.b. Visalise the Alarms notification on the map access the realted video from the mapc. Trigger and receive alarms.d. Act on the alarm from the DGM, including acknowledgements, forwarding, and investigation.e. Visualize that an alarm occurred in an underlaying linked map.

28. The DGM shall provide the following search capabibilites:a. Search and center by entity name.b. From the Display of an entity in the USP locate the entie on the map and offer the ability to select

an other one close-by.29. Any update of map content by an administrator shall be immediately and dynamically pushed to all DGM

users.T. Audit and User Activity Trails (Logs)

1. The USP shall support the generation of audit trails. Audit trails shall consist of logs ofoperator/administrator additions, deletions, and modifications.

2. Audit trails shall be generated as reports. They shall be able to track changes made within specific timeperiods. Querying on specific users, changes, affected entities, and time periods shall also be possible.

3. For entity configuration changes, the audit trail report shall include detailed information of the valuebefore and after the changes.

4. The USP shall support the generation of user activity trails. User activity trails shall consist of logs ofoperator activity on the USP such as login, camera viewed, badge printing, video export, and more.

5. The ACS shall support the following actions on an audit and activity trail report: print report and exportreport to a PDF/ Microsoft Excel/CSV file.

U. Incident Reports1. Incident reports shall allow the security operator to create reports on incidents that occurred during a

shift. Both video-related and access control-related incident reports shall be supported.2. The operator shall be able to create standalone incident reports or incident reports tied to alarms.3. The operator shall be able to link multiple video sequences to an incident, access them in an incident

report, and change the date or time of the sequences later on.4. It shall be possible to create a list of Incident categories, tag a category to an incident, and filter the

search with the category as a parameter.5. Incident reports shall allow the creation a custom form on which to input information on an incident.6. Incident reports shall allow entities, events, and alarms to be added to support at the report’s

conclusions.V. Session Initiation Protocol (SIP) Communication Management (CM)

1. An operator of the USP shall be able to, within the USP Monitoring UI, initiate calls to and answer callsfrom other operator and edge voice devices, such as intercoms, emergency call stations, informationdesks, softphones or phone devices.

2. The USP shall support CM between the USP client User Interface and SIP endpoint devices.3. SIP endpoints shall be able to register to the UPS using a standard SIP protocol.4. The USP shall support CM between two SIP endpoint devices.5. The USP shall allow the configuration of SIP trunk connections to multiple SIP Servers supporting SIP

Trunks.6. The CM shall support the management of calls to and from other SIP Servers connected though SIP

Trunks.7. The CM is a service of the USP and shall not require the addition of any third party software.8. The CM shall support the following audio compression formats:

a. PCMA (G.711 aLaw).b. PCMU (G.711 uLaw).


c. G.722.d. G.729.

9. The CM shall certify SIP devices from the following manufacturers:a. Axis.b. Castel.c. Cisco.d. CodeBlue.e. Commend.f. Jacques.g. Vingtor- Stentofon.h. Zenitel.

10. The CM shall allow bidirectional audio and video recording of call sessions. The USP shall offer thefollowing recording capabilities:a. Automatic cleanup of call session files after a programmable number of days.b. Deactivation of call recording between operators.c. Deactivation of call recording with specific operators.d. Deactivation of call recording with specific voice devices.e. Selection of the storage path for call session recordings.

11. The CM shall provide the flexibility for the administrator to define the network ports used tocommunicate between the USP servers and :a. USP Operator Client User Interfaces.b. SIP devices.c. SIP servers.

12. The CM shall provide the capability to create Ring Groups. A Ring Group is a group of call numbersgrouped under a single call number. It shall be possible to set a Ring Group to simultaneously orsequentially call the members of the group. Dwell time for sequence mode shall be configurable.

13. The CM shall allow the automatic routing of calls through the configuration of a collection of rules (DialPlan). Dial Plans shall support the following capabilities:a. Match a phone number with regular expression.b. Route calls based on matching the phone numbers from which calls are made.c. Route calls based on matching the destination phone numbers to which calls are made.d. Change the phone extension from which calls are received.e. Change the phone extensions to which calls are sent.f. A combination of any of the above capabilities in a configured priority and based on a schedule.

14. Dial Plans shall be applicable to calls between SIP entities registered to the USP as well as to and fromexternal SIP servers.

15. The USP shall unify, within a simple user interface, the workflow between the associated securityentities of a call session, including the call box, cameras, doors, intrusion zones and outputs.

16. The USP shall support video and audio calls :a. Between USP Client User Interfaces.b. To and from USP Client User Interfaces and SIP devices.c. Between SIP devices.

17. The USP shall provide an advanced and friendly call management user interface that allows operatorsto:a. Connect standard USB headsets and webcams to USP Client User Interface workstations so that

USP users can make voice and video calls through the USP Client User Interface.b. Display the video associated with the call and switch between multiple video sources.c. Receive incoming call notifications directly through a notification tray.d. Initiate, answer, forward, place on hold, or cancel calls from a dedicated call dialog box.e. Control cameras, doors, zones, and device outputs during a call.f. Create a customizable list of contacts, so that users can quickly call their contacts. Contact lists

shall include other USP users, as well as SIP devices.g. Dial a phone number to make a call.h. Dial a DTF sequence during a call.i. Monitor the availability status of a user and set its own availability status.j. Access a history log of calls that the operator both initiated and received. This log shall show the

time of the call, duration, direction and the reason for its ending. It shall be possible to redial one ofthe entries in the log.


18. The USP shall allow an operator to manage up to 10 calls simultaneously. The call queue shall showthe status of each call: incoming, in call, or on hold. It shall be possible to hold and resume a calldirectly from the call queue.

19. The USP shall offer a call window. It shall be possible within the call windows to:a. Switch between cameras associated with the call participant.b. Open and lock doors associated with the call participant.c. Arm and Disarm zones associated with the call participant.d. Trigger outputs associated with the call participant.e. Put on hold, resume, forward, and end a call.f. Mute the microphone.g. Hide the webcam video feed.

20. The USP shall have a built-in address book. The address book shall be available in the call dialog box,in which users can view and manage their list of contacts. From the address book, users shall be ableto do the following:a. Call a contact by simply double-clicking the contact name.b. See the availability status of their contacts (users and SIP Devices).c. Quickly display a contact's information, such as photo, name, and number.d. Filter their contacts by type (SIP Device or User).e. Create a list of favorites by adding and removing contacts.f. Search for and call numbers that appear in the contact list.

21. The USP shall provide a graphical dial pad to allow the operator to make calls and dial DTMF tonesduring a call.

22. The USP shall provide call reporting capabilities to allow for the investigation of activities during specificcall sessions. The report shall provide the capability to replay audio recordings and watch call sessionsthat have associated video. The Call report shall provide filters to query the call records by:a. Date and time.b. Call session duration.c. Involved users and call stations.d. Call events and actions.e. Actions taken by a user on doors, intrusion zones and outputs during the call session.

23. The USP shall give the capability to export a call session, including bidirectional audio, associatedvideo, and log journal of the call session.

24. It shall be possible to place the voice devices as icons on a map that shall display the call status of thevoice device with a color code. A right-click on the voice device map icon shall allow the user to:a. Answer or reject an incoming call.b. Initiate a call to the device.c. Put on hold and resume a call with the device.

25. It shall be possible for an operator to select and broadcast his or her availability status, with the possiblestatuses being Available, Away and Busy. This status will appear with a color code in the call dialog boxof other operators.

W. Software Update Service1. The USP shall offer a web-based tool to manage software update of the SSM and CSA.2. The Software Update Service shall connect to the web to get automatic notification from the

manufacturer about new software version and update availability.3. The Software Update Service shall support a peer-to-peer mode to provide the ability to dedicate a

single server to be connected to the web and act as a proxy for the other SSM servers and CSAworkstations.

4. The Software Update Service shall offer the following functionality:a. Check for update at a regular interval.b. Notify administrator about the availability of new software versions and updates.c. Ability to automatically download the new software packages.d. Ability for the administrator to push the installation of the new software in a silent mode on both the

SSM servers and CSA workstations.e. Ability for the administrator to disable the service.

2.06 INTEGRATION TOOLKITSA. Software Development Kit (SDK)

1. A USP SDK shall be available to support custom development for the platform.


2. The SDK shall include functionalities specific to the embedded automatic license plate recognition(ALPR), access control (ACS), and video (VMS) systems.

3. Integration with external applications and databases shall be possible with the SDK.4. The SDK shall enable end-users to develop new functionality (user interface, standalone applications or

services) to link the USP to third party business systems and applications, such as Badging Systems,Human Resources Management Systems (HRMS), and Enterprise Resource Planning (ERP) systems.

5. The SDK shall be based on the .NET framework.6. The SDK shall support dynamic or transactional updates to the USP configuration. It shall also support

change notification of USP entity configuration.7. The SDK shall provide an extensive list of programming functions to view and/or configure core entities

such as: users and user groups, alarms, custom events, and schedules, and more.8. The SDK shall provide an extensive list of programming functions to view and configure ACS and VMS.9. The SDK shall provide an extensive list of programming functions to view and configure most ACS

entities such as: cardholders, cardholder groups, visitors, credentials, access rules (modify only), andcustom fields.

10. The SDK shall be able to receive real time events from the following USP entities: users and usergroups, areas, zones, cameras, video units, doors, door controllers (units), elevators, cardholders,cardholder groups, and credentials.

11. The SDK shall be able to query the history of events for areas, cameras, zones, alarm, cardholders,credentials, visitors, doors, query license plate read events, license plate hit events, generate a licenseplate hits report, generate a license plate reads report.

12. The SDK shall support the following alarm functions: view alarms in real time, acknowledge alarms,change priority, and change recipient.

2.07 VIDEO SURVEILLANCE SYSTEM FUNCTIONALITYA. General

1. The VMS shall be based on a true open architecture that shall allow the use of non-proprietaryworkstation and server hardware, non-proprietary network infrastructure and non-proprietary storage.

2. The VMS shall offer a complete and scalable video surveillance solution that shall allow cameras to beadded on a unit-by-unit basis.

3. The VMS shall interface with analog-to-digital video encoders and IP cameras and with digital-to-analogvideo decoders, hereafter referred to as digital video servers (DVS). The VMS shall support DVS fromvarious manufacturers.

4. The VMS shall integrate DVS using the DVS native SDK or using the following industry standards tointerface to the DVS:a. ONVIF.

5. All video streams supplied from analog cameras or IP cameras shall be digitally encoded in MPEG-4,MPEG-2, MJPEG, H.264, H.265, Wavelet, or JPEG2000 compression formats and recordedsimultaneously in real time.

6. All audio streams supplied from IP video servers shall be digitally encoded in g711 (u-law), g721, g723,or AAC compression formats and recorded simultaneously in real time.

7. Each camera’s bit rate, frame rate, and resolution shall be set independently from other cameras in thesystem, and altering these settings shall not affect the recording and display settings of other cameras.

8. The VMS shall be able to use multiple CCTV keyboards to operate the entire set of cameras throughoutthe system, including brands of cameras from various manufacturer and including their PTZfunctionalities (i.e.: Pelco keyboard controls Panasonic dome or vice-versa).

9. The VMS shall be able to retrieve and set the current position of PTZ cameras using XYZ coordinates.10. The VMS shall support PTZ camera protocols from multiple manufacturers, including analog and IP

protocols.11. The VMS shall arbitrate the user conflict on PTZ usage based on user levels per camera12. The VMS shall support the following list of CCTV keyboard protocols:

a. American Dynamics 2078 ASCII, and American Dynamics 2088 ASCII.b. Bosch Autodome, Bosch Intuikey.c. DVTel.d. GE ImpactNet.e. Panasonic, Pelco ASCII, Pelco KBD-300, and Pelco P.f. Radionics.g. Samsung SSC-1000.h. Videoalarm.

13. The VMS shall support the following list of joysticks and control keyboards:


a. Axis 295.b. Axis T8310 Video Surveillance Control Board.c. Panasonic WV-CU950 Ethernet keyboard.d. Any USB joystick detected as a Windows Game Controller.

14. The VMS shall allow for the configuration of a time zone for each camera connected to a DVS. Forplayback review, users shall have the ability to search for video based on the following options:a. Local time of the camera.b. Local time of the SSM.c. Local time of the user’s workstation.d. GMT Time.e. Other time zone.

15. Audio and Video storage configuration for the SSM shall either be:a. Internal or external IDE/SATA/SAS organized or not in a RAID configuration;b. Internal or external SCSI/iSCSI/Fiber Channel organized or not in a RAID configuration;c. Within the overall storage system, it shall be possible to include disks located on:

1) External PCs on a LAN or WAN.2) Network Attached Servers (NAS) on a LAN or WAN.3) Storage Area Networks (SAN).

16. The SSM shall not limit the actual storage capacity configured per server.B. Configuration UI

1. The Configuration UI shall allow the administrator or users with appropriate privileges to change videoconfiguration.

2. The Configuration UI shall provide the ability to change video quality, bandwidth, and frame rateparameters on a per camera (stream) basis for both live and recorded video.

3. The Configuration UI shall provide the ability to change video quality by a selection of predefined videoquality template.

4. The Configuration UI shall provide the ability to configure brightness, contrast, and hue settings for eachcamera on the same DVS.

5. The Configuration UI shall provide the capability to enable audio recording on DVS units that supportaudio.

6. The Configuration UI shall provide the ability to change the audio parameters, serial port and I/Oconfiguration of individual DVS units

7. The Configuration UI shall provide the capability to rename all DVS units based on system topology andto add descriptive information to each DVS.

8. The Configuration UI shall provide the ability to set recording schedules and modes for each individualcamera. The recording mode can be:a. Continuous.b. On motion and Manual.c. Manual only.d. Disabled.

9. The Configuration UI shall support the creation of schedules to which any of the following functionalaspects can be attached:a. Video quality (for each video stream per camera).b. Recording (for each camera).c. Motion detection (for each detection zone per camera).d. Brightness, Contrast, and Hue (for each camera).e. Camera sequence execution.

10. The Configuration UI shall support the creation of unlimited recording schedules and the assigning ofany camera to any schedule.

11. The Configuration UI shall detect and warn user of any conflict within assigned schedules.12. The Configuration UI shall provide the capability to set a PTZ protocol to a specific DVS serial port and

shall allow mixing domes of various manufacturers within a system.13. User shall have the ability to configure a return to home function after a predefined period of inactivity

for PTZ cameras. This period of inactivity time shall be configurable from 1 to 7200 seconds.C. Archiving

1. The Archiver (role) shall use an event and timestamp database for the advanced search of audio/videoarchives. This database shall use Microsoft SQL.


2. The Archiver shall protect archived audio/video files and the system database against network accessand non-administrative user access.

3. The Archiver shall digitally sign recorded video using 248-bit RSA public/private key cryptography.4. The Archiver shall offer a plug and play type hardware discovery service with the following

functionalities:a. Automatically discover DVS units as they are attached to the network.b. Discover DVS units on different network segments, including the Internet, and across routers with

or without network address translation (NAT) capabilities.5. The Archiver shall have the capacity to configure the key frame interval (I-frame) in seconds or number

of frames.6. The Archiver shall provide a pre-alarm and post-alarm recording option that can be set between one

second and 5 minutes on a per camera basis.7. The Archiver shall provide the functionality of storing of video and audio streams based on triggering

events, such as:a. Digital motion detection.b. Digital input activation.c. Macros.d. Through SDK application recording.

8. The Archiver shall perform video motion detection on each individual camera based on a grid of 1320motion detection blocks. All of the video motion detection settings are configurable on schedule. Aglobal sensitivity threshold is available to reduce motion detection sensitivity when the video signal isnoisy or when a lot of false hits are incurred. Video motion detection itself can be set into four differentmodes:a. Full Screen: All 1320 blocks on screen are activated, and a general threshold for the overall motion

in the entire image can be set and, when it is reached, it can trigger recording and a motion eventor a custom event.

b. Full Screen Unit: This is the same as the Full Screen, but the motion detection takes place in theDVS.

c. Detection Zone: Six overlapping zones can be defined in the 1320 blocks on screen with each ofthese zones having its own threshold, and, when that threshold is reached, each one of them cantrigger recording and a motion event or a custom event. Each zone triggering its own event allowsfor the configuration of directional motion detection events and other complex motion detectionlogic.

d. Detection Zone Unit: This is the same as the Detection Zone, but the motion detection takes placein the DVS and only one zone is supported.

e. Disabled: No motion detection is performed on this camera.9. The Archiver shall be able to detect motion in video within 200 milliseconds and not only on key frames.10. The Archiver shall allow for multiple recording schedules to be assigned to a single camera. Each

schedule shall be created with the following parameters:a. Recording mode:

1) Continuous.2) On Motion/Manual.3) Manual.4) Disabled.

b. Recurrence pattern:1) Once on specific days.2) Specific days on a yearly basis.3) Specific days on a monthly basis.4) Specific days on a weekly basis.5) Daily.

11. Time coverage:a. All day.b. Specific time range(s).c. Daytime or nighttime based on the times of sunrise and sunset that are automatically calculated

from the time of year and a geographical location. Provision shall be given to offset the calculatedsunrise or sunset time by plus or minus 3 hours.

12. The Archiver shall allow each camera (video source) to be encoded multiple times in the same ordifferent video formats (MPEG-4, MPEG-2, MJPEG, H.264, H.265,Wavelet, or JPEG2000), limited onlyby the capabilities of each DVS.


13. Whenever multiple video streams are available from the same camera, users shall be free to use anyone of them based on their assigned usage. The standard video stream usages are:a. Live.b. Recording.c. Remote.d. Low resolution.e. High resolution.

14. The Archiver shall allow the video quality to vary according to predefined schedules. Such schedulesshall have the same configuration flexibility as the recording schedules mentioned earlier. The videoquality shall be based on, but not limited to, the following parameters:a. Maximum bit rate.b. Maximum frame rate.c. Image quality.d. Key frame interval.

15. The Archiver shall have the ability to dynamically boost the quality of the "recording stream" (seeprevious bullet) based on specific events:a. When recording is started manually by a user.b. When recording is triggered by a macro, an alarm or detected motion.

16. The Archiver shall have the capacity to communicate with the DVS using 128 bits SSL encryption.17. The Archiver shall have the capacity to communicate with the DVS using HTTPS secure protocol.18. The Archiver shall have the capacity to receive multicast UDP streams directly from the DVS.19. For network topologies that restrict the DVS from sending multicast UDP streams, the Archiver shall

redirect audio/video streams to active viewing clients on the network using multicast UDP.20. The Archiver shall have the capacity to redirect audio/video streams to active viewing clients on the

network using unicast UDP or TCP.21. The Archiver shall empower the administrator with a full range of disk management options:22. The Archiver shall allow the administrator to choose which disks to use for archiving and to set a

maximum quota for each.23. The Archiver shall allow the administrator to spread the archiving of different cameras on different disk

groups (groups of disks controlled by the same controller) so that archiving could be carried out inparallel on multiple disks.

24. The Archiver shall have the capacity to move video archives to the Azure Cloud. The archives will bemoved after a preset number of days.

25. The Archiver shall offer the following options to clean up old archives, on a camera by camera basis:a. After a preset number of days.b. Deleting oldest archives first when disks run out of space.c. Stop archiving when disks are full.

26. The Archiver shall allow important video sequences to be protected against normal disk cleanuproutines.

27. Users shall have the following options when protecting a video sequence:a. Until a specified date.b. For a specified number of days.c. Indefinitely (until the protection is explicitly removed).

28. The Archiver shall allow the administrator to put a cap on the percentage of storage space occupied byprotected video.

29. The Archiver shall keep a log and compile statistics on disk space usage.30. The statistics shall be available by disk group or for the whole Archiver.31. The statistics shall show the percentage of protected video over the total used disk space.32. The Archiver shall have the capacity to down-sample video streams for storage saving purposes. The

down-sampling options available are the following:a. For H.264, MPEG-4, H.265, streams the down-sampling options are: all key frames, 1 fps, 2

sec./frame, 5 sec./frame, 10 sec./frame, 15 sec./frame, 30 sec./frame. 60 sec./frame 120sec./frame.

b. For MPEG-4 streams the down-sampling options are: all key frames, 1 fps, 2 sec./frame, 5sec./frame, 10 sec./frame, 15 sec./frame, 30 sec./frame. 60 sec./frame 120 sec./frame.

c. For MJPEG streams the down-sampling options are: 15 fps, 10 fps, 5 fps, 2 fps, 1 fps, 2sec./frame, 5 sec./frame, 10 sec./frame, 15 sec./frame, 30 sec./frame, 60 sec./frame 120sec./frame.

33. The Archiver shall support DVS with edge recording capabilities and offer the following capacities:


a. The ability to playback the video recorded on the DVS at different speeds.b. The ability to offload (video trickling) the video recorded on the DVS on schedule, on event, or

manually to store it on the Archiver.c. It shall be possible to filter the video that is being offloaded using one or multiple of the following

filters:1) Time interval.2) Playback request.3) Video analytic events.4) Motion events.5) Bookmarks.6) Alarms.7) Input pin events.

34. Unit offline events.The Archiver shall be provided with proven performance and scalability figures:a. The Archiver’s performance shall be guaranteed during the rebuild of a disk from a raid 5 disk

group. The rebuild process shall not affect the recording and playback capabilities.b. The recommended server specification from the Genetec Security Center Hardware Requirement

shall allow Archiver to perform up to 300 cameras or 300Mbs throughput first limit reached.c. The high-performance archiver specification from the Genetec Security Center Hardware

Requirement shall allow Archiver to perform :1) Up to 500 cameras or 500Mbs throughput first limit reached with a 1Gbs NIC.2) Up to 700 cameras or 1300Mbs throughput first limit reached with a 10Gbs NIC.

35. The Archiver shall provide the ability to encrypt the media stream coming from the DVS including thevideo, audio and metadata.a. Media encryption shall be optional and can be activated on a per DVS basis.b. Media encryption shall be performed with AES-128.c. Media encryption shall encrypt all video, audio and metadata at rest and in transit. Once

mediaencryption is turned on for a DVS all media stored or redirected by the Archiver shall beencrypted and shall require the private key to be decoded.

d. It shall be possible to export the encrypted media into a non-encrypted ASF file.D. Auxiliary Archiver

1. The Auxiliary Archiver shall be used to produce redundant archives (video, events, or bookmarks) forany camera in the system, on a case by case basis.

2. The Auxiliary Archiver shall have the ability to record a camera on a different schedule than theArchiver.

3. The Auxiliary Archiver shall have the ability to archive any of the standard video streams for archiving.The standard video stream usages are: Live, Recording, Remote, Low Resolution, and High Resolution.

4. The Auxiliary archiver shall have the capacity to move video archives to the Azure Cloud.E. Standby Archiver

1. The Standby Archiver shall act as a replacement Archiver role on hot standby, ready to take over thefunctions of the primary Archiver role. The failover will occur in less than 1 minute. No action from theuser will be required.

2. The Standby Archiver assigned to an Archiver role entity shall automatically provide protection for allDVS connected to that Archiver role

3. The Standby Archiver shall protect the primary Archiver role against the following failures:a. Server failure (hardware or software)b. Storage failure, such as Archiver Role detects that it cannot read or write to any of its allocated

disks.4. It shall be possible for a single USP server to act as the standby server of multiple Archiver roles.

a. Each Archiver role shall have priority value if multiple Archiver Roles fail at the same time on thesame standby server

5. It shall be possible for any Archiver role in the system to be designated as another's standby andvice-versa.

6. The Standby Archiver shall have the ability to act as a Redundant Archiver.7. The Redundant Archiver shall maintain an exact copy of everything recorded by the default Archiver, i.e.

audio/video archives, events, and bookmarks.8. Redundancy shall be configured on a camera by camera basis.9. The Redundant Archiver shall have to ability to use a multicast video stream from the DVS and shall not

require an additional connection to any DVS.


F. Cloud Archiving1. The VMS shall support the automatic transfer of video recorded on the Archiver to the cloud, based on

the age of the video.2. The Archiver shall encrypt recordings using AES-256 prior to transferring video to the cloud and

maintain encryption keys local to the user’s system.3. The VMS shall support TLS encryption between the on-premises Archiver and the cloud4. The VMS shall allow users to search video stored in the cloud through the same functionality used when

querying video that is stored locally.5. The VMS will maintain a local cache of video downloaded from the cloud, in order to playback

recordings without requiring an additional transfer.G. Media Streaming

1. The Media Router Role shall be responsible for routing video and audio streams across local and widearea networks from the source (e.g. DVS) to the destination (e.g. CSA).

2. The Media Router Role shall support multiple transport protocols, such as unicast TCP, unicast UDP,and multicast UDP.

3. The Media Router shall support IGMP (Internet Group Management Protocol) to establish multicastgroup memberships:a. IGMP v3, including SSM (Source-Specific Multicast) shall be supported.

4. The Media Router Role using Redirector Agents shall be responsible for redirecting a stream from asource IP endpoint to a destination IP endpoint.

5. The Redirector Agents shall be capable of converting a stream from and to any supported transportprotocols:a. Multicast UDP to Unicast TCP.b. Multicast UDP to Unicast UDP.c. Unicast TCP to Multicast UDP.d. Unicast UDP to Multicast UDP.

6. It shall be possible to limit the number of concurrent live and playback video redirections for eachRedirector Agent in order to better control the bandwidth across multiple sites.

7. It shall be possible to protect the Media Router Role against hardware or software unavailability byconfiguring another Media Router Role to act as a hot standby server.

8. Multiple Redirector Agents shall be used on a large VMS installation to increase the service availabilityand to provide automatic load balancing.

H. Video Archives Transfer capabilities1. Archive transfer shall provide the ability to:

a. Transfer video from a server to another server in the same system.b. Transfer video from a federated server to another server.c. Transfer video from camera storage to a server.

2. It shall be possible to program video transfers either on a recurrent schedule, or to trigger themmanually or upon connection.

3. It shall be possible to filter the video of interest for a transfer. The video of interest shall be defined withthe following filters:a. All archives when the camera was offline.b. Alarms.c. Playback request from the edge.d. Video analytics events.e. Motion events.f. Bookmarks.g. Input triggers.h. Time range.

4. It shall be possible to define the length of video before and after the event used as a filter to determinethe video of interest.

5. The USP shall offer an interface for displaying all video archive transfer requests. This interface shalldisplay all the current, requested and scheduled video transfer requests. It shall be possible to edit,trigger, and cancel video archive transfers from this interface.

2.08 ACCESS CONTROL SYSTEM FUNCTIONALITYA. General


1. The ACS shall be an enterprise class IP access control software solution. It shall be fully embeddedwithin a Unified Security Platform (USP). The USP shall allow the seamless unification of the ACS withan IP video management system (VMS).

2. The ACS shall be highly scalable to support configurations consisting of thousands of doors withfacilities spanning multiple geographic areas.

3. The ACS shall support an unrestricted number of logs and historical transactions (events and alarms)with the maximum allowed being limited by the amount of hard disk space available.

4. The ACS shall support a variety of access control functionality, including but not limited to:a. Controller (Unit) management, door management, elevator management, and area management.b. Cardholder and cardholder group management, credential management, and access rule

management.c. Badge printing and template creation.d. Visitor Management.e. People counting, area presence tracking, and mustering.f. Offering a framework for third party hardware integration, such as a card and signature scanner.

B. Access Management1. The ACS shall be based on an open architecture able to support multiple access control hardware

manufacturers. The ACS shall be able to integrate with multiple non-proprietary interface modules andcontrollers, access readers, and other third party applications.

2. The ACS shall be an IP enabled solution. All communication between the ACS and hardware controllersshall be based on standard TCP/IP protocol.

3. Access Manager Rolea. The Access Manager Role shall be the server that synchronizes all access control hardware units

under its control, such as door controllers and IO modules. It shall also be able to validate and logall access activities and events when the door controllers and IO modules are online.

b. The Access Manager Role shall maintain the communication link with the hardware controllersunder its control. It shall also continuously monitor whether the controllers are online or offline.

c. Synchronization of hardware units shall be automated and transparent to users and shall occur inthe background. It shall also be possible to manually synchronize units or to synchronize units on aschedule.

d. The Access Manager Role shall support doors and controllers located within one or more facilities.The Access Server shall support a minimum of 200 readers and up to 1024 readers per computer.

4. The Access Server shall store all access events associated with the doors, areas, hardware zones(hardware input points), elevators, and controllers under its direct control.

C. Global Cardholder Management1. The ACS shall support global cardholder management and synchronization between a central

independent site and remote independent sites, all of which can have their own Directory anddatabases.

2. It shall be possible to synchronize the following entities and their configuration data:a. Cardholders (incl. custom fields).b. Cardholder groups.c. Credentials.d. Badge templates.

3. Cardholders and other synchronized entities can be added centrally and synchronized to remote sitesfor central cardholder management.

4. Cardholders and other synchronized entities can be added at remote sites and synchronized to thecentral site and other remote sites.

5. The ACS shall support the assignment of a single card per cardholder across all of an organization’ssites.

6. Manual and scheduled synchronization shall be supported.D. Hardware Compatibility List

1. The ACS shall have an open architecture that supports the integration of third party IP-based doorcontrollers and IO modules. The ACS shall simultaneously support mixed configurations of accesscontrol hardware from multiple vendors.

2. The ACS shall support multiple types of hardware devices: single-reader controllers, 2-readercontrollers, 1- to 64-reader controllers, integrated readers and door controllers, andPower-over-Ethernet (PoE) enabled door controllers.


3. The ACS shall support most industry standard card readers that output card data using the Wiegandprotocol and Clock-and-Data.

4. The ACS shall support the following IP-enabled controllers. For a description of the capabilities of thecontroller, refer to the specific controller’s A&E specifications and design:a. Genetec Synergis Master Controller.b. Genetec Synergis Cloud Link.c. HID VertX.d. HID VertX EVO.e. HID Edge.f. HID Edge EVO.g. Mercury controllers and SIO modules.h. Mercury M5 bridge.i. Assa Abloy Aperio RS485 8 to 1 hub.j. Assa Abloy IP locks (no DSR required).

1) Corbin Russwin.2) Sargent Passport.3) Sargent Profile.4) IN120.

k. Salto Sallis RS485 and PoE routers.l. Axis A1001.m. STid RS485 readers.n. DDS AS34/TPL4.

5. The following USB enrollment readers shall be supported:a. RF Ideas pcProx HID USB reader for enrolling proximity cards.b. RF Ideas AIR ID Enroll iCLASS ID# USB reader for enrolling HID iCLASS cards.c. RF Ideas AIR ID Enroll 14443/15693 CSN USB reader for enrolling a MIFARE card using the CSN

(card serial number).d. RF Idea AIR ID Enroll pcProx Plus w/iCLASS reader for enrolling proximity and iCLASS cards.e. STid STR-W35-E/PH5-5AA.f. HID Omnikey 5x21 USB readers.

E. Software Functionality1. Seamless Unification with VMS

a. Through the USP, the ACS shall support integration with an IP Video Surveillance System or MVS.Integration with an IP video surveillance system shall permit the user to view live and recordedvideo.

b. Users shall be able to associate one or more video cameras to the following entity types: doors,elevator, and hardware zone (input points) and more.

c. The Monitoring UI shall present a true Unified Security Interface for access control and videosurveillance. Advanced live video viewing and playback of archived video shall be availablethrough the Monitoring UI.

d. It shall be possible to view video associated with access control events when viewing a report.2. Controller (Unit) Management

a. The ACS shall support the discovery, configuration, and management of IP enabled controllers andIO modules (hardware units). A user shall be permitted to add, delete, or modify a controller if he orshe has the appropriate privileges.

b. The ACS shall support automatic unit discovery. The user shall establish the settings for discoveryports and for the types of unit discovery and the ACS shall automatically detect all connecteddevices.

c. The ACS shall support a unit swap utility for swapping out an existing controller with a newcontroller. The unit swap utility shall avoid the reprogramming of the system whenever a unit isreplaced. All logs and events from the old unit shall be maintained.

d. The ACS shall support preconfiguration of the system prior to the physical hardware installation.3. Cardholder And Cardholder Group Management

a. The ACS shall support the configuration and management of cardholders and cardholder groups.A user shall be able to add, delete, or modify a cardholder or cardholder group if he or she has theappropriate privileges.

b. Custom fields shall be supported for both cardholders and cardholder groups.


c. The ACS shall permit the following activation/expiration options for a cardholder’s profile: delayedactivation of a cardholder’s profile, expiration based on the date of first use of credentials, orexpiration on a user-defined date.

d. It shall be possible to associate a picture to a cardholder’s profile. The picture shall be importedfrom a file, captured with a digital camera, or captured from a video surveillance camera. When acardholder event occurs, the picture of the cardholder shall be displayed in the Monitoring UI. TheACS shall support multiple standard picture formats.

e. Cardholder groups shall enable the grouping of cardholders to facilitate mass changes to systemsettings. It shall be possible to assign cardholder groups to access rules, thus avoiding theassignment of one cardholder at a time.

f. It shall be possible to search by picture association, custom fields, names and credential codes.g. It shall be possible to select multiple cardholders for immediate deactivation or reactivation.h. The ACS shall support the synchronization of cardholders and cardholders group through Active

Directory including the credentials and pictures of the cardholders.4. Credential Management

a. The ACS shall support the configuration and management of credentials, e.g. access cards andkeypad PIN numbers. A user shall be able to add, delete, or modify a credential if he or she hasthe appropriate privileges.

b. Users shall be able to add Custom Fields (user-defined fields) to credentials. Creating a newcredential shall be accomplished either manually or automatically.

c. Automatic creation shall allow the user to create a credential entity by presenting a credential to aselected reader. The ACS shall read the card data and associate it to the credential entity. It shallbe possible to automatically enroll any card format (128 bits or less).

d. The ACS shall support multiple credentials per cardholder without necessitating duplicatecardholder information. The ACS shall automatically detect and prevent attempts to register analready-registered credential.

e. Batch enrollment of credentials shall be supported.f. The ACS shall provide a workflow for badge issuance and card requests.

5. Custom Card Formatsa. A custom card format feature shall allow the administrator to add additional custom card formats

using an intuitive tool within the Configuration UI. The custom card format tool shall be flexible inthe following ways:1) Once enrolled, new custom card formats shall appear in the card format lists for manual card

enrollment.2) An unrestricted number of additional custom card formats can be added.3) Shall support credential with up to 256 bits.

b. The administrator shall be able to set the following options when defining a new format:1) The order in which card fields appear in the user interface or CSA.2) Whether a field is hidden from or visible to an operator.3) Whether a field is read only or modifiable by an operator.4) Complex parity checking schemes.5) The order and location of a field’s data. Location can be defined on a bit-by-bit basis.

6. Badge Designera. The badge designer shall allow the creation of badge templates that define the content and

presentation format of a cardholder badge to be printed.b. Badge production shall consist of selecting the credential, the badge template, and clicking print.c. Batch printing of cards shall be available.d. The contents of a badge template can include: cardholder’s first and last name, picture, custom

fields, bitmap graphics, lines, ovals, rectangles, dynamic text labels linked to custom fields andstatic text labels, and barcodes (Interleaved 2 of 5, Extended Code 39).

e. Copy and paste of badge template objects shall be available.f. It shall be possible to set the border thickness and color, the fill color of badge objects (content),

and the color of text labels.g. Settings, such as object transparency, text orientation, and auto-sizing of text shall be available or

transparent to the user.h. Supported badge formats shall be (portrait and landscape): CR70 (2.875" x 2.125"), CR80 (3.37" x

2.125"), CR90 (3.63" x 2.37"), CR100 (3.88" x 2.63"), and custom card sizes.i. Dual-sided badges shall be supported.


j. A badge template import and export function shall be available to allow the sharing of badgetemplates between distinct or independent ACS.

k. Chromakey shall be supported.7. Door Management

a. The ACS shall support the configuration and management of doors. A user shall be able to add,delete, or modify a door if he or she has the appropriate privileges.

b. The ACS shall permit multiple access rules to be associated to a door.c. The ACS shall support the following forms of authentication: Card Only, Card or Keypad (PIN), or

Card and Keypad (PIN). It shall be possible to define a schedule for when Card Only or Card andKeypad authentication modes shall be required.

d. It shall be possible to set an extended grant time on a per-door basis (in addition to the standardgrant time).Cardholder properties shall include the option of using the extended grant time. Whenflagged cardholders are granted access, the door shall be unlocked for the duration of theextended grant time instead of the standard grant time.

e. The ACS shall allow the configuration of the relocking mode on doors such as on door open, aftera definite time, or on door close.

f. The ACS shall support the ability to enforce the use of two valid reads from different cardholders togrant access to an area.

g. The ACS shall support the ability to enable access rules for other cardholders once a supervisorhas accessed an area.

h. The ACS shall support the ability to enable unlocking schedule on a door once an employee hasentered the facility.

i. Readerless doors.1) The ACS shall support doors configured solely with a lock, a REX, and a door contact but

without readers.2) The implementation of a readerless door shall be possible with the use of standard access

hardware IO modules. External hardware, such as timers, shall not be required.3) Unlocking schedules shall be programmable for readerless doors.4) Standard door activity reports shall also be possible with readerless doors.

j. Unlocking schedules and exceptions to unlocking schedules shall be associated with a door. Anunlocking schedule shall determine when a door should be automatically unlocked. The ACS shallalso support the use of a specific offline unlocking schedule. Exceptions to unlocking schedulesshall be used to define time periods during which unlocking schedules shall not be applied, such asduring statutory holidays.

k. The ACS shall support one or more cameras per door. Video shall then be associated to dooraccess events, such as access grant or access denied.

8. Elevator Managementa. The ACS shall support the configuration and management of elevators. A user shall be able to add,

delete, or modify an elevator if he or she has the appropriate privileges.b. The ACS shall be able to control access to specific floors using a reader within the elevator cab.

Control shall be available through the use of a controller with an interface to a reader and tomultiple output modules with relays.

c. Elevator floor selections shall be tracked using a controller with an interface to multiple inputmodules. Floor tracking shall be available within an elevator activity report.

d. The elevator control module shall continue to function in offline mode should communicationbetween the ACS and the controller fail.

e. The ACS shall support one or more cameras per elevator cab. Video shall then be associated toelevator access events, such as access grant or access denied.

9. Visitor Managementa. The ACS shall support the configuration and management of visitors. A user shall be able to enroll

or remove a visitor if he or she has the appropriate privileges. The ACS shall support the check-inand check-out of visitors from the Monitoring UI.

b. A visitor check-in wizard shall facilitate the enrollment process, allowing a user to specify thevisitor’s specific information.

c. The ACS shall permit the following credential options during visitor check-in:1) Use an existing credential.2) Automatically create a new credential.3) Manually create a new credential.


d. The ACS shall support the creation of a pool of visitor credentials in advance. Existing visitorcredentials shall be assigned to visitors during the check-in process.

e. The ACS shall permit cardholder groups to be designated as “available for visitors”. Users shall beable to define the access privileges for the cardholder groups (visitor cardholder groups) inadvance. During visitor check-in, the user shall select the appropriate visitor cardholder group toassociate with a visitor. All of the visitor cardholder group access privileges shall be automaticallytransferred to the visitor. This feature shall permit the creation of multiple types of visitor groupsand associated privileges, such as for contractors, VIPs, and day visitors. Visitors added to a visitorcardholder group in the Monitoring UI shall be automatically updated in the Configuration UIcardholder group screen.

f. A visitor’s profile shall support the real-time modification of visitor information after a visitor haschecked-in.

g. The ACS shall also provide comprehensive visitor tracking and visitor reporting. Through the realtime tracking feature, the ACS shall generate a real time and historical visitor activity listing in theMonitoring UI. The ACS shall also generate visitor-specific reports that provide comprehensivelistings of visitors as well as full details on their movement.

h. It shall be possible to exempt a visitor from any antipassback rules in effect.i. The operator shall be able to print visitor badges during the check-in process. The printing of both

paper badges (visitor without an assigned credential) and actual credentials shall be supported.j. Visitor management and reporting shall be available through the Web Client as well.k. It shall be possible to locate a visitor`s information or profile by swiping the visitor`s credential

(card) at a USB reader.l. It shall be possible to tag the person visited to the visitor’s profile.m. It shall be possible to require that the visitor must have an escort to enter an area and that that

escort must badge-in to confirm the access of the visitor.10. People Counting & Area Presence Tracking (Mustering)

a. The ACS shall support people counting (or area presence tracking). The ACS shall be able tomonitor and report the number of cardholders in an area in real-time and for all areas. Monitoringshall be based on the entire access control infrastructure, for both local areas and those in remotegeographic locations. People counting can also be used to perform mustering.

b. The ACS shall report area presence counts in the Monitoring UI. Area presence tracks shalldynamically track the total number of cardholders in an area. Displayed data shall be updateddynamically.

c. The ACS shall be able to generate an area presence report listing the cardholders located in oneor more areas, accessible through the Monitoring UI. It shall be possible to filter the report by areaand time period. The report shall also include activity from sub-areas (nested areas).

d. Through people counting, the ACS shall be able to generate First Person In and Last Person Outevents. The First Person In event shall detect when the first cardholder enters an empty area. TheLast Person Out event shall detect when the last cardholder leaves an area. It shall be possible totrigger actions from both events such as sending a message or triggering an alarm.

e. The ACS shall be able to determine the entry of a cardholder based on a dedicated sensor11. Custom Fields (User-Defined Fields)

a. The ACS shall permit the creation of custom fields. Up to 1,000 custom fields shall be supported.b. Custom fields shall be supported for the following entities: cardholders, cardholder groups,

credentials, and visitors.c. Supported custom fields shall include: text, integers, decimal Numbers, dates, boolean, and

images (graphics).d. Users shall be able to define a default value for a custom field.e. The creation of new custom field types shall be possible. New custom field types shall be based on

the standard custom fields supported. They shall support user-defined values from which anoperator must make a selection.

f. Administrators have the ability to define which users can view and modify specific custom fields.This shall limit the access to custom field data to users with pre-defined privileges. The ACS shallsupport querying and report generation using custom fields.

g. Custom fields can be grouped and ordered within these groups as defined by the user.h. Values for custom fields can be imported using the Import Tool.

12. Import Toola. The ACS shall support an integrated Import Tool to facilitate the import of existing cardholder and

credential data. The import of data shall be through the use the CSV file format. The tool shall beavailable from the Configuration UI.


b. The Import Tool shall also support the ability to manually import data that has been exported froma third party database if it is in CSV format.

c. The import tool shall permit the import of the following data:1) Cardholder name, descriptions, picture, email, and status.2) Cardholder group information.3) Credential name, status, format, and card number (including credentials with custom

formats).4) Partition information.5) Custom fields.

d. Full flexibility in selecting the fields to be imported during an import session shall be available.e. The option to use a custom and unique cardholder key shall be specified during the import process

to ensure that cardholders with duplicate names will not have their data overwritten. Cardholderkey generation shall be automated. The end user shall have the option to select which fields willbe used to create this unique key, e.g. credential number, custom fields, cardholder name.

f. The ACS shall also support re-importing a CSV file containing new information to update existinginformation in the ACS database. Re-importing shall enable bulk amendments to existing accesscontrol data.

13. Web Clienta. The Web Client shall allow users to perform the configuration, management, and reporting

activities of the ACS.b. The Web Client shall be accessible through Microsoft Internet Explorer. It shall be a truly thin client.

It shall not require the download of any ACS-specific files or executables onto the clientworkstation.

c. Functionality available through the web client includes:1) Configuration and management of cardholders and cardholder groups.2) Configuration and management of credentials.3) Configuration and management of access rules.4) Badge printing over the network.5) Assignment of access rules to doors and areas.6) Visitor management including visitor check-in and check-out and reporting.7) Advanced reporting.

2.09 COMPONENTSA. Provide modifications and extensions to existing video surveillance system and new access control system

consisting of all required equipment, conduit, boxes, wiring, connectors, hardware, supports, accessories,software, system programming, etc. as necessary for a complete operating system that provides thefunctional intent indicated.

B. Cameras:1. 360 degree camera: Arecont Vision SurroundVideo Omni G2

a. 12-20 Megapixelb. Remote focusc. Adjustable 3-axis gimbald. Multiple lensese. True day/night functionality with mechanical IR cut filterf. Forensic zoomingg. Privacy mask, motion detection, flexible cropping, bit rate control and multi-streaming.h. Dual encoder H.264/MJPEGi. PoE and auxiliary powerj. Low profile housingk. Outdoor rated IP66 and IK 10 impact resistant housingl. Ceiling mount bracket and pendant stem.

2. 180 degree cameras: Arecont Vision SurroundVideo G5a. 5, 12, or 20 Megapixel to suit applicationb. True day/night functionality with mechanical IR cut filterc. Four integrated motorized P-iris lenses with remote focusd. Privacy mask, motion detection, flexible cropping, bit rate control and multi-streaming.e. Adjustable 2-axis camera gimbal with 360 degree pan and 90 degree tiltf. PoE and auxiliary powerg. Outdoor rated housing


h. Wall or post mounting brackets to suit application.3. Fixed cameras: Arecont Vision MegaDome 2

a. 1.2-10 Megapixelb. Remote focus/zoom motorized auto-iris or P-iris lensc. Wide angle lensd. True day/night functionality with mechanical IR cut filtere. Privacy mask, motion detection, flexible cropping, bit rate control, multi-streaming, forensic

zooming, and non-integer scaling.f. PoE and auxiliary powerg. Outdoor rated IP66 and IK 10 impact resistant housingh. Adjustable 3-axis gimbali. Wall or ceiling mounting brackets to suit application.

4. License Plate Recognition Cameras: Genetec AutoVu Sharp XGAa. Monochrome progressive scan ALPR camera with a resolution of 1024X946(XGA) @ 30fps.b. Color context camera with a resolution of 640x480 @ 30fpsc. The ALPR camera shall be able to be equipped with a 12mm, 16mm, 25mm, 35mm or 50mm lensd. Operating temperature range from -4°F to 140°F (-20°C to 60°C), with an extended temperature

option ranging from -40°F to 140°F (-40°C to 60°C)e. The camera unit shall resist shock according to standard MIL-STD 810G 516.6f. Sealed according to standard IP67 IEC 60529g. Extruded aluminum housingh. T-Slots on either side for universal mountingi. The camera unit shall have following available mounting accessories:

1) Magnetic mount with clip2) Double Magnetic mount with clip3) Lightbar mount4) Hard mount5) Snow, rain, and sun visor6) Provide accessories to suit application

j. Integrated pulsed LED illuminator available in 850nm or 740nm or 590nm wavelengthsk. Up to a 100-foot (30-meter) reading range with XGAl. The camera has dynamic exposure allowing all-weather reading of dirty or obstructed plates. The

camera can read at skew angles up to 45 degreesm. The color context camera uses CMOS technology to capture color images in low light conditions.n. Status LED can be disabled for covert operationso. Ability to read multiple lanes of traffic in a mobile deployment

5. Intercom/Camera Substation: Commend C-SIP-WS201V CAa. Wallmount intercom/camera stationb. IP communication via SIPc. Vandal resistant designd. Integrated AXIS colour video camera with illuminatione. Poke protected and fitted with special security screwsf. Front panel made from 3 mm thick V-2A steelg. Back-lit call button and label area

C. Proximity Readers: HID RP151. Utilizes 125 kHz RF communication with compatible credentials.2. Low profile, rugged, weatherized polycarbonate sealed enclosure with multi-color LED's and a sounder

for access granted and denied indications.3. Mountable indoor or outdoor.4. Mullion or door frame mounted where indicated.

D. Proximity Readers: HID RP401. Utilizes 125 kHz RF communication with compatible credentials.2. Low profile, rugged, weatherized polycarbonate sealed enclosure with multi-color LED's and a sounder

for access granted and denied indications.3. Mountable indoor or outdoor.4. Single gang wall mounted where indicated.

E. Door Position Switches: Sentrol 1078CW


1. Magnetic Contacts: Encapsulated reed switch(es) and separate magnet; designed to monitoropened/closed position of doors.

2. Recessed in door frame.F. Cards: HID iClass Cards

1. Smart cards based on secure, open technology to manage and authenticate identities.2. 16K-Bytes memory3. AES-128 bits cryptographic algorithms for data protection.4. Initial quantity: 200

G. Door Locking Devices (Electric Strikes and Magnetic Locks): Comply with Section 08 7100.H. Power supplies: The power supplies shall provide power to equipment from a local or centralized location.

2.10 ACCESSORIESA. Provide components as indicated or as required for connection of video surveillance system to devices and

other systems indicated.B. Network switches:

1. Utilize existing network switches for connections of equipment. The Owenr will provide additionalnetwork switches as required.

C. Provide cables as indicated or as required for connections between system components.1. Data Cables for IP Network Connections: Unshielded twisted pair (UTP), Category 6, complying with

Section 27 1005.D. Provide accessory racks/cabinets as indicated or as required for equipment mounting.E. Lightning Protection

1. The Contractor shall provide suitable lightning protection for all video equipment.2. All lightning protection equipment shall be UL listed.

F. Surge Protection1. The Contractor shall provide suitable surge protection for all video equipment.


A. Verify that field measurements are as shown on the drawings.B. Verify that ratings and configurations of system components are consistent with the indicated requirements.C. Verify that mounting surfaces are ready to receive system components.D. Verify that branch circuit wiring installation is completed, tested, and ready for connection to system.E. Verify that conditions are satisfactory for installation prior to starting work.

3.02 INSTALLATIONA. Install systems in accordance with NECA 1 (general workmanship) and NECA 303.B. Install products in accordance with manufacturer's instructions.C. Provide required support and attachment in accordance with Section 26 0529.D. Wiring Method: Unless otherwise indicated, use cables (not in conduit).

1. Use suitable listed cables in wet locations, including underground raceways.2. Use suitable listed cables for vertical riser applications.3. Use listed plenum rated cables in spaces used for environmental air.4. Install wiring in conduit for the following:

a. Where required for rough-in.b. Where required by authorities having jurisdiction.c. Where exposed to damage.d. Where installed outside the building.e. For exposed connections from outlet boxes to cameras.

5. Conduit: Comply with Section 26 0534.6. Conceal all cables unless specifically indicated to be exposed.7. Route exposed cables parallel or perpendicular to building structural members and surfaces.

E. Provide grounding and bonding in accordance with Section 26 0526.F. Identify system wiring and components in accordance with Section 26 0553.


G. Power shall only be applied to the system after re-checking for proper grounding of the system andmeasuring all loops for lack of shorts, grounds, and open circuits.

H. Arrange for obtaining all programming information prior to bringing the system to the project site.I. All equipment shall be bench tested prior to delivery to job site and prior to installation. Bench test per

manufacturer's installation instructions.J. Wire And Cable:

1. Design, layout, size, and plan new wire and cable runs as required.2. All wire and cable from the Head-end to all cameras shall be “home-run” unless otherwise specified.3. All wire and cable passing through metalwork shall be sleeved by an approved grommet or bushing.4. Avoid splicing conductors. All splices shall be made in junction boxes (except at equipment). Splices

shall be made with an approved connection. Wire nuts shall not be used on any low-voltage wiring.5. Identify all wire and cable at terminations and at every junction box. Identification shall be made with an

approved permanent label.6. Provide cabling for camera system in accordance with Section 27 1005.

K. Wire And Cable Terminations1. Identify all inputs and outputs on terminal strips with permanent marking labels.2. Neatly dress and tie all wiring. The length of conductors within enclosures shall be sufficient to neatly

train the conductor to the terminal point with no excess. Run all wire and cable parallel or normal towalls, floors and ground.

3. Install connectors as required by equipment manufacturers.4. Terminations shall be made so that there is no bare conductor at the terminal. The conductor insulation

shall bear against the terminal or connector shoulder.5. Do not obstruct equipment controls or indicators with wire or cable. Route wire and cable away from

heat producing components such as resistors and regulators.L. Interface with Other Systems:

1. Provide products compatible with other systems requiring interface with video surveillance and accesscontrol systems.

3.03 FIELD QUALITY CONTROLA. See Section 01 4000 - Quality Requirements, for additional requirements.B. Prepare and start system in accordance with manufacturer's instructions.C. Adjust cameras to provide desired field of view and produce suitable images under all service lighting

conditions. Evaluate and adjust all existing cameras in addition to the new cameras.D. Program system parameters according to requirements of Owner.E. Test for proper interface with other systems.F. Correct defective work, adjust for proper operation, and retest until entire system complies with contract

documents.G. Provide the services of manufacturer's technical representative to prepare and start systems and supervise

final wiring connections and system adjustments.3.04 ADJUSTING

A. Adjust manual lens irises to meet lighting conditions.3.05 DEPLOYMENT SERVICES AND SYSTEM COMMISSIONING

A. General1. The contractor shall engage the services of the USP vendor to assist in the management of the

deployment of the USP at the end-user site on projects that involve:a. Multiple contractors or subcontractors that will be responsible for deploying the USP at multiple

client sites in different geographical regions.b. Complex enterprise installations involving advanced functionality (e.g. Federation, failover, plugins)

and/or multiple systems (e.g. access control, video, ALPR) and/or third party integrations.c. Extensive use of customized solutions/plugins developed by the vendor that will be integrated into

the USP.2. The USP vendor services shall include Deployment Management and System Configuration and

Commissioning.B. Deployment Management Service


1. The Deployment Management service from the vendor shall include a Project Manager acting as thesingle point of contact for all communications between the contractor and the vendor organization andwho will be responsible for:a. Conducting a Risk Assessment of the impact of potential risk factors on the operation of the

vendor's USP.b. Providing a project plan for the deployment of the vendor's USP.c. Managing the development and deployment of the custom solution components that will be

integrated into the vendor's USP (if applicable).d. Providing a scope of work detailing the services to be provided by the vendor to assist in the

deployment of the vendor’s USP.e. Coordinating and scheduling the vendor field services with the contractor to assist with the

deployment of the vendor’s USP.f. Providing regular project status updates to the contractor regarding the development of custom

solutions (if applicable) and the deployment of the vendor’s USP.C. System Configuration and Commissioning Service

1. The System Configuration and Commissioning service from the vendor shall include a Field Engineerwho will be responsible for:a. Assisting the contractor’s or subcontractor’s onsite/remote technicians with the configuration and

commissioning of the vendor’s USP at the client site.b. Conducting a test of the USP following the deployment of the system using real-world operator

scenarios to ensure optimal system performance.c. Providing the contractor with a Service Report detailing the tasks completed during the deployment

of the USP at the client site, as well as any recommendations for improving the performance of theUSP that must be implemented by the contractor.

d. Providing a knowledge transfer of the vendor's USP to the contractor following the deployment ofthe USP at the client site.

D. Demonstration: Demonstrate proper operation of system to Owner, and correct deficiencies or makeadjustments as directed.

E. Training: Train Owner's personnel on operation, adjustment, and maintenance of system.1. Use operation and maintenance manual as training reference, supplemented with additional training

materials as required.2. Provide minimum of four hours of training.3. Instructor: Manufacturer's authorized representative.4. Location: At project site.

3.06 PROTECTIONA. Protect installed system components from subsequent construction operations.

3.07 MAINTENANCEA. Provide to Owner, at no extra cost, a separate maintenance contract for the service and maintenance of

unified security system for two years from date of Substantial Completion; Include a complete description ofpreventive maintenance, systematic examination, adjustment, cleaning, inspection, and testing, with adetailed schedule.

B. Conduct site visit at least once every six months to perform inspection, testing, and preventive maintenance.Submit report to Owner indicating maintenance performed along with evaluations and recommendations.

END OF SECTION