Presentation on theme: "Systems Engineering and Leveraging Commercial Applications at CERDEC"— Presentation transcript:
1 Systems Engineering and Leveraging Commercial Applications at CERDEC Mr. Gary Blohm Director, US Army RDECOM Communications Electronics Research, Development and Engineering Center12 March 2010
2 Panelist Introduction Forum ModeratorMr. Gary Blohm Director, Communications Electronic Research, Development and Engineering Center (CERDEC / RDECOM)Panelist Members Mr. Frank Apicella SES, U.S. Army Evaluation Center, US Army Test and Evaluation Command (ATEC) Mr. Doug Richardson PEO Special Reconnaissance, Surveillance and Exploitation Systems (US SOCOM) CAPT Harry (Smokey) Robinson Commanding Officer, Naval Air Warfare Center Training Systems Division (NAWCTSD) / NSA Orlando COL Craig Langhauser Director, Training and Technology Center (STTC) / RDECOM Ms. Maureen Weller U.S. Army Corps of Engineers, Dallas HQS COL Ken Wheeler Deputy Program Executive Officer (DPEO), Simulation, Training & Instrumentation’
3 Agenda DOD System Engineering Environment Top 5 Systems Engineering Issues in the Defense IndustryVehicular Integration for C4ISR/EW Interoperability (VICTORY)Increased use of Commercial Capabilities / Applications
4 DOD System Engineering Environment DOD is a complex engineering environmentStrong emphasis on System Engineering in the departmentSystem of Systems practices emergingInteroperability - interdependencies have never been strongerEngineering the product – engineering the interfacesSystems Engineering is defined in the DoD's Defense Acquisition Guidebook as an interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and total lifecycle balanced set of system, people, and process solutions that satisfy customer needs.
5 Top 5 Systems Engineering Issues in the Defense Industry Key Systems Engineering practices known to be effective are not consistently applied across all phases of the program life cycle.Insufficient Systems Engineering is applied early in the program life cycle, compromising the foundation for initial requirements and architecture development.Requirements are not always well-managed, including the effective translation from capabilities statements into executable requirements to achieve successful acquisition programs.Collaborative environments, including SE tools, are inadequate to effectively execute SE at the joint capability, System-of-Systems (SoS) and system levels.The quantity and quality of Systems Engineering expertise is insufficient to meet the demands of the government and the defense industry.
6 VICTORY Vehicular Integration for C4ISR/EW inTerOpeRabilitY Common Data Bus Ethernet NetworkGigabit Ethernet Switches with copper mediaHigh bandwidth connections within the vehicleDisplays w/custom presentation of informationTouch screens for user input (WMI)Processing and data storage capabilityCommon DisplaysGPS antenna and receiver for each classification levelCommon displays receive time & location / publish on networkAllows for fewer GPS devices to support C4ISR/EW systemsTime & Location DistributionMILS solution protects data in intra-vehicle networkTwo physically separated enclaves (secret and unclassified)Common display with trusted separation kernelRuns software at both classification levelsInformation AssuranceDevelop ArchitectureCreate Open StandardsPEO/PM Implementation
8 Revised Regulatory Policy DoDI 5000.02 Summary of changes:cEvolutionary Acquisition RevisedLife-Cycle Sustainment PlanUpdated DoD Earned Value Management Reporting ProceduresAccounting for Military EquipmentCost of EnergyContract Incentives StrategyApproval of Acquisition Strategy prior to Release of RFP (MS A & B)Detailed Systems Engineering Policyc
9 Enclosures to the DoDI 5000.02 (2008) }E1 References, continuedE2 ACAT and MDAE3 Statutory, Regulatory, and Contract Reporting Information and Milestone RequirementsE4 IT ConsiderationsE5 Integrated T&EE6 Resource EstimationE7 Human Systems IntegrationE8 Acquisition of ServicesE9 Program ManagementE10 MDA Program CertificationE11 Management of Defense Business SystemsE12 Systems EngineeringTablesUpdatednew
10 Encl 12, Systems Engineering (New) Systems Engineering Plan (SEP) required at each milestoneMDA is approval authority for the SEPPEOs must have lead systems engineer – oversees SE across PEOs portfolio; reviews SEPs; assesses performance of subordinate systems engineers with PEO and PMEvent-driven technical reviews required – with SMEs independent of program, unless waived by MDARequires PMs to employ modular open systems approach to design (MOSA)Spectrum Supportability determination requiredRequires Corrosion Prevention Control Plan for ACAT I programs at MS B and CRequires configuration management to establish and control product attributes and the technical baselineData Management Strategy (DMS) required to assess long-term technical data needs of the system – included in Acquisition StrategyESOH risk management required to be integrated with overall SE process; Programmatic ESOH Evaluation (PESHE) required of all programs regardless of ACATNEPA and EO (Environmental Effects Abroad of Major Federal Actions) analysis required of PM, approved by CAEAddresses PM support of Mishap Accident InvestigationsEncl 12 includes SE policy previously directed by AT&L memos, and in addition:SPECTRUM SUPPORTABILITY. For all electromagnetic spectrum-dependent systems, PMs shall comply with U.S. and host nation spectrum regulations. They shall submit written determinations to the DoD Component CIO or equivalent that the electromagnetic spectrum necessary to support the operation of the system during its expected life cycle is, or will be, available (DoD Directive , Reference
11 Open Standard = VICTORY When is a standard “Open” ?Vendor neutralVendor platform independentManaged by a standards bodyImplementable by multiple sourcesOpenly publishedPlatform LimitsComplexityWeightPowerSizeRadiosFBCB2CREWSensorsCrew CompartmentFlexibilityIf current trend continuesVICTORY BenefitsGovernment accepted standardsOpen competitive environmentMinimize integration costsAllows rapid introduction of new capabilitiesFacilitates technology transition11
12 RDECOM moving toward objective SE driven portfolio process Needs/Capabilities:ASAALT IBCT Pilot (PEO System Integration)PEOs/PMs: i.e. AbramsJCIDS: i.e. CIEDsS&T Initiatives/Thrusts: i.e. Fuel Reduction, Cluster Munitions BanOthers:12Functional Decomposition of SIDsTechnology Areas(TFTs)LethalityProtectionNetworksSensorsPower & EnergyMobility & LogisticsHuman Dimension & TrainingCrosswalkTechnologiesCrosswalkTechnologiesS&T Projects to Address SID’s(ATO-Rs and ATO-Ds)34Selection Criteria5FYXXS&TProgramswith identified System and Technical KPPsStep 1: Flow Needs/Capabilities into functional areasStep 2: Decompose the functions of effectsStep 3: Crosswalk technologies into functional areasStep 4: Define Technology Gaps (ATO-Rs) and Select System Level Projects (ATO-Ds)Step 5: Prepare S&T plan for SID area with associated KPPs at the system and technology area