SPAWAR Internal Briefing Template - PowerPoint PPT Presentation

Loading...

PPT – SPAWAR Internal Briefing Template PowerPoint presentation | free to view - id: f615f-ZDc1Z



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

SPAWAR Internal Briefing Template

Description:

... enter into a contractual agreement (bailment) with the companies of the selected ... A Bailment Agreement is a legal requirement for any non-government owned ... – PowerPoint PPT presentation

Number of Views:459
Avg rating:3.0/5.0
Slides: 21
Provided by: ndi1
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: SPAWAR Internal Briefing Template


1
Trident Warrior 2008 Executive Overview
NDIA 9 SEP 2008
Richard Woods Director, Requirements Analysis and
Assessments Dept. SPAWAR 5.1.1 619-524-7562 richar
d.woods_at_navy.mil richard.woods_at_navy.smil.mil
2
Trident Warrior Scope
  • Trident Warrior (TW) experimentation has included
    USMC, USA, USAF, USCG, NCIS, FBI, local first
    responder NGOs, industry, academia, and law
    enforcement participants
  • Coalition participation has included UK, CAN, NZ,
    AUS, FR, Chile, ROK, and Netherlands
  • Direct involvement of over 60 U.S. and 19
    coalition ships
  • Since 2003 TW has provided experiment data for
  • 300 Program of Record Technologies
  • Results have verified or altered SYSCOM POR
    development - accelerating fleet delivery
  • 120 Non-Program of Record Technologies
  • Results have immediately influenced / impacted
    OPNAV POM decisions
  • Generated over 100 formal DOTMLPF recommendations
    to the Sea Trial Executive Steering Group (STESG)

3
Trident Warrior Process
  • 16 step end-to-end process covering
  • Concept Design Fleet led
  • Technology Selection Naval NETWAR FORCEnet
    Enterprise (NNFE) driven
  • Test objective development 2 month dedicated
    project
  • Lab based rehearsal risk reduction / mitigation
  • Execution both at sea and ashore
  • Analysis Naval Postgraduate School (NPS)
    experts
  • Reporting to NNFE, through Military Utility
    Assessment (MUA), then STESG
  • Predictable, repeatable, and deliberate
    experimentation
  • Sea Trial governed and Fleet coordinated approach
  • Adds to the body of knowledge for gap closure
  • Replaces anecdotal information with analytical
    data and assessments
  • Provides experimentation data repository

Experimentation Answers Questions!!
4
Trident Warrior Schedule Criteria
  • Conducted annually
  • Alternates between East and West coasts (odd and
    even years respectively)
  • C2F or C3F Officer Conducting the Experiment
    (OCE)
  • Leverages existing events or group sails
  • Work with SYSCOMs to support specific / targeted
    technology testing
  • Results / recommendations meet POM / PR deadlines

5
Trident Warrior Focus on Fleet Needs
6
Trident Warrior Technology Levels
TRL 4-5 Non-POR Technologies Needing to show
Military Utility / New Ideas
20
Trident Warrior Provides Integrated
Network Expert Objective Development Experiment
Rigor Comprehensive DCP Detailed Analysis
TRL 6-7 POR Technologies Needing at-sea testing
for product development
60
TRL 8-9 POR Technologies Ready for IOC
20
Total Experiment Technologies Per Trident Warrior
Average 110
7
Trident Warrior Technology Composition
  • Non-POR Experimentation
  • Govt or Industry sponsorship
  • Objectives
  • (1) Close Fn capability gap
  • (2) Identify barriers to success
  • (3) Transition to POR
  • POR Experimentation
  • SYSCOM or Joint sponsorship
  • Objectives
  • (1) Accelerate development
  • (2) Reduce risk
  • (3) Improve capability

thus far
  • TW technology count up 175 from TW04
  • Substantial growth in POR experimentation

8
Trident Warrior ROI
  • Pre - Trident Warrior
  • SYSCOMS had independent network experiment
    programs
  • Technologies were tested 1 or 2 at a time
  • Each test required separate planning, design,
    network development, asset coordination, and data
    collection and analysis
  • No formal reporting process or event data
    repository
  • Post - Trident Warrior
  • SYSCOMs use / rely on Trident Warrior as
    dependable FORCEnet venue
  • Quality experiment venue to over 100 technologies
    annually
  • A single team plans, designs, develops networks,
    collects data, and provides analysis
  • Single web-based planning and data collection
    repository
  • TW Process Experiment Benefits
  • Fleet leave behind HSTBG utilized SNR Network
    during deployment
  • Speed To The Fleet - ADNS increment II IOC
    accelerated by years
  • Next BIG Thing Inter-battle Group High B/W
    Network

