SOW REV A 4.23.21.docx

DOCX document 27 KB Posted

Attached to
Data Digitization Services Federal contract opportunity
Solicitation number
N0042121Q0312
Issued by
Department of the Navy Naval Air Systems Command Naval Air Warfare Center

View the file

Other files for this federal contract opportunity

Other files attached to Data Digitization Services, newest first.
File Type Posted
N0042121Q0312U0001.docx DOCX document
N0042121Q0312.docx DOCX document

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

STATEMENT OF WORK (SOW)

Project Title: Document Scanning Services

Introduction/Background/Scope PMA209 Fleet Support Team (FST) has a requirement to digitize avionics Technical Data (Tech Data) allowing availability of the tech data for fleet use.

The FST requires the digitization of various media formats such as Aperture Card, Microfiche, and paper to include sheet and roll size engineering media.

Quantity of media requiring digitization

· Aperture Cards – 159,142 ea

· Microfiche – 16mm Format – 9,600 fiche, 40 images per fiche, totaling 384,000 images

· Large Format Drawings – 1060 ea

Technical Requirements The contractor shall deliver the digitized media in both the Native TIFF and PDF file formats. The file name for both formats shall be the same. The contractor shall populate an IMAGE row for both the Native TIFF file format and the derived PDF file format.

Optical Character Recognition (OCR) shall be performed on all PDF object files. The image shall have no less than 300 DPI resolution.

The contractor shall document the digitization of the scanned object files by utilization of the PMA-209 provided RST import template. The RST file format is excel and contains conditional formatting facilitating error free documentation.

Once the RST import file is fully populated the resultant outcome will allow timely ingestion of all the object files and its associated metadata into the NAVAIR data repository.

Quality PMA-209 reserves the right to request a rescan if the image quality is collaboratively deemed poor or unacceptable. PMA-209 will communicate with the contractor regarding suspect images and determine if rescanning is required.

RST Sample The contractor shall provide a sample of five multi-sheet output files utilizing the RST template. The sample will be provided to the PMA-209 Tech Data Lifecycle manager for review to ensure the metadata is documented correctly within the RST and allow the contractor confidence that the work being performed meets the intent of the scanning effort. Once the sample is reviewed for compliance the contractor will receive direction for the remaining object scans. The Sample does not need to provide the Object file but shall contain all the IMAGE row metadata information for the TIFF and the derived PDF.

Media Transfer PMA-209 will/has provided the contractor an approved storage device for the transfer of the digitized media. NAVAIR policy restricts the use of flash technology as an approved media storage device The drive shall be encrypted and the contractor shall coordinate the transfer of the drive back to PMA-209 and the decryption of the hard drive.

Multiple sheets on one Aperture Card or Microfiche (Multi-up) The contractor shall crop out each sheet if the media contains multi-up data. Each sheet will then be indexed in the RST import file.

Destruction Once the delivered technical data has been successfully loaded into the government’s repository PMA-209 will formally request the destruction of the source data in accordance with DOD policy Object file Naming Convention The naming convention for the object files shall be as follows:

Note: If the Hollerith contains the Document Type it shall be included in the naming convention subsequent to the sheet revision

RST Table Definitions RST Table Definitions

RST Index Number
RST Field Name
FST Value definition
Value if predefined
Notes
1
IMAGE
Predefined value
IMAGE
Mandatory
2
DocNumber
Document Number of scanned object file

Mandatory

3
DocCAGE
CAGE Code of the scanned Document

Mandatory

4
DocType
Document Type of the scanned document

Mandatory if populated in the Hollerith

5
DocSize
Document Size

Mandatory

6
DocRev
Document Revision

Mandatory

7
DocRevDate
Document Revision Date

Mandatory

8
DocTitle
Document Title

Mandatory

9
SheetNumber
Sheet number of the object file

Mandatory

10
NumberofSheets
Total number of sheets that define the multi-sheet document

Mandatory

11
SheetRevision
Revision of the sheet

Mandatory

12
FrameNumber
Frame number if the Object was digitized using multiple photos (Typical for roll sizes)

Mandatory

13
Number of Frames for sheet
If object has multiple frame list total number of frames that make the object complete

Mandatory if multi-frame

14
File Type
TIFF Object Row
20
Mandatory
PDF Object Row
29
Mandatory
21
File Name
File name of the IMAGE Row object file without file extension

(No file extension)

Mandatory

22
File Extension
File extension of the IMAGE Row object file

(Do not include period)

Mandatory

27
Security Level
Predefined value
N
Mandatory
30
Nuclear
Predefined value
N
Mandatory
31
Subsafe
Predefined value
N
Mandatory
35
Control Code
Predefined value
KJ
Mandatory
50
Distribution Statement
Predefined value
C
Mandatory
58
UIC
Predefined value
N00019
Mandatory
59
RevOrder
Predefined value
99
Mandatory
62
TDAC
Predefined value
A
Mandatory
64
Export Control
Predefined value
Y
Mandatory
65
Object Type
Predefined value
DR
Mandatory
67
FLD Temp ID
Predefined value
PMA-209
Mandatory

RST Example (Yellow highlighted fields shall be prepopulated values on each image row) Notes:

1. The below index numbers shall be populated… All other RST index number fields shall NOT be populates

2. An IMAGE row shall be indexed for the TIFF and the derived PDF object file (see below example)

Hollerith and/or output text file information The contractor shall provide all output log files for all aperture or other media conversion methods image1.emf image2.emf

File details come from the government source that posted it. Updated .