From DBLWiki
Jump to: navigation, search

About DBL™

Logistics engineering is the process of planning for the support of a system throughout its life.[1] Decision-Based Logistics™ (DBL™) is a conceptual framework for defining logistics engineering requirements, planning logistics engineering tasks, and unifying and simplifying the vast and disparate resources available to the logistics engineer. DBL™ views logistics engineering as a series of questions to be answered -- or decisions to be made -- rather than a list of tasks to be performed. This approach helps focus logistics engineers on desired outcomes and avoids miscommunication due to overuse of jargon. For example, “How will we fix this system?” is much clearer than “Give me an MTA.”[2] The intended users of DBL™ are logistics engineers, acquirers of systems, providers of systems and system support, and system engineering policymakers.

By organizing logistics engineering resources and establishing resource relationships, DBL™ helps unify the concepts of acquisition logistics, integrated logistics support (ILS), and performance-based logistics (PBL) and their associated metrics, tools, and techniques.

DBL™ is organization and system agnostic. We have designed DBL™ to be used by any agency within the Government and by the private sector. Nevertheless, the DBL™ content draws heavily from the U.S. Department of Defense’s (DoD’s) acquisition logistics resources because the DoD has the most extensive set of logistics engineering resources in the world. DBL™ provides the framework and resources to guide logistics engineering, but it does not have “ready-made” solutions for particular systems. It is the job of the logistics engineer to tailor each system’s logistics support to the technology, the application, the environment, and other relevant factors.

In a world filled with business strategies, initiatives, and philosophies, it is important to differentiate between what DBL™ is and what it is not. DBL™ is a

  • conceptual framework for unifying and simplifying the vast and disparate resources available to guide logistics engineering;
  • design framework for a web-based reference system; and
  • basis for structuring logistics engineering efforts, developing contractual logistics requirements, and training logistics engineers.

DBL™ is not a

  • replacement for existing strategies, tools, or techniques, such as ILS and PBL;
  • new set of computational methods; or
  • cookie-cutter approach to logistics engineering.

For additional background information, refer to File:DBL.pdf, our DBL™ Concept Paper.

About this Wiki

LMI has created this Wiki to clarify and unify the disparate resources describing logistics engineering. However, it is beyond the skills or resources of any single organization to identify and keep current all such resources. Therefore, we appeal to logistics engineers everywhere to help us manage content.


The idea of the Wiki is to supply users with different routes to the same information. This framework is flexible, scalable and easy to use for a wide range of users.

Here is the general structure of the framework:


Let's break up this diagram from the top down. The User Entry Point is the Main Page that you entered this webpage on. From there you can navigate to Getting Started which is the gateway to the Content Entry Points. The Content Entry Points are the options you are then presented with: Decision-Based Logistics Approach, Logistics Elements, and Searching the Wiki.

Now we can fill in the boxes so the top of our diagram looks like:


Next, there are the Content Pages. These pages take a lesson from object-oriented computer programming in that they use a structure, or class. The pages of each class consists of the same attributes. The DBL is not just an amalgam of logistics engineering resources, it is a structured web of instances of classes that desribe the vast number of resources. The Wiki platform is so well suited for this structure because of its ability to connect pages through hyperlinks. Here is an example of a set of relationships of Content Pages:


Finally, let's take a look at an individual Content Page. As we talked about, there are different types of content pages, each with their own structure. One of the structures is a method. Methods are for defined processes to plan some sort of logistics support. One example is the Level of Repair Analysis (LORA). This method answers the question Where am I going to repair my asset(s)?. That question in the "Entry Point" for the LORA, so in staying with the plain-English approach of the DBL, that is the page we are looking for. Here is the structre of this particular page, an example of a Method:


If you have more questions about the Content Pages, please see The Help Page for more information on how to create these "instances" of classes from templates that were created in Wiki.

So as you can see, the DBL Wiki is a structed web of content pages with multiple entry points to allow for efficient nagivation of resources. As stated before, please review our concept paper on DBL, File:DBL.pdf, if you are interested in more information about the ideas behind Decision Based Logistics.


[1] See Benjamin S. Blanchard, Logistics Engineering and Management (New Delhi: Prentice-Hall of India, 2006), for a more comprehensive description of logistics engineering.

[2] MTA = maintenance task analysis

Personal tools