INTERNATIONAL PROGRAMS
CHAPTER 16 CHAPTER 16 NON-MAJOR SYSTEMS
16.1 HIGHLIGHTS Systems not designated as major systems
are generally single-Service systems, less o Management of Non-Major Systems costly, and by themselves less critical to by the Military Services national defense. However, non-major
systems may have a large aggregate impact o Integrated Logistic Support of upon the capabilities of combat units and
Non-Major Systems their logistic burdens.
o ILS Risk Considerations in Non-Ma- 16.3.2 Service Management Procedures jor System Acquisition
The military Services have delegated
16.2 INTRODUCTION management responsibility for non-major
systems "to the lowest levels of the compo- 16.2.1 Purpose nent at which a comprehensive view of the program exists". Materiel systems are To provide an overview of the manage- assigned to program categories based upon ment of ILS for non-major systems by the criteria such as combat role and program
military Services. cost. The decision authority, funding
criteria, and examples of programs in each 16.2.2 Objective category are listed in Figure 16-1. Non-ma- jor systems may also be categorized as The objectives of the ILS activities developmental or non-developmental.
described in this chapter. are identical to
those applicable to major systems, i.e., 16.3.2.1 Developmental Systems. Develop- deployment of ready and sustainable mental programs for non-major systems materiel systems within cost and schedule eange from full development to ruggediza-
targets. tion of commercial items prior to deploy-
ment, as depicted in Figure 16-2. Specific 16.3 MANAGEMENT ISSUES ILS procedures for influencing the design and defining and acquiring the support 16.3.1 Background parallel those for major systems but are generally characterized by a reduced scope, DoD Directive 5000.1, "Major System fewer iterations, fewer personnel, and Acquisitions", establishes acquisition smaller budgets. The Integrated Logistic management principles and objectives Support Plan (ILSP), for example, may be applicable to major and non-major systems. part of the Program Management Plan DoD Directive 5000.39, "Acquisition and rather than a separate document. Logistic Management of Integrated Logistic Support Support Analysis (LSA) requirements for for Systems and Equipment", sets general non-major systems, particularly those policy for the acquisition and management requiring only minor development, are often of ILS for all systems, while delegating significantly reduced by tailoring.
responsibility for application of ILS policies
for non-major systems to the military Non-major systems do not have the Services. Guidelines in DoD Directive intense management and detailed reviews 5000.1 for designation as a major system enjoyed by major systems. Managers and include program cost thresholds ($200 their staffs may be assigned several non- million-tDT&E, $1 billion procurement), major systems and handle a variety of risk, urgency of need, joint acquisition actions covering a wide spectrum of acqui- (multi-Service and other nation), and Con- sition functions. Les- supervision and the gressional interest. The ultimate criterion is requirement to deal with many areas can selection by the Secretary of Defense. result in some actions being overlooked.
(A CA Z 0 1
In~ ~ 10 ~ IU
w -E- 0 0 wN< E-4 H ~
a 2 H4 H 0 0n
P 0~ ~ (4 -4 z
N ~ ~~ ~ 04 bd
I H P4 H uH ~ g 1-
w~ ~ Ci04C4> 02 =
' -4 0 Hn U0 U w N :i.
>0H Z
IT fl0 go W W~ z A9(4
1-4 N ' u- 0- og40 r
E-4~ ~~~ N i z
=H -, 44 z E-4 E-4Z <
E- cnO0 NO N (n -4
1 - 4P H - C 4J Z, z. z N
j-4 W0H M~ E-4 O Z wE- 00 c- -
0
r UNH Cr' 00 W~ 00 W~ U th
Cr400 O Z PA~ Cii E-4 E- u
0~ 04U w~1 E-0sCr H
0 n w r4 N. 00 0 NN w
UOZ U 0
Nn
cy Wx (n 0
0 04
w w: z 4 C.o> : co
0 C.)
0O 0 00
E- 14 4C *- 3 - -1 -~ 4
od 0 00 0 0
0 0000 0
CNi -4 LMJ 4- C4
HH
0 0' H 0C
N C-4' -4 -4 IHn
UN Cr 0'00 bo
OH N N ~Z
C-' H ~ N r ,%4
> En Cr U H
N) 0 im
U N
wr4 wNnU
0 NW 1- H t- H U) N
CA z < H H- 1- H HN
a. ~W U UdC4
0 H 0 HU4 0- Cr' C' C-4 o4r3) N
N U
U U
16-2
NON- DEVELOPMENTAL
DEVELOPMENTAL SYSTEMS SYSTEMS
FULL DEVELOPMENT OFF-THE-SHELF
DEGREE OF DEVELOPMENT W/STANDARD MILITARIZATION RUGGEDIZATION OUT-OF-THE
DEVELOPMENT PROGRAM SUBSYSTEMS CATALOG
FIELD ARTILLERY GBU-15 C-9 MICROFIX PORTABLE
EXAMPLE BATTERY GLIDE MEDICAL (RUGGEDIZED GENERATOR
COMPUTER GLIDE TRANSPORT APPLE
SYSTEM (BCS) sOMa AICRAFT COMPUTER)
DURATION* 4 TO8 2 TO5 1 TO3 1 YEAR 4 MONTHS
YEARS YEARS YEARS
* Nominal values, wide variances possible
Figure 16-2 Acquisition Spectrum
Logistics personnel will have to assert (a) Design Influence- Design influence is themselves to ensure that ILS receives the generally limited to the selection process.
resourees and attention required. In fact, Source selection criteria should therefore the impetus is on the staff to be sure that include:
the required planning, coordination, and -=
programiing are accomplished. o Utility of available operation and support manuals
Small programs have a small logistics
burden, however; as was pointed out above, o Similarity of current and intended they have a large aggregate impact. The use, support environment, and duty
Army, for instance, has approximately cycles thirty major systems and in excess of 300
non--major systems currently under devel- o Supportability-related design factors opment. It is important that ILS is applied
as necessary tc each non-major system o Compatibility with current support
develome,,t. equipment
16.3.2.2 Non-Developmental Systems. o Compatibility of design with Non-developmental systems (Figure 16-2) existing manpower skill categories include commercial items and materiel and training programs
developed by another U.S. military Service
or Government agency or country. Purchase o Availability of suppoitability data S of non-developmental items offers the and experience.
benefits of shortened acquisition time and
reduced cost. The logistic support chal- (b) ILS Resources - Funds must be pro- lenges of purchasing non-developmental grammed and budgeted for the performance
items include: of ILS tests and analyses normally con-
.1.
16-3 44
ducted during development, and for ac- cations. If commercial manuals are used, a quiring the ILS elements (see Chapter 8). management surveillance system is required to make sure that the contractor updates (c) ILS Planning - The planning require- the manuals when the equipment is changed.
ments in Chapter 2 are also applicable to The decision to use contractor support non-developmental systems. ILS plans may facilitates the use of commercial manuals.
be prepared to cover individual items or
categories of items (e.g., commercial test 16.4 RISK MANAGEMENT equipment). In either case, the contractor's
data and field experience will be helpful in 16.4.1 Accelerated Acquisitions structuring the plans.
16.4.1.1 Risk Area. Lead times for delivery (d) Maintenance Planning - The choice of non-developmental items can be ex- between contractor and organic support is tremely short, particularly for in-stock based on operational constraints, schedules, commercial items. This poses a substantial resources, and the mission of the user. When risk of deployment with incomplete or the non-developmental system is "off the inadequate logistic support and attendant shelf" and commercial/contractor support is degraded readiness.
chosen, minimal LSA and documenthtion is
required. In fact, use of the contractor's 16.4.1.2 Risk Handling. Applicable manage- support philosphy and support structure, ment approaches include:
e.g., skills, facilities, equipment, technical
documentation, and training may be a o Perform detailed logistics planning feasible alternative. If not, the support concurrently with development of should be tailored to the user's require- the acquisition strategy.
ments. When organic support is preferred,
but lead times are insufficient, interim o Determine the need and extent of contractor support may be necessary during contractor support required and the period required to establish an organic include appropriate logistic support
support capability. requirements in the solicitation.
(e) Supply Support - Non-developmental o Employ existing commercial or items pose the problem of securing a long other developmental data to
term source of spares and repair parts. compute supply support stockage Several alternatives are available. One, levels.
procure a life-time supply prior to termi-
nating the contract with the source, or two, o Consider use of reliability im- give selection preference to the commercial provement warranties to ennance product having the greatest likelihood of reliability.
having a long term supply.
o Schedule the time and budget the (f) Test and Evaluation - An evaluation of funds required for a supportability the military suitability and supportability of evaluation.
non-developmental items is required if
marketplace testing or other developmental 16.4.2 Configuration Control of Commer- data is inadequate or fails to address the cial Items
intended military environment.
16.4.2.1 Risk Area. The Government does (g) Technical Manuals - Commercial not control the configuration of items manuals should be used if feasible and if procured from the commercial marketplace.
they satisfy the requirements of the in- This presents two potential risks:
tended user. The alternative jq the commit-
ment of 2onsiderable time and money to o Subsequent competitive repro- convert the manuals to military specifi- curement of the end item may lead
16-4
to a totally different internal o Procurement of non-developmental configuration with different sup- items may offer substantial reduc-
port requirements. tions in total program cost and
acquisition time; however, the o There is no automatic guarantee reduction in time requires that that original commercial suppliers logistics planning be performed will continue to manufacture spares concurrent with development of the and repair parts to fit the Govern- acquisition strategy.
ment's configuration.
o Acquisition of non-major develop- 16.4.2.2 Risk Handling. These configuration mental items poses special con- risks may be reduced by the following: siderations because of the more general management and review o Post-production support planning procedures employed by the Serv- should be performed to determine ices. Logistics personnel have less viable alternatives such as buyouts, program supervision and broader
modifications, and Government responsibilities for each system.
manufacture (refer to Chapter 14
for additional information). o Viable mechanisms are available to attain readiness objectives for o Multi-year procurement from the non-developmental items. These same source at agreed upon prices include incorporation of support- should be considered in order to ability issues in the source selection decrease the impact of configura- process and use of existing LSA tion changes in follow-on procure- documentation.
ment.
16.6 REFERENCES o 're-solicitation market surveys
should be performed to determine 1. AR 70-1, System Acquisition the probable availability of a Policies and Procedures.
civilian after-market that will
supply components for an extended 2. AR 700-127, Integrated Logistic period. For example, when the Army Support.
procured commercial 1 1/4-ton
trucks in 1975, surveys indicated 3. SECNAV Instruction 5000.lB, that major components would System Acquisition.
remain available through the useful
life projected at that time. 4. OPNAV Instruction 5000.42B, H DT&E/Acquisition Procedures.
16.5 SUMMARY
5. AMC/TRADOC Pamphlet 70-7, o The military Services employ Non-Development Item Acquisition
decentralized acquisition and ILS (Draft).
management procedures for non-
major items. 6. AFR 800-2, Acquisition Program
Management.
o Review bodies and decision au-
thorities have been designated for 7. AFR 800-8, Integrated Logistics each category of non-major system Support Program.
to insure compliance with DoD
acquisition and ILS policies and 8. MCO 5000.10, Systems Acquisition
Service regulations. Management Manual.
CONTENTS
Chapter 17: JOINT SERVICE PROGRAMS
17.1 HIGHLIGHTS 17-1
17.2 INTRODUCTION 17-1
17.2.1 Purpose 17-1
17.2.2 Objective 17-1
17.3 MANAGEMENT ISSUES 17-1
17.3.1 Background 17-1
17.3.2 Joint Management Structure 17-1
17.3.3 Documentation of Joint Programs 17-1
17.3.4 ILS Funding for Joint Programs 17-2
17.3.5 Unique ILS Requirements 17-2
17.3.5.1 Logistic Support Analyses 17-3
17.3.5.2 Logistic Support Analysis Record (LSAR) 17-3
17.3.5.3 Technical Publications 17-3
17.3.5.4 Training 17-3
17.3.5.5 Depot Maintenance Interservicing (DMI) 17-3
17.4 RISK MANAGEMENT 17-3
17.5 SUMMARY 17-4
17.6 REFERENCES 17-4
17-i