IWTP SCADA Quesitons Vendor Questions and Answers 27Jul26.pdf

Support for the Industrial Wastewater Treatment Plant

Questions from the Vendors

Q1. Do you have access to the current Allen Bradley PLC and Ignition SCADA program files, and will you be able to provide the files to the contract awardee?

A1. Available files have been loaded to SAM.gov

Q2. Is upgrading the current Allen Bradley hardware and software to the latest versions and creating a SCADA native to Allen Bradley an acceptable solution, or would you rather migrate to a different controls platform entirely?

A2. No, this is due to non-available local support. We need to see a different platform

Q3. 3. The issues that you are experiencing with the existing system are more to do with the support and implementation of the hardware and software than the hardware and software itself.

We feel strongly that keeping your hardware and software and upgrading it to the latest versions as well as correcting the limitations is the cost-effective action to take. Based on this, would it be allowed for the vendor to submit a proposal to replace the server hardware, computer hardware, upgrade the software, and properly document the system through reverse engineering?

A3. For HAFB, the cost-effective solution does not work long term. This has been an issue since 2010

Q4. To accurately prepare our quote, we require additional information on the following: Piping and Instrumentation Diagrams (P&IDs), Input/Output (IO) count, Screen count, and any existing system notes that might be available. Will this be provided?

A4. Reference Q1

Q5. Will the electrical drawings for the existing system be provided for review? (e.g., Cabinet Layouts, Electrical Schematics, Bill of Material / Instrument list, P&ID, Pneumatic Schematics, Network Diagrams)

A5. Reference Q1

Q6. What version of Ignition is the existing HMI application developed in?

A6. Currently unknown

Q7. Will the Ignition program for the existing system be provided for review?

A7. No, HAFB does not have the capability to extract information requested

Q8. What version of Rockwell Studio 5000 is the existing PLC code developed in?

A8. Currently unknown

Q9. Will the existing PLC code be provided for review?

A9. Reference Q7

Q10. Will the tags / structure of the existing database be shared for review?

A10. Reference Q1

Q11. How many tags are being monitored / controlled by the existing system?

A11. Reference Q1

Q12. There were a number of older VFDs located adjacent to the PLC cabinets that we suspect are part of the equipment being controlled by this system. Is there manufacturer information available for these components?

A12. HAFB is planning to replace prior to project start

Q13. It was mentioned during the bid walk that a single SCADA software is preferred over the existing Ignition / Allen Bradley system. Is there a preferred or recommended SCADA software for the application?

A13. Infoscan or equivalent in performance and capabilities

Q14. Is there an operations manual available for the existing system, and will it be made available for review?

A14. Reference Q1

Q15. Is there some kind of written narrative or process description of the existing control system available for review?

A15. Reference Q1

Q16. Please confirm which existing system files and supporting documentation will be available to the successful contractor, including:

a. current PLC program files and controller backups;

b. HMI/SCADA project files and historian configuration;

c. available P&IDs, control narratives, sequences of operation, I/O lists, alarm and setpoint lists, and loop documentation;

d. access information needed to retrieve and migrate the existing configurations; and

e. native editable drawing files. Please identify any of these materials that are not available or will not be provided.

A16. Reference Q1

Q17. Please provide any available drawings or documentation showing:

a. modifications made after the 31 May 2012 record drawings;

b. the current PLC, remote-I/O and communications architecture;

c. radio, fiber, copper, modem or serial communication links;

d. connections extending outside Building 575; and

e. the existing or planned interface with the base EMCS.

A17. Reference Q1

Q18. The drawing index appears to reference sheets EI-600, EI-601, EI-602, EI-620 and EI-621 that were not included in the released drawing set. Please provide those sheets, if they exist, or confirm that they were never completed.

A18. Reference Q1

Q19. Please identify the equipment connected through any existing 1756-DHRIO or other legacy communication modules and state whether migration of those connected devices is included in the contract scope.

A19. Migration/replacement of all legacy control system components IS fully included in the contract scope. You are required to safely remove all legacy PLC hardware, obsolete wiring, and communication modules

Q20. Please clarify what the contractor is expected to deliver for the Risk Management Framework process and what will constitute satisfactory completion of that work. Is the contractor expected to provide a securely configured and hardened system, together with the supporting RMF documentation and test results needed for a Government-led authorization process? Or is the contractor expected to prepare and maintain the full authorization package through Government assessment and issuance of an Authorization to Operate?

A20. The contractor is expected to provide securely configured and hardened system, together with the supporting RMF documentation and test results needed for a Government-led authorization process

Q21. Please confirm whether issuance of an Authorization to Operate is required before final acceptance or contract completion. If so, please explain how the Government’s review, assessment and authorization activities will be coordinated within the 180-day period of performance.

A21. The contractor is not expected to obtain the final, government-signed ATO within the 180-day PoP

Q22. Please clarify how the Government and the contractor will divide responsibility for the Risk Management Framework process. Will this SCADA system be covered by an existing Hill AFB cybersecurity authorization, or will it require a separate authorization?

A22. A separate authorization will be required due to the new system replacing another system that is already have been authorize

Q23. Please identify the cybersecurity requirements and any existing Government documentation that will apply to this project.

A23. DAFGM2024-32-01, a new DAFGM2026-32-01 is currently in a draft and contractor will follow those requirements once its publication

Q24. Please confirm whether the Government will provide the responsible cybersecurity points of contact and access to any Government systems needed to support the review and authorization process.

A24. Information will be provided with CO approval

Q25. Please identify who will perform the cybersecurity scans, review the findings, determine what corrections are required, approve any remaining risk, and issue the final authorization.

A25. ISSM, information will be provided with CO approval

Q26. If the Government’s cybersecurity review continues after the system is installed and accepted, please clarify what support the contractor must continue to provide and for how long.

A26. The contractor must provide remote, administrative support for post-installation to answer any technical questions and resolve any discrepancies on the system. Support for new requirements or any ongoing operational maintenance

Q27. Please clarify how users are expected to log in to and be authenticated by the SCADA system, including:

a. whether the system will join an Air Force domain or operate as a standalone OT enclave;

b. the Government-approved MFA method for local and administrative access;

c. whether Government identity, certificate or directory services will be furnished; and

d. the required method for authentication when external network connectivity is unavailable.

A27. a. The system can be joined to the COIN network or can remain standalone.

b. If connected by COIN then users will have to go through the MFA method for local and administrative access. If standalone then local privileged and standard user accounts.

c. If COIN is connected, than the identity, certificate or directory is handled by AFCEC.

d. No external network connectivity is authorized rather its COIN network or standalone.

Q28. SOW §§5.3.2 and 5.3.3 require each controller to include a touchscreen and two RS-485 communication ports. Please clarify whether those features must be built directly into the controller itself, or whether the requirement may be satisfied through manufacturer-supported components installed as part of the controller panel. Please confirm whether this type of integrated controller-panel arrangement would satisfy the SOW requirements.

A28. The touchscreen must be a built-in, native component of the controller hardware itself. (MPC Controller Hardware Characteristics) explicitly requires fully interactive integrated digital touchscreen for IP entry, configuration, diagnostics, and setup without a laptop

Q29. Please clarify whether the channel counts, signal types, electrical ratings and other limitations identified in SOW §5.4 are intended as exact mandatory module configurations, minimum performance requirements, or representative acceptable ranges.

A29. Yes

Q30. Please confirm the required treatment of existing spare, unused and abandoned I/O points, including whether:

1. all currently wired spare or unused channels must be recreated in the replacement system;

2. abandoned points may be removed with Government approval; and

3. the completed system must include a specified percentage or quantity of installed spare

I/O capacity.

A30. Need to research response. 1. Yes 2. Yes 3. Yes, 10% above the actual count

Q31. Please clarify how the "single supplier" requirement in SOW §1.1.3 relates to the "single, unified software platform" requirement in SOW §6.1.1. Does "single supplier" mean that the controllers, I/O, SCADA software and related components must all come from one manufacturer? Or may a single prime contractor or system integrator provide and take full responsibility for an integrated system that includes products from more than one manufacturer?

A31. Yes, from one supplier and the same platform

Q32. Please confirm whether the PLC programming and the SCADA/HMI development may use their respective manufacturer-supported tools, provided that the operator graphics, alarms, historical data, diagnostics and other SCADA functions are brought together in one unified operational platform. Alternatively, does the SOW require controller programming, HMI graphics, alarm management, historical trending and system diagnostics to be performed within a single manufacturer’s software environment?

