ATT J16 GCSS-MC ECP DD1692-1.pdf

GCSS-MC ECPS TEMPLATE INSTRUCTIONS

(DD Form 1692-1, Modified 20141017)

Engineering Change Proposal, Page 1

It is essential that all blocks on ECP forms be completed correctly. “TBD” is not an acceptable block entry. If a block does not apply to an ECP, enter “N/A”. If the ECP originator does not know if a block is applicable or does not have the required data, “UNK” shall be entered to indicate unknown.

Block 1. Originator‘s Name and Address. Enter the name and address of the contractor or Government agency submitting the change proposal. The e-mail address is required.

Block 2. Date: Enter the ECP submittal date in the following format: YYYYMMDD.

Block 3. Procuring Activity No: Leave blank. The Program CCB Secretariat will assign the Control

Number.

Block 4. DODAAC: Enter the procuring activity DODAAC.

Block 5. Justification Code. Enter the justification code as follows:

B – Interface: Proposed change will eliminate interference or incompatibility at the interface between top-level CIs or between top-level CIs and GFE items.

C – Compatibility: Proposed change corrects a deficiency that meets all of the following conditions:

1. The item will not work without the change;

2. The deficiency was discovered during system testing or installation and checkout; and,

3. The originator acknowledges that completion of the change to the CI and documentation will not increase the scope of the existing contract.

D – Deficiency: Proposed change corrects design deficiencies.

O - Operational and Logistics Support: Proposed change causes a significant change in operational or logistic support requirements.

P - Production Stoppage: Proposed change is impractical and stops production or requires a delay in production.

R - Cost Reduction: Result of the change will be a cost savings to the Government and the ECP is not submitted pursuant to the value-engineering clause of a contract. The savings shall include all effects on cost under the immediate contract and from changes to delivered items, logistic support, and items produced by others.

S - Safety: The change is required to eliminate a hazardous condition.

V - Value Engineering: The change is submitted pursuant to the value engineering (VE) clause of a contract or is the result of a government VE study and it will also cause a net life cycle cost reduction. Value engineering ECPs shall include the words “Value Engineering Change Pursuant to Contract” at the top of page 1 of the ECP form.

Block 6. Class of ECP: Enter the classification, I or II, of the change.

Class I Criteria: An ECP proposing a change to an approved configuration item for which the Government is the contracting change authority or that has been included in the contract or Statement Of Work (SOW) by the tasking activity, and:

1. Affects any physical or functional requirement in approved functional or allocated configuration documentation, or

2. Affects any approved functional, allocated or product configuration documentation, and cost, warranties or contract milestones, or

3. Affects approved product configuration documentation and one or more of the following:

• Government furnished equipment (GFE),

• Safety

• Compatibility, interoperability, or logistics support

• Delivered technical manuals for which changes are not funded

• Will require retrofit of delivered units

• Preset adjustments or schedules affecting operating limits or performance to

• the extent that a new identification number is required

• Interchangeability, substitutability, or replaceability of any item down to

• non-repairable subassemblies

• sources on a source control drawing

• skills, manning, training, biomedical factors or human engineering design.

Class II Criteria: An ECP proposing a change to an approved configuration item for which the Government is the contracting change authority or that has been included in the contract or SOW by the tasking activity, and which is not Class I.

Block 7. Priority. A priority shall be assigned in accordance with Section 8 of the Program CMP.

Enter applicable code.

CODE PRIORITY CRITERIA

E Emergency 1. To effect a change in operational characteristics which, if not accomplished without delay, may seriously compromise national security;

2. To correct a hazardous condition which may result in fatal or serious injury to personnel or in extensive damage or destruction of equipment. ( A hazardous condition usually will require withdrawing the item from service temporarily, or suspension of the item operation, or discontinuance of further testing or development pending resolution of the condition); or

3. To correct a system halt (abnormal termination) in the production environment such that CSCI mission accomplishment is prohibited.

