DI-MGMT-81232A

System Problem Report - SPR

The System Problem Report (SPR) identifies and reports hardware, software, and documentation anomalies prohibiting equipment from performing as specified during TPS development.

Approval DateOctober 8, 2019

AMSC NumberN10103

Preparing ActivityAS

Project NumberMGMT-2019-027

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

DI-MGMT-81232

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

This Data Item Description (DID) identifies anomalies prohibiting equipment from performing as specified. The anomaly can be related to hardware and software performance and documentation. This report will provide technical information to report anomalies for equipment.

This DID is applicable for use during all test program set (TPS) development program phases (design, integration, acceptance testing, and production).

This Data Item Description (DID) contains the format, content, and intended use information for the data deliverable resulting from the work task described in the contract.

This DID supersedes DI-MGMT-81232.

Preparation Instructions

1Reference Documents.None

2Format.Figure 1 provides a sample SPR format.

2.1General.The reports shall be written, single-spaced on one side only, single column, flush left, on good grade commercial white bond paper, 8 1/2 inches (width) by 11 inches (length) and 17 inches (width) by 11 inches (length) for foldouts. All pages of the report shall be of such legibility and contrast that every line, number, letter, and character is clear and readable. The left margin shall be wide enough so the test will not be obscured when the report is bound. Pages shall be sequentially numbered. All attachments shall be identified and referenced in the text of the report.

2.2Binding.The reports shall be bound in the most economical manner unless otherwise stated on DD Form 1423, Contract Data Requirement List (CDRL).

2.3Foldout Illustrations.Foldout illustrations should be avoided. However, if a foldout is necessary, the foldout shall not exceed 17 inches (width) by 11 inches (length).

3Content.The SPR shall include the following:

3.1SPR Number.The SPR number shall include the following: XXXXX-YYYYY-ZZZZ XXXXX: Up to five alphabetic characters representing the reporting activity. YYYYY: Five alphanumeric characters representing the ATE and configuration letters. ZZZZ: Sequential four digit numeral control number (leading zeros as necessary).

3.2Contractor.Identify the company or agency reporting the anomaly.

3.3Date.Enter the date of the report.

3.4Prepared Under Contract Number.Enter the contract number under which the anomaly is being reported by inserting the statement "Prepared under Contract Number #####-##-#-###."

3.5Problem Title.Enter a brief descriptive title of the anomaly.

3.6Priority.Include the conditions that impair schedule performance.

3.6.1Priority 01:The anomaly has created a work stoppage situation. Work cannot proceed and scheduled events lapse. A workaround is not possible.

3.6.2Priority 02:The anomaly, if not acted upon, will affect projected work schedule. Indicate when priority will change to Priority 1 if not corrected. A workaround may be possible, but will not affect schedule.

3.6.3Priority 03:The anomaly exists, but does not affect work schedule. A workaround is possible to correct the deficiency and does not affect schedule.

3.7TPS Affected.Enter the TPS affected by the anomaly. Use a separate report for each TPS affected.

3.8Problem Relation.Enter the general category the anomaly has effected (hardware, software, documentation).

3.9Hardware.Enter effected hardware model number, part number, and serial number and reference designator, if applicable.

3.10Software.Enter effected software, operating system, test executive, compiler, or post processor, as applicable. Include version number and date.

3.11Documentation.Enter the effected volume, book, chapter, page, paragraph, table, and figure, as applicable.

3.12Problem Description.Include schedule impact statement here. Include all substantial evidence describing the anomaly. Include, as applicable, program listings, print outs, figures, illustrations, and tables. Indicate, if a demonstration is required to manifest the anomaly.

3.13Action Taken/Recommended Workaround.Include all programming techniques required to work around the anomaly. Indicate if the workaround will be a permanent "fix" for the TPS or will be required to be removed prior to acceptance testing once the anomaly is resolved.

3.14Point of Contact.Include a point of contact in the event additional information is required.

References

—

Figures

Figure 1. System Problem Report Sample

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer