28 13 00 Physical Access Control System.pdf

PDF 292 KB Posted

Attached to
CATH LAB Federal contract opportunity
Solicitation number
36C24720B0024
Issued by
Department of Veterans Affairs Veterans Health Administration Veterans Integrated Service Network 7

About this file

This document outlines requirements for a Physical Access Control System (PACS) project at a Department of Veterans Affairs medical facility. The project scope includes removing existing Cath Lab equipment and replacing it with a new GE system, Stryker boom, and Cleansuite ceiling system. The document provides detailed technical requirements for the various PACS components to be installed, including physical access control, application software, system database, surge protection, workstations, controllers, card readers, biometric verification, enrollment capabilities, sensors, interfaces and integration requirements. The PACS must meet specified capacity limits and comply with standards for security, authentication, encryption, and redundancy.

2.4 CARD READERS A. Card Readers shall be provided as specified in the Contract Documents and shall meet the following minimum requirements: 1. Readers shall be contactless smart card readers compliant with ISO 14443 A/B, ISO 15693, and MIFARE. 2. Readers shall be dual-frequency capable of reading 13.56 MHz cards and contactless cards. 3. Readers shall support the following card technologies: a. Contactless ISO 14443 A/B b. Contactless ISO 15693 c. MIFARE Classic 1k d. MIFARE Ultralight e. MIFARE DESFire EV1/EV2 4. Readers shall be Open Standard and support the following card operating systems: a. Java Card b. MIFARE c. COS d. MultOS e. T=CL f. Calypso 5. Readers shall support the following card and credential formats: a. Visual card formats compliant with FIPS 201 and ISO/IEC 7810 ID-1 b. Magnetic stripe format compliant with ISO 7811 6. Readers shall support the following authentication mechanisms: a. Card Authentication Key (CAK) b. PIV authentication c. BIO/BIO-A d. FASC-N/PIV authentication e. PIV digital signature 7. Readers shall support the following data exchange protocols: a. PC/SC b. ISO7816 T=0, T=1 protocols c. EMV Level 1, Level 2 protocols 8. Readers shall support the following security standards: a. FIPS 140-2 Level 1 validated cryptographic module b. FIPS 201 validated for PIV card and credential processing c. NIST SP 800-73, 800-76 and 800-78 compliant 9. Readers

View the file

Other files for this federal contract opportunity

Other files attached to CATH LAB, newest first.
File Type Posted
Project 534-CSI-555 Cardiac Lab Prep Pre-Bid Sign-In.pdf PDF
PreBid Site Visit Sign In sheet.doc DOC document
Project No. 534-CSI-555 Card Cath Lab Questions from 8-26-2020.docx DOCX document
36C24720B0024 A00003.pdf PDF
26 08 00 Commissioning of Electrical Systems.pdf PDF
Project 534-CSI-555 Answers to Questions.pdf PDF
MD-100 - MECHANICAL - SECOND FLOOR - DEMOLITION - DUCTWORK.pdf PDF
MH-200 - SECOND FLOOR - NEW WORK - DUCTWORK.pdf PDF
EP-201 - ELECTRICAL - SECOND FLOOR - POWER SYSTEMS.pdf PDF
280800 Commissioning of Electronic Safety and Security Systems.pdf PDF
M-004 - MECHANICAL - SCHEDULES.pdf PDF
Addendum 2 - Project No. 534-CSI-555.pdf PDF
ED-100 - ELECTRICAL - SECOND FLOOR - DEMOLITION.pdf PDF
270800 Commissioning of Communications Systems.pdf PDF
01 91 00 Commissioning.pdf PDF
226300 - GAS SYSTEMS FOR LABORATORY AND HEALTHCARE FACILITIES.pdf PDF
S02 36C24720B0024 A00002.pdf PDF
MD-101 - MECHANICAL - SECOND FLOOR - DEMOLITION - PIPING.pdf PDF
230711 HVAC INSULATION.pdf PDF
000110 Specifications.pdf PDF
MP-201 - SECOND FLOOR - NEW WORK - PIPING.pdf PDF
M-005 - MECHANICAL - SCHEDULES.pdf PDF
Card Cath Lab Prep Dwgs ED100 ED10 EL200 EP-201.pdf PDF
20200508-VAMCCHSSC-CLSP-DRAWINGS-BIDDOCUMENTS-COMPLETE.pdf PDF
36C24720B0024 A00001.pdf PDF
20200511 - VAMC CHSSC - CLSP - Project Manual SPECS - BID DOCUMENTS - Combined - REV 3.pdf PDF
36C24720B0024 Drawing Bid Documents.pdf PDF
20200511 - VAMC CHSSC - CLSP - Project Manual SPECS - BID DOCUMENTS - Combined - REV 3.zip ZIP file
Addendum 1.pdf PDF
S02 36C24720B0024 Solicitation.pdf PDF
S02 36C24720B0024 CATH Lab Solicitation.pdf PDF
Bid Drawings Document.pdf PDF
SC Wage Determination SC20190023.pdf PDF
Specs Bid Documents.pdf PDF
Show all 34

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

SECTION 28 13 00

PHYSICAL ACCESS CONTROL SYSTEM

PART 1 – GENERAL

1.1 DESCRIPTION

A. Provide and install new equipment and wiring back to the existing JCI

Physical Access Control System, hereinafter referred to as PACS, as specified in this section. Include all cabling, equipment, door controllers, power supplies, software, firmware, licensing, programming, testing, and integration upgrades to the existing JCI

P2000 system for a fully operational system.

B. This Section includes a Physical Access Control System consisting of the required software modifications, power supplies and field-installed

Controllers, necessary to upgrade the existing JCI P2000 system, connected by a high-speed electronic data transmission network. The PACS shall have the following:

