Attachment 0006 TMCR.doc

Tech Manual Contract Requirements (Universal)

FOLAV

Version 1

14 Feb 2011

Tech Manual Contract Requirements (Universal)

FOLAV

Version 1

14 Feb 2011

Attachment 0009

1. SCOPE: This document describes the Government’s requirements for Contractor development and integration of technical publication (tech pub) data that all design modifications to the FOLAV. There are two major elements, both of which include requirements for the Contractor:

1. Tech pub data content, which includes text and/or graphics.

1. Tech pub data characteristics, which include data medium, style and format, which are concerned with the data’s functionality and arrangement.

2. ORIENTATION: PM-LAV transitioned its volumes of LAV tech pubs to an interactive electronic technical manual (IETM) medium. While the user finds it a vast improvement over paper TMs, tech pub data rendered as IETMs require more intensive processing.

2. LAV IETM System: Elements of the IETM system include:

2. The LAV IETM viewer, software that can display the LAV tech pub data as an IETM or as a PDF that mirrors the style and format of the older paper TMs.

2. The tech pub data, which include narratives, graphics, tables, schematics and the like that are tagged to display in the IETM viewer as IETM or PDF and to enable IETM functionality. Tech pub data are hyperlinked in accordance with a protocol that reflects their logical relationship to other tech pub data.

2. The authoring software that renders new tech pub data to properly display and function in the IETM viewer.

2. Vehicle Variants: The FOLAV includes legacy and production versions of the LAV-25, -AT, -CC, -M, -R, -L and LAV-EW (previously called MEWSS) variants. The entire fleet is undergoing constant upgrades, some of which take years to apply to the fleet of targeted LAVs. In the past, paper tech pubs could reflect only the latest configuration for each variant.

2. IETM Capability: The LAV IETM can call up tech pubs that contain data reflecting any combination of LAV variant and design mods. It customizes the data “on the fly” to match the configuration of individual LAVs by using the vehicle’s serial number to access its design mod history. PM-LAV is making full use of this capability, which means that:

2. Tech pub data for new design mods shall include data to integrate with all possible current vehicle configurations.

2. The Contractor shall adjust its tech pub data to reflect configuration changes, up to the point when the design is formally accepted by the Government.

3. REFERENCES: The Contractor shall use the following documents as a guide for developing tech pub data. The style and format of existing LAV tech pubs and/or the requirements defined in this TMCR the “PM-LAV IETM Data Development Guidelines 01 Apr 2008” and the “USMCLAV1 Data Type Dictionary (DTD)” shall supersede this guidance in the event of a conflict. Any reference that applies exclusively to printed manuals shall be ignored by the contractor.

3. Directive Guidance, Reference, and Examples

3. PM-LAV IETM Data Development Guidelines 01 Apr 2008

3. USMCLAV1_XML DTD 19 Feb 2008

Note: The Data Type Dictionary is also contained in the “PM-LAV IETM Data Development Guidelines 01 Apr 2008”

3. LAV Graphics Naming Protocol 21 Jul 2010

3. DRS Converter-Styler Users' Guide 12 Mar 2007

3. USMC Maintenance Concept 04 Dec 2007

3. LAV IETM Val-Ver Checklist 11 Feb 2011

3. LAV Val-Ver Plan Feb 2011

3. General Guidance and Reference

3. PM-LAV Hyperlink Protocol 11 Feb 2011

3. LAV CGM Style Guide 12 Mar 2010 Note: Use the most recent version of the below references. Since military standards and specifications are updated often and freely accessible to the contractor via the internet, the version or date of publication is not included below to ease the administrative burden. If the contractor cannot locate or download the latest version, contact the Government’s COR (Contracting Officer’s Representative) to receive a copy.

3. MIL-Q-87270: Requirements for Quality Assurance Program for IETMs and Associated Technical Information

3. MIL-DTL-28999C: Preparation of Instruction-Type [I-Type] Technical Publications

3. MIL-I-28947C: Preparation of Illustrations for Stock List Publications

3. MIL-STD-38784: General Style and Format Requirements for DoD Technical Manuals

4. DEFINITIONS:

4. Contractor Furnished Information (CFI): Data provided by the Contractor in accordance with this TMCR that is to become part of the FOLAV tech pub data.

