Emerging Components Conference Series: Perspectives and Planning Workshop

1
Emerging Components Conference Series
Perspectives and Planning Workshop

• Emerging Technology Subcommittee and
• Small Business Administration
• June 26, 2003
• 409 Third ST SW
• Washington, DC
• http//www.componenttechnology.org

2
Welcome and Logistics

• Richard Coffee, SBA, Components Subcommittee
• Good Morning!
• Restrooms, Evacuation Plan, Lunch, Notes, Flip
  Chart, etc.
• Senior SBA Officials Remarks.

3
Session 1

• Brand Niemann, Chair, Web Services WG, Emerging
  Technology Subcommittee
• 1. Agenda
• 2. Purpose
• 3. Key Question
• 4. Schematic Process Diagram
• 5. CIO Council Architecture Infrastructure
  Committee
• 6. AIC Components Subcommittee
• 7. XML Web Services Working Group
• 8. E-Forms for E-Gov Pilot
• 9. Business Cases Using Pilots
• 10. Collaboration Communities for Software
  Components
• 11. Component Registry Repository Template and
  Examples
• 12. Preview of Upcoming Pilot Workshop.
• 13. Brief Remarks Before Discussion

4
1. Agenda

• 830 AM Welcome and Logistics
• Richard Coffee, SBA, Components Subcommittee.
• 845 AM Session 1. Component Needs Context and
  Framing Principles for Coordinated Action
• Brand Niemann, Chair, Web Services WG, Emerging
  Technology Subcommittee.
• 1030 AM Break
• 1045 AM Session 2. Aligning with Component
  Needs Exploration of Strategic Opportunities for
  Small Business Entrepreneurs
• Tony Stanco, Director, Cyberspace Policy
  Institute, GWU.
• 1145 AM Session 3. Who is Here? Who is
  Missing? Next Steps
• Susan Turnbull, Chair, Universal Access WG,
  Emerging Technology Subcommittee.
• 1230 PM Lunch on your own. Room available for
  networking until 2 PM.

5
2. Purpose

• To Explore the Potential and Realities of
  Accelerating the Emergence of Components Needed
  for Federal Enterprise Development Tapping the
  Multiplicative Benefits from Small Business
  Innovation Research (SBIR) Aligned with Federal
  Enterprise Architecture (FEA) Component Needs.

6
3. Key Question

• How can we organize around proven catalytic
  programs like the SBIR to stimulate incubator and
  marketplace mechanisms needed for rapid and
  responsive federal enterprise components
  development? How can we communicate this
  potential beginning with the SBAs 50th
  Anniversary National Entrepreneurial Conference
  Expo 2003 on Sept. 17-19?

7
4. Schematic Process Diagram
Collaboration Communities
CIO Councils Architecture Infrastructure Commit
tee (AIC) Federal Enterprise Architecture (FEA)
Small Businesses Industry Advisory
Council Agencies (SBIR) E-Gov Initiatives NASCIO T
echnology Associations Venture Capitalists Etc.
(Who is missing?)
Pilots
1. XML Data Model Registry 2. XML E-Forms 3.
XML Database 4. XML Collaboration Network 5. Etc.
BCOS
XML and Component Repository
XML Documents UBR Templates Topic Maps Semantic
Web (RDF) GIDS, etc.
BCOS Business Compliance One-Stop E-Gov
Initiative
A Component is a self-contained business process
or service with predefined functionality that may
be exposed through a business or technology
interface.
UBR UDDI Business Registry UDDI Universal
Description, Discovery, and Integration
8
5. CIO Council Architecture Infrastructure
Committee

• Leadership
• Mark Forman, OMB CIO and CIOC Chair
• E-Gov 2003 Conference, June 11th Reusable
  components are at the heart of the Federal
  Enterprise Architecture and E-Gov.
• John Gilligan, USAF CIO and AIC Chair
• E-Gov 2003 Conference, June 11th Standard
  components like E-Forms are coming out of the
  Emerging Technology Subcommittee for use across
  the government.
• Norman Lorentz, OMB CTO and AIC Advisor.

9
5. CIO Council Architecture Infrastructure
Committee

• Three Subcommittees
• Governance Policy guidance and assistance in
  design and implementation of the Enterprise
  Architecture discipline and practice.
