With a View Toward Enterprise

Written by Christian Sheehy

To date, a majority of DoD SOA applications are, at a conceptual level, based on actual implementation coming within each military service’s specific ERP software. USTRANSCOM proposes to bring implementation to the SOA application level, removing responsibility from each service or agency for enterprise- level operation and enabling each to concentrate on needs at the service- or agency-centric level without worry as to interoperability after the fact.

“As we look at better ways to invest in IT software to improve capabilities, most of the services have adopted an enterprise resource planning [ERP] method of doing business, using software vendors to help them achieve data commonality for better reliability through increased automation,” said Robert Osborn, deputy director for Distribution Portfolio Management, USTRANSCOM, Scott Air Force Base. “We at USTRANSCOM have to integrate the logistics software efforts of the services and agencies and the way we are doing that is through the use of a technical approach to SOA.”

“SOA WITH A TWIST”

USTRANSCOM’s CSV initiative uses a descriptive set of user interface requirements based upon an enterprise architecture that allows the command to understand the lift requirements of the warfighter, schedule lift against that and track it throughout the enterprise. Using a common Web-based portal run by USTRANSCOM, each of the services and agencies are able to maintain their unique architectures as they need to in support of their specific warfighting missions, while using the CSV to achieve interoperability.

“We are literally the integrator of the various software applications that are being pursued by the services and agencies, using our SOA with a twist,” said Osborn.

Classic SOA involves publishing goods and services that independent service branches and agencies can subscribe to or consume. In this form of SOA, service and agency architectures converge only at customer/provider points of need. With convergence limited to need, specific services similar to one another often get duplicated due to an overlap of needs for similar fixes. This leads to unnecessary excess in service and process delays throughout the entire life cycle management chain.

“In trying to deliver the most IT capability for the least DoD investment, our ‘SOA with a twist’ manages the SOA registry more closely by prescribing which services are available, hence eliminating the chance for duplication and freeing up time and money for investment in greater capability,” Osborn remarked.

Much of the past challenge with SOA has been defining and managing services. To clarify this view, the command is examining a cross section of all the services and agencies to get a better look at how each is investing. “By understanding each service’s investment strategy for logistics acquisition, USTRANSCOM is able to see which service areas tend to be more service-centric, such as personnel management—where each service has its own ERP software methodology,” Osborn noted.

In areas where the services share more commonality regarding services needed, such as transportation management, USTRANSCOM is requesting that each service forgo their individual ERP software methodologies for a prescribed, enterprise-level SOA interface that proposes to drive down cost by eliminating unnecessary service redundancies. “The way to approach redundancy potential is to understand your enterprise architecture and where there is a need for common services, ensuring you only buy the needed service once for multiple points of use,” Osborn said.

NETWORK CHALLENGES

With traditional IT software development, USTRANSCOM program managers are left to decide from which systems information is needed and which are in need of information. Once a deal is reached between an information provider and the information consumer, a network of interface transaction points is used in delivering service to customer. “All is fine until an information provider changes the definition or method of transmission of a particular data file,” said Osborn. “In a multi-interfaced network environment, each system connected to that file has to alter their method of reception, causing a ripple effect throughout the entire network.”

To avoid this rippling, SOA with a twist offers prescribed common interfaces that enable the services and agencies to use their own ERP software as part of a greater common architecture. For example, today, GTN has more than 300 individual interfaces. USTRANSCOM’s goal is to bring that number down to less than 10.

Through CSV, the command proposes to prescribe the specific data elements that are needed to actually conduct specific movements, including all the data elements of each service and agency project manager. By coupling all data elements under a prescribed USTRANSCOM interface, an enterprisewide view of needed services can be utilized by each service and agency.

“This enterprise view will offer a greater transparency of needs and eliminate the service duplication waste associated with service- centric purchasing,” said Osborn. “This single interface-type approach will ultimately decrease the volatility within service transactions as change-in-system operation occurs since there will only be a need to conform one USTRANSCOM-defined interface. With a single enterprisewide portal, the services and agencies will also have access to increased information to use within their own ERP architectures,” he added.

An example of CSV’s potential for achieving savings in time and manpower might involve two unit commanders needing to know specific ground distribution information, one on the status of a supply part and the other on a medical patient. The data on each would normally need to be retrieved from multiple different systems requiring many segmented tracking data. Using a CSV portal, both unit commanders can access aggregated data on each request with minimal data input. Once obtained, the commanders can use the information to make quicker decisions regarding the best course of action.

Currently in phase one of CSV implementation, USTRANSCOM has developed a Web-based portal as part of the program’s common operating picture for deployment and distribution. CSV concepts are being delivered as part of the conceptual architecture approved in December 2008. Other elements are slated to be completed in September 2009 with engineering-level detail ready for implementation in January 2010.