4. Design Mod: A hardware improvement that is permanently applied to one or more variants of LAV in order to improve its safety of use, performance, reliability, availability and/or maintainability.

4. Technical Planning Meetings

4. Front End Analysis Team [FEAT]: Marine maintainers, logisticians, Contractor representatives and other subject matter experts who analyze hardware designs to determine what operational and maintenance support it will require when fielded.

4. Maintenance Planning Meeting (MPM): Representatives from PM-LAV and the Contractor will meet to determine the operation and maintenance tasks based on the configuration of the design. All tasks shall be developed in accordance with the Marine Corps maintenance concept. The Contractor shall list all tools needed for each task incorporating maximum use of tools currently in the LAV maintenance tool set. The Contractor shall notify the Government of any special tools unique to support the design.

4. Hotspot: A location within a graphic or schematic which enables hyperlinking to other graphic or text locations within the LAV tech pubs.

4. Hyperlink: An easily identifiable number, word or phrase tagged to provide quick access between two logically related data. Hyperlinks are established in accordance with PM-LAV’s hyperlink protocol.

4. LAV IETM Viewer: A software solution for displaying the LAV Tech Pub Data.

4. LAV IETM Suite: The combination of all the software tools used to view, develop, sustain, and compile a ready-to install LAV IETM for the end user. This consists of the Convertor/Styler, Sustainment Tool, LAV IETM Viewer, and XML Editor Tool.

4. Converter/Styler: The software used to hotspot graphics by the contractor to generate draft PDFs and IETMs of their developed source data for review purposes. The Convertor/Styler is limited to drafts of single PDFs or IETMs. The Convertor/Styler creates a temporary XSL:FO file from the XML and Graphics source data, and sends that file to XSLFormatter to generate the PDF or IETM.

4. Sustainment Tool: software with the same capabilities as the Convertor/Styler, but with some additional functionality and the ability to compile some or all of the source data, instead of just single publications. Also has a capability to convert various templates prepared as source data and provide error reports on the data during compiling. The Master IETM is produced by the Sustainment Tool. Beta IETM’s are also produced by the Sustainment Tool to allow a contractor to test the functionality of their tech pub data integrated with the larger master set of tech pub data. The developer and the government are the only users of the Sustainment Tool.

4. XML Editor Tool: A software add-in for the Convertor/Styler and Sustainment Tool that provides a WYSIWYG style editing capability. (This is a future addition that may or may not be available during this contract, but the definition is included in case it becomes available for use or for informational purposes in case the topic is discussed during the course of the contract.)

4. LAV IETM: A combination of tech pub data and software which enables it to display and makes it interactive when viewed on PCs and laptops. Tech pub data is digitized and rendered by means of an automated authoring system into a form and style suitable for the viewer. Logically related data are hyperlinked so that the end user can access information via a number of paths. There are seven versions of the LAV IETM which are determined by the stage of the development process the tech pub data is at.

4. Stand Alone IETM: A single draft copy of an IETM publication rendered by the Convertor/Styler software for various reviews by the contractor during the development process. This version of the IETM is a draft and the contractor may render a large number of these throughout the development process in order to view ongoing incorporation of their Tech Pub Data during the editing process.

4. TPD Working Copy: This is a raw draft set(s) of tech pub data that the contractor is developing in-between the major development events. This data is managed by the contractor under their own document control processes. The contractor may provide sections of their working copy to the government for test conversions/review/comment during development and may be required if agreed to in the SOW Meeting. This is especially advantageous for contractors who are not yet familiar with PM-LAV’s particular DTD or IETM.

4. Pre Val/Ver Tech Pub Data: The draft tech pub data authored/developed by the contractor and provided to the government for a full conversion into a (Pre Val/Ver) Beta IETM for the validation/verification efforts.

4. Beta IETM(s): A draft copy of the IETM(s) into which the government has integrated the Contractor’s design mod tech pub data for a formal review event, such as the validation, verification, post val/ver review or other activities designated by the main contract.

4. Post Val/Ver Tech Pub Data: The draft tech pub data which includes the data adjusted by the contractor to correct the discrepancies found during the government’s verification event.

4. TPD Final Deliverable: This is the final version of the data delivered for the government to accept, integrate into the Master IETM and distribute to the LAV Community’s IETM users.

