PD_Helicopter_Simulator_09_April_19.docx

Purchase Description Helicopter Defense Systems Simulator

CSN: L9TS11

09 April 2019

1.0 DESCRIPTION

The 402d SMXG has a strong desire to improve the quality of software available to war fighters with the purchase of a state of the art simulator that shall be known as the Helicopter Defensive Systems Simulator (HDSS). This acquisition is to purchase one (1) each Helicopter Defensive Systems Simulator (HDSS) for the 402d Software Maintenance Group (SMXG), Robins AFB, GA. The HDSS shall interface to the classified simulator network (SIMNET) in the 402d SMXG electronic warfare avionics integration support facility (EWAISF). The HDSS shall not interfere or inhibit (in any way) the usage of other simulators or assets connected to the SIMNET/EWAISF network.

The Contractor will provide the simulator, travel, shipping costs, services for installation and testing, and requested data. The 402 SMXG is an organic support and software solutions provider for embedded Operational Flight Programs (OFPs), Mission Data Support Tools (MDST) and Validation and Verification (V&V) services for the Air Force.

2.0 REQUIREMENTS

2.1. Cybersecurity

The Contractor shall implement a Risk Management Framework (RMF) IAW DoDI 8510.01 for the HDSS.

2.2. Information Assurance

Computers required for operations and maintenance of the HDSS shall be operational with the Windows 10 or a Linux distribution commensurate with current Air Force Information Assurance protocols.

2.2.1. All computers and information technology (IT) assets shall allow government personnel to access, apply patches and provide threat vulnerability assessments, documented through appropriate maintenance manuals deliverable to the government.

2.2.2. All computers provided by the Contractor shall be paired with at least two monitors per computer. Each monitor shall be no smaller than 24 inches.

2.3. HDSS Hosting and Software Compatibility

HDSS shall interface to the SIMNET/EWAISF classified computer network through Ethernet. The HDSS shall not interfere or inhibit (in any way) the usage of other simulators or assets connected to the SIMNET/EWAISF network.

2.3.1. The HDSS must be able to read and write threat files and write reports to network locations.

2.3.2. The HDSS must be able to communicate to systems under test (SUTs) via Ethernet and 1553 with a reconfigurable format documented in the product interfaces.

2.3.3. The HDSS shall receive IRIG-B formatted time for Ethernet and discrete sources.

2.3.4. The control subsystem of HDSS shall provide for remote control of and generation of test scenarios over Ethernet. The contractor shall provide interface software to facilitate remote programming and execution.

2.3.5. The remote control protocol and messages of HDSS shall be documented in delivered interface documents.

2.4. HDSS RF Simulation Specifications

The Contractor shall build and deliver a state of the art simulator based on the following requirements:

2.4.1. The HDSS shall be required to meet the minimum threat density described below simultaneously:

2.4.1.1. C/D band, 100,000 PPS with no fewer than 7 pulsed threats, 1 Continuous Wave (CW) threat.

2.4.1.2. E/J band, 1,500,000 PPS with no fewer than 10 pulsed threats, 1 CW threat.

2.4.1.3. K band, 250,000 PPS, with no fewer than 7 pulsed threats, 1 CW threat.

2.4.2. The HDSS shall have no fewer than 20 ports for SUT availability with reconfigurable polarizations of at least horizontal, vertical, left-hand and right-hand at for each connection.

2.4.3. The HDSS shall support frequency range outputs between 50Mhz and 40GHz for any polarization.

2.4.4. The HDSS shall allow a user to reconfigure ports for frequency ranges and polarization types.

2.4.5. The HDSS shall provide the following user selection and threat injection capabilities:

2.4.5.1. The HDSS shall be able to output pulsed and CW signals simultaneously within the frequency coverage envelope specified.

2.4.5.2. The HDSS shall output Pulse Widths between 60 nanoseconds – 130 milliseconds.

2.4.5.3. Each port shall provide interpulse modulation generation capability such as fixed shift keying (FSK), Frequency Modulated Continuous Wave (FMCW) linear and non-linear chirp, discrete Amplitude Modulation On Pulse (MOP), and Frequency MOP for any threat in the frequency coverage envelope.

2.4.5.4. The HDSS shall output Pulse Repetition Interval (PRI) modulations between 1 microsecond – 500,000 microseconds.

2.4.5.4.1. PRI modes for user selection shall include stable, jitter, stagger, switching, periodic, pulse bursts, Synchronized and manual.