1. Physical Access Control:

a. Regulating access through doors and gates

b. Anti-passback

c. Visitor assignment

d. Surge and tamper protection

e. Secondary alarm annunciator

f. Credential cards and readers

g. Biometric identity verification equipment

h. Push-button switches

i. RS-232 ASCII interface

j. Credential creation and credential holder database and management

k. Monitoring of field-installed devices

l. Interface with Pneumatic Tube System.

m. Reporting

2. Security:

a. Real-time guard tour.

b. Time and attendance.

c. Key tracking.

d. Video and camera control.

e. Time and attendance

C. System Architecture:

1. Criticality, operational requirements, and/or limiting points of failure may dictate the development of an enterprise and regional

10-11

28 13 00 - 1 server architecture as opposed to system capacity. Provide server and workstation configurations with all necessary connectors, interfaces and accessories as shown.

D. PACS shall provide secure and reliable identification of Federal employees and contractors by utilizing credential authentication per FIPS-201.

E. Physical Access Control System (PACS) shall consist of:

1. Modifications to Head-End equipment server,

2. Modifications to networked PC-based workstations,

3. Modifications to Physical Access Control System and

Database Management Software,

4. Credential validation software/hardware,

5. Field installed controllers,

6. Modifications to PIV Middleware,

7. Card readers,

8. Biometric identification devices,

9. PIV cards,

10. Supportive information system,

11. Door locks and sensors,

12. Power supplies,

13. Interfaces with:

a. Automatic door operators,

b. Fire Protection System, F. Head-End equipment server, workstations and controllers shall be connected by a high-speed electronic data transmission network.

G. Information system supporting PACS, Head-End equipment server, workstations, network switches, routers and controllers shall comply with FIPS 200 requirements (Minimum Security Requirements for Federal

Information and Information Systems)and NIST Special Publication 800-

53 (Recommended Security Controls for Federal Information Systems).

H. PACS system shall support:

1. Multiple credential authentication modes,

2. Bidirectional communication with the reader,

3. Incident response policy implementation capability; system shall have capability to automatically change access privileges

28 13 00 - 2 for certain user groups to high security areas in case of incident/emergency.

4. Visitor management, I. All security relevant decisions shall be made on “secure side of the door”. Secure side processing shall include;

1. Challenge/response management,

2. PKI path discovery and validation,

3. Credential identifier processing,

4. Authorization decisions.

J. For locations where secure side processing is not applicable the tamper switches and certified cryptographic processing shall be provided per FIPS-140-2.

K. System Software: Based on central-station, workstation operating system, server operating system, and application software.

L. Software and controllers shall be capable of matching full 56 bit

FASC- N plus minimum of 32 bits of public key certificate data.

M. Software shall have the following capabilities:

1. Multiuser multitasking to allow for independent activities and monitoring to occur simultaneously at different workstations.

2. Support authentication and enrolment;

a. PIV verification,

b. Expiration date check,

c. Biometric check,

d. Digital photo display/check,

e. Validate digital signatures of data objects (Objects are signed by the Trusted Authority

f. Private key challenge (CAK & PAK to verify private key public key pairs exist and card is not a clone)

3. Support CRL validation via OCSP or SCVP on a scheduled basis and automatically deny access to any revoked credential in the system.

4. Graphical user interface to show pull-down menus and a menu tree format that complies with interface guidelines of Microsoft

Windows operating system.

5. System license shall be for the entire system and shall include capability for future additions that are within the indicated system size limits specified in this Section.

28 13 00 - 3

6. System shall have open architecture that allows importing and exporting of data and interfacing with other systems that are compatible with existing operating system.

7. Operator login and access shall be utilized via integrated smart card reader and password protection.

N. Systems Networks:

1. A standalone system network shall interconnect all components of the system. This network shall include communications between a central station and any peer or subordinate workstations, enrollment

This Section includes a Physical Access Control System consisting of a system server, [one or more networked workstation computers,] operating system and application software, and field-installed Controllers connected by a high-speed electronic data transmission network. The

PACS shall have the following:

1. Physical Access Control:

a. Regulating access through doors

b. Anti-passback

c. Visitor assignment

d. Surge and tamper protection

e. Secondary alarm annunciator

f. Credential cards and readers

g. Biometric identity verification equipment

h. Push-button switches

i. RS-232 ASCII interface

j. Credential creation and credential holder database and management

k. Monitoring of field-installed devices

l. Interface with [paging] [HVAC] [elevator control] <Insert other> systems.

m. Reporting

2. Security:

a. Real-time guard tour.

b. Time and attendance.

c. Key tracking.

d. Video and camera control.

e. Time and attendance

C. System Architecture:

28 13 00 - 4

1. Criticality, operational requirements, and/or limiting points of failure may dictate the development of an enterprise and regional server architecture as opposed to system capacity. Provide server and workstation configurations with all necessary connectors, interfaces and accessories as shown.

D. PACS shall provide secure and reliable identification of Federal employees and contractors by utilizing credential authentication per

FIPS-201.

E. Physical Access Control System (PACS) shall consist of:

1. Head-End equipment server,

2. One or more networked PC-based workstations,

3. Physical Access Control System and Database Management Software,

4. Credential validation software/hardware,

5. Field installed controllers,

6. PIV Middelware,

7. Card readers,

8. Biometric identification devices,

9. PIV, CAC cards,

10. Supportive information system,

11. Door locks and sensors,

12. Power supplies,

13. Interfaces with:

a. Automatic door operators,

b. Fire Alarm System

14. List of system Components.

F. Head-End equipment server, workstations and controllers shall be connected by a high-speed electronic data transmission network.

G. Information system supporting PACS , Head-End equipment server, workstations, network switches, routers and controllers shall comply with FIPS 200 requirements (Minimum Security Requirements for Federal

Information and Information Systems)and NIST Special Publication 800-53

(Recommended Security Controls for Federal Information Systems).

H. PACS system shall support:

1. Multiple credential authentication modes,

2. Bidirectional communication with the reader,

3. Incident response policy implementation capability; system shall have capability to automatically change access privileges for

28 13 00 - 5 certain user groups to high security areas in case of incident/emergency.

4. Visitor management, I. All security relevant decisions shall be made on “secure side of the door”. Secure side processing shall include;

1. Challenge/response management,

2. PKI path discovery and validation,

3. Credential identifier processing,

4. Authorization decisions.

J. For locations where secure side processing is not applicable the tamper switches and certified cryptographic processing shall be provided per

FIPS-140-2.

K. System Software: Based on <Insert name of operating system> central-station, workstation operating system, server operating system, and application software.

L. Software and controllers shall be capable of matching full 56 bit FASC-

N plus minimum of 32 bits of public key certificate data.

M. Software shall have the following capabilities:

1. Multiuser multitasking to allow for independent activities and monitoring to occur simultaneously at different workstations.

2. Support authentication and enrolment;

a. PIV verification,

b. Expiration date check,

c. Biometric check,

d. Digital photo display/check,

e. Validate digital signatures of data objects (Objects are signed by the Trusted Authority

f. Private key challenge (CAK & PAK to verify private key public key pairs exist and card is not a clone)

3. Support CRL validation via OCSP or SCVP on a scheduled basis and automatically deny access to any revoked credential in the system.

4. Graphical user interface to show pull-down menus and a menu tree format that complies with interface guidelines of Microsoft Windows operating system.

5. System license shall be for the entire system and shall include capability for future additions that are within the indicated system size limits specified in this Section.

28 13 00 - 6

6. System shall have open architecture that allows importing and exporting of data and interfacing with other systems that are compatible with <insert operating system> operating system.

7. Operator login and access shall be utilized via integrated smart card reader and password protection.

N. Systems Networks:

1. A standalone system network shall interconnect all components of the system. This network shall include communications between a central station and any peer or subordinate workstations, enrollment stations, local annunciation stations, portal control stations or redundant central stations.

O. Security Management System Server Redundancy:

1. The SMS shall support multiple levels of fault tolerance and SMS redundancy listed and described below:

a. Hot Standby Servers

b. Clustering

c. Disk Mirroring

d. RAID Level 10

e. Distributed Intelligence

P. Number of points:

1. PACS shall support multiple autonomous regional servers that can connect to a master command and controller server.

2. Unlimited number of access control readers, unlimited number of inputs or outputs, unlimited number of client workstations, unlimited number of cardholders.

3. Total system solution to enable enterprise-wide, networked, multi-user access to all system resources via a wide range of options for connectivity with the customer’s existing LAN and WAN.

Q. Console Network:

1. Console network, if required, shall provide communication between a central station and any subordinate or separate stations of the system. Where redundant central or parallel stations are required, the console network shall allow the configuration of stations as master and slave. The console network may be a part of the field device network or may be separate depending upon the manufacturer's system configuration.

28 13 00 - 7

R. Network(s) connecting PCs and Controllers shall comply with NIST

Special Publication 800-53 (Recommended Security Controls for Federal

Information Systems) and consist of one or more of the following:

1. Local area, IEEE 802.3 Fast Ethernet [10 BASE-T] [100 BASE-TX], star topology network based on TCP/IP.

2. Direct-connected, RS-232 cable from the COM port of the Central

Station to the first Controller, then RS-485 to interconnect the remainder of the Controllers at that Location.

1.2 RELATED WORK

A. Section 07 84 00 - FIRESTOPPING. Requirements for firestopping application and use.

B. Section 08 71 00 - DOOR HARDWARE. Requirements for door installation.

C. Section 26 05 21 - LOW VOLTAGE ELECTRICAL POWER CONDUCTORS AND CABLES

(600 VOLTS AND BELOW). Requirements for power cables.

D. Section 26 05 33 – RACEWAYS AND BOXES FOR ELECTRICAL SYSTEMS.

Requirements for infrastructure.

E. Section 28 05 00 - COMMON WORK RESULTS FOR ELECTRONIC SAFETY AND

SECURITY. For general requirements that are common to more than one section in Division 28.

F. Section 28 05 13 - CONDUCTORS AND CABLES FOR ELECTRONIC SAFETY AND

SECURITY. Requirements for conductors and cables.

G. Section 28 05 26 - GROUNDING AND BONDING FOR ELECTRONIC SAFETY AND

SECURITY. Requirements for grounding of equipment.

H. Section 28 05 28.33 - CONDUITS AND BOXES FOR ELECTRONIC SAFETY AND

SECURITY. Requirements for infrastructure.

I. Section 28 08 00 - COMMISIONING OF ELECTRONIC SAFETY AND SECURITY. For requirements for commissioning, systems readiness checklists, and training.

J. Section 28 31 00 - FIRE DETECTION AND ALARM. Requirements for integration with fire detection and alarm system.

1.3 QUALITY ASSURANCE

A. The Contractor shall be responsible for providing, installing, and the operation of the PACS as shown. The Contractor shall also provide certification as required.

B. The security system will be installed and tested to ensure all components are fully compatible as a system and can be integrated with all associated security subsystems, whether the security system is

28 13 00 - 8 stand-alone or a part of a complete Information Technology (IT) computer network.

C. Manufacturers Qualifications: The manufacturer shall regularly and presently produce, as one of the manufacturer's principal products, the equipment and material specified for this project, and shall have manufactured the item for at least three years.

D. Product Qualifications:

1. Manufacturer's product shall have been in satisfactory operation, on three installations of similar size and type as this project, for approximately three years.

2. The Government reserves the right to require the Contractor to submit a list of installations where the products have been in operation before approval.

E. Contractor Qualifications:

1. The Contractor or security sub-contractor shall be a licensed security Contractor with a minimum of five (5) years experience installing and servicing systems of similar scope and complexity.

The Contractor shall be an authorized regional representative of the

Security Management System’s (PACS) manufacturer. The Contractor shall provide four (4) current references from clients with systems of similar scope and complexity which became operational in the past three (3) years. At least three (3) of the references shall be utilizing the same system components, in a similar configuration as the proposed system. The references must include a current point of contact, company or agency name, address, telephone number, complete system description, date of completion, and approximate cost of the project. The owner reserves the option to visit the reference sites, with the site owner’s permission and representative, to verify the quality of installation and the references’ level of satisfaction with the system. The Contractor shall provide copies of system manufacturer certification for all technicians. The

Contractor shall only utilize factory-trained technicians to install, program, and service the PACS. The Contractor shall only utilize factory-trained technicians to install, terminate and service controller/field panels and reader modules. The technicians shall have a minimum of five (5) continuous years of technical experience in electronic security systems. The Contractor shall have a local service facility. The facility shall be located within

28 13 00 - 9

60 miles of the project site. The local facility shall include sufficient spare parts inventory to support the service requirements associated with this contract. The facility shall also include appropriate diagnostic equipment to perform diagnostic procedures.

The Resident Engineer reserves the option of surveying the company’s facility to verify the service inventory and presence of a local service organization.

a. The Contractor shall provide proof project superintendent with

BICSI Certified Commercial Installer Level 1, Level 2, or

Technician to provide oversight of the project.

b. Cable installer must have on staff a Registered Communication

Distribution Designer (RCDD) certified by Building Industry

Consulting Service International. The staff member shall provide consistent oversight of the project cabling throughout design, layout, installation, termination and testing.

F. Service Qualifications: There shall be a permanent service organization maintained or trained by the manufacturer which will render satisfactory service to this installation within four hours of receipt of notification that service is needed. Submit name and address of service organizations.

1.4 SUBMITTALS

A. Submit below items in conjunction with Master Specification Sections 01

33 23, SHOP DRAWINGS, PRODUCT DATA, AND SAMPLES, Section 02 41 00, DEMOLITION, and Section 28 05 00 COMMON WORK RESULTS FOR ELECTRONIC

SAFETY AND SECURITY.

B. Provide certificates of compliance with Section 1.3, Quality Assurance.

C. Provide a complete and thorough pre-installation and as-built design package in both electronic format and on paper, minimum size 48 x 48 inches (1220 x 1220 millimeters); drawing submittals shall be per the established project schedule.

D. Shop drawing and as-built packages shall include, but not be limited to:

1. Index Sheet that shall:

a. Define each page of the design package to include facility name, building name, floor, and sheet number.

b. Provide a complete list of all security abbreviations and symbols.

28 13 00 - 10

c. Reference all general notes that are utilized within the design package.

d. Specification and scope of work pages for all individual security systems that are applicable to the design package that will:

1) Outline all general and job specific work required within the design package.

2) Provide a detailed device identification table outlining device Identification (ID) and use for all security systems equipment utilized in the design package.

