B2B Attachment 4--B2B Implementation Briefing 2013.ppt
PPT presentation 1 MB Posted
- Attached to
- Medical Records Coding Services Federal contract opportunity
- Solicitation number
- N6264520R0064
View the file
Other files for this federal contract opportunity
Show all 21
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Business to Business (B2B) Gateway Implementation Briefing Chief of Sustainment Operations Ms. Jennifer Pereira Version 1.0
Enterprise Infrastructure
Agenda
| Key stakeholders |
| Overview |
| Roles & Responsibilities |
| Implementation Process |
| Escalation Procedures |
| Points of Contact |
Purpose of Briefing
| Describe plans to connect Commercial Partners to DoD Military Health System (MHS) systems and networks |
| Requirements |
| Participants |
| Approach |
Key Stakeholders
Key Stakeholders
| TMA Falls Church |
| Enterprise Infrastructure |
| Defense Health Information Management System (DHIMS) |
| Defense Health Service Systems (DHSS) |
| Information Assurance (IA) Program Office |
| Office of the Chief Information Officer Information Assurance (OCIO IA) |
| Pharmaceutical Operations |
| Office of the Chief Medical Officer (OCMO) |
Key Stakeholders (con’t)
| Defense Information System Agency (DISA) |
| TRICARE Management Activity Aurora (TMA Aurora) |
| Purchased Care Systems Information Branch (PCSIB) |
| Dental Programs |
| Military Medical Departments |
| Defense Manpower Data Center (DMDC) |
| Defense Finance and Accounting Services (DFAS) |
| Commercial Business Partners (Contractors, Vendors) |
Overview
B2B Gateway Overview Objectives
| Provides authorized MHS Business Partners secure access to DoD Network |
| Connects MHS information systems on Defense Information System Network (DISN) infrastructure and MHS Business Partners on commercial infrastructure in support of DoD healthcare mission |
| Complies with DISN policy |
| Provides support for non-Web based applications |
| Supports secure e-commerce for client/server and system-to-system interfaces |
| Enterprise solution |
| Not intended to provide a Secure Remote Access solution for individuals |
B2B Gateway Management Enterprise Infrastructure VPN Team .Mil Location MHS Business Partner DISA Montgomery/ DISA Columbus Procurement of VPN and Internet Service Provider. Manages their LAN Manages VPNs at MHS Business Partner location, DISA DECC Montgomery and Columbus Manages MHS VPN domain. VPNs between DISA Columbus and the .Mil location Manages their LAN
B2B Gateway Overview Functions
| Provide an assured computing path for the enterprise |
| Meet authentication, integrity, and confidentiality requirements for DoD healthcare environment |
| Provide high availability and redundancy with duplicate components and diverse sites |
| Support documented requirements for MHS Business Partner connections and services |
B2B Gateway Overview Security Features
| Controlled access to the NIPRNet |
| Address translation simplifies DoD traffic filtering |
| Encryption |
| Triple Data Encryption Standard (3DES) Internet Protocol Security (IPSec) VPN |
| Contractor site to gateway |
| Gateway to DoD destination |
Traffic/transaction inspection
| User authentication to the Gateway |
| Individual user ID and password |
Audit capability
Roles & Responsibilities
Roles and Responsibilities Enterprise Infrastructure
| Manages the MHS B2B Gateway Program |
| Customer Relations Management Support |
| Liaison between DISA and Program Office for B2B Gateway implementation and sustainment activities |
| Receives and process initial requirement |
| Recommend technical solution |
| Provide technical consultant to program offices |
| Review and process B2B Gateway Questionnaire |
| Implementation Support |
| Prioritize B2B Gateway implementations |
| Facilitate technical specification meetings |
| Schedule and facilitate connectivity tests |
Roles and Responsibilities Enterprise Infrastructure (con’t)
| Operations and sustainment Support |
| End-to-End monitoring |
| Monitors .mil and commercial VPN tunnel status |
| Incident Management |
| In accordance with ITIL practices |
| Problem Management |
| In accordance with ITIL practices |
| Provide Ports, Protocol and Services (PPS) Category Assignment List (CAL) Support |
| Describe PPS applicability to B2B Gateway |
| Virtual Private Networks (VPNs) |
| Review PPS Registration Requirements |
| Provide current status PPS of policy and procedural updates |
Roles and Responsibilities
DISA
| DISA |
| Montgomery and Columbus (B2B Gateway support) |
| Mechanicsburg, Oklahoma City, etc |
| Computing Center Support for a number of organizations |
| Implementation Support |
| Approves/Disapproves implementation requests |
| Participates in technical specification meetings |
| Provides ruling on Ports, Protocols and Services issues |
| Coordinates firewall changes and changes to other DISA-managed assets as appropriate |
Roles and Responsibilities DISA (con’t)
| Implementation Support (con’t) |
| Access controls |
| Manages User Accounts |
| Issue and delete user identification and passwords as appropriate |
| Password resets |
| Operations and Sustainment support |
| Network Monitoring |
| Distributes outage notifications |
| Incident Management |
| Problem Management |
Roles and Responsibilities Program Office/Government Sponsor
| Sponsors B2B Gateway connection |
| Identify B2B Gateway requirement |
| Review and approve B2B Gateway Questionnaire |
| Approve System Access Authorization Request (DD 2875) for users |
| Complete and submit Enterprise Infrastructure Requirements Worksheet Cover page |
| Coordination network configuration changes with .mil site hosting their application and/or server |
Roles and Responsibilities Commercial Business Partner
| Provide network information |
| Procure and install B2B Gateway compatible VPN/encryption device |
| Procure Tier I or Tier II Internet Service Provider for connectivity |
| Provide qualified on-site touch labor technical support |
| Help resolve telecommunications and support routine maintenance activities |
| Ensure personnel have appropriate security qualifications IT Level II clearance |
| Ensure personnel complete annual Information Assurance Training |
| Submit DD Form 2875 |
Roles and Responsibilities Commercial Business Partner (con’t)
| Obtain Certification & Accreditation documentation |
| DOD Information Assurance Certification and Accreditation Process (DIACAP) accreditation |
| Authority to Connect (ATC) |
| Certificate of Networthiness (CON) |
| Platform IT (PIT) |
| Department of Defense Instruction 8582.01 |
| Report all problems the MHS Service Desk |
| Provide 24 X 7 on call technical points of contact |
| Assist in problem resolution |
| Provide configuration management of B2B Gateway Questionnaire |
Roles and Responsibilities DoD locations
| Submit change request to local Change Control Board or firewall team |
| Configure the local area network to support the B2B Gateway connection |
| Ensure that the appropriate technical support personnel are available to participate in end-to-end connectivity test |
Roles and Responsibilities Military Health System Service Desk
| Provides 24 x 7 x 365 toll-free worldwide access |
| First contact for problem resolution |
| Provides Tier 1 and 2 sustainment support for centrally managed MHS systems |
| Identify, assess, and resolve hardware/software issues |
| Tracks hardware/software issues escalated to Tier 3 until resolution |
| Ascertains failure trends, perform root cause analyses, and suggest architecture/software/business rule changes, when warranted |
| Users can contact MHS Service Desk in the following ways |
| Telephone |
| CONUS on 1-800-600-9332 |
| OCONUS by using the country access code |
| Email to mhssc@tma.osd.mil |
Implementation
B2B Gateway Implementation Key Steps
| MHS Business Partners complete the B2B Gateway Questionnaire and submits to Program Office/Government Sponsor for submission to Enterprise Infrastructure |
| Documents the following |
| Functional and technical requirements |
| Information needed to configure the VPN devices and the B2B Gateway |
| Satisfies Information Assurance and Ports, Protocols, and Service requirements |
| Government Sponsor must complete Enterprise Infrastructure RW |
| Government Sponsor submits Enterprise Infrastructure RW and B2B Questionnaire to Enterprise Infrastructure for review. |
| Technical Specification Meetings as needed |
| Discuss and resolve network/communication issues that could impact a successful connection to the B2B Gateway or government applications and systems. |
| Provide specification for VPN procurement, configuration, installation |
| Develop and update implementation schedules |
| Enterprise Infrastructure submits questionnaire to DISA for review, acceptance, and implementation |
| Obtain signature documentation |
| VPN Configured and installed |
| B2B Gateway configuration completed |
| B2B Gateway End-to-End connectivity testing |
| Service Desk support |
| Configuration Management/Change Management |
| MHS Business Partners obtain the appropriate IT Sensitivity Designation for its employees |
| The DoD currently requires a minimum of IT Level II public trust clearance for access to DoD IT Resources |
| IT Level II or interim IT Level II must be obtained prior to completing the DD Form 2875 |
B2B Gateway Implementation Key Steps (continued)
Escalation Procedures
B2B Gateway Escalation Procedures
| Enterprise Infrastructure/DISA Scheduled Outages |
| MICCB notices are prepared and forwarded to TMA Aurora for distribution |
| Enterprise Infrastructure works with TMA Aurora to ensure minimal operational impact to the Business Partners |
| Enterprise Infrastructure will notify TMA Aurora as soon as possible if it is determine that outage will last longer than the scheduled window |
| Use alternate path if needed |
| Unscheduled Outages |
| Known by Enterprise Infrastructure/DISA |
| Outage notification will be prepared and forwarded to TMA Aurora for distribution |
| Enterprise Infrastructure Network Operations, Enterprise Infrastructure VPN Team, and/or DISA Operations will contact the appropriate technical support needed to resolve the outage. |
| MHS Service Desk notified to inform customers to use secondary path via DISA San Antonio |
B2B Gateway Escalation Procedures
| Unscheduled Outages (con’t) |
| Experienced by MHS Business Partner |
| MHS Business Partners opens a Remedy ticket with the MHS Service Desk |
| Describe the outage (able to log-on but cannot access an application/server, no connectivity to B2B Gateway) |
| Document the trouble ticket number |
| MHS Business Partner notifies the appropriate Government sponsor |
| MHS Service Desk will forward the Remedy ticket to the Enterprise Infrastructure Network Security Operations Center (NSOC) or the DISA VPN team |
| Enterprise Infrastructure NSOC will contact the appropriate network support needed to resolve the outage. |
| Regardless of the type of outage, Enterprise Infrastructure/DISA will provide timely status update to TMA Aurora and the MHS Business Partners |
Points of Contact
| Personnel | Enterprise Infrastructure |
| Government Lead 1 |
Phone Number Email Mr. John Werner 210-338-3186 John.Werner@tma.osd.mil Government Lead 2 Phone Number Email Ms. Jennifer Pereira 703-575-0850 x311 Jennifer.pereria@tma.osd.mil Functional Lead Phone Number Email Chris McDonald 703-347-7674 Christopher.McDonald.ctr@tma.osd.mil Functional Lead Phone Number Email Susie Clarke 210-3383317 Susie.Clarke.ctr@tma.osd.mil Engineering Lead 1 Phone Number Email Eric Connor 703-712-4248 eric.connor.ctr@tma.osd.mil
Questions?
Backup Slides
B2B Gateway Implementation DD Form 2875 Processing
| Business Partner completes DoD Form 2875 |
| Ensure the user completes required IA training |
| Submits the DD Form 2875 to appropriate AIS Security Office |
| TRICARE Management Activity |
| Service |
| AIS Security Office verifies and validates DD Form 2875 |
| Forwards it to Enterprise Infrastructure |
| Enterprise Infrastructure captures the information in System Access Authorization Request database |
| Forwards validated form to DISA |
| DISA issues B2B Gateway ID and password to the user |
| Enterprise Infrastructure provides status report of submitted DD Form 2875s |
B2B Gateway Background
| Enterprise Infrastructure tasked DISA to develop a technical solution to provide NIPRNet access for commercial health care providers in a secure environment (Summer FY02) |
| Solution must comply with DoD/DISA and HIPAA regulations |
| Assumed providers would gain access through the Internet |
DISA provided a CONOPS for B2B Gateway Pilot (Jan 03)
Enterprise Infrastructure/DISA/Humana completed successful test of B2B Gateway Pilot (Mar-Apr 2003)
Enterprise Infrastructure distributed B2B Concept of Operations to TRICARE Next Generation Management Care Support Contractors (MCSCs) (May 2003)
B2B Gateway was fully operational (Sep 2003)
First TNEX contractor successfully connected to B2B Gateway (WPS) (Nov 2003)
B2B Gateway Background (continued) All TNEX MCSC successfully connected to B2B Gateway and in production (June 2004)
MMSO, AudioCARE, and Quest Laboratory successfully connected to B2B Gateway and in production (Aug 2004)
Designated Providers (Jan 2005)
| Vulnerability Management Systems (Mar 2005) |
| Joint Medical Workstation (JMeWS) (Jul 2005) |
Successfully connected Veterans’ Administration and commercial partners supporting the Military Treatment Facility (MTFs) during 2006 - Present
DoD Guidance
Overarching Guidance DoD Instruction 8551.1 To operate on the DoD Network, all systems must:
| Use most current Ports, Protocols and Services (PPS) Assurance Category Assignment List |
| Implement most current version of DISA Security Technical Implementation Guides for enclave security and network infrastructure |
Implement most current version of NSA Security Recommendation Guide for router security configuration
Overarching Guidance TRICARE Systems Manual 7950.1-M
| “All contractor systems that will communicate with DoD systems will interconnect through the established MHS B2B Gateway” |
| “For all Web applications, contractors will connect to a DISA-established Web Demilitarized Zone (DMZ)” |
“Managed Care Support Contractors will connect to the B2B Gateway via contractor procured Internet Service Provider (ISP) connection”
| “Contractor will assume all responsibilities for establishing and maintaining their connectivity to the B2B Gateway” |
| “This will include acquiring and maintaining the circuit to the B2B Gateway and acquiring a Virtual Private Network (VPN) device compatible with the MHS VPN device” |
File details come from the government source that posted it. Updated .