2.4.5.5. The HDSS shall output the following scan modulations:

2.4.5.5.1. Steady

2.4.5.5.2. Conical

2.4.5.5.3. Sector

2.4.5.5.4. Circular

2.4.5.5.5. Nodding Circular

2.4.5.5.6. Raster, Palmer

2.4.5.5.7. Helical

2.4.5.5.8. Spiral

2.4.5.5.9. Track While Scan

2.4.5.5.10. Multibeam

2.4.5.5.11. Electronic Scan

2.4.5.5.12. Lobe Switching

2.4.5.5.13. Lobe on Receive Only (LORO)

2.4.5.5.14. Orthogonal

2.4.5.5.15. Synchronized and Random

2.4.5.6. The HDSS shall allow programming techniques to utilize Frequency, PRI, Pulse Width and Transmit Scan modulations to model and simulate the following types of complex signals:

2.4.5.6.1. Guidance Signals – Sequence of Frames of Constant Length Containing Pulse Groups In Fixed and Variable Positions

2.4.5.6.2. Pulse Code Modulation (PCM) – Sequences of Frames of Constant Lengths Containing Pulse Groups In Fixed Positions

2.4.5.6.3. Burst Signals – Sequence of Frames of Constant Length Containing Bursts of Regular Radar Signals

2.4.5.6.4. On/Off Keying – 0 to 10 s on/off times with 1 µs resolution

2.4.5.6.5. Keyed CW With Modulation – AM and FM modulations

2.4.5.7. Each port share support Radio Frequency (RF) agile threats with a switch speed of less than 1 microseconds.

2.4.5.8. The HDSS shall implement surface effects such as multipath, terrain masking, and at least 3 levels of atmospheric attenuation (notional fog, rain, heavy rain).

2.4.6. The HDSS shall have no external combiners, splitters, mixers or RF plumbing with the exception of RF cables and impedance matching devices (if required).

2.4.7. All required mechanisms shall reside inside the HDSS (behind panels or lockable drawers/doors).

2.4.8. The HDSS shall include all control computers and hardware interfaces required to manage/run/operate the simulator.

2.4.9. Included Maintenance and Support Equipment:

2.4.9.1. The HDSS shall include RF cables for each RF port capable of supporting calibration and SUTs.

2.4.9.2. No RF interfaces shall be in the top or bottom of the HDSS.

2.4.9.3. The HDSS shall include industry standard RF port interfaces (notional – Threaded N-Connector, TK, SMA, SSMA, etc.).

2.4.9.4. The HDSS shall include casters on each rack for mobility.

2.4.9.5. The HDSS shall be configured to not exceed 150 pounds per square foot floor loading when fully assembled.

2.4.10. The HDSS shall provide 2-D, 360 coverage allowing full Angle Of Arrival (AOA) injection of threats of all bands at all frequencies.

2.4.11. Platform Motion Characteristics shall include (SUTs and other programmable emitters):

2.4.11.1. Flat Earth (SUT) – X, Y, Altitude, Roll, Pitch, and Yaw

2.4.11.2. Round Earth (SUT) – Latitude, Longitude, Altitude, Roll, Pitch, and Yaw

2.4.11.3. Flat Earth (Emitters) – X, Y, Altitude, Roll, Pitch, and Yaw

2.4.11.4. Round Earth (Emitters) – Latitude, Longitude, Altitude, Roll, Pitch, and Yaw

2.4.11.5. Maximum Platform speeds – 7500 km/hr

2.4.12. The HDSS shall provide a mechanism that can plan and execute static and dynamic scenarios based on user inputs in a graphical environment that includes a map.

2.4.13. The HDSS shall be capable of importing DTED data and creation manual terrain maps.

2.4.14. The HDSS shall have an engagement time (duration of testing) no less than 66 hours to facilitate extended multi-day testing events.

2.5. HDSS Dimensions and Power Requirements

The HDSS should provide a minimum footprint utilizing height as an advantage to accommodate existing lab and facility infrastructure. The dimension specifications shall accommodate all service and maintenance areas:

2.5.1. The HDSS square footage shall be less than 150 square feet and no single dimension shall exceed 10 feet.

2.5.2. The HDSS shall have no individual component dimensions (including casters) that exceed:

2.5.2.1. Width: 30 inches

2.5.2.2. Height: 80 inches

2.5.3. The HDSS shall conform to available facility power requirements below:

2.5.3.1. 3 phase: 208, 5-wire wye configuration

