Attachment 1 - SOW.pdf

Statement of Work 432 MSG Regional Fire Training Facility Application & Design Project at Creech Air Force Base

Contract No. TBD Date: 16 June, 2025

1. General This Statement of Work (SOW) sets forth the performance requirements for services required to develop a complete application to the Department of Defense’s Office of Local Defense Community Cooperation Grants for the development of a Regional Fire Training Facility scoped, scaled, and designed to meet the training requirements of both Clark County Fire Department and Creech AFB’s fire training needs.

The Contractor shall furnish all labor, management, investigations, studies, travel, facilities, supplies, equipment, and materials to perform the required services. The Contractor is responsible for determining what disciplines and skill sets are required for accomplishing the work under this SOW and form a team accordingly. The Contractor shall accomplish the required services and furnish to the Government reports and other data together with supporting material developed during the period of service as set forth herein. All source data and products are property of US Government and should be provided upon completion of the Task Order to the project manager in both native data and final product form, without the need for proprietary data systems for the US Government to process the data. During the execution of work, the Contractor shall provide adequate supervision and quality control to assure the accuracy, quality, timeliness, and completeness of the work. Subcontractors' service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government. The Government Contract Officer’s Representative (COR), after coordination with the Contract Officer (KO), must approve any deviations from this SOW, including those recommended by the Government during the production and review process. For each task ensure there is a virtual option for participants.

1.1 Objectives

The Contractor will complete application for a Department of Defense (DOD) grant out of the Office of Local Defense Community Cooperation (OLDCC) for the design, construction, and operation of a regional fire training facility to be built and operated by the government of Clark County, Nevada. This effort as conceived in accordance with the goals of the grant program office will allow the mutual benefit of both Clark County’s fire department training needs and those of the fire department of Creech AFB.

Clark County and Creech AFB have entered into a memorandum of understanding that they with jointly develop the application clearly identifying to the contractor the training requirements of each organization and the various equipment requirements that would be dual use at the facility. The expectation is that Clark County will be the ultimate design authority, construction execution agent, and operator of the facility, if the grant process successfully obtains funding from the DOD. This effort is to design an application package to the appropriate grant program on behalf of Clark County and Creech AFB with the appropriate level of planning and design to make the package viable for consideration by the grant program.

All applicable standards, including those that are not referenced or listed, constitute criteria for the execution of this task order.

Table 1 – Tasks

Task Number (Base/Option)

Task Title (Line Item) Customer/Location

Base Task 1 Contract Kickoff Meeting Virtual Base Task 2 Project Management Plan and Monthly Status Reports Virtual Base Task 3 On site Charette for application development with 432

Wing and Clark County at Creech AFB (Projected One Week)

Onsite CAFB

Base Task 4 35% review of application with all identified stakeholders (432 WG and Clark County as primary) Virtual

Base Task 5 65% review of application with all identified stakeholders (432 WG and Clark County as primary) Onsite CAFB

Base Task 6 95% review of application with all identified stakeholders (432 WG and Clark County as primary) Virtual

Option Task 7 Technical support and presence at time of application submittal and defense to Department of Defense TBD

1.2 Period of Performance

All work required within this statement of work shall be completed within 12 months from award.

Performance of each scheduled line item shall comply with the schedule of deliverables identified.

Modifications are required in writing and further approval. The strategic Goal of this effort is to have a complete and viable application package for DOD submittal for the Fiscal year 2027 program. The expectation for the submittal process would be end of month June 2026.

1.3 Project Locations

Work will be completed primarily at the contractor’s office and partially onsite at Creech AFB located near Indian Springs, Nevada. There is potential for additional project site consideration within the boundaries of Clark County Nevada, along the I-95 corridor between the City of Las Vegas and Indian Springs Nevada.

1.4 Scope Review

Prior to submission of the proposal for the performance of this scope of services, the Contractor shall review the Scope and provide comments on any errors, omissions, inconsistencies, new industry standards or procedures which would provide the customer with a better end product. Please contact the Contracting Officer immediately if you have any suggestions or questions.

1.5 Quality Control

The Contractor shall be responsible for Quality Control of all submittals under this task order. The minimum requirements for the Quality Control Plan (QCP) are given in ER 1110-1-12, Quality Management, and the project SOW. The QCP is the Contractor firm’s management plan(s) for execution of the contract. The QCP describes the way in which the Contractor will produce the deliverables, the steps that will be taken to control quality, and an assigned point-of-contact within the Contractor firm’s organization responsible for ensuring compliance with the QCP. The QCP will be modified to include any changes to the contract that occur.

The Contractor shall submit a Quality Control Plan within 5 business days of task order award electronically to the PM and COR which describes the quality control processes and methods of review, with personnel assignments, which will ensure a quality check and quality deliverables. The contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this SOW. The Contractor is responsible for quality control (QC) of the technical products, reports, and submissions produced under this statement of work. The Contractor’s QC activities must consist primarily of:

a. Development and execution of a Quality Control Plan (QCP),

b. Internal QC

1.6 Data Rights

The Government has unlimited rights to all documents/material produced under this Task Order. All documents and materials, to include the source codes of any software, produced under this Task Order shall be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials may not be used or sold by the Contractor without obtaining written permission from the Contracting Officer before any release. All materials supplied to the Government shall be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.7 Point(s) of Contact

The Government’s day-to-day point of contact for this task order is:

The key point of contact with the installation is:

Nicholas DiRosario 432 MSG Deputy/CMO Director Creech Air Force Base Office: (603) 391-8397 Nicholas.dirosario@us.af.mil

Captain Erik R. Keller 432 MSG/Construction Management Office Creech AFB Office: 440-669-7853

The above POCs will be the Contractor firm’s primary points of contact with the Government; however, they do not have the authority to modify the SOW. The Contractor shall not take direction that deviates from the terms of the SOW until the Contracting Officer (CO) formally modifies the SOW.

The Contractor shall appoint a Project Manager to serve as a single point of contact and liaison between the Contractor and the Government. The Contractor’s Project Manager shall be responsible for the complete coordination of all work developed under this Task Order.

2. Project Description

The requirements of the grant program can be found on-line at:

https://oldcc.gov/our-programs/defense-community-infrastructure-program

The government will make multiple examples of successful program applications from past years available for reference, scoping, and scaling of this effort.

The Defense Community Infrastructure Program is designed to assist state and local governments, and not-for-profit, member-owned utilities in addressing deficiencies in community infrastructure supportive of a military installation. “Community Infrastructure” includes projects related to transportation; schools; hospitals; police, fire, emergency response or other community support facilities; and utility projects (e.g., water, wastewater, telecommunications, electric and natural gas facilities).

No award may exceed $20 million or be less than $250,000. Projects must be:

- on land located off a military installation or on property under the jurisdiction of a Secretary of a military department that is subject to a real estate agreement allowing the project or facility to be located on military property (including a lease or easement) mailto:Nicholas.dirosario@us.af.mil https://oldcc.gov/our-programs/defense-community-infrastructure-program

- support a military installation

- are supported by the installation commander representing the installation benefitting from the proposed project

- are where ground-disturbing work has not yet commenced

- are construction-ready.

The facility or project itself must be owned by a state or local government, or a not-for-profit, member owned utility.

3. Product Scope

3.1 Base Task 1 - Contract Kickoff Meeting

The Contractor shall host a virtual contract kick-off meeting no later than 28 business days after contract award. The Contractor shall assume the kick-off meeting will be held via teleconference and will be conducted prior to initiation of any work requirements. The purpose of the contract kick-off meeting will be to provide an introduction of both contractor and Government personnel, discuss the contractual requirements, discuss the schedule status of individual installation kick-off meeting, and lay out the path forward for successful contract execution. The meeting will also include a discussion of the Contractor’s draft Project Management Plan (PMP). The contractor must prepare and submit a summary of the meeting minutes no later than 5 business days after the meeting is held for review and comment.

3.2 Base Task 2 - Project Management and Monthly Status Reports

3.2.1 Project Management Plan (PMP)

The Contractor shall develop, submit, and maintain a detailed Project Management Plan (PMP) for all Tasks described in the SOW. The draft PMP shall be submitted within 14 business days of contract award; Government comments to the draft PMP will be reviewed during the Contract Kick-off Meeting. The Contractor shall resolve review comments and submit the Final PMP as a pdf via email to the PM within 14 business days of the Contract Kick-off Meeting.

The PMP shall be broken into individual sections with the following information in each section:

• Technical approach

• Schedule (including Gantt chart)

• Organization and integration of the project team

• Schedule management and project controls

• Quality management

• Project communications

• Stakeholders/POCs

• Quality Assurance Plan

• Accident Prevention Plan (APP)

• Any Other Required

In addition, the PMP shall specify the resources required for the planning, execution, control, and completion of the stated performance objectives. The PMP will present the Contractor’s approach for executing the entire project (the Work Plan), to include the provision of a PM to serve as the Contractor’s single point of contact for coordinating performance of the PWS requirements. The Work Plan will include a Gantt chart of the overall project’s master schedule tied to each task and its associated deliverables identified below and will be provided to the COR, PM, and Installation POC.

The master schedule will be submitted in pdf format. It is recommended the Work Plan’s master schedule be optimized through proposing concurrent events, as applicable, to meet the identified period of performance for this contract.

3.2.2 Monthly Status Reports (MSR)

