1 | P a g e PWS Version September 2026

PERFORMANCE WORK STATEMENT

(Attachment A1)

DEPARTMENT OF VETERANS AFFAIRS

Veterans Affairs St. Louis Health Care System John Cochran Veterans Affairs Medical Center

New Bed Tower

INITIAL OUTFITTING, TRANSITION, AND ACTIVATION SERVICES (IOTA)

INDEFINITE DELIVERY INDEFINITE QUANTITY (IDIQ)

IDIQ # TBD

Task Order #1 Project Management & Pre-Planning Services

Date:

10/26/2026

2 | P a g e

1.0. Background

The VA St. Louis Health Care System - John Cochran Division (VA STLHCS-JC), located at 915 North Grand Boulevard, St.

Louis, Missouri, is part of a two-division health care system that also includes the Jefferson Barracks VAMC approximately 18 miles south of the John Cochran campus. These facilities serve Veterans in metropolitan St. Louis, Missouri, southwestern Illinois, and the broader Veterans Integrated Service Network (VISN) 15 service area.

The John Cochran campus is in a highly constrained urban setting in midtown St. Louis. The existing hospital infrastructure includes Building 1, constructed in 1953, and the Clinical Addition constructed in the mid-1980s. The campus requires modernization to address functional adjacency, physical security/force protection, aging infrastructure, seismic compliance, parking, and clinical capacity concerns.

The Department of Veterans Affairs Office of Construction and Facilities Management (CFM), VA St. Louis Health Care System, and the Kansas City District (NWK) U.S. Army Corps of Engineers (USACE) are partnering to provide new and replacement facilities for the John Cochran Division. The John Cochran Major Project will relocate inpatient functions to a new seismically compliant Bed Tower, add new functionality, improve departmental adjacencies, replace aging utility infrastructure, and address physical security requirements.

The John Cochran Major Project includes campus-wide expansion. Planned new facilities include, but are not limited to, parking garages, a Central Utility Plant, the Bed Tower, an Engineering/Administration building, a motor pool building, and supporting structures. The project includes more than 700,000 net usable square feet of new space. Clinical and administrative services anticipated to be supported include surgery, radiology, pharmacy, surgical services, spinal cord injury inpatient and rehabilitation services, emergency services, engineering, police, nutrition and food services, dialysis, and additional services as refined by the Government-approved program and design documents.

2.0. Scope

Conduct all necessary Design and Equipment Planning, and IOTA activities, in accordance with the PWS, in support of the project(s) identified in Section 1.0 above. The IOTA contractor shall provide professional services to include all labor, materials, transportation, and equipment to conduct and provide IOTA support services to accomplish the PWS tasks.

The scope includes project support for planning, activating, outfitting, and transitioning the staff and Veterans/patients associated with the project. The scope of services includes Comprehensive Project Management, Comprehensive Interior Design, FF&E, and Space Planning Services and Concept of Operations (CONOPS), Transition Planning and Project Staffing Planning for the identified project.

3.0. Period of Performance

See 1449

4.0. Type of Order

Firm-Fixed Price

5.0. Place of Performance

Services under this Performance Work Statement shall be performed at the 915 N Grand Blvd. St. Louis, MO; offsite at the contractor’s facility or alternate work site(s) (i.e., old clinic space, VA Medical Center Campus).

6.0. Travel

The Government anticipates travel under this effort to perform the tasks, as well as to attend program-related meetings throughout the Period of Performance. Cost reimbursable travel will be included in the Task Order award based upon the Government’s estimate.

3 | P a g e

Travel shall be in accordance with this individual Task Order requirements. Cost-reimbursable (CR) travel is funded on this Task Order and is limited to travel directed by the Government and performed in conjunction with a specific, authorized requirement. All travel is listed on the Task Order as a separate cost-reimbursable line item with a Not to Exceed (NTE) amount, and will be requested, approved, and reimbursed in accordance with the Task Order, the Federal Travel Regulations (FTR), and FAR 31.205-46. The Government will not reimburse any living or relocation costs for IOTA Contractor employees from other geographic areas. Mobilizing personnel and paying living expenses for non-local staff is considered a cost of doing business.

Local travel, within a 50-mile radius from the place of performance will not be reimbursed. The Government will not pay travel charges for travel to and from the IOTA contractor employee’s home and Government office or from one Government facility to another. Travel beyond a 50-mile radius of the contractor’s facility is authorized for reimbursement on a case-by-case basis and must be pre-approved by the COR via the Travel Authorization Request (Attachment C). The IOTA contractor must obtain written approval from the COR BEFORE any travel begins, utilizing the Travel Authorization Request form. Other documents or e-mails will not be accepted as pre-approval. Travel that occurs without written pre-approval will not be reimbursed. Travel expenses will be reimbursed on an actual expenditure’s basis in accordance with FTR and FAR 31.205-46. Per-diem expenses will be paid per the GSA daily rates for the location of travel. To be reimbursed for travel, the IOTA contractor shall submit supporting documentation as required by FTR with invoices. FTR requires for any temporary travel destination you must provide a receipt to substantiate your claimed travel expenses for lodging and a receipt for any authorized expenses costing over $75 (FTR 301-11.25). Expenses for subsistence and lodging will be reimbursed to the IOTA contractor only to the extent where an overnight stay is necessary and authorized by FTR in effect at the time of the stay for the specific location. Approval for rental vehicles is discouraged and will be approved on an individual basis. Additional information can be found at GSA FTR.

