Added: Sep 07, 2008 11:42 am
This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.
The contractor shall provide personnel, equipment, tools, materials, supervision, transportation and other items and services necessary to provide and install an Emergency Alert Crash/Ring down system for the Arizona Air National Guard Base, 162nd Fighter Wing, 1500 E Valencia Rd, Tucson, Arizona, 85706, in accordance with the following statement of work:
The 162nd Fighter Wing (162FW) is in need of an updated crash/ring down system that meets the current Air Force Instruction (AFI) requirements and provides dependable operation with minimal maintenance actions.
Please note that the governing directives in attachment 1, AFI 13-213, paragraph 3.2.2.3.3. Airfield Management Operations and ANG Supplement 13-213 list the requirements for the secondary crash network (SCN).
The Secondary Crash Alarm System (SCAS) is initiated at our Command Post located in building 44, room 148. It must be initiated by the controller picking up a telephone handset. We also require a second initiation point at the Bell Room located in building 50, room 1. The Governing Directive Requirements, listed below, requires there to be some sort of visual display that shows what extensions are answered/unanswered. Although all extensions may not be installed at the users location, contractors are to plan for at least 16 available outputs/extensions. These will be available at a 66 type telephone block on the telecommunications frame in the Master Distribution Frame (MDF) room, building 1, room 126.
All systems are located on the 162FW and there is copper available to those facilities and the MDF as well. Distances will be less than one mile to all on base locations. Existing base infrastructure can be utilized if coordinated in advance. A minimal amount of rack space is currently available and must be coordinated in advance. All advance coordination is done through the 162FW Contracting Office with the 162FW Communications Flight Operations Branch Chief. All patch cords, fiber or copper as well as interconnect cabling if necessary will be contractor furnished. The SCN is a redundant system; it must operate independent of our Voice Server (Telephone Switch).
Contractor must furnish all equipment including telephone instrument for the main initiating location, 20 extensions, and four beacons. Each instrument must have a visual indication when ringing and Push to Talk (PTT) capability with no speaker phone option.
Warranties must cover all equipment, and operating systems for a minimum of one year. This must include onsite if necessary. Training for 162FW technicians to include limited maintenance actions must be included in initial pricing as well as possible service contract pricing after the initial year of warranty service. Complete testing documentation, as built drawings and schematics of all equipment will be required after installation.
Suppliers/Contractors of these systems must be experienced and knowledgeable of these types of systems before bidding. Complete system specifications, operating systems and parameters will be required with bids. Thank you in advance for your interest in serving our needs.
Governing Directive Requirements:
AFI 13-213, Airfield Management Operations, dated 29 January 2008; ANG Supp 13-213; and inspection items are the governing directives. Paragraph 3.2.2.3 from AFI 13-213 and paragraph 3.2.2.3 from ANG Supp 13-213 are shown below.
Secondary Crash Requirements:
3.2.2.3. Secondary Crash Net (SCN). AMOPS section must have SCN activation capability with an additional extension to provide immediate access by other personnel on-duty, monitoring and training purposes.
3.2.2.3.1. All agencies on the SCN will be on lines dedicated to the dissemination of emergency information that affects airfield or aircraft operations.
3.2.2.3.2. The SCN may be a separate telephone or integrated into a multi-line call center.
3.2.2.3.3. The telephone must be equipped with a visual feature that activates as each two-way party on the SCN picks up the handset.
3.2.2.3.4. All agencies on the SCN must use a noise reduction feature such as push-to-talk handsets or Confidencor (Trademark of National Communications Inc.) that filters out background noise.
3.2.2.3.5. The SCN is limited to agencies requiring emergency action/response to aircraft incidents/mishaps. As a minimum, the SCN agencies include:
3.2.2.3.5.1. Fire Department.
3.2.2.3.5.2. Weather.
3.2.2.3.5.3. CE Readiness.
3.2.2.3.5.4. Hospital/Medical Treatment Facility.
3.2.2.3.5.5. Command Post.
3.2.2.3.5.6. Civil Engineering.
3.2.2.3.5.7. Security Forces.
3.2.2.3.6. Requests for additions/deletions (excluding those listed in paragraph 3.2.2.3.5.) to SCN must be coordinated through the AFM and forwarded to the OSS/CC for approval/disapproval.
3.2.2.3.6.1. Determine talk back or listen only capability for approved additions as warranted in justification.
3.2.2.3.6.2. The total number allowed on the SCN must not exceed the capacity of the system or minimize signal strength and quality.
3.2.2.3.7. Test the SCN daily and backup procedures at least quarterly. Document test results on the AF IMT 3616.
3.2.2.3.8. Unless testing, only activate the SCN to relay emergency situations that are critical to the safety and security of airfield/flight operations. Emergency situations requiring activation of the SCN are as follows:
3.2.2.3.8.1. Hazardous weather warnings.
3.2.2.3.8.2. IFEs.
3.2.2.3.8.3. GEs.
3.2.2.3.8.4. Force Protection Condition (FPCON) levels.
3.2.2.3.8.5. Disaster Response Force (DRF) activations/recalls.
3.2.2.3.8.6. Bomb threats or terrorist activities.
3.2.2.3.8.7. As requested by the EOC Director to support Comprehensive Emergency
Management Plan (CEMP) outlined in AFI 10-2501. The installation CEMP 10-2 provides comprehensive guidance for emergency response to physical threats resulting from major accidents, natural disasters, conventional attacks, terrorist attack, and CBRN attacks.
3.2.2.3.9. AMOPS section is the primary activation authority of the SCN.
3.2.2.3.9.1. When mission requirements dictate, an additional SCN may be installed/activated by another agency provided a LOA exists between AM and the other agency.
3.2.2.3.9.2. Operating procedures will be clear, concise on whom the activation authority is, and when the SCN is used.
3.2.2.3.9.3. Regardless of activation authority, the SCN will be operated and maintained in accordance with this AFI.
ANG SUPP 13-213, AIRFIELD MANAGEMENT
3.2.2.3. (Added) A second extension of SCN is not required for shared use locations.
3.2.2.3.1. (Added) New or replacement SCN systems will have all features described in this paragraph.
3.2.2.3.3. (Added) The OG/CC is approval authority for additions/deletions to the SCN.
INSPECTION ITEMS:
AM 070. Is the SCN tested daily and are SCN backup systems/procedures tested quarterly and results documented on the AF Form 3616? (AFI 13-213, 3.2.2.3.4)
AM 071. Are all stations on the SCN on lines dedicated to the dissemination of emergency information, have a visual feature showing parties availability, and equipped with a noise reduction feature? (AFI 13-213, 3.2.2.3.1)
AM 072. Is the SCN limited to agencies requiring emergency action/response to aircraft incidents/mishaps and used only to relay information critical to aircraft and airfield operations? (AFI 13-213, 3.2.2.3.2, 3.2.2.3.5)
AM 078. Does AMOPs possess a dual extension of the Primary Crash Alarm System (PCAS)? (AFI 13 -213, 3.2.2.2)
AM 079. Does AMOPs possess SCN activation capability with an additional extension for monitoring and training purposes? (AFI 13-213, 3.2.2.3)
AM-014-ANG. Is the primary crash alarm system and secondary crash net installed, operational and tested daily? (AFI 13-213 3.2.2.2, 2.3.2.4 and AFI 13-203, 5.5)
Contact TSgt Hollie A Hansen at hollie.hansen@aztucs.ang.af.mil for packages and for any questions. Questions must be submitted no later than 17 September 2008.