Monthly Progress Reports shall be submitted during the period of performance and continue when there is award of any option tasks. The Contractor shall prepare and submit a monthly progress report documenting the work in progress. Each monthly report shall be provided to the COR and PM by close of business on the 5th day of the following month. The monthly progress report must be broken down into individual sections corresponding to the specific installation for which awarded work is being performed and identified in the PMP. The monthly progress report will be used to review and evaluate the overall progress of the project, along with any existing or potential problem areas. At a minimum, the monthly progress report shall include a summary of work performed, by task, during the month highlighting important progress or key milestones achieved, work to be performed during the upcoming month, identification of issues encountered (and their resolution), identification of any potential issues (and a plan for their resolution), any outstanding or new issues, and Request for Information (RFI) tracker for Government Furnished Information (GFI). The monthly progress report will also include an updated master project schedule.

The Monthly Progress Report shall be reviewed by the contractor, PM, and Installation POCs each month on a web conference and/or teleconference as established by the project team during the Contract and individual Installation Kick-off Meetings. The Contractor will be required to prepare and submit an agenda and prepare and submit meeting minutes for each monthly status reporting meeting held.

3.3 Base and Option Tasks 3 – 7, PLANNING CHARRETTE REPORTS

Objective: The government is requesting a Planning Charette Report 1 in accordance with AFIMSC expectations regarding programming of MILCON projects for emergency submittal. This effort requires development of a cost estimate that is developed, reviewed, and certified by a certified cost engineer.

Government will provide the latest AFIMSC business rules upon award of contract. The contractor will prepare a Planning Charrette Report I for the effort.

3.3.1 Conduct On-Site Concept Charrette

The Planning Charrette Report must include gathering information concerning user activities, number of personnel, equipment, utility requirements, and future mission requirements. The Contractor shall coordinate with the installation for the full on-site charrette, to include participating units and location. The Contractor shall provide electronic sketches, meeting minutes and other data as appropriate while on-site. The Contractor's team must be composed of members able to work in a charrette environment and in a collaborative manner. There must be an out brief at the end of the charrette with all information collected and rough draft ideas for all COAs specified below.

The team must travel to the installation and conduct an intensive, concept charrette exercise on-site for five (5) days for the best layout and uses of the infrastructure to maximize current mission requirements while preserving the ability to support this task order. The Contractor shall coordinate travel with the COR, Stakeholders, and installation personnel. The intent of the charrette is to verify all programming and user requirements and all possible permutations to develop the COAs specified below.

3.3.2 Conduct On-Site PCR Visit Preparation

The Contractor shall conduct an on-site visit to gather all required info for PCR report. The Contractor must assemble a team with experience appropriate to the planned infrastructure.

1. The Contractor will submit an invitation to customer representatives to discuss schedule and any required teleconference coordination. Contractor shall participate in a teleconference coordination discussion with the COR and customer representative to discuss: draft agenda;

proposed execution schedule; confirm project requirements and any other data/info required to complete site visit.

2. Submit PCR Charrette In-brief Presentation, Agenda and Invite. Agenda shall outline the entire event schedule with timelines, project team, session topic from in-brief presentation;

break-out sessions; and out-brief presentation within 14 days of the on-site. Contractor will coordinate with installation POC to develop an invitation list to ensure all stakeholders are given the opportunity to attend and participate. COR approved agenda and execution timelines shall be conveyed in charrette briefings.

3. PCR Preparation is complete upon COR acceptance of In-brief presentation & Agenda and confirmation of charrette start date and location with installation points of contact.

4. The Contractor shall conduct a virtual In Progress Review prior to Final submittal. The second site visit will serve as vector check final deliverables. Site Visit will follow all required preparation at Section III of this SOW.

3.3.3 Planning Charrette for Preferred COA

The PCR report must be in the referenced AFCEC MILCON PCR format and follow the template.

The Draft PCR submittal must include, as a minimum, a Design Analysis including narratives and preliminary calculations, Drawings, Cost Estimate, and Economic Analysis. The report must describe all proceedings of the Planning Charrette including the program verification; user survey responses;

validated scope and cost; special design considerations, site opportunities and constraints; site plan, demolition plan; site photographs; budgetary cost estimate; and open action items. The Draft Planning Charrette Report must address each of the areas in the provided Charrette Report template.

The executive summary and project description must identify all COAs and provide a high-level scoring system based on various attributes collected during the charrette. The document must also contain a site analysis based on findings in addition to detailed analysis of utilities, floor layouts, maximization of net space, conversion areas, operations areas, etc. The COA document must contain a rough order of magnitude cost estimate that is reflective of the concepts developed in addition and with input from the installation personnel during the charrette, the Contractor must develop a separate cost estimate for non-facility items such as communications/monitoring equipment, etc. for the purposes of choosing a final option.

The Contractor must review and abide by existing National Environmental Policy Act (NEPA) cultural resource information. The Contractor must obtain any additional existing information and surveys concerning potential environmental concerns affecting the site. AF Form 813s, Environmental Impact Analysis Process (EIAP) and supporting documentation will be provided to the A-E as part of their due diligence review. The Contractor must identify in the design all operating and construction permits required which may include air quality, natural resources, hazardous materials, hazardous waste, solid waste, drinking water, ground water, and storm water permits and any other environmental actions required. This scope of environmental requirements shall be limited to review of the existing documentation and providing recommendations and an analysis of potential issues during construction. Environmental surveys, mitigation, and restoration are not required. An environmental permit matrix is not required.

