OSA SCN - QA Clarifications - 17 Sep 26.pdf
PDF 8 MB Posted
- Attached to
- 48 OG - OSA Secondary Crash Network
- Solicitation number
- FA558726Q0047
About this file
This is a Questions and Answers memorandum issued by the 48th Contracting Squadron of the Department of the Air Force regarding contract opportunity FA558726Q0047 for an OSA Secondary Crash Network upgrade at RAF Lakenheath.
The government seeks to upgrade the existing Forum Communications Alert 3 Secondary Crash Network (SCN) system to support 48 ports/telephone stations serving 18 emergency response base agencies plus potentially additional agencies provided by 48 OSS. The new system will leverage existing phones and wiring where feasible for like-for-like replacements, integrate with existing infrastructure as a standalone system, and support both SIP and analog devices. All equipment must be new and not refurbished. Key requirements include escorted site access with restricted area coordination, UPS backup power replacement, site survey prior to installation, and normal duty hours operation (0800-1600L) with weekend/after-hours work requiring coordination. The vendor must supply networking equipment including switches, routers, and cabling with detailed specifications to be provided. The system will not connect to DSN or require JITC certification/DoDIN APL compliance. Contractor personnel require security clearance compliance per federal and local procedures. Training must include 12 Airfield Management personnel and 2 Communications personnel for operator training, with 2 Communications staff requiring maintenance/troubleshooting training. Training materials are required in both printed and digital formats and must be delivered on-site. The government requires 12 months of remote technical support during normal duty hours (0800-1600L) covering both software updates and hardware replacement, plus on-site support for critical failures. A maintenance contract is required beyond the initial 12-month support period. Visual activation features, noise reduction via push-to-talk phones, and recording capabilities specifications were referenced with supporting photos. All questions and clarifications will be posted on SAM.gov for all interested parties, with government providing an addendum to address remaining items including OSS point of contact information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 26Q0047 - OSA Secondary Crash Network - QA - 09Sep26.pdf | ||
| SOW SCN 30 Jul.pdf | ||
| Solicitation - FA558726Q0047- SAM.gov.pdf | ||
| Quote Sheet.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
DEPARTMENT OF THE AIR FORCE
48TH CONTRACTING SQUADRON
11 September 2026
MEMORANDUM FOR RECORD
FROM: 48 CONS/PKA
SUBJECT: FA558726Q0047 – OSA Secondary Crash Network - Vendor Questions
1. What are you using currently for your Secondary Crash Network (SCN)?
A: Forum Communications Alert 3.
2. The RFP references 18 emergency response agencies, but also wants 30 ports, are the extra 12 ports for future expansion, or are we connecting to other miscellaneous endpoints?
A: We currently have 48 ports/ requesting 48 ports.
3. If there are other miscellaneous endpoints, can you please explain what they are and how many of each. For example, how many sirens, strobes, speakers, etc…
A: No all are connect to a phone.
4. Will this SCN be tied into existing infrastructure or be completely stand alone?
A: Tied into existing infrastructure>
5. Will we be leveraging existing phones, or will vendor need to provide them?
A: Existing Phone
6. Is this solution to be fully SIP or will it include analog devices?
A: Analog devices.
7. Will this system be connected to the DSN in any way?
A: No.
8. Is JITC Certification and being on DoDIN APL a requirement?
Contracting Question?
9. Is all wiring in place for the endpoints?
A: Yes, if the new system is a like for like.
10. Will the vendor be required to supply all networking equipment such as switches, routers, cabling? If yes, can you provide detail of what will be needed?
Photo Included
11. Can you provide a diagram of existing or proposed SCN?
Photo Included
12. Will these questions be visible to all participating vendors?
a. All questions and requested clarifications will be posted to SAM.gov for all interested parties to view.
13. Do you suggest a site survey prior to installation to uncover any unexpected wiring needs, etc…?
A: Yes
14. In the attachment, you recommend reaching out to OSS, do you have a point of contact for us to reach out to?
a. The government will clarify these responses and post an addendum to the Q&A on
SAM.gov
DEPARTMENT OF THE AIR FORCE
48TH CONTRACTING SQUADRON
15 September 2026
MEMORANDUM FOR RECORD
FROM: 48 CONS/PKA
SUBJECT: FA558726Q0047 – OSA Secondary Crash Network – Site Survey Questions
System Architecture & Integration
1. What existing SCN infrastructure is currently in place at RAF Lakenheath? (SOW: “Upgrade RAF
Lakenheath SCN mentions an upgrade? A: Forum Communications Alert 3
2. Is the upgrade expected to reuse any existing cabling, racks, or telephony hardware, or must everything be replaced? (SOW: “All equipment… shall be new and not refurbished.”) A: Yes
3. What telephony environment is used on base (VoIP, analog, SIP trunking, PBX type)?
A: PBX Forum Communications Alert 3
4. Are there existing conference bridges or recording systems that must integrate with the new SCN?
A: No
5. Is there a secondary route required for contingency and to stop any potential single point failures?
A: No
6. Will this be classed as a Black or Red route?
A: Stand Alone System
7. Are there any fibre network drawings showing what fibres currently go between each of buildings including the main pipes into the site.
Photo Included
8. Are the any Technical/design drawings of existing equipment on the other 18 emergency response areas?
Photo Included
Port & Station Requirements
9. Confirmation on the exact number of telephone stations required? (SOW: “The designated number of telephone stations shall be installed…”) Photo Included
10. How Many ports SOW says 30, Solicitation says 50 A: 48 Ports as what we currently have.
11. Do any agencies require multiple stations or redundancy?
A: 1 station needs two phones/ Airfield Management
Agency Connectivity
12. Provide the full list of the 18 emergency response agencies? (SOW: “Number of Supported Users: 18 emergency response base agencies”) Photo Included
13. Are any additional agencies expected beyond the 18 listed? (SOW: “…and additional agencies provided by 48 OSS.”)
A: Yes potentially.
14. Are connection points already established for each agency, or must new lines be run?
A: All have line
Functional Requirements
15. Multi-line call capabilities: What is the expected maximum number of concurrent calls per station?
A: Yes. 1 Station Airfield Management to imitate calls and have the ability to select which stations to call.
16. Visual activation feature: What specific visual indicator is required? LED? Screen pop? (SOW:
“Visual feature which is activated when each two-way party picks up Tracking Takeoff Data”)
Photo Included
17. Noise reduction: Is this acoustic noise reduction, line noise suppression, or both?
A: push to talk phones
18. Recording capabilities:
Photo Included
19. What retention period is required?
A:
20. Where will recordings be stored (on-prem, secure server, external storage)?
Photo Included
21. Is encryption required?
A: No
Installation & Engineering Clarifications
Site Access & Security
22. What security clearances are required for contractor personnel? (SOW: “The contractor shall remain in compliance with all Federal and local security procedures…”)
23. Are escort requirements expected?
A: Yes
24. Are there restricted areas requiring special coordination?
A: Yes, escorted access will be given
25. Are there any specific site inductions required and are these weekly, monthly etc?
A: No
Physical Installation Requirements
26. Are there existing equipment rooms or must new racks/enclosures be provided?
A: No
27. Is power conditioning or UPS backup required?
A: Yes UPS Replacement
28. Are there environmental constraints (noise, temperature, EMI)?
A: No
Work Schedule
29. What are the base’s normal duty hours? (SOW: “Any work outside of normal duty hours shall be coordinated…”) A: 0800-1600L
30. Is weekend or after-hours work permitted if required?
A: Requires Coordination
31. Is there a mandated installation completion deadline?
A: No
Training Requirements
Training Scope
32. How many personnel require operator training?
A: 12 Airfield Management. 2 Comm
33. How many require maintenance/troubleshooting training? (SOW: “This shall include operator training as well as maintenance and troubleshooting.”) A: 2 Comm
34. Is training expected to be on-site only, or must remote/virtual training be included?
A: on site
35. Are training materials required in printed form, digital form, or both?
A: Both
36. What specific qualifications, if any, are needed for the instructors?
A: None
Support & Warranty Clarifications
Remote Support Requirements
37. What is the expected response time for remote support? (SOW: “TECHNICAL SUPPORT: 12 months of remote support”) Photo Included
38. Does remote support include software updates, hardware replacement, or both?
A: Both
39. Is 24/7 support required or only during base duty hours?
A: Normal Duty Hours 0800-1600L
Warranty Expectations
40. Is a minimum warranty period required beyond the 12 months of support?
A: No/ Required Maintenance Contract
41. Does the customer require on-site support for critical failures?
A: Yes
| ADP5BAE.tmp |
| DEPARTMENT OF THE AIR FORCE |
| MEMORANDUM FOR RECORD FROM: 48 CONS/PKA |
| ADPCAC1.tmp |
| DEPARTMENT OF THE AIR FORCE |
| MEMORANDUM FOR RECORD FROM: 48 CONS/PKA |
| System Architecture & Integration |
| Port & Station Requirements |
| Agency Connectivity |
| Functional Requirements |
| Installation & Engineering Clarifications |
| Site Access & Security |
| Physical Installation Requirements |
| Work Schedule |
| Training Requirements |
| Training Scope |
| Support & Warranty Clarifications |
| Remote Support Requirements |
| Warranty Expectations |
File details come from the government source that posted it. Updated .