Amministrazione generale > Implementazione di Windchill ESI > Implementing Windchill ESI in an ORACLE Applications Environment > Understanding Windchill ESI Architecture > Common Business Object Data Model
  
Common Business Object Data Model
Common Business Object (CBO) is the data model adopted by the Windchill ESI business logic to represent the data for each object published from Windchill PDMLink. It uses concepts from the Open Application Group Interface Standard (OAGIS), which is a self-describing, XSD-based XML schema, specifically designed for communicating and passing data between ERP, CRM, and other enterprise-level systems.
TheWindchill ESI CBO schema is capable of handling parts, BOMs, documents, Change Notices (CNs), and manufacturing objects such as process plans and resources. It is centrally maintained and incorporates a neutral data format to accommodate the data requirements of all current as well as future source and target enterprise systems. Instead of creating a complex configuration of source and distribution target mappings for each new system integrated into the enterprise, one single, direct mapping is created between the CBO and the distribution target. This type of mapping also makes it easy to make any needed enhancements or changes to the CBO for specific systems, without involving or impacting all the systems in the enterprise.
The CBO contains separate self-describing business objects. It can be customized to create new objects as well as to add new attributes to existing objects. Each business object contains a UserArea element where all user-defined data used for customization is kept, cleanly separated from the originalWindchill ESI data.