Exhibit_A.pdf

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information 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. Please DO NOT RETURN your form to either of these addresses. 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:

TBD A TDP________ TM _______ OTHER QCIC

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Depot Level Interferometer N64267-19-D-XXXX TBD

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A001 CALIBRATION CERTIFICATE Calibration Certificate

II

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-QCIC-80798B

(See Block 16)

SOW Paragraph: 5.1.3

NSWC, Corona Division

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT

A (See Block 16) (See Block 16)

b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Final

N/A N/A (See Block 16) Draft Reg. Repro

16. REMARKS Daniel M Martinez (MS35) 1

Block 4/5: DI-QCIC-80798B and SOW specification paragraph 5.1.3 shall be used as guidance and are provided for reference. Data points from the actual calibration must be included with this report. Information items in DI-

QCIC-80798B that are not relevant to the procurement do not need to be included in format.

Block 10: Frequency of Calibration Certificate (CDRL A001 subtitle) shall be generated for each unit calibrated.

Block 12: Date of first submission shall be in accordance with (IAW) first unit calibrated.

Block 13: Date of subsequent submissions shall be IAW each unit returned to the Government after subsequent calibration is performed.

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). Addressee's POC information provided on CDRL supplemental page 2.

NSWC Corona Division

Hien T. Le (MS33) 1

NSWC Corona Division

With each calibration performed 1

15. TOTAL 3

G. PREPARED BY

H. DATE I. APPROVED BY J. DATE

D. M. Martinez NSWC, Corona (MS35) K. Bergland NSWC, Corona (MS35) CDM 01/30/2019

DD FORM 1423 (CDRL) Supplemental

BLOCK 14 ENTRY COMPLETE ADDRESS

Daniel M Martinez, NSWC, Corona MS35, daniel.m.martinez@navy.mil

MS Department (Attn: Daniel M Martinez, MS35, Building 521)

PO Box 5000

Corona CA 92878-5000

Hien T. Le, NSWC, Corona MS33, hien.t.lee@navy.mil

MS Department (Attn: hien.t.lee@navy.mil MS33, Building 521)

Page 2 of 2 Pages mailto:daniel.m.martinez@navy.mil mailto:hien.t.lee@navy.mil

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: 2019-01-30T17:06Z 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: 2019-01-30T17:06Z

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: 2019-01-30T17:01Z

Software Version Description (SVD)

DI-IPSC-81442

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.).

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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information 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. Please DO NOT RETURN your form to either of these addresses. 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:

TBD A TDP________ TM _______ OTHER IPSC

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Depot Level Interferometers N64267-19-D-XXXX TBD

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A002 Software Version Description (SVD) Software/Firmware Version Description

II

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-IPSC-81442A

(See Block 16)

SOW Paragraph: 5.1.6 (See Block 16)

NSWC, Corona Division TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

LT (See Block 16) A (See Block 16) (See Block 16) b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Final

N/A N/A (See Block 16) Draft Reg

Repro

16. REMARKS Daniel M Martinez (MS35) 1 Block 4/5: For the description of software and firmware versions provided with each interferometer DI-IPSC-81442A and SOW specification paragraph

5.1.6 shall be used as guidance and are provided for reference. Information items in DI-IPSC-81442A that are not relevant to the procured unit do not need to be included in format.

Block 10: Frequency of Software/Firmware Version Description (CDRL A002 subtitle) shall be as generated for each interferometer.

Block 12: Date of first submission shall be in accordance with (IAW) first interferometer installed.

Block 13: Date of subsequent submissions shall be IAW each interferometer returned to the Government after warranty repair is performed. The Software/Firmware version shall be the same on all interferometer’s 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 IAW CDRL distribution (Block 14). Addressee's POC information provided on CDRL supplemental page 2.

Hien T. Le (MS33) 1

With each unit delivered 1

15. TOTAL 3 0

BLOCK 14 ENTRY COMPLETE ADDRESS

Daniel M Martinez, NSWC, Corona MS35, daniel.m.martinez@navy.mil NSWC Corona Division MS Department (Attn: Daniel M Martinez, MS35, Building 521)

MS Department (Attn: hien.t.lee@navy.mil MS33, Building 521)

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: 2019-01-30T17:03Z

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 Final

8. OTHER SYS/CONFIG ITEMS AFFECTED

YES NO

9. IN PRODUCTIO N

YES NO

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?

YES NO

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

(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

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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information 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. Please DO NOT RETURN your form to either of these addresses. 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:

TBD A TDP________ TM __ ____ OTHER MISC

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Depot Level Interferometers N64267-19-D-XXXX TBD

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

A003 Software/Firmware Change Request Software/Firmware Change Request

II

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-MISC-81807

(See Block 16)

SOW Paragraph 5.1.7

(See Block 16)

NSWC, Corona Division TOTAL PRICE

$ 3,420.00

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

XX C

b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE Final

N/A

Draft Reg

Rep ro

16. REMARKS Daniel M Martinez (MS35) 1 1 0

Block 4/5: DI-MISC-81807 shall be used as guidance and is provided for reference.

SOW Paragraph 5.1.7 is mandatory to this requirement.

Block 8: Prior notification and Government approval of all Software/Firmware

Change Request(s) (CDRL A003 subtitle) for the interferometer is required by the

Government. Contractor shall provide a Software/Firmware Change Request 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 interferometer.

Government comments with or without approval will be provided to the contractor within 15 days of receipt of Software/Firmware Change Request providing information explained in DI-MISC-81807.

Block 9: DISTRIBUTION STATEMENT C. DISTRIBUTION AUTHORIZED TO

U. S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS TO PROTECT

PUBLICATIONS REQUIRED FOR OFFICIAL USE OR FOR ADMINISTRATIVE

OR OPERATIONAL PURPOSES ONLY. OTHER REQUESTS FOR THIS

DOCUMENT SHALL BE REFERRED TO MEASUREMENT SCIENCE

DIRECTORATE, NAVAL SURFACE WARFARE CENTER, CORONA

DIVISION, P.O. BOX 5000, CORONA.

Block 10/12/13: Submission(s) of Software/Firmware Change Request(s) apply to both new and warranty repaired interferometer and shall be provided to the

Government prior to each software/firmware change and initial operating capability

(IOC) of the interferometer. Transmission of the Software/Firmware Change

Request(s) data shall follow the requirements specified in SOW paragraph 5.1.7.

Block 14: Submission in Contractor format is acceptable. Quantity and copies shall be provided IAW CDRL distribution (Block 14). Addressee's POC information provided on CDRL supplemental page 2.

Hien T. Le (MS22) 1 1 0

15. TOTAL 2 2

DD Form 1423-1 JUN 90 Previous editions are obsolete. Page 1 of 2 Pages

1077/183

BLOCK 14 ENTRY COMPLETE ADDRESS

MS Department (Attn: Daniel M Martinez, MS35, Building 521)

MS Department (Attn: hien.t.lee@navy.mil MS33, Building 521)

DATA ITEM DESCRIPTION

Title: COMMERCIAL OFF-THE-SHELF (COTS) MANUALS AND ASSOCIATED

SUPPLEMENTAL DATA

Number: DI-TMSS-80527C Approval Date: 20110812 AMSC Number: 9207 Limitation: No DTIC Applicable: No GIDEP 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 which 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-80527B, dated 17 Oct 2006.

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 in the contractor's format. Supplemental data shall be in the format specified by the contracting 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-PRF-87268 or 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.

Source: http://assist.dla.mil -- Downloaded: 2019-01-30T17:08Z

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 this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information 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. Please DO NOT RETURN your form to either of these addresses. 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:

TBD T TDP________ TM TMSS OTHER _________

D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR

Depot Level Interferometers N64267-19-D-XXXX TBD

1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE 17. PRICE

GROUP

T001 Commercial Off-The-Shelf (COTS) Manuals and

Associated Supplemental Data

Operator/Service Manual

II

4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE 18. ESTIMATED

DI-TMSS-80527C

(See Block 16)

SOW Paragraph 5.1.1, CSS 06-3211 Paragraph 3.1

(See Block 16)

NSWC, Corona Division

TOTAL

PRICE

7. DD 250 REQ 9. DIST STATEMENT 10. FREQUENCY 12. DATE OF FIRST

SUBMISSION

14. DISTRIBUTION

XX C

b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

a. ADDRESSEE

Final

A

N/A (See Block 16)

Draf t

Reg. Repro

16. REMARKS Daniel M Martinez (MS35) 1 1 0

Block 4/5: DI-TMSS-80527C shall be used as guidance and is provided for reference. SOW paragraph 5.1.1 and CSS 06-3211 paragraph 3.1 are mandatory to this requirement and are provided for guidance.

Block 8: Operator/Service Manual (CDRL T001 subtitle) requires government approval. Contractor shall provide a preliminary draft to the Government for review, comment, and approval no later than (NLT) 60 calendar days prior to acceptance testing. Government will provide the Contractor with comments NLT 15 calendar days of receipt of preliminary draft. Contractor shall provide a Government approved final version with incorporated comments NLT 30 days prior to Initial Operating

Capability (IOC) of the first system. IOC shall be defined as the Estimated Day of

Delivery (EDD) provided by the contractor and included in the base delivery order award.

Block 9: DISTRIBUTION STATEMENT C. DISTRIBUTION AUTHORIZED TO

U. S. GOVERNMENT AGENCIES AND THEIR CONTRACTORS TO PROTECT

PUBLICATIONS REQUIRED FOR OFFICIAL USE OR FOR ADMINISTRATIVE

OR OPERATIONAL PURPOSES ONLY. OTHER REQUESTS FOR THIS

DOCUMENT SHALL BE REFERRED TO MEASUREMENT SCIENCE

DIRECTORATE, NAVAL SURFACE WARFARE CENTER, CORONA

DIVISION, P.O. BOX 5000, CORONA.

Block 10/12/13: Submissions of Operator/Service Manual(s) shall be provided with each interferometer installed.

Block 14: Submission in Contractor format is acceptable. Electronic format is desired and acceptable if in MS-Excel or MS Word. Electronic submission of data shall also be on CD-ROM and/or DvD media. Quantity and copies shall be provided

IAW CDRL distribution (Block 14a). Addressee's POC information provided on

CDRL supplemental page 2.

Hien T. Le (MS33) 1 1 0

With each system installed 1

15. TOTAL 2 3 0

DD Form 1423-1 JUN 90 Previous editions are obsolete. Page 1 of 2 Pages

1077/183

BLOCK 14 ENTRY COMPLETE ADDRESS

MS Department (Attn: Daniel M Martinez, MS35, Building 521)

MS Department (Attn: hien.t.lee@navy.mil MS33, Building 521) mailto:hien.t.lee@navy.mil mailto:hien.t.lee@navy.mil