2. Drawing sheets that will be plotted on the individual floor plans or site plans shall:

a. Include a title block as defined above.

b. Clearly define the drawings scale in both standard and metric measurements.

c. Provide device identification and location.

d. Address all signal and power conduit runs and sizes that are associated with the design of the electronic security system and other security elements (e.g., barriers, etc.).

e. Identify all pull box and conduit locations, sizes, and fill capacities.

f. Address all general and drawing specific notes for a particular drawing sheet.

3. A detailed riser drawing for each applicable security subsystem shall:

a. Indicate the sequence of operation.

b. Relationship of integrated components on one diagram.

c. Include the number, size, identification, and maximum lengths of interconnecting wires.

d. Wire/cable types shall be defined by a wire and cable schedule.

The schedule shall utilize a lettering system that will correspond to the wire/cable it represents (example: A = 18 AWG/1

Pair Twisted, Unshielded). This schedule shall also provide the manufacturer’s name and part number for the wire/cable being installed.

4. A detailed system drawing for each applicable security system shall:

a. Clearly identify how all equipment within the system, from main panel to device, shall be laid out and connected.

28 13 00 - 11

b. Provide full detail of all system components wiring from point-to-point.

c. Identify wire types utilized for connection, interconnection with associate security subsystems.

d. Show device locations that correspond to the floor plans.

e. All general and drawing specific notes shall be included with the system drawings.

5. A detailed schedule for all of the applicable security subsystems shall be included. All schedules shall provide the following information:

a. Device ID.

b. Device Location (e.g. site, building, floor, room number, location, and description).

c. Mounting type (e.g. flush, wall, surface, etc.).

d. Power supply or circuit breaker and power panel number.

e. In addition, for the PACS, provide the door ID, door type (e.g.

wood or metal), locking mechanism (e.g. strike or electromagnetic lock) and control device (e.g. card reader or biometrics).

6. Detail and elevation drawings for all devices that define how they were installed and mounted.

E. Pre-installation design packages shall go through a full review process conducted by the Contractor along with a VA representative to ensure all work has been clearly defined and completed. All reviews shall be conducted in accordance with the project schedule. There shall be one

(1) stages to the review process:

100 percent

F. Provide manufacturer security system product cut-sheets. Submit for approval at least 30 days prior to commencement of formal testing, a

Security System Operational Test Plan. Include procedures for operational testing of each component and security subsystem, to include performance of an integrated system test.

