SHARP SENSOR Statement of Work


Note to Potential Offerors: Offerors are encouraged to provide recommendations and submit questions in response to this draft SOW. Recommendations for tailoring, consolidation, or substitution of contract data items to promote significant cost and schedule savings without deviating from the original purpose or degrading end item use will be considered. Please submit all questions and comments on this draft to [email protected] by 16 September 1999.





1.0 SCOPE *

1.1 Purpose *

1.2 IPPD Team Structure *


2.1 Military Specifications *

2.2 Military Standards *

2.3 Other Military Documents *

2.4 Other Documents *


3.1 Equipment Design *

3.1.1 Hardware *

3.2 Software *

3.2.1 Non-Developmental Software (NDS) *

3.2.2 Software Metrics *

3.3 Test And Evaluation *

3.3.1 Test And Evaluation Support *

3.3.2 R&M And BIT Monitoring During Flight Test *


4.1 Configuration Identification (CI) *

4.1.1 Functional/Physical Configuration Audits (F/PCA) *


5.1 Meetings And Reviews *

5.1.1 Program Management Reviews *

5.2 Technical Interchange Meetings *


6.1 Environmental And Hazardous Material *

6.2 Reliability, Maintainability And Built In Test *

6.2.1 Failure Reporting, Analysis And Corrective Action System (FRACAS) *

6.2.2 System Reliability Predictions *

6.2.3 System Maintainability Predictions *

6.2.4 Maintainability And BIT Demonstration *

6.2.5 Reliability Critical Items *

6.2.6 Part Level Stress Analysis *

6.3 Failure Modes, And Effects And Criticality Analysis (FMECA) *

6.4 Electromagnetic Environmental Effects *



8.1 ILS Program Management *

8.2 Offerer LMI/Engineering Interface *

8.3 ILS Program Control *

8.3.1 LMI Guidance Conference *

8.3.2 ILS Elements Baseline Schedule *

8.3.3 LMI Program Reviews *

8.3.4 LMI Data Product Review *

8.4 LMI Program Requirements *

8.5 Logistics Element Supportability Analysis *

8.6 LMI Data Products *

8.6.1 Data Organization *

8.6.2 Data Not Resident In The LMI Data Product *

8.6.3 Data Validation *

8.7 LMI Task Requirements *

8.7.1 Maintenance Plan *

8.7.2 Analysis Tasks And Studies *

8.7.3 Environmental Impact *

8.8 Support Equipment *

8.9 Source Data For Technical Manuals *

8.10 Drawings *

8.11 Interim Contractor Support *

8.12 Training *

8.13 Packaging, Storage, Handling & Transportation (PHS&T) *

8.14 Facilities *

8.15 Manpower And Personnel *

8.16 Supply Support *



  1. SCOPE

