**Business Enterprise Common Core Metadata (BECCM)**

**Community of Interest (COI) Meeting Minutes**

February 1, 2012  3:30 PM – 5:00 PM 

Pentagon Conference Center, Room B9

**Attendance**

**Agenda**

1. Data Integration Strategy

1. Defense Logistics Management System (DLMS) 

1. DCMO Equipping the Workforce Update

1. Next Steps

1. Action Items

**Meeting Introduction**

Mr. Dennis Wisnosky began with a roll call of participants and then Mr. Jerry Cole discussed the agenda. 

**Data Integration Strategy**

Mr. Ray Bombac began with an overview of the Data Integration Strategy presented at the December BECCM COI Meeting. He mentions the accomplishments and the need for a solid data integration strategy. BECCM COI membership expanded to include the Military Service and Field Agencies, other DoD components, and implementing systems and ERPs. The BECCM will be a forum to bring operational data issues to the table and encourage enterprise collaboration. 

Mr. Bombac further discussed that in order to see that data requirements are met, we must look at the “what” and “how.”  There are plenty of LRPs that dictate what is required, such as policy requirements and data standards. We are faced with challenges when we run into how to leverage technical solutions. The benefits of data standardization are interoperability accuracy, compliance, business analytics and reduced cost. Leveraging COTS as we improve integration, maintenance, testing, and development results in reduced cost. 

The Data Integration Strategy should focus on the data as it relates to an End to End (E2E) process. Procure to Pay (P2P) and Hire to Retire (H2R) are the two top priorities now. Before publishing data requirements in the Business Enterprise Architecture (BEA), we need to have a dialogue with implementing systems to make sure they (business system/ERP) are not negatively impacted. One Voice was formed to consolidate and prioritize requirements to leverage Oracle and SAP development. The ERP Lab is a sanbox instance of an ERP used to test requirements and recommend standard configuration solutions. The One Voice POC is Mr. Jack Woolum. Mr. Mike Sorrento (SAF A8) is the One Voice Chair for Oracle. 

**Action Item:****At the next BECCM COI Meeting, discuss the One Voice effort and what has been accomplished. An informational brief will be provided.**

Another focus area for Data Integration Strategy is Enterprise Exchange Data. We need to identify and standardize critical transaction sets used across the enterprise. 

**Action Item:   Enterprise Line of Accounting/Accounting Classification Memo is a draft and we want feedback on how it impacts your systems, need feedback by February 28, 2012. Memo will also be sent out electronically**. 

We need a master data governance process to ensure we have the right policy in place. Master data can be thought of as the people, places, concepts and things that are critical to business and referenced throughout the enterprise. We need to ensure data standards are consistently developed in the BEA. Data standards should have standard definition, values and implementable business rules. 

We have many DoD Enterprise Standards throughout the enterprise. We would like to open dialogue on enterprise standards in the BECCM to make sure the BECCM community understands the questions posed on slide 7. 

Implementation business rules are reflected in the BEA and in order to understand what it means to be compliant, the relationship to business rules must be developed. Mr. Mike Shannon spoke about SFIS validation and how data elements are applicable to systems, looking at standard configuration guidance. The business rules for the main account are found on the screen shots from SAP on slides 9-13. The first business rule, Data Syntax, specifies what length should be. It shows view elements and the authoritative source. The store and maintain business rule is for specific data elements, separate field with their own list of values for that account. Run transaction calls at the table where the data element is stored. Typical usage business rule for any main account is associated to one fund type. Post to the general ledger business rule is the main account used for accounting classification. 

In order to IGT (Intra-Governmental Transactions), need to have buyer side and seller side. Today, LMP does not receive the seller side information. Trading Partner Entity Code is trading partners main account and trading partners limit. This is an operational challenge in multiple ERPs and we need to figure out how to solve the IGT problem for the department moving forward as more and more transactions are processed. 

**Defense Logistics Management System (DLMS)**

