BEA DoDAF Models
List of DIV-2 Logical Data Model Diagrams
Name Description
Accounting Classification Structure Composition The subject area diagram that shows the decomposition of the funds identified by the Treasury Appropriation Fund Symbol into budget activities, sub-activities, and budget line items; how these budget concepts are related to each other; and how they define the accounting classification structure.
Accounting Transaction This is the complete General Accounting, Cost Accounting, and General Ledger including the touch points with the other functional areas.
The purpose of this diagram is to show the entry/touch points with the combined entities from the other functional areas as they impact an ACCOUNTING-TRANSACTION through the sub-type entities.
Acquisition Element This view is intended to assist in understanding the data supporting activities that require data about the existence and nature of contracts for goods and services. (Execution of contracts is a different view.)
Acquisition Program Contract Information Intended Use: This diagram is to demonstrate information that supports management oversight of the Acquisition Program Contract. Such information includes Budget, Contract, and Actual Cost of the Contract.
Acquisition Program Management Personnel Information Intended Use: This view is created to show contact information of management personnel who plays a role such as Program Manager (PM), Program Executive Officer (PEO), and Point of Contact (POC) in an Acquisition Program.
Acquisition Program Oversight Intended Use: This view supports the recordation of an Acquisition Program, Acquisition Program Baseline, and Program Assessment information in support of major acquisition activities. Additionally, it supports projected-estimated costs, earned value, and program links to budget execution data.
Acquisition SOA Service Data Model Intended Use: This view displays all of the entities and their relationships that support AV SOA Services.
Assign Real Property Space This subject area model depicts entities and the relationships between them needed to support the functionality for Real Property Management space management efforts.
Assignment Action Administer Assignment Action includes determining the ASSIGNMENT of a PERSON, submitting the ASSIGNMENT request, performing ASSIGNMENT screening, and finalizing the ASSIGNMENT decision.
Budget - Defense Resource Plan This diagram shows the Entities and Relationships in context with each of the other Budget diagrams, the Organization Structure, and the SFIS Accounting Classification Structure.
Collection and Accounts Receivable This diagram represents collections and accounts receivable functions of the Financial Management System (FMS) being developed for Department of Defense. It includes information on receivables due to DoD from a vendor person or another government or a foreign government organization. Receivables may be set up for goods and services sold by DoD, for loans, debts, donations or for miscellaneous revenue streams. It also includes credit approval and credit rating of the vendors before DoD can do business with them. This information is kept updated on an ongoing basis. Another function included in this diagram is the billing function. It may be inter-agency reimbursable billing, billing of vendors or foreign governments.
Contract This view is intended to assist in understanding the data supporting activities that require data about the existence and nature of contracts for goods and services. (Execution of contracts is a different view.)
Contract Execution Event This view is intended to assist in understanding the data supporting activities that require data about the execution of contracts for goods and services.
Cost The purpose of this diagram is to show the entities involved with the Cost Accounting area.
Depreciation This view shows the information needed to plan for, determine amounts for, and record the depreciation of real property, personal property, and improvements to real property.
Disbursement and Payables This diagram presents the view of the logical data model that relates to and supports the Financial Management Activity (FMA) disbursement activity models.

In this view, the purpose of the logical data model is to provide traceability from a basis for payment (PAYABLE) and a payment (PAYMENT).

Please note that PAYABLE is subtyped. The relationships associated with a PROCUREMENT-PAYABLE subtype are shown here. For the sake of clarity and simplicity and because HRM creates the basis for payment (PAYABLE) for travel/expense and payroll, the relationships associated with the other two subtypes, TRAVEL-EXPENSE-PAYABLE and PAYROLL-PAYABLE are presented in the view: HRM - Payroll and Travel.
Distribution The purpose of this view is to depict the requisition of materiel items from the DOD sources of supply, and their movement through the DOD distribution process.
Document The BMA Logical View Document, presents the structure for a document within the BEA.

The Department of Defense creates and stores thousands of documents each year. Documents are used in support of budgeting, policy, planning, guidance and much more. This view captures fundamental information about a document. It must be clarified that this view focuses on capturing information about the documents without delving into the contents of the document.

The central entity is DOCUMENT, which is does not represent a document, but rather the essential information about a document. The document itself may be available in various media, (ex..: hardcopy, CD), and formats, (ex,: Word, PDF, CAD file). The media may be located in various locations.

The association of one document to another is captured in the entity: DOCUMENT-ASSOCIATION. Examples of associations would be:
- supersedes
- referenced by
- is part of.
Enterprise Energy Information Management Logical representation of enterprise information needed to manage DoD facility energy information.
Environmental Liability The Environmental Liability (EL) view presents those entities that are solely for Environmental Liability as well as those BEA entities necessary to understand how EL integrates to the rest of the BEA Logical Model.

There are three groupings of EL entities in the diagram:
1. Those entities that represent the information about the area that has an environmental concern.
2. Those entities that represent the formal cost estimate and the recording of the environmental liability, and
3. Those entities that support the cost estimate.
ESOH Compliance Agreement The Environmental Safety and Occupational Health (ESOH) community often makes agreements with its stakeholders. This view supports development of and compliance with agreements such as permits and letters of concurrence.
Funds Distribution Event This subject area diagram presents the lifecycle events for funds distribution, from the master appropriation file event through funds transfer and funding authorization.
Geospatial Feature The purpose of this view Geospatial Feature is to present the structure for a Geospatial Feature within the BEA and how it is being used to represent PROPERTY, INTEREST_AREA, LOCATION, and GEOPOLITICAL_AREA. The central entity is GEOSPATIAL_FEATURE, which, together with the coordinate reference system entities, provide the essential information required for correct representation of a geospatial location. These entities can be used to describe placement and shape of phenomena in the framework established by a coordinate reference system. They can also be used to collect correct coordinate information about a location.

The view also contains essential information about the two types of geospatial features, vector and coverage, including a metadata identifier. The metadata identifier provides a way to obtain detailed information usually maintained by the Geographic Information Systems. This information can be used to completely describe a coverage geospatial feature or a vector data set. Some of those attributes include: data quality, data precision, fitness of use, data currency, organization information, the data proponent, and point of contact information.
Hazardous Process Authorization The purpose of Hazardous Process Authorization is to provide the data requirements needed by DoD's Environment, Safety, and Occupational Health (ESOH) functional community to make a decision on the procurement, issuance, and control of hazardous materials used in hazardous processes (unit of work) performed by the DoD. These data requirements were collaboratively identified and defined by subject matter experts from DoD Components and within the ESOH functional community, as well as strong representation from the logistics community. They lay the foundation to enhance installations life cycle management to target sustainability and for hazardous materials management from concept to disposal.

A hazardous process authorization begins when an organization tasked to perform work defines the need for a hazardous substance and submits the process authorization request. The request undergoes collaborative review in consultation with the process owner by individuals with expertise in specific environment, safety, and health areas. For example, the environment review will identify requirements that limit wastes and releases, mandate reporting for on-site chemical quantities, and control the disposal of byproducts. Similarly, the occupational health experts will evaluate the request for applicable worker exposure limits and requirements for personal protective equipment. The result of the review may be an authorization of the organization's use of the hazardous substance subject to specific operating limitations, training requirements, or other controls designed to mitigate the hazards.
HRM Integrated View The HRM Integrated View depicts core HRM information encompassing persons, organizations, positions, reenlistments, assignments, skills, agreements, occupations, health services, personnel requisitions, travel, and compensation.
HRM Overview Personnel Visibility is the fusion of accurate human resources information, with respect to numbers, competencies (occupations, skills, education, and training), reception accounting, individual readiness, patient accountability and status reporting, person's unit and location, and assigned duty within organizations.

This includes ensuring timely and accurate access to compensation and benefits for DoD personnel and their families and ensuring that Combatant Commanders have access to the timely and accurate data on personnel and their skill sets.

Supporting warfighters with the right types of people, in the appropriate quantity, at the right place and time will significantly increase the opportunity for mission success.

This view also depicts the information required to support the recording of a commitment and obligation for estimated pay and travel reimbursement. It further encompasses support for pay determination, allowances and reimbursement for pay distribution. Accruals, employer contributions, liabilities and collections are recorded as well as the linkage of individuals/institutions routing and account information to computed payment.
Inspection This subject area model depicts entities and the relationships between them needed to support the functionality for Real Property Management inspection efforts.
Installation, Site, & Real Property Network The BMA Logical View Installation, Site, and Real Property Network, presents the concepts on Installation, Site, and Real Property Network as defined by the Installations and Environment Real Property Inventory Requirements document (I&E RPIR).
Item Unique Identifier The purpose of this view is to identify those data elements required to uniquely register a Personal Property in the Item Unique Identifier Registry.
Location This view creates a unified structure for the locations of things or organizations. It presents the structures for two logical concepts, LOCATION and GEOPOLITICAL-SPATIAL-AREA, and the relationship between them. For example, the view presents the concept of location and its subtypes (NETWORK-FACILITY, SITE, and INSTALLATION) for the DoD Business Enterprise Architecture (BEA). With this view one can record both the political (address) and geospatial (latitude/longitude) locations of an item.
Materiel The purpose of this view is to depict the relationships between Materiel, Personal, Financial, and Acquisition data. The data captured allows for the comparison of a government-owned uniquely identified item, not intended for sale in the normal course of operations, intended for use or is available for use by the Department of Defense, and related agencies or services.
OmniClass This physical data model is intended to depict the industry foundation classes (IFC) XML exchange specification that addresses key building information that spans the building lifecycle. It uses the OmniClass Construction Classification System (OmniClass or OCCS), a classification system for the construction industry. The classification provides a standardized basis for classifying information created and used by the North American architectural, engineering and construction (AEC) industry throughout the life cycle from conception to demolition or reuse. It currently consists of 15 tables.

