Attachment_A_-_AAR.pdf

AUTOMATION AND APPLICATION REQUIREMENTS (AAR)

1.1 Project Information Exchange Requirements

1.1.1 – GENERAL

The Contractor shall utilize Newforma Information Exchange (“NIX”) as its project information exchange application with the Board. The Contractor shall also use NIX to transfer information to both the Board and the Board’s Consultant’s if required in the the Contract. NIX is a Web server application that enables the Board’s project team members to easily and securely exchange project files with the Contactor’s project team members (and vice-versa) using a website. NIX enables users to access, upload and download project files, send and view RFI’s and submittals.

Additionally, it provides email notifications, reminders, automated transfer expiration (deletion), and a history log (audit trail) for all posted file transfers.

1.1.2 – NEWFORMA INFO EXCHANGE REQUIREMENTS

a. The Contractor shall utilize the Board’s Newforma Info Exchange website as a means to communicate all project file transfers for the Project’s supporting documents and Contract Deliverables

i. Examples of file transfers include but are not limited to models, drawings, meeting minutes, presentations, photos, reports, schedules, briefings, agendas, work plans, response records, certifications, issuance of bid and construction documents, issuance of supplementary information or instructions, Submittals, Requests for Information, assessment of potential Change Orders, site visit, deficiency and punchlist records.

b. The NIX website will support the Project during all phases of the project.

c. All project files excluding RFI’s and Submittals shall be sent using the Send Files activity center in NIX, see 1.1.2.i for file types examples

d. All RFI’s shall be sent using the “Send RFI” activity center in NIX.

i. Any project related question(s) shall be regarded as an RFI.

e. All Submittals shall be sent using the “Send Submittals” activity center in NIX.

f. All file transfers, RFI’s and submittals shall follow the Board’s naming convention.

g. The Contractor’s key team member(s), excluding Sub-Contractors will be given access to the Boards NIX site after proper documents are filled out and approved by the COR.

It is the Contractors responsibility to transfer information to their Sub-Contractors using and approved application, See 1.2 Applications Requirements.

http://help.newforma.com/robohelp/robo/server/general/projects/Project%20Center%20tenth%20Edition%20Help/Overviews/Project_Overview.htm http://help.newforma.com/robohelp/robo/server/general/projects/Project%20Center%20tenth%20Edition%20Help/Overviews/File_Transfer_Overview.htm http://help.newforma.com/robohelp/robo/server/general/projects/Project%20Center%20tenth%20Edition%20Help/Overviews/File_Transfer_Overview.htm

Board of Governors of the Federal Reserve System Automation and Application Requirements

1.1.3 – NEWFORMA ADDITONAL INFORMATION

a. Newforma releases a new version and updates its application. The Board will communicate with all users when an upgrade or update takes place. The upgrades and updates will not disrupt the project schedule.

b. The Board will provide NIX training to the Contractor.

1.2 Application Requirements

1.2.1 APPLICATION SECURITY

All applications used to store, share, and transfer the Board’s project documents shall meet the Board’s security requirements as described below:

a. To the extent Construction Contractor provides Work that include storage of information belonging to the Board, such Work (“Work”) must comply with the Board’s Information Security Program, which requires compliance with the Federal Information Security Management Act of 2002 (FISMA). In this regard, the Board must assure itself that Construction Contractor has or will implement appropriate security controls for the information system that contains the Board’s information and that the controls for that system are effective. The necessary controls, which depend on the security impact rating assigned to the information by the Board, are outlined in the publication entitled, “Recommended Security Controls for Federal Information Systems,” which can be found at: http://csrc.nist.gov/publications/nistpubs/800-53-Rev2/sp800-53-rev2-final.pdf (the SP 800-53 controls). As applicable, the Board will assign the information security impact rating and the relevant SP 800-53 controls shall apply to information. Therefore, to meet the Board’s obligation of ensuring that Board information is properly protected, Construction Contractor must either:

i. confirm, to the Board’s satisfaction, that it has adopted the FISMA security control standards or security controls that are consistent with FISMA, and provide the Board with supporting documentation that demonstrates the controls are in place and effective;

ii. if Construction Contractor has not adopted formal FISMA security control standards, the Construction Contractor must provide the Board documentation describing the security controls that are in place and their effectiveness, along with any independent evaluation of those controls, such as an acceptable SSAE-16; or

iii. in the alternative, at the Construction Contractor’s preference or if the information provided by Construction Contractor is not sufficient, the Board’s Information Security Officer or other appropriate Board official will conduct an on-site data security review.

http://csrc.nist.gov/publications/nistpubs/800-53-Rev2/sp800-53-rev2-final.pdf

b. If the Services undergone FedRAMP authorization or security assessment and authorization processes, the Board may be able to leverage some of the results of those efforts in determining the extent to which security controls are implemented correctly and operating as intended. However, the Board can only utilize results that are current, correct, and complete. Thus, any leveraged information should not be over six months old, especially if changes to Services have occurred. If there are no existing assessment results, the Board reserves the right to perform a security assessment of the Services based on the Board’s information security requirements. After the Board’s security assessment, the Construction Contractor may be required to create a Plan of Action and Milestones (POA&M) that describes any deficiencies discovered during the assessment, planned corrective measures, and milestones to reduce or eliminate those deficiencies.