As part of the Planning Charrette, the AE must conduct a Project Definition Rating Index (PDRI) assessment in accordance with Engineering Construction Bulletin (ECB) 2010-17, Implementing PDRI for AF MILCON or Maintenance, Repair, and Restoration (MR&R).

All site analysis and site layout drawings to be provided in CADD or GIS file formats, along with all associated shapefiles and CAD xrefs IAW AF PCR requirements. The package must outline the following areas of interest, by providing a narrative of each detailed section below:

A. EXECUTIVE SUMMARY AND PROJECT DESCRIPTION - The Executive Summary and Project Description is a short narrative that addresses broad concerns including program requirements, site, location, utility connections, force protection, etc. The executive summary must specifically address sustainable development and high-performance green building requirements as well as identify possible selections of building structural systems, exterior materials, doors, windows, roofing, and interior materials. The contractor will provide an assessment and proposed upgrades for the potable water supply systems.

B. SITE ANALYSIS - The Site Analysis must describe the site and adjacent context. This section must include a graphic showing site in relation to the Installation. Describe any special considerations required for the treatment of the site and address infrastructure siting issues such as, approximate topography, site constraints including AT/FP set-back requirements, utility easements, , etc.; and any required demolition. This section must also contain a graphic that will show labeled adjacent facilities, parking lots and access roads.

C. INFRASTRUCTURE DESIGN CONCEPTS - The Infrastructure Design Concepts section, by using the same program elements developed above, will show the development of a viable concept. The Contractor must develop site layouts that address the program requirements and adjacencies. All site layout drawings are to be provided in CADD or GIS file formats, along with all associated shapefiles and xrefs. For any above ground construction, this section must show entrances, corridors, stairways, work areas, special spaces, mechanical rooms for major equipment, and service spaces (with principal spaces label).

D. SITE DEVELOPMENT CONCEPTS - The Site Development Concepts section will show the placement of infrastructure design concept(s) on the site. A full rendering depicting materials and finishes is not required for the Draft; however details and characteristics for any above ground construction should be indicated. All site development and site layout drawings to be provided in CADD or GIS file formats, along with all associated shapefiles and xrefs.

The Contractor is not required to show photo-realistic images.

E. COST ESTIMATE - This section must contain a parametric cost estimate that is reflective of the project planning concepts and scaling utilized by Clark County in their facility design and development process. It is key that the contractor come to understand how Clark County develops and approves project cost estimates for efforts that transition into construction. This project proposal must be construction ready, as such the estimate must mimic the criteria, standards, and applicability of Clark County standards to allow an immediate transition, if the grant is award to the construction phase of the effort. Creech AFB will facilitate direct access to Clark County staff capable of providing the approved contractor with the accurate fidelity on process and details to achieve the grant process level of fiscal fidelity.

3.3.4 Meeting Records

This section of the document must include all of notes and sign in rosters for the conferences, meetings, discussions, verbal directions, and telephone conversations that take place during and around the charrette. Final Planning Charrette Document the unit cost for the building type the source of the costs must be referenced.

3.3.5 PCR Submittals & Deliverables

The Contractor shall provide one PCR on-site visit for data gathering and interview and a second site visit for vector check. The Contractor must submit the following documents that were created during the site visits and meetings: digital copies of attendance rosters, reports that were created, and notes from visits/meetings during the charrette period.

1) PCR Package Document Submittals. The Contractor must submit the completed PCR Package to include GIS and CAD data. Documents including all sections as outlined in Task II of this SOW.

a) The Contractor will provide meeting summary trip report to Government for Site Visit. Trip

Report will include: who was interviewed, when, next steps and any significant highlights.

b) Draft Report will consist of all of the information collected during the charrette instrumental in filling out all sections as described in SOW task including the completed parametric cost estimates as separable documents. All draft documents will be produced and delivered electronically.

c) The Contractor will coordinate with COR and Government POC to hold a telephonic In- Progress Review (IPR) of the draft document to address any outstanding concerns within five

(5) days of receiving Government comments. Contractor shall record meeting minutes.

2) Pre-final Submittal consist of all of the information collected during the charrette instrumental in filling out all sections as described in SOW task including the completed parametric cost estimates as separable documents. All pre-final submittals will be produced and delivered electronically.

3) Final PCR Report will include all changes and corrections based on input from the Government review period from the draft report. Final documents will be produced and delivered electronically.

4. Services

4.1 Confirmation Notices

The Contractor firm shall provide a record of all conferences, meeting (virtual and/or in-person), discussions, verbal directions, telephone conversations, etc. The Contractor firm shall identify all participating personnel, subjects discussed, and conclusions reached. The Contractor firm shall title these records Confirmation Notices and shall number them sequentially. The Contractor shall forward each Confirmation Notice via email to the Government POC within three business days. Communication via email is acceptable for minor, day-to-day correspondence.