Organization Management This data view supports all activities associated with the management of human resources for DOD organizations. The view includes DOD mission plan implementation by organizing force structure, strength projections, accession targets, peacetime authorizations and wartime requirements.

P2P only view This view is intended to assist in understanding the data supporting activities that require data about supplier agreements for goods and services.
PDS only view This view is intended to assist in understanding the data supporting activities that require data about supplier agreements for goods and services.
Performance Management Provides a view of performance evaluation and promotion or demotion.

ADMINISTRATIVE-EVENT tracks ongoing evaluation which involves personnel EVALUATION in terms of COMPETENCY regarding a PERSON in terms of SKILL, for a given OCCUPATION within a given POSITION.
Personnel Agreement The Personnel Agreement view delineates a structure of data entities associated with management of the transition process, extensions of enlistment contract, and reenlistment, as defined in the OV-5 Manage Personnel Agreement activity.
Procurement Instrument This view is intended to assist in understanding the data supporting activities that require data about supplier agreements for goods and services.
Product Hazard Data This Product Hazard Data (PHD) view depicts, from a high-level perspective, the kinds of information necessary to identify, describe, and track hazard-related information or the lack thereof, related to Department of Defense (DoD) consumables, DoD materiel assets (which include products obtained or generated by DoD, materials found by, donated to, captured by, or loaned to DoD, and byproducts created via DoD processes). In general, this information included data from material safety data sheets (MSDS), DoD and governmental sources, and reference sources such as the chemical abstract service (CAS) and regulatory reference data providers.

Product hazard data is the comprehensive set of material, chemical, and regulatory data necessary to develop and implement Environmental, Safety, and Occupational Health (ESOH) controls for hazardous material operations. Thus, the PHD view provides a blueprint for the data infrastructure of systems that track product hazard data in support of DoD's environmental, safety, and health professionals to assure worker safety, environmental compliance, and mission sustainability.
Real Property Asset Accountability The Real Property Asset Accountability view of the BEA Logical Data Model presents three aspects of Real Properties: 1) Real Property Accountability: - What is it? - Where is it? - Who is responsible for it? - What condition is it in? - What is its value? 2) What actions have been performed involving the real property? - Acquisition - Disposal - Work (including new footprint construction, restoration, modernization, and sustainment) (3) The taxonomy of a real property as defined by the RPILM CBM: - Land parcel - Facility - Building - Structure - Linear Structure.
Receipt and Acceptance This diagram presents the Receipt and Acceptance view of the logical data model that relates to and supports the activity models.
The Receipt and Acceptance subject area diagram is based upon the structure for CONTRACT-EXECUTION-EVENT presented in the subject area diagram Contract Execution Event.
The difference between the two diagrams is their focus. The focus of the Contract Execution Event diagram is the accounting aspects of contract execution events (after a contract has been issued). The Receipt and Acceptance subject area diagram focuses on the actions that are related to contract execution events.
Request for US Exports This view supports the data used in a workflow routing application. It links a REQUEST, in this case a request for the review of an export license, to the organizations and parties participating in the review. The "status" of each item subject to the export license review request recorded a link to the appropriate review parties.
Solicitation This view is intended to assist in understanding the data supporting activities that require data about the solicitation of goods and services.
Standard Financial Information Structure This diagram shows the Entities, with the additional Attributes that are associated to the Standard Financial Information Structure Data Elements.
Supplier This view is intended to assist in understanding the data supporting activities that require data about suppliers of goods and services.
Supplier Agreement This view is intended to assist in understanding the data supporting activities that require data about supplier agreements for goods and services.
Valuation The Valuation Subject Area diagram presents the entities and relationships in the BEA Logical Data Model that support the determination of the value of a property, the depreciation of a property, (either by itself or as part of a set), and the recording of those values in the general ledger.