G. Submit manufacture’s certification of Underwriters Laboratories, Inc.

(UL) listing as specified. Provide all maintenance and operating manuals per Section 01 00 00, GENERAL REQUIREMENTS, and Section 28 05

00 COMMON WORK RESULTS FOR ELECTRONIC SAFETY AND SECURITY.

H. Completed System Readiness Checklists provided by the Commissioning

Agent and completed by the contractor, signed by a qualified technician and dated on the date of completion, in accordance with the

28 13 00 - 12 requirements of Section 28 08 00 COMMISSIONING OF ELECTRONIC SAFETY AND

SECURITY SYSTEMS.

I. General: Submittals shall be in full compliance of the Contract

Documents. All submittals shall be provided in accordance with this section. Submittals lacking the breath or depth these requirements will be considered incomplete and rejected. Submissions are considered multidisciplinary and shall require coordination with applicable divisions to provide a complete and comprehensive submission package.

Additional general provisions are as follows:

1. The Contractor shall schedule submittals in order to maintain the project schedule. For coordination drawings refer to Specification

Section 01 33 10 - DESIGN SUBMITTAL PROCEDURES, which outline basic submittal requirements and coordination. Section 01 33 10 shall be used in conjunction with this section.

2. The Contractor shall identify variations from requirements of

Contract Documents and state product and system limitations, which may be detrimental to successful performance of the completed work or system.

3. Each package shall be submitted at one (1) time for each review and include components from applicable disciplines (e.g., electrical work, architectural finishes, door hardware, etc.) which are required to produce an accurate and detailed depiction of the project.

4. Manufacturer’s information used for submittal shall have pages with items for approval tagged, items on pages shall be identified, and capacities and performance parameters for review shall be clearly marked through use of an arrow or highlighting. Provide space for

Resident Engineer and Contractor review stamps.

5. Technical Data Drawings shall be in the latest version of AutoCAD®, drawn accurately, and in accordance with VA CAD Standards. FREEHAND

SKETCHES OR COPIED VERSIONS OF THE CONSTRUCTION DOCUMENTS WILL NOT

BE ACCEPTED. The Contractor shall not reproduce Contract Documents or copy standard information as the basis of the Technical Data

Drawings. If departures from the technical data drawings are subsequently deemed necessary by the Contractor, details of such departures and the reasons thereof shall be submitted in writing to the Resident Engineer for approval before the initiation of work.

28 13 00 - 13

6. Packaging: The Contractor shall organize the submissions according to the following packaging requirements.

a. Binders: For each manual, provide heavy duty, commercial quality, durable three (3) ring vinyl covered loose leaf binders, sized to receive 8.5 x 11 in paper, and appropriate capacity to accommodate the contents. Provide a clear plastic sleeve on the spine to hold labels describing the contents. Provide pockets in the covers to receive folded sheets.

1) Where two (2) or more binders are necessary to accommodate data, correlate data in each binder into related groupings according to the Project Manual table of contents. Cross-referencing other binders where necessary to provide essential information for communication of proper operation and or maintenance of the component or system.

2) Identify each binder on the front and spine with printed binder title, Project title or name, and subject matter covered. Indicate the volume number if applicable.

b. Dividers: Provide heavy paper dividers with celluloid tabs for each Section. Mark each tab to indicate contents.

c. Protective Plastic Jackets: Provide protective transparent plastic jackets designed to enclose diagnostic software for computerized electronic equipment.

d. Text Material: Where written material is required as part of the manual use the manufacturer's standard printed material, or if not available, specially prepared data, neatly typewritten on 8.5 inches by 11 inches 20 pound white bond paper.

e. Drawings: Where drawings and/or diagrams are required as part of the manual, provide reinforced punched binder tabs on the drawings and bind them with the text.

1) Where oversized drawings are necessary, fold the drawings to the same size as the text pages and use as a foldout.

2) If drawings are too large to be used practically as a foldout, place the drawing, neatly folded, in the front or rear pocket of the binder. Insert a type written page indicating the drawing title, description of contents and drawing location at the appropriate location of the manual.

3) Drawings shall be sized to ensure details and text is of legible size. Text shall be no less than 1/16” tall.

28 13 00 - 14

f. Manual Content: In each manual include information specified in the individual Specification section, and the following information for each major component of building equipment and controls:

1) General system or equipment description.

2) Design factors and assumptions.

3) Copies of applicable Shop Drawings and Product Data.

4) System or equipment identification including: manufacturer, model and serial numbers of each component, operating instructions, emergency instructions, wiring diagrams, inspection and test procedures, maintenance procedures and schedules, precautions against improper use and maintenance, repair instructions, sources of required maintenance materials and related services, and a manual index.

g. Binder Organization: Organize each manual into separate sections for each piece of related equipment. At a minimum, each manual shall contain a title page, table of contents, copies of Product

Data supplemented by drawings and written text, and copies of each warranty, bond, certifications, and service Contract issued.

Refer to Group I through V Technical Data Package Submittal requirements for required section content.

h. Title Page: Provide a title page as the first sheet of each manual to include the following information; project name and address, subject matter covered by the manual, name and address of the Project, date of the submittal, name, address, and telephone number of the Contractor, and cross references to related systems in other operating and/or maintenance manuals.

i. Table of Contents: After the title page, include a type written table of contents for each volume, arranged systematically according to the Project Manual format. Provide a list of each product included, identified by product name or other appropriate identifying symbols and indexed to the content of the volume.

Where more than one (1) volume is required to hold data for a particular system, provide a comprehensive table of contents for all volumes in each volume of the set.

j. General Information Section: Provide a general information section immediately following the table of contents, listing each product included in the manual, identified by product name.