• Robert Haycock, OMB, and John Przysucha, DOE.
• Components Identify, mature and facilitate
  use/reuse of Component-based Architectures.
• Reynolds Cahoon, CIO, NARA, and Robert Haycock,
  OMB.
• Emerging Technology Identify technologies with
  the potential to improve the value and quality of
  the FEA.
• Dawn Meyerriecks, CTO, DISA, and Mark Day, DCIO,
  EPA.
• Universal Access and XML Web Services Working
  Groups.

10
6. AIC Components Subcommittee

• Vision Interoperable, shareable, re-usable
  Enterprise Architecture Components that support
  the Presidents Management Agenda principles of
  customer-focused, results-oriented, and
  market-based Government.
• Mission Foster the identification, maturation,
  use, and re-use of Enterprise Architecture
  Components and component-based Enterprise
  Architectures in Government.
• Goal Facilitate cross-agency development and
  implementation of Enterprise Architecture
  Components.
• Definition An Enterprise Architecture component
  is defined as a self-contained business process
  or service with predefined functionality that may
  be exposed through a business or technology
  interface.

11
6. AIC Components Subcommittee

• FY 2003 Task Plan
• Task 1. Develop a Components-Based Architecture
  White Paper.
• Lead Harry Feely, Department of Education.
• Task 2. Develop a Components Registry/Repository
  Concept Paper.
• Lead Tim Bass, Air Force (consultant).
• Task 3. Develop a Solution Development Life Cycle
  (SDLC).
• Leads John McManus (NASA) and Daud Santosa
  (USPTO).
• Task 4. Develop and Market a Quick Win.
• Lead David Holyoke, SSA.

12
7. XML Web Services Working Group

• Users never know what they want
• until they see what they get

13
7. XML Web Services Working Group

• Pilots
• Purpose To populate the Government-wide
  Components Registry and Repository with reusable
  (interoperable) components from successful
  pilots.
• Basic Process
• (1) Version 1 Participant Interest Driven
  (see next slide).
• (2) Version 2 Requirements Driven (see next
  slide).
• Funding Options
• (1) Vendor Resources.
• (2) Agency Resources.
• (3) Combination of (1) and (2).

14
7. XML Web Services Working Group
Governance and Accreditation Process

• Version 1
• Anyone Purpose(1)
• Pilot(2)
• Operationalize(3)
• Institutionalize(4)

• Version 2
• General Call(5)
• Pilot(2)
• Publish Template(6)
• Evaluation(7)

• Must implement XML Web Service Standards and be
  accepted by the Collaboration Workshop and XML
  Web Services Working Group.
• Must demonstrate a working implementation of the
  standards (e.g. W3C).
• AIC, Agency, E-Gov Initiative, etc. offers to try
  it.
• AIC, Agency, E-Gov Initiative, etc. offers to
  host it.
• AIC, Agency, E-Gov Initiative, etc. requests it.
• Vendor(s) publish the template and demonstrate a
  working implementation.
• AIC, Agency, E-Gov Initiative, etc. evaluate it
  for their purposes.

15
7. XML Web Services Working Group
Basic Working Implementation of the Standards
WSDL Document

• 1. Client queries registry to locate service.
• 2. Registry refers client to WSDL document.
• 3. Client accesses WSDL document.
• 4. WSDL provides data to interact with Web
  service.
• 5. Client sends SOAP-message request.
• 6. Web service returns SOAP-message response.

UDDI Registry
2
3
1
4
5
Client
Web Service
6
16
7. XML Web Services Working Group
The Basic Standards

• Acronyms
• UDDI
• WSDL
• SOAP
• HTTP, SMTP, FTP
• Programming (DOM, SAX)
• Schema (DTD, XSD)
• XML

• Practical Examples
• Phone Book
• Contract
• Envelope
• Mailperson
• Speech
• Vocabulary
• Alphabet

17
8. E-Forms for E-Gov Pilot

• Sub-Teams
• Accessibility
• Business Case
• Client Specifications
• Fixed Content Behavior
• Form Selection (six selected)
• Presentation
• Records-Keeping
• Schema (draft paper)
• Security (draft paper)
• Services
• See new Web Site and ListServ
• http//www.fenestra.com/eforms
• Recent news story
• http//www.gcn.com/vol1_no1/daily-updates/22014-1.
  html