A32. Using separate, manufacturer-supported tools for PLC programming and SCADA/HMI development—even if the final operator interface is unified—is explicitly prohibited by the SOW. Unified Software Platform Characteristics, which mandates:

A Single unified software environment for programming, graphics, alarming, trending, historian functions, and diagnostics. The system eliminates multivendor toolchains.

Q33. Please confirm whether offerors may propose a currently manufactured and supported server that meets or exceeds the performance, storage and redundancy requirements of the Dell PowerEdge T340 specified in SOW §5.1.1.

A33. HAFB requires specified server

Q34. Please confirm whether a currently supported version of Windows Server may be proposed, provided that it is compatible with the approved SCADA platform and all applicable cybersecurity and RMF requirements.

A34. HAFB requires specified Windows Server

Q35. Please identify the required environmental and electrical classification for each control-panel location, including the Main and TTO panels in Building 575 and any other locations included in the project. Please confirm:

a. whether any panel location is classified as a hazardous area;

b. the required enclosure rating for each location; and

c. whether any location is exposed to corrosive chemicals or other conditions requiring stainless-steel or corrosion-resistant enclosures. If the Government intends the replacement panels to match the ratings of the existing installed enclosures, please confirm those ratings.

A35. Existing panels meet electrical classification. Replacement panels will match existing installed enclosures

Q36. Please clarify which existing field devices and wiring are to be replaced and which are expected to remain. Should offerors assume that the existing instrumentation, analyzers, transmitters, switches, valve feedback devices, motor starters, variable-frequency drives, and field wiring will be reused and reterminated, tested during the required loop checks, and retained unless specifically identified for replacement?

A36. Existing field devices will be reutilized

Q37. Please clarify how pre-existing failed, inaccurate, or nonfunctional equipment discovered during installation or loop testing will be addressed.

A37. Validate plant operations/field devices prior to project start. Anything failed after that will be the contractors responsibility

Q38. SOW §4.2.1 requires removal of obsolete wiring, unsecured communication adapters and redundant field programming ports. Please identify:

a. whether "obsolete wiring" includes only internal panel wiring or also field cabling;

b. the communication adapters and programming ports intended for removal;

c. the modems referenced in SOW §5.2.4; and d. any communication equipment outside the IWTP building that is included in the replacement scope.

A38. Obsolete wiring will be in the panels. Field wiring can remain in place if functional and labeled as Spare. Remaining questions will reference available information in Q1

Q39. Does the Government have any asbestos or lead-based paint survey reports for the areas where the work will be performed? If so, please provide those reports and identify any findings relevant to the proposed demolition or installation work.

A39. Abatement shop can provide a non-ACM/non-LBP report. This will change if new wall/roof penetrations are made. Currently, installed conduits/wiring will be reutilized which will preclude additional testing

Q40. Please confirm whether the Government anticipates any asbestos or lead-based paint disturbance or abatement under this contract and, if so, whether that work should be included in the firm-fixed price.

A40. Reference Q39

Q41. SOW §4.1.2 identifies Environmental Abatement Inc. and Eagle Environmental as pre-approved specialty contractors. Please clarify whether one of those firms must be used or whether the contractor may use another properly licensed and certified asbestos or lead-abatement contractor in Utah.

A41. Vendors listed above are certified/authorized to perform work on HAFB. No other vender will be accepted

Q42. Please confirm:

a. whether the required software license supporting at least 100,000 active I/O points must be perpetual, or whether a subscription license is acceptable;

b. the required number of concurrent operator, engineering, and administrative users; and

c. whether Modbus TCP, BACnet/IP, and OPC UA must be configured and demonstrated as part of the completed system, or whether the software must only include licensed native support for those protocols for future use.

A42. No subscriptions to the GUI updates, they will be provided as needed. Number of operator, engineering and administrative users = 25. Requirement for Support: the contractor shall ensure native support for BACnet/IP, Modbus TCP, and OPC UA interoperability for future integration needs.

Q43. Please provide additional information about the required monitor-only connection between the new SCADA system and the base Energy Management and Control System under SOW §6.3.3. Please identify the existing Energy Management and Control System platform, the required communication protocol, the physical and network connection points, and the approximate number and type of alarms or data points to be transmitted.

A43. Reference Q1

Q44. Please clarify how the monitor-only restriction is expected to be maintained and which party will be responsible for providing and configuring any firewall, gateway, or other connection device, as well as the network connection, addresses, certificates, and programming required on the Government’s system.

A44. It works, in principle, as an extended OWS with no ability to manipulate SCADA. ~ 1% of total system is being monitored.

Q45. Does the Government require a system with an active Authorization to Operate (ATO) at turnover, or a system engineered to be accreditable with the Government executing the RMF / A&A?

A45. System engineered to be accreditable with the Government executing the RMF/A\&A

Q46. Who are the assigned Authorizing Official (AO), ISSM, and ISSE/SCA, and which RMF steps (Categorize, Select, Implement, Assess, Authorize, Monitor) is the contractor responsible for versus the Government?

A46. Government has assigned AO, ISSM and SCA. Contractor will assist Monitor step of the RMF cycle. The Government will handle the rest of the steps of the RMF cycle

Q47. What is the system security categorization (Confidentiality / Integrity / Availability) and the applicable NIST SP 800-53 control baseline and overlays, including the ICS/OT and AFCEC CS-CRG overlays?

A47. The current system CIA is LOW/LOW/LOW and will be NIST 800-53 Rev 5 with DAF Civil Engineer (CE) Control Systems (CS) Baseline Security Controls, 29 February

Q48. Is the SCADA system standalone / air-gapped, or connected to a base network (e.g., NIPRNet or a base control-system network)? Where is the authorization boundary drawn?

A48. Standalone

Q49. How are RMF activities expected to fit within the 180-day PoP, given A&A/ATO timelines often exceed that? Is an ATO a condition of Beneficial Occupancy, or a post-BOD activity?

A49. The contractor is not expected to obtain the final, government-signed ATO within the 180-day PoP

Q50. Documents reference CMMC Level 1. Please confirm the required CMMC level for the prime and for any subcontractor that will process, store, or transmit FCI/CUI, and whether OT design data on this effort is CUI.

A50. Prime and subcontractors must hold CMMC level 1 to perform work

Q51. Has the IWTP SCADA been designated Platform IT (PIT)? If so, does it follow a PIT-specific RMF path or inherit from an existing PIT enclave / site ATO?

A51. IWTP is a IS Major Application system

Q52. Which security controls are inherited from base infrastructure or an existing enclave (physical, network, personnel), and which must the contractor provide and document?

A52. IWTP is a standalone system and not attached to the base infrastructure

Q53. Does the current IWTP SCADA hold an ATO or RMF package that the replacement can leverage, or must a new package be built?

A53. IWTP does hold an ATO for the CURRENT system. New system will require a new ATO package

Q54. Will the system be tracked in eMASS? Is contractor eMASS access and data entry required, and who registers the system/package?

A54. Is entered in eMASS. Contractor will not be required to access/enter data.

Q55. Which DISA STIGs must be applied (Windows Server 2019, Windows 11, SCADA application, network devices), and is a documented STIG compliance/hardening report a deliverable?

A55. The final hardware and software configurations have not yet been selected, the exact list of applicable STIGs will be finalized post-award based on the contractor's proposed system architecture. Documented STIG compliance/hardening reports (including DISA STIG Viewer .ckl files and SCAP scan results) for all proposed components are required deliverables and must be submitted to the Government to support the RMF accreditation process.

Q56. Is ACAS/Nessus vulnerability scanning required for assessment? Who furnishes the scanner and performs/validates scans, and what residual-finding threshold is acceptable?

A56. ACAS/Nessus vulnerability scanning is required for the system. System must be able to handle the vulnerability scan without shutting down the system. Government will be performing the scan and will coordinate with contractor to help fix vulnerabilities

Q57. SOW §6.2.2 specifies MFA via an authenticator application. Will app-based MFA be accepted, or is DoD PKI (CAC/PIV) authentication required? Also, what is the required account-inactivity period after which accounts must be automatically disabled (SOW §6.2.3)?

A57. If connected by COIN then users will have to go through the MFA method for local and administrative access. If standalone then local privileged and standard user accounts

Q58. Who furnishes and accredits the network devices (switches, firewalls) — contractor or Government? Are specific hardened/APL-approved models required?

A58. Contractor Furnished, Government Accredited: The contractor is responsible for procuring (furnishing) all network devices (switches, firewalls) as part of the system deliverable. The Government retains the authority to accredit the devices prior to network connection. Device Requirements: Yes. All contractor-procured network devices must be active on the DISA DoD Approved Products List (APL) at the time of delivery and hardened in accordance with the latest DISA STIGs

