D.188.8.131.52 Block 23b. Ship/vehicle class affected. When the delivered CI is
installed in one or more ship/vehicle classes, enter the identification of
such classes. Not applicable when ECP Short Form procedure is specified by
D.184.108.40.206 Block 23c. Estimated kit delivery schedule. State estimated kit
delivery schedule by quantity and date. When special tooling for retrofit is
required for Government use, reference an enclosure in Block 23b on which is
specified the dates of availability of tools, jigs, and test equipment
required in conjunction with the kits to accomplish the change.
D.220.127.116.11 Block 23d. Locations or ship/vehicle numbers affected. State the
location(s) at which retrofit is to be accomplished. If retrofit is to be
accomplished in ships (or in vehicles for which the serial numbers are not
shown in Block 23), enter the ship hull numbers (or vehicle numbers). Not
applicable when ECP Short Form procedure is specified by contract. D.18.104.22.168
For CSCI's, this block shall apply if the change is part of a hardware or
equipment change and implementation of the CSCI change is per a hardware
retrofit schedule, or the fielded version of the software is to be replaced.
If the CSCI change is part of a larger hardware or equipment change and
incorporation of the CSCI change is per a hardware retrofit schedule, that
information will be included here either directly or by reference.
D.5.1.24 Block 24. Estimated costs/savings under contract. Enter the total
estimated costs/savings impact of the ECP on .he contract for the subject CI.
This Figure normally will be the same as that in column 5, line e, of DD Form
1692/3 (Page 4). savings shall be shown in parentheses.) .5.1.25 Block 25.
Estimated net total costs/savings. Enter the total estimated costs/savings
impact of the basic and all related ECPs, including other costs/savings to the
Government. This Figure normally will be the same as that in column 6 the
bottom line of Page 4 or, if there are related ECPs, in column 4, line e, of
Page 5. Not applicable when ECP Short Form procedures are specified by
D.5.1.26 Block 26. Submitting activity authorized signature. An authorized
official of the activity entered in Block 1 shall sign this block and provide
title in Block 26b. This indicates the ECP has the official sanction of the
D.5.1.27 Block 27. Approval/disapproval. This block is for use by the
Government. [Note: The Contract Administration Office will review all
engineering changes. It will recommend approval or disapproval of Class I ECPs
by marking Block 27a and completing Block 27d. It will concur or non-concur in
the classification of Class II engineering changes by marking Block 27c
accordingly and by completing Block 27d, 27e and 27f. When the Government
requires approval of Class II engineering changes prior to contractor
implementation, the designated approval activity will mark Block 27b
accordingly and will complete Block 27d. For Class I ECPs, the Government
contracting officer will mark Block 27g accordingly and will complete Block
27h, 27i and 27j.
D.5.2 DD Form 1692/1, "Engineering Change Proposal,
Paqe 2", Effects on Functional/Allocated Configuration Identification. DD Form
1692/1 (See Figure 9b
) is to be completed only if the proposed change affects the system
specification or the item development specification(s). If a separate product
function specification is used, effects on such specification of changes
proposed after the PBL has been established shall be described either on DD
Form 1692/2 (Page 3) or on enclosures referenced thereon.
D.5.2.1 ECP number. Enter the same ECP number as in Block 8d of DD Form
1692 (Page 1). If the ECP number is assigned on the basis of the system, the
system designation also shall be qiven.
D.5.2.2 Block 28. Other systems affected. Insert data when Block 7 of DD
Form 1692 (Page 1) is checked "yes".
D.5.2.3 Block 29. Other contractors/activities affected. Identify the other
contractors or Government activities which will be affected by this
D.5.2.4 Block 30. Configuration items affected. Enter the names and numbers
of all CIs, maintenance and operator training equipment, and support equipment
D.5.2.5 Block 31. Effects on Performance allocations and interfaces in
system specification. Describe in this block the changes in performance
allocations and in the functional/physical interfaces defined in the system
D.5.2.6 Block 32. Effects on employment, integrated logistic support,
traininq, operational effectiveness, or software.
a. For hardware, describe the effects of the proposed change on employment,
deployment, logistics, and/or personnel and training requirements which have
been specified in the approved system and/or CI specifications, including any
changes or effects on the operability of the system. In particular, there
shall be an entry detailing any effect on interoperability.
b. For CSCIs, the following information shall be entered as applicable to
the degree of design development of the CSCI at the time of ECP
(1) Identify any required changes to the data base parameters or values, or
to data base management procedures;
(2) Identify and explain any anticipated effects of the proposed change on
acceptable computer operating time and cycle-time utilization;
(3) Provide an estimate of the net effect on compu~er software storage;
(4) Identify and explain any other relevant impact of the proposed change
on utilization of the system.
D.5.2.7 Block 33. Effects on configuration item specifications. The effect
of the proposed change on performance shall be described in quantitative terms
as it relates to the parameters contained in the CI development
specifications. (See MIL-STD-490)
D.5.2.8 Block 34. Developmental requirements and status.
a. For hardware, when the proposed engineering change requires a major
revision of the development program (e.g., new prototypes, additional design
review activity, tests to be reaccomplished), the nature of the new
development program shall be described in detail, including the status of
programs already begun.
b. For CSCIs, the contractor shall identify the scheduled sequence of
computer software design and test activities which will be required. ECPs
initiated after preliminary design which affect the FBL and/or the ABL shall
identify, as appropriate, significant requirements for computer software
redesign, recoding, repetition of testing, changes to the software
engineering/test environments, special installation, adaptation, checkout, and
live environment testing. In addition, the specific impact of these factors on
approved schedules shall be identified. The impact of the software change on
the hardware design and input/ output cabling shall also be detailed.
D.5.2.9 Block 35. Trade-offs and alternative solutions. A summary of the
various solutions considered shall be included with an analysis showing the
reasons for adopting the solution proposed by the ECP.
D.5.2.10 Block 36. Date by which contractual authority is needed. Enter the
date contractual authority will be required in order to maintain the
D.5.3 DD Form 1692/2, "Engineering Change Proposal,
Paqe 3n, Effects on Product confiquration documentation, logistics and
operations. Certain information required on DD Form 1692/2 (See Figure 9c
) may have been required
on DD Form 1692 and 1692/1 (Pages 1 and 2) or does not apply to computer
software. When this information has already been supplied, a cross-reference
to such information will be adequate.
a. For hardware, if any specific logistic interoperability factors are
affected, the contractor shall provide information detailing the possible
impact on the operational configuration on an attached page.
b. For CSCIs, the software engineering and test environments are usually
not affected by changes in the product configuration of a CSCI. In Block 42,
the contractor shall provide information about the status of the software
redesign and retesting effort. There shall also be a review of the intent of
Blocks 40, 41, 45, 46, 47 and 49, to document CSCI impacts in these
D.5.3.1 ECP number. Enter the same ECP number as in Block 8d of DD Form
1692 (Page 1). If the number is assigned by system, include the system
D.5.3.2 Block 37. Effect on Product confiquration documentation or
contract. The effects on the approved CI product specifications shall be
described by reference to the SCNs, NORs or other enclosure(s) which cover
such proposed text changes in detail. The effects on performance, weight,
moment, etc., which are covered in the enclosure(s), shall be indexed by
proper identification adjacent to the factor affected. The effects on
drawings, when not completely covered on Page 1, shall be described in general
terms by means of a referenced enclosure. Such enclosure may consist of a list
of enclosed NORs if submittal of an NOR for each drawing affected is a
requirement of the contract. Indicate any technical data submittal which is
not provided for in the CDRL by means of a referenced enclosure. Address
nomenclature change when applicable.
D.5.3.3 Block 38. Effect on integrated logistics suport elements. The
effects of the engineering change on logistic support of the item shall be
indicated by checking the appropriate boxes. These effects shall be explained
in detail on an enclosure indexed by appropriate identification adjacent to
the subject under discussion. The information required shall indicate the
method to be used to determine the integrated logistic support plans and items
which will be required for the support of the new configuration as well as
retrofi..ing previously delivered items to the same configuration. The
following shall be covered as applicable:
a. Effects on schedule and content of the ILS plan.
b. Effect on maintenance concept and plans for the levels of maintenance
c. System and/or CI logistics support analysis (LSA) tasks (MIL-STD-1388-1)
to be accomplished and LSA data (MIL-STD-1388-2) requiring update wherever it
exists ln the contract.
d. Extension/revision of the interim support plan.
e. Spares and repair parts that are changed, modified, obsoleted or added,
including detailed supply data for interim support spares.
NOTE: Failure to include detailed supply data will delay ECP
f. Revised or new technical manuals.
g. Revised or new facilities requirements and site activation plan.
h. New, revised, obsoleted or additional support equipment (SE), test
procedures and software. For items of SE and trainers which require change,
furnish a cross reference to the related ECPs, and for any related ECP not
furnished with the basic ECP, furnish a brief description of the proposed
change(s) in SE and trainers.
i. Qualitative and quantitative personnel requirements data which identify
additions or deletions to operator or maintenance manpower in terms of
personnel skill levels, knowledge and numbers required to support the CI as
modified by the change.
j. New operator and maintenance training requirements in terms of training
equipment, trainers and training software for operator and maintenance
courses. This information should include identification of specific courses,
equipment, technical manuals, personnel, etc. required to set up the course at
either the contractor or Government facility.
k. See paragraph i above for instructions.
l. See paragraph j above for instructions.
m. Any effect on contract maintenance that increases the scope or dollar
limitation established in the contract.
n. Effects on packaging, handling, storage, and transportability resulting
from changes in materials, dimensions, fragility, inherent environmental or
D.5.3.4 Block 39. Effect on operational employment. The effects of the
engineering change of CI utilization shall be indicated by checking the
appropriate factors and providing details by enclosures. Quantitative values
shall be used whenever practicable but are required when reliability and
service life are impacted. Survivability includes nuclear