4.2 Periodic Status Reports

The Contractor firm shall provide a monthly status report to the Government COR and PM’s. The report shall include: Current Status, Action Item List, and discussion of major issues. Reports shall be submitted at the end of each month.

4.3 Reporting Labor Power to OASA

The Contractor shall report ALL Contractor labor hours (including sub-Contractor labor hours) required for performance of services provided under this contract for the US Army Corps of Engineers via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: https://cmra.army.mil/default.aspx?ReturnUrl=%2f. Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year of contract/task order performance. Contractors may direct questions to the help desk and may review user manuals and gain an understanding about the data fields that will be included in the reporting structure that is hosted at http://www.ecmra.mil/.

5. Schedule & Deliverables

5.1 Schedule

The Tables below shows the schedule of services and deliverables covered in this task order. The Contractor shall submit a schedule showing dates for all key submittals.

The days listed below are business days, including Saturdays, Sundays, and Federal holidays. The Government must receive the deliverable by the start of the next business day. If the due date falls on a Saturday, Sunday, or Federal holiday, the Government expects receipt by the start of the next business day.

Table 2 – Kickoff Meeting, PMP and Administrative

KEY SERVICE OR DELIVERABLE DUE DATE

https://cmra.army.mil/default.aspx?ReturnUrl=%2f http://www.ecmra.mil/

Draft PMP (Base Task 2) Within 14 business days of T.O.

award

Kickoff Meeting (Base Task 1) Within 28 business days of T.O.

award

Kickoff Meeting Minutes (Base Task 2) Within 5 business days following completion of Kickoff Meeting

Final PMP (Base Task 2) Within 14 business days following completion of Kickoff Meeting

Monthly Status Reporting By the 5th day of each month Administrative Reporting Labor Power to OASA (Section 4.3) By 30 September of each year Biweekly Teleconferences Scheduled biweekly during duration of PoP.

Biweekly Teleconference Meeting Minutes Within 5 business day of meeting Quality Control Plan (Section 1.6) Within 5 business days of T.O.

award

Table 3 – Key Service of Deliverable

KEY SERVICE OR DELIVERABLE DUE DATE

Task 3 – 6 – Application and design reviews PCR Workshop Minutes (Electronic) Within 10 business days following the workshop event.

Draft Submittal (Electronic) Within 60 business days following the workshop event.

PreFinal Submittal (Electronic) Within 30 business days following the government comments on the Draft.

Final (Mail) Within 30 business days following delivery of government comments on the PreFinal Submittal.

5.2 Deliverables

The Table below shows the list of deliverables and their required distribution. See Associated Points of Contact Address List below:

Table 4- Deliverables

Deliverables A B C D Draft PMP (Base Task 2) X X X Kickoff Meeting Minutes (Base Task 2) X X X X Final PMP (Base Task 2) X X X PCR Workshop Minutes X X X X Draft Submittal X X X X Pre-Final Submittal X X X X Final Deliverables X X X X

5.2.1 Associated Points of Contact Address List

The points of contact that correspond to the letters (A, B, C, etc.) in deliverable distribution schedule above are referenced below.

A. Nicholas DiRosario, Creech AFB B. TSgt Kaitlin Hassman, Contracting Officer

The Contractor firm shall coordinate submittal distribution with the POCs. The original transmittal letter will be addressed to the POC and will note that by information copy of that transmittal, appropriate review agencies are being provided copies of the work products and are requested to provide comments electronically to the POCs and to the Contractor firm by the due date. The original transmittal letter and all copies will include a schedule showing data distribution.

5.2.2 Deliverables

All Draft and Prefinal Deliverables will be submitted electronically via DOD SAFE to the Distribution list noted above. Hard copy deliverables will be sent by mail.

6. Reviews and Conferences

6.1 Quality Assurance Reviews

6.1.1 Formal Reviews

The Government will perform a formal Quality Assurance (QA) check on the following:

a. The POC will be responsible for providing the comments to the Contractor and the Contractor shall be responsible for responding to, and incorporating (if appropriate), all comments from reviewers into the deliverables.

b. The Contractor maintains professional responsibility and liability for the deliverables. If, in the Contractor’s professional opinion, a QA comment either does not apply or the Contractor disagrees with it, then the Contractor shall not incorporate that comment into the deliverables.

The Contractor shall respond to the comment “Do not concur.” and provide the comment submitter with an explanation of the disagreement. The Contractor shall also be prepared to discuss the position with the reviewer.

c. Excel spreadsheet will be developed by the Contractor to use for tracking and responding to comments.

6.1.2 Casual Reviews

The Contractor firm is responsible for ensuring compliance with all requirements in this task order. The Government will examine all deliverables submitted by the Contractor firm. If the Government finds deficiencies, the Contractor firm shall amend and resubmit as necessary.

