Attachment 0001 -- CM523U Statement of Work.docx
DOCX document 275 KB Posted
- Solicitation number
- W31P4Q-22-R-0034
About this file
This statement of work describes requirements for the acquisition of a battery-operated, handheld spectrum analyzer to be fielded as the Analyzer, Spectrum: CM-523/U. Key requirements include measuring input signals from 9 kHz to 26.5 GHz to support various Army systems. The contractor shall perform all material and equipment production, testing, delivery, and maintenance requirements defined in the statement of work. This involves program management, systems engineering, logistics, calibration support, and warranty obligations. The contractor must meet configuration management, quality assurance, and other technical standards in delivering the CM-523/U, associated data, and training packages.
View the file
Other files
Show all 20
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
STATEMENT OF WORK
FOR
Analyzer, Spectrum: CM-523/U
Version 3
September 2021
Prepared By:
Test Equipment Modernization
Product Director, Test, Measurement and Diagnostic Equipment
W31P4Q-22-R-0034
Attachment 0001: Statement of Work Solicitation #: W31P4Q-22-R-0034 Dated: 22 September 2021
Table of Contents
| 1.0 Scope. | 5 |
| 1.1 Background. | 5 |
| 1.2 Operational/Mission Requirement. | 5 |
| 2.0 Applicable Documents. | 5 |
| 3.0 Requirements. | 6 |
| 3.1 Status Report (Contract Data Status & Schedule Report). | 6 |
| 3.2 Conference Minutes. | 6 |
| 3.3 Start of Work Meeting. | 7 |
| 3.3.1 Supplied by the Government. | 7 |
| 3.3.2 Supplied by the Contractor. | 7 |
| 3.4 Safety and Hazardous Material Reporting. | 8 |
| 3.4.1 Safety Assessment Report. | 8 |
| 3.4.2 Hazardous Materials Management. | 8 |
| 3.5 Calibration and Measurements Requirements Summary and Maintenance, Test, and Support Equipment Requirements List. | 9 |
| 3.5.1 Requirements. | 9 |
| 3.5.2 Selection Criteria. | 9 |
| 3.5.3 Documentation. | 10 |
| 3.5.4 Alternative Maintenance Strategies. | 10 |
| 3.5.5 Interim Approval. | 11 |
| 3.5.6 Calibration Software | 11 |
| 3.6 Maintenance Allocation Chart. | 13 |
| 3.6.1 Document Preparation | 13 |
| 3.6.2 Support Concept | 13 |
| 3.6.3 Maintenance Allocation Chart Distribution/Format | 13 |
| 3.6.4 Tasks Supported | 13 |
| 3.6.5 Modifications | 14 |
| 3.6.6 Selection Criteria | 14 |
| 3.6.7 Interim Approval | 14 |
| 3.7 Technical Manuals. | 14 |
| 3.7.1 Operator’s Technical Manual. | 14 |
| 3.7.2 Maintenance Technical Manual. | 18 |
| 3.8 Operator and Field Maintenance Training CD-ROM and Institutional Training Package. | 23 |
| 3.8.1 Training Documentation. | 23 |
| 3.8.2 Training and Training Support. | 24 |
| 3.8.3 Course Development Qualifications. | 25 |
| 3.8.4 Security. | 26 |
| 3.8.5 In-Process Reviews. | 26 |
| 3.8.6 Computer Managed Instruction Requirements. | 28 |
| 3.8.7 Safety. | 28 |
| 3.8.8 Training Aids and Equipment. | 29 |
| 3.8.9 Source Files | 29 |
| 3.9 Product Verification. | 29 |
| 3.9.1 Product Verification Test (PVT) Plan. | 30 |
| 3.9.2 Product Verification Test Failures. | 32 |
| 3.9.3 Interim Product Verification Test Reports. | 32 |
| 3.9.4 Product Verification Test Restart. | 32 |
| 3.9.5 Product Verification Test Report (PVTR). | 32 |
| 3.9.6 Refurbish Product Verification Test Units. | 33 |
| 3.9.7 Specification Change Process. | 33 |
| 3.10 Reliability, Availability, and Maintainability. | 33 |
| 3.10.1 Responsibility for Inspection. | 33 |
| 3.10.2 Product Acceptance. | 33 |
| 3.10.3 Reliability, Availability, and Maintainability Requirements. | 33 |
| 3.11 Quality Assurance. | 34 |
| 3.12 Configuration Management. | 34 |
| 3.12.1 Configuration Management Policies and Procedures. | 34 |
| 3.12.2 Configuration Audits. | 34 |
| 3.12.3 Product Drawings/Models and Associated Lists. | 35 |
| 3.12.4 Engineering Change Activity Requirements. | 36 |
| 3.13 Provisioning. | 38 |
| 3.13.1 Technical Documentation. | 38 |
| 3.13.2 Supply Support. | 39 |
| 3.13.3 Provisioning Reviews | 39 |
| 3.13.4 Purchasing Provisioning Standards. | 40 |
| 3.14 Wide Area Workflow Receiving Report for Contract Data Requirements Lists. | 40 |
| 3.14.1 Technical Manuals. | 40 |
| 3.14.2 Operator and Field Maintenance Training CD-ROM and Institutional Training Package. | 40 |
| 3.15 Cybersecurity. | 40 |
| 3.15.1 Program Protection | 41 |
| 3.16 Equipment Marking and Identification Requirements. | 41 |
| 3.16.1 Marking. | 41 |
| 3.16.2 Item Unique Identification Markings Requirements. | 41 |
| 3.16.3 Transit Case Identification Plate. | 43 |
| 3.16.4 Equipment Identification Plates/Labels. | 43 |
| 3.16.5 Battery Information. | 44 |
| 3.17 Packaging. | 44 |
| 3.17.1 Packaging Data | 44 |
| 3.18 Transportation. | 45 |
| 3.19 Production Report. | 45 |
| 3.20 Shipping and Storage Options. | 46 |
| 3.20.1 Option #1 – Government Managed Shipping and Storage. | 46 |
| 3.20.2 Option #2 – Contractor Managed Shipping and Storage. | 46 |
| 3.21 Warranty. | 47 |
| 3.21.1 Warranty Provisions. | 47 |
| 3.21.2 Defects. | 49 |
| 3.21.3 Turn Around Time on Warranted Items. | 49 |
| 3.21.4 Submission of Warranty and Non-Warranty Report. | 49 |
| 3.21.5 Failure Reporting, Analysis, and Corrective Action System. | 49 |
| 3.21.6 Warranty Extension. | 50 |
| 3.22 Contractor Repair and Calibration Support. | 50 |
| 3.22.1 Support Requirement. | 50 |
| 3.22.2 Equipment Service Parameters. | 50 |
| 3.22.3 Non-Warranty Repair Actions. | 50 |
| 3.22.4 Repair Requirements. | 51 |
| 3.22.5 Equipment Receipt Process. | 51 |
| 3.22.6 Contractor Furnished Resources. | 52 |
| 3.22.7 Uneconomically Repairable Process. | 52 |
| 3.22.8 Parts Replacement Standard. | 52 |
| 3.22.9 Acceptance Standard. | 52 |
| 3.22.10 Government-Furnished Equipment Program Management. | 52 |
| 3.22.11 Equipment Shipment. | 52 |
| 3.22.12 Inspection Criteria. | 53 |
| 3.23 Weekly Teleconference. | 53 |
| 3.24 Program Management Reviews. | 53 |
| 4.0 Travel. | 53 |
| 4.1 Required Travel. | 53 |
| 5.0 Acronyms. | 53 |
1.0 Scope.
This Statement of Work (SOW) defines the effort required for the production, test, delivery, and maintenance for the Analyzer, Spectrum: CM-523/U, hereinafter referred to as the CM-523/U. It includes the associated program management, systems engineering, acquisition logistics, and warranty requirements.
1.1 Background.
Product Director, Test, Measurement, and Diagnostic Equipment (PD TMDE) is the Government entity responsible for program management for the acquisition of the CM-523/U. PD TMDE will acquire the CM-523/U as part of the Test Equipment Modernization program established in 1981 to replace obsolete General Purpose Electronic Test Equipment (GPETE). GPETE requirements are based on current projections from United States (US) Army Training and Doctrine Command (TRADOC). A continuing requirement exists to modernize the Army’s inventory of GPETE. Army operators and maintainers at all maintenance levels require GPETE to support current and emerging communications, electronics, biomedical, missile, air defense, aviation systems, and ground vehicle systems. Rapid technology development, obsolescence, and unsupportable test equipment require the capability to modernize and consolidate GPETE. This requirement is intended to encompass all GPETE not considered to be automatic test equipment. The new GPETE will replace current Test, Measurement, and Diagnostic Equipment (TMDE) systems in an effort to modernize and standardize GPETE by reducing the number of makes and models in the Army inventory.
GPETE enables the current and future force operators and maintainers to correctly measure, calibrate, diagnose, verify, and test systems and components prior to the system or component’s battlefield use or return to the Soldier. The Army must provide maintenance and repair capability for the fighting force in both peacetime and combat operations.
1.2 Operational/Mission Requirement.
The CM-523/U is a battery operated, handheld spectrum analyzer which will meet the general purpose functional test requirements to measure signal spectrum across a myriad of communication and weapon systems. It will be required to deliver the measurement capability to accurately measure input signals at ranges between 9 kilohertz (kHz) and 26.5 Gigahertz (GHz) in support of Army avionic, missile, ordnance, and signal equipment.
2.0 Applicable Documents.
The applicable top level documents are contained in the Contract Document Summary List (DSL) by number, title, date, contract reference, and category. The document versions specified on the DSL take precedence over the generic references (those without revision letters) cited in the SOW. Unless otherwise indicated, copies of Defense and Federal specifications, standards, and Military handbooks listed may be obtained from the Acquisition Streamlining and Standardization Information System website: https://quicksearch.dla.mil/qsSearch.aspx. Army Regulations may be obtained from the Army Publishing Directorate website: https://armypubs.army.mil. TRADOC Regulations and Pamphlets (PAM) may be obtained from the TRADOC website: https://adminpubs.tradoc.army.mil.
3.0 Requirements.
The contractor shall furnish all material and equipment necessary to meet the requirements of this SOW. The contractor shall produce and deliver the CM-523/U in accordance with (IAW) Purchase Description (PD): TEMOD-20-01 (hereinafter referred to as the “Specification”), or as modified after contract award, and all approved Facility of Use (FOU) Evaluation comments (if applicable).
3.1 Status Report (Contract Data Status & Schedule Report).
The contractor shall establish and maintain a reporting system to track all deliverable data and hardware. The contractor shall prepare a status report IAW DI-MGMT-80368 “Status Report” (Contract Data Requirements Lists (CDRL) A001). The draft Contract Data Status and Schedule Report (CDSSR) shall convey the contractor’s interpretation of all contract schedule dates that are established in this SOW and associated CDRLs. The Statement of Work Meeting (SoWM) date is defined as the last day of the meeting. If there are any differences in the contract schedule between the contractor and the Government, they will be discussed at the SoWM.
3.2 Conference Minutes.
The contractor shall provide detailed written conference minutes IAW DI-ADMN-81250 “Conference Minutes” (CDRL A002) for all SoWMs, In-Process Reviews (IPRs), program reviews, validations, verifications, and other conferences, unless otherwise specified by the Government.
The Government will notify the contractor when conference minutes are not required. The draft conference minutes shall be reviewed by the Government and the contractor at the conclusion of each day’s events. Before the meeting is adjourned, identified key Government and contractor personnel in attendance are to sign and date the draft conference minutes of the meeting. The signed draft conference minutes shall constitute as agreement by all parties and concurrence by the Government.
The signed conference minutes shall not be interpreted or construed as a direction to work or as a redirection for the contractor to incur additional costs that will increase the price of the contract. Changes to contract effort approved and performed by contractor personnel outside the scope of the contract, without specific authorization by the Government Procuring Contracting Officer (PCO), shall be the sole responsibility of the contractor.
3.3 Start of Work Meeting.
The contractor shall attend the SoWM. The SoWM will be held at Redstone Arsenal, Alabama no later than (NLT) thirty (30) days after contract award. The purpose of this meeting is to provide a high level overview of the work to be performed by the contractor and update the contractor of any changes to applicable standards. Government’s Subject Matter Experts will provide short presentations that correspond to each section of this SOW and CDRL deliveries, they will be available throughout the meeting to answer any questions that the contractor may have.
The contractor shall consider this meeting as the SoWM for all contractual deliverables.
It is highly recommended individuals whom will be working the CDRL deliverables be present at the SoWM for clarity purposes.
3.3.1 Supplied by the Government.
The Government will provide the following items to the contractor at the SoWM:
· A copy of Technical Bulletin 43-180, Calibration and Repair Requirements for the Maintenance of Army Materiel, Distribution A (to be used in conjunction with Army Calibration Publications).
· Multi-User Engineering Change Proposal (ECP) Automated Review System (MEARS) login and instructions.
· An example Maintenance Allocation Chart (MAC)
· A TK-17/G toolkit (for use during the SoWM only).
· Army Calibration Publications (AN/GSM-287 and AN/GSM-440 Hand Receipts and Reference Catalogs).
· A copy of Army Regulation 350-1, “Army Training and Leader Development” and TRADOC Regulation 350-70, “Army Learning Policy and Systems.”
· The SoWM presentations.
· Identification of the Government Test Equipment Modernization (TEMOD) personnel to include the Program Officer, CM-523/U Project Leader, CM-523/U Logistics Lead, and the Acquisition Program Specialist, at a minimum.
3.3.2 Supplied by the Contractor.
The contractor shall supply the following items to the Government at the SoWM:
· All tools that are required for maintenance and disassembly of the CM-523/U that are not found in the TK-17/G toolkit.
· Information not included in the contractor’s standard commercial warranty including the additional conditions of its commercial warranty, id est (i.e.), timeframes, execution procedures (limitations, lists of factory-authorized service centers, et cetera (etc)).
· Data specification sheets for the Configuration Item (CI), repair parts, and accessories
· The name(s) of the official(s) of its organization authorized to sign ECPs and Request for Variance (RFV) as the submitting activity, and thereby commit the contractor to the statements made therein. The name(s) of personnel authorized to create an ECP and RFV.
· The designated point of contact for all calibration and repair matters.
· Names and email addresses of all personnel that will require MEARS training.
· Provide a list that identifies all facilities, worldwide and within the Continental United States, that the Government can utilize as service centers for on-call repair and calibration.
· All items required to provide detailed written minutes, action items, and the person the action item is assigned for this SoWM. The minutes will have to be agreed upon and signed by the Government and contractor prior to the meeting being adjourned.
· The names of the contractor’s primary contract representatives.
· All proposed specification changes
3.4 Safety and Hazardous Material Reporting.
3.4.1 Safety Assessment Report.
The contractor shall prepare a Safety Assessment Report (SAR) in IAW DI-SAFT-80102 “Safety Assessment Report” (CDRL A003) and MIL-STD-882 “System Safety.” The SAR shall provide a comprehensive evaluation of the assumed safety risks. The contractor shall establish a hazard tracking system that monitors the status, through final resolution, of each identified program hazard using unique hazard/risk assessment codes. If there are design changes during the acquisition process, the contractor shall provide an updated SAR with updated hazard logs that capture the additional hazards. The contractor shall maintain a hazard log and provide an updated version to the Government with each SAR submission at no additional charge to the Government.
3.4.2 Hazardous Materials Management.
All contractor and subcontractor activities shall comply with applicable federal, state, and local environmental laws and regulations. The contractor shall ensure that design, maintenance, operation, manufacturing, programmatic decisions, and trade-off studies strive to eliminate or reduce hazardous materials and waste. The contractor shall prepare an annual Hazardous Materials Management Program (HMMP) Reports IAW DI-MISC-81397 “Hazardous Materials Management Program Report” (CDRL A004) using National Aerospace Standard (NAS) 411. The HMMP Reports shall identify via graphic or drawing of the specific location of each hazardous material contained in the final end item(s).
The Contractor shall report the data elements found in MIL-STD-882, Task 108, section 108.2.4 a, b, and d for Tracked HAZMATs. The contractor shall report coatings (identified by Military Specification), functional fluids (e.g. coolant, hydraulic fluid, lubricants, et cetera (etc.)), radionuclides (40 Code of Federal Regulations (CFR) 302.4, Appendix B), and energetics/solid rocket motor components (including Explosives Class Number) with the same 108.2.4 a, b, and d data elements. The Contractor shall provide Material Safety Data Sheets or Safety Data Sheets for all reported materials.
The Contractor shall report any hazardous material, as defined in NAS 411-1 “Hazardous Materials Target List,” to be used for the maintenance, sustainment, and demilitarization of the end item under this contract. The hazardous material shall be properly identified and include any applicable identification number, such as National Stock Number or Special Item Number. The Contractor hazardous materials list shall be updated during performance of the contract whenever the Contractor determines that any other material to be used in the maintenance, sustainment, and demilitarization of the end item under this contract is hazardous.
The contractor shall not use any Class I or Class II Ozone Depleting Chemical/Ozone Depleting Substance (ODS), identified by the lists at https://www.epa.gov/ozone-layer-protection/ozone-depleting-substances, in the manufacture or support of items required by this SOW unless approved IAW Army ODS policy and/or Title 10 United States Code section 2302. All ODS alternatives must be in compliance with the U.S. Environmental Protection Agency Significant New Alternatives Policy program and identified as approved – per the specific application – in the lists at https://www.epa.gov/snap/snap-regulations#notices. All ODS alternatives shall also receive a Toxicity Clearance for the specific application from the US Army Public Health Center.
3.5 Calibration and Measurements Requirements Summary and Maintenance, Test, and Support Equipment Requirements List.
3.5.1 Requirements.
The contractor shall prepare a Calibration and Measurements Requirements Summary (CMRS) IAW DI-QCIC-80278 “Calibration and Measurements Requirements Summary” (CDRL A005) and a Maintenance, Test, and Support Equipment Requirements List (MTSERL) IAW DI-SESS-80294 “Maintenance Test and Support Equipment List” (CDRL A006) that identifies the equipment required to verify all performance specifications and the performance of each of the following maintenance functions: inspect, test, service, adjust, align, remove/install, replace, rebuild, overhaul, calibrate, and repair. Tools and test equipment shall be listed in alphabetical order by nomenclature.
3.5.2 Selection Criteria.
The contractor shall screen current Army inventory using the sources identified below for equipment/tools that meet the specifications required to perform all maintenance tasks. Items that meet the criteria shall be included in the MTSERL. The contractor shall research their MTSERL items from the following attached sources:
· Tool Kit, TK-17/G, Supply Catalog Number: 5180-91-R63, National Stock Number (NSN): 5180-01-195-0855
· Transfer Set Standards, AN/GSM-440 Hand Receipt
· Transfer Set Standards, AN/GSM-440 Reference Catalog
· Transfer Set Standards, AN/GSM-287 Hand Receipt
· Transfer Set Standards, AN/GSM-287 Reference Catalog The equipment/tools utilized shall be available in both the Transfer Set Standards, AN/GSM-440 and Transfer Set Standard, AN/GSM-287.
The Government will provide the necessary materials (including the latest version of the supply catalogs listed above), at the SoWM, for use in screening and selection of equipment/tools that meet the specifications required to perform all calibration and maintenance tasks.
3.5.2.1 Sources Available.
Upon determining that the required support equipment or tools are within the sources listed in paragraph 3.5.2 “Selection Criteria,” the contractor shall list those items in the MTSERL.
3.5.2.2 Sources Not Available.
Upon identifying that test equipment or tools are not within the sources listed in paragraph 3.5.2 “Selection Criteria,” the contractor shall provide written notification IAW IAW DI-SESS-80294 “Maintenance Test and Support Equipment List” (CDRL A006) of these items. This notification shall list the equipment required and explain why the Government needs it. The contractor shall provide a negative response, if applicable.
3.5.3 Documentation.
The MTSERL shall be organized in tabular format conveying the information specified in paragraph 3.5.1 “Requirements” IAW DI-SESS-80294 “Maintenance Test and Support Equipment List” (CDRL A006) and MIL-STD-40051- 2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)”, paragraph G.5.3.4 “(A) Tools and test equipment requirements <tereqtab>”. The MTSERL shall identify all maintenance, test, and support equipment required to provide full organic support maintenance, (to the level depicted in the MAC) on the CM-523/U IAW the developed maintenance concept. The contractor shall maintain a digital file backup of the MTSERL for the duration of the contract.
3.5.4 Alternative Maintenance Strategies.
In the event the data requested is not available (i.e., repairing a particular assembly to the component level) due to current commercial practices or manufacturing philosophy, the contractor shall propose an alternative maintenance strategy regarding the assemblies and subassemblies in question in line with its commercial practices.
3.5.5 Interim Approval.
Any Government approval of the contractor’s draft and final CMRS and MTSERL prior to completion of all technical manual verifications will be given with the stipulation that any further, subsequent changes required to the CMRS and MTSERL or any publication as a result of product verification test results, all Technical Manual Verifications, and the Logistics Demonstration shall be provided to the Government at no additional cost.
3.5.6 Calibration Software.
The contractor shall design, develop, and document a software source code calibration application and tests to automate the CM-523/U test equipment calibration process IAW DI-IPSC-81441 “Software Product Specification (SPS)” (CDRL A007). The calibration software application shall provide test equipment setup and interactive instructions for the operator and automatically derive the required calibration coefficients and store the coefficients in the test equipment memory.
The contractor shall design and develop the software source code to interface with existing standard test equipment and the Integrated Calibration Environment/Army CALSETS Environment (ICE/ACE).
The calibration software application shall execute on a 64 Bit windows 10 Enterprise computer/controller with Long-Term Servicing Channel (LTSC). The calibration software application shall have either Institute of Electrical and Electronics Engineers – General Purpose Interface Bus (IEEE-GPIB) interface or serial interface. The calibration software shall have necessary drivers for all applicable hardware. The calibration software shall have programmers interface to allow interface with the Army (ICE/ACE) application. The calibration software shall comply with cyber security requirements. The contractor shall deliver any software required to complete the alignment of the instrument on a standard format Compact Disk Read-Only Medium (CD-ROMs) or Digital Video Disc (DVD). The Government may request clarification of the information provided by the contractor at any time during the development of the Government calibration procedures.
The contractor shall develop a streamlined Graphical User Interface (GUI) for the automated calibration procedure and all adjustments. The contractor shall also have the GUI display how far out of tolerance, if any, any measurement are.
The contractor shall include calibration procedure methodology, procedures, and recommended verification tests in the DI-IPSC-81441 “Software Product Specification (SPS)” (CDRL A007) documentation.
3.5.6.1 Test Engineering.
The contactor shall develop Software Test Plan IAW DI-IPSC-81438 “Software Test Plan (STP)” (CDRL A043) to document the software test procedures and processes. The software test plans shall document traceability of the developmental testing with the functional requirements.
Testing shall not commence prior to Government review and approval of the contractor’s STP. The contractor shall notify the PCO in writing no later than thirty (30) calendar days prior to the testing start date with the testing schedule and the location of all testing site(s). The Government shall be afforded the opportunity to witness testing (either in person or virtually/remotely), or portions thereof, at the Government’s discretion.
Testing shall be conducted using CM-523/U materiel that is production-representative, i.e. representative of items to be manufactured for CM-523/U production materiel acceptance by Government, using the same design, revision, configuration, parts, components, materials, processes and procedures and manufactured at the same facilities and sub-suppliers and/or contract manufacturers as CM-523/U full-rate production. Any deviation of CM-523/U testing materiel from production-representative item as defined herein is not acceptable for testing without express PCO approval, and contractor shall notify Government prior to testing of any planned or manifest deviation of any CM-523/U testing item vs. production-representative materiel. (Ref. Section 3.10.2) The contractor shall conduct software tests for each software deliverable as described in the software test plans.
The Government, at its option, may request a repeat of the testing, or any part thereof, to verify corrective action at no additional cost to the Government. The contractor shall complete testing NLT 60 days after the approval of the STP.
Upon completion of testing, the contractor shall prepare a Software Test Report PVTR IAW DI-IPSC-81440 “Software Test Report (STR)” (CDRL A044) to document the disposition and field readiness of the software item under test.
3.5.6.2 Configuration Management.
The contractor shall implement configuration and data management process to control software and documentation change activity. The contractor shall participate in software configuration control boards and meetings.
3.5.6.3 Software Version Description.
The contractor shall provide a Software Version Description IAW DI-IPSC-81442 “Software Version Description (SVD)” (CDRL A045) to document the final approved software executable, installation, and source code application.
3.6 Maintenance Allocation Chart.
The contractor shall develop a Government approved maintenance concept based on contractor and Government recommendations, disassembly of the equipment, and available technical data. The contractor shall develop a top down breakdown or family tree for use in determining equipment maintenance concepts.
3.6.1 Document Preparation.
The contractor shall prepare a Logistics Support Analysis (LSA)-004 “Maintenance Allocation Chart” IAW DI-SESS-81759 “Logistics Product Data Summaries” (CDRL A009). The Maintenance Allocation Chart shall be presented at the SoWM to assist in the development of this deliverable. A physical teardown of the equipment shall be conducted during the SoWM to further assist in the Maintenance Allocation Chart development in conjunction with government personnel.
3.6.2 Support Concept.
The MAC shall display a maintenance concept that is consistent with the Army’s TMDE two-level maintenance concept (Field Maintenance and Sustainment Maintenance) IAW MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals” (CDRL A0012). Army TMDE maintenance philosophy is clarified as follows:
3.6.2.1 Field Maintenance.
Field Maintenance is on-system maintenance and is mainly replacement of defective parts and preventative maintenance. Field maintenance returns repaired equipment to the soldier. Some “off-system” maintenance can be done at field level if, based on task analysis, it is simple to complete or it is critical to mission readiness. The Field Maintenance level consists of Crew Maintenance and Maintainer Maintenance.
3.6.2.2 Sustainment Maintenance.
Sustainment maintenance is off-system maintenance and is mainly repair of defective equipment/parts. Sustainment maintenance returns repaired equipment/parts to the supply system. The Sustainment Maintenance level consists of Below Depot Maintenance and Depot Maintenance.
3.6.3 Maintenance Allocation Chart Distribution/Format.
The contractor shall include the final approved MAC as an appendix in the Maintenance Manual and other manuals/documents as required in the contract.
3.6.4 Tasks Supported.
The MAC shall form the baseline for all logistics and maintenance tasks such as the development of technical publications, parts provisioning, and support equipment requirements. The contractor shall maintain a digital file backup of the MAC for the duration of the contract.
3.6.5 Modifications.
The MAC is subject to change as a result of Product Verification Test (PVT) results, Technical Manual (TM) Verifications, Logistics Demonstration (LOGDEMO), or any unforeseen maintenance and logistics support system mandates. Once approved, the MAC requires Government approval to change. Any changes made to the MAC after Government approval shall be at no additional cost to the Government.
3.6.6 Selection Criteria.
When developing the MAC, the contractor shall maximize the use of existing Army Calibration Sets, Kits, and Outfits listed in paragraph 3.5.2 “Selection Criteria”. The Government will provide the necessary materials (supply catalogs, hand receipts, technical bulletins and reference catalog), at the SoWM, for use in screening and selection of equipment/tools that meet the specifications required to perform all calibration and maintenance tasks.
3.6.7 Interim Approval.
Any Government approval of the contractor’s draft and final MAC prior to completion of all technical manual verifications will be given with the stipulation that any further, subsequent changes required to the MAC or any publication as a result of product verification test results, all Technical Manual Verifications, and the Logistics Demonstration shall be provided to the Government at no additional cost.
3.7 Technical Manuals.
3.7.1 Operator’s Technical Manual.
3.7.1.1 Technical Documentation.
The contractor shall create and deliver Extensible Markup Language (XML)-tagged text and data files and illustrations required for an Operator’s Manual IAW the requirements of MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011) and MIL-HDBK-2361 “Army Digital Publications Development Implementation Guide”. The contractor may use MIL-HDBK-1222 “Guide to the General Style and Format of U.S. Army Work Package Technical Manuals” for reference. A baseline set of Document Type Definitions (DTD) tags and style sheets used in authoring text information and ensuring consistency for the XML-tagged files is available on the following website: https://www.logsa.army.mil/#/.
The Government will convert the XML-tagged text and data files and illustrations the contractor delivers into Portable Document Format (PDF) files. The Government will review the XML-tagged text and data files and illustrations for format, and the PDF files that the Government creates for content. The Government will provide both sets of comments to the contractor for incorporation into the contractor’s master operator’s manual file.
The Government will provide a complete TM number for this manual NLT the 30% IPR.
The 30% TM shall include the TM outline per the Content Selection Matrix with all Work Packages identified and at least one complete Work Package. The 70% TM shall include 80% of the Work Packages, diagrams, schematics, etc. complete. The 100% TM shall include all Work Packages, diagrams, schematics, etc. complete.
3.7.1.2 Effectivity.
The contractor shall ensure that documentation reflects all active configurations of the hardware, the maintenance concept, and maintenance philosophy as established for the target audience and the Government-approved MAC.
3.7.1.3 Operator’s Manual Publication.
The contractor shall develop or extract any needed technical data from existing Commercial-Off-the-Shelf (COTS) publications, engineering notes, previously developed Government TMs, and from any other additional data source necessary to develop the manual. Any information that does not exist in these data sources shall be developed to support the maintenance concept. Developed or extracted technical data shall be repackaged and republished in the form of XML-tagged text files, and illustrations, consistent with the requirements of the MAC and the content/format requirements of MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011).
3.7.1.4 Operator’s Manual Source Material.
The contractor shall package and deliver all source material, defined as operating plans, standard procedures, computer programs, and residual material to include computer disks, computer tapes, and all other media containing digital files developed to fulfill the requirements of this SOW.
3.7.1.5 Illustrations and Diagrams.
Illustrations and diagrams used with the XML-tagged text and data files shall reflect the equipment delivered to the Government. The contractor shall develop illustrations IAW the requirements of this SOW and MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011) regarding size, display density, and legibility. Illustrations shall be in Computer Graphics Metafile (CGM) 4, CGM4, standard. All CGM files shall be fully functional. Illustrations and diagrams shall not require display dimensions greater than 5 inches wide by 6.5 inches tall. The main structure shall have 0.01 inch line weight, and small details shall have a line weight of either 0.005 or 0.003. All callouts shall be in either Ariel or Helvetica font with an eight (8) point size and shall be sequentially numbered in a clockwise rotation with one (1) starting at the 11:00 o’clock position. Illustration identifications number (tracking numbers) shall be used as described in MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011). Identification numbers (tracking numbers) shall be either Ariel or Helvetica font with a bold six (6) point size. All illustrations and diagrams shall be in black and white. The dimensions of the Operator’s Manual is 8.5 inches by 11 inches.
3.7.1.6 Meetings and Reviews.
The contractor shall support IPRs to be held throughout the development of the Operator’s Manual at no additional cost to the Government.
3.7.1.6.1 In-Process Reviews.
The Government will conduct an IPR for each delivery of the tagged files described in MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011). The Government will perform these reviews in various ways, i.e., desktop, conference calls, or meetings. The Government will review each submission for content and format compliance to the standards. The Government will review and comment on the tagging of the data files and return the comments to the contractor for incorporation. The contractor shall use the corrected files to develop the final version of the tagged files. The contractor shall then incorporate all content comments into the tagged files. The contractor shall retain copies of all comments.
3.7.1.6.2 Post-Review Teleconference.
If the contractor needs any clarification on comments provided by the Government on the 30% TM or 70% TM reviews, the contractor shall request a teleconference after receiving the comments from the Government. Once a teleconference date and time has been established, the contractor shall provide the conference telephone number and dial-in code, if applicable, to the Government before the teleconference is to take place.
3.7.1.7 Preliminary Technical Manual Data Files Validation and Review.
The contractor shall validate the Preliminary Technical Manual (PTM) as follows:
3.7.1.7.1 Contractor Validation Responsibilities.
The contractor shall validate the technical accuracy and adequacy of all operating and maintenance procedures, 100% Operator’s Manual content, XML-tagged files, and related illustrations at a contractors designated facility using hands-on approach.
3.7.1.7.2 Government Witness of Validation.
The Government reserves the right to witness all or a portion of the validation. However, Government observation of the validation will not necessarily constitute a verification of the material. If the Government does attend the validation and provides comments, the contractor shall incorporate all provided Government comments into the Manual before the PTM is submitted.
3.7.1.7.3 Records Keeping.
The contractor shall maintain records showing dates of validation reviews, material reviewed by task or action, findings with applicable remarks, and action taken IAW International Organization for Standardization (ISO) 9001:2015 or equivalent. The Government reserves the right to examine these records at the contractor’s facility.
3.7.1.7.4 Preliminary Technical Manual Data Files Review.
Once the contractor has validated the 100% Operator's Manual, the Manual is considered a PTM. The PTM consists of the validated 100% content, XML-tagged files, and related illustrations. The Government will review the contractor completed, validated PTM data files to ensure technical accuracy, previous review comments incorporated, acceptable format, and conformity to the Army maintenance philosophy.
3.7.1.8 Verification and Logistics Demonstration.
The Government will verify the tagged data files at a Government designated facility. Verification will be performed on a PTM generated by the Government from the validated XML-tagged files. Government comments on the validated PTM will be provided to the contractor at or before Verification. The Government will verify operating instructions and operator’s maintenance procedures using military personnel with the appropriate Military Occupational Specialty (MOS) performing tasks as detailed in the Operator’s PTM. Preventive Maintenance Checks and Services (PMCS) will also be 100% verified as described above. Verification will be IAW all requirements cited in this SOW. All portions of the Operator’s Manual not subject to hands-on Verification will be desktop-review verified. The Government reserves the right to use additional Verification methods as appropriate.
3.7.1.8.1 Text And Graphics.
The contractor shall correct all errors found in the PTM text and graphics during Verification, at no additional cost to the Government. After Government review of the PTM, the contractor shall correct all errors found in the PTM (that are considered to be within the scope of the contract) at no additional cost to the Government.
3.7.1.8.2 Resourcing.
The contractor shall provide at a minimum a technical writer, an engineer, and any tools needed to perform maintenance or operation of the CM-523/U for the Verification of the manual and the LOGDEMO at no additional cost to the Government. The Government will determine the times for the verification and LOGDEMO, which will be held at Redstone Arsenal, Alabama.
3.7.1.8.3 Contractor Assistance.
The contractor shall provide assistance to the Government at the Verification and LOGDEMO. The contractor shall provide the Government with a copy of all proposed faults that have been validated and are listed in the PTM IAW MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011). The contractor may use MIL-HDBK-470 “Designing and Developing Maintainable Products and Systems, Volume I” as a reference to determine fault insertion sample size and methodology. The contractor shall provide the necessary means to allow for the insertion of all the listed faults for Verification and LOGDEMO purposes. The contractor shall have the necessary resources on-site to provide on-the-spot corrections to the XML-tagged text, data files, and illustrations required for an Operator’s Manual within twelve hours.
3.7.1.8.4 Records Process.
The contractor shall record and maintain a list of deficiencies that occurred and their corresponding corrective actions during the Verification and the LOGDEMO processes. The contractor shall provide a detailed report of all actions taken following successful completion of the Verification and LOGDEMO IAW MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A011).
3.7.1.8.5 Administrative Support.
The contractor shall provide administrative support for completion of the Verification of the manual and the LOGDEMO.
3.7.1.9 Final Acceptance Review.
The Government will perform a final approval review of the Final Reproducible Copy (FRC) XML-tagged data files and illustrations after Verification and LOGDEMO to ensure all requirements of this SOW are met. The FRC shall be the final XML-tagged text, data files, and illustrations, with all necessary changes and corrections incorporated including final resolution of all comments and recommendations made as a result of validation, Verification, LOGDEMO, testing and user review. If errors are found in the FRC, the XML-tagged files and illustrations will be considered a PTM until the errors are corrected.
3.7.1.10 Over-pack Requirements.
The Government will provide the Operator's Manuals for over-pack. The contractor shall over-pack one (1) each Operator’s Manual (paper copy) inside the transit case with each piece of equipment delivered as specified in this contract.
3.7.2 Maintenance Technical Manual.
3.7.2.1 Technical Documentation.
The contractor shall create and deliver XML-tagged text and data files and illustrations required for a Maintenance Manual IAW the requirements of MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A012) and MIL-HDBK-2361 “Army Digital Publications Development Implementation Guide”. The contractor may use MIL-HDBK-1222 “Guide to the General Style and Format of U.S. Army Work Package Technical Manuals” as reference and information. The Maintenance Manual data files shall incorporate a Field and Sustainment level Repair Parts & Special Tools List (RPSTL) developed IAW MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs).” A baseline set of DTD tags and style sheets used in authoring text information and ensuring consistency for the XML-tagged files is available on the following website: https://www.logsa.army.mil/#/.
The Government will convert the XML-tagged text and data files and illustrations the contractor delivers into PDF files. The Government will review the XML-tagged text and data files and illustrations for format, and the PDF files that the Government creates for content. The Government will provide both sets of comments to the contractor for incorporation into the contractor’s master maintenance’s manual file.
The Government will provide a complete TM number for this manual NLT the 30% IPR.
The 30% TM shall include the TM outline per the Content Selection Matrix with all Work Packages identified and at least one complete Work Package. The 70% TM shall include 80% of the Work Packages, diagrams, schematics, etc. complete. The 100% TM shall include all Work Packages, diagrams, schematics, etc. complete.
3.7.2.2 Effectivity.
The contractor shall ensure documentation reflects all active configurations of the hardware, the maintenance concept, and maintenance philosophy as established for the target audience and the Government-approved MAC.
3.7.2.3 Maintenance Manual Publication.
The contractor shall develop any needed technical data from existing COTS publications, engineering notes, previously developed Government TMs, and from any other additional data source necessary to develop the manual. Any information that does not exist in these data sources shall be developed to support the maintenance concept. Developed or extracted technical data shall be repackaged and republished in the form of XML-tagged text files, and illustrations, consistent with the requirements of the MAC and the content/format requirements of MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A012). Product warranty information shall be included in the final tagged files with return procedures for equipment failures occurring during the period of the manufacturer’s warranty entered in the maintenance and servicing section of the TM.
3.7.2.4 Maintenance Manual Source Material.
The contractor shall package and deliver all source material, defined as operating plans, standard procedures, computer programs, and residual material to include computer disks, computer tapes, and all other media containing digital files developed to fulfill the requirements of this SOW.
3.7.2.5 Illustrations and Diagrams.
Illustrations and diagrams used with the XML-tagged text and data files shall reflect the equipment delivered to the Government. The contractor shall develop illustrations IAW the requirements of this SOW and MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A012) regarding size, display density, and legibility. Illustrations shall be in CGM4 standard. All CGM files shall be fully functional with multiple layers. Illustrations and diagrams shall not require display dimensions greater than 7 inches wide by 8.5 inches tall. The main structure shall have 0.01 inch line weight, and small details shall have a line weight of either 0.005 or 0.003. All callouts shall be in either Ariel or Helvetica font with an eight (8) point size and shall be sequentially numbered in a clockwise rotation with one (1) starting at the 11:00 o’clock position. Illustration identifications number (tracking numbers) shall be used as described in MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A012). Identification numbers (tracking numbers) shall be either Ariel or Helvetica font with a bold six (6) point size. All illustrations and diagrams shall be in black and white. The dimensions of the Maintenance Manual is 8.5 inches by 11 inches.
3.7.2.6 Meetings and Reviews.
The contractor shall support IPRs to be held throughout the development of the Maintenance Manual at no additional cost to the Government.
3.7.2.6.1 In-Process Reviews.
The Government will conduct an IPR for each delivery of the tagged files cited in the CDRL. The Government will perform these reviews in various ways (i.e.: desktop, conference calls, or meetings). The Government will review each submission for content and format compliance to the standards. The Government will review and comment on the tagging of the data files and return the comments to the contractor for incorporation. The contractor shall use the corrected files to develop the final version of the tagged files. The contractor shall then incorporate all content comments into the tagged files. The contractor shall retain copies of all comments.
3.7.2.6.2 Post-Review Teleconference.
If the contractor needs any clarification on comments provided by the Government on the 30% TM or 70% TM reviews, the contractor shall request a teleconference after receiving the comments from the Government. Once a teleconference date and time has been established, the contractor shall provide the conference telephone number and dial-in code, if applicable, to the Government before the teleconference is to take place.
3.7.2.7 Preliminary Technical Manual Validation and Review.
The contractor shall provide 100% PTM IAW MIL-STD-40051-2 “Preparation of Digital Technical Information for Page-Based Technical Manuals (TMs)” (CDRL A012). The contractor shall validate the PTM as follows:
3.7.2.7.1 Contractor Validation Responsibilities.
The contractor shall validate the technical accuracy and adequacy of all operating and maintenance procedures, 100% Maintenance Manual content, XML-tagged files, and related illustrations at a contractors designated facility using hands-on approach
3.7.2.7.2 Government Witness of Validation.
The Government reserves the right to witness all or a portion of the validation. However, Government observation of the validation will not necessarily constitute a verification of the material. If the Government does attend the validation and provides comments, the contractor shall incorporate all provided Government comments into the Manual before the PTM is submitted.
3.7.2.7.3 Records Keeping.
The contractor shall maintain records showing dates of validation reviews, material reviewed by task or action, findings with applicable remarks, and action taken IAW ISO 9001:2015 or equivalent. The Government Technical Manager or designated representative reserves the right to examine these records at the contractor’s facility.
3.7.2.7.4 Preliminary Technical Manual Data Files Review.
Once the contractor has validated the 100% Maintenance Manual, the Manual is considered a PTM. The PTM consists of the validated 100% content, XML-tagged files, and related illustrations. The Government will review the contractor completed, validated data files to ensure technical accuracy, previous review comments incorporated, acceptable format, and conformity to the Army maintenance philosophy.
3.7.2.8 Verification and Logistics Demonstration.
The Government will verify the tagged data files at a Government designated facility. Verification will be performed on the validated PTM generated by the Government from the validated XML-tagged files. Government comments on the validated PTM will be provided to the contractor at or before verification. The Government will verify maintenance instructions and procedures using military personnel with the appropriate MOS performing tasks as detailed in the Maintenance PTM. PMCS will also be 100% verified as described above. Verification will be IAW all requirements cited in this SOW. All portions of the Maintenance Manual not subject to hands-on verification will be desktop-review verified. The Government reserves the right to use additional Verification methods as appropriate.
3.7.2.8.1 Text And Graphics.
The contractor shall correct all errors found in the PTM text and graphics during verification, at no additional cost to the Government. After Government review of the PTM, the contractor shall correct all errors found in the PTM (that are considered to be within the scope of the contract) at no additional cost to the Government.
3.7.2.8.2 Resourcing.
The contractor shall provide at a minimum a technical writer, an engineer, and any tools needed to perform maintenance or operation of the CM-523/U for the Verification and the LOGDEMO at no additional cost to the Government. The Government will determine the times and the locations for the Verification and LOGDEMO.
3.7.2.8.3 Contractor Assistance.
The contractor shall provide assistance to the Government during the…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .