sentinel week 6 h4d stanford 2016

Team Sentinel

● Team members:○ Jared Dunnmon○ Darren Hau○ Atsu Kobashi○ Rachel Moore

● Cumulative # of interviews: 62 + 11○ Users: 3 Experts: 8

● What we do: Enable rapid, well-informed decisions by establishing a common maritime picture from heterogeneous data

○ Open and automated data aggregation (i.e. incorporate open source data)○ Flexible layering and filtering with improved UI/UX○ Enhanced intel through contextualization and easily accessible, common database○ Identifying deviations from baseline by utilizing historical data

● Why it matters:○ Information overload○ A2/AD prevents deployment of traditional ISR in a timely manner○ Data aggregation platforms and database access in PACOM appear extremely manual

● Military Liaisons○ John Chu (Colonel, US Army)○ Todd Cimicata (Commander, US Navy)

● Problem Sponsor○ Jason Knudson (Lieutenant, US Navy

7th Fleet)● Tech Mentors include:

○ Elston ToChip (Palantir)

QUOTE OF THE WEEK

“There’s a huge gap between smart risk-taking and abject stupidity.”

Contents

1. Customer Discovery○ Get-Keep-Grow Diagram

2. Mission Model Canvas

3. Value Props

4. MVP

Last Week...

QUELLFIRE

GCCS (1)

FOBM

STORAGE/COMMS

CST

GCCS (3)GCCS (2)

STORAGE/COMMS

STORAGE/COMMS

Sensors Sensors Sensors

.oth-.json Translator

Visualization

Analytics

Ship-to-Ship Sharing

Long-Term Storage

KEY NEEDSFUNCTIONS

& PROGRAMS

SHIP 2 SHIP 3SHIP 1

Hypotheses Experiments Results Action

We need to figure out how to improve the GCCS workflow

INVALIDATED

- Interviews with Anonymous, Brett Vaughan (OPNAV), Cesar Morales (SRI), CDR David Slayton (Hoover), LCDR David Butler (7th Fleet JICO), Jim Heg/Gina Fiore (BAH)

- COP is different from intel- We need to consider what programs are in the pipeline- We should focus on enabling tools to talk with each other

- Visit to San Diego- Talk with participants in deployment experiments- Get people from different Fleets who own tools talking with each other

Doing COP well is a subset of doing intel well

INVALIDATED

- Interviews with Lee Stewart (S&T Advisor SOCPAC), CDR Jason Schwarzkopf (7th Fleet MOC Chief)

- Intel focuses on red forces and presenting information- COP integrates intel with blue forces and makes decisions- Good intel is a subset of good COP ← ultimate goal

- Talk with on-the-ground watchstanders/analysts

Customer Discovery

Questions for this week...

Are we solving a COP problem or an intel problem?

Are existing data aggregation/fusion/etc program effectively addressing pain points?● Who owns these tools?● What capability gaps still persist?● What other programs have been attempted, and have they succeeded/failed? Why?

Find a way to put different programs in front of beneficiaries and hear feedback (CSII/SIMON, Insight)● Who are the best people to reach out to if we want to connect PACOM/PacFleet/7th

Fleet with capabilities that might exist in other Fleets?

What tools do intel people use? What insights are they trying to get from the tools?

Customer Discovery - Get/Keep/Grow Diagram

Awareness Interest Consideration Purchase Keep Unbundling Up-sell Cross-sell Referral

Activity & People

- Evangelist & advocate from originator Flt- ???

Corey Hesselberg, CDR Jason Schwarzkopf, MIOC watch standers

- Buy-in from flag officers- ADM Swift, VADM Aucoin, RADM Piersey

- N8/9- Dave Yoshihara (PacFlt N9)- 7th Fleet ???

- Maintainers (N6)- Bob Stevenson (PacFlt N6)- 7th Fleet ???

N/A Expanding COP & intel extensions / functionality within 7th Fleet

Expanding user base within 7th Fleet

Expanding tool set to other fleets

Metrics % people who have heard of program before vs after *how to reassess?

# people who say “we want this”

Seems binary… any recommendations?

# Systems outfitted

?? ?? ?? # users within 7th Fleet using tool

# fleets using tool

Research- Interviews to assess needs, organizational dynamics, procurement strategy- Site visits to see current practices-Understanding current workflow

Connecting People and Programs- Ensuring tool developers and users are aware of one another- Finding functional gaps to fill

Prototype- Compile existing data resources- Create representative “fake” datasets- Evaluate relevant ML algorithms for prediction/rules for push alerts- Iterate on human-machine interaction

