DRAFT Attachment 0115 - SIL Configuration and Verification Audit (SCAVA).docx

UNCLASSIFIED

Attachment 0115 SIL (Systems Integration Lab) Configuration and Verification Audit (SCAVA) October 2021

Distribution Statement A – Approved for Public Release; distribution unlimited

General The SCAVA is used to verify the CSIL (Contractor Systems Integration Lab):

1. Establish and maintain CSIL configuration management control

2. Static single facility with a designated room (environmentally controlled and secure) with all equipment (GFE and CFE) concurrently present in a defined test bench and floor (for larger items) locations

3. COMSEC and CCI storage

4. COMSEC device maintenance

5. COMSEC keying material management, EKMS (keying material) transfer to vendor, device fill, and end COMSEC device

6. All GFE and CFE (incl. all kits with electrical interfaces) systems

7. All vehicle electrical system components

8. Vehicle production intent wiring and interconnects

9. All GFE terrestrial and satellite antennas are permanently mounted outside on the building roof with clear view of sky for satellite coverage (incl. GPS)

10. GFE and CFE software

11. Contractor obtained terrestrial spectrum use (frequency, power, radius from CSIL) approval for each GFE communication system

12. Contractor obtained CSIL facility/room clearance up to SECRET and as directed by the DD254

13. Conduct operational verification including operational vignettes of the systems including CSIL bi-directional data and voice connectivity (internal to CSIL, CSIL – Gov’t NOC, CSIL – Contractor vehicle(s))

14. Conduct system stress tests using simulation tools to stimulate the CFE and GFE

15. Information Assurance/Cyber

Configuration

The Contractor shall develop and maintain the following for the CSIL information:

1. Floor plan with all equipment identified

2. List of equipment (incl. CFE, GFE, infrastructure systems, hardware, software, harnesses) and schedule for integration and SCAVA events

3. External GFE antennas placement

4. Electrical schematics (incl. detailed logical wiring diagrams, schematics, electrical one-wire diagrams, connector pin-outs and types, wire types, and physical routing diagrams)

5. IA/Cyber vulnerability status (IAVA, patch updates)

6. CFE and GFE operational readiness

7. COMSEC keying material on distribution schedule

8. CSIL verification methods and results

9. CSIL maintenance requirements (incl. COMSEC Hold-Up-Battery replacement schedule)

Verification

The Contractor shall demonstrate the following operations individually and as part of an operational vignette:

1. CFE and GFE (hardware and software systems) stress testing

2. Vetronics operation and driver systems (displays and controls)

3. Vetronics diagnostics on-platform and GFE at-platform devices

4. Bi-directional OTA (Over the Air) communication (voice and data) to and from CSIL for each communication and software systems

5. CFE and GFE operational capabilities for each system/item

6. Platform systems interoperability

7. Off-platform systems interoperability

8. Long duration system power-on stability

Operational Vignettes

Vehicle Operation

A. The driver starts the ignition and releases the parking brake. The driver adjusts the CTIS, suspension, and lighting settings. The driver verifies the basic automotive display settings function in static condition: fuel, engine oil pressure, tachometer, speedometer, odometer, and coolant temperature. The driver verifies situational awareness with cameras. The driver reaches a speed to verify automotive display settings in dynamic condition. The driver attempts to adjust the CTIS, suspension, and lighting settings.

B. The driver starts the ignition and verifies the DC bus voltage, current, and power for automotive configuration. The passenger turns on the radios, CROWS, and CREW. The driver verifies the DC voltage, current, and power settings and sheds these loads for continued operation.

C. The driver verifies the current health status of the automotive configuration. The driver changes the DSDU display to mobility settings. The passenger removes automotive sensor and driver acknowledges fault on DSDU. The driver selects the affected subsystem on the DSDU to view the detailed description of the fault and obtain the relevant section of the ETM. The driver searches the ETM on the DSDU to find maintenance procedures associated with the fault code. The passenger replaces sensor and driver verifies health status of automotive configuration. The driver enters a note on the DSDU about the issue that was experienced to be later used by the maintainer to troubleshoot the vehicle. The maintainer demonstrates the EMSS or MSD ability to query diagnostics faults. The maintainer reviews CBM data storage on the DSDU.

D. If the DSDU is kitted, the DSDU shall be removed. The driver changes the mobility settings. The passenger removes automotive sensor and driver acknowledges fault. The passenger replaces sensor and driver verifies health status of automotive configuration. The maintainer demonstrates the EMSS or MSD ability to query diagnostics faults.

C5ISR/EW Operation A. The Commander utilizes the CSDU to remotely change radio and intercom settings. The Commander verifies on the radio and intercom that the commanded changes have occurred. The Commander launches Primary GFE application. Using the Primary GFE application the Commander sends and receives data using GFE communication devices to Gov’t NOC and Contractor vehicles.

I. Remote control verified on each GFE voice radio II. Primary GFE and Core Service applications III. GFE radios/communication paths B. The Commander utilizes CSDU to remotely access and control ASDU #1 Primary Applications. Using the Primary GFE application hosted on ASDU the Commander sends and receives data using GFE communication devices to Gov’t NOC and Contractor vehicles.

I. All ASDU #1 hosted Primary GFE applications and each of its respective GFE radios/communication paths shall verified C. The Commander utilizes CSDU to remotely access and control ASDU #2 Primary Applications. Using the Primary GFE application hosted on ASDU the Commander sends and receives data using GFE communication devices to Gov’t NOC and Contractor vehicles.

I. All ASDU #2 hosted Primary GFE applications and each of its respective GFE radios/communication paths shall verified D. The 2nd row crewmember utilizes the ASDU to remotely change radio and intercom settings. The crewmember verifies on the radio and intercom that the commanded changes have occurred. The crewmember launches Primary GFE application. Using the Primary GFE application the crewmember sends and receives data using GFE communication devices to Gov’t NOC and Contractor vehicles.

I. Remote control verified on each GFE voice radio II. All hosted Primary GFE applications and each of its respective GFE radios/communication paths shall verified E. The 2nd row crewmember utilizes ASDU to remotely access and control CSDU Primary Applications. Using the Primary GFE application hosted on CSDU the crewmember sends and receives data using GFE communication devices to Gov’t NOC and Contractor vehicles.

I. All CSDU hosted Primary GFE applications and each of its respective GFE radios/communication paths shall verified

UNCLASSIFIED