Q59. During the one-year warranty, is ongoing cyber sustainment (patching, STIG updates, continuous monitoring, scan remediation) in scope, and to what SLA?

A59. No, ongoing cyber sustainment is out of scope for the one-year warranty, which strictly covers system defects and does not include SLAs for operational cybersecurity maintenance

Q60. Will the Government provide RMF templates (SSP, control implementation, POA&M), the CS-CRG, and reference-architecture artifacts to the awardee?

A60. Yes. The Government will provide blank templates of the SSP and POA\&M, as well as sanitized reference-architecture artifacts, to the awardee post-award

Q61. Please confirm the governing proposal due date and time. SF1449 states 27 Jul 2026 at 2:00 PM local; the Instructions & Evaluation Factors state 26 Jul 2026 at 2:00 PM MDT.

A61. Proposal are due No later than 3 August 2026 @ 0830 MDT. Window extend to correct error, and provide time for the questions and answers to be evaluated.

Q62. Given the technical and cybersecurity clarifications outstanding, will the Government consider a short extension of the proposal due date?

A62. Yes. Proposal are due No later than 3 August 2026 @ 0830 MDT

Q63. Beyond SF1449 and active SAM, what offer forms, fill-ins, certifications, or representations must the offeror submit?

A63. None

Q64. What CMMC / SPRS / UID evidence is expected with the proposal for the prime (and for FCI/CUI-handling subcontractors)?

A64. Evidence will be pulled from our system by the contract specialist

Q65. Is submission strictly by email to the two POCs, or is DoD SAFE acceptable for large files? Preferred file-naming convention and maximum attachment size?

A65. Email is the preferred submission method. Vendors may send multiple emails if necessary. Multiple emails submission should be numbered to ensure delivery. i.e. 1 of 3 etc.

Q66. Does the 40-page technical limit include BOM / manufacturer data sheets, resumes / certifications, and appendices, or only the technical narrative?

A66. 40 Page limit applies to the technical narrative. BOM, Manufacturer data sheets can be separate files.

Q67. Because this is LPTA, should the technical volume be limited strictly to the five stated evaluation elements, or will additional management / past-performance narrative be considered?

A67. The technical solutions to address the issues are the only factors that will be considered.

Q68. SOW §1.1.3 requires the system be designed, fabricated, programmed, tested, started up, and warranted by a "single supplier." Please confirm this is satisfied by a single prime contractor holding total responsibility while using qualified subcontractors (e.g., cybersecurity, abatement), rather than requiring one manufacturer/integrator to self-perform all work.

A68. Reference section 10.1.2

Q69. Will amendments and answers to offeror questions be posted to SAM.gov, emailed directly to interested offerors, or both?

A69. The solicitation will be amended. The amendment and the questions and answers will be posted on SAM.gov

Q70. Please provide the CLIN structure and the scope mapped to each CLIN (e.g., CLINs 0001– 0004). Is CLIN 0004 (Technical Data & Deliverables) separately priced or not-separately-priced?

A70. See solicitation SF 1449 pg. 3 for CLIN structure. CLIN 4 is not separately priced.

Q71. Which labor standards apply — the Service Contract Act (SCA) wage determination, Davis-Bacon Act construction wage rates, or both? Please provide the applicable wage-determination number(s).

A71. 52.222-41 Service Contract Labor Standards apply for this project.

Q72. Are performance and payment bonds, or specific insurance types/minimums, required for this effort given the demolition and installation work on the installation?

A72. Not required

Q73. Please define the boundary between the SCADA replacement and existing field infrastructure: which existing field instruments, motor controls, wiring, conduit, and junction boxes are to be reused, and which are in the Contractor’s scope to replace?

A73. Reference Q36

Q74. To meet SOW §1.2.3 (sustainment by 75 CES "without vendor dependence"), must the Contractor deliver the fully editable and unlocked application program/configuration and the development-software licenses/seats needed to modify it, with no runtime or licensing lockouts?

A74. Yes

Q75. Is a single, non-redundant central SCADA server with a single OWS acceptable as specified, or does the Government expect server redundancy/failover or additional operator or view-only clients?

