Data Requirements.pdf
PDF 1 MB Posted
- Attached to
- Vision Measurement System Federal contract opportunity
- Solicitation number
- FA2263-20-Q-0009
About this file
This solicitation requests offers for a Vision Measurement System with technical manuals and software user manual. Required is a new, commercial off-the-shelf unit that meets the specifications in Attachment 1. Offerors must provide pricing for the base year and option year quantities. Offers are due by June 1, 2020 and shall be submitted electronically through DoD SAFE. The North American Industry Classification System code is 334516 and the business size standard is 1,000 employees. The Department of the Air Force Materiel Command Lifecycle Management Center at Wright Patterson Air Force Base intends to award a firm-fixed-price contract for purchase of the system. Successful offerors must register in the System for Award Management and accept payment by electronic funds transfer using Wide Area Workflow.
View the file
Other files for this federal contract opportunity
| File | Type | Posted |
|---|---|---|
| Anticipated Installation and Training Locations.pdf | ||
| Solicitation FA226320Q0009.pdf | ||
| Purchase Description 20M-271A-DI Rev. 0.pdf | ||
| Instructions to Offerors.pdf | ||
| TEP WORKSHEET.xlsx | XLSX spreadsheet | |
| Anticipated Delivery Locations.pdf |
On GovTribe
Work with this file on GovTribe
- 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!
http://www.adobe.com/go/reader
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
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Page of Pages
1_DATA_ITEM_NO: B001
2_TITLE_OF_DATA_ITEM: Technical Manual Contract Requirements (TMCR)
3_SUBTITLE:
4_AUTHORITY_Data_Acquisit: TM-86-01
5_CONTRACT_REFERENCE: PD 20M-271A-DI Atch
6_REQUIRING_OFFICE: AFLCMC/WNMM
7_DID_250_REQ: N/A
8_APP_CODE: N/A
DIST_STATEMENT: D
10_FREQUENCY: ASREQ
11_AS_OF_DATE: ASREQ
12_DATE_OF_FIRST_SUBMISSI: See BLK 16
13_DATE_OF_SUBSEQUENT_SUB: See BLK 16 addressee1:
draft1:
reg1:
repro1:
addressee2:
draft2:
reg2:
repro2:
addressee3:
draft3:
reg3:
repro3:
addressee4: Ship with unit draft4:
reg4: 12 repro4:
addressee5:
draft5:
reg5:
repro5:
addressee6:
draft6:
reg6:
repro6:
addressee7:
draft7:
reg7:
repro7:
addressee8:
draft8:
reg8:
repro8:
addressee9:
draft9:
reg9:
repro9:
addressee10:
draft10:
reg10:
repro10:
addressee11:
draft11:
reg11:
repro11:
addressee12:
draft12:
reg12:
repro12:
addressee13:
draft13:
reg13:
repro13:
addressee14:
draft14:
reg14:
repro14:
addressee15:
draft15:
reg15:
repro15:
addressee16:
draft16:
reg16:
repro16:
addressee17:
draft17:
reg17:
repro17:
addressee18:
draft18:
reg18:
repro18:
addressee19:
draft19:
reg19:
repro19:
addressee20:
draft20:
reg20:
repro20:
addressee21:
draft21:
reg21:
repro21:
addressee22:
draft22:
reg22:
repro22:
addressee23:
draft23:
reg23:
repro23:
addressee24:
draft24:
reg24:
repro24:
addressee25:
draft25:
reg25:
repro25:
addressee26:
draft26:
reg26:
repro26:
addressee27:
draft27:
reg27:
repro27:
addressee28:
draft28:
reg28:
repro28:
addressee29:
draft29:
reg29:
repro29:
addressee30:
draft30:
reg30:
repro30:
addressee31:
draft31:
reg31:
repro31:
addressee32:
draft32:
reg32:
repro32:
addressee33:
draft33:
reg33:
repro33:
addressee34:
draft34:
reg34:
repro34:
addressee35:
draft35:
reg35:
repro35:
addressee36:
draft36:
reg36:
repro36:
addressee37:
draft37:
reg37:
repro37:
addressee38:
draft38:
reg38x:
repro38:
total_draft: 0 total_repro: 0
16_REMARKS: Blk 12&13: Concurrent with delivery of production units, the contractor shall furnish and pack 1 set of manuals with each unit. Manuals shall be on CD/DVD in Indexed Portable Document Format (iPDF). Ship with unit.
The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.
17_PRICE_GROUP:
ESTIMATED_TOTAL_PRICE:
G_PREPARED_BY:
H_DATE: 2/27/20
1_APPROVED_BY:
J_DATE: 2/27/2020
Page: 3 reg38t: 12
A_CONTRACT_LINE_ITEM_NO:
B_EXHIBIT: B(FY 21)
TDP:
TM: x
OTHER:
DSYSTEMITEM: Vision Measurement System
E_CONTRACTPR_NO:
FCONTRACTOR:
of_pages: 4
Reset:
2020-02-27T12:40:17-0500
CAPUANO.FRANK.R.1403209658
2020-02-27T15:10:59-0500
SKINNER.KEVIN.L.II.1024227223
DD FORM 1423-2, AUG 96
(2 Data Items)
The public reporting burden for this collection of information is estimated to average 220 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
TDP ________ TM _______ OTHER _________________________
11. AS OF DATE 13. DATE OF SUBSEQUENT
12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION
Page ____ of ____ Pages
A_CONTRACT_LINE_ITEM_NO:
B_EXHIBIT: B(FY 21)
TDP: Off
TIM: Yes
OTHER:
D_SYSTEMITEM: Vision Measurement System
E_CONTRACTPR_NO:
FCONTRACTOR:
1_DATA_ITEM_NO1: B002
2_TITLE_OF_DATA_ITEM1: Software User Manual
3_SUBTITLE1:
4_AUTHORITY1: DI-IPSC-81443A
5_CONTRACT_REFERENCE1: PD 20M-271A-DI Atch
6_REQUIRING_OFFICE1: AFLCMC/WNMM
7_DD_250_REQ1: N/A
8_APP_CODE1: N/A
9_dist1: D
10_FREQUENCY1: ASREQ
11_AS_OF_DATE1: ASREQ
12_DATE_OF_FIRST_SUB1: See BLK 16
13_DATE_OF_SUBSEQUENT_SUB1: See BLK 16 addr1_1:
draft1_1:
reg1_1:
repro1_1:
1_DATA_ITEM_NO2: B003
2_TITLE_OF_DATA_ITEM2: Calibration Certificate
3_SUBTITLE2:
4_AUTHORITY2: DI-QCIC-80798C
5_CONTRACT_REFERENCE2: PD 20M-271A-DI Atch
6_REQUIRING_OFFICE2: AFLCMC/WNMM
7_DD_250_REQ2: N/A
8_APP_CODE2: N/A
9_dist2:
10_FREQUENCY2: ASREQ
11_AS_OF_DATE2: ASREQ
12_DATE_OF_FIRST_SUB2: See BLK 16
13_DATE_OF_SUBSEQUENT_SUB2: See BLK 16 addr2_1:
draft2_1:
reg2_1:
repro2_1:
addr1_2: Ship with unit draft1_2:
reg1_2: 12 repro1_2:
addr1_3:
draft1_3:
reg1_3:
repro1_3:
addr1_4:
draft1_4:
reg1_4:
repro1_4:
addr1_5:
draft1_5:
reg1_5:
repro1_5:
addr1_6:
draft1_6:
reg1_6:
repro1_6:
addr1_7:
draft1_7:
reg1_7:
repro1_7:
addr1_8:
draft1_8:
reg1_8:
repro1_8:
addr1_9:
draft1_9:
reg1_9:
repro1_9:
addr1_10:
draft1_10:
reg1_10:
repro1_10:
addr1_11:
draft1_11:
reg1_11:
repro1_11:
addr1_12:
draft1_12:
reg1_12:
repro1_12:
addr1_13:
draft1_13:
reg1_13:
repro1_13:
addr1_14:
draft1_14:
reg1_14:
repro1_14:
15_total_Draft1: 0
15_TOTALReg1: 12
15_TOTALRepro1: 0
16_REMARKS1:
BLK 12: Concurrent with the delivery of production units contractor shall furnish and pack one (1) Software User Manual with each unit.
The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.
17_PRICE_GROUP1:
18_totalprice1:
addr2_2: Ship with unit addr2_3:
addr2_4:
16_REMARKS2: BLK 12: Concurrent with delivery of first production unit, the contractor shall furnish and pack one (1) calibration certificate with each unit. Ship with unit.
The listed number of copies is the maximum amount for the acquisition. Specific quantities will be identified by issuance of a modification to exercise option quantities.
17_PRICE_GROUP2:
18_totalprice2:
addr2_5:
addr2_6:
addr2_7:
addr2_8:
addr2_9:
addr2_10:
addr2_11:
addr2_12:
addr2_13:
addr2_14:
draft2_2:
reg2_2: 12 repro2_2:
draft2_3:
reg2_3:
repro2_3:
draft2_4:
reg2_4:
repro2_4:
draft2_5:
reg2_5:
repro2_5:
draft2_6:
reg2_6:
repro2_6:
draft2_7:
reg2_7:
repro2_7:
draft2_8:
reg2_8:
repro2_8:
draft2_9:
reg2_9:
repro2_9:
draft2_10:
reg2_10:
repro2_10:
draft2_11:
reg2_11:
repro2_11:
draft2_12:
reg2_12:
repro2_12:
draft2_13:
reg2_13:
repro2_13:
draft2_14:
reg2_14:
repro2_14:
15_total_Draft2: 0
15_TOTALReg2: 12
15_TOTALRepro2: 0
G_PREPARED_BY:
H_DATE: 2/27/20
1_APPROVED_BY:
J_DATE: 2/27/2020
Page: 4 of_pages: 4
Reset:
2020-02-27T12:41:33-0500
CAPUANO.FRANK.R.1403209658
2020-02-27T15:11:34-0500
SKINNER.KEVIN.L.II.1024227223
DATA ITEM DESCRIPTION
Title: SOFTWARE USER MANUAL (SUM)
Number: DI-IPSC-81443A AMSC Number: N7378 DTIC Applicable: No Office of Primary Responsibility: N/SPAW AR Applicable Forms: NIA
Use, Relationships:
Approval Date: 20000111 Limitation: N/ A GIDEP Applicable: No
The Software User Manual (SUM) tells a hands-on software user how to install and use a Computer Software Configuration Item (CSCI), a group of related CSCl's, or a software system or subsystem. It may also cover a particular aspect of software operation, such as instructions for a particular position or task.
The SUM is developed for software that is run by the user and has a user interface requiring on line user input or interpretation of displayed output. If the software is embedded in a hardware software system, user manuals or operating procedures for that system may make separate SUMs unnecessary.
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.
This DID is used when the developer is tasked to identify and record information needed by hands-on users of software.
The SUM is an alternative to the Software Input/Output Manual (SIOM) (DI-IPSC-81445A) and Software Center Operator Manual (SCOM) (DI-IPSC-8 l 444A).
This DID supersedes DI-IPSC-81443.
Requirements:
1. Reference documents. None.
2. 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.
DI-IPSC-81443A
3. Format. Following are the format requirements.
The specification shall be in contractor format unless otherwise specified on the Contract Data Requirements List (CDRL)(DD 1423). The CORL 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.
4. Content. The specification shall contain the following:
a. 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.
b. Table of contents and index. The document shall contain a table of contents providing the number, title, and page number of each titled paragraph, figure, table, and appendix, and an index providing an alphabetic listing of key terms and concepts covered in the document and the pages or paragraphs in which the terms or concepts are covered. 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.
c. 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.
d. 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.
e. Multiple paragraphs and subparagraphs. Any section, paragraph, or subparagraph in this DID may be written as multiple paragraphs or subparagraphs to enhance readability.
f. 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 pref erred over including the description itself.
D1-IPSC-81443A
g. 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.
The numbers shown designate the paragraph numbers to be used in the document.
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 ).
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. Software summary. This section shall be divided into the following paragraphs.
3 .1 Software application. This paragraph shall provide a brief description of the intended uses of the software. Capabilities, operating improvements, and benefits expected from its use shall be described.
3.2 Software inventory. This paragraph shall identify all software files, including databases and data files, that must be installed for the software to operate. The identification shall include security and privacy considerations for each file and identification of the software necessary to continue or resume operation in case of an emergency.
3.3 Software environment. This paragraph shall identify the hardware, software, manual operations, and other resources needed for a user to install and run the software. Included, as applicable, shall be identification of:
a. Computer equipment that must be present, including amount of memory needed, amount of auxiliary storage needed, and peripheral equipment such as printers and other input/output devices
b. Communications equipment that must be present
c. Other software that must be present, such as operating systems, databases, data files, utilities, and other supporting systems
d. Forms, procedures, or other manual operations that must be present
e. Other facilities, equipment, or resources that must be present
3.4 Software organization and overview of operation. This paragraph shall provide a brief description of the organization and operation of the software from the user's point of view.
The description shall include, as applicable:
a. Logical components of the software, from the user's point of view, and an overview of the purpose/operation of each component
b. Performance characteristics that can be expected by the user, such as:
I) Types, volumes, rate of inputs accepted
2) Types, volume, accuracy, rate of outputs that the software can produce
3) Typical response time and factors that affect it
4) Typical processing time and factors that affect it
5) Limitations, such as number of events that can be tracked
6) Error rate that can be expected
7) Reliability that can be expected
c. Relationship of the functions performed by the software with interfacing systems, organizations, or positions
d. Supervisory controls that can be implemented (such as passwords) to manage the software
3. 5 Contingencies and alternate states and modes of operation. This paragraph shall explain differences in what the user will be able to do with the software at times of emergency and in various states and modes of operation, if applicable.
3.6 Security and privacy. This paragraph shall contain an overview of the security and privacy considerations associated with the software. A warning shall be included regarding making unauthorized copies of software or documents, if applicable.
3. 7 Assistance and problem reporting. This paragraph shall identify points of contact and procedures to be followed to obtain assistance and report problems encountered in using the software.
4. Access to the software. This section shall contain step-by-step procedures oriented to the first time/occasional user. Enough detail shall be presented so that the user can reliably access the software before learning the details of its functional capabilities. Safety precautions, marked by WARNING or. CAUTION, shall be included where applicable.
4.1 First-time user of the software. This paragraph shall be divided into the following subparagraphs.
4.1.1 Equipment familiarization. This paragraph shall describe the following as appropriate:
a. Procedures for turning on power and making adjustments
b. Dimensions and capabilities of the visual display screen
c. Appearance of the cursor, how to identify an active cursor if more than one cursor can appear, how to position a cursor, and how to use a cursor
d. Keyboard layout and role of different types of keys and pointing devices
e. Procedures for turning power off if special sequencing of operations is needed
4 .1.2 Access control. This paragraph shall present an overview of the access and security features of the software that are visible to the user. The following items shall be included, as applicable:
a. How and from whom to obtain a password
b. How to add, delete, or change passwords under user control
c. Security and privacy considerations pertaining to the storage and marking of output reports and other media that the user will generate
4.1.3 Installation and setup. This paragraph shall describe any procedures that the user must perform to be identified or authorized to access or install software on the equipment, to perform the installation, to configure the software, to delete or overwrite former files or data, and to enter parameters for software operation.
4.2 Initiating a session. This paragraph shall provide step-by-step procedures for beginning work, including any options available. A checklist for problem determination shall be included in case difficulties are encountered.
4.3 Stopping and suspending work. This paragraph shall describe how the user can cease or interrupt use of the software and how to determine whether normal termination or cessation has occurred.
5. Processing reference guide. This section shall provide the user with procedures for using the software. If procedures are complicated or extensive, additional Sections 6, 7, ... may be added in the same paragraph structure as this section and with titles meaningful to the sections selected. The organization of the document will depend on the characteristics of the software being documented. For example, one approach is to base the sections on the organizations in which users work, their assigned positions, their work sites, or the tasks they must perform. For other software, it may be more appropriate to have Section 5 be a guide to menus, Section 6 be a guide to the command language used, and Section 7 be a guide to functions. Detailed procedures are intended to be presented in subparagraphs of paragraph 5 .3. Depending on the design of the software, the subparagraphs might be organized on a function-by-function, menu-by-menu, transaction-by-transaction, or other basis. Safety precautions, marked by WARNING or CAUTION, shall be included where applicable.
5 .1 Capabilities. This paragraph shall briefly describe the interrelationships of the transactions, menus, functions, or other processes in order to provide an overview of the use of the software.
5.2 Conventions. This paragraph shall describe any conventions used by the software, such as the use of colors in displays, the use of audible alarms, the use of abbreviated vocabulary, and the use of rules for assigning names or codes.
5. 3 Processing procedures. This paragraph shall explain the organization of subsequent paragraphs, e.g., by function, by menu, by screen. Any necessary order in which procedures must be accomplished shall be described.
5.3.x (Aspect of software use). The title of this paragraph shall identify the function, menu, transaction, or other process being described. This paragraph shall describe and give options and examples, as applicable, of menus, graphical icons, data entry forms, user inputs, inputs from other software or hardware that may affect the software's interface with the user, outputs, diagnostic or error messages or alarms, and help facilities that can provide on-line descriptive or tutorial information. The format for presenting this information can be adapted to the particular characteristics of the software, but a consistent style of presentation shall be used, i.e., the descriptions of menus shall be consistent, the descriptions of transactions shall be consistent among themselves.
5.4 Related processing. This paragraph shall identify and describe any related batch, offline, or background processing performed by the software that is not invoked directly by the user and is not described in paragraph 5.3. Any user responsibilities to support this processing shall be specified.
D1-IPSC-81443A
5.5 Data backup. This paragraph shall describe procedures for creating and retaining backup data that. can be used to replace primary copies of data in event of errors, defects, malfunctions, or accidents.
5.6 Recovery from errors, malfunctions, and emergencies. This paragraph shall present detailed procedures for restart or recovery from errors or malfunctions occurring during processing and for ensuring continuity of operations in the event of emergencies.
5. 7 Messages. This paragraph shall list, or refer to an appendix that lists, all error messages, diagnostic messages, and information messages that can occur while accomplishing any of the user's functions. The meaning of each message and the action that should be taken after each such message shall be identified and described.
5.8 Quick-reference guide. If appropriate to the software, this paragraph shall provide or reference a quick-reference card or page for using the software. This quick-reference guide shall summarize, as applicable, frequently used function keys, control sequences, formats, commands, or other aspects of software use.
6. 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. If Section 5 has been expanded into section(s )6, ... , this section shall be numbered as the next section following section n.
A. Appendices. Appendices 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.).
END OF D1-IPSC-81443A.
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.
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.
TM-86-01Q 27 Oct 2017 1-01: AF TMSS Linear TMs
Air Force Technical Manual Contract Requirements (TMCR) for
AIR FORCE CALIBRATION AND METROLOGY (AFMETCAL) PROGRAM
Vision Measurement System
ATTACHMENT DD FORM 1423, TO CDRL SEQUENCE NUMBER 001, EXHIBIT A REQUEST FOR
PROPOSAL/CONTRACT:
Date: 8 April 2020
SECTION 1. TECHNICAL ORDER (TO) PROGRAM REQUIREMENTS
1. TMCR Tailoring. This TMCR has been tailored by the program office, including the associated tables, matrices and Specification/Standard Interface Records (SIRs). The Contractor may propose and submit, in writing, additional tailoring to the Technical Order Manager Agency/Agent (TOMA), Government
Program Manager (PM), and Procuring Contracting Officer (PCO) for consideration. The tailored TMCR shall be attached to the Contract Data Requirements List (CDRL) for Technical Order (TO) delivery, and shall be included in the proposal as a separate exhibit, referenced in the proposal Statement Of Work
(SOW). Air Force (AF) TO Acquisition procedures, including procedures for tailoring this document, are found in TO 00-5-3, AF Technical Order Life Cycle Management, located at http://www.tinker.af.mil/Home/TechnicalOrders.aspx. A copy may also be obtained from the Program
TO Manager. Any terms or procedures found in this document may be researched there.
2. TO Program Scope. The Contractor shall develop and deliver technical manuals in accordance with
(IAW) this TMCR that supports the AFMETCAL requirements for technically usable manuals. The technical manuals will include Operation and Maintenance Instructions, Illustrated Parts Breakdown, and
Calibration Process/Procedure in a Portable Document Format (PDF). PDF TO Publications may be produced and distributed as physical media (Paper/CD) or electronically via Enhanced Technical
Information Management System (ETIMS) electronic TO Viewer (eTOV).
3. Commercial Manuals. Contractors shall recommend the use of existing commercial manuals to the maximum extent possible without impairing program support objectives. All proposed commercial manuals are subject to Government review and approval. Contractors shall use Data Item Description
(DID) DI-TMSS-80067C, Technical Manual (TM) Contractor Furnished Aeronautical Equipment or
Contractor Furnished Equipment (CFAE/CFE) Notices, to provide recommendation data. A copy is available through ASSIST at http://quicksearch.dla.mil/qsSearch.aspx.
3.1. The AF requests the ability to electronically store, print, distribute, update and decollate the commercial manual to allow for printing. Commercial manuals shall be delivered as Portable
Document Format (PDF) unless otherwise specified.
3.2. Approved Commercial-Off-The-Shelf (COTS) Manuals shall be delivered with an Identifying
TO Publication Sheet (ITPS), IAW MIL-PRF-32216, Performance Specification: Evaluation Of
Commercial Off-The-Shelf (COTS) Manuals And Preparation Of Supplemental Data. All PDF files of commercial data shall be non-password protected to allow the AF to decollate the manual for printing.
http://www.tinker.af.mil/Home/TechnicalOrders.aspx http://quicksearch.dla.mil/qsSearch.aspx
3.3. If the proposed COTS data is found to be insufficient after review by the Government, the
Contractor shall prepare supplemental data for the COTS manual as required IAW Military Standard
(MIL-STD)-38784. If the COTS data cannot be supplemented sufficiently the Contractor may be tasked to develop new TM data IAW the applicable TMSS listed in Section 2, Table 1.
4. Technical Manual Specifications and Standards (TMSS) Tailoring. The contractor shall develop all
TMs IAW most current version of applicable TMSS for the type manual being developed and comply with the Specification/Standard Interface Records (SIRS) provided within Section 3.
5. Subsequent TO/Data Requirements. (Deleted)
6. TO Development. TOs shall be written to a scope and depth of coverage to support the AFMETCAL operations and maintenance concepts.
6.1. Standard Generalized Markup Language (SGML) tagged TO files shall include required illustration (graphics) files in an approved graphics exchange format. Illustration files developed and delivered for other purposes shall be used in lieu of developing special TM illustration files whenever possible. All delivered graphics shall conform to the approved graphic creation and format guidelines listed in Attachment 1, Graphics Format Guidelines. For assistance with illustration requirements contact AF TMSS via (e-mail: SGMLSupport@us.af.mil).
6.2. (Deleted)
7. TO Numbering. (Deleted)
8. Data Rights. Contractors shall comply with 10 U.S.C. 2320 and cognizant Defense Federal Acquisition
Regulation Supplement (DFARS) provisions and clauses in providing Unlimited Rights for all source data, TO publications, and TO updates prepared specifically for the contract. Government rights in data are specified in the DFARS, 252.227-7013, Rights in Technical Data, Noncommercial Items, 252.227-
7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software
Documentation, and 252.227-7015, Technical Data-Commercial Items. The Government shall be given
Unlimited Rights for all Government-funded business rules (tailoring and application methods and procedures) and documented business processes developed under the contract for the purpose of TO development. For all data delivered to the Government with other than Unlimited Rights, the Contractor shall assert their data rights IAW DFARS 252.227-7017, Identification and Assertion of Use, Release, or
Disclosure Restrictions. The Contractor shall pass through and enforce all requirements in this TMCR to all sub-Contractors.
9. Classification, Distribution, Destruction, Disclosure, Export Control Notices, and Cyber Security.
Contractors shall recommend the correct markings and controls for classified and restricted distribution data and TOs IAW the program’s Security Classification Guide (SCG) and Department of Defense
Manual (DODM) 5200.01, Department of Defense Instruction (DODI) 5230.24, Department of Defense
Directive (DODD) 5230.25, Air Force Instruction (AFI) 16-1404, and MIL-STD-38784 (available at http://www.e-publishing.af.mil/ or https://assist.dla.mil/online/start/index.cfm). The markings and notices shall be reviewed during In-Process Reviews (IPR). The Contractor shall also apply policy and procedures for Cyber Security Protection IAW AFI 33-200, Information Assurance (IA) Management, AFMAN 17-1301, Computer Security (COMPUSEC), and MPTO 00-33B-5008, Remanence Security for
Information Systems. NOTE: Distribution limitations will be determined on a case-by-case basis as TOs are developed, dependent upon TO content.
mailto:SGMLSupport@us.af.mil http://www.e-publishing.af.mil/ https://assist.dla.mil/online/start/index.cfm
10. TO Quality. Contractor proposals shall describe how the Government will be allowed to interact with the Contractor’s TO development team. The Contractors shall ensure prepared TOs are: a) technically accurate and safe; b) written to a scope and depth of coverage to support the operations and maintenance concepts; c) properly classified and marked with export control and distribution limitation statements.
11. TO Delivery. TO file delivery requirements are located in Section 2, Table 3 of this document.
11.1. MIL-SPEC (SGML) Tagged Files. The Contractor shall parse all SGML files required for the
TOs prior to Government delivery and shall verify the SGML is compliant with the appropriate DTD.
NOTE: The Government will parse the files prior to acceptance using the public domain SGML parser (http://www.jclark.com/sp/).
12. Source Data Maintenance. (Deleted)
13. TO Maintenance. (Deleted)
14. Schedules. (Deleted)
15. Time Compliance Technical Orders (TCTOs). (Deleted) http://www.jclark.com/sp/
SECTION 2. TM TYPE AND DELIVERY REQUIREMENTS
NOTES:
Mark the TM Type Selection Tables indicating the applicable TO types and related specifications.
(NEW DEVELOPMENT) LINEAR TM TYPE (PUBLICATION) SELECTION TABLES.
TABLE 1
TMSS REQUIREMENTS FOR THE AFMETCAL
(Vision Measurement System)
Title or Type of Manuals Specification Required
1. Inspection TOs MIL-DTL-5096
a. Inspection and Maintenance Requirements (-6) Manual
b. Acceptance and Functional Check Flight (FCF) Procedures (-6CF)
Manual
c. Acceptance and Functional Check Flight (-6CL) Checklist
d. Inspection Workcards (-6WC)
e. Maintenance/Operations Checklists
2. Cargo Aircraft Loading and Offloading TOs MIL-DTL-5288
a. Loading Instructions Manual
b. Nuclear Weapon Cargo Loading Manual
c. Checklists
3. Weight and Balance (Aircraft) MIL-DTL-5920
a. Loading Data Manual
b. Sample Basic Weight Checklists
4. Flight Manuals MIL-DTL-7700
a. Flight Manual
b. Performance Data Manual
c. Mission Crew Manual
d. Supplemental Manual
e. Abbreviated Flight Crew Checklist
5. List of Applicable Publications MIL-DTL-8031
6. Structural Repair Manuals (for Aircraft) MIL-DTL-9854
7. Munitions/Weapons Loading Procedures, Non- nuclear and Nuclear TOs MIL-DTL-9977
a. Nuclear Weapons Basic Information and Loading Procedures
b. Nuclear Weapons Loading Procedures
c. Non-nuclear Munitions Basic Information
d. Non-nuclear Loading Procedures
e. Non-nuclear Munitions Loading Standard Data Packages (SDPs)
f. Loading Procedures Checklist
g. Single Loading Procedures Checklist
h. Integrated Loading Procedures Checklists
i. Family Group Loading Procedures Checklist
j. Nuclear Weapons Loading Procedure Checklists
k. Functional Check Procedures Checklist
l. NATO Stage B Cross-Servicing Checklists
m. End of Runway (EOR) Procedures Checklist
8. Space Operations and Support Documentation TOs
-- MIL-SPEC (Intercontinental Ballistic Missiles)
-- MIL-SPEC (Space)
MIL-PRF-38311
MIL-PRF-38314
a. Operations Manual
b. Operations Checklists
c. Technical Manuals and Related Checklists
9. Nuclear and Non-nuclear Weapon Delivery and Aircrew Procedures
Manuals and Checklists
MIL-DTL-38384
a. Non-nuclear Weapon Delivery Manual
b. Aircrew Nuclear Bomb Delivery Manual (Strategic Bomber Aircraft)
c. Aircrew Nuclear Missile Delivery Manual (Strategic Bomber Aircraft)
d. Aircrew Nuclear Bomb Delivery Manual (Tactical Aircraft)
e. Non-nuclear Weapon Delivery Checklist
f. Nuclear Weapon Delivery Checklist (Strategic Bomber Aircraft)
g. Aircrew Nuclear Bomb Delivery Checklist (Tactical Aircraft)
h. Non-nuclear Weapon Delivery Source Data Packages
10. Work Unit Code Manual
a. Standard WUC Manual
b. Two Chapter Manual
c. Three Chapter Manual
MIL-DTL-38769
11. Calibration Procedures MIL-DTL-38793
12. Time Compliance Technical Orders (TCTOs)
a. TCTO
b. TCTO Supplement
MIL-DTL-38804
13. Aircraft Battle Damage Assessment and Repair TOs MIL-DTL-87158
14. Illustrated Parts Breakdown MIL-DTL-38807
15. On-Equipment Organizational Maintenance Manual Set MIL-DTL-83495
a. General Equipment (GE) Manual
b. General System (GS) Manuals
c. Combined GE & GS Manual
d. Job Guide (JG) Manuals
e. Fault Reporting (FR) Manual
f. Fault Isolation (FI) Manual
g. Wiring Data (WD) Manual
h. Schematic Diagram (SD) Manual
16. Operation and Maintenance Instructions in Work Package Format MIL-DTL-87929
a. Maintenance Manuals
(1) Organizational Maintenance
(2) Intermediate Maintenance
(3) Depot Maintenance
(4) Combined (I&D) Maintenance
(5) On Condition Maintenance
b. Operation & Maintenance Instruction Manuals
c. Special Manuals
(1) Aircraft Engine Testing and Trending Procedures
(2) Aircraft Power Package Testing Procedures
(3) Static Firing of Missile Motors
(4) System Peculiar Corrosion Control
(5) Nondestructive Inspection (NDI)
(6) Aircraft Structural Integrity Program (ASIP)
(7) ATE Operator Test Procedures
(8) Special Requirements for Storage and Maintenance Procedures;
AUR Munitions/Launchers and Associated Support Equipment, Conventional Components and CMBR Agents
(9) Parachute Packing Procedures
(10) Operators Instructions (Hand-Held Flight Computers)
(11) Installation-Engineering Facility (Ground C-E Equipment)
d. Checklists (IAW MIL-DTL-5096)
e. With Illustrated Parts Breakdown
17. Commercial Manuals (Evaluate according to MIL-PRF-32216)
18. Aircraft Cross-servicing Guide MIL-DTL-22202
TABLE 3 – LINEAR TM DELIVERY REQUIREMENTS
FOR THE AFMETCAL
Vision Measurement System
NOTES:
For Paper media delivery indicate required quantity
DELIVERY SCHEDULE
Event Number of days data required prior to event
Technical
Review(s)
(30 DACA)
First
Article/First
Production
Unit
(90 DACA)
Administrative
(Logistics)
(30
DAFAOK)
Final TO
Distribution
(Ship With
Prod Units)
(90
DAFAOK)
Enter physical mailing address, electronic delivery location or web access point
Legend: DACA - After Contract Award
DAFAOK - Days after First Article accepted (passes
Acceptance testing)
Engineering (Draft) Copy
AFLCMC/WNMRP/AFMETCAL Division
ATTN: Frank Capuano frank.capuano@us.af.mil 813 Irving Wick Drive West, Bldg 2
Heath, Ohio 43056
IPDF / 1
IPDF /
First Production Copies (ship w/1st Prod.)
Bionetics Transportation
ATNN: Carol Cooperrider
813 Irving Wick Drive West, Bldg 4, Door 15
Administrative (Logistics) Copies
AFLCMC/WNMRP/AFMETCAL Division
ATTN: Frank Capuano frank.capuano@us.af.mil 813 Irving Wick Drive West, Bldg 2
Final (Production) Copies (ship w/ unit)
Bionetics Transportation
ATNN: Carol Cooperrider
813 Irving Wick Drive West, Bldg 4, Door 15
IPDF / 14
Total Paper Copies Required: 1 1 1 14
SECTION 3. DELETED
DD FORM 1423-1, FEB 2001
(1 Data Item)
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
TDP ________ TM _______ OTHER
Page of Pages
1_DATA_ITEM_NO: A001
2_TITLE_OF_DATA_ITEM: Technical Manual Contract Requirements (TMCR)
3_SUBTITLE:
4_AUTHORITY_Data_Acquisit: TM-86-01
5_CONTRACT_REFERENCE: PD 20M-271A-DI Atch
6_REQUIRING_OFFICE: AFLCMC/WNMM
7_DID_250_REQ: N/A
8_APP_CODE: N/A
DIST_STATEMENT: D
10_FREQUENCY: ASREQ
11_AS_OF_DATE: ASREQ
12_DATE_OF_FIRST_SUBMISSI: See BLK 16
13_DATE_OF_SUBSEQUENT_SUB: See BLK 16 addressee1:
draft1:
reg1:
repro1:
addressee2: 1. AFMETCAL draft2:
reg2:
repro2:
addressee3: Attn: Frank Capuano draft3:
reg3:
repro3:
addressee4: 813 Irving Wick Dr., W. Horton Building draft4:
reg4: 1 repro4:
addressee5: Heath, OH 43056 draft5:
reg5:
repro5:
addressee6:
draft6:
reg6:
repro6:
addressee7:
draft7:
reg7:
repro7:
addressee8:
draft8:
reg8:
repro8:
addressee9:
draft9:
reg9:
repro9:
addressee10:
draft10:
reg10:
repro10:
addressee11:
draft11:
reg11:
repro11:
addressee12: Ship to addressee draft12:
reg12: 1 repro12:
addressee13:
draft13:
reg13:
repro13:
addressee14:
draft14:
reg14:
repro14:
addressee15:
draft15:
reg15:
repro15:
addressee16:
draft16:
reg16:
repro16:
addressee17:
draft17:
reg17: 1 repro17:
addressee18:
draft18:
reg18:
repro18:
addressee19:
draft19:
reg19:
repro19:
addressee20:
draft20:
reg20:
repro20:
addressee21:
draft21:
reg21: 1 repro21:
addressee22:
draft22:
reg22:
repro22:
addressee23:
draft23:
reg23:
repro23:
addressee24:
draft24:
reg24:
repro24:
addressee25:
draft25:
reg25: 1 repro25:
addressee26:
draft26:
reg26:
repro26:
addressee27:
draft27:
reg27:
repro27:
addressee28:
draft28:
reg28:
repro28:
addressee29:
draft29:
reg29:
repro29:
addressee30:
draft30:
reg30:
repro30:
addressee31:
draft31:
reg31:
repro31:
addressee32:
draft32:
reg32:
repro32:
addressee33:
draft33:
reg33:
repro33:
addressee34:
draft34:
reg34:
repro34:
addressee35:
draft35:
reg35:
repro35:
addressee36:
draft36:
reg36:
repro36:
addressee37:
draft37:
reg37:
repro37:
addressee38:
draft38:
reg38x:
repro38:
total_draft: 0 total_repro: 0
16_REMARKS: BLK 8: The Government has 30 calendar days to review the preliminary draft. The contractor has 10 calendar days after receipt of Government comments to prepare and deliver revised data. Criteria for approval shall meet the Government comments. Reference the contract number in all correspondence. Final approval after first production acceptance.
BLK 9: The following statement shall be included on the manuals:
DISTRIBUTION STATEMENT D: DoD and US DoD contractors only
Blk 12: No later than 30 days after contract award, 1 copy(ies) of the final manual is(are) required on CD/DVD in indexed Portable Document Format (iPDF). Ship to addressee #1 listed in BLK 14a. If manuals are available electronically, the file or web link may be sent to frank.capuano@us.af.mil. Reference contract number in all correspondence.
Blk 13: No later than 30 days after after First Production Unit is accepted, 1 copy (ies) of the final manual is required. Manual shall be on CD/DVD in indexed Portable Document Format (iPDF). Ship to addressee #1 listed in BLK 14a.
Blk 13: Concurrent with delivery of production units contractor shall furnish and pack 1 set of the manuals with each unit. Manual shall be on CD/DVD in indexed Portable Document Format (iPDF). Ship with unit.
Blk 13: No later than 90 days after contract award, concurrent with delivery of first production units, the contractor shall furnish and pack 1 set of manuals with each of the first production units. Manuals shall be on CD/DVD in Indexed Portable Document Format (iPDF). Ship with unit.
17_PRICE_GROUP:
ESTIMATED_TOTAL_PRICE:
G_PREPARED_BY:
H_DATE: 2/27/2020
1_APPROVED_BY:
J_DATE: 2/27/2020
Page: 1 reg38t: 5
A_CONTRACT_LINE_ITEM_NO:
B_EXHIBIT: A(FY 20)
TDP:
TM: x
OTHER:
DSYSTEMITEM: Vision Measurement System
E_CONTRACTPR_NO:
FCONTRACTOR:
of_pages: 4
Reset:
2020-02-27T12:37:59-0500
CAPUANO.FRANK.R.1403209658
2020-02-27T15:09:46-0500
SKINNER.KEVIN.L.II.1024227223
DD FORM 1423-2, AUG 96
(2 Data Items)
The public reporting burden for this collection of information is estimated to average 220 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
TDP ________ TM _______ OTHER _________________________
11. AS OF DATE 13. DATE OF SUBSEQUENT
12. DATE OF FIRST SUBMISSION 14. DISTRIBUTION
Page ____ of ____ Pages
A_CONTRACT_LINE_ITEM_NO:
B_EXHIBIT: A(FY 20)
TDP: Off
TIM: Yes
OTHER:
D_SYSTEMITEM: Vision Measurement System
E_CONTRACTPR_NO:
FCONTRACTOR:
1_DATA_ITEM_NO1: A002
2_TITLE_OF_DATA_ITEM1: Software User Manual
3_SUBTITLE1:
4_AUTHORITY1: DI-IPSC-81443A
5_CONTRACT_REFERENCE1: PD 20M-271A-DI Atch
6_REQUIRING_OFFICE1: AFLCMC/WNMM
7_DD_250_REQ1: N/A
8_APP_CODE1: N/A
9_dist1: D
10_FREQUENCY1: ASREQ
11_AS_OF_DATE1: ASREQ
12_DATE_OF_FIRST_SUB1: See BLK 16
13_DATE_OF_SUBSEQUENT_SUB1: See BLK 16 addr1_1:
draft1_1:
reg1_1:
repro1_1:
1_DATA_ITEM_NO2: A003
2_TITLE_OF_DATA_ITEM2: Calibration Certificate
3_SUBTITLE2:
4_AUTHORITY2: DI-QCIC-80798C
5_CONTRACT_REFERENCE2: PD 20M-271A-DI Atch
6_REQUIRING_OFFICE2: AFLCMC/WNMM
7_DD_250_REQ2: N/A
8_APP_CODE2: N/A
9_dist2:
10_FREQUENCY2: ASREQ
11_AS_OF_DATE2: ASREQ
12_DATE_OF_FIRST_SUB2: See BLK 16
13_DATE_OF_SUBSEQUENT_SUB2: See BLK 16 addr2_1:
draft2_1:
reg2_1:
repro2_1:
addr1_2: Ship with unit draft1_2:
reg1_2: 1 repro1_2:
addr1_3:
draft1_3:
reg1_3:
repro1_3:
addr1_4:
draft1_4:
reg1_4:
repro1_4:
addr1_5:
draft1_5:
reg1_5:
repro1_5:
addr1_6:
draft1_6:
reg1_6:
repro1_6:
addr1_7:
draft1_7:
reg1_7:
repro1_7:
addr1_8:
draft1_8:
reg1_8:
repro1_8:
addr1_9:
draft1_9:
reg1_9:
repro1_9:
addr1_10:
draft1_10:
reg1_10:
repro1_10:
addr1_11:
draft1_11:
reg1_11:
repro1_11:
addr1_12:
draft1_12:
reg1_12:
repro1_12:
addr1_13:
draft1_13:
reg1_13:
repro1_13:
addr1_14:
draft1_14:
reg1_14:
repro1_14:
15_total_Draft1: 0
15_TOTALReg1: 1
15_TOTALRepro1: 0
16_REMARKS1:
BLK 12: Concurrent with the delivery of production units contractor shall furnish and pack one (1) Software User Manual with each unit.
17_PRICE_GROUP1:
18_totalprice1:
addr2_2: Ship with unit addr2_3:
addr2_4:
16_REMARKS2: BLK 12: Concurrent with delivery of first production unit, the contractor shall furnish and pack one (1) calibration certificate with each unit. Ship with unit.
17_PRICE_GROUP2:
18_totalprice2:
addr2_5:
addr2_6:
addr2_7:
addr2_8:
addr2_9:
addr2_10:
addr2_11:
addr2_12:
addr2_13:
addr2_14:
draft2_2:
reg2_2: 1 repro2_2:
draft2_3:
reg2_3:
repro2_3:
draft2_4:
reg2_4:
repro2_4:
draft2_5:
reg2_5:
repro2_5:
draft2_6:
reg2_6:
repro2_6:
draft2_7:
reg2_7:
repro2_7:
draft2_8:
reg2_8:
repro2_8:
draft2_9:
reg2_9:
repro2_9:
draft2_10:
reg2_10:
repro2_10:
draft2_11:
reg2_11:
repro2_11:
draft2_12:
reg2_12:
repro2_12:
draft2_13:
reg2_13:
repro2_13:
draft2_14:
reg2_14:
repro2_14:
15_total_Draft2: 0
15_TOTALReg2: 1
15_TOTALRepro2: 0
G_PREPARED_BY:
H_DATE: 2/27/2020
1_APPROVED_BY:
J_DATE: 2/27/2020
Page: 2 of_pages: 4
Reset:
2020-02-27T12:39:10-0500
CAPUANO.FRANK.R.1403209658
2020-02-27T15:10:39-0500
SKINNER.KEVIN.L.II.1024227223
File details come from the government source that posted it. Updated .