28 13 00 - 15

Under each product, list the name, address, and telephone number of the installer and maintenance Contractor. In addition, list a local source for replacement parts and equipment.

k. Drawings: Provide specially prepared drawings where necessary to supplement the manufacturers printed data to illustrate the relationship between components of equipment or systems, or provide control or flow diagrams. Coordinate these drawings with information contained in Project Record Drawings to assure correct illustration of the completed installation.

l. Manufacturer’s Data: Where manufacturer's standard printed data is included in the manuals, include only those sheets that are pertinent to the part or product installed. Mark each sheet to identify each part or product included in the installation.

Where more than one (1) item in tabular format is included, identify each item, using appropriate references from the

Contract Documents. Identify data that is applicable to the installation and delete references to information which is not applicable.

m. Where manufacturer's standard printed data is not available and the information is necessary for proper operation and maintenance of equipment or systems, or it is necessary to provide additional information to supplement the data included in the manual, prepare written text to provide the necessary information.

Organize the text in a consistent format under a separate heading for different procedures. Where necessary, provide a logical sequence of instruction for each operating or maintenance procedure. Where similar or more than one product is listed on the submittal the Contractor shall differentiate by highlighting the specific product to be utilized.

n. Calculations: Provide a section for circuit and panel calculations.

o. Loading Sheets: Provide a section for DGP Loading Sheets.

p. Certifications: Provide section for Contractor’s manufacturer certifications.

7. Contractor Review: Review submittals prior to transmittal.

Determine and verify field measurements and field construction criteria. Verify manufacturer’s catalog numbers and conformance of submittal with requirements of contract documents. Return non-

28 13 00 - 16 conforming or incomplete submittals with requirements of the work and contract documents. Apply Contractor’s stamp with signature certifying the review and verification of products occurred, and the field dimensions, adjacent construction, and coordination of information is in accordance with the requirements of the contract documents.

8. Resubmission: Revise and resubmit submittals as required within 15 calendar days of return of submittal. Make resubmissions under procedures specified for initial submittals. Identify all changes made since previous submittal.

9. Product Data: Within 15 calendar days after execution of the contract, the Contractor shall submit for approval a complete list of all of major products proposed for use. The data shall include name of manufacturer, trade name, model number, the associated contract document section number, paragraph number, and the referenced standards for each listed product.

J. Group 1 Technical Data Package: Group I Technical Data Package shall be one submittal consisting of the following content and organization.

Refer to VA Special Conditions Document for drawing format and content requirements. The data package shall include the following:

1. Section I - Drawings:

a. General – Drawings shall conform to VA Special Conditions and CAD

Standards Documents. All text associated with security details shall be 1/8” tall and meet VA text standard for AutoCAD™ drawings.

b. Cover Sheet – Cover sheet shall consist of Project Title and

Address, Project Number, Area and Vicinity Maps.

c. General Information Sheets – General Information Sheets shall consist of General Notes, Abbreviations, Symbols, Wire and Cable

Schedule, Project Phasing, and Sheet Index.

d. Floor Plans – Floor plans shall be produced from the

Architectural backgrounds issued in the Construction Documents.

The contractor shall receive floor plans from the prime A/E to develop these drawing sets. Security devices shall be placed on drawings in scale. All text associated with security details shall be 1/8” tall and meet VA text standard for AutoCAD™ drawings. Floor plans shall identify the following:

1) security devices by symbol, 28 13 00 - 17

2) the associated device point number (derived from the loading sheets),

3) wire & cable types and counts

4) conduit sizing and routing

5) conduit riser systems

6) device and area detail call outs

e. Architectural details – Architectural details shall be produced for each device mounting type (door details for doors with physical access control, reader pedestals and mounts, security panel and power supply details).

f. Riser Diagrams – Contractor shall provide a riser diagram indicating riser architecture and distribution of the physical access control system throughout the facility (or area in scope).

g. Block Diagrams – Contractor shall provide a block diagram for the entire system architecture and interconnections with SMS subsystems. Block diagram shall identify SMS subsystem (e.g., physical access control, intrusion detection, closed circuit television, intercom, and other associated subsystems) integration; and data transmission and media conversion methodologies.

h. Interconnection Diagrams – Contractor shall provide interconnection diagram for each sensor, and device component.

Interconnection diagram shall identify termination locations, standard wire detail to include termination schedule. Diagram shall also identify interfaces to other systems such as elevator control, fire alarm systems, and security management systems.

i. Security Details:

1) Panel Assembly Detail – For each panel assembly, a panel assembly details shall be provided identifying individual panel component size and content.

2) Panel Details – Provide security panel details identify general arrangement of the security system components, backboard size, wire through size and location, and power circuit requirements.

3) Device Mounting Details – Provide mounting detailed drawing for each security device (physical access control system, intrusion detection, video surveillance and assessment, and intercom systems) for each type of wall and ceiling

28 13 00 - 18 configuration in project. Device details shall include device, mounting detail, wiring and conduit routing.

4) Details of connections to power supplies and grounding

5) Details of surge protection device installation

6) Sensor detection patterns – Each system sensor shall have associated detection patterns.

7) Equipment Rack Detail – For each equipment rack, provide a scaled detail of the equipment rack location and rack space utilization. Use of BISCI wire management standards shall be employed to identify wire management methodology. Transitions between equipment racks shall be shown to include use vertical and horizontal latter rack system.

8) Security Control Room – The contractor shall provide a layout plan for the Security Control Room. The layout plan shall identify all equipment and details associated with the installation.

9) Operator Console – The contractor shall provide a layout plan for the Operator Console. The layout plan shall identify all equipment and details associated with the installation.

Equipment room - the contractor shall provide a layout plan for the equipment room. The layout plan shall identify all equipment and details associated with the installation.