6.1.3 Monthly Teleconferences

The Contractor is responsible for scheduling and holding monthly teleconferences with the entire project team. These meetings should allow for the contractor to discuss project status with the USACE PM and Installation POCs. The Contractor will be required to take and provide Draft meeting minutes to the USACE PM and Installation POC within 5 working business day of the monthly call.

7. Technical Criteria, Standards/Specifications, General Requirements and Government

Furnished Information The Contractor shall use the following standards as applicable for this project.

a. Installation Master Planning UFC 2-100-01.

b. Integrated Installation Planning (AFI 32-1015)

c. Facility Requirements Standards (DAFMAN 32-1084)

d. International Building Code (IBC).

e. NFPA Life Safety Codes 13, 90A, 101.

f. Uniform Federal Accessibility Standards and Americans with Disability Act.

g. Architectural Barriers Act (ABA).

h. NFPA 70, National Electric Code.

i. All applicable Federal, State and industry standards, including those not referenced constitute design criteria for this project.

7.1 Proprietary Specifications and Requirements

The Contractor firm shall avoid specifying proprietary materials, equipment, systems, or other features of the work unless the Contractor firm can demonstrate the use of such proprietary requirements will be advantageous to the Government (e.g. fire alarm transmitters and locksets that must be compatible with other products at the facility). The Government is prohibited from specifying proprietary requirements except in unusual circumstances which requires documentation and approval by the Contracting Agency Head or higher authority. If the Contractor firm can show that a proprietary material could be more advantageous to the Government, provide a description that includes the brand name and a general description of those salient physical, functional, or performance characteristics of the item.

7.2 Office Documents

The table below lists the software products the Government uses for work products produced through general-purpose office software (e.g. VE Study, Design Analysis, Etc.):

Table 6 - Government Software Packages

File Type Software Publisher

Portable Document Format (*.pdf) Acrobat Adobe

Hypertext transfer protocol (http) Internet Explorer Microsoft

Word Processing (*.docx) WORD Microsoft

Spreadsheets (*.xlsx) EXCEL Microsoft

Slideshow presentations (*.pptx) POWERPOINT Microsoft eMail client (*.msg) OUTLOOK Microsoft

Shapefiles (*.shp) ArcMap ESRI

CADD AutoCADD Autodesk

The Contractor firm shall ensure the documents they produce and submit to the Government are compatible with these software packages. The Contractor firm shall be responsible for any file translation necessary to permit Government reading of documentation. The Contractor firm shall consult with the Government on the use of software not on this list to ensure the Government can read the files the Contractor firm will submit.

The Contractor firm shall consider readability and reproducibility in the preparation of documents. This includes (but is not limited to) font sizes, organization and layout of documents, paper sizes, and use of color documentation. Documents will be viewed primarily electronically (e.g. Adobe PDF on a computer screen) and not printed.

7.3 Units of Measure

The Contractor shall verify use of U.S. Customary, International, or other units in all work products.

7.4 Government Furnished Information and Materials

To be determined at the Contract kickoff teleconference.

8. Administrative Instructions

8.1 Communication

The Contractor firm’s primary point of contact POC with the Government is listed in Section 6.2.1. The Contractor firm may communicate with other members of the project delivery team (PDT) as necessary to facilitate project delivery. The Contractor shall ensure that the POC is included in all such communications – especially when such communications could potentially lead to a modification to this task order.

8.2 COR/CO Communication

The Contractor firm may always contact the COR, the CO, or the contract specialist assigned by the CO at any time about any issues involving this task order. See subsection “Work Authorization” below.

9. General Provisions

9.1 Ownership

10.1.1 The Government, for itself and such others as it deems appropriate, will have unlimited rights under this Task Order to all information and materials developed under this Task Order and furnished to the Government and documentation thereof, reports, and listings, and all other items pertaining to the work and services pursuant to this agreement including any copyright. Unlimited rights under this Task Order are rights to use, duplicate, or disclose text, data, drawings, and information, in whole or in part in any manner and for any purpose whatsoever without compensation to or approval from the Contractor firm.

The Government will have the right to inspect the work and will have access to and the right to make copies of the above-mentioned items. All text, digital files, data, and other products generated under this Task Order shall become the property of the Government.

9.2 Project Location Considerations and Base Access

The Contractor firm shall become acquainted with all available site related information to properly estimate the difficulty and/or cost of successfully executing the work under this task order. Base access paperwork will be the responsibility of the consultant and should be prepared and submitted with adequate time for processing and approval prior to any onsite visits which will be determined during the kickoff meeting.

9.3 Work Authorization

The Contractor firm shall not accept instructions issued by any person employed by the Government or otherwise, that may affect the terms and conditions of the Task Order substantially, other than the Contracting Officer, or the COR acting within the limits of their authority. Any work done by the Contractor firm without being properly directed to do so will be done at the Contractor firm’s own risk.