4. Master IETM: The copy of whole LAV IETM Viewer, which represents the authorized compiled/distributed version of LAV tech pubs and software for Marine Corps operators and maintainers.

4. Modification Instruction (MI): A document prepared by the Government or a contractor using the government furnished template and in accordance with specified regulations, validated/verified and, signed by the PM once approved. It contains information essential to the installation of a design mod, to include the complete equipment preparation and design mod installation task and related requirements.

4. SME: Subject matter expert.

4. Source Data: TDP, source drawings, ECP, schematics, memoranda, etc. produced by the design developer and/or the Government that are needed by the Contractor to generate the applicable tech pub data.

4. Style/Format/Function: The manner in which tech pub data is structured and functions when viewed in PDF or IETM modes.

4. Tech Pubs: Volumes of tech pub data that are provided for each LAV vehicle variant and that reflect the USMC maintenance concept.

4. Tech Pub Data: Text, graphics, schematics, and/or tables that are developed by the Contractor to reflect a change in vehicle configuration, and/or to replace/adjust existing data contained within LAV tech pubs. Data granularity extends to TM paragraphs for operation/maintenance and to figures/tables for TMs, SL-3s and SL-4s.

4. Tech Pub Data Developer: The commercial or Government organization responsible for drafting, correcting, rendering and integrating tech pub data content into the LAV pub data so that it can be viewed and fully functional in the LAV IETM Viewer.

4. TPD Errors. Discrepancies of any type discovered in existing tech pub data

4. Simple Errors. Discrepancies existing in the tech pub data which are administrative in nature such as obvious typos, renumbering of steps, lists, incorrect nomenclature, graphic call-outs and labels, clarifications and the like. These are errors that once corrected will not require a full validation/verification, but are taken at face value.

4. Complex Errors. Discrepancies existing in the tech pub data that cause compound adjustments that can extend into multiple sections of the tech pub, and require validation/verification once corrected.

4. Correction Request. A formal request made by individuals in the military, government, or a defense contractor to correct a TPD Error. (Not for TPD under development, but that which is already published.)

4. Kick-off (KO) meeting. A meeting held between the government and the contractor at the beginning of each work directive to discuss the details of the specific design mod in relation to this TMCR.

5. GENERAL REQUIREMENTS: The Contractor shall render tech pub data to conform to PM-LAV’s system for managing and displaying tech pub data (described in Para 2).

5. All of the tech pub data generated by the contractor shall:

5. Properly display and function within the PM-LAV IETM.

5. Belong to PM-LAV. This shall include all narratives, tables, graphics, and schematics, as well as models developed to generate illustrations.

5. The Contractor will coordinate with PM-LAV to resolve problems. The Contractor shall implement changes that are necessary to resolve problems integrating its tech pub data into the TPD Final Deliverable.

5. Tech pub data content: The Contractor shall produce tech pub data that include narratives, graphics, schematics and tables reflecting the Contractor’s change(s) in LAV design configuration(s) and satisfy the following conditions:

5. The Contractor shall conform to non-disclosure agreements required (Unilateral NDA WebTM PM-LAV May 2009) for use of proprietary software and/or imposed by the Government in order to qualify for access to GFI design mod source data and/or software.

5. The Contractor shall generate tech pub data that encompass all configurations covered by the specific work directive. [See Para 6.g.(3)]

5. The MI shall be a PDF document that reflects configuration management (CM) data derived from the final version of the Contractor’s Government-approved tech data package (TDP) and engineering change proposal (ECP). The MI shall be developed during a trial installation of the design mod. The Government highly recommends that the Contractor use this occasion to develop other task-related tech pub data deemed by (FEAT or MPM) as required for remove/replace and/or repair narratives and/or related digital photographs. All data targeted for the LAV tech pubs shall reflect the MI. Data shall include creation of and/or adjustments to text (narratives, tables) and/or graphics (including schematics) for every location within every volume of LAV tech pubs that is affected by the design mod.

5. Correction of Existing Errors: The Contractor shall identify and correct all TPD errors [See 4.n.] in the portions of the tech pub data affected by the design mod being updated by the contractor. This shall exclude tech pub areas where only links or locater graphics are updated, or supply information related changes, (e.g., Total quantity used on equipment) that are indirectly impacted by the design mod. The contractor shall maintain a log in Microsoft Excel © of TPD errors/omissions it finds and corrects in the course of its tech pub data development, which it shall make available to the Government upon request.

5. In developing tech pub data that supports its design mod, the Contractor shall make maximum use of existing tech pub data.

5. The contractor shall work from the fresh version of GFI source tech pub data provided in accordance with the contract.

5. The Contractor shall prepare a list of all portions to be revised in relation to the work directive down to the paragraph (maintenance tasks) and figure (Repair Parts Listings) level in the GFI template TPD Revision Tracker template or in a contractor formatted document as long as it contains the same elements as contained in the government template. If the contractor determines later in the development process that additional tasks/figures require adjustment, the Government shall be notified and an updated list will be provided to the Government as quickly as possible. If the total time for the specific work directive exceeds three months, the contractor shall request a government review of those data sections to determine if the government should provide the contractor with a new set of tech pub data, just for those sections not originally identified during the start-of-work or kick-off meeting. In most cases, new data will not be required.

5. The Contractor’s tech pub data shall:

5. Contractor shall generate tech pub data that encompass all configurations covered by the specific work directive. [See Para 6.g.]

5. Narratives shall:

5. Be tagged in accordance with the GFI “USMCLAV1_XML DTD 19 Feb 2008,” and the “PM-LAV IETM Data Development Guidelines 01 Apr 2008.” All tech pub data shall be tagged in accordance with existing LAV tech pub syntax and semantics. The Contractor shall make full use of the DTD and shall get Government permission to make use of tags that must be added to the DTD or to repurpose an existing tag.

5. The Contractor is strongly urged to use GFI software (Convertor-Styler Application) especially designed to work with PM-LAV’s IETM viewer in rendering its tech pub data. The Government will use these software packages in evaluating the Contractor’s tagged tech pub data.

5. Include all of the elements that appear within the section of tech pub being adjusted, such as TOOLS, MATERIALS, PRECONDITIONS, WARNINGS, etc. (see MIL-STD-38784). The content of the data must be so written as to be indistinguishable in style and format from existing data when it is integrated into the LAV tech pubs.

5. Be written in simple, practical English. All terminology, symbols, and abbreviations shall be readily understandable by Marine operators and maintainers. Abbreviations shall be defined the first time they appear in the text. The Contractor shall use nomenclatures already established in the LAV tech pub data, wherever possible. Any nomenclatures introduced by the Contractor’s shall be consistent throughout the Contractor’s tech pub data.

5. Graphics: The Contractor shall generate graphics, to include schematics, that conform to the style/format/functionality of existing tech pub graphics and to the following:

5. All new graphics shall be CGM (version 4). Existing raster graphics requiring significant modification shall be re-done as CGMs. Existing raster images requiring minor adjustments many be converted to vector CGM or may remain as a raster image if the image is otherwise accurate and of high quality. When a raster graphic contains significant evidence of previous revisions, such as speckling, blurring, overly jagged lines or other distortions, the raster image will not be reused regardless of the size of the modification that will be performed to the graphic and a new vector CGM shall be developed by the contractor.

5. The Contractor shall assign graphic IDs (GIDs) to its graphics using a block of serial numbers assigned by the Government and in accordance with the “LAV Graphics Naming Protocol 21 Jul 2010.” (see Attachment X)

5. New/modified graphics shall conform to requirements in MIL-I-28947C and the LAV CGM Style Guide that are implemented in the LAV tech pubs.

5. Schematics: The Contractor shall update all LAV tech pub electrical, hydraulic and/or pneumatic schematics affected by the design mods. CFI schematics shall include:

5. Adjustment of existing schematics (Note: if schematics provided to the contractor as GFI source data do not match the current configuration due to ongoing upgrade efforts, the contractor shall develop a schematic depicting the unique circuit related to the design mod integration. This schematic will show the locations where it connects to the main systems. This will provide technical illustrators an accurate circuit schematic for updating the main schematic at a later date, and ensuring the maintainer has the technical information represented by the schematic for troubleshooting purposes.

5. Schematics internal to the design mod when:

5. (FEAT or MPM) deems repair of components to be economical and/or

5. Schematics are required for testing design mod component functionality.

5. Tables: The Contractor shall load data appropriate to existing tech pub tables that have been impacted by the design mod. The Contractor shall include state, truth, or condition tables (Charts which simplify the input/output signals of circuit/equipment conditions in contrast to the changing variables during the various operational functions.) where a simplified chart view in conjunction with CFI schematics and/or flowcharts are needed by maintainers for understanding/testing the functionality of design mod components.

5. The government will have 30 days to review the post val/ver delivery and provide comments to the contractor.

5. The Contractor shall make corrections up to 30 days after the government provides its post val/ver comments identifying adjustments to content or functionality (e.g., linking) that were originally documented by the government during the val/ver and within the scope of the contract.

5. Tech Pub Data Characteristics:

5. Style/Format/Functionality: The Contractor shall generate its tech pub data in a digital medium that conforms to the following requirements:

5. The data shall display in the LAV IETM Viewer in either PDF or IETM mode.

5. The style and format shall be so configured as to be indistinguishable from the tech pub data into which it is to be integrated. See style and format of existing tech pub data and MIL-STD-38784. The Contractor shall tag its tech pub data to the same functionality as similar data already contained within the LAV tech pub.

5. The Contractor shall ignore all guidance within the references cited in Para 3 that relate solely to the preparation of paper tech pubs.

5. Contractor data to be inserted into the SL-3’s for all variants and the LTI (Limited Technical Inspection) shall be formatted in accordance with GFI templates. Changes will be in red font. Data in the spreadsheet that will remain the same should be left alone and in black font.

5. Graphics: The Contractor shall generate graphics that conform to the style/format/functionality of existing tech pub graphics and to the following:

5. New/modified graphics format shall conform to requirements in the “LAV-CGM-Style-Guide_12Mar2010” and be linked in accordance with instructions in the “Converter DRS Converter-Styler Users' Guide 12 Mar 2007” for LAVs that are implemented in the LAV tech pubs (see Attachment X).

5. Contractor-generated and/or modified graphics shall be provided to the Government in their own file and which shall accompany narratives, tables and related tech pub data.

5. Hyperlinks: The Contractor’s tech pub data appearing in narratives, graphics, schematics and tables shall be hyperlinked to related data located throughout the LAV tech pubs in accordance with the PM-LAV hyperlink protocol (see Attachment X).

6. SPECIFIC REQUIREMENTS:

6. Start of Work (SOW) and (or) Kick-off (KO) Meeting: The Government and Contractor shall meet before the start of tech pub data development/adjustment/integration to go over in detail the requirements contained within this TMCR. The meeting may be part of a more comprehensive SOW or KO meeting. The Government will arrange for representation of other contractors that are to be involved in the tech data development/integration as required. The agenda shall include:

6. The development and finalization of a schedule of major activities that fits within the larger sequence of events for developing, testing, manufacturing and fielding the Contract’s design mod as described elsewhere in this Contract. [see Para 9]

6. A review of how the Government and Contractor will manage tech pub data Quality Assurance (QA), to include:

6. The Contractor’s or Government’s Validation/Verification Plan (VVP) or Quality Assurance Plan (QAP), with an emphasis on its data tracking concept (when required)

6. The Government’s plan for reviewing the Contractor’s tech pub data.

6. The Government’s criteria for acceptance/rejection of the Contractor’s tech pub data.

6. The resources that the Contractor shall provide for the reviews mandated by this TMCR.

6. How schedule conflicts or other issues that may arise during tech pub data handoffs are to be accomplished.

6. Defining requirements for tech pub data delivery to support design mod developmental testing and reviews, as required by this contract.

6. Final integration of the Contractor’s tech pub data. The meeting will address potential problems between the Contractor’s tech pub data and the LAV IETM system.

6. The minutes will document points of consensus and Government direction having a bearing on the execution of this TMCR’s requirements. The Government shall review the minutes and provide comments within ten business days. The minutes shall be considered finalized and part of this Contract’s requirements after all points of contention are addressed and resolved to the Government’s satisfaction. Any new requirements that are documented in the meeting that would add scope, instead of added clarification or details for existing requirements will be reviewed for possible contract modification in a separate meeting.

6. Front End Analysis Team (FEAT) or Maintenance Planning Meeting (MPM): The Government and Contractor shall form a (FEAT or MPM) whose functions include planning for the development of the design mod’s tech pub data. To cover the tech pub data side of (FEAT or MPM), the team shall include at least one Government representative who is a maintenance subject matter expert (SME) and at least one Contractor representative with maintenance background who is also responsible for drafting the tech pub data. The team will meet to determine the operation and maintenance tasks that are based on the configuration of the design mod and that are to be developed in accordance with the Marine Corps maintenance concept and that are based on the configuration of the design mod. The Contractor shall list the tools needed for each task reflecting maximum use of tools already included in the LAV maintenance tool sets, and shall notify the Government whenever a task requires a special tool unique to the support of the design mod.

6. Tech Pub Data Processing: The Contractor shall develop and publish all tech pub data for the design mod.

6. Version of Tech Pub Data – The contractor shall develop their tech pub data from the GFI source data provided in accordance with the (contract or work directive).

6. Data Development: The Contractor shall develop all tech pub data (narratives, tables, graphics, schematics, etc.) required by its design mod that reflects (FEAT or MPM) findings/directions.

6. Data Style/Format/Functionality:

6. The tech pub data shall conform to LAV tech pub formats when displayed as either PDF or IETM. In the rare occasion when the nature of the Contractor’s tech pub data requires a unique data structure, the Contractor shall obtain clarification from the Government for alternate tags that satisfy it.

6. The Contractor shall render the data to display and function properly as a PDF or IETM. The Contractor is strongly advised to use PTC’s Arbortext Editor. The Contractor may subcontract this to specialists, but they must know how to use the Contractor’s chosen software, and they must so render the data as to make it indistinguishable from the style and format of existing tech pub data when viewed as PDFs and IETM.

6. Once the contractor completes the Pre Val/Ver Tech Pub Data, it shall be furnished to the government for review and integration into a beta IETM to be furnished back to the contractor, allowing the contractor to review and conduct quality reviews on their tech pub data as integrated with a full beta version of the LAV IETM.

6. The contractor shall make further adjustments to their tech pub data as necessary to meet the requirements of this TMCR and provide back to the government.

6. Once satisfied, the contractor shall be provided a version of the beta IETM consisting of their tech pub data as ready for the validation/verification effort.

6. Validation/Verification (Val/Ver): The Government and Contractor shall conduct an assessment of the tech pub data content. The review shall include parts data, operation, removal/replacement and/or repair tasks on design mod components. A full style/format/linking verification will be conducted by the Government on the Contractor’s developed/adjusted tech pub data in the Beta IETM.

6. The Contractor shall maintain records showing dates of contractor validation, material reviewed by task or action, findings with applicable remarks, and action taken IAW ISO 9001 or a similar and reputable document control process. The Government representative reserves the right to examine these records at the contractor's facility.

6. The assessment shall include the physical performance of 100% of operation, trouble-shooting, remove/replace and repair tasks generated by the contractor, except those which the government determines that a table top review will be sufficient. In addition a full style/format/linking verification will be conducted by the Government on the Contractor’s developed/adjusted tech pub data in the Beta IETM.

6. The Contractor shall adjust design mod tech pub data to correct for shortcomings/errors found during the review at no cost to the Government. All Government comments/direction provided to the Contractor at the val/ver regarding adjustments to the tech pub data shall be considered as final.

6. The Contractor shall provide personnel who can address Government concerns with the tech pub data content and (or) functionality.

6. The Contractor shall provide sufficient computer hardware for the style/format/linking verification throughout the val/ver event.

6. The Contractor shall provide its plan to update/correct the tech pub data.

6. Concurrent with its review of tech pub data content, the Government will conduct a desktop review of Contractor compliance to tech pub data style/format/functionality requirements defined in this TMCR.

6. The Contractor shall deliver corrected tech pub data on DVD/CD-ROM media no later than 30 business days after completion of the val/ver.

6. In accordance with the SOW Government acceptance of the TPD Final Deliverable will occur using the following process:

6. Post Val/Ver Review: The Government will conduct a 30 day Post Val/Ver desktop review for those corrections identified during the val/ver. The resulting final comments/adjustments will be incorporated by the Contractor prior to the TPD Final Deliverable, which will be 30 days after receipt of the government’s comments.

6. During the post val/ver review of the Contractor’s tech pub data the government will determine if errors/omissions in tech pub content that were identified during the val/ver have been corrected.

6. The tech pub data properly displays in PDF and IETM formats.

6. The tech pub data has the same functionality when viewed in the GFI beta IETM as similar data originally contained within the LAV tech pubs.

6. The Government will provide written comments to the Contractor that document errors/omissions in accordance with [6.d.(9.)(a.)]

6. The Contractor shall:

6. Support the Government with the necessary resources in accordance with agreements reached during the SOW meeting [Para 6.a.].

6. Adjust the data in accordance with the Government’s written comments in accordance with [6.d.(9.)(a.).]

6. Meetings/Travel: See the main contract.

6. Software:

6. The Contractor shall use the following software to render the draft tech pub data. If the Contractor does not already own the listed software, it shall purchase them.

6. XSL Formatter V 4.3 – Companion software to the Convertor/Styler, the XSL Formatter is used when generating the PDFs, in which case the CGMs are converted on the fly to SVGs for display in the PDF. http://www.antennahouse.com/product/axfo40/axfo4top.htm

6. SDI Covert Convertit“Command Line” (CLI) – Converts CGMs to SVG’s on-the-fly during the PDF creation process. http://www.sdicgm.com/sdi_convert.html

6. The Contractor shall use additional software packages to edit XML and CGM. Any high quality, full featured commercial XML editor and CGM editor software can be used to develop the IETM Content, but the Government recommends the following packages as it uses them to manage the LAV IETM’s tech pub data.

6. PTC Arbortext Editor – XML Editor for developing XML content for proper display within the LAV IETM Viewer. http://www.ptc.com/products/arbortext-editor

6. PTC Arbortext IsoDraw – Vector graphics editor for development of CGM (Computer Graphics Metafile) graphics required in the LAV IETM Viewer http://www.ptc.com/products/arbortext/isodraw/

6. Government Acceptance of Tech Pub Data: The tech pub data package that the Contractor develops to support its design modification shall be considered acceptable to the Government when it:

6. Is shown to be complete and accurate.

6. Is tagged in accordance with the LAV tech pub style/format to properly display within the IETM.

6. Encompass all configurations covered by the specific work directive.

7. DATA DELIVERABLES: Tech Pub Data Shall be delivered in accordance with the main contract.

8. SCHEDULE: The Contractor shall insert a schedule of significant events for tech pub data development as described in this TMCR into the Integrated Master Schedule (IMS) or agreed upon schedule format. The schedule shall include:

8. The generation, testing and rendering of tech pub data.

8. Interim deliveries of draft tech pub data for design mod testing and reviews.

8. Incremental deliveries of the Contractor’s finalized tech pub data.

8. Handoffs to the Government for additional data processing.

9. Furnished Material:

9. GFI: The Government will provide the following at the Start of Work Meeting:

9. Converter/Styler (The Government will provide the current version at the start-of-work meeting. Any updated versions of the software will be provided as they become available during the period of performance. Installation and setup of any updated versions shall not increase scope.)

9. Copy of “Unilateral NDA WebTM PM-LAV May 2009.docx”

9. LAV Project Action Items Tracking 11 Feb 2011

9. LAV IETM Viewer installation disk, Release X.X (The Government will provide the current version at the start-of-work meeting.)

9. A beta IETM [Para 6.c.(3)(c)]

9. Microsoft Excel © Data templates (SL-3, SL-4, LTI)

9. References: All MIL documents and other guidance cited in this TMCR, referenced in Para 3

9. IETM Change Levels: The Government will provide the appropriate change levels for the relevant tech pub data within ten days following the start-of-work meeting.

9. Microsoft Excel © format “TPD Revision Tracker Template” [5.c.(7.)]

9. CFE/CFI: The Contractor shall provide the following:

9. Tech pub data: All narratives, tables, graphics, schematics and related data that are based upon the final Government-approved design mod configuration and that are deemed necessary by the (FEAT or MPM) for its operational and maintenance support.

9. Val/ver: Facilities, equipment, material, SMEs, computer hardware, and time adequate for a tech pub data review that is in accordance with this TMCR and agreements reached during the SOW meeting.

9. Material identified in the “LAV Val-Ver Plan Feb 2011”

9. A tools list for each task that identifies special tools.

9. A list of Test Measurement and Diagnostic Equipment (TMDE) for each task identifying TMDE requirements.

Note 1: Items in blue font represent those areas where two or more choices are to be made by the government depending on the overall nature of their particular tech pub data project.

Note 2: Items in green font require a final update prior to finalization, due to outline number shifts during the adjustment process.