A75. Yes, a single, non-redundant central SCADA server and a single Operator Workstation (OWS) are fully acceptable and meet the core requirements of this contract.

Furthermore, as noted, the Government will provide and expand additional Operator Workstations (OWS) in the future as needed. The installed system is explicitly required to support this seamless future expansion.

Q76. What historical-data retention period is required, and must existing historical/trend data be migrated from the legacy system to the new historian?

A76. Retention of historical data is not required and will not be part of the new historian

Q77. Will the Government provide the existing SCADA architecture, the complete point/tag list and I/O count, the controller make/model inventory, network diagrams, panel schedules, the alarm list, control narratives, HMI screenshots, and available as-builts?

A77. Reference Q1

Q78. As we are unable to attend a site visit, will the Government provide a site photo package (panels, enclosures, control room, field devices) and any record drawings?

A78. No photo packet provided. Reference Q1 for available documents

Q79. Will any site-visit notes, attendee Q&A, or job-walk summary provided to attending offerors be released to all offerors?

A79. No site notes taken by 75 CES or Contracting Office.

Q80. Can the Government provide the existing field-instrumentation list with signal types (4–20 mA, RTD, discrete, etc.) and counts, so the I/O module mix can be validated against SOW §5.4?

A80. Reference Q1

Q81. What communications and protocols are in service today, and are there legacy protocol gateways that must be retained?

A81. This will be a new SCADA closed loop

Q82. Will the Government furnish existing AutoCAD base drawings/backgrounds, and specify the required CAD version and layer/drafting standard for the As-Built deliverable (SOW §7.2.2)?

A82. Information will be provided to contractor after award

Q83. Please provide a copy and current revision of the 75th CS TAB K directive (1 April 2010) referenced in SOW §2.1.3.

A83. This reference is no longer applicable

Q84. What are the enclosure/panel space, power availability, and environmental conditions (H₂S, washdown, temperature) at controller locations?

A84. Reference Q35

Q85. Is the Dell PowerEdge T340 / Windows Server 2019 language an exact requirement, or will the Government accept a current-generation equivalent that meets or exceeds the specified intent? (The T340 generation is end-of-life.)

A85. Reference Q33/Q34

Q86. For RMF/STIG compliance, which Windows Server 2019 and Windows 11 editions are required (e.g., Enterprise, IoT Enterprise LTSC)?

A86. The most current versions applicable as approved by DISA and the DAF. LTSC will also use the most current OS versions and builds. All newly acquired control systems shall run on or be compatible with updates to the latest DoD approved OS. Please refer to DAFGM2024-32-01, 3.7 Software

Q87. Are the controller I/O channel counts, ratings, and resolutions in SOW §5.4 minimums, exact values, or meet-or-exceed targets?

A87. Meets or exceeds

Q88. Will the Government accept any modular controller meeting SOW §5.3 (face-mounted integrated touchscreen, ≥3 comm ports incl. 2× RS-485 + 1× 10/100 Ethernet, hot-swappable I/O), or is a specific product line expected?

A88. A controller will be deemed technically acceptable if it includes the integrated touchscreen, hot-swappable I/O, and provides native support for Modbus TCP, BACnet/IP, and OPC UA. A proposal based on a controller that does not meet these specific protocol requirements or is justified based on a non-existent RS-485 requirement, risks being found technically unacceptable.

Q89. Must the full 100,000 active-I/O license be furnished at turnover, or is it a scalable ceiling?

What is the current installed/active point count versus the 100,000 target, and what drives the 100,000 figure?

A89. Reference Q1. 100K figure is for future expansion

Q90. Please confirm all current and future required interfaces (Modbus TCP, BACnet/IP, OPC UA, serial RS-485 devices, and any legacy gateways).

A90. To be compliant, your proposed system must natively support BACnet/IP, Modbus TCP, and OPC UA. There is no contractual requirement to support Serial RS-485 devices, and all legacy communication gateways are to be removed as part of the demolition scope.

Q91. Please define the EMCS monitor-only alarm routing (SOW §6.3.3): interface owner, network boundary, exact tags/alarms to be exchanged, one-way (data diode) vs. firewalled, protocol preference, and whether Government-furnished network infrastructure is available.

A91. It works, in principle, as an extended OWS with no ability to manipulate SCADA. ~ 1% of total system is being monitored.