18
9. Business Cases Using Pilots

• Business Compliance One Stop Revised Business
  Case, April 20, 2003
• Regulatory Reform is just as important as tax
  reform for strengthening the economy
• Three Proposed Strategies for Reducing Regulatory
  Burden
• Make SBA the Advocate for Regulatory Burden
  Reduction.
• Implement E-Forms for Major Industries.
• Implement Compliance Assistance Tools.
• Common Elements of Each Alternative
• E-Forms (like an Intuits Turbo Tax).
• Customer Agent (Trusted Third Parties).
• Partnership.

Richard J. Varn, President, RJV Consulting, New
Business Models to Advance Public/Private
Collaboration, Des Moines, Iowa.
19
9. Business Cases Using Pilots

• Business Compliance One Stop Revised Business
  Case, April 20, 2003
• Four Pilot Projects Recommended for the Business
  Compliance One Stop Revised Business Case
• XML Collaborator (Blue Oxide).
• E-Forms for e-Gov The Use of XML Standards-based
  Applications (Fenestra).
• Collaboration and CoSourcing Designing
  Intergovernmental Services and Sharable
  Components (CollabNet).
• XML Data Exchange Across Multiple Levels of
  Government Using Native XML Databases (contains
  UDDI Registry) (Software AG).

Richard J. Varn, President, RJV Consulting, New
Business Models to Advance Public/Private
Collaboration, Des Moines, Iowa.
20
10. Collaboration Communities for Software
Components

• CollabNet
• Roots in the Apache Software Foundation and Open
  Source.
• SourceCast Enterprise collaboration platform
  targeting software development deployment.
• Integrates Structured Exchange (XML), Process
  Collaboration, and Free-form Interaction.
• Value proposition to the FEA Benefits of Open
  Source Process.
• Pilots
• DISA (Dawn Meyerriecks)
• About 100 participants collaborating on about 30
  projects to produce Horizontal Fusion across
  the organization.
• Slated to become the DOD Registry and the DHS
  Registry?!
• Canadian Government Pilot (Joseph Potvin)
• Users never know what they want .. until they
  can see what they will get.
• Partnered with the XML Collaborator and Assisting
  the Move of Commerces GIDS (Fenestra) into the
  Open Source Process.

21
11. Component Registry Repository Template
Examples

• 1. Company background and capabilities including
  participation in standards organizations. Include
  URL(s) to Web site (s). This could be in the
  format of the UDDI Business Registry (UBR) White
  Pages (general information about a companys
  name, address, contact information and
  identifiers), Yellow Pages (divides the company
  into various categories based on the products or
  services the company offers), and Green Pages
  (technical information about a companys
  products, services and Web services).
• 2. E-Gov pilot architecture (where are the
  re-usable components?, where are the XML Web
  Services?, where are the possibilities for
  interoperability with other vendors in Phase 2?,
  etc.). Include URL(s) to diagrams.
• 3. Demonstration of the pilot. Narrative of what
  the pilot shows. Include URL(s) to instructions
  and functioning Web services.
• 4. Supporting documentation. Include URLs to XML
  artifacts (forms, XML Schema, WSDL, etc.) and
  other information to explain them.
• 5. Lessons learned and suggestions (optional).

22
11. Component Registry Repository Template
Examples

• June 2nd Workshop at White House Conference
  Center
• 1. Open GIS Consortium (Geospatial One-Stop E-Gov
  Portal)
• 2. Adobe (presented supplemental on June 17th)
• 3. Conclusive Technology (submitted supplemental
  for today)
• 4. Digital Evolution
• 5. MetaMatrix
• 6. Microsoft
• 7. Object Builders
• 8. Sand Hill Systems (presented supplemental on
  June 17th)
• Additional Vendors Participating
• Soltex
• SeeBeyond
• ITM Associates
• Pure Edge (submitted for today)
• AmberPoint (submitted for today)
• Cardiff (may participate based on June 12th
  discussion)
• Arbortext (may participate based on June 12th
  discussion)

