Sec_L_L-1_Scenarios.pdf

PDF 360 KB Posted

Attached to
4MS-4th Space Operations Squadron (4SOPS) Mission Support Federal contract opportunity
Solicitation number
FA2550-16-R-8004
Issued by
Department of the Air Force Space Command

About this file

Section L Attachment L-1 Scenarios

View the file

Other files for this federal contract opportunity

Other files attached to 4MS-4th Space Operations Squadron (4SOPS) Mission Support, newest first.
File Type Posted
4MS_Award_Synopsis.pdf PDF
FA2550-16-R-8004-0001.pdf PDF
FA2550-16-R-8004-RFP_ATCH_1_PWS_REV_22AUG16.pdf PDF
FA2550-16-R-8004-0001-conformed.pdf PDF
4MS-RFP-Q_ _As.pdf PDF
FA2550-16-R-8004-RFP_ATCH_1_PWS_REV_18AUG16.pdf PDF
FA2550-16-R-8004-RFP_EXHIBIT_A_CDRLS.pdf PDF
Sec_L_L-4_Total_Price_Summary.xlsx XLSX spreadsheet
Sec_L_L-2_Staffing_Plan_Table.xlsx XLSX spreadsheet
Sec_L_L-3_PD_Table.docx DOCX document
FA2550-16-R-8004_RFP_Cover_Letter-20160803.pdf PDF
FA2550-16-R-8004-RFP_ATCH_2_DD254_Attachment.pdf PDF
FA2550-16-R-8004_RFP.pdf PDF
FA2550-16-R-8004-RFP_ATCH_2_DD254.pdf PDF
FA2550-16-R-8004-RFP_ATCH_1_PWS.pdf PDF
Show all 15

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

FA2550-16-R-8004

Section L, Attachment L-1 - Scenarios

1. A Navy Multi Band Terminal (NMT) user calls with problems acquiring the satellite. The operator is new, and the best they can tell the terminal is working fine. There are no faults and the weather directly outside is clear, but the sea states are moderate. They are 958 nautical miles North East of the Hawaiian Islands, and wanting to operate Extended Data Rate (XDR) networks on AEHF 3 (Located at 152 E Longitude). Reginal SATCOM Support Center Pacific (RSSC PAC) is handling multiple other user issues, and has asked the Petty Officer to call 4 SOPS for assistance.

Outline what questions would be appropriate to ask in this situation, and what other concerns are present with the limited information you have gained thus far?

2. A Marine unit called saying they are having issues putting a shot into a Family of Beyond Line of sight Terminal (FAB-T) from their ASMART-T, as part of strategic contingency testing.

The FAB-T is the Communications Controller (CC) and has confirmed the network is up and active. When the Marines try to join, they received a reject from the CC. The Marine Sergeant verified that the service was 19.2 Kbps, the ASMART-T is not CC capable, and both the terminals were verified to be at a Priority 2.

What would cause this and how would the problem be identified using both tools and documents? Once the problem is identified, what can the users do to rectify the situation?

3. First thing Monday morning you receive a call from the IPASC requesting a BSMRCA Duty Cycle change for the UK. The A SMART-T is powered on, but in standby. As you are logging on to XDR on AEHF 1, you notice a note by the terminal saying that the On Call was in over the weekend, and the terminal had been acting up. The fix action was to load a new terminal image, and operations were normal from that point on. The terminal logged onto the LGEC with no problem and had good SNR. When you try to synchronize Terminal Control (TC) to accomplish the IPASC request the process consistently fails.

What would cause this problem with TC, and what can be done to remedy the situation so proper support can be provided to the International Partners?

4. The Army Terminal Program Office (TPO) contacted the squadron through Air Force Space Command (AFSPC) with a request about how Army terminals are conducting themselves as Antenna Controllers (AC) on the system. The TPO wants to know how many of their MDR ACs move the same beam they are logged onto, or if they typically move other beams. MPSS is unable to produce this information in a single report through the typical dialogs. The Army needs this info for possible changes to a future software release on their A SMART-Ts.

With the Schema provided in the bidder’s library, provide a query that will return the desired results.

Note: MPSS with a RM database will be provided at request for this scenario.

5. The following narrative is representative of a number of fictional scenarios containing various communications issues. You, as the Protected Band Watch Officer, need to identify which reporting actions need to take place to be fully compliant with current guidance and documentation.

- A user called saying they cannot establish communication on a KGV-11 network. The Crypto shop is working to verify that they are making the requests for, and receiving, the necessary keys correctly.

- A summer rainstorm has impacted all Command and Control networks at SAFB and forced all roles out to Vandenberg.

- The AFCPT at Beale AFB reported an unscheduled outage due to a malfunction with the High Power Amplifier on the terminal. Estimated Time of Restoral is four to six hours.

- Multiple units have reported problems with UFO 2 and NAVSOC has been unable to contact it for the past 30 minutes.

6. A Special User operating an ASMART-T contacts you and states he is unable to complete logon to AEHF 1. The unit received a new end cryptographic unit (ECU) recently completed endorsement, and he personally confirmed receipt of the necessary mission keys. The terminal is able to complete both downlink and uplink acquisition but fails to complete logon. When asked, the terminals SNR was as good as the operator has ever seen it.

What would cause a terminal to behave this way, and what can be done to rectify the situation?

7. It is shortly after the new contract period of performance has started. You are working on the Squadron’s A SMART-T and notice that on the terminal endorsement key status screen the expiration is set for the following month. It is nearing the end of the current month.

Is there any cause for concern with the information you just uncovered? What actions need to be taken with the terminal to ensure it maintains successful operations?

8. You are part of a team that will be briefing 4 SOPS leadership on an upcoming payload change to AEHF 3. USPACOM has sent in multiple requests for changes to the configuration of all 3 waveforms (LDR/MDR/XDR) on both uplink and down. Prior to briefing the Commander and DO, the team has asked for you to take a final look to see if there are any operational or technical concerns needing to be addressed prior to running the final frequency plan.

Identify any technical deficiencies in the following table, which represents the changes being made.

Assumption: The Downlink Hop numbers have been intentionally skewed for classification purposes, so the totals of both Transmitter Chain and Frequency Channel are going to be wrong and do not need to be addressed.

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