Exhibit A.pdf
PDF 1 MB Posted
- Attached to
- 2000ft-lbs. Force and Torque Calibrators
- Solicitation number
- N6426725R1020
About this file
This image is a standard Adobe PDF portfolio opening screen advising users to open the document in Acrobat X or Adobe Reader X or later versions. The screen displays the Adobe PDF logo, a red and white document graphic, and a "Get Adobe Reader Now!" button. The image provides technical guidance for optimal PDF viewing and does not contain substantive contract-related information.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP_N6426725R1020.pdf | ||
| Questions and Answers - N6426725R1020.docx | DOCX document | |
| Attachment 01 - CSS FY20-0007 PAX Torque_2000 ft-lb.pdf | ||
| Attachment 03_Cross_Reference_Matrix_N6426725R1020.xlsx | XLSX spreadsheet | |
| Attachment 02 -Small Business Subcontracting Plan Checklist.pdf | ||
| Exhibit B.pdf | ||
| RFP_N6426725R1020.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
For the best experience, open this PDF portfolio in
Acrobat X or Adobe Reader X, or later.
Get Adobe Reader Now!
DATA ITEM DESCRIPTION
Title: CALIBRATION CERTIFICATE/REPORT
Number: DI-QCIC-80798C Approved Date: 20170123 AMSC Number: F9766 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 36 Project Number: QCIC-2017-003 Applicable Forms: N/A Use/Relationship: The Calibration Certificate/Report documents calibration certificates or reports accompanying the calibrations performed on Department of Defense (DoD) test, measurement, and diagnostic equipment.
a. This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement as delineated in the contract.
b. This DID is applicable to contracts requiring calibration of test equipment prior to delivery.
This DID is consistent with ISO/IEC 17025, General requirements for the competence of testing and calibration laboratories, requirements for calibration reports or certificates.
(Copies of this document are available online at http://www.iso.org.)
c. This DID supersedes DI-QCIC-80798B.
Requirements:
1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2. Format. Contractor format is acceptable.
3. Content. The calibration certificate or report shall include:
a. Title (e.g., calibration certificate or calibration report);
b. The name and address of the laboratory and the location where the calibrations were carried out, if different from the address of the laboratory;
c. Unique identification of the calibration certificate or test report (such as the serial number), and on each page an identification in order to ensure that the page is recognized as a part of the test report or calibration certificate, and a clear identification of the end of the calibration certificate or test report;
d. The name and address of the client or customer;
e. Identification of the method used;
f. A description of, the condition of, and the unambiguous identification of the item(s) tested or calibrated;
g. The date of receipt of the test or calibration item(s) where this is critical to the validity and application of the results, and the date(s) of performance of the test or calibration;
DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:31Z Check the source to verify that this is the current version before use.
DI-QCIC-80798C
h. Reference to the sampling plan and procedures used by the laboratory or other bodies where these are relevant to the validity or application of the results;
i. The test or calibration results with, where appropriate, the units of measurement;
j. The name(s), function(s) and signature(s) or equivalent identification of person(s) authorizing the calibration certificate or test report;
k. Where relevant, a statement to the effect that the results relate only to the items tested or calibrated;
l. The conditions (e.g., environmental) under which the calibrations were made that have an influence on the measurement results;
m. The uncertainty of measurement or a statement of compliance with an identified metrological specification or clauses thereof;
n. Evidence that the measurements are traceable.
End of DI-QCIC-80798C.
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:31Z
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:28Z
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:28Z
Title: COMMERCIAL OFF-THE-SHELF (COTS) MANUALS AND ASSOCIATED
SUPPLEMENTAL DATA
Approval Date: 20211203 Limitation: No GIDEP Applicable: No
Number: DI-TMSS-80527D AMSC Number: 10283 DTIC Applicable: No Office of Primary Responsibility: TM
Applicable Forms: None
Use/relationship: Commercial Off-the-Shelf Manuals may be used as-is or with supplementation to support COTS equipment used by DOD. This DID is used to:
a. Acquire sample COTS manuals for evaluation.
b. Acquire COTS manuals that have been evaluated and found to be acceptable.
c. Acquire associated supplemental data, if required.
This DID contains format, content, and intended use information for the data deliverable(s) resulting from the work described in MIL-PRF-32216.
This DID supersedes DI-TMSS-80527C, dated 12 Aug 2011.
Requirements:
1. Content. The manual shall contain all technical information on the assembly, installation, operation, parts, and maintenance of commercial equipment.
2. Evaluation. The manual shall be evaluated using the criteria found in MIL-PRF-32216.
3. Supplementation. The manual may be supplemented with additional data to comply with contract.
Supplemental data shall be prepared in accordance with MIL-PRF-32216.
4. Format. The basic manual shall be presented in the contractor's format. Supplemental data shall be presented in the format specified by the acquiring activity.
5. Digital files. Interactive Electronic Technical Manuals (IETMs) or PDFs are preferred for electronic COTS manuals.
6. PDF Files. PDF files shall be searchable, capable of having links added, and have fonts embedded.
7. IETMs. IETMs shall meet the general style and format and user interface requirements in MIL- STD-40051-1 (Army only) or MIL-STD-3031 (Army only).
8. Paper manuals. If paper manuals are acquired, the data shall be clearly legible and on paper of sufficient quality for long term use.
9. Quick Reference Guides (QRGs). QRGs shall meet the requirements of MIL-PRF-32614.
End of DI-TMSS-80527D
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:50Z
DD FORM 1423-1, FEB 2001
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
PREVIOUS EDITION MAY BE USED.
Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE
7. DD 250 REQ
8. APP CODE
9. DIST STATEMENT
REQUIRED
10. FREQUENCY
11. AS OF DATE
12. DATE OF FIRST SUBMISSION
13. DATE OF SUBSEQUENT
SUBMISSION
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
Draft Final
Reg Repro
15. TOTAL
16. REMARKS
17. PRICE GROUP
18. ESTIMATED
TOTAL PRICE
J. DATE
Page of Pages
TBD A
QCIC
2k Force and Torque Calibrators N64267-25-R-1020 TBD
A001 CALIBRATION CERTIFICATION CALIBRATION REPORT WITH DATA
DI-QCIC-80798C SOW Paragraph 5.3.2 NAWCAD BL31400
LT
N/A C
As Generated
N/A
See Block 16
NAWCAD BL31400 0 1 0
NAWCAD BL14200 0 1 0
Copies w/ each unit 0 1 0
0 4 0
Block 4/5: DI-QCIC-80798C and SOW paragraph 5.3.2 are mandatory to the requirement and shall be used as guidance and are provided for reference.
Information items in DI-QCIC-80798C that are not relevant to the procured unit do not need to be included in format. Actual calibration data shall be contained in the calibration report related to the certificate.
Block 9: DISTRIBUTION Statement "C" will be added in accordance with DoD Directive 5230.24. Distribution Statement C. Distribution authorized to U.S.
Government Agencies and their contractors to protect publications required for official use or for administration or operational purposes only. (25 April 2025).
Other requests for this document shall be referred to NAWCAD Metrology and Calibration Office, ATTN: Calibration Standards Manager, NAWCAD, NAS Patuxent River, MD 20670-1118.
Block 10/12: Contractor shall provide the commercially available Calibration Certificate/Calibration Report with data, with each system delivered.
Block 14: Submission in contractor format is acceptable. Electronic format is preferred if in a widely available commercial document format such as MS-Excel or MS Word. Electronic submission of data is also accepted on CD-ROM.
Quantity and copies shall be provided in accordance with (IAW) CDRL distribution (Block 14). Addressee's POC information provided on CDRL supplemental page 2.
Block 16: This CDRL refers only to the format of the Calibration Report printed by the calibration standards, it is not intended that the contractor run actual US Navy workload for calibration.
NSP
1 2
4/28/25
16. REMARKS (Continued)
DD FORM 1423-1, FEB 2001 Page of Pages
TBD A QCIC
Box 14a Addressees:
2 2
INSTRUCTIONS FOR COMPLETING DD FORM 1423
(See DoD 5010.12-M for detailed instructions.)
FOR GOVERNMENT PERSONNEL
Item A. Self-explanatory.
Item B. Self-explanatory.
Item C. Mark (X) appropriate category: TDP - Technical Data Package;
TM - Technical Manual; Other - other category of data, such as "Provisioning,""Configuration Management," etc.
Item D. Enter name of system/item being acquired that data will support.
Item E. Self-explanatory (to be filled in after contract award).
Item F. Self-explanatory (to be filled in after contract award).
Item G. Signature of preparer of CDRL.
Item H. Date CDRL was prepared.
Item I. Signature of CDRL approval authority.
Item J. Date CDRL was approved.
Item 1. See DoD FAR Supplement Subpart 4.71 for proper numbering.
Item 2. Enter title as it appears on data acquisition document cited in Item 4.
Item 3. Enter subtitle of data item for further definition of data item (optional entry).
Item 4. Enter Data Item Description (DID) number, military specification number, or military standard number listed in DoD 5010.12-L (AMSDL), or one-time DID number, that defines data content and format requirements.
Item 5. Enter reference to tasking in contract that generates requirement for the data item (e.g., Statement of Work paragraph number).
Item 6. Enter technical office responsible for ensuring adequacy of the data item.
Item 7. Specify requirement for inspection/acceptance of the data item by the Government.
Item 8. Specify requirement for approval of a draft before preparation of the final data item.
Item 9. For technical data, specify requirement for contractor to mark the appropriate distribution statement on the data (ref. DoDD 5230.24).
Item 10. Specify number of times data items are to be delivered.
Item 11. Specify as-of date of data item, when applicable.
Item 12. Specify when first submittal is required.
Item 13. Specify when subsequent submittals are required, when applicable.
Item 14. Enter addressees and number of draft/final copies to be delivered to each addressee. Explain reproducible copies in Item 16.
Item 15. Enter total number of draft/final copies to be delivered.
Item 16. Use for additional/clarifying information for Items 1 through 15.
Examples are: Tailoring of documents cited in Item 4; Clarification of submittal dates in Items 12 and 13; Explanation of reproducible copies in Item 14.; Desired medium for delivery of the data item.
FOR THE CONTRACTOR
Item 17. Specify appropriate price group from one of the following groups of effort in developing estimated prices for each data item listed on the DD Form 1423.
a. Group I. Definition - Data which is not otherwise essential to the contractor's performance of the primary contracted effort (production, development, testing, and administration) but which is required by DD Form 1423.
Estimated Price - Costs to be included under Group I are those applicable to preparing and assembling the data item in conformance with Government requirements, and the administration and other expenses related to reproducing and delivering such data items to the Government.
b. Group II. Definition - Data which is essential to the performance of the primary contracted effort but the contractor is required to perform additional work to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, or quality of the data item.
Estimated Price - Costs to be included under Group II are those incurred over and above the cost of the essential data item without conforming to Government requirements, and the administrative and other expenses related to reproducing and delivering such data item to the Government.
c. Group III. Definition - Data which the contractor must develop for his internal use in performance of the primary contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of content, format, frequency of submittal, preparation, control, and quality of the data item.
Estimated Price - Costs to be included under Group III are the administrative and other expenses related to reproducing and
d. Group IV. Definition - Data which is developed by the contractor as part of his normal operating procedures and his effort in supplying these data to the Government is minimal.
Estimated Price - Group IV items should normally be shown on the DD Form 1423 at no cost.
Item 18. For each data item, enter an amount equal to that portion of the total price which is estimated to be attributable to the production or development for the Government of that item of data.
These estimated data prices shall be developed only from those costs which will be incurred as a direct result of the requirement to supply the data, over and above those costs which would otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any amount for rights in data. The Government's right to use the data shall be governed by the pertinent provisions of the contract.
DD FORM 1423-1 (BACK), FEB 2001
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the
QCIC
A002 INSTRUMENT CALIBRATION PROCEDURE INSPECTION AND TEST PLAN
DI-QCIC-81110 SOW Paragraph 5.3.3 NAWCAD BL31400
No
A C
NAWCAD BL31400 1 1 0
NAWCAD BL14200 1 1 0
3 4 0
Block 4/5: DI-QCIC-81110 and SOW paragraph 5.3.3 are mandatory to the
Block 8: Instrument Calibration Procedure (CDRL A002) requires government approval. The contractor shall provide a preliminary draft of the Analysis of the Measurement Uncertainty to the Government for review, comment, and approval of the format no later than (NLT) 60 calendar days prior to initial operating capability (IOC) for each system. IOC shall be defined as the delivery date of the initial order of system(s). Government will provide the contractor with approval/disapproval of format including comments within 30 days of receipt of preliminary draft. Contractor shall provide a government approved final version with incorporated comments NLT 30 days prior to IOC for first system.
Government Agencies and their contractors to protect publications required for official use or for administration or operational purposes only. (25 April 2025).
Other requests for this document shall be referred to NAWCAD Metrology and
Block 10: The Contractor shall provide the manufacture's Instrument Calibration Procedure.
Block 11/12: Submissions shall be provided with each System delivered as specified in the delivery schedule of the contract.
or MS Word. Electronic submission of data is also accepted on CD-ROM.
Quantity and copies shall be provided in accordance with (IAW) CDRL distribution (Block 14). Addressee's POC information provided on CDRL supplemental page 2.
TBD A QCIC
Block 14a Addressees:
conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the
IPSC
A003 SOFTWARE VERSION DESCRIPTION SOFTWARE VERSION DESCRIPTION
DI-IPSC-81442A SOW Paragraph 5.3.4 NAWCAD BL31400
As Required
NAWCAD BL31400
1 1 0
Copies with each un 0 1 0
Block 4/5: DI-IPSC-81442A and SOW paragraph 5.3.4 are mandatory to the
Block 8: Prior notification and government approval of all Software Version Description(s) (CDRL A003 subtitle) for each system is required by the government. Contractor shall provide a Software Version Description to the government for review, comment, and approval no later than (NLT) 15 calendar days prior to installation of software and/or firmware revisions to any system.
Government comments with or without approval will be provided to the contractor within 15 days of receipt of Software Version Description providing information explained in DI-IPSC-81442A. The firmware and software used to operate each and every calibration standard procured on any individual delivery order under this contract shall be of the same release and version. The contractor shall provide the US Government the release and/or version number of each item of firmware and software included in the calibration standard. No deviation or substitution of firmware and/or software shall be done without the approval of the US Government.
Government Agencies and their contractors to protect publications required for official use or for administration or operational purposes only. (25 April 2025).
Other requests for this document shall be referred to NAWCAD Metrology and
Block 10: The contractor shall submit the Software Version Description A003 whenever a new software version is released.
Block 11/12/13: Submission(s) of Software Version Description (s) apply to new systems and shall be provided to the government prior to each software/firmware change to the Initial Operating Capability (IOC) of each system. IOC of a system is defined as its delivery date.
TBD A IPSC
Block 14: Submission in contractor format is acceptable. Electronic format is preferred if in a widely available commercial document format such as MS-Excel or MS Word. Electronic submission of data is also accepted on CD-ROM. Quantity and copies shall be provided IAW CDRL distribution (Block 14).
conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the
MISC
A004 SOFTWARE/FIRMWARE CHANGE REQUEST SOFTWARE/FIRMWARE CHANGE
REQUEST
DI-MISC-81807 SOW Paragraph 5.3.5 NAWCAD BL31400
LT
As Required
NAWCAD BL14200 0 1 0
Copies with each un 0 1 0
0 4 0
Block 4/5: DI-MISC-81807 and SOW paragraph 5.3.5 are mandatory to the
Government Agencies and their contractors to protect publications required for official use or for administration or operational purposes only. (25 April 2025).
Other requests for this document shall be referred to NAWCAD Metrology and
Block 10/11/12/13: Submission(s) of Software/Firmware Change Request(s) apply to both new and upgraded systems and shall be provided to the government prior to each software/firmware change to the initial operating capability (IOC) of each system. Upgraded systems are defined as systems bought under contract number N64267-25-R-1020, in accordances with CDRL A004, to at an earlier date whether its under warranty or not.
or MS Word. Electronic submission of data is also accepted on CD-ROM.
Quantity and copies shall be provided IAW CDRL distribution (Block 14).
Addressee's POC information provided on CDRL supplemental page 2.
TBD A MISC
conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services and Communications Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the
TMSS
T001 COMMERCIAL OFF-THE-SHELF(COTS) MANUALS
AND ASSOCIATED SUPPLEMENTAL DATA
DI-TMSS-80527D See Block 16 NAWCAD BL31400
A C
Block 4/5: DI-TMSS-80527D and SOW paragraphs 5.2.2, 5.3.1 and 5.3.6 are mandatory to this requirement and shall be used as guidance and are provided for reference.
Block 8: Commercial Off-The-Shelf (COTS) Manuals and Associated Supplemental Data (CDRL T001) requires government approval. The contractor shall provide a preliminary draft of the Analysis of the Measurement Uncertainty to the Government for review, comment, and approval of the format no later than (NLT) 60 calendar days prior to initial operating capability (IOC) for each system.
IOC shall be defined as the delivery date of the initial order of system(s).
Government will provide the contractor with approval/disapproval of content and/or format including comments within 30 days of receipt of preliminary draft.
Contractor shall provide a government approved final version with incorporated comments NLT 30 days prior to IOC. IOC shall be considered the delivery date for the first system(s) ordered by the government.
Government Agencies and their contractors to protect publications required for official use or for administration or operational purposes only. (25 April 2025).
Other requests for this document shall be referred to NAWCAD Metrology and
Block 10 Frequency: Contractor shall provide the commercially available Operators/Service Manual(s) with each system delivered.
Block 12/13: Date of Subsequent: Submissions of Operator/Service Manual(s) shall be provided with each new system being delivered.
desired and acceptable if in MS-Excel or MS Word. Electronic submission of data shall also be on CD-ROM and/or DvD media. Qty. (1) Operator/Service Manual shall be shipped with each Calibration Standard installed. Quantity and copies shall be provided IAW CDRL T001 distribution ( Copies with each unit delivered) Block 14a. Addressee's POC information provided on CDRL supplemental page 2.
TBD A TMSS
Block 14a. Addressees:
Block 16: The United States Government shall have limited technical data rights for all technical manuals and documents furnished with the procured commercial items, for the purpose of Government use only in duplicating or posting technical documentation to limited access web sites for use by US Government Personnel and Contractors engaged in maintenance, calibration or related logistics activities associated with the procured commercial items in accordance with DFARS 252.227-7015 Technical Data--Commercial Items.
conformance with Government requirements, and the required to perform additional work to conform to Government without conforming to Government requirements, and the contracted effort and does not require any substantial change to conform to Government requirements with regard to depth of otherwise be incurred in performance of the contract if no data were required. The estimated data prices shall not include any
DATA ITEM DESCRIPTION Form Approved
OMB NO.0704-0188
Public reporting burden for collection of this information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to Washington Headquarters Services, Directorate of Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington , DC 20503.
1. TITLE
SOFTWARE VERSION DESCRIPTION (SVD)
2. IDENTIFICATION NUMBER
DI-IPSC-81442
3. DESCRIPTION/PURPOSE
3.1 The Software Version Description (SVD) identifies and describes a software version consisting of one or more Computer Software Configuration Items (CSCIs). It is used to release, track, and control software versions.
3.2 The term "version" may be applied to the initial release of the software, to a subsequent release of that software, or to one of multiple forms of the software released at approximately the same time (for example, to different sites).
4. APPROVAL DATE
(YYMMDD) 941205
5. OFFICE OF PRIMARY RESPONSIBILITY
EC
6a. DTIC APPLICABLE 6b. GIDEP APPLICABLE
7. APPLICATION/INTERRELATIONSHIP
7.1 This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by specific and discrete task requirements as delineated in the contract.
7.2 This DID is used when the developer is tasked to identify and record the exact version of software to be delivered to a user, support, or other site.
7.3 The Contract Data Requirements List (CDRL) (DD 1423) should specify whether deliverable data are to be delivered on paper or electronic media; are to be in a given electronic form (such as ASCII, CALS, or compatible with a specified word processor or other support software); may be delivered in developer format rather than in the format specified herein; and may reside in a computer-aided software engineering (CASE) or other automated tool rather than in the form of a traditional document.
7.4 This DID supersedes DI-MCCR-80013A, and DI-MCCR-80312.
8. APPROVAL LIMITATION
Limited Approval from 12/5/94 through 12/5/96
9a. APPLICABLE FORMS 9b. AMSC NUMBER
N7085
10. PREPARATION INSTRUCTIONS
10.1 General instructions.
a. Automated techniques. Use of automated techniques is encouraged. The term "document" in this DID means a collection of data regardless of its medium.
b. Alternate presentation styles. Diagrams, tables, matrices, and other presentation styles are acceptable substitutes for text when data required by this DID can be made more readable using these styles.
(Continued on Page 2)
11. DISTRIBUTION STATEMENT
DISTRIBUTION STATEMENT A. Approved for public release; distribution is unlimited.
DD Form 1664, APR 89 Previous editions are obsolete Page 1 of 4 Pages 135/123
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:17Z
Software Version Description (SVD)
10. PREPARATION INSTRUCTIONS -- 10.1 General Instructions (continued)
c. Title page or identifier. The document shall include a title page containing, as applicable:
document number; volume number; version/revision indicator; security markings or other restrictions on the handling of the document; date; document title; name, abbreviation, and any other identifier for the system, subsystem, or item to which the document applies;
contract number; CDRL item number; organization for which the document has been prepared; name and address of the preparing organization; and distribution statement. For data in a database or other alternative form, this information shall be included on external and internal labels or by equivalent identification methods.
d. Table of contents. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix. For data in a database or other alternative form, this information shall consist of an internal or external table of contents containing pointers to, or instructions for accessing, each paragraph, figure, table, and appendix or their equivalents.
e. Page numbering/labeling. Each page shall contain a unique page number and display the document number, including version, volume, and date, as applicable. For data in a database or other alternative form, files, screens, or other entities shall be assigned names or numbers in such a way that desired data can be indexed and accessed.
f. Response to tailoring instructions. If a paragraph is tailored out of this DID, the resulting document shall contain the corresponding paragraph number and title, followed by "This paragraph has been tailored out." For data in a database or other alternative form, this representation need occur only in the table of contents or equivalent.
g. Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability.
h. Standard data descriptions. If a data description required by this DID has been published in a standard data element dictionary specified in the contract, reference to an entry in that dictionary is preferred over including the description itself.
i. Substitution of existing documents. Commercial or other existing documents may be substituted for all or part of the document if they contain the required data.
10.2 Content requirements. Content requirements begin on the following page. The numbers shown designate the paragraph numbers to be used in the document. Each such number is understood to have the prefix "10.2" within this DID. For example, the paragraph numbered 1.1 is understood to be paragraph 10.2.1.1 within this DID.
10. PREPARATION INSTRUCTIONS -- 10.2 Content Requirements (continued)
1. Scope. This section shall be divided into the following paragraphs.
1.1 Identification. This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s). It shall also identify the intended recipients of the SVD to the extent that this identification affects the contents of the software released (for example, source code may not be released to all recipients.)
1.2 System overview. This paragraph shall briefly state the purpose of the system and the software to which this document applies. It shall describe the general nature of the system and software; summarize the history of system development, operation, and maintenance;
identify the project sponsor, acquirer, user, developer, and support agencies; identify current and planned operating sites; and list other relevant documents.
1.3 Document overview. This paragraph shall summarize the purpose and contents of this document and shall describe any security or privacy considerations associated with its use.
2. Referenced documents. This section shall list the number, title, revision, and date of all documents referenced in this document. This section shall also identify the source for all documents not available through normal Government stocking activities.
3. Version description. This section shall be divided into the following paragraphs.
3.1 Inventory of materials released. This paragraph shall list by identifying numbers, titles, abbreviations, dates, version numbers, and release numbers, as applicable, all physical media (for example, listings, tapes, disks) and associated documentation that make up the software version being released. It shall include applicable security and privacy considerations for these items, safeguards for handling them, such as concerns for static and magnetic fields, and instructions and restrictions regarding duplication and license provisions.
3.2 Inventory of software contents. This paragraph shall list by identifying numbers, titles, abbreviations, dates, version numbers, and release numbers, as applicable, all computer files that make up the software version being released. Any applicable security and privacy considerations shall be included.
3.3 Changes installed. This paragraph shall contain a list of all changes incorporated into the software version since the previous version. If change classes have been used, such as the Class I/Class II changes in MIL-STD-973, the changes shall be separated into these classes.
This paragraph shall identify, as applicable, the problem reports, change proposals, and change notices associated with each change and the effects, if any, of each change on system operation and on interfaces with other hardware and software. This paragraph does not apply to the initial software version.
3.4 Adaptation data. This paragraph shall identify or reference all unique-to-site data contained in the software version. For software versions after the first, this paragraph shall describe changes made to the adaptation data.
10. PREPARATION INSTRUCTIONS -- 10.2 Content Requirements (continued)
3.5 Related documents. This paragraph shall list by identifying numbers, titles, abbreviations, dates, version numbers, and release numbers, as applicable, all documents pertinent to the software version being released but not included in the release.
3.6 Installation instructions. This paragraph shall provide or reference the following information, as applicable:
a. Instructions for installing the software version
b. Identification of other changes that have to be installed for this version to be used, including site-unique adaptation data not included in the software version
c. Security, privacy, or safety precautions relevant to the installation
d. Procedures for determining whether the version has been installed properly
e. A point of contact to be consulted if there are problems or questions with the installation
3.7 Possible problems and known errors. This paragraph shall identify any possible problems or known errors with the software version at the time of release, any steps being taken to resolve the problems or errors, and instructions (either directly or by reference) for recognizing, avoiding, correcting, or otherwise handling each one. The information presented shall be appropriate to the intended recipient of the SVD (for example, a user agency may need advice on avoiding errors, a support agency on correcting them).
4. Notes. This section shall contain any general information that aids in understanding this document (e.g., background information, glossary, rationale). This section shall include an alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and a list of any terms and definitions needed to understand this document.
A. Appendixes. Appendixes may be used to provide information published separately for convenience in document maintenance (e.g., charts, classified data). As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes may be bound as separate documents for ease in handling.
Appendixes shall be lettered alphabetically (A, B, etc.).
Data Item Description
Title: Software/Firmware Change Request Approval Date: 20100420 Number: DI-MISC-81807 Limitation: N/A AMSC Number: N9130 GIDEP Applicable: N/A DTIC Applicable: N/A Office of Primary Responsibility: SH/PMS-408 Applicable Forms: N/A
Use/relationship: The Software/ Firmware Change Request will be used to alert or inform the government about changes to software and firmware and also to provide detailed information to the government about the changes and the estimated cost of the software/firmware changes.
This DID contains the format, content and preparation instructions for the data product generated by the specific and discrete work task requirement as delineated in the contract.
Requirements:
1. Reference Documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions shall be as specified in the contract.
2. Format. The Software/Firmware Change Request shall be presented in the Contractor’s format.
3. Content. The Software/Firmware Change Request shall contain all the information identified in Figures 1-7.
4. End of DI-MISC-81807.
Page 1 of 8 Pages
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:37Z
DI-MISC-81807
SOFTWARE CHANGE REQUEST (SCR), PAGE 1
2. DATE
3. JUSTIFICATION CODE
1. ORIGINATOR NAME AND ADDRESS (include e-mail address and telephone number)
Name:
Organization:
Street 1:
Street 2:
City, State, Zip Code:
Telephone Number: ( ) ext:: E-mail address:
4. TYPE OF SCR
Class I Class II
5. PRIORITY
Emergency Urgent Routine
6. SCR DESIGNATION 7. BASELINE AFFECTED
a. CI/CSCI AFFECTED
b. CAGE CODE
c. SYSTEM DESIGNATION
FUNCTIONAL ALLOCATED PRODUCT
d. SCR No.
e. REVISION
f. TYPE Preliminary
8. OTHER SYS/CONFIG ITEMS AFFECTED
YES NO
9. IN PRODUCTIO N
10. DOCUMENTS AFFECTED
CAGE CODE SPEC/DOC NO. REVISION SCN/NOR/ECN/ECO NO.
11. TITLE OF CHANGE
12. CONTRACT NO. & LINE ITEM
13. CONFIGURATION ITEM NOMENCLATURE
14. PROCURING CONTRACTING OFFICER
15. LOWEST ASSEMBLY AFFECTED
a. NOMENCLATURE
b. PART NO.
16. DESCRIPTION OF CHANGE
17. NEED FOR CHANGE
18. PRODUCTION EFFECTIVITY BY SERIAL NUMBER
19. EFFECT ON PRODUCTION DELIVERY
SCHEDULE
20. RETROFIT
a. RECOMMENDED ITEM EFFECTIVITY
b. ESTIMATED KIT DELIVERY SCHEDULE
c. PLATFORMS AFFECTED
21. ESTIMATED COST or (SAVINGS) UNDER CONTRACT
No Additional Cost/Savings – In Scope of the Contract
22. SUBMITTING ACTIVITY AUTHORIZING SIGNATURE
22a. TITLE
23. APPROVAL/DISAPPROVAL
a. LCCB CHAIRMAN
DATE :
RECOMMEND APPROVAL
RECOMMNED DISAPPROVAL
b. CCB CHAIRMAN
DATE :
APPROVED
DISAPPROVED
Figure 1 Page 2 of 8 Pages
SOFTWARE CHANGE REQUEST (SCR), Figure 2
SCR NUMBER & REV:
EFFECT ON FUNCTIONAL/ALLOCATED CONFIGURATION IDENTIFICATION
24. OTHER SYSTEMS AFFECTED
25. OTHER CONTRACTORS/ACTIVITIES AFFECTED
26. CONFIGURATION ITEMS AFFECTED
27. EFFECTS ON PERFORMANCE ALLOCATIONS AND INTERFACES IN SYSTEM SPECIFICATION
28. EFFECTS ON EMPLOYMENT, INTEGRATED LOGISTICS SUPPORT, TRAINING, OPERATIONAL, EFFECTIVENESS, OR SOFTWARE
29. EFFECTS ON CONFIGURATION ITEM SPECIFICATIONS
30. DEVELOPMENTAL REQUIREMENTS AND STATUS
31. TRADE-OFFS AND ALTERNATIVE SOLUTIONS
32. DATE BY WHICH CONTRACTUAL AUTHORITY IS NEEDED
Figure 2 Page 3 of 8 Pages
SOFTWARE CHANGE REQUEST (SCR), Figure 3
SCR NUMBER & REV:
EFFECTS ON PRODUCT CONFIGURATION IDENTIFICATION, LOGISTICS, AND OPERATIONS
(X) FACTOR ENCL. PAR. (X) FACTOR ENCL. PAR.
33. EFFECT ON PRODUCT CONFIGURATION
IDENTIFICATION OR CONTRACT
35. EFFECT ON OPERATIONAL
EMPLOYMENT
a. PERFORMANCE a. SAFETY
b. WEIGHT-BALANCE STABILITY (Aircraft) N/A N/A b. SURVIVABILITY
c. WEIGHT-MOMENT (Other equipment) N/A N/A c. RELIABILITY
d. CDRL, TECHNICAL DATA d. MAINTAINABILITY
e. NOMENCLATURE e. SERVICE LIFE
f. OPERATING PROCEDURES
g. ELECTROMAGNETIC INTERFERENCE 34. EFFECT ON INTEGRATED LOGISTICS
SUPPORT (ILS) ELEMENTS
h. ACTIVATION SCHEDULE
a. ILS PLANS i. CRITICAL SINGLE POINT FAILURE ITEMS
b. MAINTENANCE CONCEPT, PLANS, PROCEDURES j. INTEROPERABILITY c LOGISTICS SUPPORT ANALYSIS
d. INTERIM SUPPORT PROGRAMS 36. OTHER CONSIDERATIONS
e. SPARES AND REPAIR PARTS N/A N/A a. INTERFACE
f. TECH MANUALS/PROGRAMMING TAPES b. OTHER AFFECTED EQUIPMENT/GFE/GFP N/A N/A
g. FACILITIES N/A N/A c. PHYSICAL CONSTRAINTS N/A N/A P h. SUPPORT EQUIPMENT N/A N/A d. COMPUTER PROGRAMS AND RESOURCES
i. OPERATOR TRAINING e. REWORK OF OTHER EQUIPMENT N/A N/A
j. OPERATING TRAINING EQUIPMENT f. SYSTEM TEST PROCEDURES
k. MAINTENANCE TRAINING g. WARRANTY/GUARANTEE
l. MAINTENANCE TRAINING EQUIPMENT h. PARTS CONTROL N/A N/A
m. CONTRACT MAINTENANCE i. ENVIRONMENTAL
n. PACKAGING , HANDLING, STORAGE, AND
TRANSPORTABILITY
N/A N/A j. FMS RELEASE
37. ALTERNATE SOLUTIONS
38. DEVELOPMENTAL STATUS
39. RECOMMENDATIONS FOR RETROFIT
40. WORK-HOURS PER UNIT TO INSTALL RETROFIT KITS
a. ORGANIZATION
b. INTERMEDIATE
c. DEPOT
d. OTHER
41. WORK-HOURS TO CONDUCT SYSTEM TESTS AFTER RETROFIT
42. THIS CHANGE MUST BE ACCOMPLISHED
BEFORE WITH AFTER THE FOLLOWING CHANGES:
43. IS CONTRACTOR FIELD
SERVICE ENGINEERING
REQUIRED?
44. OUT-OF-SERVICE TIME
45. EFFECT OF THIS SCR AND PREVIOUSLY APPROVED SCRs
46. DATE CONTRACTUAL AUTHORITY NEEDED
FOR PRODUCTION:
FOR RETROFIT:
Figure 3 Page 4 of 8 Pages
Figure 4 Page 5 of 8 Pages
SOFTWARE CHANGE REQUEST (SCR), Figure 5 SCR NUMBER and REV:
48. ESTIMATED COSTS SAVINGS/SUMMARY, RELATED SCRs (Use parentheses for savings)
FACTOR
CAGE CODE
(a)
SCR NUMBER
(b)
COSTS/SAVINGS
UNDER CONTRACT
(c)
OTHER COSTS/
SAVINGS
(d)
a. PRODUCTION COST/SAVING (Subtotal of Costs/Savings Elements from block 51a applicable to aircraft, ship, tank, vehicle, missile, or its subsystem)
SUBTOTAL PRODUCTION COSTS/SAVINGS
b. RETROFIT COSTS (Applicable to aircraft, ship, tank, vehicle, missile, or its subsystem)
SUBTOTAL RETROFIT COSTS
c. INTEGRATED LOGISTICS SUPPORT COSTS/SAVING REVISED
REQUIREMENTS
(1) ITEM RETROFIT (If not covered under “b”) (Applicable to aircraft, ship tank, vehicle, missile, or its subsystem)
(2) ILS SUBTOTAL (Applicable to aircraft, ship, tank, vehicle, missile or its subsystem)
(3) OPERATOR TRAINER (Net total cost/saving from each SCR covering operator trainer)
(4) MAINTENANCE TRAINER (Net total cost/saving from each SCR covering maintenance trainer)
(5) OTHER TRAINING EQUIPMENT
(6) SUPPORT EQUIPMENT (Net total cost/saving from each SCR on support equipment)
(7) ILS PLANS
(8) MAINTENANCE CONCEPT, PLANS, SYSTEM DOCUMENTS
(9) INTERIM SUPPORT PLAN
RECURRING COSTS
NEW REQUIREMENTS
PROCURIN
G
ACTIVITY
CODE
NON-
RECURRING
COSTS UNIT QTY TOTAL
(10) PROVISIONING DOCUMENTATION
(11) OPER TRNR/TRNG DEVICES/EQUIP
(12) MANUALS/PROGRAMMING TAPES, SPARES,
REPAIR PARTS (For 11)
(13) MAINTENANCE TRNR/TRNG DEVICES/
EQUIPMENT
(14) MANUALS/PROGRAMMING TAPES, SPARES,
REPAIR PARTS (For 13)
(15) SUPPORT EQUIPMENT
(16) MANUALS/PROGRAMMING TAPES (For 15)
(17) PROVISIONING DOCUMENTATION (For 15)
(18) REPAIR PARTS (For 15) N/A N/A N/A N/A N/A N/A N/A
(19) SUBTOTAL ILS COSTS/SAVINGS (Sum of c. 1 through c. 18)
CAGE CODE SCR NUMBER
d. OTHER COSTS/SAVINGS (Total from block 48d of related SCRs)
TOTAL OTHER COSTS/SAVINGS
SUBTOTALS OF COLUMNS
SUBTOTAL UNDER CONTRACT
Figure 5 Pages 6 of 8 Pages
SOFTWARE CHANGE REQUEST (SCR), Figure 6
SCR NUMBER and REV:
49. TITLE OF CHANGE
50. DATE AUTHORIZATION TO PROCEED
RECEIVED BY CONTRACTOR (YYMMDD)
S START DELIVERY C COMPLETED DELIVERY PROGRESS POINT
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
Figure 6 Page 7 of 8 Pages a.
C O
(1) Software Engineering
N F I
(2) Software Documentation
G U R
(3) Software Engineering Test
A T
(4) Update TDP b.
S
(1) Software Engineering Environment Upgrade
P
(2) Software Test Environment Upgrade
E Q
M c.
(1) Operator
A
(2) Maintenance
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 2
26 27 28 29 30 31 32 33 34 35 36
SOFTWARE CHANGE REQUEST (SCR), Continuation Sheet, Figure 7
TITLE OF CHANGE
SCR NUMBER and REV:
PARAGRAPH# BLOCK/LINE NO. BLOCK TITLE AND SUPPLEMENTARY INFORMATION
Figure 7 Page 8 of 8 Pages
23. APPROVAL/DISAPPROVAL
Figure 1 Page 2 of 8 Pages
SOFTWARE CHANGE REQUEST (SCR), Figure 2
SCR NUMBER & REV:
SOFTWARE CHANGE REQUEST (SCR), Figure 3
SCR NUMBER & REV:
SCR NUMBER and REV:
SOFTWARE CHANGE REQUEST (SCR), Figure 6
SCR NUMBER and REV:
SCR NUMBER and REV:
Title: PROPOSED SPARE PARTS LIST Number: DI-PSSS-80134B Approval Date: 20171107 AMSC Number: F9866 Limitation: N/A DTIC Applicable: No GIDEP Applicable: No Preparing Activity: 11 (AFLCMC/WIN) Project Number: PSSS-2017-030 Applicable Forms: N/A Use/Relationship: The Proposed Spare Parts List identifies the contractor’s recommended spare parts required to maintain a system under a given set of circumstances and duration and will be used to determine spare parts stocking levels.
a. 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.
b. This DID supersedes DI-ILSS-80134A.
Requirements:
1. Reference documents. None.
2. Format. Contractor’s format shall be acceptable.
3. Content. The Proposed Spare Parts List shall contain the contractor’s recommended quantities of every type of spare part required for the system, to include all consumable and expendable items. This list shall explain any assumptions, formulas, or models used by the contractor in the creation of the list and shall include the following:
a. Complete item name.
b. Prime manufacturer’s or vendor’s part number.
c. Commercial and Government Entity (CAGE) Code
d. National Stock Number (NSN).
e. Quantity per end item.
f. Unit of issue (e.g., each, feet, lot).
g. Estimated unit price.
h. Recommended quantity to sustain operation for the time period and under the conditions stated in the contract.
i. Alpha numeric numbering of items on list.
j. Shelf life (if not indefinite).
k. Mean-Time-Between Failure (MTBF) of each item.
l. Production lead time for each item
m. Explanatory narrative which describes the recommended quantity to take into account multiple end items at a single location.
4. End of DI-PSSS-80134B.
DISTRIBUTION STATEMENT A. Approved for public release. Distribution is unlimited.
Source: http://assist.dla.mil -- Downloaded: 2025-04-04T16:42Z
File details come from the government source that posted it. Updated .