Appendix_P_UASOCS_12Feb15.docx

DOCX document 29 KB Posted

Attached to
Unmanned Aircraft System Operations Center Support (UASOCS)
Solicitation number
FA4890-14-R-0018
Issued by

About this file

Appendix P

View the file

Other files

File Type Posted
FBO_UASOCS_Award_Synopsis_02_Feb_2016.doc DOC document
UASOCS_CLINs_Pricing_Sheet_Updated_rev_7.xlsx XLSX spreadsheet
Final_RFP_Q_and_A__(01_May_15).xlsx XLSX spreadsheet
Conformed_Copy_of_UASOCS_Sol_FA4890-14-R-0018_(Through_Amendment_0002).pdf PDF
Amendment_0002_-_UASOCS_Solicitation_FA4890-14-R-0018.pdf PDF
UASOCS_PPC__companies_attending.docx DOCX document
Extension_of_Q_and_A_to_30_April.docx DOCX document
UASOCS_CLINs_Pricing_Sheet_Updated_rev_6.xlsx XLSX spreadsheet
Amendment_0001_-_UASOCS_Sol_FA4890-14-R-0018.doc DOC document
UASOCS_PWS_20_Apr_2015.docx DOCX document
Draft_Appendix_F--Award_Fee_Plan-_20_Apr_15.docx DOCX document
Clarification_on_9_April_2015_Posting.docx DOCX document
CDRL_A013_-_GFP_432_WG_(9_Apr_15).xls XLS spreadsheet
Appendix_B_UASOCS_9_Apr_15.pdf PDF
Final_RFP_Q_and_A__(9_Apr_15).xlsx XLSX spreadsheet
Past_Performance_Questionnaire.doc DOC document
DD_Form_254__-_UASOCS_(Draft).pdf PDF
UASOCS_DD254_Continuation_Pages.rtf RTF text file
EUR1_CDRL_Mar_2015__Ramstein.xls XLS spreadsheet
EUR2_GFP_Ramstein.XLSX XLSX spreadsheet
Appendix__L_UASOCS26Mar15.docx DOCX document
Final_RFP_Q_and_A_26_March_2015.xlsx XLSX spreadsheet
UASOCS_RFP__DD254.pdf PDF
Final_RFP_Q_and_A_20_March_2015.xlsx XLSX spreadsheet
UASOCS_PreProposal_Conference_Agenda.docx DOCX document
Ramstein_GFP_1.xlsx XLSX spreadsheet
Ramstein_additional_equipment_SRVT_GFE.xlsx XLSX spreadsheet
Ramstein_GFP.xlsx XLSX spreadsheet
UASOCS_Help_Desk_Tickets_2012-2014.xls XLS spreadsheet
CDRL_A013_-_Government_Furnished_Property_432_ATKS_(19_Dec_13).xlsx XLSX spreadsheet
CDRL_A013_-_Government_Furnished_Property_732_OG_(Sep_14).pdf PDF
PAC_1_GFE_Update_12_Mar_2015.XLS XLS spreadsheet
UASOCS_FBO_posting_Ques_and__-_Govt_Answers_(6_Mar_2015).docx DOCX document
CDRL_A013_-_Government_Furnished_Property_432_WG_(19_Dec_13).xlsx XLSX spreadsheet
Errata_for_Final_RFP_FA4890.docx DOCX document
WD_2005-2485_Rev_14.pdf PDF
WD_2005-2331_Rev_15.pdf PDF
Appendix_O_UASOCS_12_Feb_15.docx DOCX document
UASOCS_PWS_4_Mar_2015.docx DOCX document
Appendix_N_UASOC_12Feb15.docx DOCX document
Appendix_Q_UASOCS_12Feb15.docx DOCX document
Appendix_I-UASOCS_11Feb15.docx DOCX document
Appendix_S_UASOCS_12Feb15.docx DOCX document
Appendix_C_UASOCS_12Feb15.docx DOCX document
WD_2005-2511_Rev_19.pdf PDF
UASOCS_Final_RFP_Doc_-_5_Mar_15.pdf PDF
Appendix_B_UASOCS_5_Mar_15.pdf PDF
Appendix_K_UASOCS_12Feb15.docx DOCX document
Appendix_E_UASOCS_11Feb15.docx DOCX document
WD_2005-2543_Rev_17.pdf PDF
Show 40 more

Latest 50 of 130 listed here. See the rest on GovTribe.

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

UASOCS PWS

Solicitation No. FA4890-14-R-0018

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 UASOCS customers/users.

1.3. REPORTING: (U//FOUO) The help desk will submit an accurate COMSTAT on all reportable events to the WOC Director and COTR 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 UASOCS 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 UASOCS systems or subsystems having degraded services or one to multiple redundancies (where available) are not operating, configured correctly or are unsafe. The UASOCS system 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 UASOCS systems or subsystems unable to perform any mission.

EXAMPLE:

1 CS/CFP COMSTAT

Langley AFB, Va

1. COMSTAT POC:

Rank/Name: SSgt Doe, Chris Unit/Org: 1 CS Location: Langley AFB, Va Phone: (312) 574-1111 Other: 574-2222 (STE)

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 MCCC via SIPRNET e-mail. Use secure voice if SIPRNET access is not available.

2.4. THRESHOLDS:

2.4.1. A C2 link goes down for more than 15 minutes (with or w/o redundancy)

2.4.2. A video customer is isolated for more than 15 minutes

2.4.3. A feed (video from a UAS to all customers) goes dark for more than 15 minutes

EXAMPLE:

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

1. COMPSPOT POC:

Rank/Name: SSgt Doe, Pat Unit/Org: 1 CS/CFP Location: Langley AFB, Va Phone: (312) 574-1111 Other: 574-2222 (STE)

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)

File details come from the government source that posted it. Updated .