Space

1
Space Naval Warfare Systems Command
PMW 166 Naval Messaging and Base Level Informati
on Infrastructure (OCONUS) Brief to AFCEA San Die
go Chapter
17 Jun 2002
CAPT Bill Bry PMW 166 [phone] william.
bry_at_navy.mil
2
PMW 166s Mission

• Provide integrated, end-to-end, secure,
  interoperable
  
• organizational messaging capabilities for Navy
  ashore
  
• and afloat commands, Joint Task Forces (JTFs),
• embarked USMC units, Military Sealift Commands,
• and USCG platforms and to provide the OCONUS
• Navy shore establishment with secure, improved
• quality network service, as well as the
  telephony
  
• replacements and upgrades.

Established December 2001
3
PMW 166s Programs

• Shore Messaging
• Defense Message System (DMS)
• Legacy Messaging Systems
• Tactical Messaging
• NAVMACS II/SMS
• Base Level Information Infrastructure (BLII)
  OCONUS/Telephony
  

4
Shore Messaging

• PMW 166-1

5
Defense Message System
6
DMS Directory
7
DMSHigh Assurance Messaging
EncryptstheMessage
DecryptstheMessage
Message
8
End-to-End Architecture
Legacy (transitioning to DMS)
DMS
NAVAL AMPHIBIOUS BASE
BASE
TELEPORT
OTHER SERVICES
CLINIC
ACC/LCC
BASE
HQ
TRNG CEN
TMG
IMA FISC
NAVAL TRAINING CENTER
NAVAL WEAPONS STATION
PIER CONNECTIONS
Tactical Messaging Gateway
Deployed/ Mobile Units
Area/LocalControl Center
ShoreOrganizationalUsers
Base Area Network
End-to-End Secure, Interoperable Organizational
Messaging
9
Evolution of Naval Messaging Systems
Task Force Web Portal
FY96 Transition
FY97 Transition
DMS Implementation
X.400/X.500 Transition
Tactical SingleMessaging Solution
Baseline Components
FMX/FSMDUSC
MDT
FAMIS/FSMDSA
TacticalMessagingGateway(TMG)
NAVCOMPARSCSRFS
Baseline Components

MFIMTAPUA/UA
MCS Nova User Profiler

LMDX
SRTMODE-5
MDT
DEFENSE MESSAGE SYSTEM
MMS/Gate Guard
PCMT (MARCEMP)
RIXT
DMSACCsLCCs
MMS
NAMRADSDCT-2000O-T-C
MMS/GateGuard
PCMT (MARCEMP)
TELETYPE
Ashore DMS Client
10
Tactical Messaging

• PMW 166-2

11
Tactical Messaging Gateway
12
NAVMACS/SMS Family
1970sTechnology
DMS Legacyfor AlliedInteroperability
1990sTechnology
13
Joint Interoperability
Between these 2 points We must be Interoperable
with other S/As !
STEP
Will Receive Both Navy and JTF Messages
CJTF and Staff Embarked
Also must support Other Service Embarked Units
TMG
To a Large Extent We have Architectural Freedom
Between these 2 Points !
Navy Only Domain
14
Base Level Information Infrastructure (BLII)
OCONUS

• PMW 166-3

15
BLII OCONUS Goal(Major Customers CPF, CNE, CUSNC)
IT-21 Operational
THE NMCI BLII OCONUS Operational Support

• Secure IT Transport
• BLII OCONUS NMCI IT 21 Navys Contribution
  to GIG

Building the Navy Intranet which will support
Joint Vision 2020
16
What is BLII OCONUS?

• It is IT as product
• Delivers NMCI-Like Infrastructure to OCONUS Navy
  Customers
  
• Designed to assure NMCI interoperability
• FFP order under the ViViD contract to General
  Dynamics
  
• Provides a secure infrastructure to the wall plate

• Is not IT as service
• BLII OCONUS Intranet does not provide
• Seat Management
• Operations and Support
• PCs, Workstations, or Peripherals
• WAN connectivity
• It is not designed by the Government

17
BLII OCONUS Implementation Approach
Mod 2 Exercised 10/16/2001 CLIN Bahrain - 0014
Priority 5 Buildings
Common apps
Options
Enterprise Management CLIN 0013,0014
Mod 1 Exercised 6/14/2001 CLINs Far East - 0007
, 0010, 0013
Bahrain - 0008, 0011 Europe - 0009
Server Consolidation/Farms CLIN 0009, 0010, 0011
Netview/Cisco Works Integration CLIN 0007, 0008
Information Assurance
Basic Order Awarded 5/16/2001
WAN Electronics
Task Requirements Notice (TRN) Firm Requirements
BAN Electronics
LAN Electronics
Priority 1-4 Buildings ISP/OSP
All Bases all Buildings
Asset Inventory Database
18
BLII Projects

• BLII OCONUS Modernization
• Pierside Connectivity Upgrades
• Telephone switch upgrades and replacements
• DISN-E/DISA-PAC Navy portion of the Defense
  Information Systems Network in Europe and the
  Pacific
  
• OCONUS CONUS switch improvements (i.e., San
  Diego CATS, Guantanamo Bay)
  
• IT Infrastructure Support for MILCON
• USCINCPAC HQ 21
• Bahrain P903/904 Command Center

19
BLII (OCONUS) Program Schedule
BLII OCONUS Timeline
USMC/EDS define CLIN 0036AA USMC Bases Japan
DiegoGarcia
Chinhae
Sasebo
Naples
Rota and Sigonella
ASN RDA Decision Brief Strategy for CLIN 0036
Guam and U.K.
Souda Bay
Yokosuka
La Mad
Okinawa


Jan Feb Mar Apr May Jun Jul Aug Sep Oct
Nov Dec
CY02
YokosukaLine Upg
La Maddalena Switch Repl
Bahrain P903/904DRSN order
Rota Switch Upg
Diego Garcia Switch Upg
LondonSwitch Upg
Order BahrainP903/904DSN Switch
Bahrain P903/904DSN TSIP work
Order Sigonellaswitch
Telephony Timeline
20
Back-ups
21
AUTODIN (c1965 - 20__)Too Tough to Die
22
DMS Program Schedule
FY02
FY04
FY03
Q1
Q2
Q3
Q4
Q1
Q2
Q3
Q4
Q1
Q2
Q3
Q4
AUTODIN DTH Closure
DMS 3.0 Fielding
3.0 Implementation
3.0 Transition
Tactical Fielding
DPG Guideline
Afloat FOCFY 16
NAVY (Ashore and Afloat)
SCI AUTODIN Bypass Closure
23
Points of Contact
Tactical Messaging APMPMW 166-2Kathy
Grauer(858) 537-0243kathy.grauer_at_navy.mil
Base Level Information Infrastructure (OCONUS)
APMPMW 166-3Ken Higa524-7583ken.higa_at_navy.mil
Naval Messaging Technical Support DMS
Consolidated Help Desk (DCHD) [phone], dms
help.navy.mil, dmshelp.navy.smil.mil
DMS Tech Support [phone], tsa_at_spawar.navy.
mil Legacy [phone], dtms_at_spawar.navy.mil
NAVMACS Help Desk(800) 222-4656
Program Manager PMW 166CAPT Bill Bry (619) 52
4-7910 william.bry_at_navy.mil Deputy Program Mana
ger PMW 166A Carol Kim [phone] carol.ki
m_at_navy.mil Shore Messaging APM, Acting PMW 166-1
CDR Chris Roberts [phone] chris.robert
s_at_navy.mil
24
Joint Interoperability
National Gateway
2-way SMTP/HTTPS