9
Organizations
  • CFFC Sea Trial Lead
  • OPNAV N6 Resource Sponsor
  • NETWARCOM Trident Warrior lead
  • Numbered Fleets - Trident Warrior Fleet Sponsors
  • C2F Sea Strike and Sea Basing Lead
  • C3F Sea Shield Lead
  • SPAWAR Trident Warrior CHENG
  • Naval Postgraduate School Analysis Lead for TW
  • NWDC Navy Doctrine
  • AUSCANNZUKUS Coalition lead
  • MCCDC USMC Lead for TW Integration
  • OPTEVFOR Test and Evaluation

10
Trident Warrior 08
  • Trident Warrior 2008 (TW08)
  • TW08 executed in June 2008, 6th annual major
    'operational' C4ISR experiment
  • Participants 41 Commands, 12 U.S. Ships, 2
    Canadian Ships, 2 Australian Ships, 1 New Zealand
    Ship, and 1 United Kingdom Ship (virtual)
    Netherlands, ROKN and Chile (observers)
  • Experiment data is still being analyzed with
    final report expected in OCT 08

11
(No Transcript)
12
TW08 Participants
  • Ship
  • USS GEORGE WASHINGTON (CVN 73)
  • USS BLUE RIDGE (LCC 19)
  • USS BONHOMME RICHARD (LPD 6)
  • USS MILIUS (DDG 69)
  • USS COMSTOCK (LSD 45)
  • USS CHUNG-HOON (DDG 93)
  • USS PAUL HAMILTON (DDG 60)
  • USS LAKE ERIE (CG 70)
  • USS PORT ROYAL (CG 73)
  • USS OKANE (DDG 77)
  • USS REUBEN JAMES (FFG 57)
  • USS RODNEY M DAVIS (FFG 60)
  • USNS YUKON (T-AO 202)
  • HMAS ANZAC
  • HMCS OTTAWA
  • HMCS REGINA
  • HMNZS TE KAHA

Shore
COMPACFLT MIFCLANT C2F MIFCPAC C3F NO
RTHCOM NCTAMSPAC TFMC NCTS San
Diego ICSTD Balboa Naval Hospital METOC Lab
N.I SSC S.D. FIOC SSC Charleston SPAWAR
OT3 NSWC Crane CTF 34 NSWC Philadelphia ONI NSWC
PHD NMIC NSWC Dahlgren CPR7 Patuxent River MD
  • 43 Commands
  • 113 Technologies
  • 85 Shipboard Installations
  • 50 Shore Installations

13
Technologies by Focus Areas
21 Mar 08
Information Operations (8) (LCDR Trenny Foster
/ Larry Bagley) KIV-7MIP Project Midway Net SEI
HITS/ISRnet (aka JF COMINT) MLS Sensor Grid RTT
(HITS/ISRnet) HITS on Sub BFC Test INMARSAT C
Validation
Maritime Domain Awareness (11) (Dan Dunaway /
Kevin Kurtz) CMA JCTD Panda Google Earth
Services (aka BMC aka Coll COP) GBS /
USCG MASTER JCTD (Inc Radiant Dahlia) MS CPA LiN
X FP Portal MIDAS SIDI
Cross Domain Solution (6) (Caterina Brott) HAP
(2) HAP on SUBLAN Radiant Mercury (2)
I3-CDS
Coalition (15) (Martin Jordan)
AIS2GOLD SPAWN MIO Data Reduction Ad hoc
NW CND (IA Srvr) Virtulized Services C2PC
Accelerator Multi- Ad hoc Subnet Mgmt ACP
200 A-Z Eff XML Lab Risk Reduction Testing
Only NXP Lite RR LOE JPIP RR LOE SNR
Wideband G_93 RR LOE WAN Opt RR LOE P-Chat
RR LOE KG-250 RR LOE
Distance Support (9) (LT Ken Box) RED Sup Center
Air Squad Agil (OOMA Booster) ICAS to
MRAS Remote Mon. CIWS E-Prognostic Cap DS SIPR
NIAPS AVITS ERDDS JAL
Intelligence, Surveillance, and Reconnaissance
(11) (Dave Ayers) ASA Sea Mist (aka SA
MDA) MSI Radiant Sunrise 3 w/Google
Earth Client Radiant Brass Aqua
QuIPS TAMM SeaPort ELT 3500 DCGS-N LCTN (includes
Joint Hybrid OPs )
Networks (12) (Tom Loftis) Tactical Switching (3)
ITSM Incident Mgmt (TSw) ISNS NGT ADNS/TSw
high speed (2) IASM Blackberry NGO Network
PKI/CAC Cap Efficient XML
Fires (5) (Ricardo Blanco) CRAM MIT w/AFATDS
6.5 MAX Link-16 SACC-A w/NFCS Efficient XML
Command and Control (17) (Mark Steers) SCJC2
NECC Mako Chat AIS CPOF CAP on Demand
GCCS-M Pilot GCCS-M Client Comparison / XCOP
OSI JCRE JMPS-E TMIP-J LOGCOP NTCSS
(Viking) NITES (VNE-NCS) TMOCCS SOA MHQ/MOC
Sea Shield (2) (LT Bob Leopold C3F / Jim Beck,
C3F) USW-DSS DS DTE
Human Systems Integration (4) (LCDR Doug
Magedman) HPAT SLATE TBCMS HSI GVP (w/GCCS-M)
Wireless Networks (8) (Chris Dillman) WRBS EMIO
VBIS, Relay Hop, Mesh MIO Tar2Host
TBCMS Mobilisa FAN MCSBEN (w/SUITE B)
Knowledge Management (2) (Dr. Shelley
Gallup) ERM CLA
Government Sponsor Commercial Sponsor
ISNS NGT Hosted CMFP Connection
Across Focus Areas
14
TW08 Technologies
  • PMW 120 HITS/ISRnet, HITS on Sub, ML Sensor
    Grid RTT, AIS, NITES, SCCID, DCGS-N, Project
    Midway, I3 CDS
  • PMW 150 Air Squadron Agility, BMC/Google
    Earth., Capability on Demand, GCCS-M Client,
    Comparison, TMIP, NTCSS Viking
  • PMW 160 HAP, SCJC2, IASM, KIV7-7MIP, IA Sever,
    C2PC Accelerator, EMIO/VBIS/USV//Relay, Hop Mesh,
    RM, NGO network, Blackberry, PKI/CAC, ISNS NGT
  • PMW 170 SNR WB,
  • PMW 790 Tactical Switching/ITSM/EMNS/Inc IIA
  • SPAWAR 5.1 Modeling Simulation Model
    validation
  • SSC MIT/AFATDS, Log Cop
  • Others PMA, PMS, PMO, NRL, NUWC, NSWCONR,
    JFCOM, STRATCOM, NSA, C2F, C3F, TENCAP,
    AUSCANZUKUS, Industry. Etc.

15
Future Trident Warriors
  • Trident Warrior 2009
  • Planned for Summer 2009 in Atlantic, emphasis on
    MHQ/MOC and MDA
  • COMSECONDFLT identifying ships and dates. A_Z
    will propose Coalition technologies.
  • U.S. government and industry technology selection
    complete
  • Trident Warrior 2010
  • Planned for Summer 2010 in Pacific (historically
    using ships transiting to support RIMPAC),
    Concept Development to start August 2008
  • Technology Selection will occur in early 2009

16
Opportunities to Participate
  • Trident Warrior 2009
  • U.S. government and industry technology selection
    complete
  • Trident Warrior 2010
  • Technology Selection will occur in early 2009
  • Commercial Area Announcement will be published by
    SPAWAR in early calendar 2009

17
Commercial Area Announcement
  • SPAWAR will enter into a contractual agreement
    (bailment) with the companies of the selected
    Initiatives where the initiative proposes to use
    a technology(s) not owned by the government
  • The companies will loan their technology to
    SPAWAR for the duration of the experiment
  • A Bailment Agreement is a legal requirement for
    any non-government owned technology(s) that are
    in the physical custody of the government (ex. in
    a government lab or on a government ship,
    aircraft, sub, etc.)
  • A Bailment Agreement is also a legal requirement
    for any non-government owned technology(s) for
    which government support (ex. NETWARCOM, SPAWAR,
    NPGS, etc. for ex. SSAAs, IATOs, installation
    planning drawings, installations, removals, etc.)
    is required for experimentation participation
  • Liability and payment for technology
    transportation are typically negotiated as part
    of the bailment agreementTW policy is to not
    accept liability for technologies on loan to the
    experiment and to require the industry vendors to
    pay for all shipping

18
Recommendations(Helpful Hints)
  • Start early
  • Be flexiblethings change
  • Be familiar with Navy Installation processes and
    requirements
  • Ex. System Security Certification and
    Accreditation
  • Be aware of corporate resource commitments
    (personnel, equipment, etc.)
  • Assume youre behind or late now!
  • Assume that I am optimistic

19
Questions?
20
End of Slides
About PowerShow.com