PEO C4I/IT Seminar Brief - CANES - Aug 08


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Brief Title is normally Arial 32 bold. Brief POC information block is Arial 18 bold. The distribution block should be edited to reflect the distribution category of your specific brief. The distribution statement may be deleted for internal PEO C4I briefs.
  • System Design and Development 2 contracting efforts: System Developer (SD) and NCES Core Services federation/integration (SOA) Full and open competition for SD: Award 2 contracts to provide SDD phase for FY09-10 Competitive down-select to a single SD for LRIP installs in FY11-12 Follow-on competition for FRP phase of Inc 1 (FY13-17) Extensive government/industry prototyping prior to program initiation to reduce technical risk, validate cost estimates Industry providing prototypes of highest risk areas as part of RFP responses SOA is an iterative contract based on NCES development Schedule Contract Award: 1QFY10 Preliminary Design Review (PDR) prior MS B Critical Design Review (CDR): 6 months after contract award LRIP: 4QFY11
  • PEO C4I/IT Seminar Brief - CANES - Aug 08

    1. 1. 23 April 2009 Jason Livingston Director, NCIIPT (SSC-LANT) 843.218.5409 [email_address] Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I) Consolidated Afloat Networks and Enterprise Services (CANES) Program and Acquisition Overview DISTRIBUTION STATEMENT D. Distribution authorized to the Department of Defense and U.S. DoD contractors only due to critical technology content November 2008. Other requests shall be referred to the PEO C4I and Space (Program Office PMW 160) or SPAWAR Office of Congressional and Public Affairs (SPAWAR 00P).
    2. 2. Agenda <ul><li>Program Overview and Status </li></ul><ul><li>Program Schedule </li></ul><ul><li>Program Contracting Strategy </li></ul><ul><li>ACS Overview </li></ul><ul><li>ACS Contracting Strategy </li></ul><ul><li>Seam Management </li></ul>Disclosure: Unfortunately, due the acquisition sensitive phase CANES is now it, questions will not be taken but can be submitted via email to the SSC-LANT contracts office.
    3. 3. Navy Mandate in PR09 <ul><ul><li>CANES concept and investment strategy validated by Navy, DoD leadership </li></ul></ul><ul><li>CANES Concept – OPNAV N6/DoN CIO, NNWC, and PEO C4I </li></ul><ul><li>CNO-directed approach to consolidate multiple afloat networks, provide </li></ul><ul><li>secure, reliable common hosting for multiple C4I applications (Dec 05) </li></ul><ul><ul><li>Technical and programmatic realignment of legacy </li></ul></ul><ul><ul><li>infrastructure and services-more efficient, additional capability </li></ul></ul><ul><ul><li>Fundamental change in C4I acquisition approach </li></ul></ul><ul><li>CANES POR (FY11 LRIP) </li></ul><ul><ul><li>Consolidated afloat network, providing </li></ul></ul><ul><ul><li>CCE, Afloat Core Services, CDS, and integrated </li></ul></ul><ul><ul><li>Voice, Video, and Data network infrastructure </li></ul></ul><ul><ul><li>Pre–MDAP/MAIS, projected ACAT 1D </li></ul></ul>CANES Migration (FY08-11) Prototype CCE & Afloat Core Services technologies – accelerate capability delivery, mitigate technical risks Existing Network POR Modifications to support early application migration LINCOLN SG and CPF MHQ/MOC in 09 Today: By FY11:
    4. 4. CANES Status Under New DoDI 5000.02 <ul><li>New DoDI 5000.2 signed 2 Dec 08 </li></ul><ul><li>CANES completed MDD review 14 Nov 08, ADM signed 12 Dec 08 </li></ul><ul><ul><li>Proceed to MS B in FY10 after completion of PDR and 2366b certification; MS A not necessary as CANES is network consolidation effort with no new technology development </li></ul></ul><ul><ul><li>CCE and ACS to be established as sub-programs at MS B </li></ul></ul><ul><ul><li>CCE RFP released following SPAWAR/PEO peer review </li></ul></ul><ul><ul><li>ACS RFP will be released upon DoD CIO review of Net-Ready KPP </li></ul></ul>
    5. 5. FY08 FY09 FY10 FY11 FY12 FY13 FY14 FY15 MDD MS B MS C LRIP FRP MS B MS C MDD SDD Overall Program Approach Increment 1: Subprogram 1A Common Computing Environment/Cross Domain Solution Capabilities and Technologies <ul><li>Voice, Video on SR and SCI enclaves </li></ul><ul><li>MAC1 for system critical services (Secret enclave only) </li></ul><ul><li>Satisfies NNWC Drop Count Reqmnts </li></ul><ul><li>Hosting Up To Near-Real Time Combat Support applications </li></ul><ul><li>Internal Shipboard Wireless – 50% coverage </li></ul>Platforms (151) <ul><li>CVN, LCC-19/20, LHA/D, CG, DDG, LSD, MHQ/MOC, SSN, SSBN/GN </li></ul><ul><li>CVN 78, LHA 7 initial SCN platforms </li></ul>Increment 2 Enhanced Network Capabilities and Technologies <ul><li>Voice on all enclaves </li></ul><ul><li>MAC1 for system critical services (Secret/SCI/UNCLAS enclave) </li></ul><ul><li>Will satisfy NNWC ORT Objective Requirements </li></ul><ul><li>Hosting up to Real Time Weapon-In-The-Loop Applications </li></ul><ul><li>HM&E Applications/Subsystems </li></ul><ul><li>Internal Shipboard Wireless – 100% coverage </li></ul>Platforms (275+) <ul><li>Increment 1 plus DDG1000, CGX, LCS, JCCX, LHA (R) MALS, LPD-17, JHSV, NECC, PC , MPA/Other Aircraft </li></ul>Increment 1: Subprogram 1B Afloat Core Services Capabilities and Technologies <ul><li>Build on existing ISNS Afloat Core Services delivering in 2009 </li></ul><ul><li>Incremental acquisition </li></ul><ul><li>Federate NCES Core Services to tactical user </li></ul>
    6. 6. Nov 06 - ISNS Inc 2 ADM (Pre-Acq Activities) Dec 07 – CANES: pre-MDAP/MAIS Jan 08 – Gate 3 Review w/ CNO/VCNO Aug 08 – CANES OSD FIG#1 Sep 08 – CANES OSD FIG#2 Oct 08 – AoA Completion / Acquisition OIPT Dec 08 – MDD ADM / CCE Draft RFP Nov 08 – Gate 4/5 Review / MDD w/ USD (AT&L) / ASD (NII)` Apr 09 – CCE RFP Released Jun 09 – ACS RFP Released Nov 09 – CCE Contract Award May 10 – MS B Program Status <ul><ul><li>CANES is meeting all program milestones </li></ul></ul><ul><ul><li>Integrator </li></ul></ul>Dec 09 – ACS Contract Award
    7. 7. CANES Program Summary Schedule
    8. 8. CANES Contract Strategy FY08 FY09 FY10 FY11 PCs & S/W Licenses procured using Navy and DoD enterprise contracts Afloat Core Services Afloat CS development: ISNS INCR 1 Mod 5 CS v1.0 CS v1.1 CANES ACS v1.0 MS C MS B Source Selection 4 mo CS RFP aligned to System Developer RFP. RFP Process 3 mo MDD Complete 1 mo 3 mo 6mo CCE System Developer 2 CCE System Developer 1 14 mo 2 mo LRIP Government Oversight 11 Dec 08 Release draft RFP, technical components of PR EDM Drop CA + 4 mo EDM Drop CA + 8 mo EDM Drop CA + 12 mo US TestX2 S Test X2 SIT 1 X2 OA X2 SRR Preliminary Design Review Final RFP Build Prop Prep 2 mo Vendor provided Allocated Baseline and Prototype Develop Solicitation Review 2 mo Government Oversight Developed Functional Baseline & SDS Develop Solicitation Draft RFP Source Selection Down-Select
    9. 9. Afloat Core Services (ACS) <ul><li>The ACS contract is decoupled from System Development contract </li></ul><ul><ul><li>Due to nature of SOA as an emergent concept and architecture within the DoD </li></ul></ul><ul><ul><li>Large number of PEO C4I and other COI applications and hardware interfaces that ACS is anticipated to support </li></ul></ul><ul><ul><li>Leverage lessons learned from the NCES SOA contract </li></ul></ul><ul><li>The Core Services (CS) are a component of the overall system architecture and fundamentally a system application/enhancement </li></ul><ul><ul><li>CS v1.0/1.1 provides an initial, technically mature core services stack </li></ul></ul><ul><ul><li>The Government ACS Trusted Agent will provide CS to the CCE developer for incorporation into the network </li></ul></ul><ul><li>The ACS contractors will be responsible for developing open standards compliant products and supporting the integration of those products into the CANES ACS stack </li></ul><ul><ul><li>Overall CANES network not dependent on ACS for delivery </li></ul></ul>
    10. 10. Services Layers <ul><ul><li>Service-oriented infrastructure results from applying the principles of service-orientation to the enterprise architecture pillar </li></ul></ul>
    11. 11. ACS Contracting Strategy <ul><li>The ACS contract will be released and managed from SSC Atlantic with daily interaction with the CANES PMO </li></ul><ul><li>The ACS contract will be an IDIQ MAC with up to five primes who will be responsible for 50% of the work performed </li></ul><ul><li>The contract activities will be broken out into the following areas </li></ul><ul><ul><li>Development and Application Integration </li></ul></ul><ul><ul><li>Fielding and Procurement </li></ul></ul><ul><ul><li>Sustainment </li></ul></ul><ul><li>The ACS RFP is currently planned to be released in June 09 with a contract award in Dec 09 </li></ul><ul><li>The seams between ACS and the CCE will be managed via strict government oversight and continuous engagement between the CANES SE, the CCE SD vendors, the ACS Trusted Agent, and the ACS vendors </li></ul>
    12. 12. What are we buying? <ul><ul><li>The Government will serve as the Lead Integrator </li></ul></ul>Integrate Core Services Procure Core Services Develop Core Services Establish multiple SOA/ESB RI sites Develop and provide SDKs Develop SOA Allocated Baseline Develop SOA Product Baseline - CI Specifications / CI Tree - Creation of Dependency Tree Develop SOA Product Specifications Develop SOA Unit Test Plans Support / Implement SOA Testing Process - Procure and provide testing tools Execute Information Assurance / Accreditation Requirements Productionize - Provide ILS - Create Load Plans and Procedures - Develop Training - Create documentation - Redundancy/backup Conduct Software Support Activity - Licenses / Maintenance - Version control - Trouble ticket tracking and resolution (IAVAs, STRs) - Help Desk <ul><li>Provide Configuration Management </li></ul><ul><li>Maintain CM of CIs </li></ul><ul><li>Support overall CANES CM </li></ul>Provide Systems Engineering / Software Engineering Process expertise / artifacts
    13. 13. Seam Management <ul><li>A governance board will be established within the CANES program office </li></ul><ul><li>An ACS-IPT will be formed </li></ul><ul><ul><li>Biweekly meetings to discuss engineering challenges and disseminate necessary information regarding CS v1.0 or CS v1.1 </li></ul></ul><ul><li>Reviews will be conducted regularly with both SD vendors </li></ul><ul><li>Online collaboration sites via the ACS Integrated Development Environment (IDE) will be established </li></ul><ul><ul><li>Each SD will have ability for daily interaction with the ACS Trusted Agent </li></ul></ul><ul><ul><li>Interaction and Collaboration are KEY to Seams Management </li></ul></ul>
    14. 14. Integrated Development Environment
    15. 15. Thank You <ul><ul><li>“ The CANES system achieves an open, agile, flexible and affordable network architecture that will move us forward. CANES embraces cross domain solutions that enable enhanced movement of data. It is a revolutionary change in our information technology infrastructure and it is absolutely vital for us to excel in 21st century warfare” </li></ul></ul><ul><ul><li>ADM Roughead’s CNO testimony to Senate Armed Services Committee on 2009 Budget Priorities </li></ul></ul><ul><ul><li>28 Feb 08 </li></ul></ul>