U Urgent 1. To effect a change which, if not accomplished expeditiously, may seriously compromise the mission effectiveness of deployed equipment, software, or forces;

2. To correct a potentially hazardous condition, the uncorrected existence of which could result in injury to personnel or damage equipment. (A potentially hazardous condition compromises safety and embodies risk, but within reasonable limits, permits continued use of the affected item provided the operator has been informed of the hazard and appropriate precautions have been defined and distributed to the user.)

3. To meet significant contractual requirements (for example, CODE PRIORITY CRITERIA when lead-time will necessitate slipping approved production or deployment schedules if the change was not incorporated).

4. To effect a significant net life cycle cost savings to the tasking activity, as defined in the contract, where expedited processing of the change will be a major factor in realizing lower costs accomplishment.

5. To effect an interface change which, if delayed, would cause a schedule slippage or increase cost.

6. To correct a condition causing unusable output information that is critical to mission accomplishment.

7. To correct critical CI files that are being degraded.

8. To effect a change in operational characteristics to implement a new or changed regulatory requirement with stringent completion date requirements issued by an authority higher than that of the functional proponent.

R Routine Emergency or urgent implementation is not applicable, required or justifiable.

Block 8. ECP Designation. Enter information in appropriate boxes:

a. Model/Type. Enter the common MK and MOD or type designation of the lowest assembly common to all “Lowest Assemblies Affected” identified in Block 18 in accordance with the Joint Electronics Type Designation System (JETDS).

b. CAGE Code: CAGE code of activity submitting the ECP.

c. System Designation: Enter the MK and MOD or type designation of the system of top-level CI. The approved Nomenclature/type designator for this system is GCSS-

MC

d. ECP No.: Enter the ECP number as provided by the GCSS-MC CM Manager.

e. Revision: Identifier for an ECP revision. Revision: Enter the ECP revision number as a number beginning with “1”. A change shall be revised when: (a) a major alteration or change to the initial change (or to an earlier version of the change) is necessary to describe the proposed change and (b) the Government concurs with the additional effort involved. A change revision shall consist of a complete document, which supersedes a previous submittal.

f. Type: Check Preliminary or Final ECP.

Block 9. Baseline Affected. Enter an “X” in one or more of the boxes according to the baseline(s) affected.

Block 10. Other System/CIs Affected. Enter an “X” in the “Yes” or “No” block, as applicable.

Supply full details in Blocks 31 and 32 on Page 2 of the ECP form.

Block 11. In Production. Check the “Yes” box if the system is operational/in production or check the “No” box if it is not.

Block 12. Specifications Design Documentation Affected - Test Plan. If specifications, Oracle

AIM/OUM documentation or test plans are affected by the ECP, enter the design activity CAGE code, document number, revision letter, and applicable document version number or Specification Change Notice or Notice Of Revision (NOR) number.

Block 13. Drawings Affected. Enter the number of the highest level affected drawing, the revision of the affected drawing, the number of the NOR, and the CAGE code of the design activity whose number is assigned to the listed drawing(s). All other drawings and all drawings directly referenced in the item specification(s) that are affected by the ECP shall be listed in an enclosure referenced in this block.

Block 14. Title of Change. Enter a brief descriptive title indicating the purpose of the change.

Block 15. Contract Number and Line Item. Enter the prime contract number and line item number from the contract applicable to the CI shown in Block 15.

Block 16. Configuration Item Nomenclature. Enter the common MK/MOD, Report/Interface/Conversion/Extension (RICE) or JETDS type designation and official nomenclature of all lowest assemblies affected identified in Block 18. In cases where an assembly identified in Block 18 is used in several configurations, the lowest common configuration for that assembly will be identified. For CSCIs, enter the CSCI name and number. The approved Nomenclature Assignment Request for the GCSS-MC program provides the system designation.

Block 17. Procuring Contracting Officer. Enter the code of the Procuring Contract Officer for the contract listed in Block 16.

Block 18. Lowest Assembly Affected

a. Nomenclature. Enter the lowest repairable part(s) affected. For CSCIs, enter the name of each lower level computer software component (CSC) and computer software unit affected.

b. Part No. Enter the part number of the lowest assembly(ies) affected. For CSCIs, enter the identifier of each lower level CSC and computer software unit affected.

c. NSN. Enter the National Stock Number of the lowest assembly(ies) affected.

Block 19. Description of Change. Describe the change in sufficient detail to allow complete understanding of the change and its impact. Describe which parts of the item or system are being changed and what type of change is being made. Identify maintenance changes.

Supplemental drawings and sketches shall be provided to clearly portray the proposed change. State if the proposed change is an interim solution.

Block 20. Need for Change. Describe the problem the ECP intends to correct or the new capability the ECP intends to provide. Use all available failure data. If the change will provide a new capability, improvements in range, speed, performance, endurance, striking power, defensive, or offensive capabilities, etc., describe the capability or impact in quantitative terms. Identify the change’s origin (e.g., Fleet CASREP, flag-level review, etc.)

Block 21. Effectivity by Environment. Select the appropriate environment, B1CM, Production

Support System (PSS), Enterprise/Operational/Deployed System, or Mobile Training Suite (MTS).

Block 22. Effect on Delivery Schedule. Enter the number of days that the delivery schedule will change by incorporating the ECP.

Block 23. Estimated Costs/Savings Under Contract. Enter the estimated costs/savings impact on the contract. This figure normally will be the same as that in column 5, line “e” of page 4.

Block 24. Estimated Net Total Costs/Savings. Enter the estimated costs/savings impact of the basic and all related ECPs including other costs/savings to the Government. This figure will normally be the same as that in the bottom line of column 6 on page 4. When there are related ECPs, this figure will normally be the same as that in column d, line “e” of page 5.

Block 25. Submitting Activity Authorizing Signature. An authorized official of the originating activity shall sign the ECP with official title.

a. Title. Title of the Authorizing Signature.

Block 26. Approval/Disapproval. ECPs shall be approved/disapproved as follows:

a. CCB Chairman Signature. The CCB Chairman/Co-Chairman shall review the ECP to confirm the correct classification, I or II; review for completeness and proper classification and to recommend approval or disapproval. The CCB Chairman shall sign and date the ECP.

b. Date. Date of signature by CCB Chairman/Co-Chairman and Decision.

c. Decision. Select the appropriate decision.

Engineering Change Proposal, Page 2

Block 27. Other Systems Affected. List the names and numbers of any other systems affected by this proposed engineering change.

Block 28. Other contractors/activities affected. Identify other contractors or government activities, which will be affected by this change.

Block 29. Configuration Items Affected. Enter the names and numbers of CIs and training and support/test equipment affected. This include identification of RICE.

Block 30. Effects on Performance Allocations and Interface in System Specifications. Describe changes in performance or interfaces, which have been defined in a requirement document.

Block 31. Effects on Employment, Integrated Logistics Support, Training, Operational

Effectiveness, or Software. Describe the effect of the proposed change on employment, logistics, personnel, training requirements, and software, which have been specified in a requirement document, including any changes or effects on system operability. For CSCIs, identify changes to databases, effects on computer operating time and cycle-time utilization, the net effect on software storage, and other relevant impacts on system utilization.

Block 32. Effects on Configuration Item Specifications. Describe in quantitative terms the effect on performance as it relates to parameters contained in the CI specifications/AIM/OUM documentation.

Block 33. Developmental Requirements and Status. When the proposed change requires a major revision of a development program, the nature of the new development program shall be described in detail including the status of programs already begun. For software, identify the scheduled sequence of computer software design and test activities, which will be required, any changes in schedule, which will be required, and the impact of the software change on hardware design and input/output cabling.

