Questions and Answers Command Center.docx
DOCX document 40 KB Posted
- Attached to
- PACAREA Battle Watch Command Center Display System (CCDS) Federal contract opportunity
- Solicitation number
- 75150PR260000082
About this file
This is a Questions and Answers document associated with the Battle Watch Command Center Display System (CCDS) Integration solicitation for the U.S. Coast Guard Pacific Area (PACAREA) in Alameda, California. The document itself does not contain substantive information about required products or services; rather, it serves as a repository for clarifications and responses to contractor inquiries regarding the solicitation. The Q&A file format is typical for RFQs and solicitations where the government addresses questions from potential bidders to ensure clear understanding of requirements prior to proposal submission. Contractors should review all Q&A entries for relevant clarifications that may impact their offer development, cost proposals, and compliance with stated requirements outlined in the primary solicitation documents, including the Statement of Work (SOW). The deadline for proposal submission remains September 20, 2026, at 8:00 a.m. Pacific Time, and all inquiries should be directed to Contracting Specialist Elizabeth Tam-Hurley at Elizabeth.h.tam-hurley@uscg.mil, with site visit requests directed to Jacob Dupree at (510) 437-3701.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| SF 30 Signed.pdf | ||
| Wage Determination 2015-5623.pdf | ||
| SOW PACAREA_Redacted.pdf |
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
1. AUXILIARY SCREEN DIMENSIONS - APPARENT INCONSISTENCY.
SOW Section 2, Hardware Procurement & Delivery / Video Wall Specifications, requires a video wall array 29 feet wide by 8 feet high, "and at minimum two auxiliary screens (30 feet wide by 8 feet high)." SOW Section 2, Facility Specifics, describes the space as 24 by 29 feet. Two auxiliary screens each 30 feet wide cannot be accommodated on any wall of a 24 by 29 foot room. Please clarify whether the auxiliary screens are (a) two large-format displays of a size to be proposed by the offeror, (b) an aggregate auxiliary canvas totaling 30 feet wide by 8 feet high, or (c) as literally stated. This materially affects display quantity and price.
No for the aux screens they will go on the adjacent 30ft wall, only 2 are needed about 55” and supports on the wall are already in place
2. NUMBER AND CLASSIFICATION OF NETWORK ENCLAVES.
SOW Section 2, Network & Security, states the system shall "Manage Sensitive and Classified Information across 4 separate networks (1 unclassified, 2 classified)." One unclassified plus two classified totals three, not four. SOW Section 6, Security & Signal Isolation, further references isolation between "Unclassified, Secret, and TS/SCI visual panels." Please confirm the total number of enclaves and the classification level of each. Each enclave requires an independent processing and transport path, so this drives both architecture and price.
3. STRUCTURAL LOAD ASSESSMENT RESPONSIBILITY.
SOW Section 2, Facility Specifics, states "floor loading capacity is unknown," while SOW Section 2, Out of Scope, excludes major structural civil engineering modifications. Will the Government furnish a structural load assessment for the one-foot raised floor and for the wall framing attachment points, or is that assessment the contractor's responsibility and within scope?
The floor is good to go and the CG is leveling out the walls where the CCDS will go but should the company need to add mounting support that’s on them.
4. PERSONNEL SECURITY AND FACILITY CLEARANCE REQUIREMENTS.
Please state (a) the personnel security clearance level required for contractor installation, integration, and test personnel; (b) whether a Facility Clearance (FCL) is required of the offeror at time of award; and (c) whether, during the 30-day downtime window, the space will be sanitized to permit escorted uncleared installation personnel.
Space will be shut off from district side but contractors should have ability to enter should they need to with escort.
5. VERIFICATION METHOD FOR THE 99.999% UPTIME CRITERION.
SOW Section 6, Visual Quality & Reliability, requires an uptime rating of 99.999%. That equates to approximately 5.3 minutes of unavailability per year and cannot be empirically demonstrated within the period of performance. Will the Government accept manufacturer-published availability/MTBF ratings together with a documented redundancy design as evidence of compliance, or is a specific test protocol required for acceptance?
It will only have NIPR and SIPR, we had mentioned more in the solicitation should the PAC watch be thinking of JWICS but they are just going baseline class/unclass
6. SCOPE OF SOURCE INTEGRATION - APPARENT INCONSISTENCY.
SOW Section 2, Source Integration, states "Integration with existing systems is not required." SOW Section 6, Tactical Integration, requires that the display processor "ingest and render all primary Coast Guard systems without visual latency or system lag." Please identify which systems constitute the 16 primary sources, and confirm the boundary of contractor responsibility where those sources are existing Government systems.
Sources will be from 8 NIPR Work stations and 8 SIPR
7. GOVERNMENT FURNISHED EQUIPMENT AVAILABILITY.
SOW Section 2, Out of Scope, identifies end-user workstation PCs as GFE. Will GFE workstations be installed and available on site prior to Phase 4 (System Integration & Testing), so that end-to-end source routing can be verified during the SATP?
GOV computers will be in built out space before CCDS goes up.
8. PERIOD OF PERFORMANCE.
SOW Section 2 states a 90-day timeline with a 30-day downtime tolerance. Please confirm (a) whether the 30-day downtime window runs concurrently within the 90 days, and (b) whether the 90 days is measured from date of award or from Government approval of the System Design Document at Phase 2 (CDR).
From Award, plan would be they start work at the start of January with the month of January being the 30 day period of down.
9. SERVICE CONTRACT ACT APPLICATION.
Wage Determination 2015-5623, Revision 31 (Alameda and Contra Costa Counties) is attached to the solicitation. Please confirm SCA applicability to this requirement. We note that the wage determination contains no occupation corresponding to audiovisual or video wall integration. Should offerors map installation labor to occupations 23181-23183, Electronics Technician Maintenance I-III, or does the Government anticipate a conformance action (SF-1444) after award?
We do not anticipate a conformance action after award.
10. GOVERNMENT ESTIMATE.
Is there a Government estimate, budget ceiling, or not-to-exceed value established for this requirement?
The solicitation is requesting a quote for the service described in the SOW. No estimate or budget listed. Please provide a quote.
11. SITE VISIT.
Please confirm whether a site visit is required for a quote to be considered responsive, and the latest date on which a site visit can be scheduled in advance of the 20 September 2026 due date.
Site visit is not required.
12. Will a DD Form 254 be issued? Please state the facility clearance required of the contractor and the personnel clearance required for technicians working on the watch floor.
They will have escorted access at all times so just baseline secure space clearance.
13. SOW Section 2 requires dedicated switching between unclassified and classified. SOW Section 6 requires absolute isolation between Unclassified, Secret, and TS/SCI panels. Does the Government require physically separate distribution per enclave, or will an accredited multi-domain processor be accepted, and under what accreditation?
Under Department of Defense (DoD) and Committee on National Security Systems (CNSS) cybersecurity policies, NIPRNet (Unclassified) and SIPRNet (Secret) AV-over-IP networks and endpoints cannot share unclassified/classified switching infrastructure, controllers, or processors. They must remain completely physically separated (air-gapped) A stated quantity of one (1) controller/processor cannot be cross-connected to both NIPR and SIPR IP networks simultaneously without violating network separation mandates.
14. SOW Section 2 cites "4 separate networks (1 unclassified, 2 classified)." Please confirm the correct count and the classification of each.
It will be UNCLASS and Class
15. Does the delivered system require its own RMF authorization? Please confirm whether the contractor-furnished AV network must be physically separate from USCG production networks.
It is meant to display CG networks
16. Please provide the output interface and classification level for each of the 16 primary sources.
At minimum the 16 are 8 NIPR and 8SIPR
Physical and dimensional
17. SOW Section 2 specifies a video wall 29 ft wide and auxiliary screens 30 ft wide, in a room measuring 24 by 29 ft. Please provide correct dimensions, quantity, and mounting wall for each.
The CCDS will be on a wall that is 27FT long by 8ft high and the aux screens will be on the 30X8ft wall.
18. SOW Section 2 cites a 12 ft structural ceiling, 3 ft drop ceiling, and 1 ft raised floor. Please confirm finished clear height, required bottom-of-screen elevation, and service clearance.
From floor to ceiling its 8ft
19. SOW Section 2 requires front and rear serviceability with framing tied to the structural wall. Is a rear service corridor available? If not, is front-service-only acceptable?
Front is acceptable
20. SOW Section 2 lists floor loading as unknown and excludes structural modification. Please provide raised floor and slab loading capacity, and confirm responsibility if reinforcement is required.
The floor is rated and good to go
21. Will floor plans or as-builts for the watch floor partition be made available before the quote due date?
They’ve been provided to my knowledge but are available
Performance and acceptance
22. SOW Section 6 sets acceptance at 99.999% uptime and zero dead pixels. Please define the measurement period and verification method, and confirm whether module-level replacement within a stated response time satisfies the criterion.
After CCDS is installed, tested will be conducted alongside CG IT staff and PAC leadership to verify system abilities and picture quality. Pixels should last based on manufacturer guarantee.
23. SOW Section 3 requires a standard warranty package. Please state the required warranty term and support response time.
We will accept phone support for minor issues but for downtime extending past 30 minutes on site assistance is requested. For warranty, we would go off equipment manufacture rating for gear.
24. SOW Section 6 requires 90% of watchstanders and supervisors complete training. Please provide the total number of personnel to be trained.
It would be roughly 30 people.
Schedule and site access
25. SOW Section 2 cites a 30-day downtime tolerance. Is this a continuous outage window, and what working hours are permitted on the watch floor?
The watchfloor would be sectioned off from the District side and normal working hours permitted, 0800 – 1600.
26. Please state the Government review period for the System Design Document, and confirm whether that time is excluded from the 90-day performance period.
90 day starts when awarded, we are looking for work to start beginning of January.
27. Please state the expected lead time for base access and badging for non-local personnel.
Once awarded we can get VAR in from contractor and begin access approvals.
Contractual
28. Please confirm that the Service Contract Act and Wage Determination 2015-5623 apply to all labor under this effort, and that the Davis-Bacon Act does not.
This is not construction and will not need the Davis-Bacon Act.
29. Offers are due 20 September 2026, a Sunday. Please confirm the date and time.
Date and time are listed on the solicitation in SAM.
Source Inventory
30. Please provide an inventory of the sixteen (16) initial sources and anticipated future sources, including source type, signal format, connector type, resolution, and classification level.
8 SIPR and 8 NIPR
31. Network Architecture Under Department of Defense (DoD) and Committee on National Security Systems (CNSS) cybersecurity policies, NIPRNet (Unclassified) and SIPRNet (Secret) AV-over-IP networks and endpoints cannot share unclassified/classified switching infrastructure, controllers, or processors. They must remain completely physically separated (air-gapped).
A stated quantity of one (1) controller/processor cannot be cross-connected to both NIPR and SIPR IP networks simultaneously without violating network separation mandates.
32. Please clarify the required method of separation between the four referenced network classifications.
Under Department of Defense (DoD) and Committee on National Security Systems (CNSS) cybersecurity policies, NIPRNet (Unclassified) and SIPRNet (Secret) AV-over-IP networks and endpoints cannot share unclassified/classified switching infrastructure, controllers, or processors. They must remain completely physically separated (air-gapped).
A stated quantity of one (1) controller/processor cannot be cross-connected to both NIPR and SIPR IP networks simultaneously without violating network separation mandates.
33. Is the Government expecting contractor-furnished switching and segregation hardware, or will portions of the security architecture be Government Furnished Equipment (GFE)?
Contractor furnished Security Requirements
34. Are contractor personnel required to possess any facility clearances, personnel security clearances, escorts, CAC credentials, or other special access authorizations to perform installation, testing, or training?
They will be escorted at all times but should have a clearance Drawings and Existing Conditions
35. Are floor plans, room elevations, equipment room layouts, pathway drawings, photographs, or other facility documentation available for offerors?
Prior to award, only dimensions listed in SOW. After award, drawings and existing conditions can be given.
Display Wall Location
36. Please confirm whether the fabricated wall structure described in the SOW is existing infrastructure or new contractor-furnished infrastructure.
One will is being removed and part of the wall is being constructed to match the depth of the other
37. Please confirm available rear-service access dimensions behind the proposed display wall location.
Behind the ccds is a server room where they contractors will have access to hook up equipment.
Power Infrastructure
38. Please provide available information regarding existing electrical capacity, branch circuits, and power distribution serving the project area.
There are multiple outlets on the wall were the CCDS to go, SOW asks contractors to add more if needed but with it adjoining to server room it shouldn’t be an issue.
Acceptance Testing
39. Can the Government provide additional detail regarding the acceptance test process, success criteria, and any required Government witnessing procedures?
Testing will be done with CG IT personnel, PAC battle watch standers and Leadership. Both NIPR and SIPR will be displayed and each console will be tested to see if they can switch displays.
Past Performance Requirements
40. Are offerors expected to submit project references, CPARS reports, or other past-performance documentation as part of their quotation?
Offerors are not expected to submit CPARS or past performance documents.
Evaluation Criteria
41. The solicitation states award will be made on a best-value basis with price and other factors considered.
Technical Capability & Engineering Design, Price/Cost, and Qualifications.
42. Please identify the evaluation factors and relative importance of technical approach, past performance, and price.
CPARS and past performance will not be used for evaluation.
Post-Award Field Verification
43. If field verification identifies site conditions materially different from those represented in the SOW, will the Government consider equitable adjustments for resulting scope, schedule, or equipment modifications?
Yes Facility / Structural
44. Floor loading capacity is listed as “unknown” in the SOW — can the Government provide the raised floor and structural floor loading capacity (lbs/sq ft) for the video wall mounting wall and equipment rack location?
CG GE has approved flooring, no issues with what it can handle.
45. The room is 24' x 29'. The main video wall is specified at 29' wide x 8' high, and “at minimum two auxiliary screens” at 30' wide x 8' high — larger than the room's longest dimension. Can the Government confirm the intended auxiliary screen dimensions and their wall/location within the room, since as written they do not appear to fit alongside the main wall?
Answered above
46. With a 12' structural ceiling, 3' drop ceiling, and 1' raised floor, the available mounting height appears to be approximately 8' — matching the specified 8' wall height with no clearance for mounting hardware or trim. Can the Government confirm this is workable, or provide as-built reflected ceiling plan/elevation drawings?
Adjustments can be made on contractor input
47. Has the fabricated metal wall framing referenced in the SOW already been structurally engineered/load-rated, or is that analysis part of the Contractor's System Design Document (SDD) scope?
Building will commence in OCT.
48. Are existing structural or as-built drawings (architectural, electrical, mechanical) available for Bldg 51 that can be provided prior to award to support design?
Yes and have been
49. Does the room require classification signage both outside the entry door(s) and inside the room (e.g., at the video wall/workstations), and if so, per what governing standard?
Yes but the CG handles that.
Network, Security & Classification
50. Section 2 of the SOW states “4 separate networks (1 unclassified, 2 classified),” which totals 3, while the Acceptance Criteria reference Unclassified, Secret, and TS/SCI. Can the Government clarify the actual number and classification levels of networks/domains the CCDS must support?
NIPR and SIPR
51. Can the Government identify the specific networks by name that the CCDS must integrate with (e.g., NIPRNet, SIPRNet, JWICS, or other)?
NIPR and SIPR
52. What accreditation or approved-products requirements apply to switching/processing equipment that will handle Secret and TS/SCI visual data (e.g., NSA-approved cross-domain solution, DoDIN APL listing, TEMPEST)?
Tempest compliant and Under Department of Defense (DoD) and Committee on National Security Systems (CNSS) cybersecurity policies, NIPRNet (Unclassified) and SIPRNet (Secret) AV-over-IP networks and endpoints cannot share unclassified/classified switching infrastructure, controllers, or processors. They must remain completely physically separated (air-gapped).
A stated quantity of one (1) controller/processor cannot be cross-connected to both NIPR and SIPR IP networks simultaneously without violating network separation mandates.
53. Is there an existing Authority to Operate (ATO) or Risk Management Framework (RMF) package this system must be integrated into, or will the Contractor need to support a new ATO/RMF accreditation effort?
Already exists.
54. Bandwidth availability between the room and network closets is listed as “unknown.” Can the Government provide available bandwidth/uplink capacity for the AV-over-IP system?
Not at this time.
55. Is the space itself an accredited SCIF or similarly controlled space with RF/TEMPEST shielding requirements that would affect equipment selection or installation methods?
Can’t have WIFI or anything like that, requirement was listed in SOW.
Personnel & Access
56. What personnel security clearance level is required for Contractor installation/engineering staff to access the Battle Watch floor and adjacent network closets, given classified data present in the space?
Answered above
57. What is the process and lead time for badging/access credentials at Coast Guard Island, Bldg 51?
Once awarded company can send VAR and we can start access approvals.
58. Is a site visit being offered before the question deadline, and if so, how should it be scheduled given the short window?
Yes and has been .
Government-Furnished vs. Contractor Responsibility
59. Will the Government be responsible for providing power (circuits/drops) to the video wall and equipment rack, or is that within the Contractor's scope?
If more outlets are needed the contractor will add.
60. Will the Government be responsible for the video wall support structure (wall backing/framing to receive the mount), or is fabrication/installation of that structure Contractor-furnished?
CG is leveling out wall, if more support is required it’s on the contractor.
61. Will the Government be responsible for data cable pathways (conduit, cable tray, core drills through the dividing wall to the network closets), or is that Contractor-furnished?
Contractor Furnished.
Video Wall, Processing & Control
62. MEI understands the Government's intent is for a Direct View LED (dvLED) video wall. Does the Government have a preferred manufacturer for the dvLED video wall, or is manufacturer discretion acceptable provided the equipment meets TAA compliance and the specifications stated in the SOW?
As long as it meets TAA we are good.
63. Using the standard LED viewing-distance guideline of approximately 1 meter (3.28 ft) of minimum viewing distance per 1mm of pixel pitch, the SOW's stated 8-foot near viewing distance calculates to approximately a 2.5mm pixel pitch as the coarsest acceptable resolution. However, given the likely requirement to display VTC/SVTC participant video and GIS/map-based graphical content — which demand finer detail and text legibility at close range — MEI recommends specifying a finer 1.8mm or 1.5mm pixel pitch. Does the Government concur with pixel pitch in this range, or have a preference/objection?
Yes we concur and are ok with changing based on contractor input.
64. Is the intent for a single front-wall video wall configuration only, or a main front video wall with two additional auxiliary video walls mounted on the side walls of the room?
1 wall to have the main CCDS and the side wall to have the aux screens.
65. Is redundant/UPS power required for the video wall processor, controller, and switching equipment to support the 99.999% uptime requirement, given the SOW states no additional power redundancy is required beyond the building generator?
Correct.
66. Are the two touch panels fixed at specific desk locations, wall-mounted, or wireless/roaming? Is a backup/redundant control processor required?
Not required and one touch panel should be on the floor and one can be in the server room.
67. What are the required hardware replacement timelines under the warranty (e.g., 4-hour, next-business-day) referenced in the Warranty & Sustainment deliverable?
4hours.
VTC/SVTC & Source Integration
68. What platform/devices will be used to host VTC/SVTC calls (e.g., Microsoft Teams, a dedicated hardware codec, or other)? Is this Government-furnished or part of the Contractor's scope?
System will not do SVTC or VTC.
69. If VTC/SVTC is required, what camera type is expected (PTZ, fixed, auto-tracking)? What microphone type (ceiling array, desktop/boundary, gooseneck)? What speaker type (ceiling, wall-mounted, soundbar)? Is a DSP required for audio processing, echo cancellation, and mixing?
Not needed.
70. For the 16 (+8 future) sources overall, what are the connector/signal types per source category (HDMI, DisplayPort, SDI, fiber) and approximate cable run distances from source to rack?
HDMI and run length is through the wall to the server and from each desk to connectors 20ft or less.
71. Is fiber backbone already in place between the Battle Watch room and the adjacent network closets, or does the Contractor need to establish new pathway/conduit through the dividing wall?
In place.
72. What is the delivery schedule for the GFE end-user workstation PCs relative to the 90-day install/integration timeline?
Computers are going in OCT/NOV and work for CCDS is expected to start January.
73. For “PC audio routing is requested” — is this a firm requirement, and what is the desired audio architecture (room reinforcement only, or per-operator)?
Just basic speakers but no bluetooth or wifi
74. Where is the equipment rack intended to be located — within the Battle Watch room itself, or in the adjacent network closet space?
Network closet space.
Schedule & Operations
75. What is the anticipated contract award / notice-to-proceed date, since the 90-day timeline runs from the Effective Date?
Once awarded, the timeline will be created with the chosen vendor.
76. Given 24/7 continuous staffing and only a 30-day downtime tolerance within the 90-day period, can the Government confirm whether the room will be fully vacated for a contiguous 30-day window, or whether phased/partial cutover is expected while operations continue?
Accomodations can be made.
77. Are there work-hour restrictions (e.g., no work during active watch shifts) that would affect the installation schedule?
Duty hours are between 7 am and 5 pm.
Compliance & Contract Administration
78. The Wage Determination attachment suggests Service Contract Act (SCA) labor categories apply — can the Government confirm SCA applicability and the correct labor category/wage determination for AV installation technicians?
Wage Determinations must be submitted with the solicitation. Please utilize the link provided below: https://www.google.com/goto?url=CAESZgHrOzAV4PItcdwfchphYz54fEOnr5c6keU1uimYXH3xVcc75yj11eOGRk6NiFIjV736oml6dX9EKpKiVTLhPo2UvD0t20eUCicrGIvnCE4t_WNeegtCpC2zyucczisM73B6Wb5yPA
Contract line items and pricing structure
79. We did not identify a contract line item number (CLIN) schedule in the SOW. Will the Government issue a CLIN schedule or prescribed pricing format, or should offerors submit pricing without a Government-provided CLIN structure?
CLIN structure can be listed in your quote and may be used for award.
Primary video wall dimensions and viewing area
80. The SOW specifies a video wall 29 feet wide by 8 feet high, but the room’s floor-to-ceiling height is also 8 feet. This would require the video wall to extend from the floor to the ceiling, leaving its lower portion obstructed by desks and cubicle partitions and preventing seated watch standers from viewing the entire display. Please confirm whether an 8-foot-high video wall is required, or whether a shorter video wall mounted above these obstructions is acceptable.
Any changes to fit the space are acceptable, we put the max we could theoretically do in there but today we had a vendor come through and they’d need to go smaller which is fine.
Auxiliary display dimensions
81. The SOW calls for at least two auxiliary screens and lists dimensions of 30 feet wide by 8 feet high, which would discribe actually a 3 video wall requirement. Our site surveyor understood from watch floor staff that conventional flat-panel displays would meet this need. Please confirm the required quantity and size of the auxiliary displays (if this is indeed what is desired), and whether the dimensions in the SOW should be revised.
The two aux screens would go on the side wall of the room, something about 55in would suffice, just 2 of them.
Simultaneous sources on the video wall
82. The Video Wall Processors requirement specifies the simultaneous display of at least 10 sources. Please confirm whether 10 is the minimum number of sources that must be visible on the primary video wall at one time, regardless of the total number of connected inputs.
Not all 10 would need to be up at once, just have the ability to feed 10 sources to be put up when the watch needs.
Networks and classification levels
83. During site visit, only two networks were discussed (NIPR and SIPR) The Network & Security paragraph of the SOW refers to four separate networks but identifies one unclassified and two classified networks, which totals three. The acceptance criteria also refer to Unclassified, Secret, and TS/SCI visual panels. Please confirm the number of networks and classification levels the system must support, including whether the requirement is limited to NIPR and SIPR or includes additional networks or TS/SCI sources.
Only 2 sources, NIPR and SIPR. We weren’t sure when we did the SOW if we’d be adding a higher level but we are not.
Initial inputs and expansion capacity
84. The SOW requires 16 primary sources with capacity for eight additional sources. Our site surveyor understood that the watch floor requires eight SIPR and eight NIPR inputs, totaling 16 initial sources. Please confirm whether the required baseline is 16 installed inputs, expandable to 24, and identify the required allocation by network. Please also clarify whether the additional eight inputs must be fully equipped at delivery or supported as future expansion capacity.
Expandable to 24 and it would be split evenly between NIPR/SIPR.
Simultaneous display of different classifications
85. Will NIPR and SIPR sources be displayed on the video wall simultaneously?
Yes they should be able to display at the same time but not bleed over to each other.
Front and rear service access
86. The SOW and hardware deliverables require both front and rear service access. Would a fully front-serviceable video wall satisfy the maintenance requirement, or is rear access mandatory? If rear access is mandatory, please clarify the required service clearance.
Front service would be fine Power drops
87. The SOW calls for approximately 12 adjustable power drops along the wall and floor. Are these intended solely for the video wall, or must they also serve auxiliary displays, workstations, or other equipment? May offerors propose a different quantity and arrangement based on the selected video wall's power requirements, including a design using remote power supplies? (Offboard power which would require no AC outlets to be installed to power the wall).
Yes, if they think something different would work we are good with them making suggestions and going that route if it makes sense and the IT/ Security teams have no issues.
Separate AV-over-IP systems and controllers
88. The hardware deliverables list one centralized AV-over-IP controller/processor, while the security requirements call for separation of classified and unclassified sources. Please confirm whether NIPR and SIPR must use completely separate, air-gapped AV-over-IP systems, including separate controllers/processors and switching equipment, or whether another Government-approved architecture is intended. Please reconcile the required architecture with the stated quantity of one controller/processor.
Under Department of Defense (DoD) and Committee on National Security Systems (CNSS) cybersecurity policies, NIPRNet (Unclassified) and SIPRNet (Secret) AV-over-IP networks and endpoints cannot share unclassified/classified switching infrastructure, controllers, or processors. They must remain completely physically separated (air-gapped) Equipment rack
89. The SOW requires a dedicated equipment rack. Our site surveyor reported that existing rack space is available in the server room. May the contractor use that space, subject to verification of capacity, access, power, cooling, and security requirements, or must a new dedicated rack be furnished?
Yes, they can use the available rack space as it’s been made available for this project.
Warranty and support
90. The Warranty & Sustainment Package calls for 24/7 technical support and hardware replacement timelines. Please define whether telephone support alone is sufficient or onsite service is also required; the required response, onsite arrival, and hardware replacement times; and the duration of the support obligation, such as one year or two years. The SOW prohibits remote access, so please also confirm that troubleshooting support must be provided by telephone and, when necessary, onsite.
We would want both telephone and onsite.
91. SOW 2 specifies auxiliary screens "30 feet wide by 8 feet high." What dimensions and quantity should be priced alongside the 29-by-8-foot wall?
For the aux screen about 55”
92. SOW 2 permits "LED or LCD"; SOW 3 specifies "4K LED." Which governs the main wall?
Whatever the company thinks will work the best for the space, the company today thourhg LED would be better
93. SOW 2 lists "4 separate networks (1 unclassified, 2 classified)." What is the fourth network's classification?
Its only NIPR and SIPR, SOW left room incase the CC added JWICS but they aren’t
94. For SOW 6's "physical and logical visual isolation," what approved switching/sanitization standard and controller-sharing constraints govern the design?
That would have to come from CG Cyber which will take me some time
95. For SOW 4's "site access credentials," what personnel/facility clearances and DD-254 requirements apply, and who handles classified configuration?
CSO will have to get back to me but they will have escorted access the whole time, closed off from the active command center side.
96. SOW 2 calls floor loading and bandwidth "unknown." What structural, electrical, and network capacity information will be available for pricing?
In the sow it talks about them putting in power spot if necessary, the companies today didn’t think that would be and the flooring can handle whatever is put on it.
97. For SOW 6's "99.999%" and "without visual latency," what measurement periods, exclusions and test thresholds establish acceptance?
Whatever the manufacturer guarantee on the product works (for the screens)
98. For SOW 3's "Warranty & Sustainment Package," what support duration and replacement deadlines should be priced, given the remote-access prohibition?
Baseline we just need onsite support if the system goes down, I can ask the command if theres an acceptable period phone troubleshooting before help must arrive
99. For SOW 2's "90-day timeline and 30-day downtime tolerance," how are Government approval/access delays and cumulative downtime counted?
I believe that will be based on when work start in the space, once they start it’ll need to be completed but that will have to go above me as well.
100. The notice "incorporates provisions and clauses by reference." Please provide the applicable clause list, including the subcontracting limitation treatment for this mixed hardware/services order.
FAR 52.203-6, FAR 52.203-6ALT, FAR 52.232-40
File details come from the government source that posted it. Updated .