7.0. Specific Tasks and Deliverables

7.1. Comprehensive Project Management Services

Provide comprehensive planning and activation project management services integral to the execution of tasks ensuring effective, efficient, and timely completion of contracted services. The IOTA Activation Project Manager may be required to be onsite as required per contract and lead UGM and Integrated Project Team (IPT) meetings, installation activities, and project closeout. The IOTA Activation Project Manager will ensure close coordination with the design and construction efforts of the building contractor.

Project Plans, Schedules, and Reports:

The IOTA contractor shall support the FAPM’s planning, scheduling, and reporting requirements.

The IOTA contractor shall support the FAPM in establishing a local level IPT. The purpose of the IPT is to provide timely input to concept and design development, identification, planning, and execution of procurement functions, and logistical and operational requirements in order to bring the project into operation. Stakeholder engagement is vital to a successful outcome. IPT members should include, at a minimum: local OI&T, Infection Control, Emergency Safety & Preparedness, Logistics, Patient Safety, facility Fiscal office, Privacy, Lock Shop, Police, Environmental Management, project Resident Engineer, local Union representation, Biomedical Engineering, Interior Design, local Contracting, public affairs, and others as required depending on project type and scope.

The IOTA contractor is also responsible for developing a Work Breakdown Structure (WBS) and an associated Activation Integrated Master Schedule (AIMS) which integrates activation activities, construction project/schedule, and the VA Information Technology project schedule, etc. The AIMS shall be coordinated with the CFM contract dates and the Lessor/building contractor’s construction schedule.

In managing the AIMS, the IOTA contractor shall advise the Government of suspense dates that need to be met by the Government and/or government contractors to ensure on-time execution such as, but not limited to, delivery dates for items purchased by the Government, information that the contractor needs from the Government to

4 | P a g e complete the requirements of this PWS, and any other milestone dates for all tasks associated with bringing the space into operation. The IOTA contractor is responsible for tracking these dates and keeping the parties informed.

However, the IOTA contractor is not responsible for enforcing dates or ensuring work is completed on schedule to the extent the dates and/or work are not a requirement of the IOTA contractor as described herein. The IOTA contractor shall report in a timely manner any schedule deviations to the COR and CO. Upon the Government's acceptance of the schedule deviation, the IOTA contractor shall prepare and submit a revised AIMS for approval.

In the event a schedule deviation impacts the period of performance of this contract, the IOTA contractor shall provide in writing to the CO the reason for the delay, associated points of contact, and a request for extension.

Extension requests must detail the amount of additional time required and are not automatically granted. The IOTA contractor shall document lessons learned throughout the project in the monthly status report.

# Deliverable Name Deliverable Description

16.1.1 Monthly Project

Status Report

The Monthly Project Status Report shall cover the same reporting period as the monthly invoice, correlate to the invoice, and be submitted with the invoice. It shall summarize project progression and work completed; AIMS and major milestone status; moderate- and high-risk items; risk and change-management status; meetings attended; decisions and action items; lessons learned; schedule deviations; SharePoint/OCAMS data-quality issues; design-support and A/E review-event status; procurement and acquisition progress; and HTM, SCM, OI&T, Interior Design, and service coordination. If prime-contractor, subcontractor, or Key Personnel staffing changes occurred during the month, the report shall include an updated Contract Staff Roster (Attachment D). During acquisition-support, the report shall include a graph showing equipment purchased, remaining to be purchased, pending market research, pending review or approval, and deferred items, including percentages complete and dollar amounts.

Monthly reports are to be uploaded to a document library on the project’s SharePoint site.

16.1.2

Activation Integrated Master Schedule (AIMS)

(Attachment E is a representation of required data/information

Actual deliverable data/information requirements are defined in SharePoint tool)

The AIMS shall be provided as a work breakdown structure (WBS) and color-coded, time-lined graphic which marks the start and end dates of major element or sub-element milestones/gateway of construction which may impact the start, duration, or completion date of scheduled activation tasks, shows start and end dates of milestone/gateway events for purchased items, shows scheduled activities in activating or approving building systems and support contracts, and shows activation events which may be impacted by schedule acceleration or slippage by others. A complete AIMS will include and demonstrate all construction milestone/gateway dependencies with an activation-related processes.

The Government-approved CFM/USACE project IMS and A/E design schedule shall be the schedule-of-record inputs, with the construction contractor's schedule coordinated as applicable. The AIMS shall include A/E user-group, interim, Government-review, pre-final, final-review, final/backcheck, BCOES, and IFC events; extend through Day One and project closeout regardless of task owner; and identify Government and contractor suspense dates.