2.5.3.2. Voltage: 198 to 216 volts, 208 nominal

2.5.3.3. Current: 30 amps maximum

2.5.3.4. Frequency: 57 to 63 hertz, 60 hertz nominal

2.5.3.5. Connector plug: L21-30P

2.5.4. The Contractor shall provide and integrate an Uninterruptible Power Supply (UPS) adequate to run the entire HDSS (and all support computers/instruments/equipment) for 20 minutes in normal operations, following the loss of commercial power.

2.6. HDSS Calibration

Required calibration and maintenance equipment (hardware and software) shall be integrated in the HDSS.

2.6.1. The Contractor shall provide all equipment for calibration and maintenance (including hardware and software and special equipment).

2.6.2. The HDSS shall allow calibration and routine maintenance to be performed by organic personnel, described in appropriate user and maintenance manuals.

2.6.3. The HDSS shall contain fault isolation testing operations capable of testing to the assembly level.

2.6.4. The Contractor shall provide calibration certificates for all required HDSS components.

[CDRL A004, Calibration Certificates, DI- QCIC-80798C/T]

2.7. Warranty

A warranty shall cover the HDSS software and hardware for a period of twenty-four (24) months from acceptance. The warranty shall be constructed in such a way that any failure or defect found is corrected in less than seven (7) days at no cost to the Government (labor, material, and associated travel) during the warranty period.

2.8. Packaging, Handling, Storage, and Transportation (PHS&T) The Contractor shall deliver and install the HDSS to BLDG 229S at Robins AFB, GA. (280 Byron Street, Robins AFB GA 31098-1670).

2.8.1. Delivery and installation shall be completed NLT 365 days after contract award. The Contractor shall ship all items in packaging that is consistent with commercial packaging recommendations with coordination 15 days prior to delivery and installation.

2.8.2. Delivery shall be for FOB Destination – Inside delivery to include uncrating/unpacking all items.

2.8.3. Delivery Address and DoDAAC:

402 SMXG/MXDE

280 Byron Street Bldg 229S Robins AFB, GA 31098-1610 DoDAAC: F3QCCM

Point of Contacts:

2.9. Documentation

In addition to the HDSS, the Contractor shall deliver the following documentation to the Government:

2.9.1. All Interface documents with Government Purpose Rights.

[CDRL A001, Interface Design Document, DI-IPSC-81436A/T]

2.9.2. Monthly Status Reports

Monthly Status Reports (MSR) containing “need by” dates, Technical Interchange Meeting (TIM) notes, action item lists, CLIN expenditures, Program Management (PM) data, Integrated Master Schedule (IMS), etc.

[CDRL A002, Monthly Status Reports (MSR), DI-MGMT-80368A/T]

2.9.3. Data Accession List

[CDRL A003, Data Accession List (DAL), DI-MGMT-81453B/T]

2.9.4. Operation and Maintenance Manual with calibration procedures, system component removal/repair procedures, preventative maintenance procedures, etc.

[CDRL A005, System Technical Manual – Operations and Maintenance Manual, DI-TMSS-81677B/T]

2.9.5. Software User Manual (SUM) with the following tolerance data and user selectable range included in the HDSS:

2.9.5.1. Attenuation modes with user selectable values

2.9.5.2. Platform Motion Characteristics (SUTs and other programmable emitters)

2.9.5.3. PRI Modulations modes with values and tolerances

2.9.5.4. Frequency Modulation modes with values and tolerances

2.9.5.5. Pulse modulation modes with values and tolerances

2.9.5.6. Pulse Shaping modes with values and tolerances

2.9.5.7. Scan Modulation modes with values and tolerances

2.9.5.8. Power modes with values and tolerances

2.9.5.9. Port-to-port phase coherency values and tolerances

2.9.5.10. External time synchronization

2.9.5.11. Transmit Antenna Polarization types and tolerances

[CDRL A006, Software User Manual, DI- IPSC-81443A/T]

2.9.6. Software product description, software product version information, and computer software product for the software installed on the simulator.

[CDRL A007, Software Product Package, DI-IPSC-82090A/T]

2.9.7. Test Plan Reports (Acceptance Test Plans, Acceptance Test Reports, etc.). The Contractor shall identify processes for ATPs, requirements verification, and documentation for potential reuse for this effort. Wherever possible, tools, equipment, and test methods shall be reused to improve efficiency and confidence in the testing, requirements verification and delivery.

