SYSTEM REQUIREMENTS DOCUMENT (SRD) - Air Force Freedom ...

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Requirement Text Containing TBXThe Video Services, at a minimum, shall simultaneously encode eighteen (18)videos [TBR-19]: 10 videos for the Unclassified enclave and 4 videos each forSecret and ROKUS. [SRD ID 14530]The Video Services shall simultaneously encode thirty-six (36) videos [TBR-20]:20 videos for the Unclassified enclave and 8 videos each for Secret and ROKUS.[SRD ID 14531]The Streaming Packet Service shall support the processing of IP multicast datastreams at data rates up to 20 Mbps each. [TBR-21] [SRD ID 14700]The EPG shall provide three days [TBR-22] of broadcast history, specific to eachindividual receive suite that will allow the RBMs to determine what broadcastcontent that was intended for them was not received. [SRD ID 15000]The Tuning Guide shall allow the SBM Operator to update the NIPRNET TuningGuide within 5 minutes [TBR-23] after being notified of JIPM updates by theTactical Network Controller (TNC). [SRD ID 15900]The Tuning Guide shall allow the SBM Operator to update the SIPRNET andROKUS Tuning Guide within 2 hours [TBR-24] of being notified of JIPM updatesby the TNC. [SRD ID 16000]The BDA Usability shall support at least 250 [TBR-25] concurrent users (i.e., GBSOperations Managers, TIM, Content Providers, End User with reachback), perenclave, without degradation of service. [SRD ID 17000]The SBM shall support the Session Description Protocol for content providerentry of video descriptors. [TBR-26] [SRD ID 17300]The BDA shall adjust transmit data rates, within each enclave, with minimalinterruption to the broadcast (e.g., 1 minute or less [TBR-27]). [SRD ID 19000]TBX ResolutionTBR-19 - We accept the value as is in the baseline.Recommend closure of TBR-19 after ATP.TBR-20 - We accept the value as is in the baseline.Recommend TBR-20 closure after ATP.TBR-21 - We accept the value as is in the baseline.Recommend TBR-21 closure after ATP.TBR-22 - We accept the value as is in the baseline.Recommend TBR-22 closure after ATP.TBR-23 - We accept the value as is in the baseline.Recommend TBR-23 closure after ATP.TBR-24 - We accept the value as is in the baseline.Recommend TBR-24 closure after ATP.TBR-25 - We accept the value as is in the baseline.Recommend TBR-25 closure after ATP.TBR-26 - We accept the value as is in the baseline.Recommend TBR-26 closure after ATP.TBR-27 - We accept the value as is in the baseline.Recommend TBR-27 closure after ATP.This Current SBM status information shall be current to within 5 minutes [TBR-28]. [SRD ID 21202]This Current RBM status information shall be current to within 10 minutes [TBR-29]. [SRD ID 21303]The GBS System Monitoring Service, with respect to GBS Usage Statistics, shallstore, process, compile historical information, and generate usage statistics overselectable time intervals [TBR-30] for each enclave. [SRD ID 21501]The GBS System Monitoring Service, with respect to GBS Usage Statistics, shallstore, process, compile historical information, and generate usage statistics overselectable time intervals [TBR-30] for each enclave. [SRD ID 21501]The GBS System Monitoring Service, with respect to GBS Usage Statistics, shallprovide the ability to generate, in the Secret enclave, a merged usage statisticalreport on a daily basis [TBR-31]. [SRD ID 21503]The broadcast segment shall replicate 100 percent of the system managementand system configuration parameters at the COOP site every thirty (30) minutes[TBR-32] to facilitate a transfer of SBM operations. [SRD ID 24900]The broadcast segment shall be capable of ingesting a minimum of 300 Mbps[TBR-33] of files per enclave (Secret and Unclassified). [SRD ID 25100]The broadcast segment shall be capable of ingesting a minimum of 400 Mbps[TBR-34] of IP data and video streams per enclave (Secret and Unclassified).[SRD ID 25200]The broadcast segment shall be capable of ingesting a minimum of 200 Mbps[TBR-35] of files in the ROKUS enclave. [SRD ID 25300]TBR-28 - We accept the value as is in the baseline.Recommend TBR-28 closure after ATP.TBR-29 - We accept the value as is in the baseline.Recommend TBR-29 closure after ATP.TBR-30 - We accept the value as is in the baseline.Recommend TBR-30 closure after ATP.TBR-30 - We accept the value as is in the baseline.Recommend TBR-30 closure after ATP.TBR-31 - We accept the value as is in the baseline.Recommend TBR-31 closure after ATP.TBR-32 - Open – This TBR value is dependent onDECC service level agreements (SLAs) for datareplication between the Primary and COOP sites.Based on the LM Team’s proposed DECC SLAs, werecommend that TBR-32 be changed to one (1) minute.We will work with the DISA DECC personnel onresolution of TBR-32 after ATP.TBR-33 - We accept the value as is in the baseline.Recommend TBR-33 closure after ATP.TBR-34 - We accept the value as is in the baseline.Recommend TBR-34 closure after ATP.TBR-35 - We accept the value as is in the baseline.Recommend TBR-35 closure after ATP.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-99

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Requirement Text Containing TBXThe broadcast segment shall be capable of ingesting a minimum of 200 Mbps[TBR-36] of IP data and video streams in the ROKUS enclave. [SRD ID 25400]The broadcast segment shall be capable of supporting a nominal data rate of 72Mbps [TBR-37] for each group of multicast streams per modulator. [SRD ID25900]The RBM Heartbeat shall indicate a loss of the heartbeat signal via the displayedicon if any heartbeat is not received for an extended period [TBR-38]. [SRD ID30106]Specific to OTA Software and IA Updates only, the RDA shall have the ability toallow the end user to select if and when they will install the automated IAupdates.[TBR-39] [SRD ID 35800]Specific to OTA Software and IA Updates only, the RDA shall process OTAsoftware updates and include a mode that overrides the end user control forcritical updates. [TBR-40] [SRD ID 35900]The RDA shall be functionally compatible with the existing IP broadcast by beingable to auto-forward content using FTP and FTPS [TBR-41] similar to the existingreceive suite so that the system can be interchanged with existing receive suites.[SRD ID 36100]The RDA shall be functionally compatible with the existing IP broadcast by beingable to provide the receive suite presence display required information [TBR-42].[SRD ID 36500]The RDA shall be capable of supporting Ipv6. [TBR-43] [SRD ID 37100]The Auto Push functionality shall deliver products via FTPS or SFTP [TBR-44](act as FTPS or SFTP client) to end user systems. [SRD ID 39500]The Video functionality shall provide IP video recording capability for at least 30minutes, at a minimum rate of 3 Mbps [TBR-45], so that incoming video streamscan be time shifted. [SRD ID 41000]The SBM to DECC Facility interfaces shall comply with [the TBD-1] establishedDECC interface standards and policies. [SRD ID 44500]TBX ResolutionTBR-36 - We accept the value as is in the baseline.Recommend TBR-36 closure after ATP.TBR-37 - We accept the value as is in the baseline.Recommend TBR-37 closure after ATP.TBR-38 - We accept the value as is in the baseline.Recommend TBR-38 closure after ATP.TBR-39 - We accept the value as is in the baseline.Recommend TBR-39 closure after ATP.TBR-40 - We accept the value as is in the baseline.Recommend TBR-40 closure after ATP.TBR-41 - We accept the value as is in the baseline.Recommend TBR-41 closure after ATP.TBR-42 - We accept the value as is in the baseline.Recommend TBR-42 closure after ATP.TBR-43 - We accept the value as is in the baseline.Recommend TBR-43 closure after ATP.TBR-44 - We accept the value as is in the baseline.Recommend TBR closure after ATP.TBR-45 - We accept the value as is in the baseline.Recommend TBR-45 closure after ATP.TBD-1 - Open – This requirement is dependent onDECC interface documents which the contractor hasnot yet seen. We will work with the DISA DECCpersonnel on closure of this TBD-1 after ATP.Each LRU element of the GBS system shall include Built-In-Test (BIT)TBR-46 - We accept the value as is in the baseline.diagnostics that fault isolate using contractor supplied test equipment, 95% of the Recommend TBR-46 closure after ATP.time [TBR-46]. [SRD ID 48400]If support equipment is required, the GBS System support equipment, at aminimum, shall be comprised of 90 percent [TBR-47] COTS support equipment.[SRD ID 52600]The broadcast segment shall support the 10 satellites, 100 downlink beams, 56aggregated streams (each consisting of multiple multicast streams to be injectedby a specific modulator at the JIPM hub), 5000 RBMs, 2500 subscriptions(content folders and IP streams), and 250 content providers. [TBR-48] [SRD ID25500]The DISN to SBM DMZ interfaces shall accept various files and streamingproducts from sources using standard internet protocols that include but are notlimited to Encapsulated Security Payload (ESP), Secure Shell (SSH), Simple MailTransfer Protocol (SMTP), Simple Mail Transfer Protocol Secure Sockets Layer(SMTP SSL)Domain Name Server (DNS), Hyper Text Transfer Protocol (HTTP),Hyper Text Transfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), FileTransfer Protocol over Secure Sockets Layer (FTPS), SSH File Transfer Protocol(SFTP), Message Hopper [TBR-49], MSCHAT [TBR-50], Power Publisher, andMulticast. [TBR-51] [SRD ID 44700]TBR-47 - We accept the value as is in the baseline.Recommend TBR closure after ATP.TBR-48 - We accept the value as is in the baseline.Recommend TBR closure after ATP.TBR-49, TBR-50, TBR-51 - We accept the value as is inthe baseline. Recommend TBR closure after ATP.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-100

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Requirement Text Containing TBXTBX ResolutionThe SBM DMZ to SBM interfaces shall accept various files and streaming TBR-52, TBR-53, TBR-54 - We accept the value as is inproducts from the SBM DMZ using standard internet protocols that include but not the baseline. Recommend TBR closure after ATP.limited to Encapsulated Security Payload (ESP), Secure Shell (SSH), Simple MailTransfer Protocol (SMTP), Simple Mail Transfer Protocol Secure Sockets Layer(SMTP SSL) Domain Name Server (DNS), Hyper Text Transfer Protocol (HTTP),Hyper Text Transfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), FileTransfer Protocol over Secure Sockets Layer (FTPS), SSH File Transfer Protocol(SFTP), Message Hopper [TBR-52], MSCHAT [TBR-53], Power Publisher,TACACS, NTP, SNMP Traps, SYS Log, and Multicast. [TBR-54] [SRD ID 45000]The RBM to End User Interface shall allow the RBM to deliver various files and TBR-55, TBR-56 - We accept the value as is in thestreaming products to end users using standard internet protocols that include, baseline. Recommend TBR closure after ATP.but are not limited to: Hyper Text Transfer Protocol (HTTP), Hyper Text TransferProtocol Secure (HTTPS), File Transfer Protocol (FTP), File Transfer Protocolover Secure Sockets Layer (FTPS), SSH File Transfer Protocol (SFTP) [TBR-55],Real-Time Transport Protocol (RTP), Internet Group Management Protocol(IGMP), Session Description Protocol (SDP), Trivial File Transfer Protocol(TFTP), and Multicast. [TBR-56] [SRD ID 47000]A Broadcast Receive Suite – Terrestrial (BRS-T) shall be comprised of any GBSReceive Suite suitably modified to include the necessary transmit capability tosupport a wireless terrestrial network extension of the broadcast to twenty ormore nearby (within 5-miles distance line-of-sight) locations [TBR-57]. [SRD ID61500]TBR-57 - We accept the value as is in the baseline.Recommend TBR closure after ATP.The SBM software shall respond to information provider or InformationTBR-58 - We accept the value as is in the baseline.Dissemination Management (and successor programs, to the extent implemented Recommend TBR closure after ATP.in Block-2) requests for statistics on the broadcast of individual products, orgroups of products, by source over configurable time intervals [TBR-58]. [SRD ID62501]The SBM software shall respond to information provider or InformationDissemination Management (and successor programs, to the extent implementedin Block-2) requests for statistics on the reception of individual products, orgroups of products, by receive suites over configurable time intervals [TBR-59].[SRD ID 62502]TBR-59 - We accept the value as is in the baseline.Recommend TBR closure after ATP.Figure 5.3-1. Contractor Filled-In TBRs, TBDs, TBSs. We recommend closure of all but two of the TBRs, TBDs, TBSs inthe SRD at ATP.5.3.1 SYSTEM REQUIREMENTS DOCUMENT (SRD)30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-101

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3System Requirements DocumentFor The Global Broadcast Service (GBS) Program:SBM to DECC TransitionRevision 3.0.18March 30, 2009Cage Code 3VQB0Solicitation No: FA8726-08-R-0001Contract No: FA8726-09-C-0006Prepared for:Contracting OfficerESCG/KCK5 Eglin StreetHanscom AFB, MA 01731-1620Prepared by:Lockheed Martin CorporationInformation Systems & Global Services (IS&GS)700 North Frederick AvenueGaithersburg MD 20879Approved By: ______________________________GBS Chief Engineer______________________________GBS Program Manager,MILSATCOM Joint Program Office30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-102

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Table of Contents1 SRD OVERVIEW .......................................................................................................................... 1061.1 Scope ...................................................................................................................................... 1061.2 PDM IV Background ........................................................................................................... 1061.3 CONOPS Background ......................................................................................................... 1061.4 System Overview ................................................................................................................. 1061.4.1 Broadcast Segment: .......................................................................................................... 1081.4.2 Space Segment: ................................................................................................................. 1101.4.3 Receive Segment: .............................................................................................................. 1101.5 Document Overview ........................................................................................................... 1111.6 Precedence............................................................................................................................. 1111.7 System Classification ........................................................................................................... 1111.8 ORD III Background ............................................................................................................ 1122 APPLICABLE DOCUMENTS .................................................................................................... 1132.1 Government Documents ..................................................................................................... 1132.2 Non-Government Documents ............................................................................................ 1142.3 Reference Documents .......................................................................................................... 1143 REQUIREMENTS ......................................................................................................................... 1153.1 Definition............................................................................................................................... 1153.1.1 System Description .......................................................................................................... 1153.1.2 System Segments or Elements ........................................................................................ 1173.1.3 Top-Level System Functions .......................................................................................... 1173.1.4 System States and Modes ................................................................................................ 1173.1.5 Operational and Support Concept ................................................................................ 1183.1.6 System Threats ................................................................................................................. 1183.1.6.1 Threats to Be Countered ......................................................................................... 1183.1.6.2 Information Operations........................................................................................... 1183.1.6.3 Electronic Warfare ................................................................................................... 1183.1.6.4 Computer Network Operations ............................................................................. 1193.1.6.5 Physical Destruction ................................................................................................ 1193.1.7 Key Performance Parameters ......................................................................................... 1203.2 Characteristics ...................................................................................................................... 1203.2.1 Performance Characteristics: Broadcast Segment ...................................................... 1203.2.1.1 Broadcast Delivery Activities (BDA)..................................................................... 1203.2.1.2 Operations Management Activity ......................................................................... 1273.2.1.3 Content Management Activity ............................................................................... 1303.2.1.4 Content Provider Activity ...................................................................................... 1303.2.1.5 DECC Broadcast Segment Architecture and Infrastructure .............................. 1313.2.2 Performance Characteristics: Receive Segment .......................................................... 1323.2.2.1 Receive Delivery Activities ..................................................................................... 1323.2.2.2 Broadcast Reception Management Activities ...................................................... 1363.2.3 Physical Characteristics ................................................................................................... 1373.2.3.1 Broadcast Segment ................................................................................................... 13730 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-103

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.2.4 External Interface Requirements .................................................................................... 1373.2.4.1 Broadcast Segment Interfaces ................................................................................. 1373.2.4.2 Receive Segment Interfaces .................................................................................... 1383.2.5 Internal Interfaces ............................................................................................................ 1393.2.6 Interface: Test Equipment ............................................................................................... 1393.2.7 Interface: Common Interfaces and Services ................................................................ 1393.2.8 Intelligence ........................................................................................................................ 1393.2.9 Command, Control, and Communications .................................................................. 1393.2.10 System Quality Factors ................................................................................................ 1393.2.10.1 Reliability .............................................................................................................. 1393.2.10.2 Maintainability ..................................................................................................... 1393.2.10.3 Operational Availability ..................................................................................... 1403.2.11 Environmental Conditions ......................................................................................... 1403.2.12 Transportability ............................................................................................................ 1403.3 Design and Construction .................................................................................................... 1413.3.1 Selection of Specifications and Standards .................................................................... 1413.3.2 Electrical ............................................................................................................................ 1413.3.2.1 Power ......................................................................................................................... 1413.3.2.2 Electromagnetic Radiation Compatibility (EMC) ............................................... 1413.3.2.3 Electrostatic Discharge (ESD)................................................................................. 1413.3.3 Mechanical ........................................................................................................................ 1413.3.4 Parts, Materials, and Processes (PM&P)....................................................................... 1413.3.5 Interchangeability and Replacement ............................................................................. 1413.3.6 Identification & Marking ................................................................................................ 1413.3.7 Workmanship ................................................................................................................... 1413.3.8 Human Engineering ........................................................................................................ 1413.3.9 Software Engineering ...................................................................................................... 1423.3.9.1 Commercial and Government-off-the-Shelf Software. ....................................... 1423.3.9.2 Design and Development ....................................................................................... 1423.3.9.3 Database Management Systems ............................................................................ 1423.3.10 Computer Resources.................................................................................................... 1423.3.11 Safety .............................................................................................................................. 1423.3.12 Security .......................................................................................................................... 1433.4 Logistics ................................................................................................................................. 1443.5 Personnel and Training ....................................................................................................... 1443.5.1 Broadcast Segment Manning and Training .................................................................. 1443.5.2 Receive Segment Manning and Training ..................................................................... 1443.5.3 GBS System Training ....................................................................................................... 1443.6 Pre-Planned Product Improvements (P3I) ....................................................................... 1453.6.1 2-Way Transmit Receive Suites ...................................................................................... 1453.6.2 Enhanced Source Integration ......................................................................................... 1463.6.3 Ground Mobile Receive Suite ......................................................................................... 1463.6.4 Broadcast Receive Suite – Terrestrial Extension .......................................................... 1473.6.5 Enhanced GIG Network-Ops ......................................................................................... 14730 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-104

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.6.6 Broadcast Metrics Software Development ................................................................... 1483.7 Documentation ..................................................................................................................... 1484 VERIFICATION AND QUALITY ASSURANCE PROVISIONS .......................................... 1494.1 System Verification .............................................................................................................. 1494.2 Verification Methods ........................................................................................................... 1494.2.1 Demonstration .................................................................................................................. 1494.2.2 Test ..................................................................................................................................... 1494.2.3 Analysis ............................................................................................................................. 1494.2.4 Examination/Inspection ................................................................................................. 1494.2.5 Qualification by Similarity.............................................................................................. 1494.3 Verification Matrix ............................................................................................................... 1504.4 Quality Assurance Provisions ............................................................................................ 1704.4.1 Quality Assurance ............................................................................................................ 1704.4.2 Records .............................................................................................................................. 1705 PREPARATION FOR DELIVERY ............................................................................................. 1715.1 Preservation and Packaging ............................................................................................... 1716 NOTES ........................................................................................................................................... 1716.1 Acronyms and Abbreviations ............................................................................................ 1716.2 Terms and Definitions ......................................................................................................... 1767 APPENDIX A: SRD to ORD Requirements Trace (Child-to-Parent)................................... 184Table of FiguresFigure 1: GBS Phase II DECC Architecture ..................................................................................... 107Figure 2: Broadcast Segment Detail .................................................................................................. 109Figure 3: JIPM-R Baseline Receive Segment Configuration ......................................................... 110Figure 4: GBS Operational Activity View ........................................................................................ 115Figure 5: Multicast Address Assignments....................................................................................... 121Figure 6: GBS Two-Way Upgrade Kit Architecture ....................................................................... 146Figure 7: GBS Wireless Extension Architecture .............................................................................. 147List of TablesTable 1: Compliance Documents ...................................................................................................... 113Table 2: Non-Government Compliance Documents ...................................................................... 114Table 3: GBS Delivery and Management Activities ....................................................................... 116Table 4: Broadcast Delivery Service ................................................................................................. 121BDA File-Based Services ..................................................................................................................... 122Table 5: Personnel Skill Levels .......................................................................................................... 14430 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-105

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 31 SRD OVERVIEW1.1 ScopeThis document is the Global Broadcast Service (GBS) System Requirements Document (SRD). It providesguidance for the GBS Phase II System functional and performance requirements for the "Defense EnterpriseComputing Center (DECC) Architecture" to be implemented in 2008 and beyond. It will be used to establish acontractual baseline requirements document. Each requirement has been identified with a unique number that willbe used to track the requirement through the GBS Program lifecycle. As the GBS program transitions operationsfrom the IP Enhanced Architecture (EA) at the NCTAMS (located at Wahiawa, Hawaii and Norfolk, Virginia) tothe DECC there will be two relevant program SRDs, the IP EA SRD version 2.1, dated March 2005 and thisdocument for the DECC Architecture.1.2 PDM IV BackgroundOn 13 December 2006, the Deputy Secretary of Defense England approved Program Decision Memorandum(PDM) IV. This document directed the Air Force to:1) Transfer the Satellite Broadcast Manager (SBM) functions to DECC with new hardware and softwarearchitecture by FY 2010;2) Implement system transmission security (TRANSEC) via the Joint IP Modem (JIPM);3) Provide operations, maintenance, and sustainment for the GBS program throughout the life of GBS.This SRD addresses items (1) SBM transition to the DECC, (2) JIPM implementation, and Maintenance, andSustainment of the system from item (3). Operations of the DECC system will be addressed in an update of theCONOPS.1.3 CONOPS BackgroundA new version of the GBS CONOPS for the IP EA system was approved on 21 June 2007, which will supersedesthe 24 January 1996 CONOPS. The CONOPS will be updated again to reflect the DECC Architecture andoperations.1.4 System OverviewJoint tactical operations require high speed, high volume multimedia communications and information flow fordeploying, deployed and garrisoned forces. The GBS system employs emerging technologies that allow thewarfighter to satisfy these information requirements in the conduct of modern warfare. An extension of the GlobalInformation Grid (GIG), GBS provides worldwide, space based, IP over DVB-S/S2, broadcast of high speed, onewaytransmission of video, imagery and other information to support forces in garrison, in transit and in theater.GBS provides relief to overburdened communications systems already in place and provides information topreviously unsupportable users. The GBS must be accessible to end users and must therefore employ readilyavailable commercial technologies, which are inexpensive and easily integrated into existing systems andprocesses, yet not so unwieldy as to be unusable by smaller and more mobile units. To this end, GBS usesbroadcast payloads on a variety of Government owned and operated geosynchronous satellites, augmented byleased commercial satellite services, and a system of fixed and transportable injection terminals interconnectedvia high-bandwidth terrestrial communications links.The GBS system consists of three physical segments: Broadcast, Space, and Receive. The associated systemarchitecture is shown in Figure 1.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-106

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3TheaterInformationMangersGBS OperationsManagerBROADCAST SEGMENT SPACE SEGMENT RECEIVESEGMENTDISN COREDECC SBMDefense EnterpriseComputing Centers(DECC)UFOPIPsJoint IP Modem HubJoint IP Modem(JIPM)/TRANSECDynamic AllocationBandwidth EfficiencyTIPUFO / CommercialWGS / CommercialJoint IPModemIP ReceiveBroadcast Mgr.IP ReceiveBroadcast Mgr.RBMRBMCNPSGlobal/RegionalSATCOMSupportCentersSourcesSITLTeleportJoint IPModemRBMRBMTacticalNetworksBACKUP CONTINUITYOF OPERATIONS(COOP) SITEDECC SBMCOOP SiteJoint IPModemHubAutomated Management InterfacesData FlowWideband GlobalSatcom (WGS)/X &Ka BandCOMSAT Ku-BandUHF Follow-OnGBS Receive SuiteJoint IP ModemTRANSECFigure 1: GBS Phase II DECC ArchitectureGBS is not a typical SATCOM system. Its flexible design takes advantage of multiple SATCOM systems – bothDoD developed and commercial. Two Ultra High Frequency Follow-on Satellite (UFO) GBS payloads operatingin the military Ka band provide the core service, multiple commercial Ku payloads also deliver service to endusers. New customers are expected as GBS will soon uplink through DoD Teleports at both X and Ka band to theWideband Global SATCOM (WGS) satellites when they are on orbit – thus taking advantage of the WGS crossbandingcapability to deliver even more broadcast information. In addition, with the incorporation of inexpensivecommercial equipment into the GBS Receive Broadcast Manager (RBM), virtually any military terminal with thenew DoD standard L-band Intermediate Frequency capability can also receive the broadcast.This SATCOM data transport flexibility is combined with a Network Centric Internet Protocol (IP) design to takefull advantage of the DoD’s transponded SATCOM resources to deliver broadband products from data storesthroughout the Global Information Grid (GIG) to deployed end users who would otherwise not have thebandwidth to receive such products.A fundamental feature of GBS is the System Delivery and Management Activities (SDMA) with functionsresponsive to Combatant Commander inputs. The SDMA will accept, coordinate, and package (if required),information (general broadcast products, smart push products, user pull products) from national and theatersources to be broadcast based on the direction and priorities of the supported Combatant Commanders, othercommanders, and their functional users. The SDMA also includes the functions necessary to support the efficientuse of GBS. These functions include, but are not limited to: capacity sharing, providing interface protocols andstandards to allow information producers to submit information in a form acceptable by the GBS broadcast,coordination with the Theater Information Management (TIMs) cells to apply Combatant Commanderdissemination priorities to information destined for broadcast in their respective Area of Responsibility (AOR),and coordination with TIMs and information producers to attempt to satisfy users requests forwarded by the TIMand unable to be satisfied by other means. GBS relies on the Defense Information Systems Network (DISN)connectivity to relay information from national and theater information sources to the DECC SBM and from theDECC SBM to the Teleports and UFO Primary Injection Points (PIP) for broadcast injection.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-107

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The SDMA will include the delivery and management functions for both the Broadcast and Receive segments.The broadcast functions will manage the flow of information from sources to the appropriate injection point fortransmission to the satellite. The receive function will support the filtering of user determined relevantinformation from broadcast streams and the transport of the received information from receive suites to end users’servers or dissemination applications.A key function of GBS is both “Smart-Push” and “User-Pull” to provide warfighter information. Smart-Pushgives the users the majority of their predictable information needs resulting from deliberate planning. User-Pullsupports ad hoc on-demand requests to give authorized users direct responsive access to information. Using GBSin concert with other existing communications means, virtual two-way networks can be created for interaction.Requested information is provided through network centric systems to users using GBS when appropriate. GBSshares and reallocates available bandwidth between various users, information products, multimedia types, andsecurity releasability levels, without interruption to the broadcast. The broadcast content is prioritized to meet thetimeliness requirements of each product when taken in aggregate, within the constraints imposed on the broadcastby information product availability, the Combatant Commander’s dissemination policy, the user needs, and theinformation priorities.GBS is essentially a one-to-many (hub-to-spoke) communications capability (a broadcast); however, use ofmultiple broadcasts is permitted using deployed theater injection equipment with an understanding that multipleone-to-many broadcast may require reallocating satellite resources between multiple broadcasts or may requireusers to select the most applicable broadcast(s) injection to receive or require multiple RBMs to be employed toaccess multiple simultaneous broadcasts. The prescribed method to deliver information products for broadcast isby information providers and users funding product integration and DISN connectivity. Direct connections to thebroadcast centers and their associated dedicated equipment are to be avoided.GBS is designed to give users, below headquarters level, information from a high data rate broadcast system. TheGBS RBMs is not intended to be a stand-alone system, and will not host user applications for manipulation ofreceived information. GBS will receive the broadcast signal, de-multiplex it, decrypt it, if required, and route it touser-supplied equipment and systems for viewing and manipulation.Using Combatant Commander or TIM guidance and priorities, the SBM will combine validated user profiles tocreate the GBS broadcast then send it to the Injection Point for transmission. In addition, the SBM fills "ad hoc"user requests on an as available basis. The SBM evaluates "Smart Push" products to ensure their priority,bandwidth, and spot beam requirements fall within Combatant Commander priorities and allocated resources. TheSBM creates both an unclassified and a classified (containing more detail) electronic program guide (EPG) so thatusers receiving the broadcast can easily determine what, when, and where information will be or has beenbroadcasted. The program guide will be available to all users via GBS and also media other than the GBSbroadcast. This allows users not located within a GBS spot beam to determine when they can expect GBS serviceand when requested information might be delivered. The SBM will be connected to the DISN as the means forgiving all information providers’ access to GBS.The Theater Injection Point (TIP) combines the functions of an SBM and Injection Terminal on a smaller scale.The TIP will be used to develop, build, and inject theater-produced information directly to the satellite forbroadcast to forces, within a specific region. Use of a TIP must be coordinated with the SBM and approved by theaffected Combatant Commanders TIM.1.4.1 Broadcast Segment:The Broadcast Segment includes a primary Satellite Broadcast Manager (SBM) and a Continuity of Operations(COOP) SBM, both located at Defense Enterprise Computing Centers (DECC); Theater Injection Points (TIP),which includes the TSBM and TTI; Information Sources; Information Managers; and Injection Terminal(s), bothfixed and transportable. Both the primary SBM and the COOP SBM are capable of independently supporting theglobal broadcast. For broadcast originating at a SBM, the Theater Information Manager (TIM) controls the flowof data and streaming products from Sources into the SBM for inclusion in broadcasts which are routed across theDISN Core to Teleports and UFO Primary Injection Points (PIP) for transmission. For broadcast originating at the30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-108

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3TIP, the Information Managers work with the TIP operators to incorporate source products into a broadcast to betransmitted over an appropriate tactical terminal.For integration and testing purposes, a System Integration and Test Lab (SITL) will be created by the contractor.The SITL will host a mock-up of SBMs with enough equipment for at least one security enclave and the neededtest equipment to simulate the transmission of product across the DISN, through an uplink facility, over a satellite,and received by the Receive Segment.All systems operations and management is controlled by the GBS operations managers through enclave specificweb interfaces. Through these interfaces, the operations managers will set the guidelines for the bandwidthmanagement between enclaves and within the individual enclaves themselves. Each enclave will produce a set offlow controlled multicast streams that will converge into an IP connection prior to linking to a Teleport or PIPacross the DISN Core. Within the Teleport, the multicast strings will be encapsulated and modulated within theJoint IP Modem hub. GBS specific end user requirements will be submitted by the Information Manger to theTheater Network Controller (TNC). In support of the system threshold requirement to dynamically managebandwidth between enclaves, a one-way cross-domain connection from the JIPM hub to each enclave will be usedto manage the real time flow of data products between the enclaves and the JIPM Hub. A representation of thisinformation flow is shown below in Figure 2.DECCTIMTELEPORTSourcesTIM & GBSOperationsManagerDMZSecret EnclaveVideo EncoderApproved CrossDomain FeedbackRxRokus Enclave}BroadcastControl &Setup managedby BCMSTNCJMOSControl & ManagementEncrypted IP MulticastSourcesTIM & GBSOperationsManagerSourcesTIM &OperationsManagerDMZDMZVideo EncoderApproved CrossDomain FeedbackRxUnclassified EnclaveVideo EncoderApproved CrossDomain FeedbackRx}BroadcastControl &Setup managedby BCMS}BroadcastControl &Setup managedby BCMSEncryptedIP MulticastFIPS EncryptedIP MulticastDISN CoreIP MulticastSMPTE-325MFeedbackAutomated Management InterfacesData FlowEncapsulatorModulatorPart ofJIPM HUBSATUPLINKFigure 2: Broadcast Segment DetailAs shown in Figure 2, the operations manager will control each security enclave individually through a webinterface within each enclave (i.e., one each for Secret, ROKUS, and Unclassified). This web interface will allowenclave access through the site DMZ (see section 6.2) allowing the operations manger to control the videoencoder and the Broadcast Control and Set-up. The broadcast control and set-up will be run by a single integratedBroadcast Content Management Software (BCMS) application. Each enclave will produce multicast streams thatwill flow across the DISN Core to satellite uplink facilities. At the uplink facilities, the JIPM Hub provides flowcontrol information to each SBM enclave via the SMPTE-325M, and into each enclave via an approved low-tohighcross-domain device, such as one-way fiber or data diode. The Teleport Program Office is responsible formaintaining and operating the JIPM Hubs.The BCMS will be a single integrated application and able to operate identically on multiple security enclaves.The BCMS must operate Fazzt 7.1 or equivalent software (key functionality of the software is described in30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-109

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Section 3, be installed at the DECCs and operate on a DECC approved OS (Linux, MS, UNIX, etc). The sameBCMS application that is loaded at that SBMs must also be able to operate the TIPs and be backwards compatiblewith the legacy receive suite software, i.e., receive files (unclass/class), streaming products (video, tunneled data,Power Publisher, etc), EPG displays, heartbeats, and web content, while supporting RBM presence displays andover-the-air updates. Additionally, the BCMS must take into account that with DVB-S2 Variable Coding andModulation (VCM) Multicasting, different RBMs can have different Receive Terminals of various sizes,receiving at different effective data rates.1.4.2 Space Segment:The Space Segment initially consists of the following elements: four uplink modulators per UFO satellite (UFO 8& 10), four equivalent GBS uplink modulators per WGS satellite, and leased commercial uplink modulators.1.4.3 Receive Segment:The Receive Segment consists of a Receive Broadcast Manager (RBM) and Receive Terminal e.g., the NextGeneration Receive Terminal (NGRT), the Shipboard Receive Terminal (SRT), the Sub Surface ReceiveTerminal (SSRT), the Airborne Receive Terminal (ART), or the Manpack Receive Terminal (MRT). Dataproducts are received over the air by the terminal and processed within the RBM for use by an RBM operator orpushed to a Local Area Network (LAN) for distribution to end users. The Receive Segment configuration, shownin Figure 3, is representative of the future system baseline with the JIPM Remote Modem (RM) installed,however other variations are possible.Figure 3: JIPM-R Baseline Receive Segment ConfigurationWith DVB-S2 Variable Coding and Modulation (VCM) Multicasting different RBMs may have different ReceiveTerminals of various sizes, receiving at different effective data rates. The Receive Segment hardware may beconfigured in a variety of ways with unique components making it imperative for the receive version of theBCMS software to be flexible and easily portable between configurations.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-110

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3A key component to the successful transition of GBS functionality from the NCTAMs based SBMs to the DECCArchitecture will be maintaining backwards compatibility. The DECC SBM broadcast must work with theexisting legacy IP RBMs and the Receive Content Management Software (RCMS) application developed for newRBM’s must work with the NCTAM’s SBMs. The legacy IP RBMs must be able to receive from the BCMSbroadcast: files (Unclassified or Classified), streaming products (video, tunneled data, Power Publisher, etc),Electronic Program Guides (EPG) displays, heartbeats, and web content, while supporting RBM presencedisplays at the DECC SBM and over-the-air updates provided by the legacy sustainment activity. The DECCArchitecture does not need to support auto tuning on the legacy RBMs.The flow of products within the RBM will be managed by a RCMS application. The RCMS must both be a singleintegrated application and able to operate identically on multiple security enclaves. The RCMS must be easilyinstalled on the RBMs, operate on an IA certifiable OS (Linux, MS, UNIX, etc), and be backwards compatiblewith the legacy broadcast software.1.5 Document OverviewThis document defines the GBS Phase II system requirements for the DECC Architecture. It is based on theapproved GBS Operational Requirements Document (JROCM 007-05), dated 12 January 2005 and ProgramDirection Memorandum (PDM) IV, signed by DepSECDEF England on 13 December 2006.1.6 PrecedenceFor the GBS Phase II DECC Architecture, the top-most requirements document is the GBS OperationsRequirement Document (ORD) III. The Block I, II, and III ORD requirements relevant to the PDM IV directedDECC transition are allocated and further requirements derived in this GBS SRD. This SRD does not address theTransportable Satellite Broadcast Manager (TSBM) hardware specifications, satellite uplink hardware, the spacesegment, or the full set of Receive Broadcast Managers and Receive Terminals requirements. A separaterequirements document is being developed to address the production of Receive Broadcast Managers and ReceiveTerminals. Additional requirements may be derived from the ORD and incorporated into this SRD as Pre-PlannedProgram Improvements (P3I) as direction and associated funding are provided by the Government.1.7 System ClassificationThe IA Classifications and Acquisition Category Classification are described in the GBS Systems EngineeringPlan (SEP).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-111

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 31.8 ORD III BackgroundOn 7 April 1997, the Joint Requirements Oversight Council (JROC) approved the Phase-2 requirements containedin Operational Requirements Document (ORD) I and validated the Phase-2 Key Performance Parameters (KPP).On 27 April 2000, JROC Memorandum (JROCM) 080-00 requested the Air Force prepare a limited scope update,in an expedited manner, to ORD I in the following four areas: incremental Initial Operational Capability (IOC),clarify required capabilities, update quantities, and Chairman, Joint Chiefs of Staff Instruction (CJCSI) 3170.01Acompliance. The JROC approved the limited scope update, ORD II, and validated the new Interoperability KPPon 23 May 2001. JROCM 080-00 also requested the vetting of three additional capabilities: protection duringtransmission of certain unclassified information, discretionary access control for enforcing repudiation of accessto broadcast information, and palletized vs. shelter theater injection points.Phase-3 requirements and KPPs were defined by the validated Satellite Communications (SATCOM) SystemsCapstone Requirements Document (CRD), 7 March 2003.The ORD III update includes Network Ready KPP (NR-KPP) compliance requisite to CJCSI 6212.01C, 20 Nov2003 and DODI 4630.8, 30 June 2004. The NR-KPP assesses information needs timelines, information assurance,joint interoperability and supportability. It also assesses the network-ready attributes required for both thetechnical exchange of information and end-to-end operations. The NR-KPP is comprised of: (1) SupportingArchitecture products, (2) Compliance with the Net Centric Operations and Warfare Reference Model (NCOWRM), (3) Compliance with the GIG Key Interface Profiles (KIP), and (4) Information Assurance (IA) policies andprocedures. NR-KPP compliance is described in Appendix-E to the ORD, Integrated Architecture Products.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-112

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 32 APPLICABLE DOCUMENTS2.1 Government DocumentsThe following documents in Tables 1 and 2 are applicable to the extent specified herein. In the event of conflict,this document will supersede all other referenced documents.Table 1: Compliance Documents1 CJCSI 3170.01 C, Joint Capabilities Integration and Development System2 CJCSI 6212.01D, Interoperability and Supportability of Information Technology and National SecuritySystems3 CJCSI 6250.01, Military Telecommunications Agreements and Arrangements Between the United Statesand Regional Defense Organizations or Friendly Foreign Nations, May 24, 20064 CJCSI 6510.01E, Information Assurance and Computer Network Defense, 15 August 20065 Department of Defense (DoD) Joint Technical Architecture (JTA), V. 4.0 17 July 20026 DISA CIRCULAR 310- 55- 1: OPERATIONS Status Reporting, 21 January 20007 DoD Directive 5000.1, Defense Acquisition System, May 12, 20038 DoD Instruction 4630.5, Interoperability and Supportability of Information Technology and NationalSecurity Systems, May 5, 20049 DoD Instruction 4630.8, Procedures for Interoperability and Supportability of Information Technology andNational Security Systems, June 30, 200410 DoD Instruction 5000.2, Operation of Defense Acquisition System, May 12, 200311 DoD Directive 8500.01E, Information Assurance, April 23, 200712 DoD Instruction 8500.2, Information Assurance Implementation, February 6, 200313 DoD Instruction 8510.bb, Department of Information Assurance Certification and Accreditation Process(DIACAP), 28 November 200714 GBS Information Support Plan (ISP), TBD15 GBS Interface Control Document (ICD), TBD16 GBS Operational Requirements Document III, January 12, 200517 GBS Systems Safety Management Plan, Version 1.0, dated 18 March 200818 GBS Programmatic Environmental, Safety, and Health Evaluation (PESHE), TBD19 Joint Integrated Logistics Support Plan (JILSP), April 3, 200620 Joint IP Modem, Performance Specification, July 2, 200721 Joint IP Modem Remote Modem Operators Manual, TBD22 Master UFO Link Budget23 Master WGS Link Budget24 MIL-HDBK-46855A, Human Engineering Program Process and Procedures, May 17, 199925 MIL-STD-1472F, Human Engineering, August 23, 199926 MIL-STD-1888-164A, Interoperability of SHF Satellite Communications Earth Terminals, 15 April 200227 Multiband Global Broadcast Service Shipboard Antenna System, SPAWAR-S-874, 18 August 199728 NSTISSP No 11, National Information Assurance Acquisition Policy, January 200029 NTISSP No. 1 dated 17 June 198530 Operational Safety, Suitability and Effectiveness (OSS&E) Implementation Plan and Report Rev. 2.0, dated18 March 2008; AFMCI-63-120131 PMW 146-S-003, Space Segment Specification for the Interim Global Broadcast Service, 27 February 199632 Secret and Below Interoperability (SABI) ASD/C3I letter, dated 20 March 1997.33 SMPTE-325M34 SPAWARSYSCOM Satellite Communications System, submarine high data rate (HDR) - SPAWAR-S-868, 9 February 199635 Wideband Gapfiller Satellite (WGS) Interface Control Document (ICD), MILSATCOM Joint ProgramOffice, 18 February 2000.36 Wideband Gapfiller Satellite (WGS) Program System Specification, SS80769-H00-001, Revision A, May,2001.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-113

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 32.2 Non-Government DocumentsTable 2: Non-Government Compliance Documents1 Digital Video Broadcasting (DVB); DVB specification for data broadcasting, ETSI Standard EN 301 192V1.2.1 (1999-06)2 Digital Video Broadcasting (DVB); Second generation framing structure, channel coding and modulationsystems for Broadcasting, Interactive Services, News Gathering and other broadband satellite applications,ETSI EN 302 3073 Digital Video Broadcasting (DVB); Framing structure, channel coding and modulation for 11/12 GHzsatellite services, ETSI Standard EN 300 421 V1.1.2 8(1997-08)4 Digital Video Broadcasting (DVB); A guideline for the use of DVB specifications and standards, ETSITechnical Report TR 101 200 V1.1.1 (1997-09)5 IPv6 QoS: RFC 2460 Internet Protocol, Version 6 Specification2.3 Reference DocumentsNot applicable.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-114

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33 REQUIREMENTS3.1 Definition3.1.1 System DescriptionThis section of the SRD integrates the overarching GBS system, broadcast segment, and receive segmentsrequirements into a specification for the GBS DECC Architecture. Within each segment, detailed functional andperformance requirements are associated with system delivery and management activities. The system deliveryand management activities are shown in Figure 4.BROADCAST SEGMENTSPACESEGMENTRECEIVE SEGMENTTroubleManagementSystem (TMS)GBSOperationsManagerDECC SBMSATCOMSupportCenters(SSC)DISN CORETheaterInformationMangers4351UplinkFacility6GBSRT2RBMEnd UserContentProviderFigure 4: GBS Operational Activity ViewnAutomated Management InterfacesData FlowExternal CoordinationSystem Deliver & Management ActivityThese activities represent the core functionality required for the GBS system to successfully complete its mission.The intended user/operators and functionalities associated with each activity are listed in Table 3.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-115

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Table 3: GBS Delivery and Management ActivitiesActivity User/Operator Function123456BroadcastDelivery Activity(BDA)Receive DeliveryActivity (RDA)OperationsManagementActivity (OMA)ContentManagementActivity (CMA)Content ProviderActivity (CPA)BroadcastReception Activity(BRA)DECC SBMRBM14th Air Force(SBMOperators)/Help DeskTheaterInformationManager (TIM)SourceEnd UserManage End-To-End Broadcast ServicesFile TransferContent CatalogFile Transfer with ManagementHeartbeatWeb CrawlSource Managed ContentMirrored File TransferVideoIP StreamingTuning GuidesElectronic Program GuidesOver-The-Air Software and IA UpdatesWork Flow ProcessesManage Broadcast Reception ServicesSupport RBMs with and without ReachbackPush Received Products to End User ComputerMan Help DeskSupport Key ManagementSupport Coordination with Sources, DAA, and Information ProvidersInputs & Maintains System ParametersSupport Coordination with Space Operators for Coverage & BandwidthSupport Coordination with TNC (Teleport, JIPM, DISN) for bandwidthManage trouble shooting to include Trouble Management System (TMS)Report GBS status to TNC, etc.View StatusMaps source content to RBMsPrioritize the BroadcastSupport Coordination with Sources, DAA, and Information ProvidersCoordinates with Ops Manager on System ParametersSupport Coordination with Space Operators for Coverage & BandwidthSupport Coordination with TNC (Teleport, JIPM, DISN) for bandwidthView StatusReceive Suite Remote Disable ManagementManage permissions / access to IFD Folders including validation of IFDAccountsManage and Approve COMSEC requests for Full Motion Video (FMV) streamsin the COCOM AOR.Manage DVB-RCS suite access to DVB-RCS channels.Support TSBM operations.Restricts Content Listings in Catalog (by exception)Describes contentView StatusDescribes RBM parametersUser Pull RequestRebroadcast RequestTuning GuidesView Status30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-116

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.1.2 System Segments or ElementsSystem segments previously described in paragraphs 1.4 and 3.1.1.3.1.3 Top-Level System FunctionsThis section provides general requirements that apply to the entire GBS system.The GBS System shall provide the core functionalities, contained herein this specification’s Table 3 (Column“Function”), to address the needs of the user/operator(s) designated for area. [SRD ID 10100]The GBS System will be in compliance with the DOD mandated Net-Ready Key Performance Parameters (KPP)requirements, to include:The GBS System shall be in compliance with DoD mandated Net-Ready Key Performance Parameters, includingsatisfying 100% of all the specified Joint integrated architecture requirements designated enterprise-level orcritical activity interfaces; services; policy-enforcement controls; data-sharing, data availability, data correctness,data processing and information assurance accreditation requirements in the Net-Centric Operations and WarfareReference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIP) (KPP). [SRD ID 10201] The GBSInformation Support Plan (ISP) provides additional information on NR-KPP compliance with respect to these fouraspects.The GBS System shall be in compliance with the DOD mandated Net-Ready Key Performance Parameters (KPP),including meeting GIG interoperability standards (CJCSI 3170.01C, CJCSI 6212.01D, DoDI 4630.5, and DoDI4630.8) for the interfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems. [SRD ID 10202]The GBS system shall satisfy 100 percent of the top-level Information Exchange Requirements (IER) designatedcritical to the standards specified in the IER Matrix, defined in the GBS Operational Requirements Document(KPP). [SRD ID 10300]The GBS system shall accommodate scaling, both up to 200% increases and up to 50% decreases, of thefollowing factors including but not limited to: satellites, antennas, uplink modulators, RBMs, security enclaves,broadcast load, total products, and number of each end-to-end service types. [SRD ID 10400]The GBS system shall be scalable, both up to 200% increases and up to 50% decreases, and capable to passmultiple and varied compartmented information sources. [SRD ID 10501]The GBS system shall be scalable, both up to 200% increases and up to 50% decreases, to provide information tothe user beyond the receive suite. [SRD ID 10502]The GBS System is part of the GIG and shall meet GIG interoperability standards for the interfaces, protocols,and equipment required to receive and disseminate video and data from existing systems (Threshold). [SRD ID10600]The GBS System shall provide a minimum of 90 percent statistical assurance of receipt of all broadcastinformation (measured from the point where the broadcast information is received in the SBM and delivered atthe interface between the RS’s RBM and the attached LAN). [SRD ID 10701]The GBS System shall provide a minimum 95 percent statistical assurance of receipt of all broadcast information(measured from the point where the broadcast information is received in the SBM and delivered at the interfacebetween the RS’s RBM and the attached LAN). [SRD ID 10702]The GBS system shall meet the Quasi-Error Free (QEF) condition under clear weather conditions, equivalent toless than one (1) uncorrected error event per transport stream hour (corresponds to a BER between 10 -10 and 10 -11 ). [SRD ID 10705]3.1.4 System States and ModesNot applicable.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-117

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.1.5 Operational and Support ConceptRefer to GBS Operational Concept Document (in draft)3.1.6 System ThreatsGBS threats are diverse and multi-national and include regional instability; proliferation of weapons of massdestruction; and trans-national dangers such as global terrorist groups and drug traffickers. From a tacticalperspective, theater commanders are challenged by regional factions seeking to expand their influence bycoercion or force. These potential opponents range from nations with modern conventional military forces,organized terrorists, and insurgent organizations to small bands of individuals armed with any weapon available.3.1.6.1 Threats to Be CounteredGBS is vulnerable to the same threats as most commercial satellite systems. Threats to the GBS system originatefrom a variety of sources and encompass capture of a GBS Receive Suite or attacks upon all physical nodes andelectronic links associated with the system. Various elements of Information Operations (IO), “traditional” threatsassociated with physical destruction of system components, and threats from conventional and nuclear weaponseffects are a possibility, as well as environmental aberrations. Because various intelligence studies indicate themost significant threats to MILSATCOM originate from the electronic warfare elements of IO, this ORDprimarily addresses requirements to mitigate or avoid those threats.3.1.6.2 Information OperationsIO encompasses actions taken to achieve information superiority by affecting adversary information andinformation systems while leveraging and protecting friendly information and information systems. With regardto GBS, the relevant portions of the IO threat stem from adversary Electronic Attack, Electronic Support,Computer Network Attack (CNA), Computer Network Exploitation (CNE), physical destruction, and radiofrequency weapons.3.1.6.3 Electronic WarfareThreats include jamming, interception, and exploitation, which result in degradation of commercial and militarycommunications links or the signal environment. The GBS uplink is vulnerable to nuisance electromagneticinterference (EMI) and jamming. Using a variety of techniques (e.g. steerable beam antennas, coding schemes,frequency hopping, etc.), these threats may be mitigated. Classified threat assessments related to satellitecommunications are contained in Interim Space Capstone Threat Capabilities Assessment, NAIC-1574-0727-03,July 2003, and the Military Satellite Communications (MILSATCOM) System Threat Assessment Report(STAR), NAIC-1574-0367-03-Chg 1, (July 2003), July 2003, (S/NF).3.1.6.3.1 Electronic AttackThe objective of electronic attack or electronic degradation is to deny or disrupt an opponent's use of theelectromagnetic spectrum. Defined as the deliberate or incidental radiation, re-radiation, or reflection ofelectromagnetic energy to degrade or neutralize military combat capability, electromagnetic jamming attacks areintended to disrupt, degrade, or deny use of the electronic spectrum. Jamming can be intentional or unintentional,fixed or transportable, and can vary in power. Interference and jamming of the GBS could disrupt usercommunications.3.1.6.3.2 Electronic SupportElectronic Support is that division of electronic warfare involving actions to search for, intercept, identify, andlocate sources of intentional and unintentional radiated electromagnetic energy for the purpose of immediatethreat recognition. Electronic support efforts against GBS beam locations could lead to detection of signals thatwould assist an enemy in locating friendly forces and could allow the interception of SATCOM signals forintelligence purposes.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-118

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.1.6.4 Computer Network OperationsComputer network warfare encompasses the elements of CNA, Computer Network Defense (CND), and CNE.CNA includes data deception or corruption, compromise of information, information denial or loss, and physicaldestruction or damage. CND includes efforts to ensure that friendly computer networks are adequately protectedfrom attack, intrusion, and exploitation. CNE is defined as obtaining information from computer networks.3.1.6.4.1 Computer Network Attack (CNA)Because MILSATCOM relies heavily on computer networks, attempts to degrade, disrupt, deceive, destroy, ordeny the functionality of those computer systems poses a significant threat to GBS mission accomplishment.Denial of Service or insertion of malicious software into friendly computer systems is a constant threat. Malicioussoftware and viruses can also attack processor-controlled transmission equipment, control systems, or theinformation being passed. "Hackers" using malicious software or viruses to manipulate network protocols anddeny, destroy, corrupt, modify, or compromise data, service, and software also pose a significant threat. Anadversary who successfully attacked a computer network upon which the GBS relied could substantially degradethe military’s combat effectiveness and civil functions.3.1.6.4.2 Computer Network Exploitation (CNE)CNE or “data mining” describes efforts to obtain information from computer networks. The vast amounts of datacontained within computer networks has changed the traditional spy paradigm of an individual painstakinglycopying classified data to that of a skilled computer operator transferring libraries of documents with a key stroke.3.1.6.5 Physical DestructionPhysical threats include the entire spectrum of direct and indirect weapons fire, chemical or biologicalcontamination and nuclear destruction. GBS equipment would also be vulnerable to capture if deployed withforward units. The threat of physical destruction will increase over the next decade. The threat is rising due toforeign nation’s growing awareness of the significance of communication links to the US military.3.1.6.5.1 Operational Threat EnvironmentThe operational threat environment can vary from the relatively benign environment of humanitarian missions tothe more stressed environments of Small Scale Contingency or Major Contingency Operation to the mostthreatening environment of global nuclear war.3.1.6.5.2 Physical Destruction Threats (Non-Nuclear)Threats against GBS include physical attack (to include capture or theft), terrorist activity, chemical andbiological warfare, and weapons fire. There is a threat from chemical weapons that cause corrosive damage tounprotected electronic components or degrade moisture barriers within the systems.3.1.6.5.3 Nuclear EffectsWith the proliferation of nuclear weapons and technology, the nuclear threat encompasses both theater andstrategic environments. Nuclear effects that could affect the GBS include interference, scintillation, blackout, andelectromagnetic pulse (EMP), as well as the direct effects of detonations such as blast, heat, and radiation.Scintillation, as a residual effect, could cause interruptions or total loss of the signal for some protracted amountof time (blackout) in signal transmissions from the GBS through absorption, attenuation, phase distortion, loss ofcoherence, and multi-path dispersion. A nuclear event can also cause electromagnetic upset or physicaldestruction of electronic components in the equipment because of gamma and X-ray radiation and EMP. TheEMP from a high altitude, atmospheric nuclear detonation produces a very large and sudden surge of current inelectronic equipment or circuitry. Nuclear events in the upper atmosphere pose a collateral tactical or strategicthreat.3.1.6.5.3.1 High Altitude Electromagnetic Pulse (HEMP)30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-119

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3HEMP is a specifically targeted event designated to produce disruption over a large geographic region inunprotected electronic support equipment, computer and communication devices, and the operation of thecommercial infrastructure and power grid. GBS does not require being a survivable or endurable system andtherefore will not be equipped with special HEMP or High-Altitude Nuclear Explosion (HANE) protection.3.1.6.5.3.2 Scintillation and BlackoutScintillation and blackout are effects that interfere with communications but last for a predictable time.Scintillation and blackout disrupt or delay communications but do not result in damage to components. Thespecific effects vary with proximity, yield, blast geometry, and altitude.3.1.6.5.4 Radio Frequency WeaponsGBS equipment could be vulnerable to radio frequency weapons, which could be used to physically destroy ordisrupt electronic circuits.3.1.7 Key Performance ParametersRefer to section 3.1.3.3.2 Characteristics3.2.1 Performance Characteristics: Broadcast SegmentThis paragraph provides requirements for the broadcast segment. The broadcast segment includes the hardwareand software required for DECC SBM, COOP SBM, SITL, the web interfaces for GBS Operators, ContentManagers, and Content Providers to operate the system, and the interfaces to the DISN and Satellite Uplinkfacilities.3.2.1.1 Broadcast Delivery Activities (BDA)Broadcast Delivery Activities (BDA) includes the unidirectional content delivery services intended to be used atthe DECC SBM, COOP SBM, and the functional/ operational users.The BDA shall use the uplink encapsulator(s) and modulator(s) at the Satellite uplink facilities (i.e., Teleports andPIPs). [SRD ID 11000] The JIPM Performance Specification provides descriptions of this equipment.The BDA shall support content broadcast to an RBM that is receiving from one, and up to six (6), uplinkmodulators. [SRD ID 11101]For all data services, the BDA shall use unique multicast addresses for each satellite downlink, as described inFigure 5. [SRD ID 11200]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-120

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Figure 5: Multicast Address AssignmentsThe BDA shall organize broadcast content as associated with each RBM receiver Terminal size (e.g. small,medium, large) and assign multicast addresses that are consistent with the DVB-S2 VCM capability of the JIPMHub. [SRD ID 11300]The BDA shall not allow transmission of content to the RBM system root (i.e., “ C:\”). [SRD ID 11400] This isto prevent inadvertent sending of content to the RBM root directory.The BDA shall provide a capability to automatically broadcast file-based content from sources as it arrives at theSBM. [SRD ID 11500]The BDA shall support the transmission of any size file up to 20 GB. [SRD ID 11600]The BDA shall provide the set of end-to-end broadcast services listed in Table 4. [SRD ID 11700] These servicesare the minimum required capabilities for the system.Table 4: Broadcast Delivery ServiceBroadcast Delivery ServicesFile Transfer ServiceWeb Crawl ServiceFile Transfer Service (FTS) withManagement ServiceSource Managed Tunneling ServiceMirrored FTS ServiceVideo ServiceIP Streaming ServiceDescriptionFiles injected to the uplink are queued for transmission to specific RBMsbased upon product priority and file size.Service that provides off-line viewing of specific web content.Files are injected to the uplink with specific delivery instructions. Productscan also be cancelled; reprioritized, sent with return receipt requested andprovided other information.Currently implemented using Fazzt Power Publisher product, the sourcemanaged service provides a mechanism for file content to be streamed intothe broadcast for delivery. It provides sources with control of the contentflow while allowing the SBM to manage bandwidth.The mirrored FTS service replicates a directory and its contents at the SBMto one or more RBMs.Provides an ability to accept various forms of video and process them tomeet mission requirements (e.g. transrate; transcode; encode).Provide packet delivery of either generic UDP streams or previouslyencrypted IP content over the broadcast.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-121

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3BDA File-Based ServicesAll file-based services (web crawl, FTS, etc.) will provide the following capabilities:All file-based services shall have a file-based error correction capability that allows files to be efficientlyreconstituted in of the even that there are missed packets. [SRD ID 11800]All file-based services shall have a queuing mechanism that can support prioritization between files andstill simultaneously service both large and small files of the same priority. [SRD ID 11900]All file-based services shall have a queuing scheme for scheduling the queuing of a product at a designatedtime based on CJCSI 6250.01 priority. [SRD ID 11901]. Requirements 11902 through 11905 address queuingdelay requirements and do not address prioritization of files within a queue, only the delay associated with thetransmission of the files within a files size range.All file-based services shall have a queuing scheme that provides prioritization between files and allocationof available bandwidth among file types of different sizes. [SRD ID 11902]All file-based services shall have a queuing delay (time for a unique, recently arrived file to begintransmission assuming no other similar sized files are currently in queue), for files sizes less than 1 MB, ofnot more than 1.0 seconds. [SRD ID 11903]All file-based services shall have a queuing delay, for a file of 100 MB or less, of not more than 5.0 seconds.[SRD ID 11904]All file-based services shall have a queuing delay, for a file of 2 GB or less, of not more than 10 seconds.[SRD ID 11905]All file-based services shall be available in every security enclave. [SRD ID 11906]All file-based services shall address content to one, many, or all RBMs. [SRD ID 11907]3.2.1.1.1 BDA FTS ServiceThe following requirements apply only to the FTS Service:The FTS Service shall provide immediate file-based content delivery. [SRD ID 12000] “Immediate”, in thiscontext, means within the queuing delay identified in 0The FTS Service, within an enclave, shall be capable of receiving and processing source products that are injectedfrom sources via FTP or equivalent. [SRD ID 12100]3.2.1.1.2 BDA Web Crawl ServicesThe following requirements apply only to the Web Crawling Service:The Web Crawl Services shall accept scheduling information to collect web site content on a scheduled basis.[SRD ID 12200]The Web Crawl Services shall provide the ability to crawl web site traffic to a specified crawl depth. [SRD ID12300]The Web Crawl Services shall provide controls to prevent excessive collection of web content, including, at aminimum, the ability to limit the size of the web crawl; the ability to control whether the crawler will traverselinks that are off-server relative the root URL. [SRD ID 12400]The Web Crawl Services shall provide the capability to pass PKI client certificates in response to a challenge by aweb server. [SRD ID 12500]The Web Crawl Services shall provide the ability to collect HTTP and HTTPS. [SRD ID 12600]The Web Crawl Services shall ensure that collected content can be viewed organically (using existing RBMsoftware) on the RBM without the need to repopulate a web server. [SRD ID 12700]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-122

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The Web Crawl Services shall implement techniques to minimize impacts to crawled web servers (e.g., complywith robots.txt). [SRD ID 12800]3.2.1.1.3 BDA FTS with Management ServiceThe following requirements apply only to FTS with Management Service:The FTS with Management Service shall provide a web services based interface for injecting content into thebroadcast. [SRD ID 12900]The FTS with Management Service shall provide transmission status for individual products including feedbackon RBM reception if available. [SRD ID 13000]The FTS with Management Service shall provide sources the ability to access the functionality to canceltransmission of products not yet broadcast. [SRD ID 13101]The FTS with Management Service shall provide sources the ability to access the functionality to delete productsfrom the system not yet broadcast. [SRD ID 13102]The FTS with Management Service shall provide sources the ability to access the functionality to estimatetransmission time for a product. [SRD ID 13103]The FTS with Management Service shall provide sources the ability to access the functionality to re-transmitsource products. [SRD ID 13104]The FTS with Management Service shall provide sources the ability to access the functionality to request a returnreceipt (as available) from fully connected receive suites. [SRD ID 13105]The FTS with Management Service shall provide sources the ability to access the functionality that provides thelist of authorized receive suites available to the source. [SRD ID 13106]3.2.1.1.4 BDA Source Managed Tunneled Content ServiceThe following requirements apply only to Source Managed Tunneled Content Service:The Source Managed Tunneled Content Service shall provide the ability to route source streaming contentdirectly into the broadcast stream without any additional processing. [SRD ID 13200]The Source Managed Tunneled Content Service shall provide local (within the BDA) bandwidth managementcontrol that can restrict the amount of bandwidth a specific source receives to be commensurate with the COCOMTIM priorities and bandwidth limitations placed on source. [SRD ID 13300]The Source Managed Tunneled Content Service shall be backwards compatible with existing source managedusers that currently use Fazzt Power Publisher 7.1 or provide a functionally similar application for these sources.[SRD ID 13400]3.2.1.1.5 BDA Mirrored FTS ServiceThe following requirements apply only to the Mirrored FTS Service:The Mirrored FTS Services shall provide a capability to replicate all content of a directory including all subdirectoriesand their content at the SBM to the RBM. [SRD ID 13500]The Mirrored FTS Services, after the initial directory content is broadcast and replicated, shall provide thecapability to only broadcast incremental changes in the SBM directory. [SRD ID 13600]The Mirrored FTS Services shall provide a capability to select the periodicity of the incremental updates. [SRDID 13700]BDA Video Services30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-123

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The following requirements apply only to the Video Service: Current channels run from 1.2Mbps to 3Mbps at thehigh end. The government anticipates the addition of 1-2 HD videos by the time of contract award at a rate of16Mbps.The Video Services shall have the capability to ingest MPEG-2 or MPEG-4 H.264 encoded video streams andrebroadcast the streams as a different multicast address using the same encoding algorithm. [SRD ID 13800]The Video Services shall be capable of transcoding videos from one format to another, specifically supporting at aminimum, the conversion from MPEG-2 to MPEG-4 H.264, MPEG-2 over ATM to MPEG-2 over IP, andMPEG-2 over ATM to MPEG-4 over IP. [SRD ID 13900]The Video Services shall be capable of transrating videos from one encoding rate to another. [SRD ID 14000]The Video Services shall be capable of converting video stream resolutions, specifically at a minimum, theconversion from MPEG-2 HD to MPEG-2 SD and MPEG-4 H.264 HD to MPEG-4 H.264 SD. [SRD ID 14100]The Video Services shall be capable of transmitting metadata in pre-encoded streams, if present (e.g. ClosedCaptioning Line 21, KLV). [SRD ID 14200]The Video Services shall be capable of encoding native analog or digital streams and any associated metadata asMPEG-2 SD, MPEG-2 HD, MPEG-4 H.264 SD or MPEG-4 H.264 HD formatted video. [SRD ID 14300]The Video Services shall be able to simultaneously encode at least 10 analog video streams and be capable ofscaling to encode 25 analog video streams. [SRD ID 14400]The Video Services shall have the capability to simultaneously support three modes of video operations:Transcoding/Transrating, Remapping, and Encoding. [SRD ID 14500]The Video Services, at a minimum, shall simultaneously transcode/transrate eighteen (18) videos: 10 videos forthe Secret enclave and 4 videos each for Unclassified and ROKUS enclave. [SRD ID 14510]The Video Services, at a minimum, shall simultaneously transcode/transrate thirty-six (36) videos: 20 videos forthe Secret enclave and 8 videos each for Unclassified and ROKUS. [SRD ID 14511]The Video Services, at a minimum, shall simultaneously remap one hundred (100) videos:Secret enclave, 14 videos for Unclassified and 6 videos for ROKUS. [SRD ID 14520]80 videos for theThe Video Services, at a minimum, shall simultaneously remap two hundred (200) videos: 160 videos for theSecret enclave, 28 videos for Unclassified and 12 videos for ROKUS. [SRD ID 14521]The Video Services, at a minimum, shall simultaneously encode eighteen (18) videos: 10 videos for theUnclassified enclave and 4 videos each for Secret and ROKUS. [SRD ID 14530]The Video Services shall simultaneously encode thirty-six (36) videos: 20 videos for the Unclassified enclaveand 8 videos each for Secret and ROKUS. [SRD ID 14531]The Video Services shall support use of the same multicast addresses for two or more satellite downlinks. [SRDID 14600]3.2.1.1.6 BDA Streaming Packet ServiceThe following requirements apply only to the Streaming Packet Service:The Streaming Packet Service shall support the processing of IP multicast data streams at data rates up to 20Mbps each. [SRD ID 14700]The Streaming Packet Service shall support the passing of previously encrypted IP data at levels up to andincluding TS/SCI. [SRD ID 14800]The Streaming Packet Service shall accept Encapsulated Security Payload (ESP) packets from a source and beable to route them over the broadcast. [SRD ID 14900]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-124

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.2.1.1.7 EPG Function:The following requirements apply only to the Electronic Program Guide (EPG):The EPG shall provide three days of broadcast history, specific to each individual receive suite that will allow theRBMs to determine what broadcast content that was intended for them was not received. [SRD ID 15000]The EPG shall provide a listing of all GBS broadcast videos and relevant reception information such as multicastIP addresses, port numbers, etc. [SRD ID 15100]The EPG shall be provided for each enclave and be available over-the-air and via the appropriate networkconnection. [SRD ID 15200]The EPG shall provide a web announcements page that allows GBS operations managers and TIMs to providedaily GBS updates. [SRD ID 15300]3.2.1.1.8 Heartbeat FunctionThe following requirements apply only to the Heartbeat:The Heartbeat shall provide a unique identifier on each broadcast stream to identify the associated satellite anduplink modulator. [SRD ID 15400]The Heartbeat shall include a free form text message capability of at least 256 full characters that is displayed as abanner upon reception. [SRD ID 15500]The Heartbeat shall use reports received from RBMs as the primary means for determining which RBMs areactive and which satellite uplink modulator(s) are being received by each RBM. [SRD ID 15600]3.2.1.1.9 Tuning Guide FunctionThe following requirements apply only to the Tuning Guide:The Tuning Guide shall include all necessary information required to tune each GBS RBM to the appropriatesatellite and begin reception of products. [SRD ID 15700]The Tuning Guide shall be Unclassified. [SRD ID 15801]The Tuning Guide shall be provided for each enclave. [SRD ID 15802]The Tuning Guide shall be available over-the-air and via all network connections. [SRD ID 15803]The Tuning Guide shall allow the SBM Operator to update the NIPRNET Tuning Guide within 5 minutes afterbeing notified of JIPM updates by the Tactical Network Controller (TNC). [SRD ID 15900]The Tuning Guide shall allow the SBM Operator to update the SIPRNET and ROKUS Tuning Guide within 2hours of being notified of JIPM updates by the TNC. [SRD ID 16000]The Tuning Guide shall include all scheduled changes to the tuning plan. [SRD ID 16100]3.2.1.1.10 Content Catalog FunctionThe following requirements apply only to the Content Catalog:The Content Catalog shall include a list of enclave specific authorized content and their descriptions that areavailable for “user pull” from the SBM. [SRD ID 16200]The Content Catalog shall be able to display the SBM Content Catalog over the applicable DISN network andallow selection and indications of the relative priority of products for delivery to selected RBMs. [SRD ID 16300]3.2.1.1.11 Work Flow Process FunctionThe following requirements apply only to the Work Flow Process:30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-125

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The Work Flow Process shall provide access controls that prevent unauthorized users from creating, modifying,or deleting information entered by other users. [SRD ID 16400]The Work Flow Process shall include, but not be limited to, defining groups and granting/ authorizing access toother users within a group to database entries. [SRD ID 16500]The Work Flow Process shall be configurable by the SBM operator to allow end user access to only theinformation (e.g., forms and reports) that are allowed by the COCOM TIM. [SRD ID 16600]3.2.1.1.12 BDA UsabilityThe following requirements apply only to the BDA Usability:The BDA Usability shall provide a means for updating displayed information to ensure access to the latestavailable data. [SRD ID 16700]The BDA Usability shall provide confirmations, either visual or audible, of user inputs and actions. [SRD ID16800]The BDA Usability shall provide status or mode indications during computations, downloads, or processingactivity. [SRD ID 16900]The BDA Usability shall support at least 250 concurrent users (i.e., GBS Operations Managers, TIM, ContentProviders, End User with reachback), per enclave, without degradation of service. [SRD ID 17000]The BDA Usability shall provide meaningful descriptor fields relevant to RBMs and products to enableconvenient management (e.g., sorting, searching, and filtering) of displayed information. [SRD ID 17100]The BDA Usability shall employ knowledge management techniques (e.g., broadcast efficiency metrics andnaming conventions). [SRD ID 17200]3.2.1.1.13 Additional BDA FunctionalitiesOther BDA activity requirements include:The SBM shall support the Session Description Protocol for content provider entry of video descriptors. [SRD ID17300]The BDA shall allocate bandwidth from services not currently in use to other active services within each enclave.[SRD ID 17400]The BDA shall be capable of automatically reallocating bandwidth within a security enclave between streamingand data services based on changes in service load. [SRD ID 17500]The BDA shall be capable of generating unique broadcast content for each IP Multicast Stream. [SRD ID 18000]The BDA shall dynamically share and re-allocate bandwidth for data products between enclaves, using flowcontrol feedback from the JIPM hub. [SRD ID 18100]The BDA shall be a single integrated application, able to operate identically on multiple security enclaves, andsupport File-based Multicast Content delivery and Streaming Services. [SRD ID 18200]The BDA shall operate Fazzt 7.1 and higher versions, or equivalent software. [SRD ID 18300]The BDA shall be installed at the DECC locations and operate on a DECC approved OS (Linux, MS, UNIX, etc).[SRD ID 18400]The BDA shall be backwards compatible with the legacy receive suite software (i.e., receive unclass/class files,streaming products [video, tunneled data, Power Publisher, etc], EPG displays, heartbeats, and web content) whilesupporting RBM presences displays and over-the-air updates. [SRD ID 18600]. The BDA shall simultaneouslysupport broadcasts at both JIPM and non-JIPM enabled uplink facilities. [SRD ID 18700]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-126

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The BDA shall support Microsoft Internet Explorer browser version 5.5 and higher versions supported byMicrosoft. [SRD ID 18800]. The BDA shall support Mozilla Firefox version 1.5 and higher versions that aresupported by Mozilla. [SRD ID 18900]The BDA shall adjust transmit data rates, within each enclave, with minimal interruption to the broadcast (e.g., 1minute or less). [SRD ID 19000]The BDA shall allow the SBM to share and reallocate available bandwidth dynamically, in near-real time amongvarious users, information products, multi-media types (data, video, and audio), and security release levelswithout interruption to the broadcast. [SRD ID 19100]The BDA shall allow the SBM to dynamically, in near-real time, allocate a portion of the bandwidth to insertlower priority, unscheduled information products where unused bandwidth exists. [SRD ID 19200]The BDA shall pre-empt files when higher priority/precedence files are available for broadcast. [SRD ID 19300]The BDA shall resume transmission of products that were preempted without loss of data. [SRD ID 19400]The BDA shall provide a capability for operators to set bandwidth allocations between security enclaves thatcannot be overridden by automatic controls. [SRD ID 19500]The BDA shall automatically delete ingested files after a minimum of 3 days. [SRD ID 19600]The BDA shall store all ingested data files for at least 3 days to provide the end users the ability to request filerebroadcast. [SRD ID 19700]The BDA shall allow the SBM to automatically protect and store queued information and systematically shutdown after loss or fluctuations of external power. [SRD ID 19801]The BDA shall process User Pull request based on current broadcast profile priorities. [SRD ID 19900]The GBS Network Management Software (NMS) shall be capable of automatically alerting local GBS operatorsof changes in SBM network element status or critical failures of systems that impact the broadcast of data viaaudible alarms, email, pages, and pop-up alarms in a manner consistent with the rules of the security enclave thatthe NMS is managing. [SRD ID 20000]The BDA shall provide automated Over-The-Air (OTA) software and Information Assurance updates to GBSJPO procured RBMs. [SRD ID 20001] Note that the BDA does not install and activate the over-the-air softwareand IA updates.The BDA shall respond to TIM authorized re-broadcast requests based on current broadcast profile priorities andthe missed files reports. [SRD ID 20200]3.2.1.2 Operations Management ActivityOperations Management Activities (OMA) includes the web interfaces, reports, and software needed for ageographically dispersed GBS Operations Managers to create and manage the GBS broadcast at the Primary andCOOP SBMs.The Operations Management Activity (OMA) shall provide the information and tools necessary for coordinatingthe use of satellite and uplink resources between the SBM, the Teleport Sites, the UFO PIPs, RSSC, WSOC, andother entities sharing GBS resources. [SRD ID 20500]The Operations Management Activity (OMA) shall provide the information and tools necessary accepting systemstatus information and displaying the status of critical components to the help desk. [20501]The OMA shall provide a capability for the GBS operations managers to set bandwidth allocations within asecurity enclave between streaming and data services. [SRD ID 20600]The OMA shall allow the GBS operations managers to regulate bandwidth allocation for source encryptedstreaming packets and integrate their information into the broadcast based upon priorities and coverage tointended users. [SRD ID 20700]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-127

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The OMA shall allow the GBS operations managers to enter or remove authorized RBMs from the broadcast.[SRD ID 20800]The OMA shall allow the GBS operations managers to assign streaming and video products to one or morespecific satellite downlinks. [SRD ID 20900]The OMA shall allow the GBS operations managers to enter authorized information providers into the broadcast.[SRD ID 21000]3.2.1.2.1 System MonitoringThe following requirements apply only to the TIMs and GBS Operations Managers for monitoring of the system:The GBS System Monitoring Service shall provide SBM information accessible via a web browser overSIPRNET and via an open, defined Web Services SIPRNET interface. [SRD ID 21100]The GBS System Monitoring Service shall include the capability to collate and format selected SBM informationand audit logs into historical textual and graphical reports. [SRD ID 21150]The GBS System Monitoring Service shall provide reporting status, key metrics, and configurable alerts of keySBM system elements and GBS usage statistics. [SRD ID 21200]The GBS System Monitoring Service shall monitor and report the operational status of key SBM elements (e.g.,ingest, DMZ, enclave servers, applications and software processes, encryption, and ingest and egress networkconnections). [SRD ID 21201]This Current SBM status information shall be current to within 5 minutes. [SRD ID 21202]The GBS System Monitoring Service shall provide status of key RBM system elements and GBS usage statistics[SRD ID 21300]The GBS System Monitoring Service, shall provide the status of every active RBM being served by the broadcast,as determined from the RBM Status Service and the RBM Status Proxy Service. [SRD ID 21301]The GBS System Monitoring Service, shall provide the capability to exclude RBMs based on operational securityconstraints. [SRD ID 21302]This Current RBM status information shall be current to within 10 minutes. [SRD ID 21303]The GBS System Monitoring Service shall provide status of key SBM system elements and GBS usage statisticsthat includes, but is not limited, to the Broadcast Coverage Map. [SRD ID 21400]The GBS System Monitoring Service, with respect to the Broadcast Coverage Map, shall generate a graphicaldisplay of the current GBS geographical satellite coverage footprints. [SRD ID 21401]The GBS System Monitoring Service, with respect to the Broadcast Coverage Map, shall identify the associatedsatellite and uplink modulator(s) and the uplink and downlink broadcast frequencies available within eachfootprint. [SRD ID 21402]The GBS System Monitoring Service, with respect to the Broadcast Coverage Map, shall include access to atabulation of all active RBMs within each footprint. And a graphical display for RBMs with known locations[SRD ID 21403]. The GBS System Monitoring Service, with respect to the Broadcast Coverage Map, shallprovide the capability to exclude RBMs based on operational security constraints. [SRD ID 21404]The GBS System Monitoring Service, with respect to the Broadcast Coverage Map, shall display the geographicallocation for all active RBMs (whose geographical locations are already known) except as precluded byoperational security constraints. [SRD ID 21405]. The GBS System Monitoring Service shall provide status ofkey SBM system elements that includes, but is not limited to, the GBS Usage Statistics. [SRD ID 21500]The GBS System Monitoring Service, with respect to GBS Usage Statistics, shall store, process, compilehistorical information, and generate usage statistics over selectable time intervals for each enclave. [SRD ID21501]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-128

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The GBS System Monitoring Service, with respect to GBS Usage Statistics, shall include historical informationparameters, but are not limited to, broadcast type (e.g. video, streaming packet, files), rebroadcast requests, and byuser pull requests. [SRD ID 21502]The GBS System Monitoring Service, with respect to GBS Usage Statistics, shall provide the ability to generate,in the Secret enclave, a merged usage statistical report on a daily basis. [SRD ID 21503]3.2.1.2.2 NETOPSThe following requirements apply only to the NETOPS Reporting Service:The NETOPS Reporting Services shall provide selectable elements from the Current SBM Status monitoringservice to the DISN Integrated Network Management System (INMS). [SRD ID 21601]The NETOPS Reporting Services shall provide selectable elements from the Current RBM Status monitoringservice to the DISN Integrated Network Management System (INMS). [SRD ID 21602]The NETOPS Reporting Services shall provide a capability for client access to the RNOSC INMS system for thepurpose of receiving and viewing INMS network maps. [SRD ID 21700]The NETOPS Reporting Services shall provide the capability to filter and report GBS system trouble tickets to theTrouble Management System (TMS). [SRD ID 21800]3.2.1.2.3 Uplink Modulator Planning ServicesThe following requirements apply only to the Uplink Modulator Planning Service:The Uplink Modulator Planning Services shall allow a GBS operational manager or TIM to manually associatespecific RBMs with uplink modulators on all GBS satellites (WGS, UFO, commercial, etc.). [SRD ID 21900]The Uplink Modulator Planning Services shall provide the capability to process the Satellite Access Authorization(SAA) and configure the system to the expected satellite configuration. [SRD ID 22000]3.2.1.2.4 Bandwidth Utilization and Configuration ManagementThe following requirements apply only to the Bandwidth Utilization and Configuration Management Service:The Bandwidth Utilization and Configuration Management Services shall provide a display of the currentbroadcast multicast streams by uplink modulator. [SRD ID 22100]The Bandwidth Utilization and Configuration Management Services shall provide a display of the currentbroadcast multicast stream allocations between data and streaming services and a breakdown of its constituentparts. [SRD ID 22200]The Bandwidth Utilization and Configuration Management Services shall accept manual inputs from the GBSoperations manager that allow control of the bandwidth allocations between multicast streams in case of the lossof flow control feedback from the JIPM hub. [SRD ID 22300]3.2.1.2.5 Queue Status ServicesThe following requirements apply only to the Queue Status Service:The Queue Status Services shall provide the GBS Operations Manager or TIM with a display of current statuswithin the queue for each uplink modulator. [SRD ID 22400]The Queue Status Services shall provide the GBS Operations Manager or TIM with a display of the statistics ofindividual products including but not limited to: list of files delivered, time of delivery, and size of files. [SRD ID22500]3.2.1.2.6 Additional OMA ServicesThe following are additional OMA requirements:30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-129

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The OMA shall provide a status display of the streaming data for each uplink modulator including, but not limitedto, a list of stream names, type of stream, data rate, and the uplink modulators over which the streams are beingbroadcast. [SRD ID 22600]The OMA shall provide a report showing the collection statistics and status of each web product. [SRD ID 22700]3.2.1.3 Content Management ActivityContent Management Activities (CMA) includes the web interfaces, reports, and software needed for ageographically dispersed Theater Information Manager (TIM) to manage the flow of products to RBMs.3.2.1.3.1 Mission Priority ServicesThe following requirements apply only to Mission Priority Service:The Mission Priority Services shall accept manual entry of pertinent information from the GBS Mission Requests(GMR). [SRD ID 22800]The Mission Priority Services shall prioritize the broadcast queue based on user mission as described in the CJCSI6250.01 and the relative priority of products being used to support that mission. [SRD ID 22900]The Mission Priority Services shall provide an interface to identify the GBS products needed to identify the GBSproducts needed to support specific user missions. [SRD ID 22930]The Mission Priority Services shall provide an interface to assign a relative priority to each product user within auser mission. [SRD ID 22950]3.2.1.3.2 Mission Management ServicesThe following requirements apply only to Mission Management Service:The Mission Management Services shall display the defined data stream (file and streaming) and allow the TIMto select and indicate the relative priority of data streams for broadcast. [SRD ID 23500] As a note, the datastreams are analogous to the current transponders.The Mission Management Services shall allow the TIM to associate data streams to one or more RBM. [SRD ID23600]3.2.1.4 Content Provider ActivityContent Provider Activities (CPA) includes the web interfaces, reports, and software needed for a geographicallydispersed authorized Content Provider or Source to post and manage the information products at the SBM.The system shall allow a content provider to view the current status of products sent to the SBM. [SRD ID 24000]Per enclave, the system shall provide the capability to test the broadcast data connectivity, protocols, securityinfrastructure, and application interfaces between an authorized content provider and SBM with appropriatemeasures to ensure such testing does not connect to the broadcast. [SRD ID 24050]The system shall provide the capability for the content provider to determine which RBMs will receive a productif sent. [SRD ID 24100]The system shall provide the necessary information for a content provider to determine which RBMs areaccessible on which uplink modulators and the associated Source Managed Tunneled Content Service multicastaddresses. [SRD ID 24200]The system shall allow an authorized content provider to enter detailed data describing content provider andproduct information. [SRD ID 24300]The system shall allow an authorized content provider to preclude their products from being displayed in thecontent catalog. [SRD ID 24400] Precluded product information should be included in the audit log information.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-130

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The system shall provide an interface where a source can provide one or more Uniform Resource Locator (URL)addresses that will be displayed at the RBM for simplified access to the source site. [SRD ID 24500]The system shall provide a content provider with a display of the current status of file products sent by the contentprovider. [SRD ID 24600]The system shall not provide a content provider the current status of file products sent by another content providerunless authorization is provided by the TIM. [SRD ID 24650]The system shall provide a content provider with display of the current status of file products sent to the SBM fordelivery to a specific RBM. [SRD ID 24700]3.2.1.5 DECC Broadcast Segment Architecture and InfrastructureThe following requirements apply to the broadcast segment architecture and infrastructure:The broadcast segment shall provide both the primary and COOP SBM capability to independently support theglobal broadcast. [SRD ID 24800]The broadcast segment shall replicate 100 percent of the system management and system configurationparameters at the COOP site every thirty (30) minutes [TBR-32] to facilitate a transfer of SBM operations. [SRDID 24900]For a scheduled transfer, the broadcast segment shall transfer SBM operations to the COOP site within 1 minute.[SRD ID 25000]The broadcast segment shall be capable of ingesting a minimum of 300 Mbps of files per enclave (Secret andUnclassified). [SRD ID 25100]The broadcast segment shall be capable of ingesting a minimum of 400 Mbps of IP data and video streams perenclave (Secret and Unclassified). [SRD ID 25200]The broadcast segment shall be capable of ingesting a minimum of 200 Mbps of files in the ROKUS enclave.[SRD ID 25300]The broadcast segment shall be capable of ingesting a minimum of 200 Mbps of IP data and video streams in theROKUS enclave. [SRD ID 25400]The broadcast segment shall support the 10 satellites, 100 downlink beams, 56 aggregated streams (eachconsisting of multiple multicast streams to be injected by a specific modulator at the JIPM hub), 5000 RBMs,2500 subscriptions (content folders and IP streams), and 250 content providers. [SRD ID 25500]The broadcast segment shall be capable of supporting IPv6. [SRD ID 25600]The broadcast segment shall incorporate Ipv6 components, as they become commercially available. [SRD ID25700]The broadcast segment shall be scalable to accommodate a 50% increase in the number of satellites, downlinkbeams, multicast streams, RBMs, subscriptions (content folders and IP streams), and content providers. [SRD ID25800]The broadcast segment shall be capable of supporting a nominal data rate of 72 Mbps for each group of multicaststreams per modulator. [SRD ID 25900]The broadcast segment shall include a DIACAP compliant DMZ. [SRD ID 26000] NOTE: Similar to the otherhardware and software being installed at the DECC, the DMZ will be procured by DISA and installed incoordination with the GBS JPO and DECC transition contractor.The broadcast segment shall be capable of supporting any mix of file or streaming data (all file, all streaming, anymix of the two) on the group of multicast streams per modulator. [SRD ID 26100]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-131

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3In the event backup power fails, the broadcast segment shall provide automatic system protection for equipmentin order to logically and systematically shut down or rapidly resume broadcast operations after loss or fluctuationsof external power. [SRD ID 26200]. The broadcast segment, in the event of power failures, shall take advantageof facility provided uninterrupted power sources. [SRD ID 26300]The broadcast segment shall provide the capability to key GBS specific cryptographic equipment manually. [SRDID 26400]3.2.2 Performance Characteristics: Receive SegmentThis paragraph provides requirements for the receive segment. The receive segment requirements, within thisSRD, are focused on the RBM software, JIPM-R upgrade kits and their associated installation, the RBM users(RBM Operators and End User), and the interfaces to the DISN.3.2.2.1 Receive Delivery ActivitiesThe receive delivery activities (RDA) supporting the Receive Segment are functions implemented to ensure thatend users can receive, process, and utilize the GBS transmission services. Most of these functions will beimplemented via existing COTS products with minimal customization other than interface modifications.3.2.2.1.1 RDA Status ElementsThe RDA reports RBM Status Elements. The following are RDA report requirements:The RDA status elements shall include, but are not limited to the RBM Heartbeat. [SRD ID 30000]The RBM Heartbeat shall report each active broadcast received by each RBM, to include multiple uplinkmodulators on the same or different satellites. [SRD ID 30101]The RBM Heartbeat shall use a unique identifier on each received broadcast to report the associated satellite anduplink modulator. [SRD ID 30102]For unclassified enclaves, the RBM Heartbeat shall include a message field for reporting broadcast receptionquality when such information is locally available (e.g. from a broadcast RBM). [SRD ID 30103]The RBM Heartbeat shall be displayed on every RBM webpage along with a banner. [SRD ID 30104]The RBM Heartbeat banner display shall terminate upon the deletion of the banner message within the heartbeat.[SRD ID 30105]The RBM Heartbeat shall indicate a loss of the heartbeat signal via the displayed icon if any heartbeat is notreceived for an extended period. [SRD ID 30106]Outside a normal shutdown, the RBM shall provide the option to generate and send an email to the RBMAdministrator to indicate a loss of the heartbeat signal. [SRD ID 30107]The RDA status elements shall include, but are not limited to, the Missed Files Report. [SRD ID 31000]The Missed Files Report shall list the files that were not received since the last status report, as determined bycomparing the files received correctly with the broadcast history information from the broadcast. [SRD ID 31101]The Missed Files Report shall include a summary of the percentage of files received correctly. [SRD ID 31102]The RDA status elements shall include, but are not limited to, the IAVA Status report. [SRD ID 32000]The IAVA Status report shall provide the current state of IAVA patches that have been installed, including thedate and time of installation. [SRD ID 32101]The RDA status elements shall include, but are not limited to, the Application Information report. [SRD ID33000]The Application Information report shall provide information about the RBM applications for use in systemtroubleshooting and Help Desk operations. [SRD ID 33101]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-132

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The Application Information report shall include, but is not limited to vendor, version, patches installed,configuration parameters, and memory and CPU usage statistics. [SRD ID 33102]The RDA status elements shall include, but are not limited to, the RBM Profile report. [SRD ID 34000]The RBM Profile shall be entered via a web browser. [SRD ID 34101]The RBM Profile shall include, but not limited to: geographical location, satellite uplink modulator(s) providingcoverage, receive terminal class (e.g., Small, Medium, Large), and RBM active times. [SRD ID 34102]3.2.2.1.2 RDA for RBMs with ReachbackThe following requirements apply only to RBMs with Reachback Connectivity (either directly via the broadcastsatellite transmission segment or via an alternate IP network):For each RBM with reachback connectivity (either directly via broadcast satellite transmission segment or via analternate IP network), the RDA shall provide status of broadcast reception and key RBM operating andconfiguration parameters to the SBM. [SRD ID 35100]For each RBM with reachback connectivity (either directly via broadcast satellite transmission segment or via analternate IP network), the RDA shall be capable of displaying the most recently received status informationlocally via web browser regardless of reachback connectivity status. [SRD ID 35200]For each RBM with reachback connectivity (either directly via broadcast satellite transmission segment or via analternate IP network), the RDA shall provide status separately for each security level. [SRD ID 35300]For each RBM with reachback connectivity (either directly via broadcast satellite transmission segment or via analternate IP network), the RDA shall allow the status-reporting interval at the RBM to be configurable (to includebut not be limited) to once per minute. [SRD ID 35400]For each RBM with reachback connectivity (either directly via broadcast satellite transmission segment or via analternate IP network), the RDA shall allow the status-reporting capability to be suppressed when required byoperational constraints. [SRD ID 35500]For each RBM with reachback connectivity (either directly via broadcast satellite transmission segment or via analternate IP network), the RDA shall provide RBM Status via an open, defined Web Services interface at theSBM, with appropriate IA attributes. [SRD ID 35600]3.2.2.1.3 OTA Software & IA UpdatesThe following requirements apply only to OTA Software and IA Updates:Specific to OTA Software and IA Updates only, the RDA shall have the ability to allow the end user to select if,and when, they will install the automated IA updates. [SRD ID 35800]Specific to OTA Software and IA Updates only, the RDA shall process OTA software updates and include amode that overrides the end user control for critical updates. [SRD ID 35900]3.2.2.1.4 RDA & Existing IPThe following requirements apply to the RDA functional compatibility with Existing IP broadcasts:The RDA shall be functionally compatible with the existing IP broadcast by being able to receive all existingover-the-air GBS services. [SRD ID 36000]The RDA shall be functionally compatible with the existing IP broadcast by being able to auto-forward contentusing FTP and FTPS similar to the existing receive suite so that the system can be interchanged with existingreceive suites. [SRD ID 36100]The RDA shall be functionally compatible with the existing IP broadcast by being able to receive and process theGBS heartbeat. [SRD ID 36200]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-133

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The RDA shall be functionally compatible with the existing IP broadcast by being able to receive and process theGBS Electronic Program Guide. [SRD ID 36300]The RDA shall be functionally compatible with the existing IP broadcast by being able to display the TuningGuide generated by the SBM. [SRD ID 36400]The RDA shall be functionally compatible with the existing IP broadcast by being able to provide the receivesuite presence display required information. [SRD ID 36500]3.2.2.1.5 Other RDA RequirementsAdditional RDA requirements include:The RDA shall be portable between all supported Microsoft Windows operating systems. [SRD ID 37000]The RDA shall operate on a Linux platform, as designated by the Government. (Objective) [SRD ID 37010]The Linux RDA application version shall meet all the requirements of the Microsoft Windows RDA version.(Objective) [SRD ID 37011]The Linux RDA application version shall be controllable and operable from a web-based HTTPS interfacewithout requiring a keyboard, mouse, or display to operate. (Objective) [SRD ID 37012]The Linux RDA application version shall, at a minimum, be based on an Intel X86-based architecture. (Objective)[SRD ID 37013]The RDA shall be capable of supporting Ipv6. [SRD ID 37100]The RDA shall be able to display the SBM Content Catalog and allow an end user to select and indicate therelative priority of products for delivery to their RBM and other RBMs as indicated in their request (User Pull –This applies to RBMs that have reachback connectivity or users with alternate communications means available toaccess the content catalog). [SRD ID 37200]The RDA shall provide a subscription request capability for a product in the catalog. [SRD ID 37300]The RDA shall be delivered as a single disk install with only minimal interaction required by the enduser/installer (no training required to perform installation). [SRD ID 37400]The RDA shall be capable of being hosted on user specified alternative computer platforms after the alternativeplatform is certified compatible with GBS and added to a Qualified Product List (QPL). [SRD ID 37500]The RDA shall be capable of operating in an unattended mode, except during configuration changes made afterinitial setup and during installation of OTA and IA updates. [SRD ID 37600]. The RDA shall be compliant,certified, and accredited in accordance with the DoDI 8510.bb, DIACAP Instructions. [SRD ID 37700]The RDA shall provide for separation of broadcast content from user data on RBM storage devices. [SRD ID37900]The RDA shall provide multiple web-based mechanisms for finding delivered content such as indexed search,content sorting, or filename based search. [SRD ID 38000]The RDA shall support the forwarding of multicast packets based upon IGMP V3 protocols. [SRD ID 38100]The RDA shall support the manual configuration of forwarding multicast over the local area network without theneed for IGMP protocols. [SRD ID 38200]The RDA shall provide a mechanism for determining what files or streams were received; which files or streamswere intended for their RBM, but were missed. [SRD ID 38300]The RDA shall automatically execute the use of automated file cleanup (to ensure there is adequate storage to runthe system); automated disk de-fragmentation; automated database maintenance or any other mechanism requiredto ensure long-term performance of the software. [SRD ID 38400] This is to ensure that the local disk driveperformance does not degrade over time.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-134

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The RDA shall provide a mechanism for providing system statistics and reports that allow end users to see theperformance of the receive system. [SRD ID 38500]The RDA shall support Microsoft Internet Explorer browser versions 5.5 and higher versions supported byMicrosoft. [SRD ID 38600]The RDA shall support Mozilla Firefox version 1.5 and higher versions supported by Mozilla. [SRD ID 38700]The RDA shall provide a capability to filter broadcast file content by file extension (e.g. *.exe) to prevent certaintypes of files from being received by the RBM. [SRD ID 38800]The RDA shall be capable of receiving all services provided by the uplink. [SRD ID 38900]The RDA shall support the processing of data at variable data rates according to the beam and terminalcombinations. [SRD ID 39000]The RDA shall support the simultaneous processing of multicast streams from at least two downlink modulators.[SRD ID 39100]The RDA shall provide a web-based mechanism that allows locally connected (i.e., via LAN) users to utilize thesystem functionality via a web browser over a local network. [SRD ID 39200]The RDA shall ensure that broadcast products cannot be written to an absolute directory path. [SRD ID 39300]3.2.2.1.6 Auto Push FunctionalityAuto Push functionality is a capability for an end user terminal, that is connected to the RBM via a LAN, to orderfile-based products and have them delivered to their system as they arrive at the RBM. The followingrequirements apply only to Auto Push:The Auto Push functionality shall deliver products via FTP (act as FTP client) to end user systems. [SRD ID39400]The Auto Push functionality shall deliver products via FTPS or SFTP (act as FTPS or SFTP client) to end usersystems. [SRD ID 39500]The Auto Push functionality shall allow for pre-configured ordering of related products based on EPGinformation or other available metadata such as data source, content type, product information, etc. [SRD ID39600]The Auto Push functionality shall provide the capability to delete, modify, and add subscriptions via a webinterface. [SRD ID 39700]The Auto Push functionality shall maintain directory structures for Auto Pushed content. [SRD ID 39800]The Auto Push functionality shall support multiple end users subscriptions to the same content at the samelocation but to different end user machines. [SRD ID 39900]The Auto Push functionality shall be available for any level of content hierarchy or organization. [SRD ID 40000]For example, if content is delivered in a directory structure “Level1 – Level2 – Level-3” content andsubdirectories can be pushed from any of the directory levels.The Auto Push functionality shall be configurable via a web browser (HTTPS) from a network-connectedmachine. [SRD ID 40100]3.2.2.1.7 Web Browser Content ManagementThe following requirements apply only to Web Browser Content Management:The Web Browser content management functionality shall support the user-pull of received content from theirweb browser over a local area network. [SRD ID 40200]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-135

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The Web Browser content management functionality shall support Microsoft Internet Explorer browser version5.5 and higher versions supported by Microsoft [SRD ID 40300]The Web Browser content management functionality shall support Mozilla Firefox version 1.5 and above. [SRDID 40400]The Web Browser content management functionality shall display the Electronic Program Guide. [SRD ID40600]The Web Browser content management functionality shall support HTTPS. [SRD ID 40700]3.2.2.1.8 Video FunctionalityThe following requirements apply only to Video functionality:The Video functionality shall provide means to convert IP video to NTSC and PAL, allowing video to be viewedon external hardware. [SRD ID 40800]The Video functionality shall include a capability of viewing the transmitted video from the uplink on the localRBM. [SRD ID 40900]The Video functionality shall provide IP video recording capability for at least 30 minutes, at a minimum rate of 3Mbps so that incoming video streams can be time shifted. [SRD ID 41000]3.2.2.1.9 RDA MonitoringThe following requirement applies to RDA Monitoring only:The RDA shall provide RBM Local Monitoring functionality that displays a statistics page for LAN connectedusers so that they can see the status of incoming files. [SRD ID 41100]3.2.2.2 Broadcast Reception Management ActivitiesBroadcast Reception Activities (BRA) includes the web interfaces, reports, and software needed for a RBMoperators and end users to manage the RBM profile and request products from the SBM.3.2.2.2.1 RBM Reception Management with ReachbackThe following requirements apply only to RBM Reception Management with Reachback:For RBMs with reachback, the Reception Management functionality shall allow an end user to enter RBM profileinformation. [SRD ID 42000]For RBMs with reachback, the Reception Management functionality shall allow an end user to request therebroadcast of products from the Broadcast Management Segment. [SRD ID 42100]For RBMs with reachback, the Reception Management functionality shall allow an end user to view the systemtuningguide. [SRD ID 42200]For RBMs with reachback, the Reception Management functionality shall allow an end user to pull content fromeither SBM’s Content Catalog or via source URL. [SRD ID 42300]3.2.2.2.2 RBM Reception Management through ProxyThe following requirements apply only to RBM Reception Management through Proxy:For RBMs using a proxy, the Reception Management functionality shall include a capability for manual entry ofkey RBM information by a proxy. [SRD ID 43500]For RBMs using a proxy, the Reception Management functionality shall allow key information to be entered via aweb browser. This information may include but is not limited to: geographical location, satellite uplinkmodulator(s) providing coverage, RBM Active times, IAVA status, receive terminal class (e.g., Small, Medium,Large), and RBM Application Information. [SRD ID 43600]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-136

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3For RBMs using a proxy, the Reception Management functionality shall include each RBM in the broadcast(s)using the best information available even if some parameters are not entered by the proxy. [SRD ID 43700]3.2.3 Physical Characteristics3.2.3.1 Broadcast SegmentThe following requirement applies to the broadcast segment physical characteristics:The broadcast segment hardware and software shall operate within the DECC infrastructure. [SRD ID 44150]3.2.4 External Interface Requirements3.2.4.1 Broadcast Segment Interfaces3.2.4.1.1 SBM to DECC FacilityThe following requirements apply to the SBM to DECC Facility interfaces:The SBM to DECC Facility interfaces shall comply with [the TBD-1] established DECC interface standards andpolicies. [SRD ID 44500]The SBM to DECC Facility interfaces shall be capable of traversing the DECC firewalls for routing across theDISN to the uplink facilities. [SRD ID 44600]3.2.4.1.2 DISN to SBM DMZThe following requirements apply to the DISN to SBM DMZ interfaces:The DISN to SBM DMZ interfaces shall accept various files and streaming products from sources using standardinternet protocols that include but are not limited to Encapsulated Security Payload (ESP), Secure Shell (SSH),Simple Mail Transfer Protocol (SMTP), Simple Mail Transfer Protocol Secure Sockets Layer (SMTPSSL)Domain Name Server (DNS), Hyper Text Transfer Protocol (HTTP), Hyper Text Transfer Protocol Secure(HTTPS), File Transfer Protocol (FTP), File Transfer Protocol over Secure Sockets Layer (FTPS), SSH FileTransfer Protocol (SFTP), Message Hopper , MSCHAT, Power Publisher, and Multicast. [SRD ID 44700]The DISN to SBM DMZ interfaces shall allow ingest of source encrypted TS/SCI traffic via tunneled IP streams(KPP). [SRD ID 44800]The DISN to SBM DMZ interfaces shall allow configuration inputs and operations management using HTTPSwith DOD PKI certificates. [SRD ID 44900]3.2.4.1.3 SBM DMZ to SBMThe following requirements apply to the SBM DMZ to SBM interfaces:The SBM DMZ to SBM interfaces shall accept various files and streaming products from the SBM DMZ usingstandard internet protocols that include but not limited to Encapsulated Security Payload (ESP), Secure Shell(SSH), Simple Mail Transfer Protocol (SMTP), Simple Mail Transfer Protocol Secure Sockets Layer (SMTPSSL) Domain Name Server (DNS), Hyper Text Transfer Protocol (HTTP), Hyper Text Transfer Protocol Secure(HTTPS), File Transfer Protocol (FTP), File Transfer Protocol over Secure Sockets Layer (FTPS), SSH FileTransfer Protocol (SFTP), Message Hopper, MSCHAT, Power Publisher, TACACS, NTP, SNMP Traps, SYSLog, and Multicast. [SRD ID 45000]The SBM DMZ to SBM interfaces shall allow ingest of source encrypted TS/SCI traffic via tunneled IP streams(KPP). [SRD ID 45100]The SBM DMZ to SBM interfaces shall allow configuration inputs, RBM feedback, and operations managementusing HTTPS with DOD PKI certificates. [SRD ID 45200]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-137

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The SBM DMZ to SBM interfaces shall use DISN connectivity and bandwidth to connect information sources,PIPs, Teleports, Primary and COOP SBMs, TIMs, Operations Mangers, and RBMs. [SRD ID 45300]The SBM DMZ to SBM interfaces shall provide the necessary tools to ingest and process analog videos fromsource inputs. [SRD ID 45400]3.2.4.1.4 SBM to Injection TerminalsThe following are requirements for the SBM to Injection Terminal interfaces:The SBM to Injection Terminal interfaces shall generate IP multicast streams for each uplink modulator. [SRD ID46000]The SBM to Injection Terminal interfaces shall transport the IP multicast streams generated at the SBM over theDISN to geographically dispersed uplink facilities. [SRD ID 46100]The SBM shall ingest SMPTE-325M messages from each injection terminal’s JIPM Hubs to control dynamicbandwidth allocations for file-based data. [SRD ID 46200]3.2.4.1.5 Other Broadcast Segment InterfacesThe Injection Terminal to Space Segment interface is a Teleport/WGS Requirement and is not addressed withinthis GBS SRD.The following are additional broadcast segment interface requirements:The SBM to RBM interfaces shall support the legacy GBS over-the-air protocols to ensure compatibility.[SRD ID 46300]The BDA to GBS Operations Manager HCI interfaces shall provide context-sensitive on-line help. [SRD ID46400]BDA to Regional Satellite Support Center (RSSC)/Wideband SATCOM Operations Center (WSOC) WGSPlanning and Control System shall be a WGS authorized SAR/SAA message. [SRD ID 46500]3.2.4.2 Receive Segment InterfacesThe Space Segment to Receive Terminal interface is a Receive Terminal (RT) production requirement and is notaddressed within this GBS SRD.The Receive Terminal to RBM interface is a Receive Suite (RS) production requirement and is not addressedwithin this GBS SRD.3.2.4.2.1 RBM to End UserThe RBM to End User Interface requirements are as follows:The RBM to End User Interface shall allow the RBM to deliver various files and streaming products to end usersusing standard internet protocols that include, but are not limited to: Hyper Text Transfer Protocol (HTTP), HyperText Transfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), File Transfer Protocol over Secure SocketsLayer (FTPS), SSH File Transfer Protocol (SFTP), Real-Time Transport Protocol (RTP), Internet GroupManagement Protocol (IGMP), Session Description Protocol (SDP), Trivial File Transfer Protocol (TFTP), andMulticast. [SRD ID 47000]The RBM to End User Interface shall allow the End User access to the RBM by using HTTPS. [SRD ID 47100]3.2.4.2.2 RBM to SBMThe following is the RBM to SBM interface requirement:The RBM to SBM interface shall allow RBM feedback across the DISN using HTTPS with DOD PKIcertificates. [SRD ID 47200]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-138

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.2.5 Internal InterfacesThis interface will vary based upon vendor design. At this time, there are no known fixed internal interfacerequirements.3.2.6 Interface: Test EquipmentThis interface will vary based upon vendor design.3.2.7 Interface: Common Interfaces and ServicesThis interface will vary based upon vendor design.3.2.8 IntelligenceNot applicable.3.2.9 Command, Control, and CommunicationsCommand and Control of the GBS operational broadcast will be managed by 14 th Air Force and COCOM TIMsvia web interfaces.3.2.10 System Quality FactorsThe GBS System will meet the following Quality Factors requirements:The GBS transport system shall provide capabilities that ensure that information identified as priority isdelivered ahead of regular traffic 99% of the time. [SRD ID 48000]3.2.10.1 Reliability3.2.10.1.1 Broadcast Segment ReliabilityNot Applicable. Per ORD III, broadcast segment reliability requirements are addressed by operational availabilityrequirements defined in 3.2.10.3.1.3.2.10.2 MaintainabilityThe following requirement applies to maintainability:Each LRU element of the GBS system shall include Built-In-Test (BIT) diagnostics that fault isolate usingcontractor supplied test equipment, 95% of the time. [SRD ID 48400]3.2.10.2.1 Broadcast Segment MaintainabilityThe following requirement applies to broadcast segment maintainability:The SBM Mean Time to Repair (unscheduled maintenance) shall be less than 90 minutes. [SRD ID 48500]3.2.10.2.2 Broadcast Segment Scheduled and Routine MaintenanceThe following are requirements for the broadcast segment scheduled and routine maintenance:SBM operator level maintenance shall be limited to basic care, cleaning, and replacement of expendablesand Line Replaceable Units (LRU). [SRD ID 48600]SBM scheduled routine maintenance shall be performed without disruption to service operations. [SRD ID48700]SBM scheduled and routine maintenance time shall not exceed one maintenance hour per 24-hour period.[SRD ID 48800]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-139

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The GBS system shall allow cryptographic equipment to be maintained and repaired in accordance withCOMSEC maintenance policies and procedures. [SRD ID 48900]3.2.10.2.3 Receive Segment MaintainabilityThe following requirement applies to receive segment maintainability:The RBM Mean Time to Repair (unscheduled maintenance) shall be less than 90 minutes. [SRD ID 50000]3.2.10.3 Operational Availability3.2.10.3.1 Broadcast Segment AvailabilityThe following requirements apply to availability:The SBM shall maintain an operational availability of 99.0% over a period of 480 hours. [SRD ID 50101]This means that following a successful System Acceptance Test and the initiation of operations at any SBM,future upgrades must be installed without downtime that would prevent the satisfaction of this requirement.Formal test periods do not count against operational availability.The SBM shall maintain an operational availability of 99.99% over a period of 480 hours. (Objective)[SRD ID 50102]. SBM is defined as being mission capable when it can support receipt of data from sources intoeach available security enclave, can form a broadcast data stream for all its allocated uplink modulators and cancommunicate these data streams to the Injection Point terminals.3.2.10.3.2 Receive Segment AvailabilityNot applicable. Per ORD III, receive segment availability is addressed by reliability requirements defined inError! Reference source not found..3.2.11 Environmental ConditionsThe GBS System will meet the following environmental requirements:Fixed Sites and Equipment exposed directly to an external environment shall operate in blowing sand, dust,and all precipitation environments during 45 mph sustained winds, gusts to 60 mph in -40°F to 120°F airtemperatures plus solar loading at all humidity levels. (Threshold) [SRD ID 50201]Fixed Sites and Equipment exposed directly to an external environment shall operate in blowing sand, dust,and all precipitation environments during 45 mph sustained winds, gusts to 60 mph in -50°F to 150°F airtemperatures plus solar loading at all humidity levels. [SRD ID 50202]3.2.12 TransportabilityThere are no transportability requirements for the broadcast segment.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-140

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.3 Design and Construction3.3.1 Selection of Specifications and StandardsCompliance to applicable specifications will be in accordance with the requirements stated herein this documentand other GBS requirement specifications.3.3.2 Electrical3.3.2.1 Power3.3.2.1.1 Broadcast Segment PowerThe following requirement applies to broadcast segment power:The broadcast segment shall be capable of operating at 120/220 VAC at 60/50 Hz power. [SRD ID 50400]3.3.2.2 Electromagnetic Radiation Compatibility (EMC)The GBS EMC compatibility, design, and construction will be in accordance with the applicable requirementsstated herein this document and other GBS requirements documents.3.3.2.3 Electrostatic Discharge (ESD)The GBS ESD design and construction will be in accordance with the applicable requirements stated herein thisdocument and other GBS requirements documents.3.3.3 MechanicalThe GBS mechanical design and construction will be in accordance with the applicable requirements stated hereinthis document and other GBS requirements documents.3.3.4 Parts, Materials, and Processes (PM&P)The GBS PM&P design and construction will be in accordance with the applicable requirements stated herein thisdocument and other GBS requirements documents.3.3.5 Interchangeability and ReplacementThe GBS interchangeability and replacement will be in accordance with the applicable requirements stated hereinthis document and other GBS requirements documents.3.3.6 Identification & MarkingThe GBS identification and markings will be in accordance with the applicable requirements stated herein thisdocument and other GBS requirements documents.3.3.7 WorkmanshipThe GBS workmanship will be in accordance with the applicable requirements stated herein this document andother GBS requirements documents.3.3.8 Human EngineeringThe GBS System should provide interface characteristics to maximize human productivity and performance, asverified by iterative testing. The following requirements are intended to ensure this provision:The GBS System design shall consider and accommodate the nine Human Systems Integration (HSI) domains(i.e., manpower, personnel, training, human factors engineering, environment, safety, occupational health,personnel survivability, and habitability). [SRD ID 50700]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-141

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Each HSI domain shall be addressed and optimized, as applicable, within the structure of the GBS design toachieve total system performance and reduce life-cycle costs. [SRD ID 50710]GBS System Human Factors Engineering shall comply with Human Systems Integration requirements set forthwithin DoD Directive 5000.1 and DoDI 5000.2, Human Engineering Program Process and Procedures, MIL-HDBK-46855A, and Human Engineering Design Criteria, MIL-STD-1472F. [SRD ID 51000]3.3.9 Software Engineering3.3.9.1 Commercial and Government-off-the-Shelf Software.Maximum use of COTS and Government-off-the-Shelf software is encouraged to reduce life-cycle costs to theextent that it complies with system requirements. System user documentation shall be developed to supportmission accomplishment. This should include a description of software-based functionality, as appropriate.Ownership rights for non-COTS software developed for the GBS shall become the property of the Government.All source codes for software and firmware maintained by Government personnel or under separate contract shallbe delivered in accordance with the applicable Government software standards. COTS software and firmwareshall be delivered with the licenses needed to allow use at any and all necessary Government locations.3.3.9.2 Design and DevelopmentAll newly developed software configuration items should be developed in a manner that promotes ease ofmaintenance and maximum system flexibility. All software should be designed with consideration given to thedesired post-production software support concept. The design activity should also ensure that future softwarechanges are affordably verified. Software upgrades should be successfully executed without degrading systemoperation. Software should be designed to allow for rapid response to changes in the operational environment.3.3.9.3 Database Management SystemsCOTS or NDI database management systems should be used where feasible. If a database management systemmust be newly designed, it shall be designed so the user can change database contents without affecting thesoftware. The data elements should take full advantage of the DoD corporate data dictionary and contribute to theShared Data Environment where feasible.3.3.10 Computer ResourcesWhen applicable, GBS software updates should be installed at the operator level by manual and automatic overthe-airbroadcast means. The GBS broadcast management and terminal components shall provide checks forcomputer operating system viruses during systems initialization and routine operations.3.3.11 SafetyThe GBS System will meet the following Environmental, Safety, and Occupational Health Requirements:The GBS System design and construction shall not use Class I and Class II ozone depleting substances.[SRD ID 51500]The GBS System design and construction shall be compliant with the GBS Safety Program requirementsspecified in the GBS System Safety Management Plan (SSMP) and GBS Programmatic Environmental,Safety, and Health Evaluation (PESHE). [SRD ID 51525]The GBS System design shall minimize use of other hazardous materials in GBS components,manufacturing materials and processes, support equipment, and disposal operations. [SRD ID 51550]The GBS System shall be HAZMAT complaint in accordance with DoD Directive 5000.1 and DoDI 5000.2.[SRD ID 51600]The GBS System shall not expose operators or maintainers to health and safety hazards as defined in the GBSHealth Hazards Assessment. [SRD ID 51700]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-142

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Applicable ESOH requirements shall be integrated into the GBS System Engineering process, as defined byNSSAP 03-01 and NEPA/EPA regulations. [SRD ID 51800]3.3.12 SecurityThe GBS System will meet the following Information Assurance requirements:The GBS System shall be compliant, certified, and accredited in accordance with the DoDI 8510.bb,DIACAP Instructions. [SRD ID 51900]The GBS System, at a minimum, shall meet all the IA controls for a Mission Assurance Category IIclassified system per DoD Instruction 8500.2. [SRD ID 52000]The GBS System shall use DoD issued PKI certificates to support authentication, access control,confidentiality, data integrity, and non-repudiation. [SRD ID 52100]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-143

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.4 LogisticsThe GBS System will comply with the following logistics requirements:The GBS System shall use existing logistics support infrastructures described in the Joint IntegratedLogistics Support Plan. [SRD ID 52400]Requirements for maintenance support equipment shall be kept at a minimum. SRD ID 52500]If support equipment is required, the GBS System support equipment, at a minimum, shall be comprised of90 percent COTS support equipment. [SRD ID 52600]The GBS system shall not require special purpose support equipment, special purpose electronic testequipment, or special purpose tools. [SRD ID 52700]3.5 Personnel and Training3.5.1 Broadcast Segment Manning and TrainingThe GBS Broadcast Segment manning and training will be in compliance with the 14 th Air Force’s trainingrequirements.3.5.2 Receive Segment Manning and TrainingThe following are requirements for the Receive Segment Manning and Training:The RBM Software shall operate in an unattended mode for steady state broadcasts. [SRD ID 53000]Personnel skill and skill levels required for operating and maintaining the RBM shall not exceed levelsdefined in Table 5 of this SRD. [SRD ID 53100]Table 5: Personnel Skill LevelsPersonnelArmy operatorsArmy network integratorArmy maintainersSkill LevelsGeneral Purpose User (GPU), TacticalOperations Center (TOC) personnel, 25B25U (Division & below)25B (above Division)ITET2Navy operatorsNavy maintainersAir Force operators 3COX1 skill level 5Air Force maintainers 2E1X1 skill level 5USMC Operators Occupational Field 2500USMC Maintainers Occupational Field 28003.5.3 GBS System TrainingThe GBS System design should minimize manpower required to operate and maintain the system. The requiredmanpower relates to the level and complexity of the system training requirements, defined as:GBS System Training, where possible, shall include commercially available Embedded Training (ET).[SRD ID 53201]GBS System Training shall not require separate training devices or simulators to support the development,operations, and maintenance of GBS. [SRD ID 53202] Trainers will provide training on the actual fieldedreceive suite units. Training at the DECC/SBM will also be performed on-site, using actual GBS equipment.GBS System Training shall be in accordance with service policies and procedures. [SRD ID 53203]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-144

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3GBS System Training shall include electronic form (and hardcopy form where required) of the operatorand maintainer training material. [SRD ID 53204]GBS System Training shall include electronic form (and hardcopy form where required) of the operationsand maintenance technical documentation. [SRD ID 53205]GBS System Training shall be provided for the elements of the broadcast segment at the time of transitionto government operations. [SRD ID 53207]3.6 Pre-Planned Product Improvements (P3I)GBS Phase 2 Block-3 (and beyond) employs pre-planned product improvements (P3I) to non-space segmentenhancements to BMS and receive suite capabilities. Block-3 requirements will require additional programfunding to be addressed as initiatives. P3I provides for a technology insertion strategy designed to fully leverageinformation technologies to permit alterations in our concepts of operations, doctrine, organizations, and forcestructure. Every Block-3 requirement should be considered annually during the budget process as an initiative forprioritization and potential implementation. This is a continuous process, meant to create or anticipate the future.P3I is meant to deal with the co-evolution of concepts, processes and organizations and technology, to create newcompetitive areas and new competencies, and to identify, leverage and even create new underlying principles forthe way things are done in order to identify and leverage new sources of power. In this regard, Block-3requirements are transformational in nature, with an objective to sustain competitive advantage.The following subparagraphs describe the P3I requirements:3.6.1 2-Way Transmit Receive SuitesThe following requirements apply only to the Transmit Receive Suites:The Transmit Receive Suite (TRS) shall be composed of a receive terminal and RBM to provide RCS capability,to support “user pull” requests, via connectivity through a Teleport and DISN core. [SRD ID 60000]The 2-way capability of the GBS Transmit Receive Suites shall be supported by the DECC architecture. [SRD ID60100]The SBM software shall support the GBS TRS capability of transmitting and receiving 2-way data between theRBM, via the GBS space segments with an RCS having connectivity to the DISN. [SRD ID 60201]The RBM software shall support the GBS TRS capability of transmitting and receiving 2-way data between theSBM, via the GBS space segments with an RCS having connectivity to the DISN. [SRD ID 60202]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-145

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3GBS IP RS with Two-Way Upgrade KitWGS / CommercialClassifiedLaptop w/BCMSKG-250JIPM RMClassifiedPEPEnthernetSwitchGBS DVB-RCSAntennaBUCFigure 6: GBS Two-Way Upgrade Kit ArchitectureUnclassifiedPEPUnclassifiedLaptop w/ BCMS3.6.2 Enhanced Source IntegrationThe following requirement applies only to the Enhanced Source Integration:The GBS system shall include an additional IA approved SCI broadcast enclave, designated for SCIcontent only, with the same capabilities defined for the ROKUS enclave. [SRD ID 60500]The GBS systems shall include an additional IA approved Coalition broadcast enclave, designated forCoalition content only, with the same capabilities defined for the ROKUS enclave. (Objective) [SRD ID60550]3.6.3 Ground Mobile Receive SuiteThe following requirements apply only to the Ground Mobile Receive Suites:The Ground Mobile Receive Suites (GMRS) shall incorporate all common receive suite requirements, suchas being capable of receiving and processing the GBS downlink while on the move, requiring no specialtools/processes/skills to move from one tactical vehicle to another, and being capable of surviving the rigorsof tactical cross-country vehicular travel. (Objective) [SRD ID 61000] The Government envisions that theGBS receive software being integrated into a Joint Tactical Mobile Radio developed through a futureprocurement.The Ground Mobile Receive Suite shall be integrated, tested, and certified with the JIPM (one-way) andGBS RBM software. (Objective) [SRD ID 61101The Ground Mobile Receive Suite shall be integrated, tested, and certified with the JIPM (twoway)and GBS RBM software. (Objective) [SRD ID 61102]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-146

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 33.6.4 Broadcast Receive Suite – Terrestrial ExtensionThe following requirements apply only the Terrestrial Extension of the Receive Suites:A Broadcast Receive Suite – Terrestrial (BRS-T) shall be comprised of any GBS Receive Suite suitablymodified to include the necessary transmit capability to support a wireless terrestrial network extension ofthe broadcast to twenty or more nearby (within 5-miles distance line-of-sight) locations. [SRD ID 61500]The wireless terrestrial network extension shall meet all required accreditations and certifications requiredto be implemented as part of the GBS system. [SRD ID 61601]The wireless terrestrial network extension shall have 2-way capability to, at a minimum, support “userpull” requests. [SRD ID 61602]The following requirements apply to the wireless extension kits and may be satisfied by modifying the BDA orRDA software or by using a hybrid approach:The wireless extension kit shall provide a web-based mechanism that allows users to utilize systemfunctionality via a lightweight web browser application operating on handheld devices connected to thewireless terrestrial extension network. [SRD ID 61701]The wireless extension kit shall provide content management and filtering capabilities to support transmitand receive streams over the wireless terrestrial extension network, which operates at lower data rates thanthe GBS Broadcast streams. [SRD ID 61702]GBS Wireless Extension ArchitectureGBSTSPDISNCOREDOD Teleportw/ JIPM HubDECC SBMWGS /CommercialBDA SW may bemodified to set upwireless-specificchannelsGBSNGRTJIPM RMFigure 7: GBS Wireless Extension ArchitectureBUCClassifiedLaptop w/BCMSKG-250ClassifiedPEPEnthernetSwitchUnclassifiedPEP UnclassifiedLaptop w/ BCMSRDA SW may bemodified to supportwireless-specificcontent mgmt functions(e.g. filtering)EnthernetSwitchEnthernetSwitchConnectivity to wiredLAN, WEBS, othernetworksTactical NetworkWireless Security&Content MgmtBlack wireless modulesupports wirelessaccess control,authentication, andconfiguration mgmt forthe base stationBaseStationWireless AccessControl & AAARed wireless module extensionto meet IA requirements andsupport other wireless-specificcontent management functionsthat may not only be neededfor GBS content & services (i.e.from the LAN)3.6.5 Enhanced GIG Network-OpsThe following requirements apply only the Enhanced GIG Network Operations:The SBM shall provide advanced asymmetric networking, implementing content caching for subsequentbroadcast. (Objective) [SRD ID 62100]The SBM shall provide advanced information and content management, including detailed/indexed contentsearch capability. (Objective) [SRD ID 62101]The detailed/indexed content search capability shall be supported by a single server, per enclave. (Objective)[SRD ID 62102]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-147

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3The SBM shall provide advanced information and content management, including video caching capabilities thatare not backed-up at an alternate site or on permanent media. (Objective) [SRD ID 62200]Video caching shall be supported by a single server, per enclave. (Objective) [SRD ID 62201]Video caching shall provide 8.1 Terabytes of capacity. (Objective) [SRD ID 62202] This value is based on 3days of caching video streaming at 31 Mbps.3.6.6 Broadcast Metrics Software DevelopmentThe following requirements apply only to Broadcast Metrics:The SBM software shall respond to information provider or Information Dissemination Management (andsuccessor programs, to the extent implemented in Block-2) requests for statistics on the broadcast ofindividual products, or groups of products, by source over configurable time intervals. [SRD ID 62501]The SBM software shall respond to information provider or Information Dissemination Management (andsuccessor programs, to the extent implemented in Block-2) requests for statistics on the reception ofindividual products, or groups of products, by receive suites over configurable time intervals. [SRD ID62502]3.7 DocumentationAll software documentation, including user’s manual with operator checklists and Technical Orders, should beprovided for the purposes of instructing system operators on how to install and operate the software. TechnicalOrders must be Joint Computer–aided Acquisition and Logistics Support System (JCALS) compliant. All systemupgrades should be accompanied by corresponding documentation updates. Electronic documentation inhypertext should also be delivered. Operations and maintenance documentation and Computer ProgramIdentification Numbering System should be contained in official Air Force Technical Orders (Tos).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-148

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 34 VERIFICATION AND QUALITY ASSURANCE PROVISIONS4.1 System Verification4.2 Verification MethodsThis section provides the provisions for Verification of requirements.4.2.1 DemonstrationDemonstration is a variation of test used to verify conformance of functional characteristics to specifiedrequirements by pass/fail criteria without the use of elaborate measurement equipment. Demonstration executesthe functions of the HWCI (hardware configuration item) and CSCI (Computer Software Configuration Item)using data in a controlled situation. Observation of the predicted outputs or results demonstrates verification ofrequirements. Simulated or live data may be used.4.2.2 TestTest exercises portions system hardware and/or software in a controlled manner, to collect the data necessary toevaluate satellite, control, and network or terminal conformance to the specified requirements. Real or simulatedinput is used to exercise specific segments of the system and generate predicted outputs. Data are formallyrecorded in accordance with procedures. Detailed data analysis is performed to determined requirementcompliance. Analysis as described here is an integral part of the test method separate and distinct from theanalysis method above.4.2.3 AnalysisAnalysis is the processing of accumulated data, including the compilation of data obtained from other verificationmethods. Techniques involve interpretation or interpolation / extrapolation of analytical, simulated, or empiricaldata under defined conditions, or reasoning to show compliance with requirements. Verification by computerizedsimulations is included in this method.4.2.4 Examination/InspectionExamination is the visual inspection of an item and the comparison of pertinent characteristics with apredetermined qualitative and quantitative standard. Examination is used to verify compliance with specifiedrequirements by inspection of engineering documentation and products. For example, examination is generallynondestructive and consists of visual and auditory observation, gauging, or simple measurements without the useof precision measurement equipment. The engineering documentation and products include, but are not limited to,flow diagrams, software code, engineering drawings, engineering plans, and design specifications.4.2.5 Qualification by SimilarityRequirements for hardware and software that are similar in design and construction to the hardware and softwareof a previously verified System, for the same or similar application and environment, can be verified bysimilarity. The evaluation is documented to include: the test procedures/reports of the item to which similarity isclaimed; a description of the differences between the items, application, or environment; and the rationale forverification by similarity. This method is also used to show where existing equipment; or commercially available,reusable or GFE software, previously qualified for other applications, have demonstrated compliance to allrequirement. Re-verification for TC may be reduced in scope or deleted completely, depending upon Customerapproval of the similarity.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-149

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 34.3 Verification MatrixSRD ID10100RequirementThe GBS System shall provide the core functionalities, contained herein thisspecification’s Table 3 (Column “Function”), to address the needs of theuser/operator(s) designated for area. [SRD ID 10100]x10201102021030010400105011050210600The GBS System shall be in compliance with DoD mandated Net-Ready KeyPerformance Parameters, including satisfying 100% of all the specified Jointintegrated architecture requirements designated enterprise-level or critical activityinterfaces; services; policy-enforcement controls; data-sharing, data availability, datacorrectness, data processing and information assurance accreditation requirements inthe Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIP). [SRD ID 10201]The GBS System shall be in compliance with the DOD mandated Net-Ready KeyPerformance Parameters (KPP), including meeting GIG interoperability standards(CJCSI 3170.01C, CJCSI 6212.01D, DoDI 4630.5, and DoDI 4630.8) for theinterfaces, protocols, and equipment required to receive and disseminate video anddata from existing systems. [SRD ID 10202]The GBS system shall satisfy 100 percent of the top-level Information ExchangeRequirements (IER) designated critical to the standards specified in the IER Matrix,defined in the GBS Operational Requirements Document (KPP). [SRD ID 10300]The GBS system shall accommodate scaling, both up to 200% increases and up to50% decreases, of the following factors including but not limited to: satellites,antennas, uplink modulators, RBMs, security enclaves, broadcast load, total products,and number of each end-to-end service types. [SRD ID 10400]The GBS system shall be scalable, both up to 200% increases and up to 50%decreases, and capable to pass multiple and varied compartmented informationsources. [SRD ID 10501]The GBS system shall be scalable, both up to 200% increases and up to 50%decreases, to provide information to the user beyond the receive suite. [SRD ID10502]The GBS System is part of the GIG and shall meet GIG interoperability standards forthe interfaces, protocols, and equipment required to receive and disseminate video anddata from existing systems (Threshold). [SRD ID 10600]xxxxxxx10701The GBS System shall provide a minimum of 90 percent statistical assurance ofreceipt of all broadcast information (measured from the point where the broadcastinformation is received in the SBM and delivered at the interface between the RS’sRBM and the attached LAN). [SRD ID 10701]x10702The GBS System shall provide a minimum 95 percent statistical assurance of receiptof all broadcast information (measured from the point where the broadcast informationis received in the SBM and delivered at the interface between the RS’s RBM and theattached LAN). [SRD ID 10702]x1070511000The GBS system shall meet the Quasi-Error Free (QEF) condition under clear weatherconditions, equivalent to less than one (1) uncorrected error event per transport streamhour (corresponds to a BER between 10 -10 and 10 -11 ). [SRD ID 10705]The BDA shall use the uplink encapsulator(s) and modulator(s) at the Satellite uplinkfacilities (i.e., Teleports and PIPs). [SRD ID 11000]Xx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-150

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID1110111200113001140011500RequirementThe BDA shall support content broadcast to an RBM that is receiving from one, andup to six (6), uplink modulators. [SRD ID 11101]For all data services, the BDA shall use unique multicast addresses for each satellitedownlink, as described in Figure 5. [SRD ID 11200]The BDA shall organize broadcast content as assoiated with each RBM receiverTerminal size (e.g. small, medium, large) and assign multicast addresses that areconsistent with the DVB-S2 VCM capability of the JIPM Hub. [SRD ID 11300]The BDA shall not allow transmission of content to the RBM system root (i.e., “ C:\”).[SRD ID 11400]The BDA shall provide a capability to automatically broadcast file-based content fromsources as it arrives at the SBM. [SRD ID 11500]11600 The BDA shall support the transmission of any size file up to 20 GB. [SRD ID 11600]11700118001190011901119021190311904The BDA shall provide the set of end-to-end broadcast services listed in Table 4.[SRD ID 11700]All file-based services shall have a file-based error correction capability that allowsfiles to be efficiently reconstituted in the event that there are missed packets. [SRD ID11800]All file-based services shall have a queuing mechanism that can support prioritizationbetween files and still simultaneously service both large and small files of the samepriority. [SRD ID 11900]All file-based services shall have a queuing scheme for scheduling the queuing of aproduct at a designated time based on CJCSI 6250.01 priority. [SRD ID 11901]All file-based services shall have a queuing scheme that provides prioritizationbetween files and allocation of available bandwidth among file types of different sizes.[SRD ID 11902]All file-based services shall have a queuing delay (time for a unique, recently arrivedfile to begin transmission assuming no other similar sized files are currently in queue),for files sizes less than 1 MB, of not more than 1.0 seconds [8]. [SRD ID 11903]All file-based services shall have a queuing delay, for a file of 100 MB or less, of notmore than 5.0 seconds. [SRD ID 11904]All file-based services shall have a queuing delay, for a file of 2 GB or less, of not11905 more than 10 seconds. [SRD ID 11905]11906 All file-based services shall be available in every security enclave. [SRD ID 11906] x11907All file-based services shall address content to one, many, or all RBMs. [SRD ID11907] x12000 The FTS Service shall provide immediate file-based content delivery. [SRD ID 12000] x121001220012300The FTS Service, within an enclave, shall be capable of receiving and processingsource products that are injected from sources via FTP or equivalent. [SRD ID 12100]The Web Crawl Services shall accept scheduling information to collect web sitecontent on a scheduled basis. [SRD ID 12200]The Web Crawl Services shall provide the ability to crawl web site traffic to aspecified crawl depth. [SRD ID 12300]xxxxxxxxxxxxxxxxx12400The Web Crawl Services shall provide controls to prevent excessive collection of webcontent, including, at a minimum, the ability to limit the size of the web crawl; theability to control whether the crawler will traverse links that are off-server relative theroot URL. [SRD ID 12400]x30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-151

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID12500126001270012800129001300013101131021310313104131051310613200133001340013500136001370013800RequirementThe Web Crawl Services shall provide the capability to pass PKI client certificates inresponse to a challenge by a web server. [SRD ID 12500]The Web Crawl Services shall provide the ability to collect HTTP and HTTPS. [SRDID 12600]The Web Crawl Services shall ensure that collected content can be viewed organically(using existing RBM software) on the RBM without the need to repopulate a webserver. [SRD ID 12700]The Web Crawl Services shall implement techniques to minimize impacts to crawledweb servers (e.g., comply with robots.txt). [SRD ID 12800]The FTS with Management Service shall provide a web services based interface forinjecting content into the broadcast. [SRD ID 12900]The FTS with Management Service shall provide transmission status for individualproducts including feedback on RBM reception if available. [SRD ID 13000]The FTS with Management Service shall provide sources the ability to access thefunctionality to cancel transmission of products not yet broadcast. [SRD ID 13101]The FTS with Management Service shall provide sources the ability to access thefunctionality to delete products from the system not yet broadcast. [SRD ID 13102]The FTS with Management Service shall provide sources the ability to access thefunctionality to estimate transmission time for a product. [SRD ID 13103]The FTS with Management Service shall provide sources the ability to access thefunctionality to re-transmit source products. [SRD ID 13104]The FTS with Management Service shall provide sources the ability to access thefunctionality to request a return receipt (as available) from fully connected receivesuites. [SRD ID 13105]The FTS with Management Service shall provide sources the ability to access thefunctionality that provides the list of authorized receive suites available to the source.[SRD ID 13106]The Source Managed Tunneled Content Service shall provide the ability to routesource streaming content directly into the broadcast stream without any additionalprocessing. [SRD ID 13200]The Source Managed Tunneled Content Service shall provide local (within the BDA)bandwidth management control that can restrict the amount of bandwidth a specificsource receives to be commensurate with the COCOM TIM priorities and bandwidthlimitations placed on source. [SRD ID 13300]The Source Managed Tunneled Content Service shall be backwards compatible withexisting source managed users that currently use Fazzt Power Publisher 7.1 or providea functionally similar application for these sources. [SRD ID 13400]The Mirrored FTS Services shall provide a capability to replicate all content of adirectory including all sub-directories and their content at the SBM to the RBM. [SRDID 13500]The Mirrored FTS Services, after the initial directory content is broadcast andreplicated, shall provide the capability to only broadcast incremental changes in theSBM directory. [SRD ID 13600]The Mirrored FTS Services shall provide a capability to select the periodicity of theincremental updates. [SRD ID 13700]The Video Services shall have the capability to ingest MPEG-2 or MPEG-4 H.264encoded video streams and rebroadcast the streams as a different multicast addressusing the same encoding algorithm. [SRD ID 13800]xxxxxxxxxxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-152

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement1390014000The Video Services shall be capable of transcoding videos from one format to another,specifically supporting at a minimum, the conversion from MPEG-2 to MPEG-4H.264, MPEG-2 over ATM to MPEG-2 over IP, and MPEG-2 over ATM to MPEG-4over IP. [SRD ID 13900]The Video Services shall be capable of transrating videos from one encoding rate toanother. [SRD ID 14000]xx1410014200The Video Services shall be capable of converting video stream resolutions,specifically at a minimum, the conversion from MPEG-2 HD to MPEG-2 SD andMPEG-4 H.264 HD to MPEG-4 H.264 SD. [SRD ID 14100]The Video Services shall be capable of transmitting metadata in pre-encoded streams,if present (e.g. Closed Captioning Line 21, KLV). [SRD ID 14200]xx14300The Video Services shall be capable of encoding native analog or digital streams andany associated metadata as MPEG-2 SD, MPEG-2 HD, MPEG-4 H.264 SD or MPEG-4 H.264 HD formatted video. [SRD ID 14300]x14400The Video Services shall be able to simultaneously encode at least 10 analog videostreams and be capable of scaling to encode 25 analog video streams. [SRD ID 14400]x14500The Video Services shall have the capability to simultaneously support three modes ofvideo operations: Transcoding/Transrating, Remapping, and Encoding. [SRD ID14500]x14510The Video Services, at a minimum, shall simultaneously transcode/transrate eighteen(18) videos: 10 videos for the Secret enclave and 4 videos each for Unclassified andROKUS enclave. [SRD ID 14510]x145111452014521145301453114600147001480014900The Video Services, at a minimum, shall simultaneously transcode/transrate thirty-six(36) videos: 20 videos for the Secret enclave and 8 videos each for Unclassified andROKUS. [SRD ID 14511]The Video Services, at a minimum, shall simultaneously remap one hundred (100)videos: 80 videos for the Secret enclave, 14 videos for Unclassified and 6 videos forROKUS. [SRD ID 14520]The Video Services, at a minimum, shall simultaneously remap two hundred (200)videos: 160 videos for the Secret enclave, 28 videos for Unclassified and 12 videos forROKUS. [SRD ID 14521]The Video Services, at a minimum, shall simultaneously encode eighteen (18) videos:10 videos for the Unclassified enclave and 4 videos each for Secret and ROKUS.[SRD ID 14530]The Video Services shall simultaneously encode thirty-six (36) videos: 20 videos forthe Unclassified enclave and 8 videos each for Secret and ROKUS. [SRD ID 14531]The Video Services shall support use of the same multicast addresses for two or moresatellite downlinks. [SRD ID 14600]The Streaming Packet Service shall support the processing of IP multicast data streamsat data rates up to 20 Mbps each. [SRD ID 14700]The Streaming Packet Service shall support the passing of previously encrypted IPdata at levels up to and including TS/SCI. [SRD ID 14800]The Streaming Packet Service shall accept Encapsulated Security Payload (ESP)packets from a source and be able to route them over the broadcast. [SRD ID 14900]xxxxxxxxx15000The EPG shall provide three days of broadcast history, specific to each individualreceive suite that will allow the RBMs to determine what broadcast content that wasintended for them was not received. [SRD ID 15000]x30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-153

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID151001520015300154001550015600RequirementThe EPG shall provide a listing of all GBS broadcast videos and relevant receptioninformation such as multicast IP addresses, port numbers, etc. [SRD ID 15100]The EPG shall be provided for each enclave and be available over-the-air and via theappropriate network connection. [SRD ID 15200]The EPG shall provide a web announcements page that allows GBS operationsmanagers and TIMs to provide daily GBS updates. [SRD ID 15300]The Heartbeat shall provide a unique identifier on each broadcast stream to identifythe associated satellite and uplink modulator. [SRD ID 15400]The Heartbeat shall include a free form text message capability of at least 256 fullcharacters that is displayed as a banner upon reception. [SRD ID 15500]The Heartbeat shall use reports received from RBMs as the primary means fordetermining which RBMs are active and which satellite uplink modulator(s) are beingreceived by each RBM. [SRD ID 15600]The Tuning Guide shall include all necessary information required to tune each GBS x15700 RBM to the appropriate satellite and begin reception of products. [SRD ID 15700]15801 The Tuning Guide shall be Unclassified. [SRD ID 15801] x15802 The Tuning Guide shall be provided for each enclave. [SRD ID 15802] x158031590016000161001620016300164001650016600167001680016900The Tuning Guide shall be available over-the-air and via all network connections.[SRD ID 15803]The Tuning Guide shall allow the SBM Operator to update the NIPRNET TuningGuide within 5 minutes after being notified of JIPM updates by the Tactical NetworkController (TNC). [SRD ID 15900]The Tuning Guide shall allow the SBM Operator to update the SIPRNET and ROKUSTuning Guide within 2 hours of being notified of JIPM updates by the TNC. [SRD ID16000]The Tuning Guide shall include all scheduled changes to the tuning plan. [SRD ID16100]The Content Catalog shall include a list of enclave specific authorized content andtheir descriptions that are available for “user pull” from the SBM. [SRD ID 16200]The Content Catalog shall be able to display the SBM Content Catalog over theapplicable DISN network and allow selection and indications of the relative priority ofproducts for delivery to selected RBMs. [SRD ID 16300]The Work Flow Process shall provide access controls that prevent unauthorized usersfrom creating, modifying, or deleting information entered by other users. [SRD ID16400]The Work Flow Process shall include, but not be limited to, defining groups andgranting/ authorizing access to other users within a group to database entries. [SRD ID16500]The Work Flow Process shall be configurable by the SBM operator to allow end useraccess to only the information (e.g., forms and reports) that are allowed by theCOCOM TIM. [SRD ID 16600]The BDA Usability shall provide a means for updating displayed information toensure access to the latest available data. [SRD ID 16700]The BDA Usability shall provide confirmations, either visual or audible, of user inputsand actions. [SRD ID 16800]The BDA Usability shall provide status or mode indications during computations,downloads, or processing activity. [SRD ID 16900]xxxxxxxxxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-154

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID1700017100172001730017400175001800018100182001830018400RequirementThe BDA Usability shall support at least 250 concurrent users (i.e., GBS OperationsManagers, TIM, Content Providers, End User with reachback), per enclave, withoutdegradation of service. [SRD ID 17000]The BDA Usability shall provide meaningful descriptor fields relevant to RBMs andproducts to enable convenient management (e.g., sorting, searching, and filtering) ofdisplayed information. [SRD ID 17100]The BDA Usability shall employ knowledge management techniques (e.g., broadcastefficiency metrics and naming conventions). [SRD ID 17200]The SBM shall support the Session Description Protocol for content provider entry ofvideo descriptors. [SRD ID 17300]The BDA shall allocate bandwidth from services not currently in use to other activeservices within each enclave. [SRD ID 17400]The BDA shall be capable of automatically reallocating bandwidth within a securityenclave between streaming and data services based on changes in service load. [SRDID 17500]The BDA shall be capable of generating unique broadcast content for each IPMulticast Stream. [SRD ID 18000]The BDA shall dynamically share and re-allocate bandwidth for data products betweenenclaves, using flow control feedback from the JIPM hub. [SRD ID 18100]The BDA shall be a single integrated application, able to operate identically onmultiple security enclaves, and support File-based Multicast Content delivery and xStreaming Services. [SRD ID 18200]The BDA shall operate Fazzt 7.1 and higher versions, or equivalent software. [SRD ID18300] xThe BDA shall be installed at the DECC locations and operate on a DECC approvedOS (Linux, MS, Unix, etc). [SRD ID 18400]xxxxxxxxx1860018700188001890019000The BDA shall be backwards compatible with the legacy receive suite software (i.e.,receive unclass/class files, streaming products [video, tunneled data, Power Publisher,etc], EPG displays, heartbeats, and web content) while supporting RBM presencesdisplays and over-the-air updates. [SRD ID 18600]The BDA shall simultaneously support broadcasts at both JIPM and non-JIPM enableduplink facilities. [SRD ID 18700]The BDA shall support Microsoft Internet Explorer browser version 5.5 and higherversions supported by Microsoft. [SRD ID 18800]The BDA shall support Mozilla Firefox version 1.5 and higher versions that aresupported by Mozilla. [SRD ID 18900]The BDA shall adjust transmit data rates, within each enclave, with minimalinterruption to the broadcast (e.g., 1 minute or less). [SRD ID 19000]xxxxx19100The BDA shall allow the SBM to share and reallocate available bandwidthdynamically, in near-real time among various users, information products, multi-mediatypes (data, video, and audio), and security release levels without interruption to thebroadcast. [SRD ID 19100]x1920019300The BDA shall allow the SBM to dynamically, in near-real time, allocate a portion ofthe bandwidth to insert lower priority, unscheduled information products whereunused bandwidth exists. [SRD ID 19200]The BDA shall pre-empt files when higher priority/precedence files are available forbroadcast. [SRD ID 19300]xx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-155

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID194001950019600197001980119900200002000120200205002050120600207002080020900210002110021150RequirementThe BDA shall resume transmission of products that were preempted without loss ofdata. [SRD ID 19400]The BDA shall provide a capability for operators to set bandwidth allocations betweensecurity enclaves that cannot be overridden by automatic controls. [SRD ID 19500]The BDA shall automatically delete ingested files after a minimum of 3 days. [SRD ID19600]The BDA shall store all ingested data files for at least 3 days to provide the end usersthe ability to request file rebroadcast. [SRD ID 19700]The BDA shall allow the SBM to automatically protect and store queued informationand systematically shut down after loss or fluctuations of external power. [SRD ID19801]The BDA shall process User Pull request based on current broadcast profile priorities.[SRD ID 19900]The GBS Network Management Software (NMS) shall be capable of automaticallyalerting local GBS operators of changes in SBM network element status or criticalfailures of systems that impact the broadcast of data via audible alarms, email, pages,and pop-up alarms in a manner consistent with the rules of the security enclave that theNMS is managing. [SRD ID 20000]The BDA shall provide automated over-the-air (OTA) software and InformationAssurance updates to GBS JPO procured RBMs. [SRD ID 20001]The BDA shall respond to TIM authorized re-broadcast requests based on currentbroadcast profile priorities and the missed files reports. [SRD ID 20200]The Operations Management Activity (OMA) shall provide the information and toolsnecessary for coordinating the use of satellite and uplink resources between the SBM,the Teleport Sites, the UFO PIPs, RSSC, WSOC, and other entities sharing GBSresources. [SRD ID 20500]The Operations Management Activity (OMA) shall provide the information andtools necessary accepting system status information and displaying the status ofcritical components to the help desk. [20501]The OMA shall provide a capability for the GBS operations managers to setbandwidth allocations within a security enclave between streaming and data services.[SRD ID 20600]The OMA shall allow the GBS operations managers to regulate bandwidth allocationfor source encrypted streaming packets and integrate their information into thebroadcast based upon priorities and coverage to intended users. [SRD ID 20700]The OMA shall allow the GBS operations managers to enter or remove authorizedRBMs from the broadcast. [SRD ID 20800]The OMA shall allow the GBS operations managers to assign streaming and videoproducts to one or more specific satellite downlinks. [SRD ID 20900]The OMA shall allow the GBS operations managers to enter authorized informationproviders into the broadcast. [SRD ID 21000]The GBS System Monitoring Service shall provide SBM information accessible via aweb browser over SIPRNET and via an open, defined Web Services SIPRNETinterface. [SRD ID 21100]The GBS System Monitoring Service shall include the capability to collate and formatselected SBM information and audit logs into historical textual and graphical reports.[SRD ID 21150]xxxxxxxxxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-156

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement21200The GBS System Monitoring Service shall provide reporting status, key metrics,and configurable alerts of key SBM system elements and GBS usage statistics.[SRD ID 21200]]x2120121202The GBS System Monitoring Service shall monitor and report the operationalstatus of key SBM elements (e.g., ingest, DMZ, enclave servers, applications andsoftware processes, encryption, and ingest and egress network connections). [SRDID 21201]This Current SBM status information shall be current to within 5 minutes. [SRD ID21202]xx21300The GBS System Monitoring Service shall provide status of key RBM systemelements and GBS usage statistics [SRD ID 21300]x21301The GBS System Monitoring Service, shall provide the status of every activeRBM being served by the broadcast, as determined from the RBM Status Serviceand the RBM Status Proxy Service. [SRD ID 21301]x2130221303The GBS System Monitoring Service, shall provide the capability to excludeRBMs based on operational security constraints. [SRD ID 21302]This Current RBM status information shall be current to within 10 minutes. [SRD ID21303]xx21400The GBS System Monitoring Service shall provide status of key SBM systemelements and GBS usage statistics that includes, but is not limited, to the BroadcastCoverage Map. [SRD ID 21400]x21401The GBS System Monitoring Service, with respect to the Broadcast Coverage Map,shall generate a graphical display of the current GBS geographical satellite coveragefootprints. [SRD ID 21401]x2140221403The GBS System Monitoring Service, with respect to the Broadcast Coverage Map,shall identify the associated satellite and uplink modulator(s) and the uplink anddownlink broadcast frequencies available within each footprint. [SRD ID 21402]The GBS System Monitoring Service, with respect to the Broadcast Coverage Map,shall include access to a tabulation of all active RBMs within each footprint. And agraphical display for RBMs with known locations [SRD ID 21403]xx214042140521500The GBS System Monitoring Service, with respect to the Broadcast Coverage Map,shall provide the capability to exclude RBMs based on operational securityconstraints. [SRD ID 21404]The GBS System Monitoring Service, with respect to the Broadcast Coverage Map,shall display the geographical location for all active RBMs (whose geographicallocations are already known) except as precluded by operational security constraints.[SRD ID 21405]The GBS System Monitoring Service shall provide status of key SBM systemelements that includes, but is not limited to, the GBS Usage Statistics. [SRD ID21500]xxx2150121502The GBS System Monitoring Service, with respect to GBS Usage Statistics, shallstore, process, compile historical information, and generate usage statistics overselectable time intervals for each enclave. [SRD ID 21501]The GBS System Monitoring Service, with respect to GBS Usage Statistics, shallinclude historical information parameters, but are not limited to, broadcast type (e.g.video, streaming packet, files), rebroadcast requests, and by user pull requests. [SRDID 21502]xx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-157

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID2150321601216022170021800219002200022100222002230022400225002260022700228002290022930RequirementThe GBS System Monitoring Service, with respect to GBS Usage Statistics, shallprovide the ability to generate, in the Secret enclave, a merged usage statistical reporton a daily basis. [SRD ID 21503]The NETOPS Reporting Services shall provide selectable elements from the CurrentSBM Status monitoring service to the DISN Integrated Network Management System(INMS). [SRD ID 21601]The NETOPS Reporting Services shall provide selectable elements from the CurrentRBM Status monitoring service to the DISN Integrated Network Management System(INMS). [SRD ID 21602]The NETOPS Reporting Services shall provide a capability for client access to theRNOSC INMS system for the purpose of receiving and viewing INMS network maps.[SRD ID 21700]The NETOPS Reporting Services shall provide the capability to filter and report GBSsystem trouble tickets to the Trouble Management System (TMS). [SRD ID 21800]The Uplink Modulator Planning Services shall allow a GBS operational manager orTIM to manually associate specific RBMs with uplink modulators on all GBSsatellites (WGS, UFO, commercial, etc.). [SRD ID 21900]The Uplink Modulator Planning Services shall provide the capability to process theSatellite Access Authorization (SAA) and configure the system to the expectedsatellite configuration. [SRD ID 22000]The Bandwidth Utilization and Configuration Management Services shall provide adisplay of the current broadcast multicast streams by uplink modulator. [SRD ID22100]The Bandwidth Utilization and Configuration Management Services shall provide adisplay of the current broadcast multicast stream allocations between data andstreaming services and a breakdown of its constituent parts. [SRD ID 22200]The Bandwidth Utilization and Configuration Management Services shall acceptmanual inputs from the GBS operations manager that allow control of the bandwidthallocations between multicast streams in case of the loss of flow control feedback fromthe JIPM hub. [SRD ID 22300]The Queue Status Services shall provide the GBS Operations Manager or TIM with adisplay of current status within the queue for each uplink modulator. [SRD ID 22400]The Queue Status Services shall provide the GBS Operations Manager or TIM with adisplay of the statistics of individual products including but not limited to: list of filesdelivered, time of delivery, and size of files. [SRD ID 22500]The OMA shall provide a status display of the streaming data for each uplinkmodulator including, but not limited to, a list of stream names, type of stream, datarate, and the uplink modulators over which the streams are being broadcast. [SRD ID22600]The OMA shall provide a report showing the collection statistics and status of eachweb product. [SRD ID 22700]The Mission Priority Services shall accept manual entry of pertinent information fromthe GBS Mission Requests (GMR). [SRD ID 22800]The Mission Priority Services shall prioritize the broadcast queue based on usermission as described in the CJCSI 6250.01 and the relative priority of products beingused to support that mission. [SRD ID 22900]The Mission Priority Services shall provide an interface to identify the GBS productsneeded to identify the GBS products needed to support specific user missions. [SRDID 22930]xxxxxxxxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-158

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement22950The Mission Priority Services shall provide an interface to assign a relative priority toeach product user within a user mission. [SRD ID 22950]x2350023600240002405024100The Mission Management Services shall display the defined data stream (file andstreaming) and allow the TIM to select and indicate the relative priority of datastreams for broadcast. [SRD ID 23500]The Mission Management Services shall allow the TIM to associate data streams toone or more RBM. [SRD ID 23600]The system shall allow a content provider to view the current status of products sent tothe SBM. [SRD ID 24000]Per enclave, the system shall provide the capability to test the broadcast dataconnectivity, protocols, security infrastructure, and application interfaces between anauthorized content provider and SBM with appropriate measures to ensure such testingdoes not connect to the broadcast. [SRD ID 24050]The system shall provide the capability for the content provider to determine whichRBMs will receive a product if sent. [SRD ID 24100]xxxxx242002430024400The system shall provide the necessary information for a content provider to determinewhich RBMs are accessible on which uplink modulators and the associated SourceManaged Tunneled Content Service multicast addresses. [SRD ID 24200]The system shall allow an authorized content provider to enter detailed data describingcontent provider and product information. [SRD ID 23000]The system shall allow an authorized content provider to preclude their products frombeing displayed in the content catalog. [SRD ID 24400]xxx2450024600246502470024800The system shall provide an interface where a source can provide one or moreUniform Resource Locator (URL) addresses that will be displayed at the RBM forsimplified access to the source site. [SRD ID 24500]The system shall provide a content provider with a display of the current status of fileproducts sent by the content provider. [SRD ID 24600]The system shall not provide a content provider the current status of file products sentby another content provider unless authorization is provided by the TIM. [SRD ID24650]The system shall provide a content provider with display of the current status of fileproducts sent to the SBM for delivery to a specific RBM. [SRD ID 24700]The broadcast segment shall provide both the primary and COOP SBM capability toindependently support the global broadcast. [SRD ID 24800]xxxxx24900The broadcast segment shall replicate 100 percent of the system management andsystem configuration parameters at the COOP site every thirty (30) minutes [TBR-32]to facilitate a transfer of SBM operations. [SRD ID 24900]x25000For a scheduled transfer, the broadcast segment shall transfer SBM operations to theCOOP site within 1 minute. [SRD ID 25000]x25100The broadcast segment shall be capable of ingesting a minimum of 300 Mbps of filesper enclave (Secret and Unclassified). [SRD ID 25100]x25200The broadcast segment shall be capable of ingesting a minimum of 400 Mbps of IPdata and video streams per enclave (Secret and Unclassified). [SRD ID 25200]x25300The broadcast segment shall be capable of ingesting a minimum of 200 Mbps of filesin the ROKUS enclave. [SRD ID 25300]x25400The broadcast segment shall be capable of ingesting a minimum of 200 Mbps of IPdata and video streams in the ROKUS enclave. [SRD ID 25400]x30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-159

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID RequirementThe broadcast segment shall support the 10 satellites, 100 downlink beams, 56aggregated streams (each consisting of multiple multicast streams to be injected by aspecific modulator at the JIPM hub), 5000 RBMs, 2500 subscriptions (content folders25500and IP streams), and 250 content providers. [SRD ID 25500]25600 The broadcast segment shall be capable of supporting Ipv6. [SRD ID 25600] x2570025800The broadcast segment shall incorporate Ipv6 components, as they becomecommercially available. [SRD ID 25700]The broadcast segment shall be scalable to accommodate a 50% increase in thenumber of satellites, downlink beams, multicast streams, RBMs, subscriptions (contentfolders and IP streams), and content providers. [SRD ID 25800]The broadcast segment shall be capable of supporting a nominal data rate of 72 Mbps x25900 for each group of multicast streams per modulator. [SRD ID 25900]26000 The broadcast segment shall include a DIACAP compliant DMZ. [SRD ID 26000] x2610026200The broadcast segment shall be capable of supporting any mix of file or streaming data(all file, all streaming, any mix of the two) on the group of multicast streams permodulator. [SRD ID 26100]In the event backup power fails, the broadcast segment shall provide automatic systemprotection for equipment in order to logically and systematically shut down or rapidlyresume broadcast operations after loss or fluctuations of external power. [SRD ID26200]xxxxx263002640030000301013010230103301043010530106301073100031101The broadcast segment, in the event of power failures, shall take advantage of facilityprovided uninterrupted power sources. [SRD ID 26300]The broadcast segment shall provide the capability to key GBS specific cryptographicequipment manually. [SRD ID 26400]The RDA status elements shall include, but are not limited to the RBM Heartbeat.[SRD ID 30000]The RBM Heartbeat shall report each active broadcast received by each RBM, toinclude multiple uplink modulators on the same or different satellites. [SRD ID 30101]The RBM Heartbeat shall use a unique identifier on each received broadcast to reportthe associated satellite and uplink modulator. [SRD ID 30102]For unclassified enclaves, the RBM Heartbeat shall include a message field forreporting broadcast reception quality when such information is locally available (e.g.from a broadcast RBM). [SRD ID 30103]The RBM Heartbeat shall be displayed on every RBM webpage along with a banner.[SRD ID 30104]The RBM Heartbeat banner display shall terminate upon the deletion of the bannermessage within the heartbeat. [SRD ID 30105]The RBM Heartbeat shall indicate a loss of the heartbeat signal via the displayed iconif any heartbeat is not received for an extended period. [SRD ID 30106]Outside a normal shutdown, the RBM shall provide the option to generate and send anemail to the RBM Administrator to indicate a loss of the heartbeat signal. [SRD ID30107]The RDA status elements shall include, but are not limited to, the Missed Files Report.[SRD ID 31000]The Missed Files Report shall list the files that were not received since the last statusreport, as determined by comparing the files received correctly with the broadcasthistory information from the broadcast. [SRD ID 31101]xxxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-160

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID311023200032101330003310133102RequirementThe Missed Files Report shall include a summary of the percentage of files receivedcorrectly. [SRD ID 31102]The RDA status elements shall include, but are not limited to, The IAVA Status report.[SRD ID 32000]The IAVA Status report shall provide the current state of IAVA patches that have beeninstalled, including the date and time of installation. [SRD ID 32101]The RDA status elements shall include, but are not limited to, The ApplicationInformation report. [SRD ID 33000]The Application Information report shall provide information about the RBMapplications for use in system troubleshooting and Help Desk operations. [SRD ID33101]The Application Information report shall include, but is not limited to vendor, version,patches installed, configuration parameters, and memory and CPU usage statistics.[SRD ID 33102]34000The RDA status elements shall include, but are not limited to, The RBM Profile report.[SRD ID 34000]x34101 The RBM Profile shall be entered via a web browser. [SRD ID 34101] x34102The RBM Profile shall include, but not limited to: geographical location, satelliteuplink modulator(s) providing coverage, receive terminal class (e.g., Small, Medium,Large), and RBM active times. [SRD ID 34102]xxxxxxx351003520035300For each RBM with reachback connectivity (either directly via broadcast satellitetransmission segment or via an alternate IP network), the RDA shall provide status ofbroadcast reception and key RBM operating and configuration parameters to the SBM.[SRD ID 35100]For each RBM with reachback connectivity (either directly via broadcast satellitetransmission segment or via an alternate IP network), the RDA shall be capable ofdisplaying the most recently received status information locally via web browserregardless of reachback connectivity status. [SRD ID 35200]For each RBM with reachback connectivity (either directly via broadcast satellitetransmission segment or via an alternate IP network), the RDA shall provide statusseparately for each security level. [SRD ID 35300]xxx35400For each RBM with reachback connectivity (either directly via broadcast satellitetransmission segment or via an alternate IP network), the RDA shall allow the statusreportinginterval at the RBM to be configurable (to include but not be limited) to onceper minute. [SRD ID 35400]x355003560035800For each RBM with reachback connectivity (either directly via broadcast satellitetransmission segment or via an alternate IP network), the RDA shall allow the statusreportingcapability to be suppressed when required by operational constraints. [SRDID 35500]For each RBM with reachback connectivity (either directly via broadcast satellitetransmission segment or via an alternate IP network), the RDA shall provide RBMStatus via an open, defined Web Services interface at the SBM, with appropriate IAattributes. [SRD ID 35600]Specific to OTA Software and IA Updates only, the RDA shall have the ability toallow the end user to select if and when they will install the automated IA updates.[SRD ID 35800]xxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-161

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID35900360003610036200363003640036500RequirementSpecific to OTA Software and IA Updates only, the RDA shall process OTA softwareupdates and include a mode that overrides the end user control for critical updates.[SRD ID 35900]The RDA shall be functionally compatible with the existing IP broadcast by being ableto receive all existing over-the-air GBS services. [SRD ID 36000]The RDA shall be functionally compatible with the existing IP broadcast by being ableto auto-forward content using FTP and FTPS similar to the existing receive suite sothat the system can be interchanged with existing receive suites. [SRD ID 36100]The RDA shall be functionally compatible with the existing IP broadcast by being ableto receive and process the GBS heartbeat. [SRD ID 36200]The RDA shall be functionally compatible with the existing IP broadcast by being ableto receive and process the GBS Electronic Program Guide. [SRD ID 36300]The RDA shall be functionally compatible with the existing IP broadcast by being ableto display the Tuning Guide generated by the SBM. [SRD ID 36400]The RDA shall be functionally compatible with the existing IP broadcast by being ableto provide the receive suite presence display required information. [SRD ID 36500]37000The RDA shall be portable between all supported Microsoft Windows operatingsystems. [SRD ID 37000]x37010The RDA shall operate on a Linux platform, as designated by the Government.(Objective) [SRD ID 37010]37011The Linux RDA application version shall meet all the requirements of the MicrosoftWindows RDA version. (Objective) [SRD ID 37011]37012The Linux RDA application version shall be controllable and operable from a webbasedHTTPS interface without requiring a keyboard, mouse, or display to operate.(Objective) [SRD ID 37012]37013The Linux RDA application version shall, at a minimum, be based on an Intel X86-based architecture. (Objective) [SRD ID 37013]37100 The RDA shall be capable of supporting Ipv6. [SRD ID 37100] xxxxxxxx372003730037400The RDA shall be able to display the SBM Content Catalog and allow an end user toselect and indicate the relative priority of products for delivery to their RBM and otherRBMs as indicated in their request (User Pull – This applies to RBMs that havereachback connectivity or users with alternate communications means available toaccess the content catalog). [SRD ID 37200]The RDA shall provide a subscription request capability for a product in the catalog.[SRD ID 37300]The RDA shall be delivered as a single disk install with only minimal interactionrequired by the end user/installer (no training required to perform installation). [SRDID 37400]xxx3750037600377003790038000The RDA shall be capable of being hosted on user specified alternative computerplatforms after the alternative platform is certified compatible with GBS and added toa Qualified Product List (QPL). [SRD ID 37500]The RDA shall be capable of operating in an unattended mode, except duringconfiguration changes made after initial setup and during installation of OTA and IAupdates. [SRD ID 37600]The RDA shall be compliant, certified, and accredited in accordance with the DoDI8510.bb, DIACAP Instructions. [SRD ID 37700]The RDA shall provide for separation of broadcast content from user data on RBMstorage devices. [SRD ID 37900]The RDA shall provide multiple web-based mechanisms for finding delivered contentsuch as indexed search, content sorting, or filename based search. [SRD ID 38000]xxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-162

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement381003820038300The RDA shall support the forwarding of multicast packets based upon IGMP V3protocols. [SRD ID 38100]The RDA shall support the manual configuration of forwarding multicast over thelocal area network without the need for IGMP protocols. [SRD ID 38200]The RDA shall provide a mechanism for determining what files or streams werereceived; which files or streams were intended for their RBM, but were missed. [SRDID 38300]xxx38400385003860038700The RDA shall automatically execute the use of automated file cleanup (to ensurethere is adequate storage to run the system); automated disk de-fragmentation;automated database maintenance or any other mechanism required to ensure long termperformance of the software. [SRD ID 38400]The RDA shall provide a mechanism for providing system statistics and reports thatallow end users to see the performance of the receive system. [SRD ID 38500]The RDA shall support Microsoft Internet Explorer browser version 5.5 and higherversions supported by Microsoft. [SRD ID 38600]The RDA shall support Mozilla Firefox version 1.5 and higher versions supported byMozilla. [SRD ID 38700]xxxx38800389003900039100The RDA shall provide a capability to filter broadcast file content by file extension(e.g. *.exe) to prevent certain types of files from being received by the RBM. [SRD ID38800]The RDA shall be capable of receiving all services provided by the uplink. [SRD ID38900]The RDA shall support the processing of data at variable data rates according to thebeam and terminal combinations. [SRD ID 39000]The RDA shall support the simultaneous processing of multicast streams from at leasttwo downlink modulators. [SRD ID 39100]xxxx39200393003940039500The RDA shall provide a web-based mechanism that allows locally connected (i.e., viaLAN) users to utilize the system functionality via a web browser over a local network.[SRD ID 39200]The RDA shall ensure that broadcast products cannot be written to an absolutedirectory path. [SRD ID 39300]The Auto Push functionality shall deliver products via FTP (act as FTP client) to enduser systems. [SRD ID 39400]The Auto Push functionality shall deliver products via FTPS or SFTP (act as FTPS orSFTP client) to end user systems. [SRD ID 39500]xxxx39600397003980039900The Auto Push functionality shall allow for pre-configured ordering of relatedproducts based on EPG information or other available metadata such as data source,content type, product information, etc. [SRD ID 39600]The Auto Push functionality shall provide the capability to delete, modify, and addsubscriptions via a web interface. [SRD ID 39700]The Auto Push functionality shall maintain directory structures for Auto Pushedcontent. [SRD ID 39800]The Auto Push functionality shall support multiple end users subscriptions to the samecontent at the same location but to different end user machines. [SRD ID 39900]xxxx40000The Auto Push functionality shall be available for any level of content hierarchy ororganization. [SRD ID 40000]x30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-163

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement4010040200The Auto Push functionality shall be configurable via a web browser (HTTPS) from anetwork-connected machine. [SRD ID 40100]The Web Browser content management functionality shall support the user-pull ofreceived content from their web browser over a local area network. [SRD ID 40200]xx40300404004060040700408004090041000The Web Browser content management functionality shall support Microsoft InternetExplorer browser version 5.5 and higher versions supported by Microsoft [SRD ID40300]The Web Browser content management functionality shall support Mozilla Firefoxversion 1.5 and above. [SRD ID 40400]The Web Browser content management functionality shall display the ElectronicProgram Guide. [SRD ID 40600]The Web Browser content management functionality shall support HTTPS. [SRD ID40700]The Video functionality shall provide means to convert IP video to NTSC and PAL,allowing video to be viewed on external hardware. [SRD ID 40800]The Video functionality shall include a capability of viewing the transmitted videofrom the uplink on the local RBM. [SRD ID 40900]The Video functionality shall provide IP video recording capability for at least 30minutes, at a minimum rate of 3 Mbps so that incoming video streams can be timeshifted. [SRD ID 41000]xxxxxxx4110042000The RDA shall provide RBM Local Monitoring functionality that displays a statisticspage for LAN connected users so that they can see the status of incoming files. [SRDID 41100]For RBMs with reachback, the Reception Management functionality shall allow anend user to enter RBM profile information. [SRD ID 42000]xx4210042200For RBMs with reachback, the Reception Management functionality shall allow anend user to request the rebroadcast of products from the Broadcast ManagementSegment. [SRD ID 42100]For RBMs with reachback, the Reception Management functionality shall allow anend user to view the system-tuning guide. [SRD ID 42200]xx4230043500For RBMs with reachback, the Reception Management functionality shall allow anend user to pull content from either SBM’s Content Catalog or via source URL. [SRDID 42300]For RBMs using a proxy, the Reception Management functionality shall include acapability for manual entry of key RBM information by a proxy. [SRD ID 43500]xx4360043700441504450044600For RBMs using a proxy, the Reception Management functionality shall allow keyinformation to be entered via a web browser. This information may include but is notlimited to: geographical location, satellite uplink modulator(s) providing coverage,RBM Active times, IAVA status, receive terminal class (e.g., Small, Medium, Large),and RBM Application Information. [SRD ID 43600]For RBMs using a proxy, the Reception Management functionality shall include eachRBM in the broadcast(s) using the best information available even if some parametersare not entered by the proxy. [SRD ID 43700]The broadcast segment hardware and software shall operate within the DECCinfrastructure. [SRD ID 44150]The SBM to DECC Facility interfaces shall comply with [the TBD-1] establishedDECC interface standards and policies. [SRD ID 44500]The SBM to DECC Facility interfaces shall be capable of traversing the DECCfirewalls for routing across the DISN to the uplink facilities. [SRD ID 44600]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-164xxxxx

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement447004480044900The DISN to SBM DMZ interfaces shall accept various files and streaming productsfrom sources using standard internet protocols that include but are not limited toEncapsulated Security Payload (ESP), Secure Shell (SSH), Simple Mail TransferProtocol (SMTP), Simple Mail Transfer Protocol Secure Sockets Layer (SMTPSSL)Domain Name Server (DNS), Hyper Text Transfer Protocol (HTTP), Hyper TextTransfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), File TransferProtocol over Secure Sockets Layer (FTPS), SSH File Transfer Protocol (SFTP),Message Hopper, MSCHAT, Power Publisher, and Multicast. [SRD ID 44700]The DISN to SBM DMZ interfaces shall allow ingest of source encrypted TS/SCItraffic via tunneled IP streams. (KPP) [SRD ID 44800]The DISN to SBM DMZ interfaces shall allow configuration inputs and operationsmanagement using HTTPS with DOD PKI certificates. [SRD ID 44900]xxx4500045100452004530045400460004610046200463004640046500The SBM DMZ to SBM interfaces shall accept various files and streaming productsfrom the SBM DMZ using standard internet protocols that include but not limited toEncapsulated Security Payload (ESP), Secure Shell (SSH), Simple Mail TransferProtocol (SMTP), Simple Mail Transfer Protocol Secure Sockets Layer (SMTP SSL)Domain Name Server (DNS), Hyper Text Transfer Protocol (HTTP), Hyper TextTransfer Protocol Secure (HTTPS), File Transfer Protocol (FTP), File TransferProtocol over Secure Sockets Layer (FTPS), SSH File Transfer Protocol (SFTP),Message Hopper MSCHAT, Power Publisher, TACACS, NTP, SNMP Traps, SYSLog, and Multicast. [SRD ID 45000]The SBM DMZ to SBM interfaces shall allow ingest of source encrypted TS/SCItraffic via tunneled IP streams (KPP). [SRD ID 45100]The SBM DMZ to SBM interfaces shall allow configuration inputs, RBM feedback,and operations management using HTTPS with DOD PKI certificates. [SRD ID45200]The SBM DMZ to SBM interfaces shall use DISN connectivity and bandwidth toconnect information sources, PIPs, Teleports, Primary and COOP SBMs, TIMs,Operations Mangers, and RBMs. [SRD ID 45300]The SBM DMZ to SBM interfaces shall provide the necessary tools to ingest andprocess analog videos from source inputs. [SRD ID 45400]The SBM to Injection Terminal interfaces shall generate IP multicast streams for eachuplink modulator. [SRD ID 46000]The SBM to Injection Terminal interfaces shall transport the IP multicast streamsgenerated at the SBM over the DISN to geographically dispersed uplink facilities.[SRD ID 46100]The SBM shall ingest SMPTE-325M messages from each injection terminal’s JIPMHubs to control dynamic bandwidth allocations. [SRD ID 46200]The SBM to RBM interfaces shall support the legacy GBS over-the-air protocols toensure compatibility. [SRD ID 46300]The BDA to GBS Operations Manager HCI interfaces shall provide context-sensitiveon-line help. [SRD ID 46400]BDA to Regional Satellite Support Center (RSSC)/Wideband SATCOM OperationsCenter (WSOC) WGS Planning and Control System shall be a WGS authorizedSAR/SAA message. [SRD ID 46500]xxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-165

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement470004710047200The RBM to End User Interface shall allow the RBM to deliver various files andstreaming products to end users using standard internet protocols that include, but arenot limitedto: Hyper Text Transfer Protocol (HTTP), Hyper Text Transfer Protocol Secure(HTTPS), File Transfer Protocol (FTP), File Transfer Protocol over Secure SocketsLayer (FTPS), SSH File Transfer Protocol (SFTP), Real-Time Transport Protocol(RTP), Internet Group Management Protocol (IGMP), Session Description Protocol(SDP), Trivial File Transfer Protocol (TFTP), and Multicast. [SRD ID 47000]The RBM to End User Interface shall allow the End User access to the RBM by usingHTTPS. [SRD ID 47100]The RBM to SBM interface shall allow RBM feedback across the DISN using HTTPSwith DOD PKI certificates. [SRD ID 47200]xxx48000The GBS transport system shall provide capabilities that ensure that informationidentified as priority is delivered ahead of regular traffic 99% of the time. [SRD ID48000]x484004850048600487004880048900500005010150102Each LRU element of the GBS system shall include Built-In-Test (BIT) diagnosticsthat fault isolate using contractor supplied test equipment, 95% of the time. [SRD ID48400]The SBM Mean Time to Repair (unscheduled maintenance) shall be less than 90minutes. [SRD ID 48500]SBM operator level maintenance shall be limited to basic care, cleaning, andreplacement of expendables and Line Replaceable Units (LRU). [SRD ID 48600]SBM scheduled routine maintenance shall be performed without disruption to serviceoperations. [SRD ID 48700]SBM scheduled and routine maintenance time shall not exceed one maintenance hourper 24-hour period. [SRD ID 48800]The GBS system shall allow cryptographic equipment to be maintained and repaired inaccordance with COMSEC maintenance policies and procedures. [SRD ID 48900]The RBM Mean Time to Repair (unscheduled maintenance) shall be less than 90minutes. [SRD ID 50000]The SBM shall maintain an operational availability of 99.0% over a period of 480hours. [SRD ID 50101]The SBM shall maintain an operational availability of 99.99% over a period of 480hours. (Objective) [SRD ID 50102]xxxxxxxx50201Fixed Sites and Equipment exposed directly to an external environment shall operatein blowing sand, dust, and all precipitation environments during 45 mph sustainedwinds, gusts to 60 mph in -40°F to 120°F air temperatures plus solar loading at allhumidity levels. (Threshold) [SRD ID 50201]x5020250400Fixed Sites and Equipment exposed directly to an external environment shall operatein blowing sand, dust, and all precipitation environments during 45 mph sustainedwinds, gusts to 60 mph in -50°F to 150°F air temperatures plus solar loading at allhumidity levels. [SRD ID 50202]The broadcast segment shall be capable of operating at 120/220 VAC at 60/50 Hzpower. [SRD ID 50400]xx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-166

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID5070050710510005150051525RequirementThe GBS System design shall consider and accommodate the nine Human SystemsIntegration (HSI) domains (i.e., manpower, personnel, training, human factorsengineering, environment, safety, occupational health, personnel survivability, andhabitability). [SRD ID 50700]Each HSI domain shall be addressed and optimized, as applicable, within the structureof the GBS design to achieve total system performance and reduce life-cycle costs.[SRD ID 50710].GBS System Human Factors Engineering shall comply with Human SystemsIntegration requirements set forth within DoD Directive 5000.1 and DoDI 5000.2,Human Engineering Program Process and Procedures, MIL-HDBK-46855A, andHuman Engineering Design Criteria, MIL-STD-1472F. [SRD ID 51000]The GBS System design and construction shall not use Class I and Class II ozonedepleting substances. [SRD ID 51500]The GBS System design and construction shall be compliant with the GBS SafetyProgram requirements specified in the GBS System Safety Management Plan (SSMP)and GBS Programmatic Environmental, Safety, and Health Evaluation (PESHE).[SRD ID 51525]xxxxx515505160051700518005190052000521005240052500526005270053000531005320153202The GBS System design shall minimize use of other hazardous materials in GBScomponents, manufacturing materials and processes, support equipment, and disposaloperations. [SRD ID 51550]The GBS System shall be HAZMAT complaint in accordance with DoD Directive5000.1 and DoDI 5000.2. [SRD ID 51600]The GBS System shall not expose operators or maintainers to health and safetyhazards as defined in the GBS Health Hazards Assessment. [SRD ID 51700]Applicable ESOH requirements shall be integrated into the GBS System Engineeringprocess, as defined by NSSAP 03-01 and NEPA/EPA regulations. [SRD ID 51800]The GBS System shall be compliant, certified, and accredited in accordance with theDoDI 8510.bb, DIACAP Instructions. [SRD ID 51900]The GBS System, at a minimum, shall meet all the IA controls for a MissionAssurance Category II classified system per DoD Instruction 8500.2. [SRD ID 52000]The GBS System shall use DoD issued PKI certificates to support authentication,access control, confidentiality, data integrity, and non-repudiation. [SRD ID 52100]The GBS System shall use existing logistics support infrastructures described in theJoint Integrated Logistics Support Plan. [SRD ID 52400].Requirements for maintenance support equipment shall be kept at a minimum. [SRDID 52500]If support equipment is required, the GBS System support equipment, at a minimum,shall be comprised of 90 percent COTS support equipment. [SRD ID 52600]The GBS system shall not require special purpose support equipment, special purposeelectronic test equipment, or special purpose tools. [SRD ID 52700]The RBM Software shall operate in an unattended mode for steady state broadscasts.[SRD ID 53000]Personnel skill and skill levels required for operating and maintaining the RBM shallnot exceed levels defined in Table 5 of this SRD. [SRD ID 53100]GBS System Training, where possible, shall include commercially availableEmbedded Training (ET). [SRD ID 53201]GBS System Training shall not require separate training devices or simulators tosupport the development, operations, and maintenance of GBS. [SRD ID 53202]30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-167xxxxxxxxxxXxxxx

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD IDRequirement5320353204532055320760000601006020160202605006055061000611016110261500616016160261701617026210062101GBS System Training shall be in accordance with service policies and procedures.[SRD ID 53203]GBS System Training shall include electronic form (and hardcopy form whererequired) of the operator and maintainer training material. [SRD ID 53204]GBS System Training shall include electronic form (and hardcopy form whererequired) of the operations and maintenance technical documentation. [SRD ID 53205]GBS System Training shall be provided for the elements of the broadcast segment atthe time of transition to government operations. [SRD ID 53207]The Transmit Receive Suite (TRS) shall be composed of a receive terminal and RBMto provide RCS capability, to support “user pull” requests, via connectivity through aTeleport and DISN core . [SRD ID 60000]The 2-way capability of the GBS Transmit Receive Suites shall be supported by theDECC architecture . [SRD ID 60100]The SBM software shall support the GBS TRS capability of transmitting and receiving2-way data between the RBM, via the GBS space segments with an RCS havingconnectivity to the DISN . [SRD ID 60201]The RBM software shall support the GBS TRS capability of transmitting andreceiving 2-way data between the SBM, via the GBS space segments with an RCShaving connectivity to the DISN. [SRD ID 60202]The GBS system shall include an additional IA approved SCI broadcast enclave,designated for SCI content only, with the same capabilities defined for the ROKUSenclave. [SRD ID 60500]The GBS systems shall include an additional IA approved Coalition broadcast enclave,designated for Coalition content only, with the same capabilities defined for theROKUS enclave. (Objective) [SRD ID 60550]The Ground Mobile Receive Suites (GMRS) shall incorporate all common receivesuite requirements, such as being capable of receiving and processing the GBSdownlink while on the move, requiring no special tools/processes/skills to move fromone tactical vehicle to another, and being capable of surviving the rigors of tacticalcross-country vehicular travel. (Objective) [SRD ID 61000]The Ground Mobile Receive Suite shall be integrated, tested, and certified with theJIPM (one-way) and GBS RBM software. (Objective) [SRD ID 61101]The Ground Mobile Receive Suite shall be integrated, tested, and certified with theJIPM (two-way) and GBS RBM software. (Objective) [SRD ID 61102]A Broadcast Receive Suite – Terrestrial (BRS-T) shall be comprised of any GBSReceive Suite suitably modified to include the necessary transmit capability to supporta wireless terrestrial network extension of the broadcast to twenty or more nearby(within 5-miles distance line-of-sight) locations. [SRD ID 61500]The wireless terrestrial network extension shall meet all required accreditations andcertifications required to be implemented as part of the GBS system . [SRD ID 61601]The wireless terrestrial network extension shall have 2-way capability to, at aminimum, support “user pull” requests . [SRD ID 61602]The wireless extension kit shall provide a web-based mechanism that allows users toutilize system functionality via a lightweight web browser application operating onhandheld devices connected to the wireless terrestrial extension network. [SRD ID61701]The wireless extension kit shall provide content management and filtering capabilitiesto support transmit and receive streams over the wireless terrestrial extension network,which operates at lower data rates than the GBS Broadcast streams. [SRD ID 61702]The SBM shall provide advanced asymmetric networking, implementing contentcaching for subsequent broadcast. (Objective) [SRD ID 62100]The SBM shall provide advanced information and content management, includingdetailed/indexed content search capability. (Objective) [SRD ID 62101]xxxxxxxxxxxxxx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-168

DemonstrationTestAnalysisExamination/InspectionQualify by SimilarityGlobal Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID621026220062201RequirementThe detailed/indexed content search capability shall be supported by a single server,per enclave. (Objective) [SRD ID 62102]The SBM shall provide advanced information and content management, includingvideo caching capabilities that are not backed-up at an alternate site or on permanentmedia. (Objective) [SRD ID 62200]Video caching shall be supported by a single server, per enclave. (Objective) [SRD ID62201]62202 Video caching shall provide 8.1 Terabytes of capacity. (Objective) [SRD ID 62202]The SBM software shall respond to information provider or InformationDissemination Management (and successor programs, to the extent implemented inBlock-2) requests for statistics on the broadcast of individual products, or groups of62501 products, by source over configurable time intervals. [SRD ID 62501]The SBM software shall respond to information provider or InformationDissemination Management (and successor programs, to the extent implemented inBlock-2) requests for statistics on the reception of individual products, or groups of62502 products, by receive suites over configurable time intervals. [SRD ID 62502]xx30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-169

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 34.4 Quality Assurance Provisions4.4.1 Quality AssuranceThe GBS quality assurance provisions will be in accordance with the applicable requirements stated herein thisdocument and other GBS requirements documents. Quality assurance will follow the guidelines provided in theGBS Systems Engineering Plan.4.4.2 RecordsThe GBS quality assurance records will be in accordance with the applicable requirements stated herein thisdocument and other GBS requirements documents.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-170

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 35 PREPARATION FOR DELIVERY5.1 Preservation and PackagingNot applicable.6 NOTES6.1 Acronyms and AbbreviationsAcronymAORARTASIATMBCMBCMSBDABDSBITBRSBRS-TBSBUCCJCSICNPSCOCOMCOMSECCONOPSCOOPCOTSCPSCPUCRDDATMS-CDATMS-UDECCDIIDISNDMZDoDDODIDVB-SDefinitionArea of ResponsibilityAirborne Receive TerminalAuthorized Service InterruptionAsynchronous Transfer ModeBroadcast Content ManagementBroadcast Content Management SoftwareBroadcast Delivery ActivitiesBroadcast Delivery ServiceBuilt-In-TestBroadcast Reception ManagementBroadcast Receive Suite – TerrestrialBroadcast SegmentBlock Up ConverterChairman, Joint Chiefs of Staff InstructionCommon Network Planning SoftwareCombatant CommanderCommunications SecurityConcept of OperationsContinuity of OperationsCommercial Off the ShelfContent Provider Management ServiceCentral Processing UnitCapstone Requirements DocumentDISN ATM Service – ClassifiedDISN ATM Service – UnclassifiedDISN Enterprise Computing CenterDefense Information InfrastructureDefense Information Systems NetworkDemilitarized ZoneDepartment of DefenseDepartment of Defense InstructionDigital Video Broadcast-Satellite30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-171

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3AcronymDVB-S2EAEMPEPGESPFTPFTPSFTPSFTSGBGbpsGBSGIGGMRGMRSGSSCEG/RSSCHANEHCIHEMPHTTPHTTPSIAIAVAIFIGMPINMSIOCIPIP RBMDefinitionDigital Video Broadcast-Satellite (Second Generation)Enhanced ArchitectureElectromagnetic PulseElectronic Program GuidesEncapsulated Security PayloadFile Transfer ProtocolFile Transfer Protocol SecureFile Transfer Protocol over Secure ShellFile Transfer ServiceGiga BytesGiga Bits Per SecondGlobal Broadcast ServiceGlobal Information GridGBS Mission RequestsGround Mobile Receive SuiteGapfiller Satellite Configuration Control ElementGlobal/Regional SATCOM Support CentersHigh-altitude Nuclear ExplosionHuman-Computer InterfaceHigh-altitude Electromagnetic PulseHypertext Transfer ProtocolSecure Hypertext Transfer ProtocolInformation AssuranceInformation Assurance & Vulnerability AssessmentIntermediate FrequencyInternet Group Management ProtocolIntegrated Network Management SystemInitial Operational CapabilityInternet ProtocolInternet Protocol Receive Broadcast ManagementIpv6 Internet Protocol Version 6JIPMJIPM-RJMOSJPOJROCJROCMJTAKIPJoint IP ModemJoint IP Modem RemoteJoint Management and Operations SubsystemJoint Program OfficeJoint Requirements Oversight CouncilJROC MemorandumJoint Technical ArchitectureKey Interface Profiles30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-172

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3AcronymKPPLANLRUMbpsMCAMHzMNSMOPP IVMPEG-2 HDMPEG-2 SDMPEG-4 H.264HDMPEG-4 H.264SDMRTMSMTBCFNBCDefinitionKey Performance ParametersLocal Area NetworkLine Replaceable UnitMega Bits Per SecondMulticast AddressesMegahertzMission Need StatementMission Oriented Protective PostureMotion Picture Expert Group Version 2 (High-Definition)Motion Picture Expert Group Version 2 (Standard Definition)Motion Picture Expert Group Version 4 (High Definition)Motion Picture Expert Group Version 4 (Standard Definition)Manpack Receive TerminalMicrosoftMean Time Between Critical FailureNuclear, Biological and ChemicalNCOW RMNCTAMNETOPSNGANGRTNet Centric Operations and Warfare Reference Model (NCOW RM)Naval Computer and Telecommunication Area Master StationNetwork OperationsNational Geospatial-Intelligence AgencyNext Generation Receive TerminalNIPRNETNMSNR-KPPNTSCOMSORDOSOSS&EOTAP3IPALPDM IVPEPPESHENon-secure (unclassified-but-sensitive) Internet Protocol Router NetworkNetwork Management SoftwareNet-Ready Key Performance ParametersNational Television System CommitteeOperations Management ServiceOperational Requirements DocumentOperating SystemOperational Safety, Suitability and EffectivenessOver the AirPre-Planned Product ImprovementsPhase Alternating LinesProgram Decision Memorandum IVPerformance Enhancing ProxyProgrammatic Environmental, Safety, and Health Evaluation30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-173

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3AcronymPIPPKIPM&PQoSRBMRCMSRDARDSRMRNOSCROKUSRSRTRTPSAASARSATCOMSBMSCISDMASDPSDPSEPSFTPSIPRNetSITLSMPTESRASRDSRTSSCSSMPSSRTTBRTFTPTIMTIPTMSTNCDefinitionUFO Primary Injection PointsPublic Key InfrastructureParts, Materials, and ProcessesQuality of ServiceReceive Broadcast ManagerReceive Content Management SoftwareReceive Delivery ActivitiesReceive Delivery ServiceRemote ModemRegional Network Operations and Security CentersRepublic of Korea / United States SecretReceive SegmentReceive TerminalReal-Time Transport ProtocolSatellite Access AuthorizationSatellite Access RequestSatellite CommunicationsSatellite Broadcast ManagerSensitive Compartmented InformationSystem Delivery and Management ActivitiesSession Description ProtocolSession Description ProtocolSystems Engineering PlanSSH File Transfer ProtocolSecret Internet Protocol Router NetworkSystem Integration and Test LabSociety of Motion Picture and Television EngineersSimplified Robust ArchitectureSystem Requirements DocumentShipboard Receive TerminalSATCOM Support CenterSystems Safety Management PlanSub Surface Receive TerminalTo be DeterminedTrivial File Transfer ProtocolTheatre Information ManagersTheater Injection PointTrouble Management SystemTactical Network Controller30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-174

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3AcronymTRANSECTRSTS/SCITSBMTTIUAVUDPUFOUHFURLUSSTRATCOMVCMWGSXMLDefinitionTransmission SecurityTransmit Receive SuiteTop Secret Sensitive Compartmented InformationTheater Satellite Broadcast ManagerTransportable Theater InjectorUnmanned Aerial VehicleUser Datagram ProtocolUltra High Frequency Follow-OnUltra High FrequencyUniform Resource LocatorUnited States Strategic CommandVariable Code ModulationWideband Global SATCOMExtensible Markup Language30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-175

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 36.2 Terms and DefinitionsAirborne Receive Suite (ARS) –A GBS receive suite installed on airborne platforms, to include fixed and rotary wing aircraft. This receiver willreceive while on the move. The ARS is planned for GBS Phase-3 as part of the TransformationalCommunications Architecture.Broadcast Stream –The aggregation of video and data products into a continuous digital stream to be transmitted to the spacesegment. Broadcast streams are created by the Satellite Broadcast Manager, processed and transmitted to thespace segment by the injection terminal, and received and processed by the receive suite (receive terminal,cryptographic equipment and Receive Broadcast Manager) for subsequent dissemination to end user systems.Broadcast Management Segment (BMS)The set of functions, processes, and systems required to collect, assemble, prioritize, transmit, encrypt or decrypt,and disseminate information provided from information producers to end user systems with functions responsiveto Combatant Commander inputs. Satellite Broadcast Management (SBM) and Theater Information Management(TIM) functions are performed within the BMS. BMS accepts, coordinates, and packages, information (generalbroadcast products, smart push products, user pull products) from sources to be broadcast based on the directionand priorities. The BMS also includes the functions necessary to support the efficient use of GBS. The broadcastmanagement segment will maximize on-orbit capabilities to include uplink and downlink beam steerage andtransponder configurations. BMS is divided into two parts: transmit broadcast management and receive broadcastmanagement.Broadcast Receive Suite – TerrestrialSpecially equipped receive suite with extension to the GBS COTS-based standards with extended GBS deliveryservices across wireless networks to locally line-of-sight (LOS) dispersed fixed or mobile platforms. Thisterrestrial extension of the GBS broadcast permits lower cost and smaller RS integration compared to fieldingmultiple satellite RS’ in the vicinity.Broadcast servicesDelivery of information products by the GBS system, which users employ to improve their combat effectiveness.“Competitive” ModeMode of operations in which the SBM has been authorized to share space segment resource in a mode ofoperations, in which the SBM interactively and dynamically interact with the other SATCOM system to competefor allocation of space segment resources (bandwidth and beam pointing) based upon automated, possibleiterative process using interactive priority-based optimized access to the other space segment resources.Content CatalogThe GBS content catalog is a listing of all the programs currently defined the GBS database. This catalog isavailable over the web at the SBM and will also be a regularly scheduled file delivery at the receive suite.Program descriptions are only available on the SECRET receive suite.Data File ProductsData file products vary widely in size and content. The primary reasons to use GBS for data products are itswidespread simultaneous distribution capability and its inherent speed. Most MILSATCOM supports point-topointcommunications requiring a separate path for each end-user. GBS uses a point-to-area approach where allusers within the area receive the communications simultaneously over the same path. Assured delivery of dataproducts is not possible with a one-way broadcast such as GBS. However, GBS Phase 2 broadcasts are very highquality (bit error rates of 10 -10 ). This high data rate can allow for multiple transmissions of the same productraising the level of statistical assurance of delivery for specific products (based on TIM direction). Examples ofinformation products requiring increased assurance of delivery include the Air Tasking Orders (ATO), Ballistic30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-176

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Missile Warning, airborne reconnaissance (or other) “highlight films,” and the Tomahawk Mission Data Update(MDU). Since GBS is not a critical command and control system, a procedural solution would have to be appliedto any critical data products that are sent over it. Such a solution might incorporate a “reply to” specification inthe data product, which instructs the receiver to verify reception with the sender over an appropriatecommunications path. (See Session Products).“Dedicated” ModeMode of operations in which the SBM has been authorized complete control over one or more spot beams and theassociated bandwidth of a space segment resource. When authorized, direct GBS SBM management may beemployed.Defense Information System Network (DISN)A network of communications paths that support information transfer within the DoD.De-Militarized Zone (DMZ)Perimeter network segment that is logically between internal and external networks. Its purpose is to enforce theinternal network’s IA policy for external information exchange and to provide external, untrusted sources withrestricted access to releasable information while shielding the internal network from outside attacks.Electronic Program GuideThe electronic program guide is a web interface that displays of all streaming programs that are scheduled and alist of file transfer service programs expected during the duration of the current beam dwell or for the next Xhours whichever is shorter.End-to-End Link AvailabilityEnd-to-end link availability is defined for the GBS System as originating at the SBM transmission of the datastream and ending with receipt of the data at the various user receive suites. End-to-end availability does notinclude dissemination of the data beyond the receive suite.End UserThe ultimate recipient or user of the information products broadcast by the GBS.FileA discrete or fixed size information product. Imagery, weather information, maps, and Air Tasking Orders areexamples of file products.FixedNot intended to be moved.Fixed Ground Receive Suite (FGRS)A GBS receive suite installed in a fixed location. This receiver will not receive while on the move.Global Broadcast Service (GBS)A former Acquisition Category (ACAT) ID (now ACAT IC) DoD program, providing a system of satellites andcommercially developed receivers used by a Combatant Commander providing a responsive or directed broadcastmanagement structure to support the flow of national and theater level generated information products to forcesdeployed, on the move (in transit), or in garrison.GBS Broadcast Product Types Consist of video, data, imagery and other information products, file-based orstreaming.Ground Mobile Receive Suite (GMRS)The GMRS is vehicle mounted (land or water), and should be removable permitting relocation between primemovers.HeartbeatA unique identifier on each broadcast stream to identify the associated satellite and uplink modulator.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-177

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Information Dissemination Management (IDM)The function of providing the right information to the right place at the right time in accordance withcommanders’ policies and optimizing the use of information infrastructure resources. IDM is “content aware” inthat it provides access to information, may integrate information from multiple sources, archives products, andmay format some information for transmission on the selected media. It involves the safeguarding, compilation,cataloging, caching, distribution, and retrieval of data; manages the flow of information to users; and enables theexecution of commanders’ information policy.Information ManagementInformation management enables warfighting decision-makers to collaborate with information producers to getrelevant information, generate knowledge and understanding about the Battlespace, and empower successfuldecision-making.Information ProductsFile and stream products from national and theater information producers to be delivered to end-users by the GBSsystem.Information ProviderInformation providers are categorized as national and theater. Those agencies, fusion centers, creators of valueadded products, sensors, sensor ground sites, etc. that have an information product that the user (warfighter) wantsand can use GBS as a high-speed path for delivery. Deployed forces may also be information providers bycreating local products for distribution or by obtaining raw data from processing at rear echelons (see InformationSource).Information SourceThe physical information product storage or creation location from which the information provider or the GBSbroadcast management segment obtains information products to be broadcast. An information provider identifiesor manages the presentation of specific sources for incorporation into the GBS broadcast.Injection PointsHardware and software that implements the functions necessary to transmit broadcast streams to the spacesegment. Injection points are categorized as Primary Injection Points and Theater Injection Points.Mean Corrective Maintenance Time for Operational Mission Failure (MCMTOMF)The average elapsed corrective maintenance time needed to repair all operational mission failures. It includes timefor maintenance preparation, failure location and isolation, on-board parts procurement, failure correction,adjustment and calibration, as well as follow-up checkout time. It does not include off-board logistic delay time;i.e., the time to obtain spare parts or use the expertise of personnel outside the unit or organizational level.MCMTOMF = Total Elapsed Time to Correct Operational Mission FailureTotal Number of Operational Mission FailuresMean Time Between Critical Failure (MTBCF)MTBCF equals the total equipment operating time in hours, divided by the number of mission-essential systemfailures. MTBCF includes all critical hardware and software failures that deny the user critical managementinformation based on user-determined critical and timing requirements.Mean Time Between Failure (MTBF)For a particular interval, the total functional life of a population of an item, divided by the total number of failureswithin the population. The definition holds for time, rounds, events, or other measures of life unit. A basictechnical measure of reliability.Mean Logistic Delay Time (MLDT)Computed from the time a failed lowest replaceable unit (LRU) is identified and placed on order to the time areplacement LRU is received and installed.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-178

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3MobileCapable of communicating while moving.Near-Worldwide CoverageAn area 65 degrees North latitude to 65 degrees South latitude, with longitude coverage limited by the UHFFollow-On satellite footprint.Network CentricExploitation of advancing technology moving from an applications-centric to a data-centric paradigm – that is,providing users the ability to access applications and services through Web services – an information environmentcomprised of interoperable computing and communication components.Network Centric Enterprise Services (NCES)Global Information Grid (GIG) Network Centric Enterprise Services (NCES) A DISA program to implement keyenabling capabilities for a network centric enterprise. NCES provide a common set of interoperable informationcapabilities in the Global Information Grid (GIG) to access, collect, process, store, disseminate, and manageinformation on demand for warfighters, policy makers, and support organizations.Net Centric Operations and Warfare (NCOW)Describes how DOD conducts business operations, warfare, and enterprise management. It is based on theconcept of an assured, dynamic, and shared information environment providing access to trusted information forall users, based on need, independent of time and place. It is characterized by assured services, infrastructuretransparency (to the user), independence of data consumers and producers, and metadata supported by informationdiscovery, protection and mediation. This fundamental shift from platform-centric warfare to net-centric warfareprovides for an Information Superiority-enabled concept of operations. The NCOW RM provides a commontaxonomy and lexicon of NCOW concepts and terms, and architectural descriptions of NCOW concepts. Itrepresents an important mechanism in DOD transformation efforts, establishing a common framework for netcentricity.It enables capability developers, program managers, and program oversight groups to move forward ona path toward a transformed, net-centric enterprise. Net-centricity enables user access and use of resources bothcollaboratively and asynchronously, regardless of time and place. It is the ability of a program or system tointegrate with, offer services to, and exploit the services of a net-centric environment.Net Centric Operations and Warfare Reference Model (NCOW RM) –(see paragraph E.1.1Compliance with NCOW RM.)The NCOW RM describes the activities required to establish, use, operate, and manage the net-centric enterpriseinformation environment to include: the generic user-interface, the intelligent-assistant capabilities, the net-centricservice capabilities (core services, Community of Interest (CoI) services, and environment control services), andthe enterprise management components. It also describes a selected set of key standards needed as the NCOWcapabilities of the Global Information Grid (GIG) are realized. The NCOW RM represents the objective end-statefor the GIG. This objective end-state is a service-oriented, inter-networked, information infrastructure in whichusers request and receive services enabling operational capabilities across the range of military operations; DODbusiness operations; and Department-wide enterprise management operations. The NCOW RM is a keycompliance mechanism for evaluating DOD information technology capabilities and the Net Ready KeyPerformance.Network Centric WarfareAn information superiority-enabled concept of operations generating increased combat power by networkingsensors, decision makers, and shooters to achieve shared awareness, increased speed of command, higher tempoof operations, greater lethality, increased survivability, and a degree of self-synchronization. Network centricwarfare translates information superiority into combat power by effectively linking knowledgeable entities in thebattlespace.Net-ReadyDOD Information Technology National Security Systems meeting required information needs, informationtimeliness requirements, has information assurance accreditation, and meets the attributes required for both the30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-179

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3technical exchange of information and the end-to-end operational effectiveness of that exchange. DODInformation Technology National Security Systems which is Net-Ready, enables warfighters and DOD businessoperators to exercise control over enterprise information and services through a loosely coupled, distributedinfrastructure, leveraging service modularity, multimedia connectivity, metadata, and collaboration to provide anenvironment promoting unifying actions among all participants. Net-readiness requires Information TechnologyNational Security Systems to operate in an environment where there exists a distributed information processingenvironment in which applications are integrated; applications and data independent of hardware are integrated;information transfer capabilities exist to ensure seamless communications within and across diverse media;information is in a common format with a common meaning; there exist common human-computer interfaces forusers; and there exists effective means to protect the information. Net-Readiness is critical to achieving theenvisioned objective of a cost-effective, seamlessly integrated environment. Achieving and maintaining thisvision requires interoperability:a. Within a Joint Task Force combatant command area of responsibility (AOR).b. Across combatant command AOR boundaries.c. Between strategic and tactical systems.d. Within and across Services and Agencies.e. From the battlefield to the sustaining base.f. Among US, Allied, and Coalition forces.g. Across current and future systems.Net-Ready Key Performance Parameter (NR-KPP)The NR-KPP assesses information needs, information timeliness, information assurance, and net-ready attributesrequired for both the technical exchange of information and the end-to-end operational effectiveness of theexchange. The NR-KPP consists of verifiable performance measures and associated metrics required to evaluatethe timely, accurate, and complete exchange and use of information to satisfy information needs for a givencapability. The NR-KPP is comprised of the following elements: (1) Compliance with the Net-Centric Operationsand Warfare (NCOW) Reference Model (RM), (2) Compliance with applicable GIG Key Interface Profiles (KIP),(3) Verification of compliance with DOD information assurance requirements, and (4) Supporting integratedarchitecture products required to assess information exchange and use for a given capability.Net-Ready KPP AssessmentThe Net-Ready KPP Assessment determines the impacts, risks, and vulnerabilities of fielding secure,interoperable, supportable, sustainable and usable (SISSU) systems to the warfighter. Parameters assessedinclude: network security, network impact, compatibility with the infrastructure, infrastructure requirements,spectrum support, security policy compliance, DISR standards compliance, communications and informationmanpower, training, logistics support, schedule and funding. A system assessed and determined to be supportablefrom a communications and information perspective, and any impacts, risks and vulnerabilities it may present tothe enterprise are deemed to be acceptable or manageable is Net Ready.Network warfare simulation (NETWARS)The standard DOD approved communications simulation tool. Combatant commanders, Services and agenciesuse NETWARS for all communications modeling purposes.Operational Availability (Ao)Ao is the total time the unit is operational and is calculated as: A = Total Uptime . o (Total Uptime + TotalDowntime). It is the operational availability of the unit; the percentage of time that the unit is able to perform itsintended operation. Where: Uptime is the time when the unit is considered ready for use and is either operating, instandby, or off Downtime is the time the unit is down for repair of operational mission failures, including offboardlogistics delays. Downtime also includes planned maintenance time. Ao in this SRD does not includegeographic effects such as rain fade or the sun passing behind a satellite. Geographic effects should only degradesystem availability when their severity overcomes the margins built into system architectures (see link30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-180

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3availability). While it is impractical to build a system with a tolerance for all possible terrestrial environments, thesystem fielded as a result of this SRD shall be designed to operate in most global environments. Outages resultingfrom extreme environmental conditions are not factored into the Ao.Ao in this SRD does not include site environmental affects resulting from electro-magnetic interference (EMI) orantenna blockage. The probability that these affects will degrade system availability is directly related to hardwarelocation (e.g. antenna placement).Limited shipboard real estate requires that the physical location of shipboard equipment resulting from this SRDbe weighed against the operational requirements of other shipboard systems. Priorities and tradeoffs will need tobe addressed prior to system fielding. Outages resulting from shipboard environmental effects are not factoredinto the Ao.The resulting shipboard availability for these systems shall be some fraction of the Ao specified in this SRD.Pass Information Ranging in ClassificationThe GBS system must be able to pass all information ranging in security classification from unclassified to TopSecret, including Allied, Coalition, and non-DoD data, video, and imagery without compromising need to knowaccess of that information to also protect and defend information or information systems by ensuring theiravailability, integrity, authentication, confidentiality, and non-repudiation. In order to permit passing of someinformation GBS may use capabilities similar to tunneling, in which the products are managed by the informationprovider and processed and encrypted at the source using GBS prescribed techniques and standards so that end-toendextensions of the GBS receive suite can using scalable and uniform methods provide the information towarfighter applications in a useful form. Passing of source-encrypted information must not violate other GBSSRD requirements for the system; such as inhibit the re-pointing of spot beams or the sharing and reallocation ofbandwidth.Payload ControlPlanning and executing antenna pointing, power or gain changes, antenna discrimination, transmission securitykey distribution, cross banding reconfiguration, and payload commanding.Portable Receive Suite (PRS)Any receive suite version suitable to single person transport and possibly covert operations.Primary Injection Point (PIP)A fixed injection system that provides the primary uplink of the broadcast streams from the broadcastmanagement segment to the space segment.Receive Broadcast Management (RBM)The set of functions, processes, and systems associated with receiving and disseminating the file and streaminformation contained within the broadcast to end-users. Receive broadcast management functions includeinterfacing on the physical layer between the receive suite and the end user system; enabling remote commandingand tuning; filtering and routing information; identifying missing or damaged files; enabling user profiling;decoding and displaying program guides, product catalogs and schedules; and providing anti-virus defense.Receive SiteA location capable of receiving the GBS downlink directly from the satellite. Receive sites will be fixed,transportable, and mobile.Receive Suite (RS)The receive terminal, cryptographic equipment, and receive broadcast management hardware and softwarerequired to support an end user’s information delivery and dissemination requirements. Receive suites arecategorized as ground, airborne, shipboard and submarine. Ground suites are further categorized as fixed ortransportable.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-181

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3Receive TerminalThe hardware (antenna) and software that implements the functions necessary to receive the downlink broadcaststreams and convert them to data streams for subsequent processing and dissemination by the receive broadcastmanagement hardware and software.Regional SATCOM Support Center (RSSC)RSSCs provide a regional operational focus for constellation payload management and assist unified commandsand other users in day-to-day management of apportioned and allocated resources.Repudiation of AccessEnsure that access to certain information is restricted to individuals with a need-to-know.Rucksack Portable Receive Suite (RPRS)A rucksack-portable GBS receive suite suitable for Special Operations forces.Satellite Broadcast ManagerThe set of functions, processes, and systems associated with collecting information products, assemblingbroadcast streams, and transmitting these streams to the injection point for uplink to the space segment. Satellitebroadcast management functions include building the schedule broadcast and program guide, coordinatinginformation products, conducting traffic analysis, constructing and transmitting the broadcast stream, providingfor protection of data, technically controlling the GBS broadcast, controlling executing remote enabling ordisabling, and establishing and maintaining the user profile database.“Scrounge” ModeMode of operations in which the SBM has been authorized to share space segment resource of another SATCOMsystem which conducts its own communications loading without respect to GBS, and then informs the SBMwhere all beams are pointed with available bandwidth suitable for establishing a broadcast to any of a variety ofcoverage area(s) which is under the control of the other SATCOM system’s manager (usually fix-pointed).Shipboard Receive Suite (SRS)A GBS receive suite that is installed on shipboard platforms. This receiver will receive while on the move.Configurations include single and dual antenna configurations.Smart PushThe capability for the end user to define information requirements in advance so that the GBS system can tailorbroadcast services without regard to specific user requests. The basis of this capability is the User Profile, whichcontains the information requirements and is resident in the SBM’s database.Satellite ControlSpacecraft station-keeping, stabilization, maneuvering and repositioning, anomaly resolution, tracking telemetry,commanding and ephemeris generation.Space SegmentThe space-borne elements of the GBS system, consisting of the broadcast satellite packages and satellitecommand and control systems.Stream or Session (Video, Audio, or Stream) ProductsA continuous or variable duration information product that originates from a national or theater source. Sessionproducts may be Unified Combatant Command, Service, or Agency-unique, and may be disseminated to any orall GBS-equipped units in the broadcast coverage area. Video products, consisting of video and accompanyingaudio or data, require a continuous segment (scheduled session) of the bandwidth for an extended period of time(10-to-30 minutes or more, or in some cases 24-hours a day). Examples of video products include dailyintelligence briefings, distance learning or training, commercial cable news or weather services, medicalprocedure videos and near real-time airborne reconnaissance video dissemination to tactical forces. Examples ofstream products include constant sensor to shooter data feeds or any real-time data dissemination requirements,30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-182

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3such as, Integrated Broadcast Service (IBS) or COP. GBS does not provide a video-teleconference (VTC)capability (see Data Products).Sub-surface Receive Suite (SSRS)A GBS receive suite that is installed on submarine platforms. This receiver will receive while on the move atperiscope depth.Suitcase Portable Receive Suite (SPRS)Receive suite versions suitable for transport as personal luggage on airliners.Theater Information Management (TIM)The set of functions, processes, and systems associated with control and management of GBS that providesindividual Combatant Commanders with the control essential for delivery of the correct information products totheir forces worldwide. TIM functions include directing GBS operations, coordinating the broadcast schedule,managing apportioned resources, identifying new products, reviewing and validating the user profile database,and auditing User Pull.Theater Injection Point (TIP)A transportable injection system that provides the capability for theater commanders to broadcast informationdirectly from within a theater. A TIP incorporates the necessary TIM and SMB functions needed to carry out itsmission. Close coordination is required between the TIP and the SBM for multiple reasons, e.g., to coordinatesharing of satellite resources.Transmit Receive Suite (TRS)A Receive Suite suitably modified to include the necessary transmit capability to support GBS User Pull usingGBS RCS reachback connectivity directly through a PIP to an SBM.TransportableCapable of being moved from one location to another and communicating from a fixed location (not while on themove).Transportable Ground Receive Suite (TGRS)A GBS receive suite packaged to provide portable capability. This receiver will not receive while on the move.Tuning GuideA web interface that displays the necessary information required to tune each GBS RBM to the appropriatesatellite and begin reception of products.User ProfileA record of information that identifies a specific user, his information needs, address, accesses, and other selecteddata that can be helpful to the user and to information managers in ensuring the user receives complete supportfrom GBS. This information is entered into the SBM’s database for use by the SBM, TIM, and informationproviders, and to facilitate management of GBS broadcast operations by the SBM.User PullThe capability for end users to define specific information to be broadcast on demand in response to operationalcircumstances, or the actual end user request for specific information to be broadcast on demand.Wideband SATCOM Operations Center (WSOC)The WSOC is an upgraded Defense Satellite Communications System (DSCS) Operations Center (DSCSOC)responsible for maintaining payload configuration of the WGS payloads. WSOCs continuously monitor satellitepayloads to determine which services are operational, which users are employing each communications resourceand conduct analysis to determine how well the payload and user links, accesses, and networks are performing.Worldwide CoverageAn area 65 degrees North latitude to 65 degrees South latitude, 180 degrees West to 180 degrees East longitude.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-183

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 37 APPENDIX A: SRD to ORD Requirements Trace (Child-to-Parent)SRD ID SRD Requirement ORD Req # ORD Requirement1010010201102021030010400The GBS System shall provide the core functionalities,contained herein this specification’s Table 3 (Column“Function”), to address the needs of the user/operator(s)designated for area. [SRD ID 10100] 30The GBS System shall be in compliance with DoD mandatedNet-Ready Key Performance Parameters, including satisfying100% of all the specified Joint integrated architecturerequirements designated enterprise-level or critical activityinterfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing andinformation assurance accreditation requirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs). [SRD ID 10201] 1, 1-1The GBS System shall be in compliance with the DODmandated Net-Ready Key Performance Parameters (KPP),including meeting GIG interoperability standards (CJCSI3170.01C, CJCSI 6212.01D, DoDI 4630.5, and DoDI 4630.8)for the interfaces, protocols, and equipment required to receiveand disseminate video and data from existing systems. [SRDID 10202] 2,3The GBS system shall satisfy 100 percent of the top-levelInformation Exchange Requirements (IER) designated criticalto the standards specified in the IER Matrix, defined in theGBS Operational Requirements Document (KPP). [SRD ID10300] 25The GBS system shall accommodate scaling, both up to 200%increases and up to 50% decreases, of the following factorsincluding but not limited to: satellites, antennas, uplinkmodulators, RBMs, security enclaves, broadcast load, totalproducts, and number of each end-to-end service types. [SRDID 10400]4-3, 80, 91,98, 103Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective). Req 1-1: The GBS System ispart of the GIG and shall meet GIG interoperability standards for the interfaces, protocols, andequipment required to receive and disseminate video and data from existing systems (Threshold).Req 2: The GBS System shall be compliant with the GIG and Network Centric Enterprise Services(Threshold). Req 3: The GBS Software that is provided to operate on platforms outside the GBSsystem shall be compliant with Level 5 of the GIG COE Integration and Runtime Specification(I&RTS), Version 4.1, 3 October 2000 and subsequent revisions as deemed appropriate by ServiceAcquisition Executive (SAE) at program reviews or milestone decisions (Threshold).Req 25: 100 percent of top-level Information Exchange Requirements (IER) designated criticalshall be satisfied to the standards specified in the IER Matrix (KPP – Threshold). All top-level IERsshall be satisfied to the standards Specified in the IER Matrix for the indicated IOC Block(Objective).Req 4-3: The system shall use scalable and interoperable means in order to handle multiple andvaried compartmented information sources and a scalable and interoperable means to provide theinformation to the user beyond the receive suite (Block-2 Threshold). Req 80: GBS shall use spacesegment capabilities to support the dynamic nature of modern warfare through using multiplecoverage areas, using responsive, independently steerable or fixed coverage areas to locations withinthe satellite’s field of view (Threshold). Req 91: Receive Suites shall be scaleable and configurableto satisfy a variety of user installations and broadcast receive requirements (Threshold). Scaleableand configurable configurations beyond basic receive suite configurations shall be separatelyprocured and accompanied with training and maintenance addendums to include at a minimum thefollowing: (see sub requirements 91-x). Req 98: In order for receive suites to support eithercoalition, allied or Top Secret compartmented security enclave(s), separate add-on configuration orseparate transit case shall be available to support each additional security enclave. A minimum oftwo additional add-on security enclaves shall be accommodated (Block-2 Threshold). Req 103:Receive Terminals shall be scalable to include configurations capable of using one or moreseparately procured interchangeable feed horn and amplifier assemblies to handle polarization andfrequency across the space segment downlink frequency bands to receive: (see sub requirements)30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-184

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementReq 4-3: The system shall use scalable and interoperable means in order to handle multiple andvaried compartmented information sources and a scalable and interoperable means to provide theinformation to the user beyond the receive suite (Block-2 Threshold). Req 80: GBS shall use spacesegment capabilities to support the dynamic nature of modern warfare through using multiplecoverage areas, using responsive, independently steerable or fixed coverage areas to locations withinthe satellite’s field of view (Threshold). Req 91: Receive Suites shall be scaleable and configurableto satisfy a variety of user installations and broadcast receive requirements (Threshold). Scaleableand configurable configurations beyond basic receive suite configurations shall be separatelyprocured and accompanied with training and maintenance addendums to include at a minimum thefollowing: (see sub requirements 91-x). Req 98: In order for receive suites to support eithercoalition, allied or Top Secret compartmented security enclave(s), separate add-on configuration orseparate transit case shall be available to support each additional security enclave. A minimum oftwo additional add-on security enclaves shall be accommodated (Block-2 Threshold). Req 103:The GBS system shall be scalable, both up to 200% increasesReceive Terminals shall be scalable to include configurations capable of using one or more10501and up to 50% decreases, and capable to pass multiple andseparately procured interchangeable feed horn and amplifier assemblies to handle polarization andvaried compartmented information sources. [SRD ID 10501] 4-3frequency across the space segment downlink frequency bands to receive: (see sub requirements)Req 4-3: The system shall use scalable and interoperable means in order to handle multiple andvaried compartmented information sources and a scalable and interoperable means to provide theinformation to the user beyond the receive suite (Block-2 Threshold). Req 80: GBS shall use spacesegment capabilities to support the dynamic nature of modern warfare through using multiplecoverage areas, using responsive, independently steerable or fixed coverage areas to locations withinthe satellite’s field of view (Threshold). Req 91: Receive Suites shall be scaleable and configurableto satisfy a variety of user installations and broadcast receive requirements (Threshold). Scaleableand configurable configurations beyond basic receive suite configurations shall be separatelyprocured and accompanied with training and maintenance addendums to include at a minimum the105021060010701The GBS system shall be scalable, both up to 200% increasesand up to 50% decreases, to provide information to the userbeyond the receive suite. [SRD ID 10502] 4-3The GBS System is part of the GIG and shall meet GIGinteroperability standards for the interfaces, protocols, andequipment required to receive and disseminate video and datafrom existing systems (Threshold). [SRD ID 10600] 1, 1-1The GBS System shall provide a minimum of 90 percentstatistical assurance of receipt of all broadcast information(measured from the point where the broadcast information isreceived in the SBM and delivered at the interface between theRS’s RBM and the attached LAN). [SRD ID 10701] . 1930 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-185following: (see sub requirements 91-x). Req 98: In order for receive suites to support eithercoalition, allied or Top Secret compartmented security enclave(s), separate add-on configuration orseparate transit case shall be available to support each additional security enclave. A minimum oftwo additional add-on security enclaves shall be accommodated (Block-2 Threshold). Req 103:Receive Terminals shall be scalable to include configurations capable of using one or moreseparately procured interchangeable feed horn and amplifier assemblies to handle polarization andfrequency across the space segment downlink frequency bands to receive: (see sub requirements)Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective). Req 1-1: The GBS System ispart of the GIG and shall meet GIG interoperability standards for the interfaces, protocols, andequipment required to receive and disseminate video and data from existing systems (Threshold).Req 4-3: The system shall use scalable and interoperable means in order to handle multiple andvaried compartmented information sources and a scalable and interoperable means to provide theinformation to the user beyond the receive suite (Block-2 Threshold). Req 80: GBS shall use spacesegment capabilities to support the dynamic nature of modern warfare through using multiplecoverage areas, using responsive, independently steerable or fixed coverage areas to locations withinthe satellite’s field of view (Threshold). Req 91: Receive Suites shall be scaleable and configurableto satisfy a variety of user installations and broadcast receive requirements (Threshold). Scaleableand configurable configurations beyond basic receive suite configurations shall be separatelyprocured and accompanied with training and maintenance addendums to include at a minimum thefollowing: (see sub requirements 91-x). Req 98: In order for receive suites to support either

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementcoalition, allied or Top Secret compartmented security enclave(s), separate add-on configuration orseparate transit case shall be available to support each additional security enclave. A minimum oftwo additional add-on security enclaves shall be accommodated (Block-2 Threshold). Req 103:Receive Terminals shall be scalable to include configurations capable of using one or moreseparately procured interchangeable feed horn and amplifier assemblies to handle polarization andfrequency across the space segment downlink frequency bands to receive: (see sub requirements)10702107051100011101112001130011400The GBS System shall provide a minimum 95 percentstatistical assurance of receipt of all broadcast information(measured from the point where the broadcast information isreceived in the SBM and delivered at the interface between theRS’s RBM and the attached LAN). [SRD ID 10702]. 19The GBS system shall meet the Quasi-Error Free (QEF)condition under clear weather conditions, equivalent to lessthan one (1) uncorrected error event per transport stream hour(corresponds to a BER between 10^-10 and 10^-11). [SRD ID10705] 18, 20The BDA shall use the uplink encapsulator(s) and modulator(s)at the Satellite uplink facilities (i.e., Teleports and PIPs). [SRDID 11000] 4The BDA shall support content broadcast to an RBM that isreceiving from one, and up to six (6), uplink modulators. [SRDID 11101] 4For all data services, the BDA shall use unique multicastaddresses for each satellite downlink, as described in Figure 5.[SRD ID 11200] 15, 37The BDA shall organize broadcast content as associated witheach RBM receiver Terminal size (e.g. small, medium, large)and assign multicast addresses that are consistent with theDVB-S2 VCM capability of the JIPM Hub. [SRD ID 11300] 15The BDA shall not allow transmission of content to the RBMsystem root (i.e., “ C:\”). [SRD ID 11400] 8, 2030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-186Req 19: The System shall have the ability to provide minimum 90 percent (Threshold) and 95percent (Objective) statistical assurance of receipt of all broadcast information (measured from thepoint where the broadcast information is received in the SBM or TSBM and delivered at theinterface between the RS’s RBM and the attached LAN). The system must also provide flexibility toensure Combatant Commander selected information is delivered with a range of statisticalconfidences approaching guaranteed assurance of receipt (Block-2 Threshold). When a TRS ornetworked reachback connectivity is available, the return path functionality shall be used to providereliable file product transmission between the SBM and RBM (Block-3 Threshold).Req 18: The GBS System shall provide a Bit Error Ratio (BER) of no greater than 10-10 underclear weather conditions with link margin to maintain specified end-to-end link availability (seeparagraph 4.3.1.4.1) (Threshold). Req 20: As an element of the GIG, the GBS System shallmaintain and guarantee during transport the integrity of file-based data that it stores and processes toenable user confidence; information integrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req37: The SBM shall manage the broadcast content for WGS coverage areas based upon a single spotbeam’s coverage for each unique broadcast injected (Block-2 Threshold), or be capable of usingWGS satellite features to duplicate the same uplink broadcast stream into multiple downlinkcoverage areas simultaneously (Block-3 Threshold, Block-2 Objective).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold).Req 8: With the exception of unclassified video (limited to public domain non-DoD derived andnon-national security related information used in fulfillment of military or intelligence missions), allinformation shall be protected from exploitation during transmission over satellites (Block-2Threshold). Req 20: As an element of the GIG, the GBS System shall maintain and guaranteeduring transport the integrity of file-based data that it stores and processes to enable user confidence;information integrity shall be 99.99% (Threshold) and 99.999% (Objective).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement115001160011700118001190011901The BDA shall provide a capability to automatically broadcastfile-based content from sources as it arrives at the SBM. [SRDID 11500] 27The BDA shall support the transmission of any size file up to20 GB. [SRD ID 11600] 19, 33The BDA shall provide the set of end-to-end broadcast serviceslisted in Table 4. [SRD ID 11700] 30All file-based services shall have a file-based error correctioncapability that allows files to be efficiently reconstituted in theevent that there are missed packets. [SRD ID 11800] 18, 19, 20All file-based services shall have a queuing mechanism thatcan support prioritization between files and still simultaneouslyservice both large and small files of the same priority. [SRD ID11900] 20All file-based services shall have a queuing scheme forscheduling the queuing of a product at a designated time basedon CJCSI 6250.01 priority. [SRD ID 11901] 20Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold).Req 19: The System shall have the ability to provide minimum 90 percent (Threshold) and 95percent (Objective) statistical assurance of receipt of all broadcast information (measured from thepoint where the broadcast information is received in the SBM or TSBM and delivered at theinterface between the RS’s RBM and the attached LAN). The system must also provide flexibility toensure Combatant Commander selected information is delivered with a range of statisticalconfidences approaching guaranteed assurance of receipt (Block-2 Threshold). When a TRS ornetworked reachback connectivity is available, the return path functionality shall be used to providereliable file product transmission between the SBM and RBM (Block-3 Threshold). Req 33: TheSBM and TSBM shall adjust transmit data rates with minimal interruption to the broadcast,consistent with the receive suite synchronization timeline (Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 18: The GBS System shall provide a Bit Error Ratio (BER) of no greater than 10-10 underclear weather conditions with link margin to maintain specified end-to-end link availability(Treshold). Req 19: The System shall have the ability to provide minimum 90 percent (Threshold)and 95 percent (Objective) statistical assurance of receipt of all broadcast information (measuredfrom the point where the broadcast information is received in the SBM or TSBM and delivered atthe interface between the RS’s RBM and the attached LAN). The system must also provideflexibility to ensure Combatant Commander selected information is delivered with a range ofstatistical confidences approaching guaranteed assurance of receipt (Block-2 Threshold). When aTRS or networked reachback connectivity is available, the return path functionality shall be used toprovide reliable file product transmission between the SBM and RBM (Block-3 Threshold). Req 20:As an element of the GIG, the GBS System shall maintain and guarantee during transport theintegrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).11902All file-based services shall have a queuing scheme thatprovides prioritization between files and allocation of availablebandwidth among file types of different sizes. [SRD ID 11902] 20Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).11903All file-based services shall have a queuing delay (time for aunique, recently arrived file to begin transmission assuming noother similar sized files are currently in queue), for files sizesless than 1 MB, of not more than 1.0 seconds. [SRD ID 11903] 2030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-187Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement11904119051190611907120001210012200123001240012500All file-based services shall have a queuing delay, for a file of100 MB or less, of not more than 5.0 seconds. [SRD ID 11904] 20All file-based services shall have a queuing delay, for a file of2 GB or less, of not more than 10 seconds. [SRD ID 11905] 20All file-based services shall be available in every securityenclave. [SRD ID 11906] 20All file-based services shall address content to one, many, orall RBMs. [SRD ID 11907] 20The FTS Service shall provide immediate file-based contentdelivery. [SRD ID 12000] 20The FTS Service, within an enclave, shall be capable ofreceiving and processing source products that are injected fromsources via FTP or equivalent. [SRD ID 12100] 20The Web Crawl Services shall accept scheduling informationto collect web site content on a scheduled basis. [SRD ID12200] 30The Web Crawl Services shall provide the ability to crawl website traffic to a specified crawl depth. [SRD ID 12300] 30The Web Crawl Services shall provide controls to preventexcessive collection of web content, including, at a minimum,the ability to limit the size of the web crawl; the ability tocontrol whether the crawler will traverse links that are offserverrelative the root URL. [SRD ID 12400] 30The Web Crawl Services shall provide the capability to passPKI client certificates in response to a challenge by a webserver. [SRD ID 12500] 30Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-188

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement1260012700128001290013000131011310213103The Web Crawl Services shall provide the ability to collectHTTP and HTTPS. [SRD ID 12600] 30The Web Crawl Services shall ensure that collected content canbe viewed organically (using existing RBM software) on theRBM without the need to repopulate a web server. [SRD ID12700] 30The Web Crawl Services shall implement techniques tominimize impacts to crawled web servers (e.g., comply withrobots.txt). [SRD ID 12800] 30The FTS with Management Service shall provide a webservices based interface for injecting content into the broadcast.[SRD ID 12900] 30The FTS with Management Service shall provide transmissionstatus for individual products including feedback on RBMreception if available. [SRD ID 13000] 30The FTS with Management Service shall provide sources theability to access the functionality to cancel transmission ofproducts not yet broadcast. [SRD ID 13101] 30The FTS with Management Service shall provide sources theability to access the functionality to delete products from thesystem not yet broadcast. [SRD ID 13102] 30The FTS with Management Service shall provide sources theability to access the functionality to estimate transmission timefor a product. [SRD ID 13103] 30Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-189

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement131041310513106132001330013400135001360013700The FTS with Management Service shall provide sources theability to access the functionality to re-transmit sourceproducts. [SRD ID 13104] 30The FTS with Management Service shall provide sources theability to access the functionality to request a return receipt (asavailable) from fully connected receive suites. [SRD ID 13105] 30The FTS with Management Service shall provide sources theability to access the functionality that provides the list ofauthorized receive suites available to the source. [SRD ID13106] 30The Source Managed Tunneled Content Service shall providethe ability to route source streaming content directly into thebroadcast stream without any additional processing. [SRD ID13200] 4-1The Source Managed Tunneled Content Service shall providelocal (within the BDA) bandwidth management control thatcan restrict the amount of bandwidth a specific source receivesto be commensurate with the COCOM TIM priorities andbandwidth limitations placed on the source. [SRD ID 13300] 28The Source Managed Tunneled Content Service shall bebackwards compatible with existing source-managed users thatcurrently use Fazzt Power Publisher 7.1 or provide afunctionally similar application for these sources. [SRD ID13400] 1-1The Mirrored FTS Services shall provide a capability toreplicate all content of a directory including all sub-directoriesand their content at the SBM to the RBM. [SRD ID 13500] 28The Mirrored FTS Services, after the initial directory content isbroadcast and replicated, shall provide the capability to onlybroadcast incremental changes in the SBM directory. [SRD ID13600] 28The Mirrored FTS Services shall provide a capability to selectthe periodicity of the incremental updates. [SRD ID 13700] 28Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 30: The SBM and TSBM (using reachback connectivity) shall provide an automated interfacethat provides GBS status information (including receive suite (and associated user) coverage statusand product delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-190

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement138001390014000141001420014300The Video Services shall have the capability to ingest MPEG-2or MPEG-4 H.264 encoded video streams and rebroadcast thestreams as a different multicast address using the sameencoding algorithm. [SRD ID 13800] 1-1The Video Services shall be capable of transcoding videosfrom one format to another, specifically supporting at aminimum, the conversion from MPEG-2 to MPEG-4 H.264,MPEG-2 over ATM to MPEG-2 over IP, and MPEG-2 overATM to MPEG-4 over IP. [SRD ID 13900] 1-1The Video Services shall be capable of transrating videos fromone encoding rate to another. [SRD ID 14000] 1-1The Video Services shall be capable of converting video streamresolutions, specifically at a minimum, the conversion fromMPEG-2 HD to MPEG-2 SD and MPEG-4 H.264 HD toMPEG-4 H.264 SD. [SRD ID 14100] 1-1The Video Services shall be capable of transmitting metadatain pre-encoded streams, if present (e.g. Closed Captioning Line21, KLV). [SRD ID 14200] 1-1The Video Services shall be capable of encoding native analogor digital streams and any associated metadata as MPEG-2 SD,MPEG-2 HD, MPEG-4 H.264 SD or MPEG-4 H.264 HDformatted video. [SRD ID 14300] 1-1Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).14400145001451014511The Video Services shall be able to simultaneously encode atleast 10 analog video streams and be capable of scaling toencode 25 analog video streams. [SRD ID 14400] 1-1The Video Services shall have the capability to simultaneouslysupport three modes of video operations:Transcoding/Transrating, Remapping, and Encoding. [SRD ID14500] 1-1The Video Services, at a minimum, shall simultaneouslytranscode/transrate eighteen (18) videos: 10 videos for theSecret enclave and 4 videos each for Unclassified and ROKUSenclave. [SRD ID 14510] 1-1The Video Services, at a minimum, shall simultaneouslytranscode/transrate thirty-six (36) videos: 20 videos for theSecret enclave and 8 videos each for Unclassified and ROKUS.[SRD ID 14511] 1-1Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-191

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement145201452114530The Video Services, at a minimum, shall simultaneously remapone hundred (100) videos: 80 videos for the Secret enclave,14 videos for Unclassified and 6 videos for ROKUS. [SRD ID14520] 1-1The Video Services, at a minimum, shall simultaneously remaptwo hundred (200) videos: 160 videos for the Secret enclave,28 videos for Unclassified and 12 videos for ROKUS. [SRD ID14521] 1-1The Video Services, at a minimum, shall simultaneouslyencode eighteen (18) videos: 10 videos for the Unclassifiedenclave and 4 videos each for Secret and ROKUS. [SRD ID14530] 1-1Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).14531146001470014800149001500015100The Video Services shall simultaneously encode thirty-six (36)videos: 20 videos for the Unclassified enclave and 8 videoseach for Secret and ROKUS. [SRD ID 14531] 1-1The Video Services shall support use of the same multicastaddresses for two or more satellite downlinks. [SRD ID 14600] 1-1The Streaming Packet Service shall support the processing ofIP multicast data streams at data rates up to 20 Mbps each.[SRD ID 14700] 4The Streaming Packet Service shall support the passing ofpreviously encrypted IP data at levels up to and includingTS/SCI. [SRD ID 14800] 4, 4-4The Streaming Packet Service shall accept EncapsulatedSecurity Payload (ESP) packets from a source and be able toroute them over the broadcast. [SRD ID 14900] 4, 4-4The EPG shall provide three days of broadcast history, specificto each individual receive suite that will allow the RBMs todetermine what broadcast content that was intended for themwas not received. [SRD ID 15000] 10The EPG shall provide a listing of all GBS broadcast videosand relevant reception information such as multicast IPaddresses, port numbers, etc. [SRD ID 15100] 1030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-192Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold). Req4-4: The SBM shall manage all file-based services ranging in classification from unclassified upand including TS/SCI (Block-3 Objective).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold). Req4-4: The SBM shall manage all file-based services ranging in classification from unclassified upand including TS/SCI (Block-3 Objective).Req 10: The GBS System shall provide unclassified and classified electronic program guides forinformation providers and users receiving the broadcast or using network centric connectivity to theSBM to easily determine what, when, and where information shall be or has been broadcast(Threshold). The RBM shall be capable of interacting with IDM tools to provide a unified interfaceto allow end users to access all their information products (Block-3 Threshold).Req 10: The GBS System shall provide unclassified and classified electronic program guides forinformation providers and users receiving the broadcast or using network centric connectivity to theSBM to easily determine what, when, and where information shall be or has been broadcast(Threshold). The RBM shall be capable of interacting with IDM tools to provide a unified interfaceto allow end users to access all their information products (Block-3 Threshold).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement1520015300154001550015600The EPG shall be provided for each enclave and be availableover-the-air and via the appropriate network connection. [SRDID 15200] 10The EPG shall provide a web announcements page that allowsGBS operations managers and TIMs to provide daily GBSupdates. [SRD ID 15300] 10The Heartbeat shall provide a unique identifier on eachbroadcast stream to identify the associated satellite and uplinkmodulator. [SRD ID 15400] 27, 28, 29, 30The Heartbeat shall include a free form text message capabilityof at least 256 full characters that is displayed as a banner uponreception. [SRD ID 15500] 27, 28, 29, 30The Heartbeat shall use reports received from RBMs as theprimary means for determining which RBMs are active andwhich satellite uplink modulator(s) are being received by eachRBM. [SRD ID 15600] 27, 28, 29, 3030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-193Req 10: The GBS System shall provide unclassified and classified electronic program guides forinformation providers and users receiving the broadcast or using network centric connectivity to theSBM to easily determine what, when, and where information shall be or has been broadcast(Threshold). The RBM shall be capable of interacting with IDM tools to provide a unified interfaceto allow end users to access all their information products (Block-3 Threshold).Req 10: The GBS System shall provide unclassified and classified electronic program guides forinformation providers and users receiving the broadcast or using network centric connectivity to theSBM to easily determine what, when, and where information shall be or has been broadcast(Threshold). The RBM shall be capable of interacting with IDM tools to provide a unified interfaceto allow end users to access all their information products (Block-3 Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interface

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).15700The Tuning Guide shall include all necessary informationrequired to tune each GBS RBM to the appropriate satellite andbegin reception of products. [SRD ID 15700] 43-1, 43-215801 The Tuning Guide shall be Unclassified. [SRD ID 15801] 43-1, 43-21580215803159001600016100The Tuning Guide shall be provided for each enclave. [SRD ID15802] 43-1, 43-2The Tuning Guide shall be available over-the-air and via allnetwork connections. [SRD ID 15803] 43-1, 43-2The Tuning Guide shall allow the SBM Operator to update theNIPRNET Tuning Guide within 5 minutes after being notifiedof JIPM updates by the Tactical Network Controller (TNC).[SRD ID 15900] 43-1, 43-2The Tuning Guide shall allow the SBM Operator to update theSIPRNET and ROKUS Tuning Guide within 2 hours of beingnotified of JIPM updates by the TNC. [SRD ID 16000] 43-1, 43-2The Tuning Guide shall include all scheduled changes to thetuning plan. [SRD ID 16100] 43-1, 43-330 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-194Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-2: The BFC shall useDISN connectivity and bandwidth to connect information sources to BFC’s managed multi Terabytedispersed content staging storage locations and to move content between staging locations as needed(Block-3 Threshold).Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-2: The BFC shall useDISN connectivity and bandwidth to connect information sources to BFC’s managed multi Terabytedispersed content staging storage locations and to move content between staging locations as needed(Block-3 Threshold).Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-2: The BFC shall useDISN connectivity and bandwidth to connect information sources to BFC’s managed multi Terabytedispersed content staging storage locations and to move content between staging locations as needed(Block-3 Threshold).Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-2: The BFC shall useDISN connectivity and bandwidth to connect information sources to BFC’s managed multi Terabytedispersed content staging storage locations and to move content between staging locations as needed(Block-3 Threshold).Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-2: The BFC shall useDISN connectivity and bandwidth to connect information sources to BFC’s managed multi Terabytedispersed content staging storage locations and to move content between staging locations as needed(Block-3 Threshold).Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-2: The BFC shall useDISN connectivity and bandwidth to connect information sources to BFC’s managed multi Terabytedispersed content staging storage locations and to move content between staging locations as needed(Block-3 Threshold).Req 43-1: The BFC shall direct receive suites to which space segment and transponder resourcewill provide each broadcast, including seamlessly managing the transition of in transit users fromone space segment satellite region to another (Block-3 Threshold). Req 43-3: The BFC shall useDISN connectivity and bandwidth to connect information content staging storage locations todispersed or redundant PIP facilities to implement GBS as both a broadcast over GBS dedicated orGBS allocated space segment resource, but also permit “scrounge” use of other non GBS SATCOM

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementresources by employing fly-away PIP kits to take advantage of unused bandwidth on other satellites(DoD leased, but under-subscribed commercial leased transponders) (Block-3 Threshold).162001630016400165001660016700The Content Catalog shall include a list of enclave specificauthorized content and their descriptions that are available for“user pull” from the SBM. [SRD ID 16200] 12The Content Catalog shall be able to display the SBM ContentCatalog over the applicable DISN network and allow selectionand indications of the relative priority of products for deliveryto selected RBMs. [SRD ID 16300] 12The Work Flow Process shall provide access controls thatprevent unauthorized users from creating, modifying, ordeleting information entered by other users. [SRD ID 16400] 1, 20The Work Flow Process shall include, but not be limited to,defining groups and granting/ authorizing access to other userswithin a group to database entries. [SRD ID 16500] 1, 20The Work Flow Process shall be configurable by the SBMoperator to allow end user access to only the information (e.g.,forms and reports) that are allowed by the COCOM TIM. [SRDID 16600] 1, 20The BDA Usability shall provide a means for updatingdisplayed information to ensure access to the latest availabledata. [SRD ID 16700] 27, 28, 29, 3030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-195Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective). Req 20: As an element ofthe GIG, the GBS System shall maintain and guarantee during transport the integrity of file-baseddata that it stores and processes to enable user confidence; information integrity shall be 99.99%(Threshold) and 99.999% (Objective).Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective). Req 20: As an element ofthe GIG, the GBS System shall maintain and guarantee during transport the integrity of file-baseddata that it stores and processes to enable user confidence; information integrity shall be 99.99%(Threshold) and 99.999% (Objective).Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective). Req 20: As an element ofthe GIG, the GBS System shall maintain and guarantee during transport the integrity of file-baseddata that it stores and processes to enable user confidence; information integrity shall be 99.99%(Threshold) and 99.999% (Objective).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementinformation providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orThe BDA Usability shall provide confirmations, either visualvia alternate means (Block-2 Threshold). This GBS status information should also be available to16800 or audible, of user inputs and actions. [SRD ID 16800] 27, 28, 29, 30 information sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast1690017000The BDA Usability shall provide status or mode indicationsduring computations, downloads, or processing activity. [SRDID 16900] 27, 28, 29, 30The BDA Usability shall support at least 250 concurrent users(i.e., GBS Operations Managers, TIM, Content Providers, Endusers with reachback), per enclave, without degradation ofservice. [SRD ID 17000] 27, 28, 29, 3030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-196(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interface

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast171001720017300The BDA Usability shall provide meaningful descriptor fieldsrelevant to RBMs and products to enable convenientmanagement (e.g., sorting, searching, and filtering) ofdisplayed information. [SRD ID 17100] 27, 28, 29, 30The BDA Usability shall employ knowledge managementtechniques (e.g., broadcast efficiency metrics and namingconventions). [SRD ID 17200] 27, 28, 29, 30The SBM shall support the Session Description Protocol forcontent provider entry of video descriptors. [SRD ID 17300] 27, 28, 29, 3030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-197(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBMand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 28: The SBM and TSBM shall be capable ofautomated interface with IDM capabilities to provide a unified mechanism for GBS users,information providers, and TIM to monitor the efficiency and content flow of the GBS broadcast(Block-3 Threshold). Req 29: The SBM and TSBM shall provide an automated interfaceintegrated with IDM for managing portions of broadcast content and priorities, and interacting withIDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold). Req 30: The SBM

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementand TSBM (using reachback connectivity) shall provide an automated interface that provides GBSstatus information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).174001750018000The BDA shall allocate bandwidth from services not currentlyin use to other active services within each enclave. [SRD ID17400] 31The BDA shall be capable of automatically reallocatingbandwidth within a security enclave between streaming anddata services based on changes in service load. [SRD ID17500] 31The BDA shall be capable of generating unique broadcastcontent for each IP Multicast Stream. [SRD ID 18000] 15, 16Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold).Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meet thetimeliness requirements of each product when taken in aggregate, within the constraints imposed onthe broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).1810018200183001840018600The BDA shall dynamically share and re-allocate bandwidthfor data products between enclaves, using flow controlfeedback from the JIPM hub. [SRD ID 18100] 31The BDA shall be a single integrated application, able tooperate identically on multiple security enclaves, and supportfile-based Multicast Content delivery and Streaming Services.[SRD ID 18200] 31The BDA shall operate Fazzt 7.1 and higher versions, orequivalent software. [SRD ID 18300] 1-1, 31The BDA shall be installed at the DECC locations and operateon a DECC approved OS (Linux, MS, Unix, etc). [SRD ID18400] 1-1, 31The BDA shall be backwards compatible with the legacyreceive suite software (i.e., receive unclass/class files,streaming products [video, tunneled data, Power Publisher,etc], EPG displays, heartbeats, and web content) whilesupporting RBM presences displays and over-the-air updates.[SRD ID 18600] 1-1, 31Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold).Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-198

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement187001880018900190001910019200The BDA shall simultaneously support broadcasts at both JIPMand non-JIPM enabled uplink facilities. [SRD ID 18700] 1-1, 31The BDA shall support Microsoft Internet Explorer browserversion 5.5 and higher versions supported by Microsoft. [SRDID 18800] 1-1, 31The BDA shall support Mozilla Firefox version 1.5 and higherversions that are supported by Mozilla. [SRD ID 18900] 1-1, 31The BDA shall adjust transmit data rates, within each enclave,with minimal interruption to the broadcast (e.g., 1 minute orless). [SRD ID 19000]. 1-1, 31The BDA shall allow the SBM to share and reallocate availablebandwidth dynamically, in near-real time among various users,information products, multi-media types (data, video, andaudio), and security release levels without interruption to thebroadcast. [SRD ID 19100] 31, 33The BDA shall allow the SBM to dynamically, in near-realtime , allocate a portion of the bandwidth to insert lowerpriority, unscheduled information products where unusedbandwidth exists. [SRD ID 19200] 31, 32Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 31: The SBM and TSBM shall share and reallocate availablebandwidth dynamically, in near-real time among various users, information products, multi-mediatypes (data, video, & audio), and security release levels without interruption to the broadcast (Block-2 Threshold).Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold). Req 33: TheSBM and TSBM shall adjust transmit data rates with minimal interruption to the broadcast,consistent with the receive suite synchronization timeline (Threshold).Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold). Req 32: The SBMand TSBM shall be capable of dynamically in near-real time allocating a portion of the bandwidthinserting lower priority, unscheduled information products where unused bandwidth exists (Block-2Threshold).19300The BDA shall pre-empt files when higher priority/precedencefiles are available for broadcast. [SRD ID 19300] 16Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).1940019500The BDA shall resume transmission of products that werepreempted without loss of data. [SRD ID 19400] 16The BDA shall provide a capability for operators to setbandwidth allocations between security enclaves that cannot beoverridden by automatic controls. [SRD ID 19500] 31, 3330 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-199Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold). Req 33: TheSBM and TSBM shall adjust transmit data rates with minimal interruption to the broadcast,consistent with the receive suite synchronization timeline (Threshold).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement1960019700The BDA shall automatically delete ingested files after aminimum of 3 days. [SRD ID 19600] 12The BDA shall store all ingested data files for at least 3 days toprovide the end users the ability to request file rebroadcast.[SRD ID 19700] 12Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).19801199002000020001The BDA shall allow the SBM to automatically protect andstore queued information and systematically shut down afterloss or fluctuations of external power. [SRD ID 19801] 45The BDA shall process User Pull request based on current 14, 39, 43-4,broadcast profile priorities. [SRD ID 19900]161The GBS Network Management Software (NMS) shall becapable of automatically alerting local GBS operators ofchanges in SBM network element status or critical failures ofsystems that impact the broadcast of data via audible alarms,email, pages, and pop-up alarms in a manner consistent withthe rules of the security enclave that the NMS is managing.[SRD ID 20000] 2-1The BDA shall provide automated over-the-air (OTA) softwareand Information Assurance updates to GBS JPO procuredRBMs. [SRD ID 20001] 2-1Req 45: The SBM, and PIP shall have the ability to automatically protect and store queuedinformation and protect system equipment in order to logically and systematically shut down or torapidly resume broadcast operations after loss or fluctuations of external power (Threshold).Req 14: The manner in which the information provider and GBS system responds to user pullrequest shall permit either the delivery of requisite information directly to the user (Threshold) or asa broadcast service to a community of interest (COI), which the user subscribes when initiating therequest (Block-3 Threshold, Block-2 Objective). All members of the COI, based upon assignedpriority shall receive the user pull response. Req 39: The SBM and TSBM shall be capable ofreceiving “user pull” data on the return channel satellite. The SBM and TSBM shall be capable ofrouting the “user pull” data to selected sources (Block-3 Threshold). Req 43-4: Req 43-4: TheBFC shall implement “User-Pull” as a broadcast service to COI across multiple space segmentresources (Block-3 Threshold).. Req 161: BMS shall permit compartment and above US Secretinformation providers to control the broadcast stream based on user pull across SCI networks(Block-3 Threshold).Req 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets.Req 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets.2020020500The BDA shall respond to TIM authorized re-broadcastrequests based on current broadcast profile priorities and themissed files reports. [SRD ID 20200] 39The Operations Management Activity (OMA) shall provide theinformation and tools necessary for coordinating the use ofsatellite and uplink resources between the SBM, the TeleportSites, the UFO PIPs, RSSC, WSOC, and other entities sharingGBS resources. [SRD ID 20500]16 ,21, 21-1,21-2, 21-3, 4030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-200Req 39: The SBM and TSBM shall be capable of receiving “user pull” data on the return channelsatellite. The SBM and TSBM shall be capable of routing the “user pull” data to selected sources(Block-3 Threshold).Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 21: The GBS System shall permit frequent pointing of steerable GBS satellite spot beamantennas to cover mission specific requirements and geographically dispersed users. (KPP –Threshold). Req 21-1: The SBM shall be the primary means for tasking GBS dedicated steerable

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementsatellite antennas using direct and continuous satellite payload control to execute every scheduled orad-hoc directed change (Threshold) and then shall use satellite telemetry to detect the completion ofsatellite beam pointing and trigger the restart of broadcast transmission (Block-3 Threshold, Block-2Objective). For ad-hoc directed changes, spot beam pointing command processing shall not exceed10 minutes from receipt at SBM to command uplink (Threshold). The SBM shall provide amechanism to manually (Threshold) automatically (Block-3 Threshold, Block-2 Objective) executea schedule of satellite commands for antenna pointing. The SBM shall operate WGS in “fixed”mode of operations in which the SBM requests and is then authorized bandwidth associated withfixed pointed WGS spot beam(s) for fixed periods of time (Block-2 Threshold); and operate in“dedicated” (UFO emulation) mode of operations in which the SBM has been authorized completeand possibly direct control over one or more WGS spot beams and the associated bandwidth (Block-2 Objective). Req 21-2: For steerable satellite antennas not dedicated to GBS, the SBM shallprovide mechanisms for interaction with the spot beam resource controllers, to: (1) Petition forcoverage and bandwidth allocations or reservations of either a long term duration commitment or fora short duration response; (2) Receive notification that coverage and bandwidth are currentlyavailable and to respond in order to take advantage of the resource; (3) Exchange status reporting toeffectively take advantage of non-dedicated share resources (Block-3 Threshold). Req 21-3: TheGBS System shall support an automated, priority based, information product queue driven spotbeam pointing capability (KPP – Block-3 Threshold, Block-2 Objective). Req 40: The SBM shallprovide an automated resource allocation tool to assist Combatant Commander planners, users, andinformation providers in efficient utilization of GBS resources (Threshold).2050120600The Operations Management Activity (OMA) shall providethe information and tools necessary accepting system statusinformation and displaying the status of criticalcomponents to the help desk. [20501]The OMA shall provide a capability for the GBS operationsmanagers to set bandwidth allocations within a security enclavebetween streaming and data services. [SRD ID 20600] 31, 33Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold). Req 33: TheSBM and TSBM shall adjust transmit data rates with minimal interruption to the broadcast,consistent with the receive suite synchronization timeline (Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-201

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement20700208002090021000211002115021200The OMA shall allow the GBS operations managers to regulatebandwidth allocation for source encrypted streaming packetsand integrate their information into the broadcast based uponpriorities and coverage to intended users. [SRD ID 20700] 4-2The OMA shall allow the GBS operations managers to enter orremove authorized RBMs from the broadcast. [SRD ID 20800] 23, 24, 28, 29The OMA shall allow the GBS operations managers to assignstreaming and video products to one or more specific satellitedownlinks. [SRD ID 20900] 37The OMA shall allow the GBS operations managers to enterauthorized information providers into the broadcast. [SRD ID21000] 24The GBS System Monitoring Service shall provide SBMinformation accessible via a web browser over SIPRNET andvia an open, defined Web Services SIPRNET interface. [SRDID 21100] 2-1, 28, 30The GBS System Monitoring Service shall include thecapability to collate and format selected SBM information andaudit logs into historical textual and graphical reports. [SRD ID21150] 28,29The GBS System Monitoring Service shall providereporting status, key metrics, and configurable alerts of keySBM system elements and GBS usage statistics. [SRD ID21200] 28,29Req 4-2: The SBM shall exercise flow-control over compartmented sources and integrate theirinformation into the broadcast based upon priorities and coverage to intended users (Block-2Threshold).Req 23: The GBS System shall provide the capability to key GBS specific cryptographicequipment manually (Threshold) and to rekey GBS specific cryptographic equipment through Overthe-AirRekey (OTAR) (Objective). Req 24: The GBS System shall include the ability to remotelydeny individually designated receive suite access to the entire broadcast (Threshold). The GBSSystem shall include the ability to remotely re-enable receive suite access to the broadcast(Objective). Req 28: The SBM and TSBM shall be capable of automated interface with IDMcapabilities to provide a unified mechanism for GBS users, information providers, and TIM tomonitor the efficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: TheSBM and TSBM shall provide an automated interface integrated with IDM for managing portions ofbroadcast content and priorities, and interacting with IDM tools to assist TIM in efficient broadcastplanning (Block-3 Threshold).Req 37: The SBM shall manage the broadcast content for WGS coverage areas based upon a singlespot beam’s coverage for each unique broadcast injected (Block-2 Threshold), or be capable ofusing WGS satellite features to duplicate the same uplink broadcast stream into multiple downlinkcoverage areas simultaneously (Block-3 Threshold, Block-2 Objective).Req 24: The GBS System shall include the ability to remotely deny individually designated receivesuite access to the entire broadcast (Threshold). The GBS System shall include the ability toremotely re-enable receive suite access to the broadcast (Objective).Req 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets. Req 28: TheSBM and TSBM shall be capable of automated interface with IDM capabilities to provide a unifiedmechanism for GBS users, information providers, and TIM to monitor the efficiency and contentflow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM and TSBM (using reachbackconnectivity) shall provide an automated interface that provides GBS status information (includingreceive suite (and associated user) coverage status and product delivery status and broadcast queuestatus) to various privileged information providers, including IDM, in order for informationproviders to make intelligent decisions about routing data via GBS or via alternate means (Block-2Threshold). This GBS status information should also be available to information sources, GBSusers, and TIMs (Block-3, Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-202

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementReq 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets. Req 28: TheThe GBS System Monitoring Service shall monitor andreport the operational status of key SBM elements (e.g.,SBM and TSBM shall be capable of automated interface with IDM capabilities to provide a unifiedmechanism for GBS users, information providers, and TIM to monitor the efficiency and contentingest, DMZ, enclave servers, applications and softwareflow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM and TSBM shall provide an21201processes, encryption, and ingest and egress networkautomated interface integrated with IDM for managing portions of broadcast content and priorities,connections). [SRD ID 21201] 2-1, 28,29 and interacting with IDM tools to assist TIM in efficient broadcast planning (Block-3 Threshold).(Req: 2-1) The GBS System shall be capable of automatically reporting the status of TransmitSuite transport elements (e.g. switches & routers) to the DISN Integrated Network ManagementSystem 99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have anautomated network management capability to obtain status of networks and associated assets. Req28: The SBM and TSBM shall be capable of automated interface with IDM capabilities to providea unified mechanism for GBS users, information providers, and TIM to monitor the efficiency andcontent flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM and TSBM shallprovide an automated interface integrated with IDM for managing portions of broadcast content and21202This Current SBM status information shall be current to withinpriorities, and interacting with IDM tools to assist TIM in efficient broadcast planning (Block-35 minutes. [SRD ID 21202] 2-1, 28,29 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor the2130021301213022130321400The GBS System Monitoring Service shall provide status ofkey RBM system elements and GBS usage statistics [SRDID 21300] 28,29The GBS System Monitoring Service, shall provide thestatus of every active RBM being served by the broadcast,as determined from the RBM Status Service and the RBMStatus Proxy Service. [SRD ID 21301] 28,29The GBS System Monitoring Service, shall provide thecapability to exclude RBMs based on operationalsecurity constraints. [SRD ID 21302] 28,29This Current RBM status information shall be current to within10 minutes. [SRD ID 21303] 28,29The GBS System Monitoring Service shall provide status ofkey SBM system elements and GBS usage statistics thatincludes, but is not limited, to the Broadcast Coverage Map.[SRD ID 21400] 28,2930 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-203efficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementReq 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theThe GBS System Monitoring Service, with respect to theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andBroadcast Coverage Map, shall generate a graphical display ofTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastthe current GBS geographical satellite coverage footprints.content and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning21401 [SRD ID 21401] 28,29(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities to214022140321404214052150021501The GBS System Monitoring Service, with respect to theBroadcast Coverage Map, shall identify the associated satelliteand uplink modulator(s) and the uplink and downlink broadcastfrequencies available within each footprint. [SRD ID 21402] 28,29The GBS System Monitoring Service, with respect to theBroadcast Coverage Map, shall include access to a tabulationof all active RBMs within each footprint. And a graphicaldisplay for RBMs with known locations [SRD ID 21403]. 28,29The GBS System Monitoring Service, with respect to theBroadcast Coverage Map, shall provide the capability toexclude RBMs based on operational security constraints. [SRDID 21404] 28,29The GBS System Monitoring Service, with respect to theBroadcast Coverage Map, shall display the geographicallocation for all active RBMs (whose geographical locations arealready known) except as precluded by operational securityconstraints. [SRD ID 21405] 28,29The GBS System Monitoring Service shall provide status ofkey SBM system elements that includes, but is not limited to,the GBS Usage Statistics. [SRD ID 21500] 28,29The GBS System Monitoring Service, with respect to GBSUsage Statistics, shall store, process, compile historicalinformation, and generate usage statistics over selectable timeintervals for each enclave. [SRD ID 21501] 28,29provide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-204

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement2150221503The GBS System Monitoring Service, with respect to GBSUsage Statistics, shall include historical informationparameters, but are not limited to, broadcast type (e.g. video,streaming packet, files), rebroadcast requests, and by user pullrequests. [SRD ID 21502] 12, 28, 29The GBS System Monitoring Service, with respect to GBSUsage Statistics, shall provide the ability to generate, in theSecret enclave, a merged usage statistical report on a dailybasis. [SRD ID 21503] 28,29Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “userpull” requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold). Req 28: The SBM and TSBM shall be capable of automated interface withIDM capabilities to provide a unified mechanism for GBS users, information providers, and TIM tomonitor the efficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: TheSBM and TSBM shall provide an automated interface integrated with IDM for managing portions ofbroadcast content and priorities, and interacting with IDM tools to assist TIM in efficient broadcastplanning (Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).2160121602The NETOPS Reporting Services shall provide selectableelements from the Current SBM Status monitoring service tothe DISN Integrated Network Management System (INMS).[SRD ID 21601] 163The NETOPS Reporting Services shall provide selectableelements from the Current RBM Status monitoring service tothe DISN Integrated Network Management System (INMS).[SRD ID 21602] 163Req 163: GBS BMS shall implement network management to enhanced integration with TheaterCommunications Coordination Center (TCCC) through reporting of real time GBS allocationsaccording to operations being supported (Block-3 Threshold, Block-2 Objective).Req 163: GBS BMS shall implement network management to enhanced integration with TheaterCommunications Coordination Center (TCCC) through reporting of real time GBS allocationsaccording to operations being supported (Block-3 Threshold, Block-2 Objective).21700The NETOPS Reporting Services shall provide a capability forclient access to the RNOSC INMS system for the purpose ofreceiving and viewing INMS network maps. [SRD ID 21700] 163Req 163: GBS BMS shall implement network management to enhanced integration with TheaterCommunications Coordination Center (TCCC) through reporting of real time GBS allocationsaccording to operations being supported (Block-3 Threshold, Block-2 Objective).218002190022000The NETOPS Reporting Services shall provide the capabilityto filter and report GBS system trouble tickets to the TroubleManagement System (TMS). [SRD ID 21800] 163The Uplink Modulator Planning Services shall allow a GBSoperational manager or TIM to manually associate specificRBMs with uplink modulators on all GBS satellites (WGS,UFO, commercial, etc.). [SRD ID 21900] 81The Uplink Modulator Planning Services shall provide thecapability to process the Satellite Access Authorization (SAA)and configure the system to the expected satelliteconfiguration. [SRD ID 22000] 81Req 163: GBS BMS shall implement network management to enhanced integration with TheaterCommunications Coordination Center (TCCC) through reporting of real time GBS allocationsaccording to operations being supported (Block-3 Threshold, Block-2 Objective).Req 81: GBS shall use WGS satellites in complement with the UFO GBS to provide space segmentresources with interoperable transponder coverage at Ka-band and X-band (KPP – Block-2Threshold). The SBM shall manage the broadcast content for WGS coverage areas based upon asingle spot beam’s coverage for each unique broadcast injected (Block-2 Threshold).Req 81: GBS shall use WGS satellites in complement with the UFO GBS to provide space segmentresources with interoperable transponder coverage at Ka-band and X-band (KPP – Block-2Threshold). The SBM shall manage the broadcast content for WGS coverage areas based upon asingle spot beam’s coverage for each unique broadcast injected (Block-2 Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-205

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementReq 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andThe Bandwidth Utilization and Configuration ManagementTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastServices shall provide a display of the current broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning22100 multicast streams by uplink modulator. [SRD ID 22100] 28,29(Block-3 Threshold).222002230022400225002260022700The Bandwidth Utilization and Configuration ManagementServices shall provide a display of the current broadcastmulticast stream allocations between data and streamingservices and a breakdown of its constituent parts. [SRD ID22200] 28,29The Bandwidth Utilization and Configuration ManagementServices shall accept manual inputs from the GBS operationsmanager that allow control of the bandwidth allocationsbetween multicast streams in case of the loss of flow controlfeedback from the JIPM hub. [SRD ID 22300] 31, 33The Queue Status Services shall provide the GBS OperationsManager or TIM with a display of current status within thequeue for each uplink modulator. [SRD ID 22400] 28,29The Queue Status Services shall provide the GBS OperationsManager or TIM with a display of the statistics of individualproducts including but not limited to: list of files delivered,time of delivery, size of files. [SRD ID 22500] 28,29The OMA shall provide a status display of the streaming datafor each uplink modulator including, but not limited to, a list ofstream names, type of stream, data rate, and the uplinkmodulators over which the streams are being broadcast. [SRDID 22600] 28,29The OMA shall provide a report showing the collectionstatistics and status of each web product. [SRD ID 22700] 28,29Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 31: The SBM and TSBM shall share and reallocate available bandwidth dynamically, in nearrealtime among various users, information products, multi-media types (data, video, & audio), andsecurity release levels without interruption to the broadcast (Block-2 Threshold). Req 33: TheSBM and TSBM shall adjust transmit data rates with minimal interruption to the broadcast,consistent with the receive suite synchronization timeline (Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 29: The SBM andTSBM shall provide an automated interface integrated with IDM for managing portions of broadcastcontent and priorities, and interacting with IDM tools to assist TIM in efficient broadcast planning(Block-3 Threshold).22800The Mission Priority Services shall accept manual entry ofpertinent information from the GBS Mission Requests (GMR).[SRD ID 22800] 16Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-206

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement22900The Mission Priority Services shall prioritize the broadcastqueue based on user mission as described in the CJCSI 6250.01and the relative priority of products being used to support thatmission. [SRD ID 22900] 16, 20Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).229302295023500236002400024050The Mission Priority Services shall provide an interface toidentify the GBS products needed to identify the GBS productsneeded to support specific user missions. [SRD ID 22930] 16The Mission Priority Services shall provide an interface toassign a relative priority to each product user within a usermission. [SRD ID 22950] 16The Mission Management Services shall display the defineddata stream (file and streaming) and allow the TIM to selectand indicate the relative priority of data streams for broadcast.[SRD ID 23500] 16The Mission Management Services shall allow the TIM toassociate data streams to one or more RBM. [SRD ID 23600] 16The system shall allow a content provider to view the currentstatus of products sent to the SBM. [SRD ID 24000] 28, 30, 92Per enclave, the system shall provide the capability to test thebroadcast data connectivity, protocols, security infrastructure,and application interfaces between an authorized contentprovider and SBM with appropriate measures to ensure suchtesting does not connect to the broadcast. [SRD ID 24050] 19Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 16: The SBM and TSBM shall generate the broadcast and adjust spot beam pointing to meetthe timeliness requirements of each product when taken in aggregate, within the constraints imposedon the broadcast by information product availability, the Combatant Commander’s disseminationpolicy, the user needs, the information priorities, and the satellite spot beam coverage (Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold). Req 92: Receive Suites (usingreachback connectivity) shall provide an automated interface that provides GBS status information(including receive suite (and associated user) coverage status and product delivery status andbroadcast queue status) to various privileged information providers, including IDM, in order forinformation providers to make intelligent decisions about routing data via GBS or via alternatemeans (Block-2 Threshold). This GBS status information should also be available to informationsources, GBS users, and TIMs (Block-3, Threshold).(Req: 19) The System shall have the ability to provide minimum 90percent (Threshold) and 95 percent (Objective) statistical assurance ofreceipt of all broadcast information (measured from the point where thebroadcast information is received in the SBM or TSBM and delivered atthe interface between the RS’s RBM and the attached LAN). The systemmust also provide flexibility to ensure Combatant Commander selected30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-207

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementinformation is delivered with a range of statistical confidencesapproaching guaranteed assurance of receipt (Block-2 Threshold).When a TRS or networked reachback connectivity is available, the returnpath functionality shall be used to provide reliable file producttransmission between the SBM and RBM (Block-3 Threshold).24100242002430024400The system shall provide the capability for the content providerto determine which RBMs will receive a product if sent. [SRDID 24100] 28, 30The system shall provide the necessary information for acontent provider to determine which RBMs are accessible onwhich uplink modulators and the associated Source ManagedTunneled Content Service multicast addresses. [SRD ID24200] 28, 30The system shall allow an authorized content provider to enterdetailed data describing content provider and productinformation. [SRD ID 23000] 28, 30The system shall allow an authorized content provider topreclude their products from being displayed in the contentcatalog. [SRD ID 24400] 12, 28, 30Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold). Req 28: The SBM and TSBM shall be capable of automated interface withIDM capabilities to provide a unified mechanism for GBS users, information providers, and TIM tomonitor the efficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: TheSBM and TSBM (using reachback connectivity) shall provide an automated interface that providesGBS status information (including receive suite (and associated user) coverage status and productdelivery status and broadcast queue status) to various privileged information providers, includingIDM, in order for information providers to make intelligent decisions about routing data via GBS orvia alternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-208

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementReq 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliveryThe system shall provide an interface where a source canprovide one or more Uniform Resource Locator (URL)status and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or via24500addresses that will be displayed at the RBM for simplifiedalternate means (Block-2 Threshold). This GBS status information should also be available toaccess to the source site. [SRD ID 24500] 28, 30information sources, GBS users, and TIMs (Block-3, Threshold).2460024650247002480024900The system shall provide a content provider with a display ofthe current status of file products sent by the content provider.[SRD ID 24600] 28, 30The system shall not provide a content provider the currentstatus of file products sent by another content provider unlessauthorization is provided by the TIM. [SRD ID 24650] 28, 30The system shall provide a content provider with display of thecurrent status of file products sent to the SBM for delivery to aspecific RBM. [SRD ID 24700] 28, 30The broadcast segment shall provide both the primary andCOOP SBMs capability to independently support the globalbroadcast. [SRD ID 24800]20, 26, 26-4,46The broadcast segment shall replicate 100 percent of thesystem management and system configuration parameters atthe COOP site every thirty (30) minutes [TBR-32] to facilitatea transfer of SBM operations. [SRD ID 24900] 20, 26, 4330 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-209Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective). Req 26: The System shallincorporate features permitting system restoration resulting from various SBM or PIP or spacesegment failures (Block-3 Threshold, Block-2 Objective). Req 26-4: Each SBM shall be able torapidly (less than three days) reconstitute 50% SBM capabilities of another SBM facility in order topartially backup and restore broadcast services (Block-3 Threshold), 100% backup (Block-3Objective). Req 46: The SBM shall have an operational availability of 99.00 percent (Threshold)and 99.99 percent (Objective) over a period of 480 hrs.Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective). Req 26: The System shallincorporate features permitting system restoration resulting from various SBM or PIP or spacesegment failures (Block-3 Threshold, Block-2 Objective). Req 43: BMS requirements shall be

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementimplemented with a Global Broadcast Fusion Center (BFC) model, which executes all planning andmanagement functions over broadcast content and coverage areas using a process that looks acrossall GBS space segment resources to direct broadcast execution. The BFC may be implemented withprocesses running under either central control (with geographically separated and paralleloperational redundancy) or running under a cooperative distributed process (Block-3 Threshold).25000251002520025300For a scheduled transfer, the broadcast segment shall transferSBM operations to the COOP site within 1 minute. 43The broadcast segment shall be capable of ingesting aminimum of 300 Mbps of files per enclave (Secret andUnclassified). [SRD ID 25100] 4, 15, 35The broadcast segment shall be capable of ingesting aminimum of 400 Mbps of IP data and video streams perenclave (Secret and Unclassified). [SRD ID 25200] 4, 15, 35The broadcast segment shall be capable of ingesting aminimum of 200 Mbps of files in the ROKUS enclave. [SRDID 25300] 15, 3530 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-210Req 43: BMS requirements shall be implemented with a Global Broadcast Fusion Center (BFC)model, which executes all planning and management functions over broadcast content and coverageareas using a process that looks across all GBS space segment resources to direct broadcastexecution. The BFC may be implemented with processes running under either central control (withgeographically separated and parallel operational redundancy) or running under a cooperativedistributed process (Block-3 Threshold).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold). Req15: The GBS system shall be capable of generating unique broadcast streams at variable data ratesup to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwide withnominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94 Mbpsinto each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24Mbps with a minimum range of data rates to support receive suite capabilities. (Threshold).Worldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600Mbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additionalnumber of transponders (Objective).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold). Req15: The GBS system shall be capable of generating unique broadcast streams at variable data ratesup to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwide withnominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94 Mbpsinto each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24Mbps with a minimum range of data rates to support receive suite capabilities. (Threshold).Worldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600Mbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additionalnumber of transponders (Objective).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementMbps with a minimum range of data rates to support receive suite capabilities. (Threshold).Worldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600Mbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additionalnumber of transponders (Objective).2540025500256002570025800The broadcast segment shall be capable of ingesting aminimum of 200 Mbps of IP data and video streams in theROKUS enclave. [SRD ID 25400] 15, 35The broadcast segment shall support the 10 satellites, 100downlink beams, 56 aggregated streams (each consisting ofmultiple multicast streams to be injected by a specificmodulator at the JIPM hub), 5000 RBMs, 2500 subscriptions(content folders and IP streams), and 250 content providers.[SRD ID 25500] 15, 35The broadcast segment shall be capable of supporting IPv6.[SRD ID 25600] 1-2, 165The broadcast segment shall incorporate IPv6 components, asthey become commercially available. [SRD ID 25700] 1-2, 165The broadcast segment shall be scalable to accommodate a50% increase in the number of satellites, downlink beams,multicast streams, RBMs, subscriptions (content folders and IPstreams), and content providers. [SRD ID 25800]15, 35, 35-1,35-2, 8030 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-211Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24Mbps with a minimum range of data rates to support receive suite capabilities. (Threshold).Worldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600Mbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additionalnumber of transponders (Objective).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24Mbps with a minimum range of data rates to support receive suite capabilities. (Threshold).Worldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600Mbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additionalnumber of transponders (Objective).Req 1-2: New DoD information systems development and modernization programs shouldconform to the DISR. Incremental changes to the GBS shall conform to the DISR during Block 2(Block-2 Threshold) and shall include implementation of IPv6 and SCA compliance during Block 3(Block 3 Threshold). Req 165: GBS System shall implement Internet Protocol version 6 upgradesand Internet Protocol mobility enhancements (Block-3 Threshold).Req 1-2: New DoD information systems development and modernization programs shouldconform to the DISR. Incremental changes to the GBS shall conform to the DISR during Block 2(Block-2 Threshold) and shall include implementation of IPv6 and SCA compliance during Block 3(Block 3 Threshold). Req 165: GBS System shall implement Internet Protocol version 6 upgradesand Internet Protocol mobility enhancements (Block-3 Threshold).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24Mbps with a minimum range of data rates to support receive suite capabilities. (Threshold).Worldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600Mbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additionalnumber of transponders (Objective). Req 35-1: As additional WGS satellites are placed on orbit,additional SBM capacity enhancements shall be incorporated into GBS to take advantage ofadditional space segment resources (Block-3 Threshold). Req 35-2: As additional WGS satellites

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementare placed on orbit, additional PIP connectivity enhancements shall be incorporated into GBS to takeadvantage of additional space segment resources (Block-3 Threshold). Req 80: GBS shall usespace segment capabilities to support the dynamic nature of modern warfare through using multiplecoverage areas, using responsive, independently steerable or fixed coverage areas to locations withinthe satellite’s field of view (Threshold).Req 15: The GBS system shall be capable of generating unique broadcast streams at variable datarates up to a minimum system capacity of 305 Mbps (Block-1) and 600 Mbps (Block-2) worldwidewith nominal per satellite uplink capacity of: 94 Mbps into each GBS UFO satellite (Block-1); 94Mbps into each WGS satellite (Block-2); maximum downlink capacity that meets link performancerequirements for each Commercial Augmentation leased transponder (Block-1) (Threshold). Req35: Worldwide the SBM shall be capable of supporting at least 13 (Block-1 Threshold) 26 (Block-2 Threshold) active broadcast transponders each capable of supporting a nominal data rate of 24Mbps with a minimum range of data rates to support receive suite capabilities. (Threshold).The broadcast segment shall be capable of supporting aWorldwide the SBM shall be capable of supporting at least 305 Mbps (Block-1 Threshold) 600nominal data rate of 72 Mbps for each group of multicastMbps (Block-2 Threshold) 1 Gbps (Objective). The SBM shall have capability to add additional25900 streams per modulator. [SRD ID 25900] 15, 35number of transponders (Objective).260002610026200The broadcast segment shall include a DIACAP compliantDMZ. [SRD ID 26000] 1The broadcast segment shall be capable of supporting any mixof file or streaming data (all file, all streaming, any mix of thetwo) on the group of multicast streams per modulator. [SRD ID26100] 28, 30In the event backup power fails, the broadcast segment shallprovide automatic system protection for equipment in order tologically and systematically shut down or rapidly resumebroadcast operations after loss or fluctuations of externalpower. [SRD ID 26200]. 45Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective).Req 28: The SBM and TSBM shall be capable of automated interface with IDM capabilities toprovide a unified mechanism for GBS users, information providers, and TIM to monitor theefficiency and content flow of the GBS broadcast (Block-3 Threshold). Req 30: The SBM andTSBM (using reachback connectivity) shall provide an automated interface that provides GBS statusinformation (including receive suite (and associated user) coverage status and product deliverystatus and broadcast queue status) to various privileged information providers, including IDM, inorder for information providers to make intelligent decisions about routing data via GBS or viaalternate means (Block-2 Threshold). This GBS status information should also be available toinformation sources, GBS users, and TIMs (Block-3, Threshold).Req 45: The SBM, and PIP shall have the ability to automatically protect and store queuedinformation and protect system equipment in order to logically and systematically shut down or torapidly resume broadcast operations after loss or fluctuations of external power (Threshold).26300The broadcast segment, in the event of power failures, shalltake advantage of facility provided uninterrupted powersources. [SRD ID 26300] 44Req 44: In case of power failures, the SBM and PIP shall take advantage of facility provideduninterrupted power sources or provide its own uninterrupted power (Threshold).26400The broadcast segment shall provide the capability to key GBSspecific cryptographic equipment manually. [SRD ID 26400] 23Req 23: The GBS System shall provide the capability to key GBS specific cryptographicequipment manually (Threshold) and to rekey GBS specific cryptographic equipment through Overthe-AirRekey (OTAR) (Objective).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-212

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement3000030101301023010330104301053010630107The RDA status elements shall include, but are not limited tothe RBM Heartbeat. [SRD ID 30000] 92The RBM Heartbeat shall report each active broadcast receivedby each RBM, to include multiple uplink modulators on thesame or different satellites. [SRD ID 30101] 92The RBM Heartbeat shall use a unique identifier on eachreceived broadcast to report the associated satellite and uplinkmodulator. [SRD ID 30102] 92For unclassified enclaves, the RBM Heartbeat shall include amessage field for reporting broadcast reception quality whensuch information is locally available (e.g. from a broadcastRBM). [SRD ID 30103] 92The RBM Heartbeat shall be displayed on every RBMwebpage along with a banner. [SRD ID 30104] 92The RBM Heartbeat banner display shall terminate upon thedeletion of the banner message within the heartbeat. [SRD ID30105] 92The RBM Heartbeat shall indicate a loss of the heartbeat signalvia the displayed icon if any heartbeat is not received for anextended period. [SRD ID 30106] 92Outside a normal shutdown, the RBM shall provide the optionto generate and send an email to the RBM Administrator toindicate a loss of the heartbeat signal. [SRD ID 30107] 92Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-213

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement3400034101341023510035200353003540035500The RDA status elements shall include, but are not limited to,The RBM Profile report. [SRD ID 34000] 92The RBM Profile shall be entered via a web browser. [SRD ID34101] 92The RBM Profile shall include, but not limited to: geographicallocation, satellite uplink modulator(s) providing coverage,receive terminal class (e.g., Small, Medium, Large), and RBMactive times. [SRD ID 34102] 92For each RBM with reachback connectivity (either directly viabroadcast satellite transmission segment or via an alternate IPnetwork), the RDA shall provide status of broadcast receptionand key RBM operating and configuration parameters to theSBM. [SRD ID 35100] 92For each RBM with reachback connectivity (either directly viabroadcast satellite transmission segment or via an alternate IPnetwork), the RDA shall be capable of displaying the mostrecently received status information locally via web browserregardless of reachback connectivity status. [SRD ID 35200] 92For each RBM with reachback connectivity (either directly viabroadcast satellite transmission segment or via an alternate IPnetwork), the RDA shall provide status separately for eachsecurity level. [SRD ID 35300] 92For each RBM with reachback connectivity (either directly viabroadcast satellite transmission segment or via an alternate IPnetwork), the RDA shall allow the status-reporting interval atthe RBM to be configurable (to include but not be limited) toonce per minute. [SRD ID 35400] 92For each RBM with reachback connectivity (either directly viabroadcast satellite transmission segment or via an alternate IPnetwork), the RDA shall allow the status-reporting capability tobe suppressed when required by operational constraints. [SRDID 35500] 92Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-215

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement3560035800359003600036100362003630036400For each RBM with reachback connectivity (either directly viabroadcast satellite transmission segment or via an alternate IPnetwork), the RDA shall provide RBM Status via an open,defined Web Services interface at the SBM, with appropriateIA attributes. [SRD ID 35600] 92Specific to OTA Software and IA Updates only, the RDA shallhave the ability to allow the end user to select if and when theywill install the automated IA updates. [SRD ID 35800] 92Specific to OTA Software and IA Updates only, the RDA shallprocess OTA software updates and include a mode thatoverrides the end user control for critical updates. [SRD ID35900] 92The RDA shall be functionally compatible with the existing IPbroadcast by being able to receive all existing over-the-air GBSservices. [SRD ID 36000] 92The RDA shall be functionally compatible with the existing IPbroadcast by being able to auto-forward content using FTP andFTPS similar to the existing receive suite so that the system canbe interchanged with existing receive suites. [SRD ID 36100] 92The RDA shall be functionally compatible with the existing IPbroadcast by being able to receive and process the GBSheartbeat. [SRD ID 36200] 92The RDA shall be functionally compatible with the existing IPbroadcast by being able to receive and process the GBSElectronic Program Guide. [SRD ID 36300] 92The RDA shall be functionally compatible with the existing IPbroadcast by being able to display the Tuning Guide generatedby the SBM. [SRD ID 36400] 92Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-216

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement3650037000370103701137012370133710037200The RDA shall be functionally compatible with the existing IPbroadcast by being able to provide the receive suite presencedisplay required information. [SRD ID 36500] 92The RDA shall be portable between all supported MicrosoftWindows operating systems. [SRD ID 37000] 92The RDA shall operate on a Linux platform, as designated bythe Government. (Objective) [SRD ID 37010] 92The Linux RDA application version shall meet all therequirements of the Microsoft Windows RDA version.(Objective) [SRD ID 37011] 92The Linux RDA application version shall be controllable andoperable from a web-based HTTPS interface without requiringa keyboard, mouse, or display to operate. (Objective [SRD ID37012] 92The Linux RDA application version shall, at a minimum, bebased on an Intel X86-based architecture. (Objective) [SRD ID37013] 92The RDA shall be capable of supporting IPv6. [SRD ID37100] 1-2, 165The RDA shall be able to display the SBM Content Catalogand allow an end user to select and indicate the relative priorityof products for delivery to their RBM and other RBMs asindicated in their request (User Pull – This applies to RBMsthat have reachback connectivity or users with alternatecommunications means available to access the content catalog).[SRD ID 37200] 12, 1430 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-217Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 1-2: New DoD information systems development and modernization programs shouldconform to the DISR. Incremental changes to the GBS shall conform to the DISR during Block 2(Block-2 Threshold) and shall include implementation of IPv6 and SCA compliance during Block 3(Block 3 Threshold). Req 165: GBS System shall implement Internet Protocol version 6 upgradesand Internet Protocol mobility enhancements (Block-3 Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold). Req 14: The manner in which the information provider and GBS systemresponds to user pull request shall permit either the delivery of requisite information directly to theuser (Threshold) or as a broadcast service to a community of interest (COI), which the usersubscribes when initiating the request (Block-3 Threshold, Block-2 Objective). All members of the

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD RequirementCOI, based upon assigned priority shall receive the user pull response.37300374003750037600The RDA shall provide a subscription request capability for aproduct in the catalog. [SRD ID 37300] 92The RDA shall be delivered as a single disk install with onlyminimal interaction required by the end user/installer (notraining required to perform installation). [SRD ID 37400] 87, 91The RDA shall be capable of being hosted on user specifiedalternative computer platforms after the alternative platform iscertified compatible with GBS and added to a QualifiedProduct List (QPL). [SRD ID 37500] 91, 91-7The RDA shall be capable of operating in an unattended mode,except during configuration changes made after initial setupand during installation of OTA and IA updates. [SRD ID37600] 88, 105Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 87: Receive Suites shall be comprised of a receive terminal, cryptographic equipment (whenrequired), and Receive Broadcast Manager (RBM) equipment (Threshold). Req 91: Receive Suitesshall be scaleable and configurable to satisfy a variety of user installations and broadcast receiverequirements (Threshold). Scaleable and configurable configurations beyond basic receive suiteconfigurations shall be separately procured and accompanied with training and maintenanceaddendums to include at a minimum the following:Req 91: Receive Suites shall be scaleable and configurable to satisfy a variety of user installationsand broadcast receive requirements (Threshold). Scaleable and configurable configurations beyondbasic receive suite configurations shall be separately procured and accompanied with training andmaintenance addendums to include at a minimum the following: Req 91-7: Scalable to permitreceive suite software to be hosted on user specified alternative computer platforms after thealternative platform is certified compatible with GBS and added to a Qualified Product List (QPL)(Block-3 Threshold).Req 88: Receive Broadcast Manager (RBM) shall be capable of operating in an unattended modeexcept for making configuration changes after initial setup (Block-2 Threshold). Req 105: ReceiveTerminals shall be capable of operating in an unattended mode during steady state broadcast datarate operation. (Block-1 Threshold) Operate in an unattended mode after initial setup (Block-2Threshold).37700The RDA shall be compliant, certified, and accredited inaccordance with the DoDI 8510.bb, DIACAP Instructions.[SRD ID 37700] 6Req 6: The GBS shall meet Designated Accreditation Authority (DAA) accreditation requirements,including certification and accreditation IAW DITSCAP process (e.g., CJCSI 6510.01C, DoDI5200.40) (Threshold).379003800038100The RDA shall provide for separation of broadcast contentfrom user data on RBM storage devices. [SRD ID 37900] 1-1The RDA shall provide multiple web-based mechanisms forfinding delivered content, such as indexed search, contentsorting or filename based search. [SRD ID 38000] 92The RDA shall support the forwarding of multicast packetsbased upon IGMP V3 protocols. [SRD ID 38100] 9230 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-218Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also be

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementavailable to information sources, GBS users, and TIMs (Block-3, Threshold).38200383003840038500The RDA shall support the manual configuration of forwardingmulticast over the local area network without the need forIGMP protocols. [SRD ID 38200] 92The RDA shall provide a mechanism for determining what filesor streams were received; which files or streams were intendedfor their RBM, but were missed. [SRD ID 38300] 19, 20The RDA shall automatically execute the use of automated filecleanup (to ensure there is adequate storage to run the system);automated disk de-fragmentation; automated databasemaintenance or any other mechanism required to ensure longterm performance of the software. [SRD ID 38400] 106The RDA shall provide a mechanism for providing systemstatistics and reports that allow end users to see theperformance of the receive system. [SRD ID 38500] 2-1, 12Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 19: The System shall have the ability to provide minimum 90 percent (Threshold) and 95percent (Objective) statistical assurance of receipt of all broadcast information (measured from thepoint where the broadcast information is received in the SBM or TSBM and delivered at theinterface between the RS’s RBM and the attached LAN). The system must also provide flexibility toensure Combatant Commander selected information is delivered with a range of statisticalconfidences approaching guaranteed assurance of receipt (Block-2 Threshold). When a TRS ornetworked reachback connectivity is available, the return path functionality shall be used to providereliable file product transmission between the SBM and RBM (Block-3 Threshold). Req 20: As anelement of the GIG, the GBS System shall maintain and guarantee during transport the integrity offile-based data that it stores and processes to enable user confidence; information integrity shall be99.99% (Threshold) and 99.999% (Objective).Req 106: The Mean Time Between Failure (MTBF) for all receive terminals shall be 2,000 hours(Threshold) and 5,000 hours (Objective). This requirement does not apply to SRS and SSRS antennasystems.Req 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets. Req 12: TheGBS system shall provide, through automated tools, the capability to fulfill “user pull” requestsfrom authorized users and shall provide the means for users to identify specific ad-hoc informationneeds. User pull requests shall be fulfilled on the broadcast through current or held for futurebroadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).38600The RDA shall support Microsoft Internet Explorer browserversion 5.5 and higher versions supported by Microsoft. [SRDID 38600] 1-1Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).38700The RDA shall support Mozilla Firefox version 1.5 and higherversions supported by Mozilla. [SRD ID 38700] 1-1Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-219

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement3880038900The RDA shall provide a capability to filter broadcast filecontent by file extension (e.g. *.exe) to prevent certain types offiles from being received by the RBM. [SRD ID 38800] 8, 20The RDA shall be capable of receiving all services provided bythe uplink. [SRD ID 38900] 89, 90Req 8: With the exception of unclassified video (limited to public domain non-DoD derived andnon-national security related information used in fulfillment of military or intelligence missions), allinformation shall be protected from exploitation during transmission over satellites (Block-2Threshold). Req 20: As an element of the GIG, the GBS System shall maintain and guaranteeduring transport the integrity of file-based data that it stores and processes to enable user confidence;information integrity shall be 99.99% (Threshold) and 99.999% (Objective).Req 89: Receive Suites shall be capable of simultaneously receiving broadcasts originating fromboth a PIP and a TIP (Block-2 Threshold) alternatively the dual capability shall be capable ofreceiving from a PIP or two TIPs (Block-2 Threshold). Simultaneously, receive 4 transponderstreams from a single satellite (Objective). Req 90: Receive Suites shall receive broadcasts atvariable data rates according to the beam and terminal combinations listed in Table 4-1 below (KPP–Threshold). Receive Suites shall automatically adjust their receive data rate to correspond with achange to the broadcast data rate within 10 seconds (Objective).39000391003920039300The RDA shall support the processing of data at variable datarates according to the beam and terminal combinations. [SRDID 39000] 90The RDA shall support the simultaneous processing ofmulticast streams from at least two downlink modulators. [SRDID 39100] 89, 91-3, 91-5The RDA shall provide a web-based mechanism that allowslocally connected (i.e., via LAN) users to utilize the systemfunctionality via a web browser over a local network. [SRD ID39200] 92The RDA shall ensure that broadcast products cannot bewritten to an absolute directory path. [SRD ID 39300] 8, 20Req 90: Receive Suites shall receive broadcasts at variable data rates according to the beam andterminal combinations listed in Table 4-1 below (KPP –Threshold). Receive Suites shallautomatically adjust their receive data rate to correspond with a change to the broadcast data ratewithin 10 seconds (Objective).Req 89: Receive Suites shall be capable of simultaneously receiving broadcasts originating fromboth a PIP and a TIP (Block-2 Threshold) alternatively the dual capability shall be capable ofreceiving from a PIP or two TIPs (Block-2 Threshold). Simultaneously, receive 4 transponderstreams from a single satellite (Objective). Req 91-3: Scalable in number (greater than two) ofsimultaneous space segment transponder broadcasts received (Threshold). Req 91-5: Scalable innumber (greater than one) of unclassified and classified video channels concurrently available to theend user (Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 8: With the exception of unclassified video (limited to public domain non-DoD derived andnon-national security related information used in fulfillment of military or intelligence missions), allinformation shall be protected from exploitation during transmission over satellites (Block-2Threshold). Req 20: As an element of the GIG, the GBS System shall maintain and guaranteeduring transport the integrity of file-based data that it stores and processes to enable user confidence;information integrity shall be 99.99% (Threshold) and 99.999% (Objective).39400The Auto Push functionality shall deliver products via FTP (actas FTP client) to end user systems. [SRD ID 39400] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).39500The Auto Push functionality shall deliver products via FTPS orSFTP (act as FTPS or SFTP client) to end user systems. [SRDID 39500] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-220

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement39600The Auto Push functionality shall allow for pre-configuredordering of related products based on EPG information or otheravailable metadata such as data source, content type, productinformation, etc. [SRD ID 39600] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).39700The Auto Push functionality shall provide the capability todelete, modify, and add subscriptions via a web interface.[SRD ID 39700] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).39800The Auto Push functionality shall maintain directory structuresfor Auto Pushed content. [SRD ID 39800] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).39900The Auto Push functionality shall support multiple end userssubscriptions to the same content at the same location but todifferent end user machines. [SRD ID 39900] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).40000The Auto Push functionality shall be available for any level ofcontent hierarchy or organization. [SRD ID 40000] 11Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).40100402004030040400The Auto Push functionality shall be configurable via a webbrowser (HTTPS) from a network-connected machine. [SRDID 40100] 11The Web Browser content management functionality shallsupport the user-pull of received content from their webbrowser over a local area network. [SRD ID 40200] 12The Web Browser content management functionality shallsupport Microsoft Internet Explorer browser version 5.5 andhigher versions supported by Microsoft [SRD ID 40300] 1-1, 12The Web Browser content management functionality shallsupport Mozilla Firefox version 1.5 and above. [SRD ID40400] 1-1, 12Req 11: The GBS System shall enable the user to develop “smart push” information profiles foridentifying specific information needs (Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 12: The GBS system shall provide, through automated tools, thecapability to fulfill “user pull” requests from authorized users and shall provide the means for usersto identify specific ad-hoc information needs. User pull requests shall be fulfilled on the broadcastthrough current or held for future broadcast coverage areas. “User pull” requests shall be capable ofusing receive suite attached network connectivity or TRS RCS connectivity for automatedinformation retrieval and broadcast (Block-2 Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 12: The GBS system shall provide, through automated tools, thecapability to fulfill “user pull” requests from authorized users and shall provide the means for usersto identify specific ad-hoc information needs. User pull requests shall be fulfilled on the broadcastthrough current or held for future broadcast coverage areas. “User pull” requests shall be capable of30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-221

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementusing receive suite attached network connectivity or TRS RCS connectivity for automatedinformation retrieval and broadcast (Block-2 Threshold).4060040700408004090041000411004200042100The Web Browser content management functionality shalldisplay the Electronic Program Guide. [SRD ID 40600] 12The Web Browser content management functionality shallsupport HTTPS. [SRD ID 40700] 12The Video functionality shall provide means to convert IPvideo to NTSC and PAL, allowing video to be viewed onexternal hardware. [SRD ID 40800] 87, 90The Video functionality shall include a capability of viewingthe transmitted video from the uplink on the local RBM. [SRDID 40900] 87, 90The Video functionality shall provide IP video recordingcapability for at least 30 minutes, at a minimum rate of 3 Mbps, so that incoming video streams can be time shifted. [SRD ID41000] 87, 90The RDA shall provide RBM Local Monitoring functionalitythat displays a statistics page for LAN connected users so thatthey can see the status of incoming files. [SRD ID 41100] 92For RBMs with reachback, the Reception Managementfunctionality shall allow an end user to enter RBM profileinformation. [SRD ID 42000] 92For RBMs with reachback, the Reception Managementfunctionality shall allow an end user to request the rebroadcastof products from the Broadcast Management Segment. [SRDID 42100] 9230 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-222Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold).Req 87: Receive Suites shall be comprised of a receive terminal, cryptographic equipment (whenrequired), and Receive Broadcast Manager (RBM) equipment (Threshold). Req 90: Receive Suitesshall receive broadcasts at variable data rates according to the beam and terminal combinationslisted in Table 4-1 below (KPP –Threshold). Receive Suites shall automatically adjust their receivedata rate to correspond with a change to the broadcast data rate within 10 seconds (Objective).Req 87: Receive Suites shall be comprised of a receive terminal, cryptographic equipment (whenrequired), and Receive Broadcast Manager (RBM) equipment (Threshold). Req 90: Receive Suitesshall receive broadcasts at variable data rates according to the beam and terminal combinationslisted in Table 4-1 below (KPP –Threshold). Receive Suites shall automatically adjust their receivedata rate to correspond with a change to the broadcast data rate within 10 seconds (Objective).Req 87: Receive Suites shall be comprised of a receive terminal, cryptographic equipment (whenrequired), and Receive Broadcast Manager (RBM) equipment (Threshold). Req 90: Receive Suitesshall receive broadcasts at variable data rates according to the beam and terminal combinationslisted in Table 4-1 below (KPP –Threshold). Receive Suites shall automatically adjust their receivedata rate to correspond with a change to the broadcast data rate within 10 seconds (Objective).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement4220042300435004360043700For RBMs with reachback, the Reception Managementfunctionality shall allow an end user to view the system-tuningguide. [SRD ID 42200] 92For RBMs with reachback, the Reception Managementfunctionality shall allow an end user to pull content from eitherSBM’s Content Catalog or via source URL. [SRD ID 42300] 12, 92For RBMs using a proxy, the Reception Managementfunctionality shall include a capability for manual entry of keyRBM information by a proxy. [SRD ID 43500] 92For RBMs using a proxy, the Reception Managementfunctionality shall allow key information to be entered via aweb browser. This information may include but is not limitedto: geographical location, satellite uplink modulator(s)providing coverage, RBM Active times, IAVA status, receiveterminal class (e.g., Small, Medium, Large), and RBMApplication Information. [SRD ID 43600] 92For RBMs using a proxy, the Reception Managementfunctionality shall include each RBM in the broadcast(s) usingthe best information available even if some parameters are notentered by the proxy. [SRD ID 43700] 92Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “userpull” requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold). Req 92: Receive Suites (using reachback connectivity) shall provide anautomated interface that provides GBS status information (including receive suite (and associateduser) coverage status and product delivery status and broadcast queue status) to various privilegedinformation providers, including IDM, in order for information providers to make intelligentdecisions about routing data via GBS or via alternate means (Block-2 Threshold). This GBS statusinformation should also be available to information sources, GBS users, and TIMs (Block-3,Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).Req 92: Receive Suites (using reachback connectivity) shall provide an automated interface thatprovides GBS status information (including receive suite (and associated user) coverage status andproduct delivery status and broadcast queue status) to various privileged information providers,including IDM, in order for information providers to make intelligent decisions about routing datavia GBS or via alternate means (Block-2 Threshold). This GBS status information should also beavailable to information sources, GBS users, and TIMs (Block-3, Threshold).4415044500The broadcast segment hardware and software shall operatewithin the DECC infrastructure. [SRD ID 44150] 87The SBM to DECC Facility interfaces shall comply with [theTBD-1] established DECC interface standards and policies.[SRD ID 44500] 1Req 87: Receive Suites shall be comprised of a receive terminal, cryptographic equipment (whenrequired), and Receive Broadcast Manager (RBM) equipment (Threshold).Req 1: Net Ready: 100% of all the specified Joint integrated architecture requirements designatedenterprise-level or critical activity interfaces; services; policy-enforcement controls; data-sharing,data availability, data correctness, data processing and information assurance accreditationrequirements in the Net-Centric Operations and Warfare Reference Model (NCOW-RM) plus GIG-Key Interface Profiles (KIPs) shall be satisfied (KPP – Block-3 Threshold), including all non-criticaland non- enterprise activities (Block-2 Objective, Block-3 Objective).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-223

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement4460044700448004490045000The SBM to DECC Facility interfaces shall be capable oftraversing the DECC firewalls for routing across the DISN tothe uplink facilities. [SRD ID 44600] 27The DISN to SBM DMZ interfaces shall accept various filesand streaming products from sources using standard internetprotocols that include but are not limited to EncapsulatedSecurity Payload (ESP), Secure Shell (SSH), Simple MailTransfer Protocol (SMTP), Simple Mail Transfer ProtocolSecure Sockets Layer (SMTP SSL)Domain Name Server(DNS), Hyper Text Transfer Protocol (HTTP), Hyper TextTransfer Protocol Secure (HTTPS), File Transfer Protocol(FTP), File Transfer Protocol over Secure Sockets Layer(FTPS), SSH File Transfer Protocol (SFTP), Message Hopper ,MSCHAT, Power Publisher, and Multicast. [SRD ID 44700] 4-1, 27The DISN to SBM DMZ interfaces shall allow ingest of sourceencrypted TS/SCI traffic via tunneled IP streams (KPP). [SRDID 44800] 4-1, 27The DISN to SBM DMZ interfaces shall allow configurationinputs and operations management using HTTPS with DODPKI certificates. [SRD ID 44900] 4-1, 164The SBM DMZ to SBM interfaces shall accept various filesand streaming products from the SBM DMZ using standardinternet protocols that include but not limited to EncapsulatedSecurity Payload (ESP), Secure Shell (SSH), Simple MailTransfer Protocol (SMTP), Simple Mail Transfer ProtocolSecure Sockets Layer (SMTP SSL) Domain Name Server(DNS), Hyper Text Transfer Protocol (HTTP), Hyper TextTransfer Protocol Secure (HTTPS), File Transfer Protocol(FTP), File Transfer Protocol over Secure Sockets Layer(FTPS), SSH File Transfer Protocol (SFTP), Message Hopper,MSCHAT, Power Publisher, TACACS, NTP, SNMP Traps,SYS Log, and Multicast. [SRD ID 45000] 4-1, 2730 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-224Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold).Req 4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold). Req 27: The SBM andTSBM shall provide standards-based interfaces that allow connections to be made to sources andTheater Information Managers via the DISN Internet Protocol based services (SIPRNet & NIPRNet)and the DISN ATM Service (DATMS). The TSBM shall provide the standards-based interfaces viaphysical and electrical connections that are consistent with the tactical sources to which they mustconnect. (Threshold).Req 4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold). Req 27: The SBM andTSBM shall provide standards-based interfaces that allow connections to be made to sources andTheater Information Managers via the DISN Internet Protocol based services (SIPRNet & NIPRNet)and the DISN ATM Service (DATMS). The TSBM shall provide the standards-based interfaces viaphysical and electrical connections that are consistent with the tactical sources to which they mustconnect. (Threshold).Req 4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold). Req 164: GBS Systemshall implement information assurance and necessary network security enhancements, including PKI(Block-3 Threshold, Block-2 Objective).Req 4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold). Req 27: The SBM andTSBM shall provide standards-based interfaces that allow connections to be made to sources andTheater Information Managers via the DISN Internet Protocol based services (SIPRNet & NIPRNet)and the DISN ATM Service (DATMS). The TSBM shall provide the standards-based interfaces viaphysical and electrical connections that are consistent with the tactical sources to which they mustconnect. (Threshold).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement45100452004530045400The SBM DMZ to SBM interfaces shall allow ingest of sourceencrypted TS/SCI traffic via tunneled IP streams (KPP). [SRDID 45100] 4, 4-1, 27The SBM DMZ to SBM interfaces shall allow configurationinputs, RBM feedback, and operations management usingHTTPS with DOD PKI certificates. [SRD ID 45200] 4-1, 27, 164The SBM DMZ to SBM interfaces shall use DISN connectivityand bandwidth to connect information sources, PIPs, Teleports,Primary and COOP SBMs, TIMs, Operations Mangers, andRBMs. [SRD ID 45300] 26-1, 26-7, 27The SBM DMZ to SBM interfaces shall provide the necessarytools to ingest and process analog videos from source inputs.[SRD ID 45400] 1-1, 2730 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-225Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold). Req4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold). Req 27: The SBM andTSBM shall provide standards-based interfaces that allow connections to be made to sources andTheater Information Managers via the DISN Internet Protocol based services (SIPRNet & NIPRNet)and the DISN ATM Service (DATMS). The TSBM shall provide the standards-based interfaces viaphysical and electrical connections that are consistent with the tactical sources to which they mustconnect. (Threshold).Req 4-1: The broadcast of compartmented or above US SECRET releasable information may useKEYMAT management and information-source encryption to restrict access. Compartmentedinformation providers (including Top Secret Collateral, TS-SCI, and Coalition or Allied and non-DoD releasable information) intending to use GBS must manage content, priorities, and providesource encryption of their information external to GBS broadcast centers, but shall use GBSprescribed and interoperable encryption and communications protocol standards which areintegrated with and tunneled through the broadcast (Block-2 Threshold). Req 27: The SBM andTSBM shall provide standards-based interfaces that allow connections to be made to sources andTheater Information Managers via the DISN Internet Protocol based services (SIPRNet & NIPRNet)and the DISN ATM Service (DATMS). The TSBM shall provide the standards-based interfaces viaphysical and electrical connections that are consistent with the tactical sources to which they mustconnect. (Threshold). Req 164: GBS System shall implement information assurance and necessarynetwork security enhancements, including PKI (Block-3 Threshold, Block-2 Objective).Req 26-1: Where a PIP is not collocated with an SBM, the PIP shall receive the broadcast streamthrough DISN connectivity (Threshold). Req 26-7: To support GBS restoration in the event ofcatastrophic PIP outage, Joint Forces Command, Joint Communications Support Element (JCSE)shall modify at least two satellite earth terminals assets to provide GBS broadcast relay. Eachterminal shall require modifications to include: a GBS prescribed Integrated Receiver Decoder, a250watt Ka-band HPA (frequencies consistent with GBS space segment transponders) and a DigitalVideo Broadcast Modem (Block-3 Threshold, Block-2 Objective). Req 27: The SBM and TSBMshall provide standards-based interfaces that allow connections to be made to sources and TheaterInformation Managers via the DISN Internet Protocol based services (SIPRNet & NIPRNet) and theDISN ATM Service (DATMS). The TSBM shall provide the standards-based interfaces via physicaland electrical connections that are consistent with the tactical sources to which they must connect.(Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 27: The SBM and TSBM shall provide standards-basedinterfaces that allow connections to be made to sources and Theater Information Managers via theDISN Internet Protocol based services (SIPRNet & NIPRNet) and the DISN ATM Service(DATMS). The TSBM shall provide the standards-based interfaces via physical and electricalconnections that are consistent with the tactical sources to which they must connect. (Threshold).

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement4600046100The SBM to Injection Terminal interfaces shall generate IPmulticast streams for each uplink modulator. [SRD ID 46000] 27, 34The SBM to Injection Terminal interfaces shall transport the IPmulticast streams generated at the SBM over the DISN togeographically dispersed uplink facilities. [SRD ID 46100] 2-1, 27Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 34: The SBM and TSBM shall be capable ofgenerating unique broadcast content for each transponder data stream (Block-2 Threshold).Req 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets. Req 27: TheSBM and TSBM shall provide standards-based interfaces that allow connections to be made tosources and Theater Information Managers via the DISN Internet Protocol based services (SIPRNet& NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide the standards-basedinterfaces via physical and electrical connections that are consistent with the tactical sources towhich they must connect. (Threshold).4620046300464004650047000The SBM shall ingest SMPTE-325M messages from eachinjection terminal’s JIPM Hubs to control dynamic bandwidthallocations. [SRD ID 46200] 2-1The SBM to RBM interfaces shall support the legacy GBSover-the-air protocols to ensure compatibility. [SRD ID 46300] 1-1, 27The BDA to GBS Operations Manager HCI interfaces shallprovide context-sensitive on-line help. [SRD ID 46400] 1-1, 27BDA to Regional Satellite Support Center (RSSC)/WidebandSATCOM Operations Center (WSOC) WGS Planning andControl System shall be a WGS authorized SAR/SAAmessage. [SRD ID 46500] 41The RBM to End User Interface shall allow the RBM to delivervarious files and streaming products to end users usingstandard internet protocols that include, but are not limited to:Hyper Text Transfer Protocol (HTTP), Hyper Text TransferProtocol Secure (HTTPS), File Transfer Protocol (FTP), FileTransfer Protocol over Secure Sockets Layer (FTPS), SSH FileTransfer Protocol (SFTP), Real-Time Transport Protocol(RTP), Internet Group Management Protocol (IGMP), SessionDescription Protocol (SDP), Trivial File Transfer Protocol(TFTP), and Multicast. [SRD ID 47000] 27, 91Req 2-1: The GBS System shall be capable of automatically reporting the status of Transmit Suitetransport elements (e.g. switches & routers) to the DISN Integrated Network Management System99% (Block-3 Threshold) and 99.9% (Block-3 Objective) of the time. GBS shall have an automatednetwork management capability to obtain status of networks and associated assets.Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 27: The SBM and TSBM shall provide standards-basedinterfaces that allow connections to be made to sources and Theater Information Managers via theDISN Internet Protocol based services (SIPRNet & NIPRNet) and the DISN ATM Service(DATMS). The TSBM shall provide the standards-based interfaces via physical and electricalconnections that are consistent with the tactical sources to which they must connect. (Threshold).Req 1-1: The GBS System is part of the GIG and shall meet GIG interoperability standards for theinterfaces, protocols, and equipment required to receive and disseminate video and data fromexisting systems (Threshold). Req 27: The SBM and TSBM shall provide standards-basedinterfaces that allow connections to be made to sources and Theater Information Managers via theDISN Internet Protocol based services (SIPRNet & NIPRNet) and the DISN ATM Service(DATMS). The TSBM shall provide the standards-based interfaces via physical and electricalconnections that are consistent with the tactical sources to which they must connect. (Threshold).Req 41: SBM shall have the ability to coordinate with the RSSC and WSOC for planning andscheduling and for payload configuration of power, bandwidth, and coverage parameters(Threshold).Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 91: Receive Suites shall be scaleable andconfigurable to satisfy a variety of user installations and broadcast receive requirements (Threshold).Scaleable and configurable configurations beyond basic receive suite configurations shall beseparately procured and accompanied with training and maintenance addendums to include at aminimum the following: Req 91-x.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-226

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement4710047200The RBM to End User Interface shall allow the End Useraccess to the RBM by using HTTPS. [SRD ID 47100] 27, 91The RBM to SBM interface shall allow RBM feedback acrossthe DISN using HTTPS with DOD PKI certificates. [SRD ID47200] 27, 91, 164Req 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 91: Receive Suites shall be scaleable andconfigurable to satisfy a variety of user installations and broadcast receive requirements (Threshold).Scaleable and configurable configurations beyond basic receive suite configurations shall beseparately procured and accompanied with training and maintenance addendums to include at aminimum the following: 91-xReq 27: The SBM and TSBM shall provide standards-based interfaces that allow connections to bemade to sources and Theater Information Managers via the DISN Internet Protocol based services(SIPRNet & NIPRNet) and the DISN ATM Service (DATMS). The TSBM shall provide thestandards-based interfaces via physical and electrical connections that are consistent with the tacticalsources to which they must connect. (Threshold). Req 91: Receive Suites shall be scaleable andconfigurable to satisfy a variety of user installations and broadcast receive requirements (Threshold).Scaleable and configurable configurations beyond basic receive suite configurations shall beseparately procured and accompanied with training and maintenance addendums to include at aminimum the following: Req 91-x. Req 164: GBS System shall implement information assuranceand necessary network security enhancements, including PKI (Block-3 Threshold, Block-2Objective).48000The GBS transport system shall provide capabilities that ensurethat information identified as priority is delivered ahead ofregular traffic 99% of the time. [SRD ID 48000] 1-3Req 1-3: Consistent with IPv6 QoS mechanism and current space segment coverage beams, GBSTransport systems shall provide QoS capabilities that ensure that information identified as priority isdelivered ahead of regular traffic 99% of the time (Block-3 Threshold) and 99.9% of the time(Block-3 Objective).48400Each LRU element of the GBS system shall include Built-In-Test (BIT) diagnostics that fault isolate using contractorsupplied test equipment, 95% of the time. [SRD ID 48400] 20Req 20: As an element of the GIG, the GBS System shall maintain and guarantee during transportthe integrity of file-based data that it stores and processes to enable user confidence; informationintegrity shall be 99.99% (Threshold) and 99.999% (Objective).48500The SBM Mean Time to Repair (unscheduled maintenance)shall be less than 90 minutes. [SRD ID 48500] 46Req 46: The SBM shall have an operational availability of 99.00 percent (Threshold) and 99.99percent (Objective) over a period of 480 hrs.48600SBM operator level maintenance shall be limited to basic care,cleaning, and replacement of expendables and LineReplaceable Units (LRUs). [SRD ID 48600] 46-1Req 46-1: SBM scheduled routine maintenance shall be performed without disruption to serviceoperations and not exceed one maintenance hour per 24-hour period (Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-227

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement48700SBM scheduled routine maintenance shall be performedwithout disruption to service operations. [SRD ID 48700] 46-1Req 46-1: SBM scheduled routine maintenance shall be performed without disruption to serviceoperations and not exceed one maintenance hour per 24-hour period (Threshold).48800SBM scheduled and routine maintenance time shall not exceedone maintenance hour per 24-hour period. [SRD ID 48800] 46-1Req 46-1: SBM scheduled routine maintenance shall be performed without disruption to serviceoperations and not exceed one maintenance hour per 24-hour period (Threshold).48900The GBS system shall allow cryptographic equipment to bemaintained and repaired in accordance with COMSECmaintenance policies and procedures. [SRD ID 48900] 23Req 23: GBS System shall provide the capability to key GBS specific cryptographic equipmentmanually (Threshold) and to rekey GBS specific cryptographic equipment through Over-the-AirRekey (OTAR) (Objective).50000The RBM Mean Time to Repair (unscheduled maintenance)shall be less than 90 minutes. [SRD ID 50000] 107Req 107: The MTTR for all receive suites, except SRS and SSRS, shall be 1.5 hours (unit level)and 1.5 hours (organizational level) (Threshold).50101The SBM shall maintain an operational availability of 99.0%over a period of 480 hours. [SRD ID 50101] 46Req 46: The SBM shall have an operational availability of 99.00 percent (Threshold) and 99.99percent (Objective) over a period of 480 hrs.501025020150202The SBM shall maintain an operational availability of 99.99%over a period of 480 hours. (Objective) [SRD ID 50102]. 46Fixed Sites and Equipment exposed directly to an externalenvironment shall operate in blowing sand, dust, and allprecipitation environments during 45 mph sustained winds,gusts to 60 mph in -40°F to 120°F air temperatures plus solarloading at all humidity levels. (Threshold) [SRD ID 50201]. 113Fixed Sites and Equipment exposed directly to an externalenvironment shall operate in blowing sand, dust, and allprecipitation environments during 45 mph sustained winds,gusts to 60 mph in -50°F to 150°F air temperatures plus solarloading at all humidity levels. [SRD ID 50202]. 113Req 46: The SBM shall have an operational availability of 99.00 percent (Threshold) and 99.99percent (Objective) over a period of 480 hrs.Req 113: The FGRS shall include an antenna capable of operating in blowing sand, dust andprecipitation environments during 45 mph (39 knots) sustained winds, 60 mph (52 knots) gusts in -25° F to 110° F (Block-1 Threshold) -40° F to 120° F (Block-2 Threshold) and -50° F to 150° F(Objective) air temperatures plus solar loading at all humidity levels (Threshold).Req 113: The FGRS shall include an antenna capable of operating in blowing sand, dust andprecipitation environments during 45 mph (39 knots) sustained winds, 60 mph (52 knots) gusts in -25° F to 110° F (Block-1 Threshold) -40° F to 120° F (Block-2 Threshold) and -50° F to 150° F(Objective) air temperatures plus solar loading at all humidity levels (Threshold).5040050700The broadcast segment shall be capable of operating at 120/220VAC at 60/50 Hz power. [SRD ID 50400] Derived Derived from US power standards .The GBS System design shall consider and accommodate thenine Human Systems Integration (HSI) domains (i.e.,The nine Human Systems Integration (HSI) domains (i.e., manpower, personnel, training, humanmanpower, personnel, training, human factors engineering,factors engineering, environment, safety, occupational health, personnel survivability, andenvironment, safety, occupational health, personnelhabitability) will be addressed and optimized as applicable within the structure of the GBS design tosurvivability, and habitability). [SRD ID 50700] Section 5.5 achieve total system performance and reduce life-cycle costs.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-228

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement5071051000Each HSI domain shall be addressed and optimized, asapplicable, within the structure of the GBS design to achievetotal system performance and reduce life-cycle costs. [SRD ID50710]. Section 5.5GBS System Human Factors Engineering shall comply withHuman Systems Integration requirements set forth within DoDDirective 5000.1 and DoDI 5000.2, Human EngineeringProgram Process and Procedures, MIL-HDBK-46855A, andHuman Engineering Design Criteria, MIL-STD-1472F. [SRDID 51000] Section 5.5.1The nine Human Systems Integration (HSI) domains (i.e., manpower, personnel, training, humanfactors engineering, environment, safety, occupational health, personnel survivability, andhabitability) will be addressed and optimized as applicable within the structure of the GBS design toachieve total system performance and reduce life-cycle costs.Interface characteristics should be chosen to maximize human productivity and performance asverified by iterative testing. Human Factors Engineering should comply with Human SystemsIntegration requirements set forth within DoD Directive 500.1 and DoDI 5000.2, HumanEngineering Program Process and Procedures, MIL-HDBK-46855A, and Human EngineeringDesign Criteria, MIL-STD-1472F.5150051525515505160051700The GBS System design and construction shall not use Class Iand Class II ozone depleting substances. [SRD ID 51500] Section 5.5.2The GBS System design and construction shall be compliantwith the GBS Safety Program requirements specified in theGBS System Safety Management Plan (SSMP) and GBSProgrammatic Environmental, Safety, and Health Evaluation(PESHE). [SRD ID 51525] Section 5.5.2The GBS System design shall minimize use of other hazardousmaterials in GBS components, manufacturing materials andprocesses, support equipment, and disposal operations. [SRDID 51550] Section 5.5.2The GBS System shall be HAZMAT complaint in accordancewith DoD Directive 5000.1 and DoDI 5000.2. [SRD ID51600] Section 5.5.2The GBS System shall not expose operators or maintainers tohealth and safety hazards as defined in the GBS HealthHazards Assessment. [SRD ID 51700] Section 5.5.2The system and system support shall not require the use of any Class I or II ozone depletingsubstances for operations and maintenance.The system and system support shall not require the use of any Class I or II ozone depletingsubstances for operations and maintenance.Operations, maintenance, support, and disposal activities require a system with minimal hazardousmaterials (HAZMAT), health hazards, and safety risks. DoD Directive 5000.1 and DoDI 5000.2provide HAZMAT requirements.The GBS should be compared to representative legacy or similar system to determine any knownenvironment, health, or safety hazards that need to be addressed during design and development ofthis system. The probability and severity of Safety risks (accidents or failures) should be identifiedand reduced to acceptable limits. Safety and Health design, cost, and risk drivers are important to theuser community. Operations, maintenance, support, and disposal activities require a system withminimal hazardous materials (HAZMAT), health hazards, and safety risks. DoD Directive 5000.1and DoDI 5000.2 provide HAZMAT requirements.GBS must conform to applicable human engineering design criteria as described in Joint TechnicalArchitecture - Air Force, Version 2.4, 26 of May 2000. The Materiel Developer should arrange for aHealth Hazard Assessment (HHA) on GBS. The GBS program should include system and personnelsafety programs. The system safety program should be in compliance with the latest DoD policies oran equivalent commercial standard. Safety critical issues should be addressed and documentedduring system design and deployment.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-229

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement51800519005200052100Applicable ESOH requirements shall be integrated into theGBS System Engineering process, as defined by NSSAP 03-01and NEPA/EPA regulations. [SRD ID 51800] Section 5.5.2The GBS System shall be compliant, certified, and accreditedin accordance with the DoDI 8510.bb, DIACAP Instructions.[SRD ID 51900]The GBS System, at a minimum, shall meet all the IA controlsfor a Mission Assurance Category II classified system per DoDInstruction 8500.2. [SRD ID 52000]The GBS System shall use DoD issued PKI certificates tosupport authentication, access control, confidentiality, dataintegrity, and non-repudiation. [SRD ID 52100] 46, 7, 8,Section 5.3.3.4, 6, 7, 8, 161,162, 164The GBS should be compared to representative legacy or similar system to determine any knownenvironment, health, or safety hazards that need to be addressed during design and development ofthis system. The probability and severity of Safety risks (accidents or failures) should be identifiedand reduced to acceptable limits. Safety and Health design, cost, and risk drivers are important to theuser community. Operations, maintenance, support, and disposal activities require a system withminimal hazardous materials (HAZMAT), health hazards, and safety risks. DoD Directive 5000.1and DoDI 5000.2 provide HAZMAT requirements.Req 6: The GBS shall meet Designated Accreditation Authority (DAA) accreditation requirements,including certification and accreditation IAW DITSCAP process (e.g., CJCSI 6510.01C, DoDI5200.40) (Threshold). Req 7: GBS shall comply with the requirements levied in Assistant Secretaryof Defense for Command, Control, Communications and Intelligence (ASD (C3I)) letter “Secret andBelow Interoperability” (SABI), dated 20 March 1997 and DCID 6/3 Protecting SCI withinInformation Systems (Threshold). Req 8: With the exception of unclassified video (limited topublic domain non-DoD derived and non-national security related information used in fulfillment ofmilitary or intelligence missions), all information shall be protected from exploitation duringtransmission over satellites (Block-2 Threshold).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold). Req6: The GBS shall meet Designated Accreditation Authority (DAA) accreditation requirements,including certification and accreditation IAW DITSCAP process (e.g., CJCSI 6510.01C, DoDI5200.40) (Threshold). Req 7: GBS shall comply with the requirements levied in Assistant Secretaryof Defense for Command, Control, Communications and Intelligence (ASD (C3I)) letter “Secret andBelow Interoperability” (SABI), dated 20 March 1997 and DCID 6/3 Protecting SCI withinInformation Systems (Threshold). Req 8: With the exception of unclassified video (limited topublic domain non-DoD derived and non-national security related information used in fulfillment ofmilitary or intelligence missions), all information shall be protected from exploitation duringtransmission over satellites (Block-2 Threshold). Req 161: BMS shall permit compartment andabove US Secret information providers to control the broadcast stream based on user pull across SCInetworks (Block-3 Threshold). Req 162: The BMS shall permit automatic machine-to-machinepasswords and other controls to access web-based content for retrieval across the DISN andbroadcast (Block-3 Threshold). Req 164: GBS System shall implement information assurance andnecessary network security enhancements, including PKI (Block-3 Threshold, Block-2 Objective).Req 4: The GBS System shall support the passing of information ranging in classifications fromUnclassified up to and including Top Secret and Sensitive Compartmented Information (TS & SCI)(KPP –Threshold). The system shall not compromise information need-to-know access (medical,personnel, mission sensitive information, including access to Sensitive But Unclassified (SBU),Allied, Coalition, non-DoD, or other compartmented releasable products) (KPP – Threshold).52400The GBS System shall use existing logistics supportinfrastructures described in the Joint Integrated LogisticsSupport Plan. [SRD ID 52400] Section 5.0 The GBS should take maximum advantage of existing logistics support infrastructures.52500Requirements for maintenance support equipment shall be keptat a minimum. [SRD ID 52500] Section 5.0 The GBS should take maximum advantage of existing logistics support infrastructures.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-230

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement5260052700If support equipment is required, the GBS System supportequipment, at a minimum, shall be comprised of 90 percentCOTS support equipment. [SRD ID 52600] Section 5.1The GBS system shall not require special purpose supportequipment, special purpose electronic test equipment, orspecial purpose tools. [SRD ID 52700]Section 5.1,5.2A direct Line Replaceable Unit (LRU) exchange capability shall be developed for GBS receivesuites. The materiel developer shall perform logistic analysis as an integral part of the systemsengineering process, and should develop logistics support concepts that provide for cost effectivetotal life-cycle logistics support. Operators should provide basic care, cleaning, and replacement ofexpendables such as fuses and filters. Lowest level repair shall be accomplished at theorganizational or direct support level through the use of LRUs. All other maintenance shall beaccomplished at the depot level. For Navy, intermediate level maintenance involvement should belimited to the installation and removal of above deck equipment. Vehicle and generator maintenanceshall be accomplished in accordance with existing maintenance procedures. Cryptographicequipment shall be repaired in accordance with Communications Security (COMSEC) maintenancepolicies and procedures.A direct Line Replaceable Unit (LRU) exchange capability shall be developed for GBS receivesuites. The materiel developer shall perform logistic analysis as an integral part of the systemsengineering process, and should develop logistics support concepts that provide for cost effectivetotal life-cycle logistics support. Operators should provide basic care, cleaning, and replacement ofexpendables such as fuses and filters. Lowest level repair shall be accomplished at theorganizational or direct support level through the use of LRUs. All other maintenance shall beaccomplished at the depot level. For Navy, intermediate level maintenance involvement should belimited to the installation and removal of above deck equipment. Vehicle and generator maintenanceshall be accomplished in accordance with existing maintenance procedures. Cryptographicequipment shall be repaired in accordance with Communications Security (COMSEC) maintenancepolicies and procedures.5300053100The RBM Software shall operate in an unattended mode forsteady state broadscasts. [SRD ID 53000] 105Personnel skill and skill levels required for operating andmaintaining the RBM shall not exceed levels defined in Table5 of this SRD. [SRD ID 53100] Section 5.5.3Req 105: Receive Terminals shall be capable of operating in an unattended mode during steadystate broadcast data rate operation. (Block-1 Threshold) Operate in an unattended mode after initialsetup (Block-2 Threshold).Initial operations and maintenance (O&M) training on the Joint Program Office (JPO) fundedreceive suites should be provided by the installation team. Since SBMs will be contractor personneland PIPs will be contractor operated and maintained, there are no initial training requirements.Provisions shall be available for training should it be desired to transition from contractor togovernment operation and maintenance at a later date. The Contractor shall provide TIP trainingupon equipment delivery. A Joint Training Plan will be developed to define common and Servicespecific training requirements. Initial factory training shall be provided to Service selected O&Minstructors (train the trainers) on receive suites and TIPs. Follow-on training should be providedthrough Service specific formal training channels. Service unique training requirements should beService funded. Maximum advantage should be taken of commercially available embedded training.5320153202GBS System Training, where possible, shall includecommercially available Embedded Training (ET). [SRD ID53201] Section 5.5.3 Maximum advantage should be taken of commercially available embedded training.GBS System Training shall not require separate trainingdevices or simulators to support the development, operations,and maintenance of GBS. [SRD ID 53202] Section 5.5.330 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-231Initial operations and maintenance (O&M) training on the Joint Program Office (JPO) fundedreceive suites should be provided by the installation team. Since SBMs will be contractor personneland PIPs will be contractor operated and maintained, there are no initial training requirements.Provisions shall be available for training should it be desired to transition from contractor togovernment operation and maintenance at a later date. The Contractor shall provide TIP trainingupon equipment delivery. A Joint Training Plan will be developed to define common and Servicespecific training requirements. Initial factory training shall be provided to Service selected O&Minstructors (train the trainers) on receive suites and TIPs. Follow-on training should be providedthrough Service specific formal training channels. Service unique training requirements should beService funded. Maximum advantage should be taken of commercially available embedded training.

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement5320353204532055320760000GBS System Training shall be in accordance with servicepolicies and procedures. [SRD ID 53203] Section 5.5.3GBS System Training shall include electronic form (andhardcopy form where required) of the operator and maintainertraining material. [SRD ID 53204] Section 5.5.3GBS System Training shall include electronic form (andhardcopy form where required) of the operations andmaintenance technical documentation. [SRD ID 53205] Section 5.5.3GBS System Training shall be provided for the elements of thebroadcast segment at the time of transition to governmentoperations. [SRD ID 53207] Section 5.5.3The Transmit Receive Suite (TRS) shall be composed of areceive terminal and RBM to provide RCS capability, tosupport “user pull” requests, via connectivity through aTeleport and DISN core . [SRD ID 60000]13, 87, 97,15930 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-232Initial operations and maintenance (O&M) training on the Joint Program Office (JPO) fundedreceive suites should be provided by the installation team. Since SBMs will be contractor personneland PIPs will be contractor operated and maintained, there are no initial training requirements.Provisions shall be available for training should it be desired to transition from contractor togovernment operation and maintenance at a later date. The Contractor shall provide TIP trainingupon equipment delivery. A Joint Training Plan will be developed to define common and Servicespecific training requirements. Initial factory training shall be provided to Service selected O&Minstructors (train the trainers) on receive suites and TIPs. Follow-on training should be providedthrough Service specific formal training channels. Service unique training requirements should beService funded. Maximum advantage should be taken of commercially available embedded training.Initial operations and maintenance (O&M) training on the Joint Program Office (JPO) fundedreceive suites should be provided by the installation team. Since SBMs will be contractor personneland PIPs will be contractor operated and maintained, there are no initial training requirements.Provisions shall be available for training should it be desired to transition from contractor togovernment operation and maintenance at a later date. The Contractor shall provide TIP trainingupon equipment delivery. A Joint Training Plan will be developed to define common and Servicespecific training requirements. Initial factory training shall be provided to Service selected O&Minstructors (train the trainers) on receive suites and TIPs. Follow-on training should be providedthrough Service specific formal training channels. Service unique training requirements should beService funded. Maximum advantage should be taken of commercially available embedded training.Initial operations and maintenance (O&M) training on the Joint Program Office (JPO) fundedreceive suites should be provided by the installation team. Since SBMs will be contractor personneland PIPs will be contractor operated and maintained, there are no initial training requirements.Provisions shall be available for training should it be desired to transition from contractor togovernment operation and maintenance at a later date. The Contractor shall provide TIP trainingupon equipment delivery. A Joint Training Plan will be developed to define common and Servicespecific training requirements. Initial factory training shall be provided to Service selected O&Minstructors (train the trainers) on receive suites and TIPs. Follow-on training should be providedthrough Service specific formal training channels. Service unique training requirements should beService funded. Maximum advantage should be taken of commercially available embedded training.Initial operations and maintenance (O&M) training on the Joint Program Office (JPO) fundedreceive suites should be provided by the installation team. Since SBMs will be contractor personneland PIPs will be contractor operated and maintained, there are no initial training requirements.Provisions shall be available for training should it be desired to transition from contractor togovernment operation and maintenance at a later date. The Contractor shall provide TIP trainingupon equipment delivery. A Joint Training Plan will be developed to define common and Servicespecific training requirements. Initial factory training shall be provided to Service selected O&Minstructors (train the trainers) on receive suites and TIPs. Follow-on training should be providedthrough Service specific formal training channels. Service unique training requirements should beService funded. Maximum advantage should be taken of commercially available embedded training.Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting “user pull” data to GBSspace segments with a Return Channel Satellite (RCS) having connectivity to DISN (Block-3Threshold). Req 87: Receive Suites shall be comprised of a receive terminal, cryptographicequipment (when required), and Receive Broadcast Manager (RBM) equipment (Threshold). Req97: The TRS equipped receive suite shall be capable of a shared RCS user pull capability withcapacity at a data rate supporting 100 (TBR) concurrently operating receive suites per satellitecoverage area with a duty cycle of 12% (TBR) average message of 200 Bytes (TBR) each andresponse time of 500 msec (TBR) to the WGS space segment (Block-3 Threshold). Req 159: ATRS shall be comprised of any GBS Receive Suite suitably modified to include the necessarytransmit capability to support GBS User Pull using GBS RCS reachback connectivity directly

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirementthrough a PIP to an SBM, and then to the DISN. For a given receive suite this shall include (Block-3Threshold):(1) Terminal: either a Transmit-capable Receive Terminal (TRT) or a separate common transmitterminal with a suitable interface to receive the return channel signal from the RBM and transmit thesignal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe return channel signal.60100The 2-way capability of the GBS Transmit Receive Suites shallbe supported by the DECC architecture . [SRD ID 60100] 13, 159Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting “user pull” data to GBSspace segments with a Return Channel Satellite (RCS) having connectivity to DISN (Block-3Threshold). Req 159: A TRS shall be comprised of any GBS Receive Suite suitably modified toinclude the necessary transmit capability to support GBS User Pull using GBS RCS reachbackconnectivity directly through a PIP to an SBM, and then to the DISN. For a given receive suite thisshall include (Block-3 Threshold):(1) Terminal: either a Transmit-capable Receive Terminal (TRT) or a separate common transmitterminal with a suitable interface to receive the return channel signal from the RBM and transmit thesignal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe return channel signal.6020160202605006055061000The SBM software shall support the GBS TRS capability oftransmitting and receiving 2-way data between the RBM, viathe GBS space segments with an RCS having connectivity tothe DISN . [SRD ID 60201] 13The RBM software shall support the GBS TRS capability oftransmitting and receiving 2-way data between the SBM, viathe GBS space segments with an RCS having connectivity tothe DISN . [SRD ID 60202] 13The GBS system shall include an additional IA approved SCIbroadcast enclave, designated for SCI content only, with thesame capabilities defined for the ROKUS enclave. [SRD ID60500] 98, 161The GBS systems shall include an additional IA approvedCoalition broadcast enclave, designated for Coalition contentonly, with the same capabilities defined for the ROKUSenclave. (Objective) [SRD ID 60550] 98, 161The Ground Mobile Receive Suites (GMRS) shall incorporateall common receive suite requirements, such as being capableof receiving and processing the GBS downlink while on themove, requiring no special tools/processes/skills to move fromone tactical vehicle to another, and being capable of survivingthe rigors of tactical cross-country vehicular travel. (Objective)[SRD ID 61000]123, 123-1,123-2, 123-3Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting “user pull” data to GBSspace segments with a Return Channel Satellite (RCS) having connectivity to DISN (Block-3Threshold).Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting “user pull” data to GBSspace segments with a Return Channel Satellite (RCS) having connectivity to DISN (Block-3Threshold).Req 98: In order for receive suites to support either coalition, allied or Top Secret compartmentedsecurity enclave(s), separate add-on configuration or separate transit case shall be available tosupport each additional security enclave. A minimum of two additional add-on security enclavesshall be accommodated (Block-2 Threshold). Req 161: BMS shall permit compartment and aboveUS Secret information providers to control the broadcast stream based on user pull across SCInetworks (Block-3 Threshold).Req 98: In order for receive suites to support either coalition, allied or Top Secret compartmentedsecurity enclave(s), separate add-on configuration or separate transit case shall be available tosupport each additional security enclave. A minimum of two additional add-on security enclavesshall be accommodated (Block-2 Threshold). Req 161: BMS shall permit compartment and aboveUS Secret information providers to control the broadcast stream based on user pull across SCInetworks (Block-3 Threshold).Req 123: The GMRS should incorporate all common receive suite requirements (Block-3Threshold). Req 123-1: The GMRS shall be capable of receiving and processing the GBS downlinkwhile on the move (Block-3 Threshold). Req 123-2: The GMRS shall require no special tools,processes or skills to move from one tactical vehicle to another (Block-3 Threshold). Req 123-3:The GMRS must be capable of surviving the rigors of tactical cross-country vehicular travel. TheReceive Terminal must be low profile and designed to withstand the rigors and external forces of anexternal vehicular mounting during travel (Block-3 Threshold).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-233

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement61101The Ground Mobile Receive Suite shall be integrated, tested,and certified with the JIPM (one-way) and GBS RBMsoftware. (Objective) [SRD ID 61101] 123Req 123:Threshold).The GMRS should incorporate all common receive suite requirements (Block-36110261500616016160261701The Ground Mobile Receive Suite shall be integrated, tested,and certified with the JIPM (two-way) and GBS RBMsoftware. (Objective) [SRD ID 61102] 123A Broadcast Receive Suite – Terrestrial (BRS-T) shall becomprised of any GBS Receive Suite suitably modified toinclude the necessary transmit capability to support a wirelessterrestrial network extension of the broadcast to twenty or morenearby (within 5-miles distance line-of-sight) locations. [SRDID 61500] 160The wireless terrestrial network extension shall meet allrequired accreditations and certifications required to beimplemented as part of the GBS system . [SRD ID 61601] 160The wireless terrestrial network extension shall have 2-waycapability to, at a minimum, support “user pull” requests. [SRDID 61602] 12, 13, 160The wireless extension kit shall provide a web-basedmechanism that allows users to utilize system functionality viaa lightweight web browser application operating on handhelddevices connected to the wireless terrestrial extension network.[SRD ID 61701] 13, 160Req 123: The GMRS should incorporate all common receive suite requirements (Block-3Threshold).Req 160: A BRS-T shall be comprised of any GBS Receive Suite suitably modified to include thenecessary transmit capability to support a wireless terrestrial network extension of the broadcast totwenty or more nearby (greater than 5-miles distance line-of-sight) locations. For a given receivesuite this should include (Block-3 Threshold):(1) Terminal: a separate transmit terminal with a suitable interface to receive the broadcast repeatsignal from the RBM and transmit the signal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe broadcast extension signal.Req 160: A BRS-T shall be comprised of any GBS Receive Suite suitably modified to include thenecessary transmit capability to support a wireless terrestrial network extension of the broadcast totwenty or more nearby (greater than 5-miles distance line-of-sight) locations. For a given receivesuite this should include (Block-3 Threshold):(1) Terminal: a separate transmit terminal with a suitable interface to receive the broadcast repeatsignal from the RBM and transmit the signal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe broadcast extension signal.Req 12: The GBS system shall provide, through automated tools, the capability to fulfill “user pull”requests from authorized users and shall provide the means for users to identify specific ad-hocinformation needs. User pull requests shall be fulfilled on the broadcast through current or held forfuture broadcast coverage areas. “User pull” requests shall be capable of using receive suite attachednetwork connectivity or TRS RCS connectivity for automated information retrieval and broadcast(Block-2 Threshold). Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting“user pull” data to GBS space segments with a Return Channel Satellite (RCS) having connectivityto DISN (Block-3 Threshold). Req 160: A BRS-T shall be comprised of any GBS Receive Suitesuitably modified to include the necessary transmit capability to support a wireless terrestrialnetwork extension of the broadcast to twenty or more nearby (greater than 5-miles distance line-ofsight)locations. For a given receive suite this should include (Block-3 Threshold):(1) Terminal: a separate transmit terminal with a suitable interface to receive the broadcast repeatsignal from the RBM and transmit the signal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe broadcast extension signal.Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting “user pull” data to GBSspace segments with a Return Channel Satellite (RCS) having connectivity to DISN (Block-3Threshold). Req 160: A BRS-T shall be comprised of any GBS Receive Suite suitably modified toinclude the necessary transmit capability to support a wireless terrestrial network extension of thebroadcast to twenty or more nearby (greater than 5-miles distance line-of-sight) locations. For agiven receive suite this should include (Block-3 Threshold):(1) Terminal: a separate transmit terminal with a suitable interface to receive the broadcast repeatsignal from the RBM and transmit the signal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe broadcast extension signal.30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-234

Global Broadcast Service (GBS)Volume VI – Model Contract – Attachment 3SRD ID SRD Requirement ORD Req # ORD Requirement617026210062101621026220062201622026250162502The wireless extension kit shall provide content managementand filtering capabilities to support transmit and receivestreams over the wireless terrestrial extension network, whichoperates at lower data rates than the GBS Broadcast streams.[SRD ID 61702] 13, 160The SBM shall provide advanced asymmetric networking,implementing content caching for subsequent broadcast.(Objective) [SRD ID 62100] 166The SBM shall provide advanced information and contentmanagement, including detailed/indexed content searchcapability. (Objective) [SRD ID 62101] 166The detailed/indexed content search capability shall besupported by a single server, per enclave. (Objective) [SRD ID62102] 166The SBM shall provide advanced information and contentmanagement, including video caching capabilities that are notbacked-up at an alternate site or on permanent media.(Objective) [SRD ID 62200] 166Video caching shall be supported by a single server, perenclave. (Objective) [SRD ID 62201] 166Video caching shall provide 8.1 Terabytes of capacity.(Objective) [SRD ID 62202] 166The SBM software shall respond to information provider orInformation Dissemination Management (and successorprograms, to the extent implemented in Block-2) requests forstatistics on the broadcast of individual products, or groups ofproducts, by source over configurable time intervals. [SRD ID62501] 40-2, 40-3The SBM software shall respond to information provider orInformation Dissemination Management (and successorprograms, to the extent implemented in Block-2) requests forstatistics on the reception of individual products, or groups ofproducts, by receive suites over configurable time intervals.[SRD ID 62502] 40-2, 40-3Req 13: A Transmit-Receive Suite (TRS) shall be capable of transmitting “user pull” data to GBSspace segments with a Return Channel Satellite (RCS) having connectivity to DISN (Block-3Threshold). Req 160: A BRS-T shall be comprised of any GBS Receive Suite suitably modified toinclude the necessary transmit capability to support a wireless terrestrial network extension of thebroadcast to twenty or more nearby (greater than 5-miles distance line-of-sight) locations. For agiven receive suite this should include (Block-3 Threshold):(1) Terminal: a separate transmit terminal with a suitable interface to receive the broadcast repeatsignal from the RBM and transmit the signal with satisfactory performance; and(2) RBM: any RBM suitably modified to include the necessary software and hardware to generatethe broadcast extension signal.Req 166: SBM and TSBM shall provide advanced asymmetric networking implementing SBMcontent caching for subsequent broadcast (Block-3 Threshold, Block-2 Objective).Req 166: SBM and TSBM shall provide advanced asymmetric networking implementing SBMcontent caching for subsequent broadcast (Block-3 Threshold, Block-2 Objective).Req 166: SBM and TSBM shall provide advanced asymmetric networking implementing SBMcontent caching for subsequent broadcast (Block-3 Threshold, Block-2 Objective).Req 166: SBM and TSBM shall provide advanced asymmetric networking implementing SBMcontent caching for subsequent broadcast (Block-3 Threshold, Block-2 Objective).Req 166: SBM and TSBM shall provide advanced asymmetric networking implementing SBMcontent caching for subsequent broadcast (Block-3 Threshold, Block-2 Objective).Req 166: SBM and TSBM shall provide advanced asymmetric networking implementing SBMcontent caching for subsequent broadcast (Block-3 Threshold, Block-2 Objective).Req 40-2: The SBM and TSBM shall respond to information provider or IDM request for status onthe broadcast of individual products (Block-3 Threshold, Block-2 Objective) and on the receivesuite product receipt status (Block-3 Objective). Req 40-3: The SBM and TSBM shall generatebroadcast and receive efficiency metrics to assist TIM and other operational managers withadjustments to broadcast priorities or processes to improve broadcast efficiencies in order toimprove satisfaction of warfighter smart push and user pull product delivery, beam pointingplanning, and sharing of bandwidth between media type, security classifications, users and products(Block-3 Threshold, Block-2 Objective).Req 40-2: The SBM and TSBM shall respond to information provider or IDM request for status onthe broadcast of individual products (Block-3 Threshold, Block-2 Objective) and on the receivesuite product receipt status (Block-3 Objective). Req 40-3: The SBM and TSBM shall generatebroadcast and receive efficiency metrics to assist TIM and other operational managers withadjustments to broadcast priorities or processes to improve broadcast efficiencies in order toimprove satisfaction of warfighter smart push and user pull product delivery, beam pointingplanning, and sharing of bandwidth between media type, security classifications, users and products(Block-3 Threshold, Block-2 Objective).30 March 2009 • Contract Number: FA8726-09-C-0006Use or disclosure of data contained on this sheet is subject to the restriction on the title page of this proposalVolume VI-5.0-235