This Statement of Work (SOW) defines the effort required for the design, development, fabrication and integration of an imaging sensor(s) into a SHAred Reconnaissance Pod (SHARP) system to be carried aboard the F/A-18E/F aircraft. The imaging sensor shall provide the capability to collect infrared and visible digital reconnaissance imagery at medium and high altitudes. The sensors must include both overflight and standoff capability as well as day/night operations in all weather conditions. The sensors shall be supportable within the capability of the deployed carrier air wing or forward deployed (land based) support posture. The sensor shall employ digital technology and be compatible with the Common Imagery Ground/Surface System (CIG/SS) compliant ground stations (e.g. Tactical Input Segment (TIS)/Tactical Exploitation Group (TEG)). The full range of reconnaissance capability may be provided through separate and interchangeable medium and high altitude sensors that can be easily reconfigured into optimum mission suites. However, a single sensor that could meet both medium and high altitude requirements is desirable. To ensure true multi-mission capability of the F/A-18E/F aircraft the SHARP pod must be capable of being installed or removed with full mission turnaround capability of less than one hour. This Engineering and Manufacturing Development (E&MD) phase includes a baseline requirement for the sensor(s) design effort, and fabrication, integration, installation and test of Engineering Development Models (EDM's).

Specific tasks to be performed include:

  1. Design, develop, and integrate the imaging sensor(s) into the SHARP system. This includes the development of sensor to pod interfaces and associated software.
  2. Conduct selected design analyses, logistic support analyses, and qualification and performance test for laboratory and flight tests environments.
  3. Coordinate and define sensor interface requirements with the supplier of the SHARP system and functional elements within the SHARP system (SHARP Reconnaissance Management System (SRMS), Image Recorder, etc.).
  4. Furnish engineering support for integration and test of the sensor(s) within the SHARP system.
  5. Document developmental results, final sensor design, and sensor support plans/needs.

Related Information:

The Contractor shall establish an Associate Contractors Agreement (ACA) with the designer/fabricator of the SHARP Pod to ensure proper design interface control is established between the sensor(s) and pod. The contractor will also use the SRMS Interface Control Document (ICD) to establish required interfaces with the sensor. This contract is envisioned to be a rapid engineering design to manufacturing effort using non-developmental items (NDI) in the system design and fabrication.


    1. Purpose
    2. Incorporation of an NDI imaging sensor(s) integrated into the designated SHARP system will provide the U.S. Navy with immediate intelligence support to the Battle Group Commander (BGC) in the prosecution of independent, joint, or combined operations as well as to provide intelligence data for the security of those forces under his/her command. This capability is required to replace the F-14 Tactical Air Reconnaissance Pod (TARPS) capability, scheduled for phase-out beginning in Fiscal Year 2003 (FY-03). To meet this requirement, the Department of the Navy will incorporate SHARP on the centerline of the F/A-18E/F, which will employ reconnaissance sensor(s) to collect infrared and visible digital reconnaissance imagery at medium and high altitudes.


    3. IPPD Team Structure

The requirements specified herein shall be fulfilled using an Integrated Product and Process Development (IPPD) team approach employing Integrated Product Teams (IPTs). An IPPD team approach shall be used for the performance of this contract. The IPPD team shall be comprised of persons possessing the appropriate disciplines, specialties and functions from both the Government and Contractor and shall include major subcontractors/vendors. Team members shall be delegated the responsibility, authority, and accountability for decision-making and management actions necessary for successful performance of the contract. They shall be provided visibility into the design, engineering development, installation, systems integration, fabrication, testing, logistics and life cycle support planning effort. The Team shall identify problems and potential problems that could adversely impact system performance, cost and/or delivery schedule accompanied by proposed solutions. The IPPD Team shall interact in accordance with (IAW) the contract requirements, the Management Plan (MP), and the Cost/Schedule Control System (C/SCS). (CDRL XX01) Program Management Plan


  2. All documents invoked form a part of this SOW to the extent specified herein. Where written approval to streamline has not been received from the Government, the full intent of all documents referenced in the SOW shall apply. Military specification and standards listed in referenced documents are considered second tiered documents and are to be considered as guidance only for implementing the tasks.

    LIST OF APPLICABLE DOCUMENTS – TBD (coordinate with Perf. Spec., SRD, and CIDS)


    1. Military Specifications
    2. See Performance Specification For SHARP Imaging Sensors, SRD, and CIDS


    3. Military Standards
    4. See Performance Specification For SHARP Imaging Sensors, SRD, and CIDS


    5. Other Military Documents
    6. NAWC/AD Patuxent River

      TEMP 99-0000 SHARP Imagery Sensor(s) Test and Evaluation Master Plan dated XX Month 1999


      MIL-PERF-49506 dtd 11NOV96 Logistics Management Information


      MIL-HDBK-217F Notice 2 Reliability Prediction of Electronic Equipment

      MIL-HDBK - 472 Notice 1 Maintainability Prediction


    7. Other Documents

    ANSI/ASQC-Q90-1987 Quality Management And Quality Assurance Standards – Guidelines for Selection and Use

    NITF Version 2.0 Level 6 National Imagery Transmission Format

    ANSI/ASQC-Q9001-1994 Quality Systems – Model for Quality Assurance in Design/Development, Production, Installation and Servicing

    ANSI/AIAA Guidelines for Developing Software Development Files Conforming to DoD-STD-2167A

    ASME/Y14.24M-1989 Types and Applications of Engineering Drawing

    ASME/Y14.34M-1989 Parts List, Data Lists and Index Lists

    ASME/Y14.35M-1989 Revision of Engineering Drawings and Associated Documents

    MDC 92B0299 F/A-18E/F Operational Mission Environment

    MDC96A0019 P.S. 884 Vol IV F/A-18E/F LSAR Procedures Guide

    AVIONINST 5235.1 Software Metrics


  4. The Contractor shall provide an imaging sensor(s) as detailed in the Performance Specification. The Contractor is strongly encouraged to use automated tools for hardware and software design analysis, requirements traceability, trade-off studies, etc. as required as part of this SOW. The contractor is strongly encouraged to use NDI to the maximum extent practical to mitigate cost and schedule risk.


    1. Equipment Design

      1. Hardware

The Contractor shall provide an imaging sensor(s) with the capability to collect infrared and visible digital reconnaissance imagery at medium and high altitudes. The sensor(s) and all supporting electronics shall not exceed the weight, volume, power, and cooling provisions provided for sensor function within the SHARP system as specified in the Sensor Performance Specification (SPS) for SHARP (document #). The Contractor shall ensure the imaging sensor(s) meets the performance requirements contained within the sensor performance specification (Spec. #). All operational performance requirements detailed for the SHARP Pod will flow through to the design and fabrication of the sensor(s). The sensor performance in the operational and flight dynamic envelop to include aircraft maneuvering environment, sensor pod environment (temperature, humidity, shock, and vibration) shall be in accordance with the Sensor Performance Specification. To meet schedule and cost, the Contractor shall make maximum use of non-development items (NDI) and near NDI. The following factors shall be considered in selecting hardware:

a. SHARP Imagery Sensor Performance Specification compliance;

    1. Life Cycle Costs (LCC), including acquisition cost,

and operational and support costs; and

c. Qualitative system considerations, including: (1) Market acceptability;

(2) Reprocurability, obsolescence and upgradeability;

(3) Adequacy of available technical data and reprocurement data rights of the product; and

(4) Availability of long term technical and part support from the Original Equipment Manufacturer (OEM).

The Contractor shall maintain an aggressive schedule for hardware design and fabrication identifying risk areas and developing risk mitigation plans for the duration of the contract. Status shall be reported during Program Management Reviews (PMRs).


    1. Software
    2. The Contractor shall develop for Government approval a Software Development Plan (SDP) which implements the requirements of the SHARP Sensor(s) Performance Specification (Spec. #) and defines the Contractors process for the management and development of software. The development process shall include system/sensor requirements analysis, software requirements analysis, risk identification and management, preliminary design, detailed design, coding, integration CSCI testing and sensor integration and test. The SDP shall include types of development tools (hardware and software) to be used for maintenance and support of deployed software. The Contractor shall use systematic and documented software development methods. The SDP will be used for imagery sensor design, development, integrating, documenting and testing sensor support software both internal to the sensor(s) and between the sensor(s) and the SHARP system. The SDP will also be followed for sensor software maintenance. The Contractor shall furnish all equipment and support software necessary for the accomplishment of software development and maintenance to the level required in the Sensor Performance Specification during performance of the contract. The Contractor shall establish a Software Quality Assurance Program to ensure the computer software programs contain as few defects as possible. Limits on defect and classification of defects will be IAW the Sensor Performance Specification. The Contractor is required to maintain the software for the duration of the contract. (CDRL XXX2/3/4, SDP,SQAP and Computer Software Product End/Item (CSPE/I) for CSCI build)


      1. Non-Developmental Software (NDS)
      2. In order to facilitate cost-effective development and support, the Contractor is encouraged to incorporate NDS. NDS may be commercially developed or reusable software from other Government projects. The Contractor shall describe in the SDP a plan to maintain commercial or reusable software and, evaluate the software to determine whether it performs as documented.


      3. Software Metrics

      As part of the SDP, the Contractor shall identify a set of metrics, including at a minimum, those identified in AVIONINST 5335.1. These metrics shall be used to track software development progress throughout the program. Status shall be reported during technical reviews and PMRs and shall include software anomaly reports.


    3. Test And Evaluation
    4. The Contractor shall develop and implement an Acceptance Test Plan (ATP). The ATP shall be developed and executed by an integrated Government/Contractor test team. The Contractor shall perform developmental lab testing for the sensor. The combined Government/Contractor test team shall conduct lab, ground and flight integration testing at the Government and SHARP Pod Contractor facilities. Laboratory tests shall consist of development and integration tests. Ground tests shall consist of installation and integration tests conducted in the SHARP System prior to flight tests. Flight tests shall be used to verify that the developed and installed sensor(s) meets the system requirements contained in the performance specification, SRD, and CIDS. The Contractor shall provide on-site support to include engineering support, test planning, prepare Test Activity Reports (TARs) and System Anomaly Reports (SARs), data management and processing at the remote site. Flight testing will be conducted at the Naval Air Warfare Center, Weapons Division, China Lake (NAWC-WD-CL) and the Naval Air Warfare Center, Aircraft Division, Patuxent River (NAWC-AD-PAX) or other sites as directed by the Government. In addition, the Contractor shall maintain the EDM units in an appropriate status to support follow on test events. (CDRL XXX5, ATP, CDRL XXX6, TARs, and CDRL XXX7 SARs)


      1. Test And Evaluation Support
      2. The Contractor shall provide all E&MD test/support equipment needed to meet the requirements of the contract except for the test/support equipment provided by the Government as identified in the Government Property clause of this contract. The Contractor shall be an active participant in the SHARP System Integration Test Team (ITT). The Contractor shall provide on-site support to include engineering support, briefs and debriefs during developmental testing to be conducted at the NAWC-WD-CL and NAWC-AD-PAX or other sites as directed by the Government.


      3. R&M And BIT Monitoring During Flight Test

The Contractor shall monitor organizational level Reliability and Maintainability (R&M) and Built-In Test (BIT) parameters on the SHARP Imagery Sensor(s) to analyze trends through E&MD. The parameters shall include, but not be limited to:

The Contractor shall monitor the maintenance activity for the E&MD flight test program. (CDRL XX08 R&M Program Plan)

  2. The Contractor shall establish a Configuration Management (CM) Program that addresses all new and/or modified hardware, firmware, software and documentation resulting from this contract. The Contractors CM program shall provide configuration identification, configuration control, configuration status accounting, of all new and/or modified sensor hardware, firmware, software, and documentation including Government-Furnished Property for the duration of the contract. (CDRL XX09 CM Plan)

    1. Configuration Identification (CI)
    2. The Contractor shall, in consonance with the maintenance concept for SHARP, select the Configuration Items (CIs) to be identified and assign hierarchical identifiers to each CI, select the configuration documentation to be used to identify each CI, define and document interfaces between CIs, and establish a release system for the control of configuration documentation and computer software source code. The hardware and software configuration of the sensor system shall be identified by the functional baseline and product baseline. The functional baseline is defined by the sensor system performance specification. The product baseline is defined by the engineering drawings, Associated Parts List, Computer Software Configuration Items, and Engineering and Logistics Life Cycle Documentation.

      1. Functional/Physical Configuration Audits (F/PCA)

    The Contractor shall perform Functional and Physical Configuration Audits. (CDRL XX10 FCA/PCA Plan and CDRL XX11 FCA/PCA Report)

  4. The Contractor shall manage all aspects of the SHARP Imagery Sensor(s) contract using an IPPD Contractor-led IPT including the Government (to include the user as appropriate). The Contractor shall implement processes that ensure attainment of Clear Accountability in Design (CAID) principles. The Contractor shall ensure engineering activities incorporate logistics and supportability considerations per the Performance Specification prior to, during and after design decisions are implemented. Data prepared by the Contractor under this SOW tasking that is not deliverable under a CDRL shall be identified on the Data Accession List. CDRL XX12, DI-MGMT-81453/T, Data Accession


    1. Meetings And Reviews

      1. Program Management Reviews

      The Contractor shall conduct PMRs at the Contractor’s facility. The PMR will be conducted to provide the Government necessary visibility into the conduct and consequences of the various efforts by the Contractor. The Contractor shall present the technical performance, cost, schedule, and logistics program status. Problem areas, variances, risks and recommended mitigation/ corrective actions and corrective action plans shall also be identified and presented. The Contractor shall provide meeting agendas to the Government and shall prepare minutes of the formal meetings. CDRL XX13 Meeting Agendas and CDRL XX14 Meeting Minutes


    3. Technical Interchange Meetings

    The Contractor shall host and participate in Technical Interchange Meetings (TIMs) to discuss and resolve sensor issues. The Contractor shall host TIMs in conjunction with PMRs. CDRL XX15 Meeting Agendas and CDRL XX16 Meeting Minutes


  6. System safety shall be accomplished IAW with the SHARP Imagery Sensor System Safety Program Plan (SSPP). The Contractor shall conduct analyses as required to identify and quantify hazards in hardware, software and human interfaces. The program shall involve system safety in the design process to assure safety in design, manufacture, handling, testing, usage, maintenance and integration. Hazards, including environmental and hazardous materials, shall be eliminated or controlled to an acceptable level of risk in accordance with the SSPP. CDRL XX17 System Safety Program Plan

    1. Environmental And Hazardous Material
    2. The Contractor shall meet all applicable international, federal, state and local environmental regulations. The Contractor shall tailor its environmental and hazardous material management program to accommodate the requirements of this program. This program shall integrate the management of environmental safety and health impacts and pollution prevention initiatives into the systems engineering process. Specifically, this includes identification of environmental, safety and health impacts associated with material and process decisions with emphasis on hazardous materials required and hazardous waste generated during the maintenance, operation, and disposal of the sensor system. The Contractor shall address not just impacts to the program, but the reduction and elimination of hazardous material where possible in the sensor system life cycle. This shall be accomplished IAW National Aerospace Standard (NAS) 411.

      The Contractor shall minimize the requirements for use of hazardous materials throughout the life cycle of the system including reductions in hazardous materials, control technologies, waste treatment, process changes, and demilitarization/disposal methods. The Contractor shall recommend the incorporation of hazardous materials into the system design only after they have been identified as the least polluting, cost effective alternative materials and processes available


    3. Reliability, Maintainability And Built In Test
    4. The Contractor shall establish and maintain an active and effective R&M and BIT program during the E&MD phase of the program. The R&M and BIT program shall ensure achievement of the Imagery Sensor Performance Specification (#xxxxx). This program shall include the R&M and BIT analyses and test tasks for the sensor system. Environmental Stress Screening (ESS), Burn-in, ATP and environmental qualification test procedures shall be proposed by the supplier as deemed appropriate by the IPPD process. The program shall also include a schedule with estimated start and completion points for each R&M and BIT analysis, test task and associated data submittals. (CDRL XX18 R&M Program Plan.)


      1. Failure Reporting, Analysis And Corrective Action System (FRACAS)
      2. The Contractor shall establish and maintain a closed loop FRACAS IAW the following requirements. Failure reporting and analysis shall be initiated by the contractor for all failures that occur throughout integration, manufacture, handling, checkout, and testing of the sensor. All failures occurring during testing, including acceptance, ESS, Burn-In, performance evaluation and qualification, shall be collected and analyzed. These data shall be used for design improvements and pattern failure identification. Failure analysis shall be of sufficient depth to permit the identification of failure causes and the corrective actions. Criticality of failures shall be prioritized IAW their individual impact on the operational performance of the equipment. Failure analysis reports shall be closed out within 30 days of failure occurrence or rationale shall be provided for any extensions. The FRACAS requirement shall be imposed on all subcontractors. The Contractor shall prepare a Failure Summary and Analysis Report IAW the CDRL. (CDRL XX19 Failure Summary and Analysis Report)

      3. System Reliability Predictions
      4. The Contractor shall provide reliability predictions IAW MIL-HDBK-217 to the SRA level of indenture. (CDRL XX20 Reliability Predictions)

      5. System Maintainability Predictions
      6. The contractor shall provide maintainability predictions to the SRA level of indenture IAW MIL-HDBK-472. (CDRL XX21 Maintainability Predictions)


      7. Maintainability And BIT Demonstration
      8. The Contractor shall conduct Maintainability and BIT Demonstrations to verify MTBF and BIT performance. (CDRL XX22 Maintainability Demonstration Plan and CDRL XX23 Maintainability Report)


      9. Reliability Critical Items
      10. The Contractor shall identify and make recommendations for control of those items which require "special attention" because of complexity, life limit, limited shelf life, application of advanced state of the art techniques and the impact of potential failure on safety, readiness, mission success, or the demand for maintenance/logistics support. This information will be made available through the IPPD process.


      11. Part Level Stress Analysis

      The Contractor shall propose parts derating criteria which must consider past component history, environmental stresses and component criticality. Parts stress analysis shall be performed to verify compliance with agreed-to derating criteria under the following conditions: Nominal unit and module power dissipation, steady state worse case piece part stress, and steady state worst case aircraft environments. This information shall be included in the system reliability prediction.


    5. Failure Modes, And Effects And Criticality Analysis (FMECA)
    6. The Contractor shall perform a functional FMECA on the Imagery Sensor(s) to support the Logistics Management Information (LMI) and maintain the results of the FMECA. Upon mutual agreement, the Contractor shall document all failure modes down to the Weapons Replaceable Assembly (WRA) level and a severity classification category for each indentured level. For those WRAs identified as "I" level candidates, the Contractor shall document all failure modes down to the SRA level and a severity classification category for each indentured level. Where practical, the Contractor shall maximize use of the sensor system internal BIT analysis. The FMECA results shall be presented at the TIM and be made available through the IPPD process and documented in the LMI.


    7. Electromagnetic Environmental Effects

    The Contractor shall plan, conduct, and support E3 testing IAW the requirements defined in attachment X entitled Electromagnetic Environmental Effects.


  8. The Contractor shall propose a performance based warranty based on a failure free operating period. A method for tracking operating hours for prime equipment and spares shall be included in the warranty implementation and management plan. (CDRL XX23 Technical Report - Warranty Implementation Management Plan)



    1. ILS Program Management
    2. The Contractor’s ILS organization shall consist of a Logistics Manager (LM) and individual Logistics Element Managers (LEMs). Management of the Contractor’s ILS program shall be vested in the LM. The LM shall serve as the point of contact with concerning matters pertaining to management of the SHARP Sensor ILS requirements in this SOW. The Contractor’s LM and individual LEMs, as required, shall participate in and address logistics support at all meetings.


    3. offeror LMI/Engineering Interface

The Contractor shall define and establish the management controls between the ILS Program and the Engineering and design activity necessary to ensure that the system support requirements are derived from, and based on the actual hardware design. To this extent, the Contractor shall institute the following in-house controls such that:


    1. ILS Program Control

      1. LMI Guidance Conference
      2. The Contractor shall host/participate in an LMI guidance conference within 30 days after contract award. The guidance conference shall establish interfaces between requiring authority/Contractor personnel; provide ground rules and assumptions to be used in the performance of LMI tasks and analysis; discuss the scheduling of LMI tasks, subtasks, and completion of data records. In addition, LMI data product requirements shall be discussed including candidates for documentation, the proposed Reference Designation Structure, and data element selection and definitions. The Contractor shall prepare minutes of the conference to be delivered to the requiring authority within 10 working days of the conference completion. The minutes will include as a minimum a description of the problems and issues raised, the alternate solutions and tradeoffs discussed with logistics and performance ramifications, alternates selected with rationale, and action items assigned. (CDRL-XX25 Conference Minutes)


      3. ILS Elements Baseline Schedule
      4. The Contractor shall prepare and submit a schedule of the major tasks and milestones for producing the required ILS for the SHARP Imaging Sensor program. This schedule shall be submitted as part of the Integrated Support Plan. The baseline schedules shall not only illustrate the tasks defined in this SOW, but shall also indicate those additional tasks and key support milestones not yet under contract, but which are required to field a fully supportable SHARP Imaging Sensors system. (CDRL-XX26 Integrated Support Plan)


      5. LMI Program Reviews

LMI program reviews shall be held at an interval that is mutually agreeable to the requiring authority and the Contractor, but not to exceed an interval of 180 days through the period of performance of this contract. LMI progress reports shall be provided by the Contractor to report progress on SOW tasks at LMI reviews. LMI program progress information shall contain, but not be limited to the following information:


      1. LMI Data Product Review

The LMI data product review(s) shall be hosted by the Contractor to allow the requiring authority to formally evaluate the adequacy, accuracy and timeliness of data contained in the LMI data products. Whenever possible, these activities shall be scheduled concurrent with the LMI program reviews. The Contractor’s review team shall consist of the analyst directly responsible for producing the work and representatives from the individual logistics elements. Hard copies of all LMI data products, topdown breakdown drawings, and supporting data used to develop the LMI data shall be readily available at the reviews. The Contractor shall prepare minutes of the review(s) to be provided to the government within 10 working days of the conclusion of each review. (CDRL-XX28 Conference Minutes)


    1. LMI Program Requirements
    2. The Contractor shall manage and execute a Supportability Analysis program for the SHARP Imaging Sensors by fulfilling the general requirements in accordance with MIL-PRF-49506 and performing the supportability analysis tasks and additional tasks as specified and tailored herein. Required documentation shall be developed in a standard data system format mutually agreed upon by the requiring authority and Contractor at the ILS guidance conference. (CDRL-XX29 Supportability Assessment Plan)


    3. Logistics Element Supportability Analysis
    4. The supportability analysis shall establish the basis for performing logistic element analysis and developing and quantifying support requirements for the SHARP Imaging Sensors. The supportability analysis shall be the primary basis for:

      a. Maintenance Planning

      b. Repair Analysis

      c. Support and Test Equipment

      d. Supply Support

      e. Packaging, Handling, Storage, and Transportation (PHS&T)

      f. Technical Data

      g. Facilities Requirements

      h. Software Support

      i. Training and Training Equipment Requirements


    5. LMI Data Products

      1. Data Organization
      2. An indentured structure (e.g., a Logistics Control Number - LCN structure), with requiring authority approval, shall be utilized for the data products. The structure shall depict relationships between assemblies and subassemblies within and shall be structured to "roll up" to the SHARP pod LCN structure. An Automated Data Processing (ADP) system shall be used to process and store LMI data. Examples of commercially available products to perform this activity are DILSA-2B, LEEDS-2B, SLIC-2B, OMEGA-2B, etc.


      3. Data Not Resident In The LMI Data Product
      4. Data and documentation generated from the LMI tasks and studies that are not captured in the Data Product shall be maintained by the Contractor, made available for Government review via the Data Accession List, and shall be provided in the Contractor’s format at the Contractor’s facility. This information shall contain control numbers and task codes where applicable and may consist of such items as supplemental data; e.g., functional block diagrams, decision trees, trouble-shooting charts, and sketches, etc.


      5. Data Validation

      The Contractor shall establish internal procedures that provide for validation of the adequacy and technical accuracy of Supportability Analysis documentation. The Contractor shall provide a means to ensure data feedback into the LMI from from R&M demonstrations, support and test equipment compatibility tests, technical publications validation actions, flight operations and maintenance actions. These results shall be incorporated into the affected Supportability Analysis database.


    7. LMI Task Requirements
    8. The Contractor shall perform the selected tasks/subtasks identified below. These tasks/subtasks shall be performed IAW procedures and schedules established during the LMI Guidance Conference. (CDRL-XX30 Logistics Management Information (LMI) Data)


      1. Maintenance Plan
      2. The Contractor shall develop a Maintenance Plan to support the SHARP Imaging Sensors at the Organizational (O-) and Intermediate (I) Level(s) of maintenance. Data and information generated from the Contractor’s analysis shall be documented and maintained in the LMI data base as specified in MIL-PRF-49506, and identified in the requiring authority’s furnished LMI data product worksheet (MaPl column) provided with this contract. Results for this task shall be documented and submitted in accordance with the data item.


      3. Analysis Tasks And Studies

Analysis tasks and studies should identify any existing/planned support resources for potential use by the SHARP Imaging Sensors. The Contractor shall perform a task analysis of the O- and I-level maintenance activities. For each operation and maintenance task the following shall be determined:


      1. Environmental Impact

To ensure control of the environmental effects of maintenance processes, the Contractor shall identify and list all processes that use hazardous material or generate a hazardous waste by-product. Specific emphasis will be to justify the reason a non-compliant process was selected. The Contractor is to identify all hazardous material used in each maintenance process. The Contractor shall supply documentation on the hazardous material which identifies the constituents and properties of the hazardous material. The Contractor shall identify the potential health hazards of the hazardous material to the procuring activity and identify the waste streams of each maintenance process that generates a hazardous waste including the category (air, solid, liquid) and hazardous constituents of the waste stream by volume and percent, as well as mitigation measures. Results shall be documented in the LMI Product database as prescribed during the LMI Product data base guidance conference.


    1. Support Equipment
    2. The Contractor shall identify all support equipment required to support and test the SHARP Imaging Sensors at the O- and I-levels of maintenance. The Contractor shall identify any modifications to existing support equipment. The Contractor shall provide a list of all peculiar support/test equipment, that currently exists or is in development, that is required to support the existing sensor(s) reconnaissance equipment at designated level(s) of maintenance. The Contractor shall provide copies of System Synthesis Models (SSM) data sheets and Test Requirements Documents (TRDs), if available, for the existing sensor(s) reconnaissance system. If the Contractor refuses to waive data rights to the TRDs, he shall price the TRDs as an option CLIN.


    3. Source Data For Technical Manuals
    4. The Contractor shall provide source data (engineering and technical data, drawings, and specifications) of SHARP Sensor hardware and support equipment (and any modifications thereto) necessary for the development of operator and maintenance manuals at the prescribed levels of maintenance for the SHARP Imaging Sensors. The Contractor shall maintain all source data required to generate any new technical manuals and change/revise existing technical manuals for any new and/or modified system hardware and support equipment. The source data shall be maintained by the Contractor to allow access by the requiring authority as necessary. The Contractor shall provide for validation of the adequacy and technical accuracy of LMI documentation used in the preparation of the manuals.


    5. Drawings
    6. The Contractor shall provide product level drawings of the SHARP Imaging Sensors to the SRA level. Engineering data shall meet the requirements set forth in MIL-T-31000A notice 1. The Contractor shall make available to the requiring authority any existing drawings (with electrical schematics that include interconnecting wiring within and without each WRA, e.g., motherboard to SRA connector, motherboard to J-connectors/backplane interface) of existing Sensor(s) reconnaissance equipment for applicability. (CDRL XX31, TDMP).


    7. Interim Contractor Support
    8. The Contractor shall plan for Interim Contractor Support (ICS) for the SHARP Imaging Sensors system and associated support equipment. The Contractor’s planning shall be provided in an Interim Contractor Support Plan (ICS Plan). The ICS Plan shall reflect any unique requirements, and how the Contractor intends to develop, implement, and manage ICS, and detail transition from an ICS posture to a complete organic capability. The Contractor shall address each level of maintenance to include necessary resources identified in the LMI Maintenance Plan. In cases where a WRA cannot be repaired on site, the maximum turnaround time from receipt at the vendor’s repair activity until it is received (RFI) by the designated Government activity shall be 30 days. The Contractor shall provide monthly status reporting to the requiring authority as provided in the ICS Plan. MILSTRIP requisitioning shall be authorized for this effort. Deliver as a Chapter in the ISP. (CDRL XX26 ISP)


    9. Training
    10. The Contractor shall document the training requirements driven by the SHARP Imaging Sensor(s) for aircrew and maintenance personnel. The Contractor shall provide a list of existing operational and maintenance training curricula, technical training equipment hardware and software, training aids, and support equipment necessary to support operational and maintenance training for the existing sensor(s) reconnaissance equipment. Deliver as a Chapter in the ISP. (CDRL XX26 ISP)


    11. Packaging, Storage, Handling & Transportation (PHS&T)
    12. The Contractor, utilizing LMI data, shall implement and maintain a PHS&T program in consonance with the SHARP Imaging Sensor(s) program environmental definition effort. The Contractor shall ensure that design of equipment/hardware in shipping configuration provides for blocking, bracing, lifting, slinging and tie down for surface and water shipment modes. The Contractor shall provide loading, unloading, and movement instructions for outsized, overweight, hazardous, and shock sensitive items. Based on the characteristics of the (item), mode of transportation, and destination, hazardous materials shall be identified, handled, packaged, and labeled to meet existing national and international requirements. Preservation and packaging for equipment components, spare parts, and peculiar support equipment shall be designed and developed to provide the degree of protection and handling provisions necessary based on the characteristics of the item, its source, destination, storage, and mode of transportation. The storage container will also be used as a shipping container. Electrostatic discharge sensitive items shall be packaged in accordance with existing regulations. Items requiring a specialized container shall be identified by the Contractor prior to undertaking a new container design. The Contractor shall provide all relevant PHS&T via the LMI database and as a Chapter in the ISP. (CDRL-XX30 Logistics Management Information (LMI) Data and CDRL XX26 ISP)


    13. Facilities
    14. The Contractor shall identify facilities both ashore and afloat required to support testing, training, movement, and maintenance of the SHARP Imaging Sensors system and peculiar support equipment. The Contractor shall identify specific technical requirements upon which facilities modifications must be predicated. The Contractor shall provide facility requirements for existing sensor system(s), if available. The Contractor may participate in any site survey activity. Results shall be documented in the LMI database and documented as a Chapter in the ISP. (CDRL-XX30 Logistics Management Information (LMI) Data and CDRL XX26 ISP)


    15. Manpower And Personnel
    16. As described in paragraph 8.7.2, the requisite analysis, tasks, and studies shall be performed by the Contractor to ensure that all manpower and personnel requirements are met. The analysis shall identify corrective and preventative maintenance tasks to be performed on each SHARP Imaging Sensor system item(s) at prescribed maintenance level(s), as well as the manpower and skill level requirements for each task performed at each maintenance level. This will ensure that there will be sufficient manpower in place to support the system when the system is fielded.


    17. Supply Support

The Contractor shall prepare summaries that will identify and recommend the requisite, and optimum numbers of, spare and repair parts that will maximize operational availability of the SHARP Imaging Sensors. The Contractor shall provide a means to integrate Government orders for spare and repair parts into SHARP Sensor(s) production procurement. The Contractor shall host and participate in a provisioning guidance conference within 30 days of contract award. The Contractor shall prepare and agenda to be approved by the requiring authority. The Contractor shall submit minutes for government review within 10 working days of the conclusion of the guidance conference. (CDRL XX31 SAIP)