23
11. Component Registry Repository Template
Examples

• June 2nd Workshop Lessons Learned
• The small businesses are honored to participate
  and the large vendors dont want to be left out
  so a more level playing field is created.
• Small businesses can relate how participation and
  partnering have benefited them (e.g. Fenestra,
  ObjectBuilders, Digital Evolution, etc.).
• Small businesses need to see a way to attract
  funding for the near-term, mid-term, and
  long-term for E-Gov business to be viewed as a
  viable, and sustainable activity.
• The business community needs a marketplace forum
  in which to promote their open standards-based
  components and attract government innovation
  research and venture capital funding.

24
12. Brief Remarks Before Discussion

• What are Components? - Daud Santosa, US PTO,
  Components Subcommittee.
• What are Pilots? - Rick Rogers, Fenestra, and
  Lead, E-Forms for E-Gov pilot.
• What are Business Cases Using Pilots? - Richard
  Varn, CTO, SBA Business Compliance One-stop.
• What are Collaboration Communities for Software
  Components? - Brian Behlendorf, Founder, Apache
  Software Foundation.
• What is the Component Registry Repository
  Template? Demonstrations as Time Permits.
• What is the Potential of Semantic Technologies
  for E-Gov? Preview of Upcoming Pilot Workshop.

25
12. Brief Remarks Before Discussion

• What is the Component Registry Repository
  Template?
• Demonstrations as Time Permits
• AmberPoint (submitted for today).
• PureEdge (submitted for today).
• Conclusive Technology (submitted supplemental for
  today).
• What is the Potential of Semantic Technologies
  for E-Gov?
• Preview of Upcoming Pilot Workshop
• Accelerating eGOV Initiatives and Agency
  Partnering with the FEA-based Capabilities
  Manager, Ralph Hodgson, TopQuadrant.

26
Accelerating eGOV Initiatives and Agency
Partnering with the FEA-based Capabilities
Manager Overview

• The vision of Universal Access Requires
  Cross-Agency Collaboration.
• Assisting Partnering through Solution Envisioning
  and Semantic Models
• Decentralized but Connectable a Government
  Core Ontology (e.g. a kind of Dublin Core for
  Agencies) with participation from the W3C
  Semantic Web Community. E.g., RDFS - Resource
  Description Framework Schema.
• The Semantic FEA Capabilities and Partnership
  Manager Pilot Project and Workshop.

27
Accelerating eGOV Initiatives and Agency
Partnering with the FEA-based Capabilities
Manager Modeling
leads
supports
develops
Agency
PresidentsInitiative
Partnership
Business Case
for
has
participates in
runs
Program
Business Area
has
has
Project
Line of Business
has
delivers
realized as
needs
Capability
Service
Web Service
uses
Component
considers
supports
Capability Case
28
Accelerating eGOV Initiatives and Agency
Partnering with the FEA-based Capabilities
Manager The Power of RDFS
Accelerating eGOV Initiatives and Agency
Partnering with the FEA-based Capabilities
Manager The Power of RDFS
eGOV realized as component
29
Accelerating eGOV Initiatives and Agency
Partnering with the FEA-based Capabilities
Manager Conceptual Architecture
30
Accelerating eGOV Initiatives and Agency
Partnering with the FEA-based Capabilities
Manager An exploratory sketch using a native
RDF DB The FEA Partnership Advisor
Built using RDF Gateway from Intellidimension,
Inc., acknowledgements to Geoff Chappell.
31
Break

• 15 minutes

32
Session 2

• Aligning with Component Needs Exploration of
  Strategic Opportunities for Small Business
  Entrepreneurs
• Tony Stanco, Director, Cyberspace Policy
  Institute, GWU
• Senior SBA official.
• Venture Capital representatives.
• Technology Association and Council
  representatives.

33
Session 2

• Aligning with Component Needs Exploration of
  Strategic Opportunities for Small Business
  Entrepreneurs
• SBAs 50th Anniversary, National Entrepreneurial
  Conference and Expo 2003, Washington Hilton
  Towers, September 17-19, 2003, http//www.sba.gov/
  50
• Possible Panel (CIO Council, SBA/SBIR, VC/Tech
  Community, BCOS Vendors, etc.)