Strategic Decision MakersVADM Joseph AucoinADM Scott Swift (PacFleet)ADM Harry Harris (PACOM)

Analysts (N/J2)E.g. Jason Knudson, John Chu, Jed Raskie, Joseph Baba Operators (N/J3)CDR Chris Adams (7th Fleet)

Planners (N/J5)Jose Lepesuastegui (N25)

- Common and consistent view of the Area of Responsibility (AOR)

- Timely operational decisions

- Decreased time to predict hot spots, ID & differentiate threats

- Reduced time for analysts to find information and draw conclusions

- Prototype operability + demonstrated scalability

Data Fusion/Sensor Integration Software

- Build solution that integrates with current systems (e.g. GCCS, QUELLFIRE, FOBM, EWBM, INSIGHT)

- Work with PMs and key influencers to determine optimal funding/dissemination avenues and integration with current tool pipeline

- Deploy prototype, confirm buy-in and update features

- Scale deployment, improve product as necessary

Fixed- Buying proprietary data- Software tools- Evaluation of commercial products

Prototyping- Existing sensor platforms and feeds- Academic research- Existing data fusion platforms

Scaling- Available commercial + military data- Existing database tools (Palantir, AWS)

- Need commanding officer to confirm decision-making benefits

- Need intelligence officers from ONI / N2 and operators from N3 to confirm effectiveness of insights

- Need IT approvals to integrate into systems

- Need support of commercial partners if we want to leverage their platforms

-Need support of existing PMOs/S&T personnel to make sure we’re not duplicating work

Beneficiaries

Mission AchievementMission Budget/Costs

Buy-In

Deployment

Value Proposition

Key Activities

Key Resources

Key PartnersMilitary- 7th Fleet + designated sponsor- NPS/ONR- Acquisition Personnel- Existing PMOs/PORs- Other Fleets

Commercial- Distributed sensor platform companies (i.e. Saildrone, AMS)- Data analytics (i.e. Palantir, Google)

Academic- Universities (i.e. University of Hawaii)- National Labs (Lincoln Labs, Sandia)

Other- IUU fishing + anti-smuggling stakeholders (i.e. Coast Guard, PNA)- Disaster relief agencies

Mission: Enabling Rapid, Well-Informed Decisions from Heterogeneous Data

Testing- 7th Fleet assets for pilot- Research barge- Access to model analyst data interface and in-development tools- Access to sample incoming sensor feeds

Variable- Travel for site visits, pilots- R&D personnel-Development

IMPROVE TACTICAL AND STRATEGIC DECISION

MAKING VIA BETTER DATA HANDLING

(1) Rapid Strategic Decisionmaking via Improved Reporting and Coordination

(2) Improved Tactical Decision Making via Timely, Accurate Information Sharing

(3) More Effective Analysis via Searchable, Visualizable Data Integration (Layering & Filtering)

(4) Predictive Intel and Alerts (e.g. Machine Learning)

ENHANCE INCOMING DATA STREAMS

(1) Improved Collection of Existing Data Streams (e.g. Fishing Broadcasts)

(2) Painless Incorporation of Multiple New Sensing Modalities

(3 Integration of Incoming Data Streams with Existing Object-Oriented Database

Products& Services- Timely data- Good UI/UX

for presenting data

- Streamlined reporting process

- Improved coordination across ranks

- Utilizes current tool pipeline

Customer Jobs

Gains

Pains

Gain Creators

Pain Relievers

- Good UI/UX- Platform

incorporates more data streams

- Platform is robust and can handle drop out of data streams

- Allocate assets- Identify,

eliminate threats

- Predict hot spots

- Safety of team- Projecting

peace, stability in region

- More informed decisions

- Faster decisions- Decisions made

on most up-to-date info

- Poor quality/lack of data

- Latency of data -> insight

Admiral/Strategic Decision Maker

Value Proposition Canvas

Customer persona:

● 3 or 4 star admiral● Born in late 1950’s● Have their own office on-base● Gives out challenge coins

● 30,000 ft view thinker● Spent entire professional career

in Navy (deeply ingrained culture)

Products& Services

- Contextualized, object-oriented database

- Algorithms for processing, analyzing data

- Ability to search for trends across database

- Integration of disparate data sources

- Automation of data analysis

- Improved UX/UI- Predictive notifications- Filtering and layering

features

Customer Jobs

Gains

Pains

Gain Creators

Pain Relievers

- Compatible data format

- Incorporate multiple data streams with existing object-oriented database

- Training and integration with current processes is simple

- Collect & analyze data

- Communicate findings

- Piece together contextualized awareness

- More actionable insights

- Faster identification & response times

- Easy-to-use

- Incorporation of context is manual/mental

- Poor quality / lack of data- Latency of data -> insight- Long onboarding processes

Analyst (N2)


Customer persona:● Sits in front of computer all day● Job is normally boring with bursts

of excitement● Some may have constantly

varying hours/schedules

● “19 year old from Oklahoma”● Regimented schedule● May or may not like what they do

Products& Services

- N/A

- Actually a common operating picture!

- Data is actually synced across databases Customer

Jobs

Gains

Pains

Gain Creators

Pain Relievers

- No hardware to deploy so no risk of asset or personnel loss

- Fewer change orders- Training and integration

with current processes is simple

- Utilize assets and human capital in order to obtain ISR data on adversary or regions of interest

- Timely and enhanced allocation and deployment of assets

- High manpower, time- Operator error- Safety concern for

deploying in unfriendly territory

- Struggle to redeploy systems on short notice (<12 hours) = frustration

- Long onboarding processes

Operations (N3)


Customer persona:

● General sense that N2 and N6 “work” for them

● “19 year old from Oklahoma”● Regimented schedule

● May or may not like what they do

(green indicates that validation is still needed)

MVP: Software Domain Awareness

Program POC OrganizationFunction & Goals

To be used by whom?

Security Level Status Contract History Inputs

Technical Details

CSII

Insight

MTC2

Quellfire

DCGS-N Increment 2

C2PC

HAMDD

SeaVision

GCCS

EWBMRC2 (Resilient C2)

Sample In-Development Product: ONR/CTI EWBM Tool

Questions?

Map of System Functions and Needs

QUELLFIRE

GCCS (1)

FOBM

STORAGE/COMMS

CST

GCCS (3)GCCS (2)

STORAGE/COMMS

STORAGE/COMMS

Sensors Sensors Sensors

.oth-.json Translator

Visualization

Analytics

Ship-to-Ship Sharing

Long-Term Storage

KEY NEEDSFUNCTIONS

& PROGRAMS

SHIP 2 SHIP 3SHIP 1

MVP (2 weeks ago)

MVP (3 weeks ago)

AIS Weather

Customer Workflow

N2

N3

N2(“owns”

the intel)

N3(“owns”

the assets)

Ready-To-Use DataDeployment

Data Acquisition

Data Analysis

Data

Order/Decision

Customer Workflow

Key Acquisition Paths

● Several potential deployment strategies

○ Linking in with an existing POR (PMW-150, etc.)

■ Pros: Allocated funding, long-term integration plans

■ Cons: Long timescale, getting in the door

■ POCs: ONI, SPAWAR (Stan Kowalski), Primes

■ Source of Excitement: TBD

○ Rapid Acquisition Pathways (Limited Objective Experiments, Rapid Reaction Technology Office)

■ Pros: Speed, Close to user, Don’t have to go through Navy (other services work)

■ Cons: Limited spending authority

■ POCs: 7th Fleet (Jason Knudson), DHS (Chuck Wolf)

■ Source of Excitement: Rapid deployment, changed acquisition model

○ DARPA

■ Pros: Development mindset, existing programs (Insight) that are well-aligned, deployment authority/capability to pay for deployment to end-users

■ Cons: stepping on toes, limited number of PMs

■ POCs: Craig Lawrence (ADAPT)

■ Source of Excitement: Directly solving a problem as opposed to many-year process

Sample Deployment Path (Software, POR Path)

1. Operational testing to make sure meets military specs (engage SPAWAR for this)a. Ensure NSA-standard Information Assurance (IA)

i. Lock down system and codeii. Make sure no category 1,2,3 in code - backdoors, exceptions, etc.

b. Observe appropriate NIST protocols (TBD)2. First, limited deployment to evaluate functionality (on testbed system or specific asset)3. Then, if integrated into a POR:

a. Deployed on whatever platform is neededb. Moves into sustainment phasec. Think about disposal & replacement--we want continuous improvement!

4. IT installs where requireda. Technical support install software and make sure up and runningb. Maintains communications systems and networks

5. Personnel training for system operation and maintenancea. CTMs focus on maintaining classified systems & special collections abilities

WE WILL BE GETTING MORE DETAIL ON THIS GOING FORWARD!

sentinel week 6 h4d stanford 2016

Education