DEPARTMENT OF VETERANS AFFAIRS



019050Department of Veterans AffairsOFFICE OF INFORMATION AND TECHNOLOGYService Delivery and EngineeringRequirements Specifications DocumentSatellite CommunicationsVersion 4.1July 26, 2012Revision HistoryDateReason for ChangesVersionAuthor4/15/11Initial Draft1.0RMP and JW5/27/11Final revision; updated sections for all stakeholders based on feedback received2.0RMP and JW4/2/12Added and updated THE DEPARTMENT OF VETERANS AFFAIRS VA Learning University (VALU) and Employee Education System (EES) Summary, objective and requirements.Added and Defined Class of Services Requirements 3.0TWY and RDA5/2/12Added section 2.1.6.,2.1.7, 2.1.8, 2.1.9Added Section 1.5 VAH IPT General Business Requirements4.0TWY and RDA7/26/12Clarified terminal size and ease of use requirements4.1RMPTable of Contents TOC \o "1-3" \h \z \u 1Introduction PAGEREF _Toc323742349 \h 11.1Purpose PAGEREF _Toc323742350 \h 11.2Scope PAGEREF _Toc323742351 \h 11.3Acronyms and Definitions PAGEREF _Toc323742352 \h 21.3.1Acronyms PAGEREF _Toc323742353 \h 21.3.2Definitions PAGEREF _Toc323742354 \h 51.4References PAGEREF _Toc323742355 \h 51.5Veterans Health Administration IPT General Business Requirements PAGEREF _Toc323742356 \h 52Requirements by Business Unit PAGEREF _Toc323742357 \h 72.1Veterans Health Administration PAGEREF _Toc323742358 \h 72.1.1Mobile Pharmacy PAGEREF _Toc323742359 \h 72.1.2Mobile Vet Centers PAGEREF _Toc323742360 \h 82.1.3Veterans Health Administration Office of Emergency Management (VHA OEM) PAGEREF _Toc323742361 \h 92.1.410N (Emergency Portion of VHA) PAGEREF _Toc323742362 \h 102.1.5Mobile Medical Units PAGEREF _Toc323742363 \h 112.1.6Medical Center PAGEREF _Toc323742364 \h 122.1.7Community-Based Outpatient Clinic (CBOC) PAGEREF _Toc323742365 \h 122.1.8Network Office PAGEREF _Toc323742366 \h 132.1.9Veterans Integrated Service Network (VISN) PAGEREF _Toc323742367 \h 132.2Office of Operations, Security and Preparedness Requirements PAGEREF _Toc323742368 \h 142.2.1Geospatial Intelligence PAGEREF _Toc323742369 \h 142.2.2Office of Security and Law Enforcement PAGEREF _Toc323742370 \h 152.2.3Continuity of Operations / Continuity of Government PAGEREF _Toc323742371 \h 152.3Veterans Benefits Administration Requirements PAGEREF _Toc323742372 \h 172.3.1Veterans Benefits Emergency Planning PAGEREF _Toc323742373 \h 172.4National Cemetery Administration Requirements PAGEREF _Toc323742374 \h 182.4.1Summary PAGEREF _Toc323742375 \h 182.4.2Threshold Requirements PAGEREF _Toc323742376 \h 182.4.3Objective Requirements PAGEREF _Toc323742377 \h 192.5Office of Information and Technology Requirements PAGEREF _Toc323742378 \h 192.5.1OI&T Emergency Communications Requirements PAGEREF _Toc323742379 \h 192.6Staff Office Requirements PAGEREF _Toc323742380 \h 202.6.1Field Program Office Requirements PAGEREF _Toc323742381 \h 202.6.2Veterans Affairs Corporate Office Requirements PAGEREF _Toc323742382 \h 202.7The Department of Veterans Affairs VA Learning University (VALU) and the Employee Education System (EES) PAGEREF _Toc323742383 \h 203Class of Services PAGEREF _Toc323742384 \h 213.1Summary PAGEREF _Toc323742385 \h 213.1.1Class Service Definition PAGEREF _Toc323742386 \h 224Data Requirements Comparison PAGEREF _Toc323742387 \h 22IntroductionSatellite communications are used in a variety of ways throughout the Department of Veterans Affairs. They are used in fixed installations to broadcast the VA’s education services (IPTV CE’s), as portable Very Small Aperture Terminals (VSATs) that provide phone and data connectivity for hospitals that lose their communications, for emergency responders to reach back into VA networks when they are operating in a disaster area with limited or damaged infrastructure, or in handheld form for voice communications anywhere in the country. Portable satellite terminals have been used by the VA since the late 1990’s to provide emergency communications, but came into increased use during and after the responses to 9/11 and hurricane Katrina. Additionally, business units like Mobile Vet Centers and Mobile Pharmacy demonstrated a requirement to reach back into the VA’s networks while operating in the rural areas where many veterans live. Growing out of these needs, together with the new mission requirements, was a VSAT program led by OI&T that served these missions well. The VA’s mission expanded as a result of HSPD-20, NCSD 3-10 and Major Initiative 9 to include both disaster response and emergency preparedness. Because these needs were different than the traditional VA programs using VSATs, a decision was made to pause and take stock of the VA’s needs for satellite communications throughout the enterprise. The VA asked The MITRE Corporation to undertake this initiative, which will unfold in three parts. First, individual business units throughout the VA will be interviewed in order to determine all the requirements. Second, a detailed profile will be prepared for the existing VSAT system, together with research into alternative technologies. Finally, an enterprise architecture and roadmap will be proposed to serve the needs of the individual business units in a cost effective way, while considering how technological changes in the satellite communications industry should impact the roadmap as the VA’s mission and needs for satellite communications continues to evolve over the next 3-5 years. This document aims to serve the first part of this initiative.PurposeThe purpose of this document is to gather requirements for satellite communications throughout all the business units in the Department of Veterans Affairs. These requirements will provide the perspective necessary to design an enterprise architecture that will serve the needs of the business units requiring satellite communications, in a cost effective manner.ScopeThe VA has moved to meet the communications needs of its business units by deploying a variety of communications technologies and communications pathways. This “communications in depth” approach will include traditional land-line resources for voice and data, cellular, and satellite communications (SATCOM). Satellite communications are the focus of this document. All requirements specified herein may potentially traverse the satellite communications network, even though these requirements may be met by other communications pathways during the course of day-day operations or even during a disaster response. Because the purpose of this document is to catalog requirements, not solutions, a deliberate effort has been made to capture the underlying requirement even where a solution currently exists. For example, rather than state that a business unit requires a satellite phone such as Iridium, the requirement is captured as “voice communications with a handheld terminal”. Supporting equipment for business units’ needs (e.g. laptops, printers, etc.) is not cataloged here except where the equipment in question levies an explicit transport requirement. For example, video teleconferencing (VTC) is frequently depicted among requirements because it speaks to a certain minimum throughput requirement.Acronyms and DefinitionsThe acronyms and technical terms used in this document are defined in this section.AcronymsThe acronyms used in this document are defined in this section.TermDefinitionACMAdaptive Coding and ModulationAEMArea Emergency ManagerARCAllocation Resource CenterARSTRATArmy Forces Strategic CommandCBOCCommunity-Based Outpatient ClinicCEOSHCenter for Engineering, Occupational Safety and HealthCJCSIChairman of the Joint Chiefs of Staff InstructionCMOPConsolidated Mail Order PharmacyCOGContinuity of GovernmentCOHRSCentral Office Human Resources SystemCOMSECCommunications SecurityCONOPSConcept of OperationsCONUSContinental United StatesCOOPContinuity of OperationsCOPCommon Operating PictureCPACConsolidated Patient Accounting CentersCPRSComputerized Patient Records SystemCTOChief Technology OfficerDHSDepartment of Homeland SecurityDISADefense Information Systems AgencyDMATSDisaster Medical Assistance TeamsDoDDepartment of DefenseDVB-RCSDigital Video Broadcasting - Return Channel via Satellite DVB-S2Digital Video Broadcasting - Satellite - Second GenerationEESEmployee Education ServicesEIE/ESEEnterprise Infrastructure Engineering/ Enterprise Systems EngineeringEMSEmergency Medical ServicesEMSHGEmergency Management Strategic Health Care GroupEOCEmergency Operations CenterFAXFacsimileFCC Federal Coordination CenterFCSAFuture Commercial SATCOM Services AcquisitionFEMAFederal Emergency Management AgencyFIPSFederal Information Processing StandardFMSFederal Medical StationsGBGigabyteGFEGovernment Furnished EquipmentGISGeographic Information SystemGPMRCGlobal Patient Movement Reception CenterGSAGeneral Services AdministrationHACHealth Administration CenterHECHealth Eligibility CenterHHSHealth and Human ServicesHR&AHuman Resource and AdministrationHRCHealth Resources CenterHSPD Homeland Security Presidential DirectiveIOCVeterans Affairs Integrated Operations CenterIPTV CE?ITInformation TechnologyJPATSJoint Patient Assessment and Command & Control Evacuation SystemJWICSJoint Worldwide Intelligence Communications SystemLANLocal Area NetworkMBMegabyteMCVMobile Command VehicleMERRTMedical Emergency Radiological ResponseMH?MILSATCOMMilitary Satellite CommunicationsMISNMemorial Integrated Service NetworkMOAMemorial Service NetworkMPUMobile Pharmacy UnitMSNMemorial Service NetworkMVCMobile Vet CentersNCANational Cemetery AdministrationNCPSNational Center for Patient SafetyNCSDNational Communications System DirectiveNDMSNational Disaster Medical SystemNIPRnetUnclassified but Sensitive Internet Protocol Router NetworkNORTHCOMUnited States Northern CommandOALOffice of Acquisition and LogisticsOCLAOffice of Congressional and Legislative AffairsOEMOffice of Emergency ManagementOGCOffice of the General CouncilOI&TOffice of Information and TechnologyOMOffice of ManagementOPIAOffice of Public AffairsOPMOffice of Personnel ManagementOPPOffice of Policy and PlanningOQPOffice of Quality PromotionOS&LEOffice of Security and Law EnforcementOSPOffice of Operations, Security, and PreparednessPIIPersonally Identifiable InformationPSTNPublic Switched Telephone NetworkQoSQuality of Service RCSnetReadjustment Counseling ServiceRFRadio FrequencySATCOMSatellite CommunicationsSBUSensitive but UnclassifiedSIPRnetSecret Internet Protocol Router NetworkSSSLMService support Service Line ManagersSTESecure Telephone EquipmentTACLANETactical Local Area Network EncryptionTDMTime Division MultiplexingTDMATime Division Multiple AccessTRACETRANSCOM Regulating and Tracking SystemTRANSCOMUnited States Transportation CommandTS/SCITop Secret / Sensitive Compartmentalized InformationUHFUltra High FrequencyVACOVeterans Affairs Corporate OfficeVAIOC COPVeterans Affairs Integrated Operations Center Common Operating PictureVBAVeterans Benefits AdministrationVCMVariable Coding and ModulationVCSVeterans Canteen ServiceVHAVeterans Health AdministrationVISNVeterans Integrated Service NetworkVistAVeterans Health Information Systems and Technology ArchitectureVoIPVoice over Internet ProtocolVPNVirtual Private NetworkVSATVery Small Aperture Satellite TerminalVTCVideo TeleconferenceDefinitionsThe technical terms used in this document are defined in this section.TermDefinitionIridiumA system of 66 Low Earth Orbit (<200 miles) satellites and their ground hubs, allowing global voice and data transport, or the handheld terminals that use this systemTerminalThe user ground equipment for satellite communications, including the transceiver and RF (antenna, power) components.SatelliteOrbiting communications platform, not a terminalTransportThe means of moving data from one place to anotherTeleHealthA system where medical providers offer services using a video teleconference transport mechanismReferences1Homeland Security Presidential Directive 20 (HSPD-20), “National Continuity Policy”, Department of Homeland Security, May 9, 2007.2National Communications System Directive 3-10 (NCSD 3-10), “Minimum Requirements for Continuity Communications Capabilities”, Office of Science and Technology Policy, July 25, 2007.3VA Directive 6500Veterans Health Administration IPT General Business RequirementsVeterans Health Administration has identified the following requirements for the use of satellite technology for the future:Each Medical Center (152) should have the capability to use a satellite to transmit and receive all types of information (voice, data, and video) to include PII. The capacity should support 10 voice lines, 10 data lines, and one Video teleconferencing unit. This unit should be placed so that it could support the Medical Centers Emergency Operations Center. The unit should be tied into emergency power. These units should be considered redundant communications systems and should not be deployable.Every CBOC (812) should have the capability to use a satellite to transmit and receive all types of information (voice, data, and video) to include PII. The capacity should support 3 voice lines and 3 data lines. The device should be tied into emergency power or battery backup. These units should be considered redundant communications systems and should not be deployable.Each Network Office (21) should have the capability to use a satellite to transmit and receive all types of information (voice, data, and video) to include PII. The capacity should support 6 voice lines, 6 data lines, and one Video teleconferencing unit. The unit should be placed so that it could support the VISN Emergency Operations Center. The unit should be tied into emergency power or battery backup. These units should be considered redundant communications systems and should not be considered deployable.There should be three large caches of satellite equipment to support a medical center in case of a catastrophic failure of critical infrastructure in the community and/or region. The capacity should support 300 voice lines, 300 data lines, and 3 video teleconferencing units. The caches should be geographically dispersed (East Coast, West Coast and Gulf Coast). Emergency generators should be included in the caches to support use of the equipment for up to 30 days.Each VISN (21) should have mobile satellite capacity to fit into an SUV type vehicle for command and control. The capacity should support 3 voice lines, 3 data lines, and video streaming (MOVI).Each VISN(21) should have mobile satellite capacity that is outfitted in a mobile vehicle (30-40 foot RV type vehicle). The capacity should support 6 voice lines, 6 data lines, and one video teleconferencing unit. These units will serve as outreach for the VISN and provide assistance to Rural Health initiatives and Home Based Primary Care initiatives.Home-based Primary Care and Homeless Coordinators in each VISN need a reliable satellite phone or hybrid cell/satellite phone (something like the Terrastar system). Planning assumptions at this point would be one for each VISN (21).The Pharmacy Benefits Management Services has a need for 5 mobile pharmacy vehicles with the capability to link to any VA facility’s VISTA system. The capacity of each system should be for 6 voice lines, 6 data lines, and one video teleconferencing unit.The Office of Telehealth anticipates that in the next 3 years, there will be a need to provide satellite services in remote locations where terrestrial fiber is not adequate. The numbers of this requirement are not known at this point.The Office of Readjustment Counseling currently has 70 mobile Vet Centers that are configured correctly. There is a need for continued sustainment and the addition of new technologies as they become available.The MERRT team has a need for 12 satellite phones for use in the deployment of the team to a radiologic event.Requirements by Business UnitIn this section the requirements for satellite communications are broken out by administration and business unit.Veterans Health Administration VHA has adopted Mobile Vet Clinics, Mobile Pharmacy, and Rural Health in order to expand care outreach to Veterans.Mobile PharmacySummaryMobile Pharmacy Units (MPU) are deployed to serve a disaster (natural or manmade) region during an emergency response, or to support drug prescription tasks for a medical center whose primary dispensing ability is lost. Such deployment is initiated by a VISN or a requesting medical center. As of May 2011, there are two MPU in use – one uses a standalone mobile VSAT unit, and the other has the VSAT components integrated into the vehicle; both are operated while stationary. Each MPU deployed or under construction is of a different vehicle type – one is a Conex container, one is built on a Ford 750 Truck and the third will be a 53 foot trailer. In all cases, the MPU connects to VistA using either remote desktop (Citrix) or a Telnet console session to access/update patient medical records, drug databases and to record the prescription process taking place where the MPU is located. While up to five of these VistA sessions are in progress, the satellite transport solution must also simultaneously allow voice communication (access to the PSTN), one VTC session, and FAX transmission/receipt. During deployment, an IT person is needed on-site to establish connection into remote VistA system, deal with troubleshooting and fault resolution of the SATCOM transport (among other tasks), but should not be required for setup of the SATCOM transport solution itself. In addition, The Pharmacy Benefits Management Services need 5 mobile pharmacy vehicles with the capability to link to any VA facility’s VISTA system. Threshold RequirementsData types6 Voice line , 6 Data lines (VistA database access) VTC, FAXLatencySufficiently low to permit up to five simultaneous VistA sessions with adequate screen update rateSecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), PSTNTerminal sizeTransit case, briefcase or vehicle-integrated SATCOM transport solution Setup time/complexityLess than 10 minutes for setup and satellite acquisition. Automatic “one button” launch of antenna is preferred. Objective RequirementsIf multiple MPU are deployed simultaneously, it is desired that they be able to talk to one another directly.Mobile Vet CentersSummaryCurrently there are 50 Mobile Vet Centers (MVC) deployed nationwide using customized 39 foot vehicles equipped with integrated VSAT terminals. The vehicles are sent to the deployment sites to provide private counseling and preventative healthcare such as flu shots, diabetes tests, blood pressure checks, but no surgery. A portable exam table, refrigerator and lifters are included for emergency patient evacuation. MVCs are used for outreach most of the time, serving as an access point, while other business units ride along to provide services. Mental Health counselors pull up veterans’ health records from the RCSnet database (Readjustment Counseling Services) to schedule appointments, and file online claims. The VBA sometimes uses the MVC to enroll new members and file benefits claims. They tunnel through the VA network to access VistA CPRS in real time. TeleHealth is also desired over VTC. All data need to be protected, including transport back to the VA network, local wireless and LAN networks.MVCs require VTC for remote mental health counseling and disaster response briefings. They need multiple phone lines with office-like features, extension to extension calling across same or multiple geographically dispersed Mobile Vet Centers. They require FAX capability, including FAX direct to emails; satellite and local television access for news & weather. Plus direct Internet access is required for non-VA personnel that may ride along and provide services to Veterans (e.g. Dept. of Labor, National Guard, Non-VA Emergency Responders, and disabled veterans outreach personnel/job services) without hindering the VA’s direct access. MVCs require direct access to VBA applications (veterans benefits); NCA applications (burial services); VHA VistA System (patient care); VistA Imaging and Tele-Radiology systems; Full CPRS for VA providers that are Non-RCS personnel; Telemedicine applications; Fiscal services; Time & leave for MVC staff; and VistA printing capability. MVCs have an emergency response and preparedness capability and cross-agency support role (HHS, DHS) during an emergency while maintaining integrity with the VA network. In the event of an emergency, VHA’s Emergency Response Group (VHA OEM) can borrow the MVCs at certain times and locations to relocate patients from hospitals to safe areas. During those instances, their emergency area managers will assume control of the MVC. They will have their own requirement to reach their networks, as specified in section 2.1.3.MVCs should have direct access to Vet Centers, VA support systems and Medical Centers’ applications computer services without running additional software. They should have the ability of continuity of operations for CBOC, Vet Centers, VBA and Medical Centers, National disaster scenarios. Applications, services, and access should remain available with no interruption if cellular, land, or commercial network access becomes unavailable. Ease of use requiring little or no technical knowledge of IT systems and seamless activation of communications systems within 30 minutes setup time are required.Threshold RequirementsData typesSATPHONE per MVC (for backup) VistA database access, voice (PSTN), VTC, FAXLatencySufficient network speed to support all applications with an acceptable level of performance to clinical providers and other users. Data latency no more than 3-4 seconds.SecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA networks (VistA, RCSNet, VBA), HHS, DHSTerminal sizeVehicle integrated preferred, but transit case or briefcase size acceptableSetup time/complexityNeed to be up running in 30 minutes without requiring an IT person to set up. Automatic “one button” launch of antenna is preferred.Objective RequirementsNone specified.Veterans Health Administration Office of Emergency Management (VHA OEM)SummaryThe Veterans Health Administration Office of Emergency Management (VHA OEM) serves the VA during emergency responses and provides “surge support” during contingency operations. One of the principal functions of the VHA OEM is to operate Federal Coordination Centers (FCCs) when DoD transports medical patients out of a disaster area using C130 aircraft. These coordinating centers will be located at the receiving airports. Although the largest scale disaster may require as many as 56 FCCs operating at one time, on average perhaps 10 would be operating at once. To support this mission, the FCCs require a portable SATCOM solution, providing connectivity into the public switched telephone network (PSTN), a tunnel into the VA network, data connections to HHS, DoD, local EMS, county EOC and state EOC. FCC teams will perform patient tracking activities as evacuation flights arrive. This requires web access to update patient information in TRACE (TRANSCOM Regulating and Command & Control Evacuation System) and JPATS (Joint Patient Assessment and Tracking System). Additional data transfers may include small documents (patient information, passenger manifests) that may be in the form of Microsoft Excel spreadsheets, plus photographs taken of transported patients. This data may be transferred to any of the coordinating groups listed above. Each FCC must be able to process 100-250 patients per day (approximately 50 patients per flight), as flights arrive, with approximately 2-3 hours to process each flight and hours of delay between flights. VTC connectivity to FCC locations is an emerging requirement; webcam quality is the minimum capability required, but standard resolution VTC is an objective.Immediately following a disaster, the VHA OEM deploys an area emergency manager (AEM) to make “quick look” assessments regarding its severity. The SATCOM solution required depends on the size of the disaster; for small disasters, the AEM will deploy alone. For medium and large scale disasters, the AEM would deploy with a team, using a Mobile Command Vehicle (MCV), which is an RV-sized vehicle similar to that used by Mobile Vet Centers. The AEM will require portable SATCOM equipment (suitcase sized) if deployed alone, and equipment set-up must be simple enough that the AEM can perform it alone – no IT specialist will be accompanying the AEM during the disaster survey. During the quick look, the AEM and team will capture data to be disseminated to the VHA Operations Center, including imagery and either pre-recorded or streaming video. Video quality is not critical; what matters is that it can be transmitted. This data needs to be returned to the VHA Operations Center even during severe weather conditions. The AEM will also require a handheld satellite phone for cases when the cellular system goes out.Threshold RequirementsData typesFCC: data (web access for TRACE/JPATS, email documents and images), VTC (webcam quality acceptableAEM: Voice, data (to transfer imagery, pre-recorded or streaming video, web access to VA SharePoint sites)LatencyFCC: Acceptable to have patient data from each arriving flight updated or files transferred within 60 minutes.AEM: Acceptable to have video and imagery transferred in 1-3 hours.SecurityFIPS 140-2 certification in accordance with VA directive 6500. PKI can be used to cover certain data transmissionsNetworksVA, PSTN, HHS, DoD, local EMS, county EOC, State EOCTerminal sizeFCC: Transit-case acceptable, if a dedicated unit is provided (i.e. not shared)AEM: Single person carry (suitcase-sized) when deployed alone; MCV-integrated SATCOM solution preferred when deployed with a team, but not absolutely required.Also required: Handheld satellite phoneSetup time/complexityFCC: Setup time less than 1 hour (afterwards, essentially fixed)AEM: Setup time 10-15 minutes whether deploying with suitcase sized solution or with MCV. Must not require an IT person to set up in either case. For a vehicle-integrated solution, automatic “one button” launch of antenna is preferred.Objective RequirementsStandard quality VTC is desired.10N (Emergency Portion of VHA)SummaryThe VA Emergency Management Office manages the deployment of national assets during a disaster.? One main function of the Emergency Management Office is to coordinate the set up and operation of Federal Medical Stations (FMSs), like field hospitals, during a disaster when patients are evacuated from a disaster area.? Typically fielded over a two-week period, these FMS are deployed in large, ~40,000ft2 buildings that may host up to 250 patients at once. During that time, patient information such as doctors’ notes and pharmacy orders must be entered into VistA (using either a TELNET console session or remote desktop). To support this mission, FMSs would requires a portable SATCOM solution, providing connectivity into the public switched telephone network (PSTN), a tunnel into the VA network, and data connections to HHS. They need to have voice and data capability to log patient encounters, record patients’ medical information, track patients, and care for the patients until they are able to return to their home facility.? Additionally, FMSs are equipped with 5-10 telephones and laptops, plus a FAX machine and VTC setup. The SATCOM setup must be simple enough that the FMS staff can set it up without IT support.? Threshold RequirementsData typesVoice, data, web, VTC, FAXLatencySufficient for standard-quality VTC performance, plus up to 5 VistA sessions operating simultaneouslySecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), HHS, PSTNTerminal sizeMultiple transit cases acceptableSetup time/complexitySetup less than 1 hour, should not require an IT support person for set upObjective RequirementsNone specified.Mobile Medical UnitsCurrently, five Mobile Medical Units are deployed with vehicle-integrated VSATs, almost identical to those deployed in Mobile Vet Centers, with the exception that these units are capable of higher throughput rates. Many other MMUs exist that do not have, but have requested, SATCOM transport solutions. Currently, deployed units are participating in VistA console and CPRS web GUI sessions, voice, email, and web browsing. Access to the VA network is required for these applications. Additionally, these units wish to transport high-resolution medical imagery whose load could reach tens, hundreds or thousands of megabytes. It is not yet clear if these image studies are expected to be transported for immediate interpretation by a radiologist, or saved in a store-and-forward capacity, sent over a longer time period (hours), with patient follow-up. Several of the medical devices that are seeking to transport data are being profiled before they are certified and permitted to transmit over the SATCOM network.Threshold RequirementsData typesVoice, Data, Web, FAXLatencySufficient to handle multiple VistA sessions with adequate screen update rates, concurrently with web browsing and multiple phone conversations, plus transfer of imagery in an acceptably short timeSecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), InternetTerminal sizeVehicle integrated preferred, but transit case or briefcase size acceptableSetup time/complexitySetup less than 1 hour, should not require an IT support person for set up. Automatic “one button” launch of antenna is preferred.Objective RequirementsTransport of data from a variety of medical devices is desired. This includes but is not limited to medical imagery and glucose monitoring results.Medical CenterThere are needed 152 medical centers need to use a satellite to transmit and receive voice, data and video to include PII. Medical Center should be placed so that it could support the Medical Centers Emergency Operations Centers.In addition, there should be three large caches of satellite equipment to support a medical center in case of a catastrophic failure of critical infrastructure in the community and /or region. The capacity should support 300 voice lines, 300 data lines and 3 video teleconferencing units. Caches should be geographically dispersed East Coast, West Coast and Gulf Coast. Emergency generators should be included in the caches to support use of the equipment for up to 30 days.Threshold RequirementsData types10 Voice lines, 10 Data lines, one VTC per medical center.300 voice lines, 300 data lines and 3 VTC per Cache.LatencySufficient to handle multiple VistA sessions with adequate screen update rates, concurrently with web browsing and 10 phone conversations, plus one VTC.SecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), InternetTerminal sizeFixed SizeSetup time/complexitySetup less than 1 hour, should not require an IT support person for set upObjective RequirementsThree large caches of satellite equipment to support a medical center in case of catastrophic failure of critical infrastructure in the munity-Based Outpatient Clinic (CBOC)There are needed eight hundred-twelve (812) CBOCs should have the capability to use a satellite to transmit and receive all voice, data, and video to include PII.Threshold RequirementsData types3 Voice lines, 3 Data lines with emergency power or battery backup.LatencySufficient to handle multiple VistA sessions with adequate screen update rates, concurrently with web browsing and 3 phone conversations, 3 data lines.SecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), InternetTerminal sizeVehicle integrated preferred, but transit case or briefcase size acceptableSetup time/complexitySetup less than 30 minutes hour, should not require an IT support person for set upObjective RequirementsThe unit should be considered redundant communications system and should not be work OfficeThere are needed twenty-one (21) Network Offices should have the capability to use a satellite and receive all voice, data, and video to include PII.Threshold RequirementsData types6 Voice lines, 6 Data lines plus one VTCLatencySufficient to handle multiple VistA sessions with adequate screen update rates, concurrently with web browsing and 6 phone conversations, 6 data lines.SecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), InternetTerminal sizeVehicle integrated preferred, but transit case or briefcase size acceptableSetup time/complexitySetup less than 30 minutes hour, should not require an IT support person for set upObjective RequirementsThe unit should be considered redundant communications system and should not be deployable.Veterans Integrated Service Network (VISN)There are needed twenty one (21) VISNs should have mobile satellite capacity that is outfitted in a mobile vehicle (30-40 foot RV type vehicle). Units will serve as outreach for the VISN and provide assistance to Rural Health initiatives and Home Based Primary Care initiatives. Home-based Primary Care and Homeless Coordinators in each VISN need a reliable satellite phone or hybrid cell/satellite phone.Threshold RequirementsData types6 Voice lines, 6 Data lines plus one VTCLatencySufficient to handle multiple VistA sessions with adequate screen update rates, concurrently with web browsing and 6 phone conversations, 6 data lines.SecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (VistA), InternetTerminal sizeVehicle integrated preferred, but transit case or briefcase size acceptableSetup time/complexitySetup less than 30 minutes hour, should not require an IT support person for set up. Automatic “one button” launch of antenna is preferred.Objective RequirementsNone Specified.Office of Operations, Security and Preparedness RequirementsGeospatial IntelligenceSummaryIn collaboration with GIS agencies across a variety of government agencies, this business unit supports deployed responders in response to an emergency or natural disaster in order to support the generation of a common operating picture (COP) for the VA leadership as well as command in the field, and field operations. These groups receive remote sensing high resolution color aerial imagery, together with other GIS data sources, and manipulate this data to create Shapefiles, and/or Geodatabases. The images (post-processed to minimize their size), Shapefiles, Geodatabase and locally created video must be transmitted at least daily to the VA IOC for inclusion into the COP. These data products can be transmitted during off-peak hours. The typical fielding model for the GIS groups assumes a “staging area” physically removed from the disaster region, and a “base camp” in the “red zone” deployed closer to the disaster area. It is desired to send a subset of these data products directly from the base camp (or wherever they are set up) using satellite communications. The remainder can be transmitted from the well-connected staging area at a later time. Data types/formats are still under investigation in order to compress the file sizes to small footprint but keep the high definition data info. This way more data can be sent from the base camp immediately but not waiting till late evening to send from staging area. Additionally, there is a requirement for asset tracking via satellite, at the level of asset, vehicles or teams, delivered in real time to the GIS system and into the VAIOC COP. It is expected that a data feed of asset/team locations would be delivered in real time from this service provider into the VA GIS network via a non-SATCOM pathway. Finally, it is expected that a daily brief to the VA leadership would be delivered over a SATCOM link from the base camp, incorporating audio/visual components but not live updates of GIS data.Threshold RequirementsData typesVoice, Data (large data files (>GB images), small data files (<1MB shape files), databases), VTCLatencyMust transmit required GIS data products within a 12 hour window (e.g. 7pm-7am) and receive on same intervalSecurityFIPS 140-2 certification in accordance with VA directive 6500. Some shape file data might be SBU, depending on what it depicts (e.g. where medications are being cached or delivered)NetworksVATerminal sizeTransit case or suitcase size.Setup time/complexityLess than 30 mins setup time, the setup must not require IT support.Objective RequirementsIt is desired to have the ability to simultaneously transmit GIS data (images, Shapefiles, Geodatabase) while the daily briefing VTC is in progress.Office of Security and Law EnforcementSummaryThe Office of Security and Law Enforcement (OS&LE) is the police law enforcement body of the VA. In the past, when deployed to disaster events (e.g. hurricane Katrina, Ike, Gustav), OS&LE recognized a need for continuous communications out of the disaster area. Although frequently deployed alongside VHA responders, OS&LE operates independently and cannot rely on communications assets fielded by those groups. IT support has not always been available during OS&LE deployments, so any solution must not rely on IT support for setup/configuration. For secure communications, they currently use secure cellular phones. Minimum capabilities required for an OS&LE deployment, which could be of any scale, includes a mobile SATCOM phone (with antennas for internal and external use plus type 1 encryption), and the ability to transport data in the form of reports / issue briefs, tunneling into the VA network via VPN.Threshold RequirementsData typesVoice, data (reports)LatencyReports transmitted within 5 minutesSecurityFIPS 140-2 certification in accordance with VA directive 6500Capability for Type 1 encryption on satellite phonesNetworksVATerminal sizePortable; a handheld satellite phone is a minimum requirement. A laptop-sized device may be needed if data transport is more than kilobytes at a time.Setup time/complexityLess than 30 mins setup time, the setup must not require IT support.Objective RequirementsNone specified.Continuity of Operations / Continuity of GovernmentSummaryIn accordance with HSPD-20 and NCS 3-10, all federal agencies must have a continuity of operations (COOP) plan facilitating continuity of government (COG) communications to allow the VA’s National Essential Functions to be carried out under all circumstances. To perform these missions, the VA COOP sites have a requirement for emergency communications at a moment’s notice. As a Category II federal agency, the VA must meet certain minimum communications requirements. While the majority of these requirements are focused on the Integrated Operations Center (IOC) site at VACO or the backup IOC at additional COOP sites, some requirements apply to the Secretary of the VA or his successors, when the Secretary is in transit between sites. The primary modes of communication from these sites and the Secretary in transit will be terrestrial (landline or cellular), with SATCOM as a backup for these, providing reduced capability when compared to the terrestrial networks. The SATCOM resources must be available on standby to serve the communications needs of the IOC should the primary pathways fail. The exact requirements for system restoral using SATCOM are 20 voice lines.The SATCOM also include for eleven (11) Command and Control vehicles.In the event of a terrorist attack or natural disaster, the IOC will need to communicate with (at minimum) the following federal agencies: Department of Veterans Affairs, Department of Homeland Security (DHS), Federal Emergency Management Agency (FEMA), Department of Health and Human Services, Department of Defense, and the White House. Communications between these agencies includes but is not limited to: secure and non-secure telephone and FAX, access to the Internet, NIPRnet, SIPRnet, and JWICS. Secure VTC up to TS/SCI may also be conducted between these sites. When in transit, the Secretary will require secure voice communications up to TS/SCI using either a commercial satellite phone or a military UHF SATCOM radio. Video streaming from disaster zone (skype, etc) shall send video back to IOC. Viper Secure VoIP phones will be used in VoSIP network.The communications infrastructure at the IOC will serve as transport to allow national essential functions to be carried out for (at minimum) the VHA and VBA, and any other business units located at VACO.The IOC has an additional mission to coordinate the responses of VHA OEM units when responding to a national disaster that hasn’t triggered the COOP plan.Area emergency manager need a very portable PBX with no more than 30 lbs and can be deployed anywhere in the U.S. with hot spot capability, hybrid cell/Satphone for emergency communications.Threshold RequirementsData typesCOOP: VoIP (secure and non-secure), data over Internet, NIPRnet, SIPRnet, JWICS. VTC (secure and non-secure), Sec/DepSec/successors: secure voice (up to TS/SCI) while in transit. There is no data requirement when on the moveLatencyVTEL within 5 minutesSecurityFIPS 140-2 certification in accordance with VA directive 6500Must have capability to go secure up to TS/SCI at COOP sites, in addition an NSA approved Type 1 encryption solution may be required for voice for Sec/DepSec/successors. Other networks can use VPN tunnel into VA and other worksDepartment of Veterans Affairs, Department of Homeland Security (DHS), Federal Emergency Management Agency (FEMA), Department of Health and Human Services, Department of Defense, and the White House, PSTNTerminal sizeCOOP: Must be mountable on the roof of a buildingSec/DepSec/successors: handheld satellite phone or suitcase-sized terminal for secure voice requirement, Must operate in a moving vehicle.Setup time/complexityCOOP: N/A (fixed)Sec/DepSec/successors: shall not require IT support to set up and use.Terminal PerformanceBecause these terminals are for COOP/COG, a link availability of at least 99% is required during benign weather conditions. The SATCOM terminals should be configured for automatic fail-over operations, which will likely require them to be on “standby” (connected into a SATCOM net, but not transmitting) all the time, but prepared to take over communications restoration within 5 minutes from failure.Objective RequirementsBandwidth requirements will be supported in the COOP terrestrial communications plan. SATCOM is not expected to support all of COOP data and voice circuits in the event terrestrial communications fail. SATCOM will be required for the following:TS/SCI VTC Minimum 348 kbps, Max 768 kbps. This Objective Requirements shall also include Satellite communications of lifecycle support, refresh of older systems and procure new system. Its solution characteristics will have new technology with cost reduction in mind to leverage current investment. Veterans Benefits Administration RequirementsVeterans Benefits Emergency PlanningSummaryThe VBA has a Central Office at VACO and at 61 sites. During an emergency, all 61 sites and VBA CO require voice communications at minimum. Additionally, the Philadelphia site has a mission essential function of providing insurance claims processing, but it is co-located with an IT site, and would plan to piggyback on their communications services. In the event of an emergency, the Philadelphia site will send coordinators to the relevant field office(s) to make available VA-owned housing units for use during the disaster response. These coordinators will need voice and data communications, but they plan to use the comms available at the DHS joint field office. In addition, when the VBA operates with the Mobile Vet Centers (MVC) for outreach services, VBA will leverage the communications provided by the MVC. The VBA Associate Deputy Under Secretaries, Chief of Staff, VBA Financial Officer, Area Directors and the Bay Pines Regional Office Director are in the line of succession for the Undersecretary of the VBA, and thus require handheld satellite phones (with type 1 encryption) and STE in accordance with OSP requirements. In conclusion, with the exception of voice communications, all other comms are expected to piggyback on the communications equipment of other business units. Voice communications must be able to reach from the Regional Offices to the Federal Executive Board in the city of the Regional Office, the VBA Central Office, other regional offices (including conference calls), and verbal reports to IOC and to the Department of the Treasury.Threshold RequirementsData typesVoice, Data (emailing medical claims, housing list spreadsheet)Latency15 minutes for transport of filesSecurityFIPS 140-2 certification in accordance with VA directive 6500security requirements for succession planning may levy additional requirementNetworksVA at IOCTerminal sizeSuitcase size or transit case are acceptableSetup time/complexityLess than 30 minutes.Objective RequirementsFAX and VTC capability is desired. A handheld terminal size is preferred if possible.National Cemetery Administration RequirementsSummaryThe National Cemetery Administration (NCA) is comprised of a headquarters element located at Central office in Washington, DC and 5 Memorial Service Networks (MSNs), located in Philadelphia, Atlanta, Indianapolis, Denver and Oakland. The MSNs have command and control of numerous cemeteries within their respective regions. The predominant traffic flow is from HQ to MSN and MSN to cemetery, but in some instances the MSN HQ may talk to each other directly. There is not a regular need for any of the MSNs to place telephone calls to DoD; however, if a mass burial incident were to occur, NCA has responsibility under the National Response Framework for assistance with mass burials and thus should be able to talk directly with DoD or similar agencies, if the need arises. Between the MSN HQ and the NCA HQ, there is a need for voice and data communications. Data transmissions are for documents, which can tolerate high latency (minutes to hours). SATCOM terminals would be set up in fixed locations, but may be moved between MSNs if the need arises. Terminals that are moved must be set up and operational within 24 hours.Threshold RequirementsData typesVoice, Data (documents)LatencyTransfer time for data files between minutes to hoursSecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA (Traffic is predominantly between each MSNs and the NCA HQ, and between MSNs), PSTN (voice-only connections to DoD, OPM, FEMA, DHS)Terminal sizeTransit cases acceptable to mount on MSN buildings, may be moved between MSNs if the need arises. Briefcase sized terminals are also acceptable. Setup time/complexityNo requirement for initial setup; if disaster requires a MSN HQ to be relocated must be set up and operational within 24 hours.Objective RequirementsVTC capability is desired.Office of Information and Technology RequirementsOI&T Emergency Communications RequirementsSummaryOI&T has three groups which will require emergency satellite communications: OI&T Leadership, OI&T Emergency Preparedness (Service Support Service Line Managers - SSSLM), and data centers. OI&T Leadership is made up of four individuals who require voice communications at minimum, should their communications go out. The SSSLM require voice and data connections, and act as the eyes and ears of the OI&T leadership during a disaster response. Data centers are the access points for all VA data, and if VA applications are to be served during a communications outage, each data center must be equipped with a satellite communications terminal. There are currently ten data centers around the country. Each terminal serving a data center could expect a sustained load on the order of many Mbps. The specific requirements are summarized below. Threshold RequirementsData typesOI&T Leadership: voiceSSSLM: voice, data (web, email), InternetData centers: streaming data in response to requestsLatencyNot specifiedSecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVA, InternetTerminal sizeOI&T Leadership: Briefcase/suitcase size desired for portabilitySSSLM: Briefcase/suitcase size desired for portabilityData centers: transit case, briefcase both acceptable, if they can meet throughput requirementsSetup time/complexityOI&T Leadership: 15-30 minutesSSSLM: 15-30 minutesData centers: N/A (fixed)Objective RequirementsOI&T Leadership desires data and Internet service in addition to a handheld terminal size and 5 minute setup time. Staff Office RequirementsField Program Office RequirementsSummaryThere are 12 field program offices throughout the VA: ARC, EES, CEOSH, CPAC, CMOP, HAC, HEC, HRC, MH, NCPS, OQP, and VCS. These offices are highly business-oriented and their functions bring in substantial revenues for the VA annually. As a result, all of these offices require backup communications, ready on a moment’s notice. What follows is a consolidated set of requirements for this set of program offices.Threshold RequirementsObjective RequirementsData transfers complete in less than 60 seconds.Veterans Affairs Corporate Office RequirementsSummaryAlthough there are 44 unique VA offices in the VACO campus, only the VACO central office itself has a requirement for emergency satellite communications. There are many business units situated in the VACO building, including OGC, HR&A, COHRS, OAL, OPIA, OCLA, OM, and OPP, all of which require backup communications should the primary communications fail. In the event of a disaster requiring VACO to be evacuated, these offices would relocate to the backup COOP site. There is a desire to expand and broaden this service to serve a larger number of users, while adding support for data, VoIP, VTC, public internet and tunneling into the VA network. Threshold RequirementsData typesVoice (analog and/or VoIP), data, VTC, public internet and tunneling into the VA networkLatencyNot specifiedSecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVATerminal sizePermanent fixed mountsSetup time/complexityN/AObjective Requirements The Department of Veterans Affairs VA Learning University (VALU) and the Employee Education System (EES)2.7.1 SummaryThe Department of Veterans Affairs VA Learning University (VALU) and the Employee Education System (EES) uses a satellite delivery system for the transmission and delivery of video, audio and IP-data for the VAKN (VA Knowledge Network) and the Content Delivery Network (CDN). This satellite delivery system is utilized by VHA, VBA, NCA, OGC and other services within the Department of Veterans Affairs. A satellite transponder bandwidth contract has supported VAKN since its inception in July 2000. It is imperative that the contract be renewed in order to provide continuous operation of VAKN and (CDN) which delivers the information to the employee desktop. This bandwidth will provide for (3) conventional channels as well as (4) channels of Internet Protocol (IP) video required for the continued operation of CDN. The VA digital satellite network utilizes fixed receive dishes. With its satellite-based approach to?distribute?educational programs and information to VA staff via the VAKN distribution system, CDN is one of the largest networks?of its kind. CDN has experienced a steady growth in scope and viewership since its beginning in 2002 with more of the same is expected in Fiscal Year 12.2.7.2 Threshold RequirementsData typesVoice, Data, Video, IPLatencyNot SpecifiedSecurityFIPS 140-2 certification in accordance with VA directive 6500NetworksVAKN, CDNTerminal size1.2m or 1.8mSetup time/complexityNot specified2.7.3 Objective RequirementsTo provide clean Ku-band non-preemptive bandwidth 24/7 with no interference or signal loss due to satellite technical issues or customer transmission interference.Class of ServicesThe purpose of Class of Services are defined the priority and bandwidth usage.The Class of Services will define the priority access to the contention time slots based on group QOS operation. The HUB can control over the resource allocation based on the Class of Services.SummaryEach Business Unit has their unique requirements in term of applications, network interface, data type and bandwidth requirements. This section will define the Class of Services association with the business units based on the requirements. Class Service DefinitionThere are five Class of Services have been defined in here with Class of Service 1 as highest Class of Service and Class of Service 5 as lowest Class of Service.In addition, Class of Services are grouped based on the similar requirements of applications, data type, network interface, terminal size and security requirement.Threshold RequirementsClass Service 1All COOP sites will be classified as Class Service 1. It will interface with DHS, FEMA, DoD and White House. It also will interface with JWICS, NIPR network and SIPR network. It has the bandwidth requirement to meet VoIP, Video, VTC, Fax, VA Share Point, Internet access, Secure voice. It needs minimum 3.8M bps of Forward link bandwidth and 2.6 return link bandwidth in order to support all applications.Class Service 2All Mobile Pharmacy and Mobile Vet Centers will be classified as Class Service 2. It will interface with VA Network, PSTN, HHS and DHS. It supports Voice, Data, VTC, Fax and remote desk top. It needs 10M bps of Forward link and 4M bps of Return link for all Mobile Units in the field to support Voice, Data, VA network, HHS and DHS interface.Class Service 3Geospatial Intelligence will be classified as Class Service 3. It will support the generation of a commo operating pictue (COP) for the VA leadership as well as command in the field. It needs 291K bps of Forward link bandwidth and 694K bps of Return link to support high resolution aerial imagery, GIS data sources and create Shapefiles and Geodatabases.Class Service 410N (Emergency portion of VHS), OI&T Emergency Communications, Field Program Office CTO and Verterans Affairs Corporate Office will be classified as Class Service 4. It will support Voice, data, Internet, fax and VTC data. It needs average 700K bps of Forward link bandwidth and 400K bps of Return link bandwidth.Class Service 5Mobile Medical units, Office of Security and Law Enforcement, Veteran Benfits EM Planning, National Cemetery Administration will be classified as Class service 5. It supports Voice and Data only. It needs average 600K bps of Forward link and 400K bps of Return link bandwidth.Data Requirements ComparisonBusiness UnitData typesSecurity RequirementNetworksTerminal SizeSetup TimeIT supportMobile PharmacyVoice, Data, VTC, FAX, Remote desktop; 6 Voice line , 6 Data linesFIPS 140-2VA (VistA), PSTNTransit case, briefcase or vehicle-integrated SATCOM transport solutionLess than 10 minutesNot desiredMobile Vet CentersVoice, Data, VTC, FAX, Remote desktop, SATPHONE per MVC (for backup)FIPS 140-2VA (VistA, RCSNet, VBA), PSTN, HHS, DHSVehicle integrated preferred, but transit case or briefcase size acceptable30 minutesNot desiredVeterans Health Administration Office of Emergency Management (VHA OEM)Voice, Data, VTC, Streaming video, Internet to VA SharePointFIPS 140-2VA, PSTN, Internet, HHS, DoD, Local EMS, County EOC, State EOCAEM: single-person- carryFCC: transit case acceptableAEM: less than 15 minutesFCC: less than 1 hourNot desired10N (Emergency Portion of VHA)Voice, Data, VTC, FAX, Internet to VA TRACE program, Remote desktopFIPS 140-2VA (VistA), PSTN, Internet, HHS, DoDMultiple transit cases acceptableLess than 1 hourNot desiredMobile Medical UnitsVoice, Data, Web, FAXFIPS 140-2VA (VistA), PSTNVehicle integrated preferred, but transit case or briefcase size acceptableLess than 10 minutesNot desiredGeospatial IntelligenceImagery files [<1MB, >GB] GeoDatabase, VTC, Voice, DataFIPS 140-2, some SBUVATransit case or suitcase size.Less than 30 minutesNot desiredOffice of Security and Law EnforcementVoice, DataFIPS 140-2VAHandheld satellite phone, Laptop-sized device.Less than 30 minutesNot desiredContinuity of Operations / Continuity of GovernmentVoice, Data, VTC, FAX, Internet, Secure voice, JWICSFIPS 140-2, NIPRnet, SIPRnet, STE (TS/SCI) VA, PSTN, Internet, DHS, FEMA, HHS, DoD, White House.Mobile: handheld or suitcase-sized; Fix: large enough to cover all load.FixedNot desiredVeteran’s Benefits EM PlanningVoice, Data, EmailFIPS 140-2VAPrefer handheld, suitcase size or transit case are acceptableLess than 30 minutesNot desiredNational Cemetery AdministrationVoice, DataFIPS 140-2VA, PSTN, NCA HQ, MSNs, DoD, OPM, FEMA, DHSTransit cases on buildings, may move between sites. Briefcase sized terminals are also acceptable.Within 24 hoursNot desiredBusiness UnitData typesSecurity RequirementNetworksTerminal SizeSetup TimeIT supportOI&T Emergency CommunicationsVoice, Data, Internet, Streaming DataFIPS 140-2VA, InternetFixed installation, transit case or briefcase/suitcase size acceptable, if they can meet throughput requirements 15 to 30 minutesNot desiredField Program Office CTOVoice, Data, VTC, FAX, InternetFIPS 140-2VA, InternetTransit cases or briefcases; must be portable.Less than 30 minutesNot desiredVeterans Affairs Corporate OfficeVoice, Data, VTC, InternetFIPS 140-2VA, InternetPermanent fixed mountsFixedNotdesiredVALU & EESVoice , Data, VTC, Video, WEBFIPS 140-2VAKN, CDNPermanent fixed mountsFixedYesMedical Center10 Voice lines, 10 Data lines, one VTC per medical center.300 voice lines, 300 data lines and 3 VTC per Cache.FIPS 140-2 VA (VistA), InternetPermanent fixed mountsless than 1 hourNot desiredCommunity-Based Outpatient Clinic (CBOC)3 Voice lines, 3 Data lines with emergency power or battery backup.FIPS 140-2VA (VistA), InternetVehicle integrated preferred, but transit case or briefcase size acceptableless than 30 minutesNot desiredNetwork Office6 Voice lines, 6 Data lines plus one VTCFIPS 140-2VA (VistA), InternetVehicle integrated preferred, but transit case or briefcase size acceptableless than 30 minutesless than 30 minutesVeterans Integrated Service Network (VISN)6 Voice lines, 6 Data lines plus one VTCFIPS 140-2VA (VistA), InternetVehicle integrated preferred, but transit case or briefcase size acceptableless than 30 minutesless than 30 minutesBusiness UnitData typesSecurity RequirementNetworksTerminal SizeSetup Time?VoiceDataVTCFAXRemote Database (VistA, TRACE)Streaming VideoPII cover (FIPS 140-2)NIPR / SBUSIPR/SecretJWICS (TS/SCI)VA NetworksPublic InternetPSTNHHSDoDLocal/County/State EOCsDHSFEMAWhite HouseHandheldSuitcase(s)Transit case(s)Fixed (Mount on buildings)Less than 10 MinutesLess than 30 MinutesLess than 1 HoursLess than 24 hoursFixed (N/A)Must not Rely on IT Support for SetupMobile PharmacyXXXXX?X???X?X???????X?X?X????XMobile Vet CentersXXXXX?X???X?XX??X????XX??X???XMobile Medical UnitsXXXXXXXXXXXVHA OEM - AEM?XX?XX?X???XXXXXX????X??X????XVHA OEM - FCCXX??XXX???XXXXXX?????XX???X??X10N FMS (Emergency Portion of VHA)XXXXX?X???XXXXX?????X?X???X??XGeospatial IntelligenceXXX???XX??X?????????X?X??X???XOffice of Security and Law EnforcementXX????X???X????????XX???X???XContinuity of OperationsXXXXX?X?XXXXXXXX?XXX???X????XXCOG - Sec/DepSec/successorsX??????XXXXXXXX?XXXXX??X????XVeteran’s Benefits EM PlanningXX????X???X????????XX?X??X???XNational Cemetery AdministrationXX????X???X?X?X?XX??X?X????X?XOI&T - LeadershipX?????X???XX????????X??X????XOI&T - SSSLMXX??X?X???XX????????X??X????XOI&T - Data centers?X????X???XX????????X?X?X????XXField Program Office CTOXXXX??X???XX????????X?X??X???XVeterans Affairs Corporate OfficeXXX?X?X???XX??????????X????XXVALU & EESXXXXXXXXXXXXXMedical CenterXXXXXXXXCommunity-Based Outpatient Clinic (CBOC)XXXXXXXNetwork OfficeXXXXXXXXVeterans Integrated Service Network (VISN)XXXXXX . ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download