Block 34. Trade-Offs and Alternative Solutions. Enter a summary of the various solutions considered including the reasons for adopting the solution proposed by the change.

Block 35. Date by Which Contractual Authority is needed. Enter the date contractual authorization is required to maintain established schedules.

Engineering Change Proposal, Page 3

Block 36. Effects on Product Configuration Identification or Contract. Place an “X” in the appropriate box to indicate the effects on contract specifications and drawings. Reference enclosures, which describe proposed text changes in detail. Reference an enclosure, which defines the work scope of the proposed change as applicable to the contractor.

Block 37. Effect on Operational Employment. Place an “X” in the appropriate box to indicate the

ECP’s effects on the CI’s use. Reference an enclosure, which explains in detail. Use quantitative values whenever practical.

Block 38. Effect on Product Support Elements. Place an “X” in the appropriate box to indicate the

ECP’s effects on logistics support. Reference an enclosure, which explains in detail.

Block 39. Other Considerations. Place an “X” in the appropriate box to indicate the ECP’s effects on the factors listed within the block.

Block 40. Alternate Solutions. The originator shall determine if the problem for which the ECP was requested can be resolved by revising operational or maintenance procedures, revising inspection or servicing requirements, revising part replacement schedules, etc.

State the advantages and disadvantages of alternative approaches to the problem.

Block 41. Developmental Status. Identify testing results to date. When applicable, recommend additional tests, trials, installations, fit checks, etc. Indicate equipment availability for testing.

Block 42. Recommendations for Release to Operational System/Environment. Describe the reason for and steps required to retrofit the proposed ECP.

Block 43. Work-hours Per Unit to Install in Environments. Enter the work hours per retrofit kit installation by maintenance level.

Block 44. Work-hours to Conduct System Tests. Enter the estimated work-hours required to test the system.

Block 45. This Change Must Be Accomplished. Where previously approved ECPs must be incorporated in a specific order in relation to the proposed change, specify the order.

Block 46. Is Field Service Support Required? Check applicable box. If “Yes,” attach a proposed program for contractor participation.

Block 47. Out-of-Service Time. Enter the estimated time the CI will be out of service for retrofit.

Block 48. Effect of This ECP and Previously Approved ECPs on Configuration Item. When design limitations are being approached or exceeded, summarize the cumulative effect on performance, weight, electrical load, etc., caused by this and previously-approved changes.

Block 49. Date Contractual Authority Needed. Contractors shall provide the date by which they require contractual authority to proceed for both production and retrofit to maintain the estimated Effectivity specified in the ECP and to provide concurrent integrated logistic support and logistic support item deliveries.

Engineering Change Proposal, Page 4

Block 50. Estimated Total Cost Impact. Class I ECPs shall include the following information. All costs shall be documented. Statements such as “funded under separate correspondence” are not acceptable. Where costs have been funded or are considered within present budget, use a footnote to identify source. Enter “N/A” as required. Attach an enclosure, which justifies each estimate. Cost estimates are not contractually binding. Unless otherwise noted, the ECP originator shall address all cost issues and activities will add cognizant costs.

TOTAL (Recurring) cost shall be generated by multiplying the RECURRING UNIT Cost [column(2)] by the RECURRING QUANTITY [column (3)]. TOTAL [column (5)] is the sum of NON-RECURRING [column (1)] and TOTAL (Recurring) [column (4)].

Engineering Change Proposal (Hardware), Page 5 This page is required for ECP impacts on hardware schedules.

Block 51. Configuration Nomenclature.

Block 52. Title of Change.

Block 53. Date Authorization to Proceed.

Engineering Change Proposal (Software), Page 6 This page is required for ECP impacts on software schedules.

Block 54. Computer Software Item Nomenclature.

Block 55. Title of Change.

Block 56. Date Authorization to Proceed.

Engineering Change Proposal, Page 7: Continuation Sheet

Include related HPDM/Change Request numbers and issue summaries as well as associated Build numbers.