Complex business operations require detailed information exchanges between many inter-related disciplines (design, manufacturing, configuration management, sustainment, supply chain management, marketing, etc.). Professionals within these various disciplines speak different languages, but rely upon each other as producers and consumers of inter-related data.

Nexus LCM is the meeting point of the standards, technologies and services that enable process and data interoperability across various disciplines and organizations.

Our premise is to leverage open, commercial standards where available to enable business and Government customers to use their choice of applications for each functional discipline. We work with standards bodies, application developers, and industry-specific specialists on behalf of our customers to support implementation of tailored solutions.

Examples of supported applications:

LOGFAS

GCSS Marine Corps

JOPES

MJDI

SAP

Our process:

  • Identify the policies, processes, systems and organizations that support LCM for your products
  • Identify the information sharing and exchange requirements for each stakeholder to perform their LCM functions
  • Map the processes with associated information requirements through the systems to identify current data management gaps
  • Develop a solution to maximize use of current systems, through use of standards-based information exchanges
  • Identify key points for automation to improve data acquisition and data quality
  • Implement the solutions based upon customer preferences

LCM is a culmination of all of the activities required from concept inception through production, usage and eventually retirement and disposal of any complex product. Complex equipment examples: aircraft, vehicles, software, industrial systems, weapon systems, communications systems, distribution networks.

Joint Enterprise Data Interoperability (JEDI)

JEDI is an open-standards interoperability platform built upon ISO 10303:239 data exchange standards identified in NATO Standardization Agreement (STANAG) 4661. This STANAG identifies “Product Life Cycle Support (PLCS)” standards to address interoperability of data between Information Systems (IS).

Using PLCS as a neutral model, the JEDI team creates data exchanges which can operate in Tactical to Strategic spaces. JEDI is designed to primarily interact with systems in the background, meaning system users’ have access to external systems or data without the need to train or knowingly interact with JEDI.

PLCS’s rich content and flexibility enables JEDI to be a many to many data sharing capability without point to point interfaces. JEDI does not translate data. Instead, it translates data formats and metadata that identify the context and meaning of data so that it can be discovered and re-used outside of its resident system. This translation is possible due to the mapping of data elements and business rules with the PLCS model. This provides the specificity needed to understand the relationship of the data to equipment. For example, “1234” is the “Product_Individual” PLCS attribute known as “Service Serial Number” assigned by “U.S. Marine Corps” but is the same item as “ABCD” which is attributed to “OEM Serial Number.”

JEDI is deployed as an Engine, tailored and operated by an administrator to mediate and implement the interactions with systems. JEDI also has translators to interpret data context for storage or further re-use. JEDI stores data in a dedicated database in the open standard PLCS format. JEDI is designed to operate in a many to many scenario to maximize interoperability across systems and organizations.

The figure below shows only 2 systems for simplicity.

Success

Customers

US Offices, West Coast

Stevenson, WA

US Offices, East Coast

Washington, DC

European Offices

Rome, Italy

Information Request

[recaptcha]