• Vendors Participate in Trade Show
• Ten City Regional Mini-Town Hall Sessions
• Other?

34
SBIR/STTR 3-Phase Program

• PHASE I
• Feasibility Study
• 100K and 6-month (SBIR)
• or 12-month (STTR) Award

• PHASE II
• Full Research/RD
• 750K and 2-year Award
• (SBIR/STTR)

• PHASE III
• Commercialization Stage
• Use of non-SBIR/STTR Funds

35
Top 10 Reasons to Seek SBIR / STTR Funding
Opportunities

• 10. Over 1.6 Billion available.
• 9. NOT A LOAN - no repayment.
• 8. Provides recognition, verification and
  visibility.
• 7. Potential leveraging tool to attract venture
  capital/other sources of .
• 6. Fosters partnerships (e.g., large
  corporations, academia).
• 5. Creates jobs and stimulates local, state and
  national economies.
• 4. Provides seed money to fund high risk
  projects.
• 3. Intellectual property rights are normally
  retained by the small business.
• 2. Small business concerns are recognized as a
  unique national resource of technological
  innovation.
• 1. To make economic and societal contributions to
  America.

36
Who Participates in SBIR?

• Firms are typically small and new to the program.
• About 1/3 are first-time Phase I awardees.
• Small hi-tech firms from across the country.

37
The SBIR Opportunity

• Each Federal agency with extramural RD budget
  over 100 million must expend not less than 2.5
  each fiscal year on SBIT or STTR. 15 U.S.C.
  Section 638(f).
• Phase I determine the scientific and technical
  merit and feasibility of ideas that appear to
  have commercial potential, submitted pursuant to
  SBIR program 15 U.S.C. Section 638(e)(4)(A).

38
The SBIR Opportunity

• Phase II further develop proposals which meet
  Program needs
• Awards made on scientific and technical merit and
  feasibility of proposals, considering commercial
  potential 15 U.S.C. Section 638(e)(4)(B).
• Phase III commercial applications of
  SBIR-funded RD funded by non-Federal sources of
  capital, or for products or services intended for
  use by the Federal Government, by follow-on
  non-SBIR Federal funding awards 15 U.S.C. Section
  638(e)(4)(C).

39
The SBIR Opportunity

• There is tremendous potential to use the SBIR and
  STTR programs to achieve the purposes of the
  e-Government Act.
• Funds are appropriated annually already.
• Only needs coordination by CIO Council to fund
  objectives outlines by the Governance, Component
  Technology and Emerging Technology Sub-committees.

40
The SBIR Opportunity

• If CIO Council communicates and coordinate
  e-Government needs to agencies with SBIR budgets,
  agencies can add value and achieve CIO Council
  objectives without new appropriations from
  Congress.
• SBA can participate to disseminate information on
  the CIO Council objectives for citizen-centric
  government and the funding opportunities
  available from the coordinated SBIR programs,
  with simplified procedures to participate.

41
The SBIR Opportunity

• Venture Capitalists can then be involved in Phase
  III, because the e-Government needs have been
  identified by the CIO Council in the coordination
  and communication of the streamlined program.
• This program can give extraordinary opportunity
  to small business throughout the country to
  participate in planning and implementing the
  e-Government infrastructure for the Federal
  government.

42
The SBIR Opportunity

• Also, the Federal e-Government infrastructure
  created will be reusable by state/local and
  international governments.
• eCommerce and e-Health programs around the world
  could also benefit from the products created.
• These huge infrastructure projects will attract
  Venture Capitalists in Phase III, as long as the
  Federal government coordinates activities in
  Phase I with the appropriate agencies.

43
The SBIR Opportunity

• The SBIR Funding program can be communicated by
  the CIO Council to the agencies, technology
  companies, Venture Capitalists, non-profit
  associations, state/local CIO, and other
  interested communities through the Component
  Technology conference series in Washington.
• The SBA can further disseminate the program to
  small business around the country through its
  existing network of SBIR workshops and other
  resources for small business.

44
Session 3

• Who is Here? Who is Missing? Next Steps
• Susan Turnbull, Chair, Universal Access WG,
  Emerging Technology Subcommittee.
• Introductions.
• Actions on Flip Chart Items.