10) Equipment Room – Equipment room details shall provide architectural, electrical, mechanical, plumbing, IT/Data and associated equipment and device placements both vertical and horizontally.

j. Electrical Panel Schedule – Electrical Panel Details shall be provided for all SMS systems electrical power circuits. Panel details shall be provided identifying panel type (Standard, Emergency Power, Emergency/Uninterrupted Power Source, and

Uninterrupted Power Source Only), panel location, circuit number, and circuit amperage rating.

k. Door Schedule – A door schedule shall be developed for each door equipped with electronic security components. At a minimum, the door schedule shall be coordinated with Division 08 work and include the following information:

1) Item Number

2) Door Number (Derived from A/E Drawings)

28 13 00 - 19

3) Floor Plan Sheet Number

4) Standard Detail Number

5) Door Description (Derived from Loading Sheets)

6) Data Gathering Panel Input Number

7) Door Position or Monitoring Device Type & Model Number

8) Lock Type, Model Number & Power Input/Draw (standby/active)

9) Card Reader Type & Model Number

10) Shunting Device Type & Model Number

11) Sounder Type & Model Number

12) Manufacturer

13) Misc. devices as required

a) Delayed Egress Type & Model Number

b) Intercom

c) Camera

d) Electric Transfer Hinge

e) Electric Pass-through device

14) Remarks column indicating special notes or door configurations

2.Section II – Data Gathering Panel Documentation Package

a. Contractor shall provide Data Gathering Panel (DGP) input and output documentation packages for review at the Shop Drawing submittal stage and also with the as-built documentation package.

The documentation packages shall be provided in both printed and magnetic form at both review stages.

b. The Contractor shall provide loading sheet documentation package for the associated DGP, including input and output boards for all field panels associated with the project. Documentation shall be provided in current version Microsoft Excel spreadsheets following the format currently utilized by VA. A separate spreadsheet file shall be generated for each DGP and associated field panels.

c. The spreadsheet names shall follow a sequence that shall display the spreadsheets in numerical order according to the DGP system number. The spreadsheet shall include the prefix in the file name that uniquely identifies the project site. The spreadsheet shall detail all connected items such as card readers, alarm inputs, and relay output connections. The spreadsheet shall include an individual section (row) for each panel input, output and card reader. The spreadsheet shall automatically calculate

28 13 00 - 20 the system numbers for card readers, inputs, and outputs based upon data entered in initialization fields.

d. All entries must be verified against the field devices. Copies of the floor plans shall be forwarded under separate cover.

e. The DGP spreadsheet shall include an entry section for the following information:

1) DGP number

2) First Reader Number

3) First Monitor Point Number

4) First Relay Number

5) DGP, input or output Location

6) DGP Chain Number

7) DGP Cabinet Tamper Input Number

8) DGP Power Fail Input Number

9) Number of Monitor Points Reserved For Expansion Boards

10) Number of Control Points (Relays) Reserved For Expansion

Boards

f. The DGP, input module and output module spreadsheets shall automatically calculate the following information based upon the associated entries in the above fields:

1) System Numbers for Card Readers

2) System Numbers for Monitor Point Inputs

3) System Numbers for Control Points (Relays)

4) Next DGP or input module First Monitor Point Number

5) Next DGP or output module First Control Point Number

g. The DGP spreadsheet shall provide the following information for each card reader:

1) DGP Reader Number

2) System Reader Number

3) Cable ID Number

4) Description Field (Room Number)

5) Description Field (Device Type i.e.: In Reader, Out Reader, etc.)

6) Description Field

7) DGP Input Location

8) Date Test

9) Date Passed

10) Cable Type

28 13 00 - 21

11) Camera Numbers (of cameras viewing the reader location)

h. The DGP and input module spreadsheet shall provide the following information for each monitor point (alarm input).

1) DGP Monitor Point Input Number

2) System Monitor Point Number

3) Cable ID Number

4) Description Field (Room Number)

5) Description Field (Device Type i.e.: Door Contact, Motion

Detector, etc.)

6) DGP or input module Input Location

7) Date Test

8) Date Passed

9) Cable Type

10) Camera Numbers (of associated alarm event preset call-ups)

i. The DGP and output module spreadsheet shall provide the following information for each control point (output relay).

1) DGP Control Point (Relay) Number

2) System (Control Point) Number

3) Cable ID Number

4) Description Field (Room Number)

5) Description Field (Device: Lock Control, Local Sounder, etc.)

6) Description Field

7) DGP or OUTPUT MODULE Output Location

8) Date Test

9) Date Passed Cable Type

10) Camera Number (of associated alarm event preset call-ups)

j. The DGP, input module and output module spreadsheet shall include the following information or directions in the header and footer:

1) Header

a) DGP Input and Output Worksheet

b) Enter Beginning Reader, Input, and Output Starting Numbers and Sheet Will Automatically Calculate the Remaining System

Numbers.

2) Footer

a) File Name

b) Date Printed

c) Page Number

K. Group II Technical Data Package

28 13 00 - 22

1. The Contractor shall prepare a report of “Current Site Conditions” and submit a report to the Resident Engineer documenting changes to the site, particularly those conditions that affect performance of the system to be installed. The Contractor shall provide specification sheets, or written functional requirements to support the findings, and a cost estimate to correct those site changes or conditions which affect the installation of the system or its performance. The Contractor shall not correct any deficiency without written permission from the COTR.

2. System Configuration and Functionality: The contractor shall provide the results of the meeting with VA to develop system requirements and functionality including but not limited to:

a. Baseline configuration

b. Access levels

c. Schedules (intrusion detection, physical access control, holidays, etc.)

d. Badge database