[CDRL A008, Acceptance Test Plan, DI-QCIC-80553A/T] [CDRL A009, Acceptance Test Report, DI-QCIC-81891/T]

2.10. Acceptance Testing

An Acceptance Test Plan (ATP) shall be developed by the Contractor and delivered to technical points of contact (TPOC) no less than 60 days prior to the scheduled delivery and installation of the HDSS. All changes/modifications to the ATP by the TPOCs will be delivered to the Contractor 15 days prior to the scheduled delivery and installation of the HDSS.

2.10.1. The Contractor shall use the ATP to perform a site acceptance test (SAT); the SAT shall be executed and passed after delivery, assembly, and installation of the HDSS at EWAISF.

2.10.2. The Government shall supplement the factory ATP with threat injection evaluation of existing organization threats in the frequency ranges and will not accept delivery until complete.

[CDRL A008, Acceptance Test Plan, DI-QCIC-80553A/T] [CDRL A009, Acceptance Test Report, DI-QCIC-81891/T]

2.11. Familiarization Training

The Contractor shall provide an HDSS familiarization for 20 people immediately following acceptance testing. The familiarization shall be presented with documentation (printed presentation slides, best practice guides, programmer’s guides, ‘quick-start’ pamphlet, workbooks, Electronic Warfare (EW) textbooks, etc.) as needed. Soft copies of the familiarization material shall be provided 14 days before the familiarization event. Attendees will keep all materials developed and presented. The familiarization shall be constructed and executed in a way that allows students and trainers to converse while providing ample time for hands-on demonstrations. The familiarization shall be conducted at Robins AFB, GA. All attendees shall receive a certificate of familiarization. The familiarization shall include at least the following items:

2.11.1. Known or expected limitations of the HDSS.

2.11.2. A conceptual overview of hardware and software used to operate the HDSS.

2.11.3. All screenshots applicable to threat development, test execution, calibration and maintenance.

2.11.4. Demonstration of:

2.11.4.1. Threat generation to include all options for pulse, frequency and amplitude intermodulation

2.11.4.2. Threat generation of CW signals

2.11.4.3. A dynamic scenario of a single SUT through a dense environment

2.11.4.4. The usage of two (2) SUTs

2.11.5. Calibration, routine maintenance and fault isolation

[CDRL A005, System Technical Manual – Operations and Maintenance Manual, DI-TMSS-81677B] [CDRL A006, Software User Manual, DI- IPSC-81443A/T] [CDRL A010, Familiarization Materials, DI-ILSS-80872/T]

3.0 GENERAL INFORMATION

3.1. Government Furnished Equipment (GFE)

None.

3.2. Data Deliverables/Contract Data Requirements Lists (CDRL)

3.3. Government Technical Representatives

The on-site Government Technical Points Of Contact (TPOC) are:

3.4. Security Requirements

3.4.1. Government Security Regulations

The Contractor shall ensure personnel, information, system, facility, and international security requirements are met in accordance with DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), Air Force Instruction (AFI) 31-101, Integrated Defense.

3.4.2. Security Clearance

The Contractor shall ensure Contractor personnel have a valid security clearance appropriate to the access required for proper accomplishment of contract/order requirements. Classified material will not be accessed as part of this contract’s performance. Contractor personnel shall not be authorized access to classified and/or sensitive, but unclassified, information and/or materials or be permitted to work on classified and/or sensitive, but unclassified, projects and/or programs without a proper security clearance and a need-to-know. Contractor personnel whose clearances have been suspended or revoked shall immediately be denied access to classified and/or sensitive, but unclassified, information.

3.4.3. Communications Security (COMSEC)

The Contractor shall use only secure communications methods and/or equipment to transmit or otherwise transfer classified and/or sensitive, but unclassified, information in accordance with DoD 5220.22-M.

3.4.4. Access to Government System

The Contractor shall ensure a CAC is obtained by all contractor/subcontractor personnel who require access to DoD computer networks/systems, for DoD facility entry control and/or for physical access to facilities and buildings to perform tasks under the contract/order. The Contractor shall provide a list of contractor/subcontractor personnel who require a CAC to the PCO. The Government will provide the Contractor instruction on how to complete a Contractor Verification System (CVS) application and notify the Contractor of approval/disapproval of contractor/subcontractor personnel application. Contractor/subcontractor personnel shall obtain the CAC from the local Real Time Automated Personnel Identification Documentation System (RAPIDS) issuing facility [usually the Military Personnel Flight PF)].

