Transcript GDAIS External PowerPoint template

Open Architecture & DHS
Mark Magee
Vice President, Homeland Security Initiatives
November 9, 2011
0
Open Architecture……Moving Into DHS

TSA Security Technology Integrated Program (STIP):
• New interfaces with Transportation Security Equipment are based
upon an Open Data Model
• STIP Enterprise interfaces utilizing open standards

CBP Border Security Programs: Customer has stated
a desire for open architecture-based systems
CBP Border Security
1
TSA STIP Phase II Development
Open Architecture (OA)

A system with an open architecture:
o Allows for easy incorporation of new capabilities
& technologies without significant architecture
modifications over the life cycle
o Easy: ability to add a new sensor, capability, etc., in a
matter of days or weeks rather than months or years
o Significant: fundamental architecture of the system –
including how components connect to each other – does
not require modification to add something new.
o Contains no system or interface-level
proprietary solutions
Standards
Interfaces
OA
Modules
o Uses modular software components
o Uses published interfaces & standards to
promote competition – both up-front & over the
life cycle of the system – to drive down costs &
schedule
Open Architecture’s Value Proposition: Better, Faster, Cheaper
2
DHS Should Insist On:
OA Characteristics
Decoupled Hardware & Software
HW & SW can be changed
independently of each other
Interface Definitions
Hallmark of an open system –
interfaces are clearly defined
Open Data Model
Data contents & descriptions
defined & published in a model
Data Rights
Buyers of the system have the
rights necessary to maintain the
system
Open Business Model
Unlocks the full potential of OA –
facilitates introduction of 3rd party
capabilities
3
Open Business Model
•Unlocks full potential of open architecture. An open business model:
•Allows competition: Costs & ideas for capability improvement
•Gives buyers greater flexibility
Case Study: Open Business Model for Navy’s LCS
•Data architecture & interfaces open to industry via web
Created an Open Data Model & gave it to the customer
•Other companies invited to participate
Did not design the system so that only GD content would work
•Used GDLCS.com & solicited input from subcontractors & other technology providers
130 RFIs >> 118 RFI responses >> 80 RFQs >> 50 proposals
•Helped to drive down cost through competition
Upwards of 70% savings for specific sub-system components
•Facilitated rapid integration of non-GD capabilities
New non-GD missile system integrated within hours in lab; within 6 weeks on ship >> not
months or years
•Made maximum use of existing solutions to minimize risk
90+% Hardware Reuse (repackaging only); 93% Software Reuse
Promoting Vendor Innovation Can Shift Costs from DHS to Industry
4
Other OA Items

Standards (the road to plug-n-play…..)
• DHS’ role in designating government or industry-defined &
controlled standards

Costs
• Perception of open systems costing more
• Savings of open systems are in standardization, reuse,
commonality, & tech insertion

Intellectual property still has a place – just not at
the interfaces
• Protecting IP is critical for 3rd party developers, particularly small
businesses
• Fosters innovation and competition
Open Architecture & Open Business Model: Way Forward for DHS
5