DATA MANAGEMENT SOLUTION

Performance-based logistics (PBL) contracts and metrics require integration between customer and original equipment manufacturer (OEM) supply chains as well as with supporting engineering teams. Leveraging startup capabilities from EDS, Siemens Product Lifecycle Management (PLM) software’s Design to Run-based approach offers required OEM product life cycle view through its Teamcenter product family, and OEM/service life cycle integration through an in-service data management software package.

Teamcenter product life cycle management software portfolio delivers an enterprise life cycle collaboration platform from which both original equipment manufacturers’ service personnel and warfighters can jointly manage and control necessary data. This data can be used to define the complete technical definition and 3-D spatial representations of a product, platform or total fleet. The software also manages all related operational and maintenance history information.

“This implemented solution provides the warfighter with a single and reliable source for the complete and current technical definition of the most complex product, platform and/or system, as well as relevant operational and maintenance history,” said Tim Nichols, managing director, aerospace and defense global marketing, Siemens PLM Software. “This minimizes the time and risk of finding the correct information, reduces the process time for repairs and overhauls, and ensures the logistics supply chain delivers the right part at the right time, every time.”

A fully unified set of applications that enable the seamless synchronization of all operations and data, Teamcenter looks at a product’s life cycle throughout its value chain. This data collection minimizes change-process cycle times and increases output data accuracy.

Developed with a clear focus on the unique challenges of the defense industry, Teamcenter delivers pre-configured industry templates to manage contract data requirements lists and supplier data requirements lists; ITAR compliance; and serialized parts tracking, among other processes. “The portfolio possesses the inherent and demonstrated scalability to manage the most complex and aggressive operational environments,” said Nichols. “The modular architecture further simplifies and accelerates its implementation into the most complex enterprise.

“Teamcenter offers a unique closed-loop feedback link between warfighters and service personnel and OEM designers and engineers, which can facilitate early recognition of field problem and solutions,” said Nichols. “Ultimately, this enterprisewide PLM support platform will enable warfighters and service personnel around the world achieve greater fleet availability and reliability, reduce repair and overhaul cycle times, and lower the total cost of fleet service and support.”

ELOG21 AND ECSS

As part of an initial acquisition strategy for modernizing legacy systems in satisfying newer IT processes, the Air Force has invested in an ERP software package that was awarded to Oracle in 2006. A second phase of the acquisition process for implementing an eventual product solution took the Air Force into a package-enabled process redesign effort. In this redesign, Air Force logistics processes are to be re-engineered to fit a new Enterprise Combat Support System (ECSS) program implementation. CSC Corp. was awarded this system integration contract in February 2007 with slated product release slated for 2010.

As a major enabler of the Air Force’s Expeditionary Logistics for the 21st Century (eLog21) transformation program, ECSS represents a shift away from stand-alone legacy system batch-oriented processes toward an integrated, enterprise-level ERP-based business architecture. Using ERP software, air commanders will be able to plan, organize and execute logistics service orders from acquisition through sustainment from an enterprisewide viewpoint.

“When fully implemented ECSS will provide real-time visibility for all Air Force equipment and supplies, this will be used by airmen at all levels worldwide to order, track, issue and receive the materiel needed to perform their mission,” said Grover L. Dunn, director of transformation, Deputy Chief of Staff for Logistics, Installations and Mission Support.

“The combining of business best practices with logistics processes at the enterprise level eliminates much of the uncertainty associated with service-centric, legacy system acquisition, maintenance and sustainment,” said Mike Keys, chief architect, ECSS, Corporate Services Corp. “By standardizing these processes under one set of business rules and within one data source, information affecting all phases of logistics operations can be shared across all commands, optimizing end-to-end supply chain function.”

ECSS uses an ERP software solution that coordinates all logistics and supply chain information to provide commanders with improved processes and greater access to critical data. Leveraging a suite of software applications to integrate existing cyclic databases, the ECSS ERP solution is intended to provide the Air Force with a standardized logistics operating picture using a single source of data aggregated from independent legacy systems. Activities such as unscheduled maintenance will likely be all but eliminated as data collected from multiple disparate legacy sources will be combined by ECSS for determining when and in what manner an aircraft is in need of service.

“ECSS will create an integrated logistics data environment across the Air Force,” said an Air Force official. “Having better metrics will enable better decision-making when it comes to maintenance of any kind, improving readiness and mission capability while reducing costs.”

The Air Force currently expects to begin fielding ECSS in 2010 and introduce final implementation by 2013. ♦

Back to Top