3.4.4.1. The Contractor shall immediately report a lost or stolen CAC as directed by local Government policy. The Contractor shall notify the PCO of any change to the list of contractor/subcontractor personnel who require a CAC and provide an updated list within five business days. The Contractor shall return a CAC within five business days once contractor/subcontractor personnel no longer require computer network/system access and/or facility access. The Contractor shall return an expired CAC within five business days after the expiration date. The Contractor shall return any and all CACs within five business days after completion/termination of the contract as directed by local Government policy.

3.4.5. Access to Government Facilities

3.4.5.1. The Contractor shall ensure Contractor personnel who require access to Robins AFB or other Government facilities comply with the security procedures of the facility.

3.4.5.1.1. The Security Manager of visiting personnel is required to submit a visit request through JPAS fifteen (15) days prior to arrival.

3.4.5.1.2. The SMO for the Software Support Facility (Bldg 229 Complex) is RX1MF126.

3.4.5.1.3. The Contractor personnel (visitor) shall provide the name of his/her Security Manager with the sponsoring POC name and phone number. The POC must be an individual who has unescorted access and escort capability in the facility.

3.4.5.1.4. Visit requests can be requested for a maximum of one year.

3.4.5.2. The Contractor shall ensure an ID card is obtained by all contractor/subcontractor personnel who require recurring access to a Government facility, but not local area network (LAN) access. The Contractor shall submit a letter to the PCO listing all contractor/subcontractor personnel requiring access to the facility. The PCO will approve the request and forward it to the issuing/registration office for processing. Contractor/subcontractor personnel shall report to the issuing/registration office to obtain the ID card(s).

3.4.5.3. The Contractor shall submit a letter to the PCO immediately if contractor/subcontractor personnel no longer require access, upon transfer/termination of contractor/subcontractor personnel or upon completion/termination of the contract/order. The letter shall identify the name(s) and social security number(s) of the contractor/subcontractor personnel. The Contractor shall return the ID card(s) to the issuing/registration office upon expiration, upon transfer/termination of contractor/subcontractor personnel, or once contractor/subcontractor personnel no longer require access to the facility. The Contractor shall return any and all ID cards to the issuing/registration office upon completion/termination of the contract.

3.4.6. Operations Security (OPSEC)

The Contractor shall ensure compliance with OPSEC requirements including procedures to protect classified and/or sensitive, but unclassified, Government projects and/or programs. The Contractor shall ensure Contractor personnel who perform work at Robins AFB or another Government facility comply with the OPSEC procedures of the facility.

3.4.7. Security Incident or Violation

The Contractor shall immediately notify the Government Security Office of any potential or actual security incidents or violations including potential or actual unauthorized disclosure or compromise of classified and/or sensitive, but unclassified, information.

3.5. Affirmative Procurement Programs (APP)

3.5.1. In accordance with FAR 23.404(b)(1), 100% of purchases of Environmental Protection Agency (EPA)-designated products included in the Comprehensive Procurement Guidelines (CPG) list [https://www.epa.gov/smm/comprehensive-procurement-guideline-cpg-program] and/or United States Department of Agriculture (USDA)-designated products included in the biobased product listings [http://www.biopreferred.gov] shall, at a minimum, meet the EPA or USDA standards for recovered materials or biobased content, respectively, unless an item cannot be acquired competitively within a realistic timeframe, meet appropriate performance standards, and/or be acquired at a reasonable price.’

3.5.2. In accordance with FAR 23.404(a)(iii), the Contractor shall provide estimates and verification of recovered material for EPA-designated CPG products and certification for both EPA-designated CPG products and USDA-designated biobased products. In accordance with the Robins Air Force Base, Georgia / Green Procurement Program (GPP) Plan, the Contractor shall provide estimates and certifications to the Government for completion of the applicable attachment(s) to be included in the Purchase Request (PR) package.

3.6. Environmental Management System (EMS) Awareness Training Environmental Management Systems (EMS) Awareness Training: All contractor personnel working on Robins AFB who perform activities on the installation are required to complete Air Force-provided initial EMS Awareness Training. It is the responsibility of the Prime Contractor to ensure that all sub-contractors, vendors, and employees complete this training prior to beginning work on Robins AFB. Notification of training completion shall be sent to both the Robins AFB Contracting Officer (CO) to be maintained in the contract file and Environmental Management, 78 CEG/CEIE, (78ceg.cev.FrontOfc@us.af.mil) for tracking purposes. Failure to provide documentation of EMS Training may result in termination of the contract.

3.6.1. EMS training is provided by Environmental Management at (478) 327-8104 or (478) 926-9645. Contractors have two options to satisfy the mandatory EMS Awareness Training requirement. Contractors that do not have a Common Access Card must exercise Option 2.

3.6.2. Option 1 (Preferred Option): The Air Force version of EMS Awareness Training is available through the Advanced Distributed Learning Service (ADLS) website: https://golearn.adls.af.mil/kc/rso/login/ADLS_login.asp. EMS Awareness Training is located under the miscellaneous tab. This option is only available to contractors who have a CAC and takes approximately 10 minutes to complete.

3.6.3. Option 2: Contractor requests a copy of the Robins EMS Awareness Training Power Point Presentation from Environmental Management. The request should be sent to the Environment Management Workflow Box at the following email address, 78ceg.cev.FrontOfc@us.af.mil. Once the presentation is received, the contractor is responsible for ensuring that all his/her employees view the training.

3.7. Place of Performance

Performance of the work is to be performed at the Contractor’s facility; with exception of installation and acceptance testing.

3.8. Hours of Operation

The Contractor’s work hours on Robins AFB shall be from 7:00 am to 3:30 pm (EST), Monday through Friday. Working any hours outside of this period shall be coordinated with the Government Representative and approved by the Contracting Officer.

3.9. Holidays and other Non-Work Periods

The Contractor personnel shall observe Federal holidays and closings, such as energy conservation days in accordance with the guidance provided for the WR-ALC civilian populace with regard to installation, acceptance testing and familiarization training.

3.10. Safety Requirements

The Contractor shall be responsible for the safety and health of all Contractor employees.

3.10.1. Contractor Safety & Health Plan Program:

The Contractor shall establish and maintain a safety and health program detailed in a written Contractor’s Safety and Health Plan tailored to this contract. This plan shall address the requirements established in Appendix C (Industrial Safety and Health Requirements). No more than two (2) Class C mishaps per contract year and Zero (0) Class A or B mishaps will be tolerated. The Contractor shall notify the cognizant safety office of any revisions made to its safety and health plan after contract award. All changes to the plan must also be submitted in writing and approved by the cognizant Government safety office.

[CDRL A011, Contractor’s Standard Operating Procedures – Safety Plan, DI-MGMT-81580/T]

3.10.2. Safety Mishap/Incident Reporting

The Contractor shall notify the WR-ALC Safety Office by telephone at 478)-926-1708 during duty hours and (478)-926-3567 after hours, within four (4) hours after initial notification of all mishaps or incidents for damage to DoD property (material plus labor) entrusted by this contract and employee injuries as a result of the contract operation. A follow-up (written or e-mail) of this mishap/incident notification shall be sent within three calendar days to the Government POC, the Procurement Contracting Officer (PCO) or the Administrative Contracting Officer (ACO), who will forward it to the Safety Office. The information that is not available at the time of the initial notification shall be provided within 20 calendar days after the mishap. Mishap notification shall contain, as a minimum, the following information:

3.10.2.1. Contract, Contract Number, Name and Title of Person(s) Reporting

3.10.2.2. Date, Time and exact location of accident/incident

3.10.2.3. Brief Narrative of accident/incident (Events leading to accident/incident)

3.10.2.4. Cause of accident/incident, if known

3.10.2.5. Estimated cost of accident/incident (material and labor to repair/replace)

3.10.2.6. Impound Authority Name and Phone Number (as applicable)

3.10.2.7. Nomenclature of equipment and personnel involved in accident/incident

3.10.2.8. Corrective actions (taken or proposed)

3.10.2.9. Other pertinent information

[CDRL A012, Accident/Incident Report, DI-SAFT-81563/T]

3.11. Robins Air Force Base Access and Gate Procedures

All commercial trucks must enter through Robins AFB Gate 4 (Commercial/Truck), for inspection. Gate 4 is open 0500 to 2000, Monday through Friday. Once at Gate 4, be prepared to exit the vehicle and allow for vehicle inspection. The driver must be able to show:

3.11.1. A current Vehicle Registration

3.11.2. A Current Proof of Insurance

3.11.3. A valid and current Driver’s License for the driver

3.11.4. A valid or current Driver’s License or other State Identification for any passenger(s) in the vehicle.

3.11.5. For Deliveries: A current Bill of Lading (BOL). The BOL must include the AF Installation name, date of anticipated delivery and specific destination (including building number, street address, and POC).

4.0 APPENDICES. None.