CANES SOA Integration Acquisition Strategy

1
CANES SOA Integration Acquisition Strategy

• San Diego Chapter

2
Participants

• Jim Lasswell, INDUS Technology
• NDIA SD Small Business Chair and Study Lead
• Jim Abbott, SAIC
• Stacey Anfuso, Referentia
• Susan Burrows, SSC San Diego
• Bob Bush, Barling Bay
• Glen Catania, Forward Slope
• Mike Fortier, FGM
• Frank Hewitt, intelliSolutions

• Laura Hooker, SPAWAR
• Dwayne Junker, Epsilon Systems
• Terry McKearney, The Ranger Group
• Gerry Nifontoff, SAIC
• Terry Simpson, SSC, Charleston
• Ken Slaght, GDIT
• Keith Sutton, Syzygy
• Frank Unetic, Teleinc
• Becky Vincent, Vincent Enterprises

3
Charter

• Provide industry perspective on contracting
  strategy for CANES SOA integration tasking
  involving small business procurement
• Develop recommended contracting strategy
• Include small business participation as prime
• Address the following
• Pros and cons of Small Business prime for SOA
  Integrator
• Conflict or avoidance of conflict of interest for
  prime and subcontractor
• Definition of Small Business, NAICS involved,
  size standards vis a vis type of work
• Technical and/or programmatic challenges
  including recommended scope of work

4
Integration Support Our Recommendation
Government issues series of multiple IDIQ awards
for integration services to teams of small
business primed contracts. Government (SSC) would
issue task orders for integration services/tasks
based on CANES development priorities.

• Allows for flexible, rapid tasking to vetted
  teams of vendors
• Allows government task as you learn, reducing
  risk
• Complicates governments management must manage
  large number of vendors working across spectrum
  of integration tasks

5
How We Got There
6
General Assumptions and Givens

• This will be an ACAT I program
• Government is responsible for governance,
  oversight, and management
• SSCs in combination would lead integration effort
• Would get the small business credit for
  integration contracts
• Significant role for small business
• Involved in both integration and application
  development
• Opportunity to prime
• Overall contracting strategy would be mix of
  vehicle types
• A-B-C approach to application and services
  procurement
• Hardware procurement will be through a large
  business vendor

Adopt, Buy, Create
7
Specific Assumptions We Made

• The integration takes identified could
  individually be done by a small business
• Some may be better done by specific boutique
  small businesses
• A single small business would not be able to
  manage the entire CANES SOA integration effort
• Integration effort can be done as a series of
  individual tasks

8
Integration Functions and SOA Acquisition Roles

• Standards development
• Evolving beyond NESI
• Determine and advise on
• Business Rules for Conformance
• Technical Requirements
• Interface Specification
• A, B. C procurement
• Analysis of proposed applications
• Compliance
• Functionality (?)
• Framework Evolution

• Functional Performance Verification and
  Validation
• IA and Compliance Evaluation
• Ensuring standards incorporated in COI
  applications
• ATO approval management
• Maintenance and operations of test bed
• Test, integration, and independent evaluation
• Delivery/installation
• Oversee shipboard testing and training
• Life Cycle and Logistics Support

9
Contracting for These

• Bin or align complimentary functions
• Can be best done by single company or mutually
  supporting team
• Develop appropriate contacting vehicles
• IDIQ contacts to teams
• Small businesses can prime
• Based on anticipated LOE
• SSC issues Task Orders to appropriate teams based
  on specific integration needs
• Variety of defend applications and services to be
  procured means, one size will not fit all in
  integration
• Single integration may take place in phases with
  multiple TOs to different teams

10
Contracting Issues Still To Be Considered

• NAICS
• Whats the right one for the integration task?
• Most likely
• 519130 Internet Publishing and Broadcasting and
  Web Search Portals - SB limit  500 persons
• 541330 Engineering Services (Military and
  Aerospace Equipment and Military Weapons) - SB
  limit 25M
• 541511 Custom Computer Programming Services- SB
  limit 23M
• 541512 Computer Systems Design Services- SB limit
  23M
• Role of specific government SB initiatives and
  programs
• Vet owned and SDVOSB
• 8(a) and HUB Zone
• Mentor/Protégé
• Women owned small business

11
Next Steps

• Further define integration tasks in terms of
• Scope and unit cost
• Linkages between
• Analyze ability of small businesses to support
  these tasks
• Based on NAICS or other government criteria
• More comprehensive report on these findings

12
Back Ups
13
General Acquisition Strategy

• Governance, Management, and Oversight
• PEO C4I, SPAWAR, PMW 160 in charge
• Architecture definition and standards
• CCB, EIII, and other boards
• Contract support

Series of individual procurements in response to
programmatic spirals and emerging operational
requirements
Ongoing, long term contractor support across wide
range of technical skills

• Individual Application and Services Procurement
• COI, services development in support of
  warfighter needs (Mission Threads)
• Compliant with SOA
• Includes both legacy and new applications
• Includes hardware

• Integration Support
• Range of integration functions to support
  architecture, services and application
  development
• Standards development
• Application assessment
• Test and validation
• Fleet introduction
• See detailed list

14

• SSC performs role as integrator as Echelon III
  command
• Manages overall integration effort though
  contacts with teams
• Including SOA evolution, best practices,
  integration with DISA efforts, requirements

• SETA or special support directly to SSC
• Admin
• Special studies
• ABC determination

• Series of IDIQ vehicles provides vetted teams to
  perform integration tasks as required by CANES
  development
• Integration functions binned or aligned by
  vehicle to provide government across to mutually
  supporting integration tasks
• Because of anticipated LOE in TOs, SB can be
  primes for each

• Governance, Management, Oversight
• PEO C4I, SPAWAR

Task Orders to teams for specific integration
efforts directly related to application/service
integration into CANES
Contracts for applications send services between
PEO/PMW and companies writing code
Individual integration tasks
Integration teams work with Application/service
developers
OCI restrictions prevent integration supporters
from development work
Individual application and service development
Technical Liaison
Contractual Relationship
15
The Tough Questions

• What will the SOA architecture look like?
• NESI, CALS?
• How will application development be managed?
• COI formation, leadership
• CJCS 8320.02 series?
• What core services will be utilized and when in
  the CANES evolution?
• NCES role?
• Whos responsible for fleet introduction of
  evolving capability
• Installation, training
• Role of integrator(s), application developers
• Will PMW160 award and manage for all applications
  integrating into the SOA
• What about PEO IWS, NAVAIR IT?

Others?