D.C. Pipp, Director, Logistics Management Standards Office, gave a presentation on the Defense Logistics Management System (DLMS).  The DLMS process has been designed to promote continuous process improvement while facilitating joint logistics Interoperability.  The mission is accomplished through an institutionalized process calling for the development of business rules, information exchange, and detailed procedures.  Mr. Pipp noted that the DLMS office, in collaboration with the Services and Agencies, develop over 100 business process changes per year. Additionally, DLMS is the long range replacement for the Defense Logistics Standard System (DLSS – also referred to as “MILS”).  He stated that DLMS is integral to, and a necessary part of the Business Enterprise Architecture.

Mr. Tommy Lyons provided an overview of how DLA EBS has coordinated with DLSM to develop a methodology for implementing the Standard and providing feedback to the DLMS Office when significant impacts or changes are required to the system and ERP COTs functionality.

Mr. John Garbarino noted that DCMO (formerly BTA) and DLMSO had formerly partnered in FY11 to develop the minimum essential data for Order to Cash (O2C).  This process and data modeling could be used to support the current BEA IGT functional gap from BEA P2P 9.0 content refinement.

**Action Item: Address what level of DLMS goes into the BEA. When focusing on the business process piece, can it or should it be found in the BEA? If uniformly implemented in the same manner across the components, then it belongs to BEA.**

**DCMO Equipping the Workforce (ETW) Update**

Mr. Jerry Cole provided recap and the vision for ETW. Slide 48 shows DCMO and Non-DCMO participation as of January 2012. Slide 49 shows our Computer-Based Training (CBT) Stats. The Executive Level Roadshow has received approval from Honorable Elizabeth McGrath, DCMO. This brief is a high-level view of semantics, business processes, and the Enterprise Information Web (EIW) approach. The current schedule can be found on slide 50. There have been approximately ten (10) classes completed since June 2011. The recent HRM Ontology work by OSD P&R IM has benefited from attendance in our courses.  

**Action Item: Send out information on logistics and ETW courses to BECCM COI distribution.**

**Action Item: HRM Community will give a high-level view on their ontology at the next BECCM COI meeting.**

**Next Steps**

Jack Ahuja initiated an Action to develop a DoD Business Data Standards WG under the BECCM COI Charter that would work to develop a draft document for review that would outline the following: 

1. What are the attributes of a Mature DoD Business Data Standard?

· Examples – Business Rules, Data Definitions, Source, LRP mapping, Primary Steward, Metadata- Values, Length, xml tag, etc.

2. How mature are the standards in the BEA?

3. What does it mean to be compliant to the Data Standard?

4. Does the Data Standard have implementable business rules?

5. What is the governance process for the Data Standard?

6. Is there a validation process for the Data Standard?

7. Has the Data Standard been coordinated with business investments/ERPs?

8. What is the impact of implementing data standard?

**Action Item:  Ray Bombac will solicit membership from each CBM and DoD Component and Data Standard Steward to begin this analysis to present a “straw-man” at the next BECCM.**

**Closing**

Mr. Dennis Wisnosky closed the meeting by talking about the Business Governance Board (BGB) drafted by the ODCMO Staff. The intention is to have a new business governance structure, new ways for managing the Business Mission Area of the department starting at the top. 

**Action Items**

1. **Action Item**:  At the next BECCM COI meeting, RP&ILM will provide the EEIM Standard briefing.

2. **Action Item:** At the next BECCM COI Meeting, discuss the One Voice effort and what has been accomplished. 

3. **Action Item:** Enterprise Line of Accounting/Accounting Classification Memo is a draft and we want feedback on how it impacts your systems, need feedback within 30 days. Memo will also be sent out electronically. 

4. **Action Item:** Address what level of DLMS goes into the BEA. When focusing on the business process piece, can it or should it be found in the BEA? If uniformly implemented in the same manner across the components, then it belongs to BEA. 

5. **Action Item:** Send out information on logistics and courses to BECCM COI distribution. 

6. **Action Item:** HRM Community will give a high-level view on their ontology at the next BECCM COI meeting. 

7. **Action Item:**Ray Bombac will solicit membership from each CBM and DoD Component and Data Standard Steward to begin this analysis to present a “straw-man” at the next BECCM.

8. **Action Item:**  BECCM COI Staff will develop revised BECCM CONOPS based on High Level Strategy presented both in February and December.  This CONOPS will be staffed with all current and new members to the Community of Interest.

3

# image1.png

# image2.png