Mandatory milestones shall include construction need-by and order dates for VC items; HCHT and architecturally significant equipment need-by, funding, and

5 | P a g e

# Deliverable Name Deliverable Description procurement dates; equipment testing; First Use (commencement of clinical services); and other milestones required for activation regardless of task owner or responsibility. Schedule changes, including new milestones and tasks, shall be annotated in monthly updates, and all prior accepted versions shall be archived in SharePoint document library. Additional task milestones must be added to the AIMS as those tasks are identified.

Initial submittal and updates are to be uploaded in a document library on the project’s SharePoint site.

16.1.3 Individual Service

Project Schedules

IOTA contractor shall develop a detailed individual service project schedule to be utilized by services in planning and executing departmental Activation. The details included in the AIMS shall also be included in the individual service project schedule as they apply to that service. Individual service project schedules shall be built on the needs of each specific service, with input from the COR, the impacted service, and IOTA contractor to determine specific milestones.

Examples of potential individual service specific requirements could be clinical grid creation, pharmaceutical informatics, service specific equipment set up, or 1st Patient Day clinic requirements.

Initial planning baselines shall be submitted within 30 calendar days after the TO effective date, using available milestones and identifying unresolved inputs.

Detailed activation planning shall be refined as dates become available; the 180-day period before planned 1st Patient/Use Date is a later refinement milestone and does not defer the TO1 baseline. For major construction projects, additional time may be required, this need will be determined by the COR.

Initial schedules and updates are to be uploaded in a document library on the project’s SharePoint site.

16.1.4 Risk Management

Plan and Log

