COMMUNICATIONS REQUIREMENTS. 9.1 The Recipient will comply with all communication requirements outlined in Schedule E.
COMMUNICATIONS REQUIREMENTS. The following guidelines describe the co-branding requirements. Essentially, we would like you to provide guidance on various marketing and promotional activities that your organization may implement after receiving your UWBA grant. Grant-Related Communications We ask that you include United Way Bay Area’s name on all printed or electronic communications related to the grant project during the grant cycle. These communications may include: website content, advertising, newsletters, fliers, event invitations, brochures, informational hand-outs, signs, posters, banners, press releases, and promotional giveaways. We also request that you mention UWBA’s partnership when making presentations related to the funded program. When appropriate, include the UWBA logo when referencing us in your communication materials and follow the “UWBA Brand Usage Guidelines,” both available: xxxxx://xxxx.xxx/campaign-resources/. UWBA’s marketing department is available to help if needed at xxxxxxxxx@xxxx.xxx.
COMMUNICATIONS REQUIREMENTS. 2Bridge's support obligations hereunder --------------------------- are contingent upon Subscriber maintaining access to the Internet ("Internet Access") meeting the minimum specifications set forth in Schedule A under "Internet Access Specifications". Acquiring, installing, maintaining and operating the Internet Access is solely the Subscriber's responsibility.
COMMUNICATIONS REQUIREMENTS. The Host Station shall (1) facilitate the provision of a voice (telephone) link from the Host Station Operations room to the IOC/SCC Washington DC. This telephone link may be multiplexed with the data communications link. There shall (2) be a redundant telephone link as well, which could be a direct-dial number through the public network. The Host Station shall (3) provide facsimile facilities in the Host Stations operations room for communication with Intelsat. Use of an existing facsimile machine with international direct-dialing capability is acceptable. The Host Station will facilitate availability of electronic mail through the standard Intelsat Administrative Reporting System to Contractor operations personnel at the Host Station operations room, and in the office space with the ability to attach files and transmit and receive mail via the Internet to Intelsat Headquarters. This is the preferred mode of communication between Intelsat and Contractor personnel during normal operations. Until the Administrative Reporting System in on place normal telephone dial–up access for electronic mail will be required.
COMMUNICATIONS REQUIREMENTS. Each emergency ambulance operating within the County must be equipped with appropriate emergency communications and alerting devices as specified by COUNTY. The standard emergency ambulance vehicle should include the ability to communicate at all times and locations with BOEC on approved 000 XXx talk groups and the ability to communicate with the Medical Resource Hospital, other hospitals, fire responders and other public safety agencies. Each ambulance must be equipped with two (2) 800 MHz radios, a Mobile Data Terminal (MDT) and AVL, and a back-up VHF radio, all meeting COUNTY specifications. PROVIDER will be responsible for contracting with the City of Portland for the maintenance of all radio equipment, except VHF radios and cellular phones. The PROVIDER must pay an access fee for the communication system to the City of Portland. The access fees are established by the City of Portland and revised annually.
COMMUNICATIONS REQUIREMENTS. The following guidelines describe the co-branding requirements. Essentially, we would like you to provide guidance on various marketing and promotional activities that your organization may implement after receiving your UWBA grant.
COMMUNICATIONS REQUIREMENTS a. N-TFS Server Requirements Access to port 9002 (both incoming and outgoing traffic) for PPC (Product Preparation Capability). The N-TFS Server receives Weather Forecasts, Warnings, Watches and Advisory messages from an Operational Weather Squadron (OWS) using the proprietary N-TFS PPC protocol (uses TCP/IP). The N-TFS Server requires true IP addresses to be passed from one system to the other. If required this transfer can be passed through a base router at the CWT base perimeter provided the N-TFS server receives the same I.P. address each time from the router. If a router is required this process will require close coordination with the local Base Network Control Center (BNCC). The N-TFS Server can support several simultaneous PPC sessions. Access to ports 20 and 21 for FTP (File Transfer Protocol). The N-TFS uses FTP for 2-way transfer of weather data products between OWSs, and Combat Weather Teams. Again, if required this transfer can be passed through a base router. The N-TFS server can support several simultaneous FTP sessions. Access to HTTP ports (80 or 82 as an example). The OWS N-TFS will use this capability primarily in a back-up role should PPC communication fail. The OWS will log into the CWT server (from a client) and issue the Forecast, Weather Warning, Watch or Advisory. Concurrently, the CWT may use this capability to log into the OWS N-TFS server to issue weather observations and retrieve operational data should their N-TFS server fail. Again, if required this transfer can be passed through a base proxy server or router Access to port 443. The N-TFS can use Hypertext Transfer Protocol over Secure Socket Layer (HTTPS) between the OWSs and base/post N-TFS servers in the same manner as HTTP once the necessary PKI certificates have been obtained. Access to port 22. This is needed to allow the prime contractor (General Dynamics) and the AFWA Help Desk access to the N-TFS server for performing remote diagnostic and maintenance services. Secure Shell (SSH) is the protocol used for this activity.
COMMUNICATIONS REQUIREMENTS
