Appx_P_COMSPOT-COMSTAT(6Nov2013)DRAFT.docx

Solicitation No. FA4890-13-R-0117

DRAFT

APPENDIX P

COMMUNICATIONS STATUS AND COMMUNICATIONS POSTURE REPORTS

1.0 Communications Status (COMSTAT) Report:

1.1. OVERVIEW: (U//FOUO) This appendix provides an unclassified example of a Communications Status Report (COMSTAT). It gives a brief overview of its purpose and describes the content of the information to be included in a COMSTAT.

1.2. PURPOSE: (U//FOUO) COMSTATs are daily reports of all planned and unplanned outages, as well as updates to current significant events. COMSTATs provide general availability oversight of core systems supporting FOL customers/users.

1.3. REPORTING: (U//FOUO) JOC Personnel will submit an accurate COMSTAT on all reportable events to the AFSOUTH/A6, FOL/CC and COR via SIPRNET e-mail, NLT 1700Z, daily. Use secure voice, if SIPRNET access is not available.

1.4. COMMUNICATIONS SYSTEMS DAILY STATUS:

1.4.1. FMC-Fully Mission Capable. This status is defined as all FOL-Curacao and FOL-Aruba systems and subsystems are operating in the correct, safe configuration including full redundancy (where available)and being fully mission capable. Equipment is fully mission capable when it can perform all of its combat missions without endangering the lives of crew or operators.

1.4.2. PMC-Partially Mission Capable. This status is defined as FOL-Curacao and/or FOL-Aruba systems or subsystems having degraded services or one to multiple redundancies (where available) are not operating, configured correctly or are unsafe. The FOL-Curacao and/or FOL-Aruba systems will be able to perform at least one but not all of its missions because maintenance is required to clear the discrepancy.

1.4.3. NMC-Non Mission Capable. This status is defined as FOL-Curacao and/or FOL-Aruba systems or subsystems unable to perform any mission.

EXAMPLE:

1 CS/CFP COMSTAT

Langley AFB, Va

1. COMSTAT POC:

C-2: FMC

Video: FMC

2.0 Communications Posture (COMSPOT) Report:

2.1. OVERVIEW: (U//FOUO) This appendix provides an unclassified example of a Communications Posture (COMSPOT) report. It gives a brief overview of its purpose and describes the content of the information to be included in a COMSPOT.

2.2 PURPOSE: (U//FOUO) COMSPOTs are reports generated when an unscheduled outage occurs, as well as updates to ongoing significant events. COMSPOTs are three phase reports providing information on unscheduled outages in the form of an INITIAL, FOLLOW-UP and FINAL report.

2.3. REPORTING: (U//FOUO) The help desk will generate an accurate INITIAL COMSPOT when an unscheduled outage meets thresholds identified in paragraph 2.4. A FOLLOW-UP COMSPOT will be generated each time the original outage status changes or every 2 hours. A FINAL COMSPOT will be generated once the unscheduled outage has been cleared. All COMSPOTS will be sent to the AFSOUTH A6 via SIPRNET e-mail. Use secure voice if SIPRNET access is not available.

2.4. THRESHOLDS are defined by the MESL in Appendix X:

EXAMPLE:

1 CS/CFP COMSPOT (INITIAL, FOLLOW-UP or FINAL) Langley AFB, Va

1. COMPSPOT POC:

2. OUTAGE DETAILS:

(U) LOCAL TROUBLE TICKET NUMBER:

(U) THIRD PARTY TROUBLE TICKET NUMBER (if applicable): (i.e. I-NOSC, DISA, CITS etc.)

(U) UNSCHEDULED EVENT: (Y,N)

(U) SUBJECT: (BRIEF OUTAGE DESCRIPTION OR EQUIPMENT/SYSTEMS AFFECTED)

(U) CURRENT STATUS: (INDICATE AS INITIAL, FOLLOWUP, OR FINAL)

(U) EXECUTIVE SUMMARY: (SPECIFIC DETAILS)

(U) MISSION IMPACT: (NUMBER OF USERS, FO/GO AFFECTED)

(U) ALTERNATE CAPABILITY: (SELF EXPLANATORY)

(U) FIX ACTION: (DETAILED ACTIONS TAKE TO RESOLVE EVENT)

(U) START TIME: (ZULU)

(U) STOP TIME: (ZULU)

(U) OUTAGE/DOWNTIME DURATION: (SELF EXPLANATORY)

P-1