Q92. Please provide the HAFB P&ID visualization and HMI graphics standards, and confirm any color/alarm conventions beyond those in SOW §6.3.

A92. UFC 3-470-01 & UFGS 25 10 10 — Building Control Graphics Requirements

Q93. Please confirm the SOW §6.3.2 alarm palette is intended as written — notably Green = Out-of-Service/Manual and Blue = Low Alarm — as it differs from common ISA-101 practice.

A93. Green will be for device successful configuration. Blue, initial start of configuration.

Yellow for fault. Red for critical and emergencies

Q94. Will the Government provide the asbestos (ACM) and lead-based-paint (LBP) inspection reports before proposal submission, so demolition and abatement can be priced accurately?

A94. Based on current scope, there should be no ACM/LBP concerns unless wall penetrations are required.

Q95. Are Environmental Abatement Inc. and Eagle Environmental required/preferred only, or may other Utah-licensed and certified asbestos/lead abatement subcontractors be proposed?

A95. Reference Q41

Q96. Who is responsible for characterization, manifesting, transport, and disposal of demolished hazardous materials and electronic waste, and can the Government provide the HAFB environmental waste policy referenced in SOW §4.2.3?

A96. HAFB will collect electronics, wire etc. There is no other hazardous waste associated with this project unless there is an accident or contractor goes outside scope

Q97. What outage windows are available for cutover, loop checks, and commissioning, and are weekend/night outages permitted if pre-coordinated (per the 21-day notice)?

A97. Weekend/night outages are preferred

Q98. Will the Government witness the minimum 3-day FAT in person, remotely, or by report only, and is there a required FAT report template?

A98. The Government will witness Factory Acceptance Test (FAT)

Q99. SOW §8.4.2 requires 24-hour telephone support "for the operational life" of the system. Is this limited to the one-year warranty period, or expected for the system’s operational life? If the latter, should it be priced as separate annual option CLINs?

A99. SOW, para 8.4.2 amended to state: 24-hour Telephone support for one-year to match the warranty term. Price should be included in CLIN 1.

Q100. How is the Beneficial Occupancy Date (BOD) determined, and what are the Government’s acceptance criteria? The BOD sets the start of the warranty and the 3-month follow-up training.

A100. When the system passes initial Factory Acceptance Test, goes into active service and the 7 business day training has been complete.

Q101. Please provide the required delivery schedule/milestones for CDRLs A001–A006, and confirm whether any DD Form 1423 or specific data-item formats apply.

A101. Each CDRL has delivery time and acceptable file delivery types in the CDRL’s.

Q102. SOW §7.2.3 requires O&M manuals and license keys on secure USB media. Given DoD removable-media restrictions, please confirm the accepted delivery media/format (e.g., encrypted/approved USB, optical media, or electronic transfer).

A102. Searchable PDF or MS Word(.docx) delivered via DoD SAFE download

Q103. Will one factory-certified individual satisfy both the Lead Programmer and Site Superintendent requirement if qualified, or are separate individuals required?

A103. The roles are functionally distinct. A Site Superintendent's primary duty is on-site management, safety, subcontractor coordination, and daily oversight. A Lead Programmer's primary duty is focused, technical work involving software development, configuration, and testing.

Q104. How many 75 CES/IWTP staff should be assumed for the 7-day initial and 2-day follow-up training, and are materials required in hard copy, electronic, or both?

A104. 17 individuals

Q105. Please define the minimum local parts inventory for critical controller cards and network components, including acceptable location radius and next-day delivery expectation.

A105. Inventory will consist of locally available components necessary to rectify an emergency failure. Expectation will be to go to the vender location and say…I need this

Q106. What are the base access and badging requirements and typical lead times for Contractor personnel (background checks, escort vs. unescorted access, foreign-national restrictions, vehicle passes)?

A106. Base access required information:

Full Name / Date of birth / Driver’s License Number / State of Issuance

After all required information is submitted, base access should be granted within one week.

Q107. Will the Government furnish any property, equipment, workspace, network access, or secure storage on site, or must the Contractor provide all of these?

A107. There will be no network access, property or equipment provided. Workspace will need to be defined. Some limited secure storage is available.

Q108. Is a formal Contractor Quality Control (CQC) plan implementing the three-phase inspection system (SOW §3.1.3) a required submittal, and at what stage?

A108. Yes, it is a required submittal