Breakout Group Outbrief:Alternative Ops ConceptsSession 11cKevin B Kreitman, Session ChairGSAW 2002New Ops Concepts• Theme: Perspective shift from stovepiped systemsto user-centered networked assets.– Integration—multi-user, multi-asset– Automate processes– Evolve and Extend• Critical for new integrated and networked world:multinational cooperation, new militaryinteroperability needs (RMA, effects-basedoperations), civil cooperative efforts.Multi-user Multi-asset Integration• The technology exists now:– Multiple vendors of Enterprise Application Integration software:Message bus (XML or analog); workflow manager, transactionmonitor, integrated security/admin. Connect legacy systems via“adaptors” as needed. Change process flow with graphicalinterface.– Significant commercial base/success in methodology andtechnology maturity in recent years, including DoD applications inlogistics and information applications• Don’t have to “shut down” for block implementation.– Integration is incremental, based on needs, particular systems andprocesses.• Additional technologies are relevant to solve aspects ofproblems.– These include peer to peer technologies, and JINI.• Web Services standards emerging rapidly.Automation of ProcessesJeff Langston, The Aerospace Corporation onKnowledge-based systems for automation and decision support– Difficult to construct so they are complete and reliable.– Important to capture and preserve specialized knowledge– Result in faster and improved decisionmaking in dealing withcomplex data.Ron Cohen, Jet Propulsion Labs onAutomated satellite tasking– can be constructed to enable user intervention (joy-stick operation)or by default, to use multiple criteria effectively for determiningtarget collects.– Well-constructed software avoids violating satellite operationsconstraints.– Optimizes asset utilization, significant improvement over humans,ROI especially for sustained long-term missions.– Social and political barriers to transition are real. Experience withsystem resulted in gradual adoption and increasing use ofautomated operation.Evolve and Extend• Enterprise Application Integration technology designed tosupport incremental migration and evolution– Component/service based architecture using MOM– Accommodates legacy systems via adaptors to variable level ofgranularity without enforcing internal changes– Enables gradual, experience-based migration to full componentservices architecture with native interfaces.– Increases flexibility and agility of system for plug and playreplacement of services, parallel testing– Extensible to other similar systems, procured by other enclaves,via XML/messaging or adaptors.– Supports emerging, experience-modified conops with changes toworkflow.• Emerging Web Services and future approaches promise tobe even more agile and flexibleIssues• Security: Still a challenge, in any system.– Security challenges are different and multiple in componentservices systems.– Use lessons learned in industry.– Use university open applications to explore and test.• Why should contractors take the risk of changing theirmethod of delivery now to ensure “future interoperability?”– Risk may be that others do—who will get next contract?• Semantic compatibility of data, metadata:– Problem remains! Need users/ providers to work together tounderstand and reconcile.– Model clashes need to be resolved!– Advantage is that data dictionary need not be complete to startimplementing the architecture.“Features” and Observations• Standards: Open/Internet standards handle many issues.– Interface standards are critical• Dot-com crash may be a windfall: new talent forDoD/contractors– EAI systems (for instance) not “rocket science” programming; newtech, distributed systems is the way of thinking among recentlytrained tech people.• University satellite ground systems– currently being successfully implemented with these componentservices, distributed systems approaches.• Some “stealth” applications of these technologies– in new and emerging DoD related systems; and in some traditionalcontractor solutions.• Adopting commercial solution enables riding on commercialsupport/development– but it means acquiring and evolving on commercial model, nottraditional procurement, O&M terms and scheduleConclusions• Not a magic bullet—but a promising opportunitywith significant advantages. You still have to “doit right.”• Layering of architecture, and multipletechnologies enable some problems to bedecomposed and addressed at appropriate levels.• Political, turf, compatibility issues and differentconcepts of operation still exist, but may be easierto try out and modify with experience in agile,flexible