Furthermore, the Government will not take beneficial use of any work outside this scope of work without properly modifying the task order.

9.4 Subcontractors

The Contractor firm shall insert all appropriate provisions in all Subcontracts relating to this Task Order and shall ensure fulfillment of all contractual provisions by subcontractors. If at any time during the process of this Task Order, the Contracting Officer determines that any subcontractor is unsatisfactory or is not performing in accordance with the Task Order, the Government will inform the Contractor firm in writing accordingly and the Contractor firm shall take immediate steps to obtain acceptable performance or terminate the subcontract. Subletting by subcontractors is subject to the same requirements. The Contractor firm shall not construe anything in this Task Order to create any contractual relation between any subcontractor and the Government. The Contractor firm’s change of subcontractors must be done in accordance with the contract clause, FAR 52.244-4.

9.5 Confidentiality

10.5.1 The Contractor firm shall protect the confidentiality of all work accomplished under this SOW. If approached by the media or others not directly involved with the project, the Contractor firm shall refer them to the COR for response.

10.5.2 Quantity surveys and construction cost estimates shall remain the sole property of the Government, and shall not be made available to others for any purpose. The release of information concerning quantities and costs to prospective bidders is prohibited. The Contractor firm shall be aware of and take such precautionary measures as necessary to maintain the confidential nature of all estimates prepared under this Task Order.

9.6 Inspection and Acceptance

During the progress of work, all work and all the Contractor firm’s or subcontractor's plant and equipment engaged in the work shall be subject to, and available for, inspection by the COR during normal office hours.

9.7 Inspection of Delivered Work

As soon as practicable after delivery of work in any installment, the Government will spot check for serious errors or an undue number of minor errors indicating mistakes or carelessness on the part of the Contractor firm. The COR may forego a thorough inspection and return the entire submittal for rechecking and correction by the Contractor firm.

9.8 Preliminary and Final Acceptance

Preliminary acceptance of work delivered at any stage may be the basis for estimating partial payments for completed work but shall not be construed as final acceptance. Preliminary acceptance of work delivered at any stage may be accepted; however, if proven by subsequent inspection to not be acceptable, the work shall be corrected by the Contractor firm. Final acceptance of the work will not be made until all work under the Task Order has been delivered and found to be acceptable. Acceptance does not relieve the Contractor firm of liability (See FAR52.236-23).

9.9 Deficiencies

The Contractor firm shall correct the deficiencies and resubmit the documents or files in the quantities originally required and within a reasonable time as specified by the Contracting Officer. The Contractor firm shall bear the cost of correcting and re-submitting deficient work.

9.10 Certification of Computer Media

The Contractor firm shall scan all electronic deliverables for known viruses utilizing current virus detection software that is updated weekly for new virus profiles. Transmittal letters transferring files to the Government shall certify if this has or has not been accomplished.

9.11 Payment Requests and Progress Reports

The Contractor shall submit payment requests and receiving reports in electronic form using Wide Area WorkFlow (WAWF), in accordance with DFARS Clause 252.232-7003. The Contractor shall prepare and furnish to the Government a receiving report at the time of each delivery of supplies or services under this contract or task or delivery order.

All invoices shall include a copy of the monthly status report or other supporting documentation demonstrating task actions completed structured in same format presented in the SOW.

The contractor shall submit a single invoice for work completed by the 5th of the month. The contractor will deviate from this requirement only with the permission of the COR.

Contractor shall include a MSR (Monthly Status Report) associated with the work being invoiced. The contractor shall provide a breakdown of the amount invoiced by individual CLIN. Invoices which are not broken down by CLIN will be rejected.

9.12 Verification of Government Furnished Information

Upon initial delivery of the Task Order and all Government furnished data, the Contractor firm shall inspect them and inform the COR if information is missing, no later than seven business days after receipt. The Contractor firm will thoroughly review the Government furnished data, conference minutes and other communications concerning the project which has transpired prior to the contract date. Should the Contractor firm find any conflict between the Government-supplied data and applicable codes, Government regulations, above referenced minutes and communications, or if the cost estimate is determined to be in error such that it appears that the construction cost will exceed funds available, the Contractor firm shall inform the Government, in writing, within five days of the discovery.

9.13 Contractor Request for Information (RFI)

When the Contractor firm needs additional, or a clarification of, information from the Government to facilitate the services required by this Task Order, the Contractor firm shall submit a Contractor RFI requesting the needed information. The Contractor firm shall use a separate Contractor RFI for each unrelated request. Even though the information is requested by other documentation or methods such as, Confirmation notices, letters, memorandums, design analysis, annotated review comments, telephone conversations, conferences, meetings, discussions, oral conversations, etc., the Contractor firm shall document the requested information on a Contractor RFI. These requests, entitled “Contractor Request for Information” shall be numbered sequentially and shall fully explain the requested information and all ancillary information needed. The Contractor firm shall forward each Contractor RFI to the POC as soon as the need for information is determined.