e. System monitoring and reporting (unit level and central control)

f. Naming conventions and descriptors

L. Group III Technical Data Package

1. Development of Test Procedures: The Contractor will prepare performance test procedures for the system testing. The test procedures shall follow the format of the VA Testing procedures and be customized to the contract requirements. The Contractor will deliver the test procedures to the Resident Engineer for approval at least 60 calendar days prior to the requested test date.

M. Group IV Technical Data Package

1. Performance Verification Test

a. Based on the successful completion of the pre-delivery test, the

Contractor shall finalize the test procedures and report forms for the performance verification test (PVT) and the endurance test. The PVT shall follow the format, layout and content of the pre-delivery test. The Contractor shall deliver the PVT and endurance test procedures to the Resident Engineer for approval.

The Contractor may schedule the PVT after receiving written approval of the test procedures. The Contractor shall deliver the final PVT and endurance test reports within 14 calendar days

28 13 00 - 23 from completion of the tests. Refer to Part 3 of this section for System Testing and Acceptance requirements.

2. Training Documentation

a. New Facilities and Major Renovations: Familiarization training shall be provided for new equipment or systems. Training can include site familiarization training for VA technicians and administrative personnel. Training shall include general information on new system layout including closet locations, turnover of the completed system including all documentation, including manuals, software, key systems, and full system administration rights. Lesson plans and training manuals training shall be oriented to type of training to be provided.

b. New Unit Control Room:

1) Provide the security personnel with training in the use, operation, and maintenance of the entire control room system

(Unit Control and Equipment Rooms). The training documentation must include the operation and maintenance. The first of the training sessions shall take place prior to system turnover and the second immediately after turnover.

Coordinate the training sessions with the Owner. Completed classroom sessions will be witnessed and documented by the

Architect/Engineer, and approved by the Resident Engineer.

Instruction is not to begin until the system is operational as designed.

2) The training documents will cover the operation and the maintenance manuals and the control console operators’ manuals and service manuals in detail, stressing all important operational and service diagnostic information necessary for the maintenance and operations personnel to efficiently use and maintain all systems.

3) Provide an illustrated control console operator's manual and service manual. The operator's manual shall be written in laymen's language and printed so as to become a permanent reference document for the operators, describing all control panel switch operations, graphic symbol definitions and all indicating functions and a complete explanation of all software.

28 13 00 - 24

4) The service manual shall be written in laymen's language and printed so as to become a permanent reference document for maintenance personnel, describing how to run internal self diagnostic software programs, troubleshoot head end hardware and field devices with a complete scenario simulation of all possible system malfunctions and the appropriate corrective measures.

5) Provide a professional color DVD instructional recording of all the operational procedures described in the operator's manual. All charts used in the training session shall be clearly presented on the video. Any DVD found to be inferior in recording or material content shall be reproduced at no cost until an acceptable DVD is submitted. Provide four copies of the training DVD, one to the architect/engineer and three to the owner.

3. System Configuration and Data Entry:

a. The contractor is responsible for providing all system configuration and data entry for the SMS and subsystems (e.g., video matrix switch, intercom, digital video recorders, network video recorders). All data entry shall be performed per VA standards & guidelines. The Contractor is responsible for participating in all meetings with the client to compile the information needed for data entry. These meetings shall be established at the beginning of the project and incorporated in to the project schedule as a milestone task. The contractor shall be responsible for all data collection, data entry, and system configuration. The contractor shall collect, enter, & program and/or configure the following components:

1) Physical Access control system components,

2) All intrusion detection system components,

3) Video surveillance, control and recording systems,

4) Intercom systems components,

5) All other security subsystems shown in the contract documents.

b. The Contractor is responsible for compiling the card access database for the VA employees, including programming reader configurations, access shifts, schedules, exceptions, card classes and card enrollment databases.

28 13 00 - 25

c. Refer to Part 3 for system programming requirements and planning guidelines.

4. Graphics: Based on CAD as-built drawings developed for the construction project, create all map sets showing locations of all alarms and field devices. Graphical maps of all alarm points installed under this contract including perimeter and exterior alarm points shall be delivered with the system. The Contractor shall create and install all graphics needed to make the system operational. The Contractor shall utilize data from the contract documents, Contractor’s field surveys, and all other pertinent information in the Contractor’s possession to complete the graphics.

The Contractor shall identify and request from the COTR, any additional data needed to provide a complete graphics package.

Graphics shall have sufficient level of detail for the system operator to assess the alarm. The Contractor shall supply hard copy, color examples at least 203.2 x 254 mm (8 x 10 in) of each type of graphic to be used for the completed Security system. The graphics examples shall be delivered to the Resident Engineer for review and approval at least 90 calendar days prior to the scheduled date the Contractor requires them.

N. Group V Technical Data Package: Final copies of the manuals shall be delivered to the Resident Engineer as part of the acceptance test. The draft copy used during site testing shall be updated with any changes required prior to final delivery of the manuals. Each manual’s contents shall be identified on the cover. The manual shall include names, addresses, and telephone numbers of each sub-contractor installing equipment or systems, as well as the nearest service representatives for each item of equipment for each system. The manuals shall include a table of contents and tab sheets. Tab sheets shall be placed at the beginning of each chapter or section and at the beginning of each appendix. The final copies delivered after completion of the endurance test shall include all modifications made during installation, checkout, and acceptance. Two (2) hard-copies and one (1) soft copy on CD of each item listed below shall be delivered as a part of final systems acceptance.

1. Functional Design Manual: The functional design manual shall identify the operational requirements for the entire system and explain the theory of operation, design philosophy, and specific

28 13 00 - 26 functions. A description of hardware and software functions, interfaces, and requirements shall be included for all system operating modes.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .