APPROACHING DEVELOPMENT IN LOGISTIC INFORMATION SYSTEMS

The introduction of technology into modern defence necessitates integrated computerized information systems to render effective and efficient logistic support. Traditional information system development does not ensure attainment of use and time scale requirements in the continuously developing environment of logistics. This paper describes current approaches to the development of logistic information systems.


INTRODUCTION
The objective with this paper is to describe current approaches being applied in the development of logistic information systems ... Logistics is seen as the collection of activities required for the acquisition provisioning, distribution and maintenance of materiel, facilities and services and the movement of materiel and personnel in support of actions by military forces.Although principles contained in this paper are equally applicable in commercial and industrial ventures, above definition delineates the sUbject scope of this paper.
The introduction of technology as a cardinal element in modern defence necessitates integrated computerized information systems to render effective and efficient logistic support.
The approaches described in this paper stems from the experience that traditional information system development approaches does not ensure attainment of use and time scale requirements.These approaches are currently being applied in a major logistics information systems development program.
The paper assumes a working knowledge of logistics and is structured to cover the following : o Overview description of the logistics environment and the "logistic information system" o Approaches to design and development.
o Approaches to management of the design and development process.

LOGISTIC ENVIRONMENT
This section contains an overview description of the "logistics environment" as a reference to the reader.

OBJECT DEFINITION
Objects are defined as the actual weapon and operational support systems.It is obvious that the objectives of activities and organizations involved change considerably as the object progresses from phase to phase.Figure 1 illustrates this for the "User" and "Developer" organizations.

LOGISTIC PROCESSES AND FUNCTIONS
The prime objective of logistics as a function in modern warfare, is to ensure weapon system availability and/or readiness, suited to the threat at any point in time.To attain this objective, logistics comprise the continuous execution of the following maj or processes and/or functions: Logistic operations control to manage the supply of logistic support in the operations of the organization and supply of logistic support during operations.
Acquisition and Phase-out cycle.Develop and supply of new weapon systems to satisfy the stated need with cognisance of baseline comparative systems data.The information systems will supply cardinal technical data to the use phase information systems.At the phase-out stage, data will be removed in parallel to system removal.
c. operating Cycle.During weapon system operation, maintenance will supply planned requirements to the materiel systems to procure and distribute materiel according to requirements.
d. Improvement cycle.During operation, performance will continuously be evaluated and modifications to the weapon system will be implemented.
e. operations cycle.In preparation for and during actual operations, actual requirements will be satisfied through priority orders within performance and status envelopes.

Goal Performance
Budgets Expenditure The implementation of logistic information systems into the "logistic organization" is primarily dependent on the role of each of the organizational entities in the execution of the logistic processes.Figure 3  This part defines the major current approaches applied in the design of the logistic information systems.The description covers the principles of integrated function allocation and multi-dimentionality, the overall design process as well as specific problems in the process.In the design of logistic information systems, it is fundamentally important to properly consider all design variables.True optimization can only be approached if "environmental" elements like organization, technology and functionality can be changed or re-designed at the same time.Figure 4 depicts a summary total system view.An example of this is new computer technologies such as graphics or distributed processing that will require changed application systems and can only effectively be utilized if use and user changes can also be effected.

COMPUTER INFRASTRUCTURE AND FOU~DAT!ON SYSTEMS
Expansion of the "total" design fundamental, outI ined above, leads to the principle to approach the design with cognisance of the multi-dimentionality of the logistic system.Typical maj or dimensions are the following: a.
Goal and objectives structures as well as the functions to attain the goals and objectives. b.
Processes that can be decomposed into tasks or functions, necessary to attain the goals.
c. objects "moved II through its life cycles by the actions inherent in the tasks or functions.

d.
Functional concepts such as technology centralization or dispersion.
e. Logistic Functionality as Logistics is actually a concept or approach that co-ordinate a variety of 4.4 -9-

DESIGN PROBLEMS
The most difficult problem is probably to design with cognisance of existing information systems and the changeover or growth path to get to the "ideal" system.
Determination of "real" requirements is made very difficult by the fact that the "science" of logistics is only maturing at this stage and is being influenced by changes in computer and software technology.The "concurrent" growth design logic is probably the cardinal approach to this problem.
Design change management demands much more from Careful choice of design expected development in consideration.
in a "concurrent" approach, available design "tools"."tools" is cardinal if the this area is taken into 5.
5.1 utilization of new approaches and technologies such as on-line computerized procedures and regulations, help functions and training, implies vast changes to current thinking and organizational roles and normally cause an equivalent resistance.

DEVELOPMENT APPROACHES
This part defines the major current approaches applied in the logistic information systems development process.The description covers the fundamentals of parallel development, prototyping, technology interfacing, development strategy and test and integration.

PARALLEL DEVELOPMENT
The parallel development approach is inherently linked to the concurrent design principle.As the realization cycle of traditional serial development processes exceeds the change cycles in requirements and technology, it is essential to implement and maintain a development approach that shortens the development cycle drastically.In the extreme, this can imply that requirement, definition, design, development and implementation work can be executed within the same time frame to allow an incremental but rapid results profile as illustrated in Figure 6.Due to the control risk inherent in this approach, the following strategies are proposed o Close integration of requirement definition and design and development functions.f.Technological (computer) Characteristics especially in terms of its interfaces with its application environment.
g. Application System (software) characteristics and the functionality thereof.

DESIGN LOGIC
It is fundamental to break away from the serial concept of design.The traditional concept of design as a serial logic should be replaced by a "concurrent" concept.A simplified example of this concept is a situation where packaged software is bought in and modified over time to suit requirements as opposed to a full requirement definition, functional analysis, design, etc. approach.It is obvious that this design approach relies heavily on design "tools", implementation software and design support functions such as quality assurance and configuration management.Figure 5 illustrates the "concurrent" design logic by summarizing the design process elements into a few major subprocesses.

METHODOLOGY AND STANDARDIZATION
Due to typical time scale requirements and complexity of the logistic function, work formalization should be based on a trade-off between the requirement for standardized, rigorous and structured analysis and synthesis methodology and the requirement for different methods to successfUlly establish a series of inherently diverse functions, processes and systems.
This tends to imply the implementation of an overall methodology template, allowing freedom to use different detail methods, as required.

PROTOTYPING
The advent of new generation tools prototyping at minimal cost.Experience in most cases the contribution of allows rapid has shown that prototypes to requirement development exceeds the value of prototypes to prove concepts.In addition to this, expanded prototypes that actually function, can have major advantages in addressing and even temporarily satisfying critical user requirements.

FUNCTIONAL DEVELOPMENT
The most cornmon cause for information systems development failure is probably the lack of "intelligent" requirement analysis and/or functional development in parallel to systems development.It is essential to fund and staff a development activity focusing on development of the functional elements of the total system, primarily implementing through organizational change to suit the systems change at fielding.

DEVELOPMENT STRATEGY
with reference to the complexity and inherent differences between logistic areas, it is essential that a cascade of development strategies be established.The strategies will form the cornerstone of development flow in each of the target areas.Development strategies should be embodied in formal development plans and should be the result of careful analysis and synthesis of the primary drivers and requirements in each area.It is essential that this activity leads mechanistic planning by a margin that exceeds reaction cycles by the maximum possible margin.

TEST AND INTEGRATION
Due to the hidden costs in fielding "flawed" systems, it is essential to implement a rigorous test and integration philosophy.Major cost savings in both operation and development can be realized if formal test and integration facilities are established, operated and managed.A typical facil i ty concept can be: o Alpha test and integration facility that is isolated from the use environment.
o Beta test and integration facility that is identified in the use environment.
Typical functions to be allocated to these facilities will be the following:

DESIGN AUTHORITY
Tbe previous parts outlined tbe approach to view a total system with functionality, object characteristics, application systems and computer infrastructure as design variables.It is important that this philosophy be effected by rigorous application of the "single design autbority" concept and ensuring of continuity of effort throughout the total system life cycle.
"s ingle design authority" bas ically impl ies that information system segmentation drives allocation of total responsibilities with clear interface definitions as the management structure deployes to enable actual program execution.This approach should normally result in a clear and line oriented program organization structure.

TECHNOLOGY AND EXPERTISE
The inevitable continued change and growth in logistics over the medium to long term necessitates that expertise and technology should be approached to ensure medium to long term survival.The most feasible current strategy is to ensure continued long term local support by actively establishing required resources through maximum utilization and development of existing local capabil i ties.

EXISTING SYSTEMS AND PROJECTS
The parallel development approach can not be realized in practice if tbe management system does not encompass existing systems and proj ects.It is essential that existing systems supply tbe lessons learned and that on-going projects be restructured to fit into tbe overall development strategy and plan.

WORK STRUCTURING
sep~rat~on of functional development and system englneerlng into two work areas is essential as the priorities are normally conflicting.
computer Infrastructure and Integrated support Development need to be separately formed and managed to ensure success in both areas.
In addition to system engineering, application systems require further delineation, primarily due to the difference in life cycle status of the individual areas.Figure 7 illustrates this approach.

ORGANIZATION
Based on the necessity of integration for success, the implementation of a single purpose systems engineering team is recommended.
To suit requirements regarding establishment and maintenance of local expertise, as defined earlier, actual systems establishment should be realized on a sUb-contracting basis.This is illustrated in Figure 9. -16-

CONCLUSION
This paper summarized cardinal approaches that are currently being applied in the development of logistic information systems.
Al though all these principles have not been fully evaluated, initial results supports continued adherence to the principles.

Figure
Figure 2 , logistic systems Functional Operation

Figure 5 :
Figure 5 : Concurrent Design logic Figure 6Parallel Development Approach

Figure
Figure 7 : Work Structuring Figure 8Phasing Strategy

Figure
Figure 9 Basic Organizational Approach

Figure 1 :Figure 2 :Figure 3 :Figure 4 :Figure 5 :Figure 6 :Figure 9 :
Figure 1: Objectives and Activities during Object Life Cycle Figure 2: Logistic Systems Functional Operation Figure 3: Information Systems Implementation Figure 4: Design Variables in a Total System Approach Figure 5: Concurrent Design Logic Figure 6: Parallel Development Approach Figure 7: Work structuring Figure 8: Phasing Strategy Figure 9: Basic Organizational Approach

and Activities During Object life Cycle life Cycle User Developer Phase Activities/Objectives Activities/Objectives 1. Need Identification and Identify/Define/Optimize Identify/Define Options options evaluation Need and User Implications 2. Requirement Definitl0n Define requirement and Develop and Development prepare user/use interface 3. Production Introduction Introduce into Service Produce and Fielding and Field
Figure 1 : Objectives

Depots COl11T1and Head Quarters logistic Management Acquisition Mai ntenance Material Requi rement and Procurement Inventory Control and Distribution Weapon System Improvement Operations Support logistic Servi ces 4 .
contains a summarized system implementation matrix.