c. In addition to the foregoing, the Board reserves the right to perform re-verification of the System’s security controls at a frequency and rigor that is commensurate with the FISMA risk level that is determined to be applicable by Board IT Security. The scope of re-verification may likewise be shaped by prior relevant and timely assessment results, and the Construction Contractor will be required to create or update (as applicable) the POA&M as a result of the re-verification.

d. It is the responsibility of the Construction Contractor to communicate the Application

Security Requirements to their Sub- Contractor(s).

1.3 Safeguarding Building Information

1.3.1– DOCUMENT REQUIREMENTS

a. The disclaimer below (1.3.1.a.i) shall be placed on the cover page of any reports, specs, or documents containing building information. It is the responsibility of the Construction Contractor to communicate this requirement to their Sub- Contractor(s).

i. NON PUBLIC INFORMATION OF THE BOARD OF GOVERNORS OF THE FEDERAL RESERVE SYSTEM WARNING: This document contains

NON PUBLIC INFORMATION OF THE BOARD OF GOVERNORS OF

THE FEDERAL RESERVE SYSTEM (the “Board”) and must be handled in accordance with the Board’s policies. This document may only be shared with contractor employees who have a valid “need-to-know.” All other disclosures, including disclosures to the public, require the Board’s written permission. This document must be stored in a locked container or area offering sufficient protection against theft, compromise, inadvertent access and unauthorized disclosure. When no longer needed, in accordance with the Board’s policies, destroy this document by shredding, pulping, or burning to assure destruction beyond recognition unless otherwise instructed by the Board’s COR.

b. The disclaimer below (1.3.1.b.i) shall be placed on all drawing pages. It is the responsibility of the Construction Contractor to communicate this requirement to their Sub- Contractor(s).

i. NON PUBLIC INFORMATION OF THE BOARD OF GOVERNORS OF THE FEDERAL RESERVE SYSTEM WARNING: This document contains

NON PUBLIC INFORMATION OF THE BOARD OF GOVERNORS OF

THE FEDERAL RESERVE SYSTEM (the “Board”) and must be handled in accordance with the Board’s policies. This document may only be shared with contractor employees who have a valid “need-to-know.” All other disclosures, including disclosures to the public, require the Board’s written permission. This document must be stored in a locked container or area offering sufficient protection against theft, compromise, inadvertent access and unauthorized disclosure. When no longer needed, in accordance with the Board’s policies, destroy this document by shredding, pulping, or burning to assure destruction beyond recognition unless otherwise instructed by the Board’s COR.

c. It is the Construction Contractor’s responsibility to make sure the security requirements in 1.31.a and 1.3.1.b are applied when documents and/or drawings are printed or transferred.

d. It is the responsibility of the Construction Contractor to communicate the security requirements in 1.31.a and 1.3.1.b to their Sub- Contractor(s).

1.4 Drawings References

a. The disclaimer below (1.4.a.i) shall apply to all reference drawings provided to the Construction Contractor by the Board or the A/E. It is the responsibility of the Construction Contractor to communicate this disclaimer to their Sub- Contractor(s).

i. The Board does not guarantee and expressly disclaims any responsibility for the accuracy, adequacy, or completeness of the information contained or not contained in the reference documents. A/E shall employ its own experts to analyze available information, including verification of existing conditions as needed. A/E shall be solely responsible for the consequences of acting on conclusions obtained from examination and analysis of the reference documents and the existing conditions at the Project.

1.5 Document Deliverables

1.5.1 – DRAWING DELIVERABLES

a. Drawings shall be submitted in hard copy, “pdf”, and in the drawings native application in “rvt” or “dwg” format.

b. If drawings are to be submitted in an application other than “pdf”, “rvt” or “dwg”, the Contractor shall make request to the COR. The COR shall approve the requested application before its use by the Contractor.

c. AutoCAD files shall include bound reference information and an approved layer naming convention.

d. The Contractor shall use the Board’s CAD Execution and Methodology Plan

(“CxP”) and must at a minimum meet the Board’s mandatory requirements as listed in the Board’s CAD/BIM Guide.

e. Facility Data/ COBie requirements

i. The Contractor shall fulfill Construction Operations Building Information

Exchange (COBIE) / Facility Data requirements as set forth by the Board in the CxP and CAD/BIM Guide, including all requirements for indexing and submission.

ii. All named products and equipment appearing in design schedules shall be listed in the Components Table. The A/E shall ensure that the list of equipment provided in the COBIE /Facility Data "Component" worksheet includes all equipment specifically identified in the Model.

iii. All objects and attributes being identified using the BIM COBie/Facility Data spread sheets shall be as listed in the CxP.

1.5.2 – PROJECT DOCUMENTS, REPORTS, PROJECT DATA, & CALCULATION

DELIVERABLES

a. Project documents, reports, Project data and calculation files shall be submitted in hard copy and electronically in native and “pdf” format.

1.5.3 – PROJECT DOCUMENTS, REPORTS, PROJECT DATA, & CALCULATION

DELIVERABLES

b. Project documents, reports, Project data and calculation files shall be submitted in hard copy and electronically in native and “pdf” format.

1. All Project manuals, calculations, reports and product data shall be submitted either on standard white bond paper or formatted sheets, 8 ½” x 11”, bound in snap action three-ring notebooks, organized in a logical sequence, and tabbed to each section heading. Calculations shall be titled with each analysis clearly indicating subject and/or issue being studied, applied references, assumptions, and analysis.