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

More documents

Recommendations

Info

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
Page 2 and 3:
Global Broadcast Service (GBS)Volum
Page 4 and 5:
Page 6 and 7:
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17: Global Broadcast Service (GBS)Volum
Page 54 and 55: DemonstrationTestAnalysisExaminatio
Page 116:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?