(Attachment F is a representation of required data/information

Actual deliverable data/information requirements are

The contractor shall use the OCAMS Activation Tool in the Government-provided SharePoint site (Risk Register SharePoint List).

The register shall provide a list of identified project-specific risks, challenges, and perceived problems for all phases of work; probability of occurrence; level of impact; risk owner; stakeholder-informed mitigation or resolution strategy; due date; status; escalation path; and residual risk. Risks shall include matters that may prevent timely completion, exceed budget, generate change orders, result in owner dissatisfaction, reduce service quality, or adversely affect design, equipment, acquisition, HTM/SCM/OI&T coordination, construction, activation, training, move, safety, security, or operational readiness. Risk management shall be a regular coordination-meeting agenda item to ensure risk are being managed.

Initial Risk identification and subsequent additional identified risks are to be entered on the project’s SharePoint site Risk Register list.

6 | P a g e

Government Provided Share Site for Information Sharing:

The IOTA contractor shall use the government provided SharePoint site for project documentation and information sharing through the provided SharePoint lists and subsites. The VA SharePoint can only be accessed by individuals with a VA email address and network access.

16.1.5 Change

Management Plan

Change Management applies to requests from user/user groups for changes to equipment lists or other user requested changes, which are not a construction requirement by code or other mandatory source, but may impact infrastructure requirements, and/or equipment and building layouts.

The IOTA contractor shall work with the COR to develop a change management plan. The Change Management Plan shall develop processes for submitting, reviewing, and approving or disapproving user requested changes. The process should include review by the local facility subject matter experts (SME), the Resident Engineer (RE), and medical center leadership to determine impact to project scope, cost, and schedule.

Plan is to be uploaded to a document library on the project’s SharePoint site.

16.1.6 Change

Management Log

(Attachment G is a required data/information)

Actual deliverable data/information requirements are

IOTA CONTRACTOR MUST UTILIZE OCAMS ACTIVATION TOOL BUILT INTO THE

GOVERNMENT PROVIDED PROJECT SPECIFIC SHAREPOINT SITE (Change Requests SharePoint List)

The IOTA contractor shall document requested and approved or disapproved user requested changes in a change management log. Any approved changes to VA purchased FF&E must also be accounted for in the Acquisition Plan. IOTA contractor shall not direct changes. Any changes with infrastructure or space impacts will need coordination with the RE to determine any scope, schedule, or cost impact prior to submitting for approval through the change management process.

Maintain the log in the Change Request list on the project’s SharePoint site.

16.1.7 Integrated Project

Team (IPT)

IOTA contractor shall draft an IPT Charter, to include IPT roles and responsibilities of stakeholders and the identification of individual members, and IPT member nominations letters. IPT members should include, at a minimum: local OI&T, Infection Control, Emergency Safety & Preparedness, Logistics, Patient Safety, facility Fiscal office, Privacy, Lock Shop, Police, Environmental Management, project Resident Engineer, local Union representation, Biomedical Engineering, Interior Design, local Contracting, public affairs, and others as required depending on project type and scope.

The IOTA contractor shall update the IPT letters and charter throughout the project, accounting for any changes.

Initial submission and updates are to be uploaded to a document library in the

7 | P a g e

Project deliverables, schedules, reports, and management plans shall be shared with the Government by posting on the government provided SharePoint site. IOTA contractor shall update and maintain all versions of project deliverables as required per the deliverable schedule and posted on the SharePoint site, unless otherwise agreed upon by the COR, CO and VA Activation Program Manager. Revisions to schedules and plans since the last update shall be tracked and clearly identified. The project SharePoint site is the official activation project management site for all project working documents and deliverables, as well as the location for lists and subsites for all data sets to be worked throughout the lifecycle of the activation project. At the end of the contract, all deliverables are to be turned over and/or coordinated for download between the IOTA contractor and the COR. All project documentation shall be compatible with systems utilized by the medical facility with files downloadable by all parties.

Where SharePoint tools are available, the IOTA contractor must utilize the tool and complete and update all fields as necessary. Data shall be input directly into the SharePoint tool, in lieu of other formats (i.e. excel). Contract attachments provided are representations of required data/information. Actual deliverable data/information requirements are defined in SharePoint tool. Tools shall be completed and updated as the project works through the activation process. The SharePoint tools are intended to be live databases, where the actual work is done. As a result, periodic bulk updates from other formats such as excel, should not be necessary.

Meeting Facilitation Services:

The IOTA contractor shall provide group facilitation services to key stakeholders, the IPT, and work groups for meetings required to perform contract PWS tasks. Key stakeholders include, but are not limited to, FAPM, IPT members, and program support staff from Facilities, Medical Maintenance, and other project-related government and medical staff as necessary. The IOTA contractor may identify additional ad hoc groups as approved by the COR.

The IOTA contractor shall guide groups to consensus by identifying requirements, facilitating group discussions, and documenting decisions. The IOTA contractor shall coordinate meetings, and facilitate the groups to assess, analyze, recommend, and document solutions as developed jointly by the contractor and the stakeholders and/or group members.

The IOTA contractor shall coordinate the meeting locations and audio/visual support as needed for these meetings, with the COR. The COR will finalize arrangements with the facility for rooms and audio/visual support. For meetings requiring teleconferencing capability, the IOTA contractor shall provide the teleconferencing service and call-in numbers and host the meetings. The IOTA contractor shall not meet with any end users, the A/E firm, the construction contractor, etc. without first coordinating with the CFM RE, COR, and VA PM. The IOTA contractor shall participate in design/construction meetings as determined by the COR.

It should be noted that prior to award of this contract, CFM worked diligently with the VAMC to produce the construction contract and its corresponding appendices. This includes workflows, the program for design (PFD), floor layouts, room contents list (i.e. general equipment list), agency specific requirements, IT requirements, security requirements, and janitorial requirements produced in the awarded construction contract.

The IOTA contractor may not make changes to the items above (except for the room contents list – provided there is no impact to infrastructure requirements). Any changes resulting from such an instance without the approval of the CFM RE will be borne by the IOTA contractor.

The IOTA contractor will be responsible for the equipment planning within the contractual boundary of the CFM contract Room Content List and defined room layouts. Any deviations will have to be routed through the COR and approved through the RE and CFM CO.

The IOTA contractor shall ensure all appropriate personnel are invited to attend each meeting either telephonically or in person. The IOTA contractor’s project manager should be available to attend requested meetings in person, as

8 | P a g e determined by the COR prior to the meeting. Beyond the IOTA contractor’s project manager, the total number of personnel required to attend meetings to support successful execution of the work for any given meeting is to be determined by the IOTA contractor and must be approved by the COR.

16.1.8 Meeting Minutes

and Meeting Agendas

The contractor shall work with the COR or designee to prepare agendas and minutes for all meetings required to perform the PWS, including User Group Meetings, weekly progress meetings, IPT/workgroup meetings, design workshops, review conferences, and HTM/SCM/OI&T coordination meetings.

The VA or facility standard template shall be used when available. Agendas shall state meeting objectives, topics, attendees, required decisions, and pre-read materials. Minutes shall include the agenda, attendees, decisions, comments, action items, responsible parties, due dates, unresolved issues, and required follow-up.

PWS Deliverable Updates:

After initial acceptance of any developed deliverable under any of the task(s) identified in the PWS, those deliverables will be updated and maintained as part of the Comprehensive Project Management Services Task.

16.1.9 PWS Deliverable

Updates

Updates must be completed no later than 10 business days after identification of need by either the Government or the IOTA contractor. Note: all updates shall reference this deliverable and the original deliverable numbers (i.e. 16.1.9 update for 16.2.1). Where a deliverable specifies a different update or correction deadline, that specific deadline applies.

7.2 Comprehensive Interior Design, FF&E, and Space Planning Services Provide and coordinate comprehensive interior design (CID) services or coordination of CID services, ensuring incorporation of evidence-based health care concepts. FF&E must complement any interior packages developed by the A/E firm associated with the construction project and/or the health care facility’s standards as provided by the Government.

The IOTA contractor may be required to identify FF&E to purchase, receive and install FF&E and visual arts and/or inventory, uninstall, pack, transport and reinstall existing FF&E and visual arts in the health care facility’s current inventory identified for reuse in the new facility following approval by the COR. Design support services include preparing cut sheets for FF&E, updating the room’s content list on the government SharePoint site, including updating spaces to be consistent with A/E drawings. IOTA contractor is to work closely with the VA Interior Designer on all furnishings, space planning, and selections. IOTA contractor shall ensure all selections are in accordance with the construction documents to avoid conflict resulting in either design or construction modifications.

IOTA contractor must keep the government provided SharePoint site updated and always maintained. SharePoint site is the official repository for all project information and is utilized by outside bodies for budgetary and tracking purposes. The IOTA contractor will be validating all FF&E and defining all salient characteristics. “Validating” in the sense means a generic item has been identified by a specific manufacturer and model has not yet been identified.

The IOTA contractor shall then develop the list to include the manufacturer and model and salient characteristics of the item. The IOTA contractor will be responsible for finalizing FF&E with the appropriate IPT representative(s) to

9 | P a g e sign off on the final cut sheets and specifications. The COR (or other designated representative with decision authority) will direct the IOTA contractor to the appropriate stakeholder for approval.

The IOTA contractor will be responsible for identifying salient characteristics for all FF&E with end users and the VA Interior Designer. This also ties into the acquisition support services required under this PWS as the identified salient characteristics will be included in “brand name or equal” procurement packages. A completed Justification and Approval (J&A) form will be required to be included in any procurement packages for any items that require a specific manufacturer or model.

The IOTA contractor is to ensure all identified FF&E or architecturally significant items are in accordance with design documents to minimize any need to change the mechanical, electrical, plumbing (MEP) or architectural support systems and locations. Any impact to MEP resulting from equipment changes must go through the Change Request process. The IOTA contractor shall utilize Space, Equipment, and Planning System (VA-SEPS) Joint Service Number (JSN) nomenclature in accordance with the VA BIM Manual (available at VA TIL MS, https://vatilms.va.gov/vatilms/reports) for all unique ID numbering. Cut sheets shall identify the basis of design item and shall show appropriate VA-SEPS JSNs. New JSN requests and JSN searches can be conducted at https://dha.max.gov/milstd1691.

Cut Sheets shall include a photo of the item, finishes, specifications, instructions, dimensions, etc., that apply to that specific item. Cut-sheet information shall be specific enough to convey information to the VA as they will need to purchase and install the product, but general enough to allow competition across multiple manufacturers. Basis of Design cut sheets shall involve UGMs to determine equipment requirements and specifications. The VA will be responsible for providing the correct point of contact for the user group meetings. These individuals will have the authority to make equipment decisions, such as identification of make and model of equipment, locations for all equipment, and any J&As planned for the procurement of specified equipment. The IOTA contractor shall develop a Rough Order of Magnitude (ROM) to include estimated costs for storage, delivery, and installation. Cut-sheet content shall mature in accordance with Deliverable 16.2.1 and the applicable Task Order schedule.

The contractor shall support VA/Major Projects Service review and validation of the A/E materials. Support shall include, as applicable, User Group Meetings, User Group Review Comments, weekly progress meetings, and final/backcheck or carry-forward reviews. The contractor shall review drawings, Basis of Design materials, Projects Rooms Content List (PRCL) data, service and user requirements, preliminary FF&E/equipment layouts, furniture considerations, HCHT and architecturally significant equipment, OI&T/networked equipment, workflow, CONOPS, phasing, and activation impacts.

The Government will provide the IOTA contractor with the following reference materials for preliminary Project Room Contents List (PRCL) reconciliation:

1. Design Submittal 1 (SD1) Room Contents PDF (Attachment R), containing the marked-up SD1 AE’s User Group Meeting (UGM) room-content comments; and

2. The CFM baseline Project Room Contents List excel documents: VA STLHCS-JC SD1 Engineering (Attachment S) and Inpatient Tower (Attachment T).

The SD1 Room Contents document represents comments and markups recorded during the accomplished SD1 submission. The September 2022 and October 2022 PRCL documents represent the CFM Planning Project Room Contents baseline derived from SD1 driven Program For Design updates and will be provided to onboarding Designer of Record (DOR). These materials may not reflect all UGM comments or subsequent Government decisions and shall not be considered complete, current, or fully reconciled.

Following award, the IOTA contractor shall compare and document discrepancies in the reference materials;

identify incorporated, omitted, conflicting, duplicate, or unclear room-content information; and submit unresolved items to the COR for Government clarification or approval as required in Deliverable 16.2.3. UGM comments and markups shall not be treated as approved requirements unless verified or approved by the Government. The IOTA https://vatilms.va.gov/vatilms/reports https://dha.max.gov/milstd1691

10 | P a g e contractor shall not direct the A/E. Accepted comments shall be routed by the Government through the approved CFM/USACE/A/E process. SD1 validation shall be records-based, using the original SD1 UGM recordings, transcripts, minutes, and documented Government decisions to trace redlines and markups to their source. New service-line/user-group meetings shall not be used to reapprove historical SD1 markups. Supported changes shall be submitted through the COR to CFM for confirmation and formal PRCL updates in SEPS; unresolved or unverifiable items shall be carried into the next design review. User-group participation in subsequent design development remains required as applicable.

Using the A/E supplied Revit files, provide 3D mock-ups of each room type; excluding duplicate room types. The IOTA contractor shall report on all mock-up services completed with resulting recommendations and findings.

Mock-ups must not be used to redirect design or relocate utilities. They can be used for location of contents that do not touch utilities, staff orientation, or CONOPS development.

TO1 includes iterative FF&E/equipment layouts and associated model updates for the Bed Tower (BT), Engineering Building (ENG), Motor Pool (MP), and Opioid Treatment Program Clinic (OTP) under Deliverables 16.2.12- BT/ENG/MP/OTP. These layouts shall support the ordered SD2, DD1, DD2, CD1, and CD2/100% CD review packages.

Final FF&E layouts shall be submitted for STL VA approval in accordance with the applicable component requirements in Section 8.1.

16.2.1-BT FF&E Cut Sheets – BT

(Bed Tower) Bed Tower cut sheets shall include the item photograph; finishes;

specifications; instructions; manufacturer/model or basis-of-design item; dimensions; weight and structural requirements where applicable; installation and clearance requirements; utility and MEP requirements; network and interoperability requirements;

training requirements; warranty and maintenance requirements;

test-equipment requirements; VA-SEPS JSN. Information shall be specific enough for the VA to understand, purchase, and install the item but sufficiently performance-based to preserve competition for brand-name-or-equal procurement. Basis-of-design requirements shall be developed through applicable User Group Meetings and design workshops. Cut-sheet information shall be developed progressively: preliminary basis-of-design information for SD2; completed basis-of-design cut sheets for priority equipment for DD1; and completed basis-of-design cut sheets for remaining equipment for DD2. Priority equipment includes long-lead, HCHT, NAC, networked medical, and architecturally significant equipment. Subsequent submissions shall update previously submitted information. Specific delivery dates shall be established in the applicable Task Order.

16.2.1-

ENG

FF&E Cut Sheets – ENG (Engineering Building)

Engineering Building cut sheets shall include the item photograph;

finishes; specifications; instructions; manufacturer/model or basis-of-design item; dimensions; weight and structural requirements where applicable; installation and clearance requirements; utility and MEP requirements; network and interoperability requirements; training requirements; warranty and maintenance requirements; test-equipment requirements; VA-SEPS JSN.

Information shall be specific enough for the VA to understand, purchase, and install the item but sufficiently performance-based to preserve competition for brand-name-or-equal procurement.

Basis-of-design requirements shall be developed through

11 | P a g e applicable User Group Meetings and design workshops. The contractor shall prioritize long-lead, HCHT, networked medical, and architecturally significant equipment.

16.2.1-

MP

FF&E Cut Sheets – MP (Motor Pool)

Motor Pool cut sheets shall include the item photograph; finishes;

specifications; instructions; manufacturer/model or basis-of-design item; dimensions; weight and structural requirements where applicable; installation and clearance requirements; utility and MEP requirements; network and interoperability requirements;

training requirements; warranty and maintenance requirements;

test-equipment requirements; VA-SEPS JSN. Information shall be specific enough for the VA to understand, purchase, and install the item but sufficiently performance-based to preserve competition for brand-name-or-equal procurement. Basis-of-design requirements shall be developed through applicable User Group Meetings and design workshops. The contractor shall prioritize long-lead, HCHT, networked medical, and architecturally significant equipment.

16.2.1-

OTP

FF&E Cut Sheets – OTP (Opioid Treatment Program Clinic)

OTP Clinic cut sheets shall include the item photograph; finishes;

specifications; instructions; manufacturer/model or basis-of-design item; dimensions; weight and structural requirements where applicable; installation and clearance requirements; utility and MEP requirements; network and interoperability requirements;

training requirements; warranty and maintenance requirements;

test-equipment requirements; VA-SEPS JSN. Information shall be specific enough for the VA to understand, purchase, and install the item but sufficiently performance-based to preserve competition for brand-name-or-equal procurement. Basis-of-design requirements shall be developed through applicable User Group Meetings and design workshops. The contractor shall prioritize long-lead, HCHT, networked medical, and architecturally significant equipment.

16.2.2 Re-use and Disposal

Plan

(Attachment H is a representation of required data/information.

Actual deliverable data/information requirements are defined in SharePoint tool)

Plan shall only include JC Major impacted items. The contractor shall use the OCAMS Activation SharePoint list to develop and maintain the FF&E/Equipment Reuse and Disposal Plan so status and changes are reflected throughout the project lifecycle. The plan shall describe the method for determining whether equipment is reusable; incorporate reusable equipment into the room-contents and acquisition plans so reuse is included in the final budget and procurement effort; identify all items proposed for disposal; and document proposed disposition methods and locations in the Re-Use Plan list for Government review. The Government remains responsible for approving and disposing of Government property. Accountable equipment shall be coordinated with SCM/NX and HTM/Biomed.

Plan is to be captured in the Re-Use Plan list on the project’s

16.2.3-BT Design Submittal 1 (SD1) Validation Package - BT

The IOTA contractor shall perform records-based SD1 validation as described in Section 16.2.

12 | P a g e

IOTA contractor is to validate the documented historical UGM comments captured in the Design Submittal 1 (SD1 Validation) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions not consistent with UGMs and the Project Room Contents List (PRCL). This report will be provided to the COR as the facility submittal response to CFM/USACE. The report is to be provided graphically by electronically marking up drawing documents as well as a summary sheet of conflicts.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.3-

ENG

Design Submittal 1 (SD1) Validation Package - ENG

The IOTA contractor shall perform records-based SD1 validation as described in Section 16.2.

IOTA contractor is to validate the documented historical UGM comments captured in the Design Submittal 1 (SD1 Validation) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions not consistent with UGMs and the Project Room Contents List (PRCL). This report will be provided to the COR as the facility submittal response to CFM/USACE. The report is to be provided graphically by electronically marking up drawing documents as well as a summary sheet of conflicts.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.3-

MP

Design Submittal 1 (SD1) Validation Package - MP

The IOTA contractor shall perform records-based SD1 validation as described in Section 16.2.

IOTA contractor is to validate the documented historical UGM comments captured in the Design Submittal 1 (SD1 Validation) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions not consistent with UGMs and the Project Room Contents List (PRCL). The report shall include all long-lead, HCHT, NAC, networked medical, and architecturally significant equipment present in the PRCL. This report will be provided to the COR as the facility submittal response to CFM/USACE. The report is to be provided graphically by electronically marking up drawing documents as well as a summary sheet of conflicts.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.3-

OTP

Design Submittal 1 (SD1) Validation Package - OTP

The IOTA contractor shall perform records-based SD1 validation as described in Section 16.2.

IOTA contractor is to validate the documented historical UGM comments captured in the Design Submittal 1 (SD1 Validation) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions not consistent with UGMs

13 | P a g e and the Project Room Contents List (PRCL). This report will be provided to the COR as the facility submittal response to CFM/USACE. The report is to be provided graphically by electronically marking up drawing documents as well as a summary sheet of conflicts.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.4 A/E Physical Mock-Up

Review Report

The contractor shall attend A/E Mockup-Up review sessions;

document observations and requested changes that impact responsibilities identified in this contract; and provide findings, recommendations in a Mock-Up Review Report. The contractor shall not furnish the A/E-required physical mock-up, redirect the design, or relocate utilities.

Mock-up report must be uploaded into a document library on the project’s SharePoint site.

16.2.5-BT Design Submittal 2 (SD2) Support Package -

BT

The IOTA contractor participates in A/E design workshop meetings for the Bed Tower and separate from the A/E, captures comments related to space design and changes to room contents. During review of the A/E submittal, the IOTA contractor will develop a conflict report identifying concerns/inclusions/omissions not consistent with UGMs. Additionally, the conflict report will identify room contents that are not consistent with what was requested and described by users.

For SD2, the contractor shall provide the COR with preliminary basis-of-design FF&E information identifying generic salient characteristics and preliminary structural, utility, network requirements, and space considerations as applicable. Detailed cut sheets shall follow the phased requirements of Deliverable 16.2.1.

Initial dates may change due to actual construction award and confirmed schedules. The date will be provided by the COR based on timelines from CFM/USACE.

Additionally, changes to rooms and their contents must be captured in the Room-by-Room FF&E list identified in deliverable

16.2.8-BT.

Design submittal shall include:

A. A conflict report which identifies conflicts between space-related user requests and A/E provided design documents.

B. Included in the conflict report, identification of all conflicts between user requested FF&E and contents identified in A/E design documents.

C. Preliminary basis-of-design information for priority equipment, consistent with Deliverable 16.2.1.

D. Graphical electronic markup of drawing documents and a summary sheet of conflicts.

14 | P a g e

E. Updated Room-by-Room FF&E / Project Room Contents List (PRCL) entries when room or equipment changes are identified.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.5-

ENG

Design Submittal 2 (SD2) Support Package -

ENG

The IOTA contractor participates in A/E design workshop meetings for the Engineering Building and separate from the A/E, captures comments related to space design and changes to room contents.

During review of the A/E submittal, the IOTA contractor will develop a conflict report identifying concerns/inclusions/omissions not consistent with UGMs. Additionally, the conflict report will identify room contents that are not consistent with what was requested and described by users.

For SD2, the contractor shall provide the COR with preliminary basis-of-design FF&E information identifying generic salient characteristics and preliminary space, structural, utility, and network requirements as applicable. Detailed cut sheets shall follow the phased requirements of Deliverable 16.2.1.

Initial dates may change due to actual construction award and confirmed schedules. The date will be provided by the COR based on timelines from CFM/USACE.

Additionally, changes to rooms and their contents must be captured in the Room-by-Room FF&E list identified in deliverable

16.2.8-ENG.

Design submittal shall include:

A. A conflict report which identifies conflicts between space-related user requests and A/E provided design documents.

B. Included in the conflict report, identification of all conflicts between user requested FF&E and contents identified in A/E design documents.

C. Preliminary basis-of-design information for priority equipment, consistent with Deliverable 16.2.1.

D. Graphical electronic markup of drawing documents and a summary sheet of conflicts.

E. Updated Room-by-Room FF&E / Project Room Contents List (PRCL) entries when room or equipment changes are identified.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.5-

MP

Design Submittal 2 (SD2) Support Package -

MP

The IOTA contractor participates in A/E design workshop meetings for the Motor Pool and separate from the A/E, captures comments related to space design and changes to room contents. During review of the A/E submittal, the IOTA contractor will develop a conflict report identifying concerns/inclusions/omissions not consistent with UGMs. Additionally, the conflict report will identify room contents that are not consistent with what was requested and described by users.

15 | P a g e

For SD2, the contractor shall provide the COR with preliminary basis-of-design FF&E information identifying generic salient characteristics and preliminary space, structural, utility, and network requirements as applicable. Detailed cut sheets shall follow the phased requirements of Deliverable 16.2.1.

Initial dates may change due to actual construction award and confirmed schedules. The date will be provided by the COR based on timelines from CFM/USACE.

Additionally, changes to rooms and their contents must be captured in the Room-by-Room FF&E list identified in deliverable

16.2.8-MP.

Design submittal shall include:

A. A conflict report which identifies conflicts between space-related user requests and A/E provided design documents.

B. Included in the conflict report, identification of all conflicts between user requested FF&E and contents identified in A/E design documents.

C. Preliminary basis-of-design information for priority equipment, consistent with Deliverable 16.2.1.

D. Graphical electronic markup of drawing documents and a summary sheet of conflicts.

E. Updated Room-by-Room FF&E / Project Room Contents List (PRCL) entries when room or equipment changes are identified.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.5-

OTP

Design Submittal 2 (SD2) Support Package -

OTP

The IOTA contractor participates in A/E design workshop meetings for The OTP Clinic and separate from the A/E, captures comments related to space design and changes to room contents. During review of the A/E submittal, the IOTA contractor will develop a conflict report identifying concerns/inclusions/omissions not consistent with UGMs. Additionally, the conflict report will identify room contents that are not consistent with what was requested and described by users.

For SD2, the contractor shall provide the COR with preliminary basis-of-design FF&E information identifying generic salient characteristics and preliminary space, structural, utility, and network requirements as applicable. Detailed cut sheets shall follow the phased requirements of Deliverable 16.2.1.

Initial dates may change due to actual construction award and confirmed schedules. The date will be provided by the COR based on timelines from CFM/USACE.

16 | P a g e

Additionally, changes to rooms and their contents must be captured in the Room-by-Room FF&E list identified in deliverable

16.2.8-OTP.

Design submittal shall include:

A. A conflict report which identifies conflicts between space-related user requests and A/E provided design documents.

B. Included in the conflict report, identification of all conflicts between user requested FF&E and contents identified in A/E design documents.

C. Preliminary basis-of-design information for priority equipment, consistent with Deliverable 16.2.1.

D. Graphical electronic markup of drawing documents and a summary sheet of conflicts.

E. Updated Room-by-Room FF&E / Project Room Contents List (PRCL) entries when room or equipment changes are identified.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.6-BT Design Submittal 3 (DD1) Support Package -

BT

IOTA contractor participates in A/E design workshop meetings for the Bed Tower.

IOTA contractor is to validate user comments during A/E UGMs are captured in the Design Submittal 3 (DD1) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions with FF&E not consistent with UGMs and the Project Room Contents List (PRCL). This report will be provided to the COR as the facility submittal response to CFM/USACE. The report is to be provided graphically by electronically marking up drawing documents as well as a summary sheet of conflicts.

As applicable to this design milestone, the submittal shall include completed basis-of-design cut sheets for priority equipment, as identified in 16.2.1 deliverable, and preliminary basis-of-design information (generic cut sheets) for all remaining FF&E.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.6-

ENG

Design Submittal 3 (DD1) Support Package -

ENG

IOTA contractor participates in A/E design workshop meetings for the Engineering Building.

IOTA contractor is to validate user comments during A/E UGMs are captured in the Design Submittal 3 (DD1) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions with FF&E not consistent with UGMs and the Project Room Contents List (PRCL). This report will be provided to the COR as the facility submittal response to CFM/USACE. The report is to be provided graphically by electronically marking up drawing documents as well as a summary sheet of conflicts.

17 | P a g e

As applicable to this design milestone, the submittal shall include completed basis-of-design cut sheets for priority equipment, as identified in 16.2.1 deliverable, and preliminary basis-of-design information (generic cut sheets) for all remaining FF&E.

Submittal is to be uploaded into a document library on the project’s SharePoint site.

16.2.6-

MP

Design Submittal 3 (DD1) Support Package -

MP

IOTA contractor participates in A/E design workshop meetings for Motor Pool.

IOTA contractor is to validate user comments during A/E UGMs are captured in the Design Submittal 3 (DD1) materials. The IOTA contractor will prepare a conflict report that identifies concerns/inclusions/omissions not consistent with…