Attachment_02_-_Contractor_capability_Requirements_and_Definitions.doc

DOC document 44 KB Posted

Attached to
Logistics Support/Technical Data
Solicitation number
N00421-18-R-0044
Issued by

About this file

This document outlines capability requirements for contractors supporting technical manual lifecycle management services. Key requirements include processing various electronic data formats such as XML, SGML, S1000D, and PDF in accordance with specifications like MIL-STD-3001 and MIL-DTL-81310. Contractors must be conversant with such requirements and have the necessary infrastructure, software, trained personnel and facilities. Additional capabilities involve validating technical manuals, interpreting various source data types, reviewing furnished source data for completeness, and maintaining current instructional documentation and employee skill levels. Graphics must be converted at 600 DPI and include indexing data. Deliverables encompass revisable master files, user distribution file formats such as PDF, and archivable source data returned in PDF format with a record of incorporation.

Attachment 02 - Contractor Capability Requirements and Definitions

View the file

Other files

File Type Posted
RFP_N00421-18-R-0044_Questions_13_Sept_2018.pdf PDF
RFP_N00421-18-R-0044_Questions_11_Sept_2018.pdf PDF
Attachment_10_WD_15-4279_St_Marys_(Rev_6).txt TXT text file
Attachment_13_WD_15-4539_Duval_(Rev_7).txt TXT text file
Attachment_04_AMEND_1_DD254_signed.pdf PDF
Attachment 17_AMEND 1 00-25-604 - Jan 2018.pdf PDF
Exhibit_B__AMEND_1_Aug_17_2018.xlsx XLSX spreadsheet
Attachment_02__AMEND_1_Contractor_capability_Requirements_and_Definitions_(1).doc DOC document
Attachment_P7_AMEND_1__Annual_Fully_Burdened_Labor.xlsx XLSX spreadsheet
Attachment_16_WD_15-4553_Orange_(Rev_8).txt TXT text file
ATTACHMENT_18_AMEND_1__NGEN_IT_requirements.docx DOCX document
Attachment_11_WD_15-5603_Kern_(Rev_8).txt TXT text file
Attachment_12_WD_15-5781_Craven_(Rev_7).txt TXT text file
Attachment_09_WD_15-5625_Ventura_(Rev_7).txt TXT text file
Attachment_14_WD_15-4195_Ocean_(Rev_7).txt TXT text file
Attachment_15_WD_15-5635_Sandiego_(Rev_9).txt TXT text file
Attachment_P6_AMEND_1_Cost_Summary_Spreadsheet.xls XLS spreadsheet
RFP_N00421-18-R-0044_Amendment_1_30_August_2018.pdf PDF
RFP_N00421-18-R-0044_Questions_27_Aug_2018.pdf PDF
Attachment_01_Applicable_Specifications_and_Standards_July_25_update.docx DOCX document
Attachment_15_WD_15-5635_Sandiego.txt TXT text file
CDRL_A004_Software_Development_Plan_rev_23_Mar_2018.pdf PDF
Attachment_P4_Past_Performance_Information_Form_Mar_2017.pdf PDF
Attachment_05_FFP_CLIN_0007__Req_Unit_Desc.docx DOCX document
Attachment_P5_Contractor_Performance_Assessment_Questionnaire_May_2016.pdf PDF
Attachment_12_WD_15-5781_Craven.txt TXT text file
Attachment_P6_Cost_Summary_Spreadsheet.xls XLS spreadsheet
CDRL_A006__OPSEC_Plan_rev_Oct_13_2017.pdf PDF
CDRL_A005_Quality_Program_Plan_May_17_2018.pdf PDF
Attachment_03_Surveillance_Activity_Checklist_Feb_07_2018.doc DOC document
Attachment_07_IT_Positions_Process_for_Contractors_dtd_5-22-18.docx DOCX document
Attachment_P7_Annual_Fully_Burdened_Labor_Attachment_(Mar_2017).xlsx XLSX spreadsheet
Attachment_09_WD_15-5625_Ventura.txt TXT text file
Attachment_04_DD254_signed.pdf PDF
CDRL_A007_Technical_Documentation-_Report.pdf PDF
Attachment_14_WD_15-4195_Ocean.txt TXT text file
RFP_N00421-18-R-0044_24_July_2018_FINAL.pdf PDF
Attachment_13_WD_15-4539_Duval.txt TXT text file
CDRL_A003__Over-arching_contractors_management_report.pdf PDF
Attachment_16_WD_15-4553_Orange.txt TXT text file
CDRL_A001_status_report_(Revised)_Individual_Task_Order_Report_Rev_Oct_13_2017.pdf PDF
Exhibit_B_FFP_Item-_May_23_2018.xlsx XLSX spreadsheet
Attachment_11_WD_15-5603_Kern.txt TXT text file
Attachment_10_WD_15-4279_St_Marys.txt TXT text file
Attachment_06_Technical_Manual_Types.doc DOC document
CDRL_A002_funds_management__(Revised)_Funds_and_Man-Hours_Expended_Report_Oct_13_2017.pdf PDF
Attachment_08_SAAR-N-OPNAV_5239_14.pdf PDF
Show all 47

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

ATTACHMENT 2

CONTRACTOR (BASELINE) CAPABILITY REQUIREMENTS

The following capabilities and requirements apply to the extent defined by individual task orders:

1. The inventory of Naval Aviation technical data includes both traditional paper publications and emerging levels of electronic data types. These electronic data types, may be formatted in Extensible Markup Language/Standard Generalized Markup Language (XML/SGML) structured in accordance with MIL-STD-3001, MIL-DTL-81310, S1000D, or legacy specifications. The contractor shall have baseline capability to accept and process various file formats. Baseline capability is defined as the infrastructure of necessary hardware, software applications, trained personnel and facilities to accept and successfully perform processing (e.g., management, update, conversion, etc.) to data written to the specifications listed. The contractor shall return the technical data to the government in the formats and media specified in the task order. Data must be usable with existing NAVAIR approved versions of software and hardware. Specific requirements may be added to task orders, but will normally consist of the following software packages:

PTC Arbortext Family

PTC ISODraw/ISOView Family

Autocad

Adobe Framemaker

Adobe Acrobat Professional

Adobe Creative Suite (includes Illustrator and Photoshop) Microsoft Word

2. The contractor shall be fully conversant with the requirements of the applicable specifications including, but not limited to S1000D, MIL-STD 3001, and MIL-DTL-81310 and those listed in Attachment 2 of the Statement of Work (SOW). The latest versions of the specifications cited in the Department of Defense Single Stock Point (DODSSP), at http://dodssp.daps.dla.mil, at time of task order award shall apply, unless otherwise indicated in task orders. Amplifying instructions, deviations, and all required source data for accomplishment of tasks, will be cited in each individual TMCRWS/Task Order. Final interpretation of specification requirements and approval/issuance of deviations are the sole responsibility of the NAVAIR 6.8.5 Policy Office. All deviations shall be requested in writing with supporting rationale, via the Task Order Contracting Officer’s Representative (TOCOR), and approval must be obtained, in writing, prior to authorization to deviate from specification requirements. Changes to Government Furnished Document Type Definitions, Formatting Output Specification Instances, Style Sheets and Viewers are prohibited unless authorized by the NAVAIR 6.8.5 Policy Office via task order.

3. Contractor shall comply with Government security programs and requisite protective measures.

4. Efforts involving classified material shall be performed in accordance with DOD 5220.22-M, Industrial Security Manual for Safeguarding Classified Information. All classified documents will be page and paragraph marked as required by DOD 5220.22-M, as modified by OPNAVINST 5510.1H, Department of the Navy Information and Personnel Security Program Regulation. At a minimum, for digitally formatted manuals the contractor shall apply DoN approved and registered XML Metadata tags at the Element Level for Security Code and Special Handling Code Elements, with the addition of DODI 8500.2 compliant System-level and Data Level attributes.

5. The contractor shall validate all TMs or source data furnished under this contract in accordance with MIL-PRF-85337(AS) and the contractor’s Quality Assurance Plan approved by the government. Initial guidance meetings and in-process reviews will be conducted by the government on an as required basis, as scheduled jointly between the government and the contractor.

6. Contractor shall be skilled in ability to interpret a variety of source data types applicable to the management of technical manuals. Source data may be a complete draft or marked-up copy of the manual; it may include a printed copy of the manual, reproducible copy and art work, negatives, sketches, photographs, and digital files. Source data may include approved Engineering Changes, Technical Directives, engineering drawings, government written manuscript copy, TM Source Data Records (TMSDRs), dispositioned Technical Publication Deficiency Reports (TPDRs) and/or other documentation required by the contractor to prepare the items ordered.

7. Contractor shall review Government furnished source data, verify completeness, and identify missing or incomplete data as soon as possible.

8. The following shall apply to all graphics processed as part of the data conversion efforts performed by the contractor:

· Graphics shall be converted at a density of 600 dots-per-inch (DPI) into requisite CGM, SVG, TIFF, or JPEG formats.

· Graphic formats shall permit use of hypertext linkage or “hot spotting”.

· All black and white graphics will be delivered as TIFF raster using CCITT Group 4 compression. Gray scale, color or half tone graphics will be delivered as Encapsulated Post Script (EPS) with no compression as best available data. Color graphics will use the CMYK color standard.

· Graphics will be “de-speckled” and “de-skewed” during the scanning process.

· Graphics will be reviewed and quality checked against the original assuring the data to be as close to the original as possible. Any graphic not meeting this standard will be rescanned and re-processed as required to obtain a good image.

9. JEDMICS compliant image formats shall include requisite indexing data and must successfully pass NAVAIR repository’s QA and archival processing.

10. It is the Contractor's responsibility to maintain the most current issue or changes of instructional documentation and to ensure that the Contractor's employees have a thorough working knowledge of the instructions and procedures relevant to their particular tasking and that they are kept abreast of any changes that apply to the technical tasks defined in their task order. It is the contractor’s responsibility to maintain employee skill levels adequate for the performance of the tasks required by task order.

11. DEFINITIONS

(1) Revisable master files shall encompass both text and illustrations and shall be furnished in any of the following formats as identified in the TMCR Work Statement/Task Order:

a. For text: Standard Generalized Markup Language (SGML)/Extensible Markup Language (XML), using government furnished Document Type Definitions (DTDs) such as MIL-STD-3001, MIL-DTL-81310, and S1000 schema, NAVSEA C2 DTD, E-6 Program DTDs, etc.) or Commercial Off-the-Shelf (COTS) formats developed from word processing software packages (e.g., Word, Interleaf, Framemaker, etc.) as designated by the government.

b. For illustrations: Digital delivery requirements of new or changed/revised illustrations shall be in any of the following formats as identified in the TMCR Work Statement/Task Order:

For new illustrations: Computer Graphics Metafile 4 (CGM 4) and/or Scalable Vector Graphics (SVG) in accordance with MIL-PRF-28003.

For revised illustrations: Computer Graphics Metafile 4 (CGM 4) in accordance with MIL-PRF-28003, or other formats prepared from COTS software packages as authorized in the TMCR Work Statement/Task Order.

(2) User Distribution File Formats encompass output formats such as Portable Document Format (PDF) or post-parsed files or databases suitable for the NAVAIR Standard Viewer (HTML or XML). All PDF files delivered under the definition of User Distribution File Format shall be in accordance with NAVAIR 6.8.5 requirements posted on the NATEC website at www.natec.navy.mil – refer to Naval Air Systems Command PDF Technical Manual Conversion/Preparation for Web Posting Policy, located under NAVAIR Technical Data Policies and Processes/Technical Manuals/Distribution/Policy Documents. When the TM Issue Type is a Change, a second file consisting of just the Change Pages and Backup pages required for initial printing and distribution shall be provided in addition to the fully collated User Distribution File Format for web posting.

(3) Portable Document Format (PDF) Terms used by NAVAIR:

a. Bookmarks – Links displayed in a PDF window next to the source document (e.g. technical manual). Refer to Naval Air Systems Command PDF Technical Manual Conversion/Preparation for Web Posting Policy, posted to www.natec.navy.mil, under NAVAIR Technical Data Policies and Processes/Technical Manuals/Distribution/Policy Documents. See Bookmark Generation.

b. Searchable - Optical Character Recognition (OCR) has been performed on scanned documents and it is possible to search the document for specific words without manual intervention. Refer to Naval Air Systems Command PDF Technical Manual Conversion/Preparation for Web Posting Policy, posted to www.natec.navy.mil, under NAVAIR Technical Data Policies and Processes/Technical Manuals/Distribution/Policy Documents.

c. Non-Searchable - Any document (e.g. technical manual) that has been digitally scanned to PDF, but Optical Character Recognition (OCR) has not been performed to permit a text search capability.

(3) Archivable Source Data encompasses all source data, including review copy markup and Manual Evaluation Records furnished to the contractor by the government under the applicable task order. All source data shall be returned to the government in PDF format at the end of the task order. A Record of Source Data Incorporation shall accompany the source data and completed TM product.

(4) Direct Image Copy - Printed copy of the finished product that is of sufficient quality as to allow for reproduction and delivery to end users.

(5) Job Performance Aids (JPAs) or Multi-media JPAs (MJPAs) are a supplement to a TM, or TD, that integrate textual, visual, and in selected cases, audio information. JPAs are intended to improve human performance, increase understanding, and provide clarification of tasks or procedures through visual enhancement of unaltered technical data. JPAs do not replace information in TMs or TDs, but supplement them in areas where additional clarification may be helpful. JPAs shall be distributed only with the TM. Requirements for JPA development and management have been described in NA-00-25-604 available on www.natec.navy.mil.

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