21
PIA & Lab Collaboration Event 5 December 2018

PIA & Lab Collaboration Event - SOFWERX...Team Orange, Idea #1 PIA & Lab Plan Overview: The Orange Team proposes to solve warfighter problems by leveraging labs, industry, academia

  • Upload
    others

  • View
    3

  • Download
    0

Embed Size (px)

Citation preview

PIA & Lab Collaboration Event5 December 2018

Voting Results

Team Color # of Votes

Black 3

Green 7

Orange 7

Blue 9

Pink 3

Purple 11

TEAM BLACK, “ITwerx”

PIA & Lab Plan Overview: Create and maintain a central hub of 1) the PIs’

capabilities/responsibilities, 2) the federal lab’s existing capabilities and existing projects, 3)

government’s needs, 4) innovation events and 5) summary of completed outcomes/deliverables – in

order to integrate Needs with Capabilities and streamline processes. This serves as a one-stop shop

to bring partners and solutions together.

Technology/Methodology Used: Use existing Software package(s) to link/integrate existing data,

update, and send notifications. Software is enabled open architecture managed by a single federal

Network Administrator. Include automation feature to capture and add new information.

Incentivization: Incentivize productive relationships, fast track innovative outcomes, and reap

economic incentives. Reduce redundancies and risks.

Implementation Plan: The central authority to oversee this is the DOC/NIST Tech Transfer Office.

Include as part of DOC/NIST’s responsibility to promote technology transfer/commercialization. Add

this tool as part of a PM’s program management plan. Announce to non-federal stakeholders.

Team Green, Idea #1—Communication & IP

PIA & Lab Plan Overview:

Gamified Social Collaboration; Forum Leader

Technology/Methodology Used:

Wiki-based database of researchers and projects

Incentivization:

If you’re not searchable and discoverable, you are irrelevant

IP protection; percentage of royalties or contract award to mitigate fear of failure

Implementation Plan:

Pinterest of Technology

Team Green, Idea #2 Communications

PIA & Lab Plan Overview:

Central Repository of Requirements (Gov Driven) and Technologies and PIAs

Use existing platforms to correlate and advocate requirements, solutions, and gaps

Technology/Methodology Used:

Vulcan Baseline

(Current solution lacks unclassified requirements database)

AI-enabled to tailor search

Knowledge discovery

Incentivization:

PIAs—Recognition, Funding, Relevance

Requirements Generators—Better, Faster, Cheaper, More Novel

Solution Developers--Relationships

Implementation Plan:

Education (Acquisition Workforce)

Spiffy Tech Rollout

Team Green, Idea #3—Margaritas for Enhanced

Collaboration

PIA & Lab Plan Overview:

Technology/Methodology Used:

Incentivization:

Implementation Plan:

Team Green, Idea #4—SecurityPIA & Lab Plan Overview:

Don’t Overclassify

--Use words with context and common understanding

Technology/Methodology Used:

Trust that industry is likely ahead of government in the technology domain

--Up to GOV to inform the application and use case

KPP’s can be unclassified—talk to tech rather than mission or application

Incentivization:

Stress Balls

Increases participation non-traditional research and solution providers

Novel Solutions

Implementation Plan:

Suck it up

Team Orange, Idea #1

PIA & Lab Plan Overview:

The Orange Team proposes to solve warfighter problems by leveraging labs, industry, academia and

SBIRs to identify or create solutions that will be commercialized and sold back to the DoD.

Participation will be incentivized in the innovation space by leveraging multiple rewards including

monetary prizes, potential for technology licensing/patents and OTAs for follow-on funding for

successful prototypes. Orange team uses Google Search enabled web technology to foster

communication across a broad range of community sectors including academia, industry and

independent innovators.

Technology/Methodology Used:

Discover ERDC – expanded to enable access by non-DoD partners

FLC-Business – this website would be expanded to create a PIA specific focus as a repository to

collect information about collaborative events and projects for sharing across the broad community

of innovators. Used to launch a question to the community, request tool access/development or

search for innovation information.

Team Orange, Idea #1

Incentivization: Collaboration will be encouraged through the following constructs:

Monetary prizes – publishing grants; research grants; cash prizes; SBIR funding

Patents/licensing – joint DoD/inventor patents and licensing; potential for profit sharing/financial

renumeration for successful capabilities

OTA or other contract

IN-Q-TEL/VC engagement

Identification of program office to transition capability to commercial spaces

Implementation Plan:

503C builds a marketing plan based on a knowledge mapping of the problem space. Invite SMEs

from industry labs, academia, and SBIRs to a technology sprint to examine the parameters of the

challenge and identify potential concepts for solutions. Orange Team will select the minimum viable

product to prove out the concept. The appropriate program office will be selected to represent this

project and provide outcome metrics to the innovation community.

The resulting capability will undergo testing and evaluation by the warfighter community to validate

utility. The participating organization will be provided support to identify intellectual property and

determine appropriate licensing for capability use. The DoD will assist in the commercialization/

transition of the product offering. DoD organizations can apply this capability as dictated by mission.

Team Orange, Idea #1

PIA & Lab Plan Overview:

The Orange Team proposes to solve warfighter problems by leveraging labs, industry, academia and

SBIRs to identify or create solutions that will be commercialized and sold back to the DoD.

Participation will be incentivized in the innovation space by leveraging multiple rewards including

monetary prizes, potential for technology licensing/patents and OTAs for follow-on funding for

successful prototypes. Orange team uses Google Search enabled web technology to foster

communication across a broad range of community sectors including academia, industry and

independent innovators.

Technology/Methodology Used:

Discover ERDC – expanded to enable access by non-DoD partners

FLC-Business – this website would be expanded to create a PIA specific focus as a repository to

collect information about collaborative events and projects for sharing across the broad community

of innovators. Used to launch a question to the community, request tool access/development or

search for innovation information.

Team Orange, Idea #1

Incentivization: Collaboration will be encouraged through the following constructs:

Monetary prizes – publishing grants; research grants; cash prizes; SBIR funding

Patents/licensing – joint DoD/inventor patents and licensing; potential for profit sharing/financial

renumeration for successful capabilities

OTA or other contract

IN-Q-TEL/VC engagement

Identification of program office to transition capability to commercial spaces

Implementation Plan:

503C builds a marketing plan based on a knowledge mapping of the problem space. Invite SMEs

from industry labs, academia, and SBIRs to a technology sprint to examine the parameters of the

challenge and identify potential concepts for solutions. Orange Team will select the minimum viable

product to prove out the concept. The appropriate program office will be selected to represent this

project and provide outcome metrics to the innovation community.

The resulting capability will undergo testing and evaluation by the warfighter community to validate

utility. The participating organization will be provided support to identify intellectual property and

determine appropriate licensing for capability use. The DoD will assist in the commercialization/

transition of the product offering. DoD organizations can apply this capability as dictated by mission.

Team Blue Problem Statement

PROBLEM: Organizations have failed to connect ideas to practice at a meaningful pace.

PURPOSE: Collide and capitalize.

OBJECTIVES:

Kitchen Collaboration

Knowledge Management

Identifying overlapping niches

KITCHEN COLLABORATION

Technology/Methodology Used: Place the following in

PIAs’ kitchens: Generic webcams, facebook portals,

google hangout, VTCs in order to increase Casual

Collisions.

Incentivization: No barrier to communication,

convenience, cheap

Implementation Plan: First, connect small groups; then,

connect larger groups.

KNOWLEDGE MANAGEMENT AND INFORMATION SHARING

Technology/Methodology Used:

- Crowd source artifact repository; word archival, Sharepoint

-Word cloud to connect people (e.g.) Elastic Search / Kibana

-Collect structured data about best practices / lessons learned (e.g.) Survey Monkey

-Web based, secure

-Spigit to rapidly separate ideas worthy of investment from immature ideas

Incentivization: Timely, actionable, relevant information available to the community of

interest.

Implementation Plan: Demonstrate to the community of interest the value of archived

information.

LEVERAGE COMMUNITY OF INTEREST / PRACTICE ECOSYSTEM

Technology/Methodology Used: Self subscribe to identifying core competencies to show

overlap. Create a Community of Practice complete with professional forums, journals,

periodicals, recognition, membership, and accreditation. Slack to create areas of interests /

core competencies.

Incentivization: Create a standards based Community of Practice across PIAs.

Implementation Plan: Stand up a Slack instance across PIAs and the Government (USGA);

define Slack channels to share information on core competencies, events. Macro Ven

Diagram to illustrate core competencies.

Team Pink, Idea #22#22 limited link/comm with gov labs/univ labs/PIAs and what tech exists

PIA & Lab Plan Overview:

• Educate senior leadership on what a PIA is, how to use

a PIA, and the benefits of a PIA

• Synchronize messaging across PIAs

Technology/Methodology Used:

• Technology/Methodology Used:• Visiting conferences/conventions (AFA, AUSA, SOFIC, etc)• Connection to OSD• Website• LinkedIn Group• Vulcan• APAN• FLC-Business

Incentivization:

• Dedicated funding for PIA activities• Flexible funding cycle to allow responsiveness• Flexible color of money

Implementation Plan:

• Create working group for PIAs to synchronize messaging

• Create doc with language to discuss

definition/benefit/outcome for Gov labs/PIAs to utilize with

leadership

• Create map of PIA ecosystem, including defining expertise

of each

• White paper to leadership describing basics of PIAs: what

they are, how to use them, importance, who to contact

• Proliferate awareness through OSTP leadership

Partnership Intermediaries

• Authorizes contracts/MoUs for partnership intermediaries

• Authorizes funding out of funds available for support of the technology transfer function

• Partnership Intermediary: • An agency of a State or local government, or a nonprofit entity that

assists, counsels, advises, evaluates, or otherwise cooperates with small business firms or institutions of higher education, that need or can make demonstrably productive use of technology-related assistance from a Federal laboratory.

• To provide services for the Federal laboratory that increase the likelihood of success in the conduct of cooperative or joint activities of such Federal laboratory.

http://globals.federallabs.org/pdf/2008/Partnerships_Gonsalves.pdf

Team Purple, Lab/PIA Ecosystem Reference Page/Database

PIA & Lab Plan Overview:

• Overview of capabilities for each PIA, organized by technology areas, SMEs

• Provides visitors with information to base decisions on and how to get started

• A place to socialize top areas/problems of interest

Technology/Methodology Used:

• PIA “Marketplace” strategy

• OSD Validation of PIA capabilities

Incentivization:

• Ability to leverage & partner with others

• Central repository for attracting industry and customer involvement

• Improve the performance of all PIAs because they are working together

Implementation Plan:

1. Establish what proven, qualified capabilities of the PIAs are

2. Obtain OSD & Lab buy-in via AFSB & others

3. Establish a working group to develop requirements