10.15 Photographs and Video Capture

The Contractor shall prepare digital photo documentation. Photography of any kind shall be coordinated through the Installation, customer or facility point of contact (POC). The Contractor shall use color and high contrast black and white photographs to illustrate subject matter. Photographs shall be well composed, avoiding background and foreground distractions (clutter, trash, unsightly vehicles, etc.).

Photographs shall be geographically linked to associated features with global positioning system coordinates. Digital copies of all photos must be provided at the end of the contract. Photo files names shall contain a brief description of the photo (i.e. 20120515_Bldg 1535.jpg). They shall be digitized, stored on a CD-ROM and linked to the test portion of the document. It is acceptable for the Contractor to use photos provided by the Public Affairs Office (PAO).

APPENDIX A:

Work during federal holidays, weekends and/or after normal business hours is possible. Contractor may submit a waiver request to the Contracting Officer for permission to work outside of normal business hours. The waiver request shall be submitted in writing at minimum 7-calendar days in advance of the proposed work. Contractor shall ensure that all work conducted during a federal holiday, weekend and/or after hour is still open/exposed such that government can inspect the work. Approval of the waiver will only be provided, if the work is deemed necessary or found to be in the best interest of the government.

Contractor shall proceed to schedule work during these periods only after receiving written approval of the waiver from the Contracting Officer. Normal business hours are considered to be from 0700-1700 hours. Weekends are considered to be every Saturday and Sunday. The following legal holidays are observed by the Federal government:

New Year's Day January 1 Martin Luther King, Jr.'s Birthday 3d Monday in January Washington’s Birthday 3d Monday in February Memorial Day Last Monday in May Juneteenth June 19

Independence Day July 4 Labor Day 1st Monday in September Columbus Day 2d Monday in October Veterans Day November 11 Thanksgiving Day 4th Thursday in November Christmas Day December 25 NOTE: Any of the above holidays falling on a Saturday will be observed on the preceding Friday;

holidays falling on a Sunday will be observed on the following Monday.

APPENDIX B:

Geospatial Information and Services (GI&S) Deliverables

1. Geospatial Data1: The Contractor shall deliver the GI&S data in an ESRI file geodatabase in accordance with the latest Air Force Adaptation version of Spatial Data Standards for Facilities Infrastructure and Environment (SDSFIE) for a seamless import of data into the appropriate HQ, MAJCOM, and/or Installation GeoBase Enterprise database. All text and graphic data related to GI&S map exhibits shall be provided in MS Word, MS Excel and Adobe .pdf format.

Deliverables intended for interaction with other databases or GeoBase feature classes or “layers” (i.e. file geodatabases, etc.) shall comply with the Open GIS Consortium (OGC) guidelines for interoperability on multiple systems.

• Data shall conform to the latest Air Force Adaptation of SDSFIE-V as applicable, and

SDSFIE-V Gold if no Component HQ Adaptation exists.

• All GI&S data delivered will be in:

o Projection: Applicable UTM Zone o Datum: WGS 1984 o Geoid: EGM 96 o Units: Meters

• Information regarding latest Air Force Adaptation of SDSFIE can be found at:

https://www.sdsfieonline.org/Components/USAF

• For those data layers that were created for or during the performance of this project, all layers shall have at a minimum the latest version of SDSFIE Gold foundational attribute fields included and populated, as enumerated in the following table:

1 Shall encompass other data types (such as Google .KML) in addition to AutoCAD .dwg created/utilized during the project to be delivered in the ESRI file geodatabase format https://www.sdsfieonline.org/Components/USAF

Table: SDSFIE Gold 4.x Foundational Attribution

SDSFIE Gold Attributes Attribute Name

Definition, Description and Note

Data Type Nullable Mandatory Attribute Guidance featureDescription A narrative describing the feature

String(Max) Yes Yes featureName The common name of the feature

String (80) Yes Yes The official name of the feature found on installation maps or in authoritative databases of record.

installationId The official code assigned by the Military Service (includes Washington Headquarters Services) used to identify the site or group of sites that make up an installation.

String (11) Yes No The installation ID should match the Installation Code reported to the RPI. All sites and assets within an installation shall have the same installationId.

mediaId Used to link the record to associated multimedia records that reference data Example media types include imagery, video, audio, scanned documents, and drawings. See your DoD Component service implementation guidance for details as to the content of this attribute.

String (40) Yes Yes metadataId Used to represent or link to feature level metadata.

String (80) Yes No featureIdpk Primary Key. A unique, user-defined identifier for each record or instance of an entity.

String (40) No Yes sdsId A unique identifier for all entities in the

SDSFIE

GUID Yes Yes

• In addition to those fields enumerated in the SDSFIE Gold foundational attribution table, the inclusion of an Installation Name field is desirable for those datasets that do not have a corresponding AF SDSFIE Adaptation Data…