Section J3 Data Item Descriptions.pdf

DTFAWA-06-R-VRRP

DATA ITEM DESCRIPTION 2. IDENTIFICATION NO

AGENCY NUMBER

1. TITLE

Conference Agenda

FAA ADM001

3. DESCRIPTION/PURPOSE 4. APPROVAL DATE

3.1 Provides agenda information concerning the purpose, location, and schedule of joint Government/Contractor conferences (e.g., conferences, reviews, audits, etc.) required to manage the acquisition of system/equipment-related items, and services. The agenda sets forth the place, time, date, purpose, and objectives of each forthcoming conference

5. OFFICE OF PRIMARY

RESPONSIBILITY

ATO-W

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP 8. APPROVAL LIMITATION

7.1 This Data Item Description (DID) is applicable to all contracts for system/equipment related items, and services.

9. REFERENCES

CDRL NUMBER

ADM001

10. PREPARATION INSTRUCTIONS

The Contractor shall prepare a separate agenda in Contractor format, as approved by the Government, for each proposed conference. The agenda shall be transmitted by electronic mail message and followed up with a formal letter. The agenda shall include, but not be limited to the following, where applicable:

a. The purpose and objective of the conference;

b. The recommended conference location, date, and duration;

c. A daily chronological listing of each topic or sub-topic to be discussed and the time scheduled for each topic;

d. A recommended list of activities to be represented and identification of their responsibilities;

e. A recommended list of subcommittees to be established during the conference and the proposed activity representation of each sub-committee;

f. Reference to and brief description of the results of previous meetings on the same subject;

g. Location, schedule, and purpose of subject area to be covered by each sub-committee;

h. Name of the Government chairperson and the Contractor co-chairperson of the conference and designated activity representative to act as sub-committee chairperson;

i. Administrative notes as required to indicate lodging, restaurant, transportation, and administrative services available to conference attendees;

j. Complete list of all documentation to be available for review;

k. Brief description of progress on actions or problems identified at previous meetings;

l. Other pertinent information such as forms to be used, identification of any deviations or waivers, security classification, clearance requirements, etc.

DID ADM001 - 1 of 1

AGENCY NUMBER

Conference Minutes

FAA ADM002

5. OFFICE OF PRIMARY

RESPONSIBILITY

ATO-W

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP 8. APPROVAL LIMITATION

CDRL NUMBER

ADM002

10. PREPARATION INSTRUCTIONS

Unless otherwise directed by the Government, the Contractor shall prepare and deliver minutes for each conference, meeting, and review held at the Contractor’s facility. The minutes will be prepared in Contractor format, as approved by the Government, and shall include, as a minimum, the following:

a. A title page containing the following:

(1) Title - type of meeting and date;

(2) Identification of system/equipment, contractor number, etc,;

(3) Space for signatures of the designated representative of the procuring activity and the Contractor.

b. The purpose and objective of the conference;

c. The conference location;

d. A summary of the discussions, decisions, agreements reached, and directions of the conference or individuals sub-committees thereof;

e. A list of attendees by name, activity represented, activity code/office, and telephone number, as appropriate;

f. Copies of action item sheets for each action to be implemented as a result of the conference. Format of the action item sheets shall be as specified by the conference chairperson;

g. An updated copy of the conference agenda to reflect the actual agenda for the conference as conducted;

h. The required elements of information specified by the conference chairperson that are applicable to the type of conference conducted and other data and information as mutually agreed between the contractor and the procuring activity.

The minutes will be delivered in paper copy and in electronic format (e.g., Microsoft Windows/Office suite of products) and recording media, and without restrictions that would prevent the Government from reproducing or editing the information.

DID ADM002 - 1 of 1

AGENCY NUMBER

Configuration Management Plan (CMP)

FAA CMP001

3.1 The Configuration Management Plan (CMP) describes the

Contractor’s internal configuration management organization;

responsibilities of the members; the relationship among several offices/divisions; the policies and procedures for identifying the documentation of the functional and physical characteristics of

5. OFFICE OF PRIMARY

RESPONSIBILITY

AND-320

configuration items required by the contract: procedures for controlling changes to configurations items during development/production;

procedures for recording and reporting change processing implementation status; and the external relationships required to maintain total system compatibility

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP 8. APPROVAL LIMITATION

9. REFERENCES

FAA-STD-021

CDRL NUMBER

CMP001

10. PREPARATION INSTRUCTIONS

10.1 GENERAL. The plan shall describe how the Contractor intends to assure proper configuration identification, configuration control, including the control of approved Engineering Change Proposal (ECPs), configuration audits, and configuration status accounting. Applicable standards and specifications, such as those listed in Block 9, shall be used in accordance with the contract requirements to develop the details of the plan. The Contractor shall use FAA-STD-021, Configuration Management, as a guide.

10.2 FORMAT. The CMP shall be prepared in a Government approved Contractor format. The Contractor shall deliver the CMP in paper copy and in Government approved electronic format (e.g., Microsoft Windows/Office suite of products, etc) and recording media. The CMP shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the CMP using the electronic version

10.3 CONTENT. The Configuration Management Plan (CMP) shall contain the following Sections and information.

SECTION 1 - INTRODUCTION

a. Purpose and Scope. This paragraph shall state the purpose, scope, and general applicability of the CMP.

b. Definitions. This paragraph shall reference applicable directives or glossaries containing definitions of terminology.

c. Configuration Management (CM) Summary. This paragraph shall describe the plan’s major features and objectives, and provide a concise summary of the Contractor’s approach to accomplish CM.

DID CMP001 - 1 of 3

DATA ITEM DESCRIPTION 2. IDENTIFICATION NO (S)

AGENCY NUMBER

1. TITLE

Configuration Management Plan (CMP) FAA CMP001

10. PREPARATION INSTRUCTIONS (Continued)

SECTION 2 – APPLICABLE DOCUMENTS

This section shall list those specifications, standards, manuals and other documents applicable to the CM effort. Each document shall be completely identified by title, document number, issuing authority, and date of issue.

SECTION 3 – CONFIGURATION MANAGEMENT ORGANIZATION AND RELATIONSHIPS

This section shall identify the Contractor’s organization for CM. It shall include the:

a. Relationships among the Contractor’s project organization functional organizations, and facility management;

b. Responsibilities and authority for CM of all participants groups and organizations;

c. Identification of Contractor CM organization including configuration control boards, or groups and material review boards;

d. Policies and directives relating to CM;

e. Relationships among the Contractor’s SW/HW CM organization, and the Contractor’s project organization, including hardware and software developmental entities;

f. Identification of a single authority who will serve as a focal point for all communications or CM related issues.

SECTION 4 – CONFIGURATION IDENTIFICATION

This section shall present the Contractor’s implementation plan for;

a. Selecting and identifying configuration items, as required by the contract, and additional items considered necessary by the Contractor to ensure proper configuration identification, including requirements traceability matrix;

b. Developing, numbering, changing, and maintaining specifications and their relationships with specifications trees, if applicable;

c. Preparing, identifying, and revising engineering drawings and associated lists;

d. Ensuring all representations of the software is completely and consistently identified.

e. Establishing baselines as appropriate (functional, allocated, design, and product);

f. Assignment of nomenclature and serial numbers:

SECTION 5 – CONFIGURATION CONTROL

This section shall describe the Contractor’s procedures for configuration control. It shall include:

a. Contractor’s configuration control organization, authorities and activities.

b. Configuration control, including depth of control and interfaces;

c. Promulgation and implementation of Specification Change Notices (SCN) and Notices of Revision

(NOR):

d. Preparation and processing of Program Trouble Reports (PTRs):

e. Procedures for ensuring that the implementation of approved hardware and software changes are reflected in all facets of the affected baselined program descriptive documentation, and program materials (e.g. design, test, and user narrative).

DID CMP001 - 2 of 3

AGENCY NUMBER

Configuration Management Plan (CMP)

FAA CMP001

10. PREPARATION INSTRUCTIONS (Continued)

SECTION 6 – CONFIGURATION STATUS ACCOUNTING

This section shall present the Contractor’s procedures for collecting, recording, processing, and maintaining data necessary for producing configuration status accounting reports. It shall include:

a. Formats and data elements for CM status accounting records and reports:

b. Format and form of configuration lists to reflect “as designed” vs. “as built” configuration;

c. Content and format of periodic summary reports to reflect status of Program Trouble Reports (PTRs) as appropriate;

d. Procedures for reconciling the CSA reports and the status of the hardware, software, descriptive documentation, and program material with the approved baselines and associated approved changes.

SECTION 7 – SOFTWARE CONFIGURATION MANAGEMENT

This section shall describe the Contractor’s procedures for:

a. Reconciling deliverable software to its approved documentation if applicable;

b. Assuring that the software, descriptive documentation, and project material are properly identified;

c. Assuring the incorporation of approved changes;

d. Reconciling the configuration status accounting reports and the status of software, descriptive documentation, and program materials with the approved baseline(s) and its approved changes.

SECTION 8 – INTERFACE CONTROL MANAGEMENT

This section shall describe the Contractor’s plan for coordinating efforts involved in design and data management to ensure compatibility through interfaces with associate Contractors (e.g., where two or more prime Contractors are participating in development/production of a subsystem), if applicable.

SECTION 9 – CONFIGURATION AUDITS

This section shall include:

a. Planned quality assurance measures that apply to CM;

b. Planned procedures for Functional Configuration Audits (FCA) and Physical Configuration Audits

(PCA);

c. Plans, procedures and schedules for conduct of CM audits.

SECTION 10 – SUBCONTRACTOR CONFIGURATION CONTROL

This section shall describe the Contractor’s system for control over subcontractors, if applicable. It shall include procedures for subcontractor integration of CM requirements with those of the prime contractor including the methods of ensuring compliance (i.e., subcontractor CM Plan, etc.).

SECTION 11 – CONFIGURATION MANAGEMENT MAJOR MILESTONE

This section shall identify major CM-related milestones for the life cycle phase (s) of the contractual efforts.

DID CMP001 - 3 of 3

AGENCY NUMBER

Configuration Audit Summary Report

FAA CMP002

3.1 The Configuration Audit Summary Report provides the text and marked-up technical documentation that identifies the hardware and software discrepancies noted during functional and physical configuration audits.

5. OFFICE OF PRIMARY

RESPONSIBILITY

ATO-W

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP 8. APPROVAL LIMITATION

7.1 This DID is shall be used in conjunction with the functional configuration audit (FCA) and physical configuration audit (PCA).

9. REFERENCES

MIL-STD-973

CDRL NUMBER

CMP002

10. PREPARATION INSTRUCTIONS

10.1 GENERAL. The configuration audit summary report(s) shall include the results of the functional configuration audit (FCA) and physical configuration audit (PCA), as applicable.

10.2 FORMAT. The Report(s) shall be prepared in Contractor format as approved by the Government. The Contractor shall deliver the Report(s) in paper copy and in Government approved electronic format (e.g., Microsoft Windows/Office suite of products, and on 3.5-inch diskette or CD-ROM). The Report and associated deliverables shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the Report using the electronic version.

10.3 CONTENTS. The Report shall include, as a minimum, the following:

a. A title page containing the following.

(1) Title of the audit, the date, and the location of the audit.

(2) Identification of system/equipment, Contractor number.

(3) Space for the signatures of the Government and the Contractor's Program Manager.

b. A copy of the audit agenda and a description of the purpose and objective of the audit.

c. A summary of the audit results, identification of the issues/discrepancies noted during audit, identification of issues/deficiencies resolved during the audit and a description of how each issue/discrepancy was resolved, and a description of open issues/deficiencies, and the assignment of action plans to correct the issues/deficiencies (e.g., hardware or software).

d. A list containing the names of each attendee, the organization represented, and the attendees telephone number.

DID CMP002 - 1 of 1

AGENCY NUMBER

COTS/NDI Manuals List

FAA DOC001

3.1 The Commercial-off-the-shelf (COTS) / Non Developmental Item (NDI) list identifies all of the manuals, e.g., operator, maintenance, system user’s, etc.,) both Contractor and Original Equipment Manufacturer (OEM), that will be provided with each system.

5. OFFICE OF PRIMARY

RESPONSIBILITY

ATO-W

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP 8. APPROVAL LIMITATION

7.1 OEMs normally provide manuals/operator’s instructions and warranty information with the hardware and software. The Contractor shall provide all OEM documentation with the hardware and software delivered as part of the contract.

9. REFERENCES

CDRL NUMBER

DOC001

10. PREPARATION INSTRUCTIONS

10.1 The Contractor shall deliver a List identifying all the OEM documentation, e.g., manuals, user information/instructions, warranty information, etc., that will be delivered with hardware and software. The List shall be prepared in Contractor’s format as approved by the Government. The List shall group the information by OEM/equipment and include the following information for each;

a. Equipment noun nomenclature;

b. Name of the Original Equipment Manufacturer (OEM);

c. Document/manual title;

d. Document/manual date of publication; and,

e. Name of the originator of the document/manual, if not the OEM.

10.2 The Contractor shall deliver the List in paper copy and Government approved electronic format (e.g., Microsoft

Windows/Office suite of products). The List shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the List using the electronic version.

DID DOC001 - 1 of 1

AGENCY NUMBER

Maintenance Manual

FAA DOC002

3.1 The Maintenance Manual shall provide a complete set of operation and maintenance instructions for the system. These instructions shall provide sufficient detail to enable a technician with little or no formal training on the equipment to perform operator or maintenance functions, as appropriate.

5. OFFICE OF PRIMARY

RESPONSIBILITY

AOS-510

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP. 8. APPROVAL LIMITATION

7.1 Commercial manuals submitted to satisfy this requirement shall comply with this Data Item Description (DID) and Appendix I, FAA-D- 2494/b.

9. REFERENCES

FAA-D-2494/b

CDRL NUMBER

DOC002

10. PREPARATION INSTRUCTIONS

10.1 GENERAL INFORMATION. The Maintenance Manual shall be prepared in accordance with the requirements defined in FAA-D-2494/b. Commercial manuals for off-the-shelf equipment may be accepted without modifications provided they meet the requirements specified by Appendix I, FAA-D-2494/b and are approved by the Government.

10.2 MAINTENANCE INSTRUCTIONS. The maintenance instructions shall contain a complete description of the following:

a. All maintenance procedures and adjustments performed periodically to calibrate and prevent failure of any part of the system (preventive maintenance). The procedures shall include the time allocated to each operation during each scheduled maintenance visit.

b. All maintenance procedures and actions performed by a maintenance technician to diagnose and locate any fault in any part of the system, and to repair, adjust, and calibrate the equipment to meet the standards in the specification (corrective maintenance).

c. All test equipment required to inspect, test, calibrate, service, repair, overhaul an end item shall be identified.

This information shall include the identification of test cables, connectors, extender kits, and adapters required.

Maintenance instructions shall include a description of the operation of mechanical and electrical/electronic subsystems in sufficient detail to enable a Government or Contractor maintenance technician/specialist with no formal training on the system to accomplish all on-equipment/on-site maintenance actions. Information on each subsystem (e.g., display panels, central switch, channel bank, printer, operator position, special test equipment, etc.) shall be provided in the appropriate section(s) of the Maintenance Manual (e.g., operations, controls and indicators, standards and tolerances, maintenance procedures, etc.).

10.3 OPERATIONAL INSTRUCTIONS. The operational instructions shall contain a complete, step-by-step description of all operating procedures. These procedures shall be in sufficient detail to provide an operator with no formal training on the system with the information needed to properly perform each operational function.

DID DOC002 - 1 of 2

AGENCY NUMBER

Maintenance Manual

FAA DOC002

10.4 SYSTEM CHECKOUT INSTRUCTIONS. The Contractor shall provide step-by-step instructions for the checkout of the system. The instructions shall include, but not be limited to, mounting and connection procedures, and bonding and grounding procedures. Step-by-step procedures shall be provided to demonstrate that the system is operating correctly and within specified tolerances.

10.5 FORMAT. In addition to the format specified in FAA-D-2494/b, the Maintenance Manual shall contain the level of detail required (i.e., theory to the block level, block diagrams, operations, maintenance and installation instructions, etc,) to enable a trained maintenance specialist to identify line replaceable unit (LRU) failures as hardware, software, or firmware failures; and shall enable the maintenance specialist to replace the faulty LRU.

10.6 The Maintenance Manual shall be delivered in paper copy and in softcopy/electronic format using Government approved software (e.g., Microsoft Windows/Office suite of products, on CD-ROM) and in accordance with CDRL DOC002. The Maintenance Manual shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the Maintenance Manual using the electronic version.

DID DOC002 - 2 of 2

AGENCY NUMBER

Site Installation Master Plan (SIMP)

FAA IMP001

3.1 The Site Installation Master Plan (SIMP) shall describe the Contractor’s plan for installation, integration, and transition of the system.

5. OFFICE OF PRIMARY

RESPONSIBILITY

ATO-W

6. DDC REQUIRED

7. APPLICATION/INTERRELATIONSHIP 8. APPROVAL LIMITATION

9. REFERENCES

CDRL NUMBER

IMP001

10. PREPARATION INSTRUCTIONS

10.1 GENERAL. The Site Installation Master Plan (SIMP) shall describe the Contractor’s overall management plan for installation, integration, and transition the at each operational facility. The SIMP shall describe the Contractor’s plan for use of existing resources (i.e., personnel and materials) to satisfy the installation requirements specified in the contract. The SIMP shall also include the Contractor’s plan for installing the system with minimum impact to the facility’s operation.

10.2 FORMAT. The SIMP shall be prepared in a Government approved Contractor format. The Contractor shall deliver the SIMP in paper copy and in Government approved electronic format (e.g., Microsoft Windows/Office suite of products) on CD-ROM. The SIMP shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the SIMP using the electronic version.

10.3 CONTENTS. As a minimum, the SIMP shall contain the following sections.

a. Title Page. The title page shall contain the name of the program and the words “Site Installation Master Plan (SIMP)”. The title page shall contain the Contractor’s name, address, and telephone number, signature of the Contractor’s Program Manager and the Contractor’s Installation Manager, and date of the document before the SIMP is submitted to the Government.

b. Introduction. This section shall provide the purpose and scope of the SIMP.

c. Applicable Documents. This section shall list all of the documents, drawings, manuals, plans and procedures that will be used during the installation, integration, check out, and testing.

d. Installation Management. This Section shall contain an overview of the Contractor’s installation management, site installation and integration, and technical support organizations. The overview will clearly delineate each organization’s responsibilities and describe how the Contractor will integrate and manage the installation activities of these organizations.

DID IMP001 - 1 of 2

AGENCY NUMBER

Site Installation Master Plan (SIMP)

FAA IMP001

(1) Key Personnel. Identify by function, name, and title the key management and technical personnel who will be responsible for the installation and integration.

(2) Subcontractor Relationships. Describe all teaming agreements with subcontractor participating in the installation. Identify and define subcontractor(s) roles and responsibilities (i.e., installation, integration, and acceptance test).

(3) Installation Teams. Describe the organization and composition of the installation team, the number of teams, and the personnel skills and numbers assigned to each team. Define the roles and responsibilities of each team member.

e. Approach and Methodology. This section shall describe the Contractor’s overall approach to installation, integration, and acceptance testing.

(1) Installation. Describe the approach and methodology for installation. Address facility coordination and access requirements, distribution/installation of power and signal cables, temporary and final installation of backroom and position equipment.

(2) Integration. Describe the approach and methodology for performing integration, signal and power cables prior to site acceptance test (SAT).

(3) Acceptance Testing. Describe the approach and methodology for preparing for and performing site acceptance test. Address the types of tests planned (e.g., test on temporary installations, checkout/shakedown test to verify the system is functioning in accordance with the Specification, site acceptance test (SAT), etc.,), the procedures for resolving discrepancy reports generated during the formal SAT, and Government acceptance of the site after SAT.

f. Schedule. Provide an integrated schedule for “each” site showing the projected start and completion dates for the:

(1) Build/assembly;

(2) Factory acceptance test (FAT);

(3) Shipping/delivery;

(4) Installation and Integration;

(5) Pre-SAT (Contractor) checkout/test(s); and,

(6) Formal (Contractor/Government) SAT.

g. Technical Performance Monitoring. Describe the process to be used to monitor the technical performance of the installation team at each facility. Describe the plan for reporting and correcting installation problems/issues. Provide a discrepancy report form and instructions for its use and distribution. As a minimum the discrepancy report shall include the following information:

(1) Facility Location and address;

(2) Date discrepancy report was initiated,

(3) Name and title of individual (Government or Contractor) who originated the report;

(4) Description of the discrepancy or problem;

(5) Subsystem or component affected;

(6) Factors contributing to the discrepancy or problem; and,

(7) Action to be taken or taken to resolve the discrepancy or problem.

DID IMP001 - 2 of 2

AGENCY NUMBER

Site Acceptance Report (SAR)

FAA IMP002

3.1 This report shall document the completion of a site’s installation, integration, site acceptance testing, Government acceptance of the system, and the final as-accepted system configuration.

5. OFFICE OF PRIMARY

RESPONSIBILITY

7.1 The Contractor shall prepare a site acceptance report for each site. 9. REFERENCES

CDRL NUMBER

IMP002

10. PREPARATION INSTRUCTIONS

10.1 GENERAL. The site acceptance report (SAR) shall include the results of the site installation, integration, checkout, initial training, acceptance testing performed, and a copy of the final system configuration data.

10.2 FORMAT. The Contractor shall deliver the SAR in paper copy and in Government approved electronic format (e.g., Microsoft Windows/Office suite on CD-ROM. The SAR and all attachment shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the SAR using the electronic version.

10.3 CONTENTS. The report shall be prepared in a Government approved Contractor format. As a minimum, the report shall contain the following sections.

a. Title Page. The title page shall contain the name of the program and the words “Site Acceptance Report (SAR)”. The title page shall contain the Contractor’s Name, Address, and Telephone Number, signature of the Contractor’s Program Manager and the Contractor’s Installation Manager, and date of the document.

b. Introduction. This section shall provide the purpose and scope of the document and the name of the site.

c. Test Configuration. The Contractor shall deliver the final test configuration worksheets that define the final as-tested system. This shall include a hardcopy of all system software settings programmed into the final system configuration.

e. Site Acceptance Test Results. The results of the site acceptance test shall be delivered as part of the SAR and shall include the following:

(1) Data Collection Forms. The Government and Contractor signed final data collection forms containing the SAT results, including all as-measured performance levels.

(2) Discrepancy Reports. A copy of the original discrepancy reports. The discrepancy reports shall identify the open and closed items. Closed items will identify the Contractor actions performed to close the discrepancies and whether or not the Government agreed that the discrepancies had been corrected.

f. Site Acceptance Documentation. The Contractor shall include a Government signed FAA Form 256 or DD- 250 with the SAR.

DID IMP002 - 1 of 1

AGENCY NUMBER

Packing List/Bill of Materials (BOM)

FAA IMP003

3.1. The Packing List/Bill of Materials for each site’s equipment is prepared by the Contractor and lists all of the materials shipped to and used at the site.

5. OFFICE OF PRIMARY

RESPONSIBILITY

7. APPLICATION/INTERRELATIONSHIP. 8. APPROVAL LIMITATION

CDRL NUMBER

IMP003

10. PREPARATION INSTRUCTIONS

10.1 The Contractor shall deliver a Packing List/Bill of Materials (BOM) for each equipment shipment to the site.

a. The Packing List/BOM shall be in Contractor format as approved by the Government.

b. A paper copy of each shipment’s packing list/BOM shall be delivered with each shipment and copies shall be delivered in accordance with CDRL IMP003.

c. An electronic copy of each shipment’s packing list/BOM shall be delivered in Government approved Contractor format (e.g., Microsoft Windows/Office suite of products), on CD-ROM in accordance with

CDRL IMP003.

10.2 The Packing List/BOM shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the Packing List/BOM using the electronic version.

DID IMP003 - 1 of 1

DATA ITEM DESCRIPTION

1. TITLE 2. IDENTIFICATION NUMBER

Integrated Support Plan (ISP) FAA LOG001

3. DESCRIPTION / PURPOSE

3.1 The Integrated Support Plan (ISP) describes the Contractor’s plans for the management, control, execution, interface, and integration of all aspects of the Contractor’s integrated logistics support (ILS) program.

3.2 The Government will use the ISP to evaluate, monitor, and approve the contractor’s planning and performance of the ILS Program task(s) as specified in the contract.

4. APPROVAL DATE (YYMMDD) 5. OFFICE OF PRIMARY RESPONSIBILITY 6a. DTIC APPLICABLE 6b. GIDEP APPLICABLE

ATO-W N/A N/A

7. APPLICATION / INTERRELATIONSHIP

7.1 This Data Item Description (DID) contains the content and preparation instructions for the data products generated by the specific and discrete task requirements identified in the contract.

7.2 Each item in this DID may not be appropriate to all applications. Tailoring of this DID is permissible if approved by the Government.

8. APPROVAL LIMITATION 9A. APPLICABLE FORMS 9b. AMBC NUMBER

10. PREPARATION INSTRUCTIONS

10.1 GENERAL. The ISP shall document the Contractor's plan for gathering and analyzing data and managing, controlling, executing, integrating and interfacing the ILS Program Task(s) identified in the contract. The ISP shall demonstrate that when fielded the system will be supportable for its life cycle.

10.2 FORMAT. The ISP shall be prepared as described in this DID. The Contractor shall deliver the ISP in paper copy and in Government approved electronic format (e.g., Microsoft Windows/Office suite of products, on 3.5-inch diskette or CD-ROM.

The ISP shall be delivered without restrictive legends and software that would limit the Government's ability to copy/reproduce and edit/modify the ISP using the electronic version.

10.3 CONTENT. The ISP shall consist of the six (6) major sections and the information described below. If no data or narrative is required for a section or element (e.g., if there are no tasks, requirements or other standards, the Contractor shall enter "NOT APPLICABLE" and state the reason(s), e.g., "NOT REQUIRED BY THE CONTRACT".)

a. Section 1: Introduction

b. Section 2: Summary of System Characteristics

c. Section 3: ILS Program Management, Organization and Execution

d. Section 4: ILS Program Tasks

e. Section 5: Milestone Schedule

f. Section 6: Related Plans

INTEGRATED SUPPORT PLAN (ISP)

SECTION 1

INTRODUCTION

This section shall identify the integrated logistics support (ILS) requirements specified in the Statement of Work (SOW). This section shall be formatted and contain the data as shown below:

Purpose and Scope. Provide a concise statement of the scope and intended purpose of the ISP.

ISP Summary. Provide a concise description of the ISP sufficient to establish a clear understanding of the total scope, content, and organization of the material presented.

DID LOG001 - 1 of 4

Updating Process. Provide a description of the manner in which changes and revisions to the content of the ISP shall be developed, approved, and incorporated therein.

SECTION 2

SUMMARY OF SYSTEM CHARACTERISTICS

This section shall provide a summary of the system characteristics contained in the Specifications and shall provide an understanding of the significant characteristics of the system and the manner in which the system shall be employed in its intended operational environment. The requirements stated in this section shall refer to specific paragraph numbers of the Specification. This Section shall be formatted and contain the data shown below:

System/Equipment Description. Provide a brief description of functional and physical characteristics of the system and its major subsystems. Also, include a description of the physical and functional relationships between the contract end item and associated systems with which they shall interface when operational. Use block diagram(s) or other graphic means to support the text.

Operating Environment. Describe the operational environment. Include annual operating hours, duty cycles, maximum allowable downtime, life expectancy, environment, and other requirements, as applicable.

Availability Requirements. State the availability requirements contained in the System Specifications. Include predicted and demonstrate values when available.

Reliability Requirements. State the Reliability Requirements contained in the System Specifications. Include predicted and demonstrate values when available.

Quantitative Maintainability Requirements. State the Quantitative Maintainability Requirements contained in the System and

Configuration Item Specifications. Include requirements for test points, and built-in-test, manpower, and personnel constraints, and other requirements, as applicable.

Other Requirements. Summarize any other logistic-related requirements no listed above which are found in the System

Specifications.

SECTION 3

ILS PROGRAM MANAGEMENT, ORGANIZATION AND EXECUTION

This section shall provide a description of the overall process, involving both the Government and the Contractor that shall be used in managing and executing the contractual ILS program. Section 3 shall consist of two subsections and contain the data shown below.

SECTION 3A

MANAGEMENT AND ORGANIZATION

Contractor's Objectives, Policies, and General Management Procedures. State the objectives, policies, and general management procedures that relate to the ILS Program.

Contractor's ILS Organizational Structure. Describe the organizational structure that has been selected to accomplish the contractual ILS Program effort. Identify names, positions, functions, responsibilities, and authority of those responsible for satisfying the contractual ILS Program Requirements.

Subcontractor and Vendor Interface Management. List the major subcontractor's involved in the ILS Program, and describe the scope of ILS work assigned to each, the method of controlling the accomplishment of this work, and the organizational interfaces established with each subcontractor. Include a general description of the method of specifying ILS Requirements in vendor purchase orders and controlling the accomplishment of specific work and deliverables.

DID LOG001 - 2 of 4

Government ILS Organizational Interfaces. Describe the Government ILS organization and indicate the relationship with the contractor's ILS organization delineated in Section 3, Contractor ILS Organizational Structure, above.

SECTION 3B

DESIGN INTERFACE PLANNING AND REPORTING

In conjunction with the approved management system, this subsection shall contain a description of how the contractor shall accomplish, report, provide an audit trail for integration, and interface a formal design influence program. This subsection shall augment Section 3, ILS Program Management, Organization, and Execution. The design interface planning shall ensure that all logistics requirements and maintenance decisions made by the other contractually required system engineering specialties are input to and output from one another (system engineering specialties include, but are not limited to, the Design Program; the Safety Program;

the Standardization Program; LMI Program; and the Human Factors Program).

Contractor's Objective. Describe a design interface specialty, which provides for the cost effective integration design, development, test, and evaluation task required to progress from an operational need to the deployment and operation of a system/equipment by a user organization. Identify audit trail and reporting criteria.

Contractor's Approach. Establish a design interface and system engineering approach or process in accordance with existing and approved procedures, which provide for a logical sequence of events as activities and decisions transforming an operational need into a viable cost effective system.

Contractor's Integration. Describe for and ensure design interface/engineering specialty integration which establishes timely and appropriate intermeshing of all engineering, design, and management efforts, and disciplines, such as Reliability, Availability, and Maintainability, ILS, Value Engineering, Standardization, and Production, to control their influence on ILS Programs, cost effective design enhancement and system/equipment design. Identify audit trail and reporting criteria.

Contractor's Control and Reporting. Identify in-house reports emanating from the above elements. Identify the relationship of technical program planning to cost and schedule planning. Identify planned interface, specific task and management procedures that ensure design influence and contractual provisions are met, and that the relationship of ILS to design influence and system engineering is established, controlled, reported (i.e., Cost Performance Report (CPR) or other such vehicle), and balanced between performance, support, ownership requirements, life cycle cost, and system effectiveness.

SECTION 4

ILS PROGRAM TASKS

This section shall contain a description of how the contractor shall accomplish all logistics requirements identified in the ILSP that are specifically tasked by the program office. It shall clearly delineate any planned phased implementation of contractual tasks resulting from spiral development and deployment. For ILS program tasks not covered by separately deliverable plans, a detailed description shall be provided in this section. The plan shall include, but not limited to, the following areas:

Logistics Management Information. The contractor shall provide a detailed description of plans for the accomplishment of each logistics management information (LMI) tasks identified by the program office.

Technical Documentation. The contractor shall describe the management and preparation procedures for Commercial-Off-The-

Shelf (COTS) technical documentation, Commercially Available Software (CAS) technical documentation, existing government technical documentation, and for newly developed technical documentation. It shall address any intentions toward expanding any existing technical documentation to satisfy the requirements. This technical documentation information will be expanded further in the Manuscript and Validation Plan. The Manuscript and Validation Plan will be incorporated as Part II of the ISP.

Technical Support. The contractor shall describe its planned approach for providing technical assistance to the sites, second level software, and second level hardware engineering support and laboratory support during the spiral phases. It shall include the plan for transitioning the second level software and hardware responsibilities to AOS.

Deleted: Contractor’s Proposal for Training (CPT). The CPT will be incorporated as Part III of the ISP.¶

DID LOG001 - 3 of 4

SECTION 5

MILESTONE SCHEDULE

The Contractor shall provide a master milestone schedule to include all program milestones and ILS tasks. This chart should depict how the logistics tasks are related to the overall program schedule. This Section shall be formatted and contain the data shown below:

Master Milestone Chart. The Master Milestone Chart to include all program milestones; e.g., Physical Configuration Audit (PCA), Preliminary Design Review (PDR), Critical Design Review (CDR), Contractor and Government Tests, Prototype delivery, Reliability and Maintainability demonstration, etc.

ILS Program Milestone Chart. A milestone chart for events required to accomplish all required ILS tasks.

Support Element Milestone Chart. A milestone chart for the events required to accomplish all contractually required support element development efforts; e.g., technical publications, training efforts, provisioning effort.

SECTION 6

RELATED PLANS

This Section shall contain appropriate appendices, as related plans required for the ILS program effort. This Section shall be formatted and contain the data as shown below:

Related Plans. This Section shall reference the most version of all contractually required ILS Program Tasks; e.g., LMI Program, and all separately deliverable plans for all contractually required support element development efforts; e.g., Technical Manual Plan, Provisioning Plan, Training and Training Equipment Plan.

DID LOG001 - 4 of 4

1. TITLE 2. IDENTIFICATION NUMBER

Logistics Management Information Summaries DI-ALSS-81530/LOG002

3. DESCRIPTION / PURPOSE

3.1 The LMI Summaries consist of information that a requiring authority can use to perform logistics planning and analysis, assess design status, influence program decisions, and verify contractor performance meets system supportability requirements.

4. APPROVAL DATE (YYMMDD) 5. OFFICE OF PRIMARY RESPONSIBILITY 6a. DTIC APPLICABLE 6b. GIDEP APPLICABLE

AML-8000 N/A N/A

7. APPLICATION / INTERRELATIONSHIP

7.1 This Data Item Description (DID) contains the format and content preparation instructions for LMI. Summaries required by Worksheet 1 (Figure1) of MIL-PRF-49506, or some other requirements identification tool.

7.2 The delivery method (e.g., on-line access, tape, floppy, etc.) is outside the scope of MIL-PRF-49506 and must be addressed separately.

8. APPROVAL LIMITATION 9A. APPLICABLE FORMS 9b. AMBC NUMBER

10.1 Reference document. The applicable issue of the documents cited herein, including their approval dates, and dates of any applicable amendments, notices, and revisions shall be as specified in the contract.

10.2 Format. The formats for LMI Summaries are not dictated by MIL-PRF-49506, but are left to the discretion of the requiring authority and the contractor. The LMI data shall be delivered without restrictive legends and software that would limit the Government’s ability to copy/reproduce and edit/modify the LMI data using the electronic version

10.3 Content. Worksheet 1 (Figure1) of MIL-PRF-49506, or some other requirements identification tool contained in the contract, identifies the required LMI Summaries, desired information per LMI Summary, and associated guidance. The Data Product Worksheets (Figure 2, MIL-PRF-49506), or some other requirements identification tool contained in the contract, shall specify the selected data.

11. DISTRIBUTION STATEMENT

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

DID LOG002 - 1 of 10

Section 1

FAA Logistics Center

Logistics Management Information (LMI) Data Products Worksheet

System: __________________________________________

Data Deliverable: __LMI Data Product_________________ CDRL: _LOG002

Specific Instructions:

Data Product Format: Government _______ Contractor ____X____

Section 2 shows those data products defined by MIL-PRF-49506 the contractor shall deliver for the FAA Logistics Center to perform logistics planning functions. The following codes reflected in the “Select” column identify the conditions under which the data products shall be provided.

Select Code Explanation A As applicable B Packaging, bulk items C Commercial items only D Developmental items only E Support Equipment F First appearance items only L LRU items only M Packaging, common items N New “P” source code items N Nondevelopmental items only O “Ref” items only P All “P” source code items R Repairable items only S SRU items only T Registered support equipment only U Non-registered support equipment only X Data product required on all items Y National Stock Number (NSN) items

Other codes may be assigned as identified below.

Select Code Explanation

Additional data products not found in MIL-PRF-49506 but needed by the FAALC to perform logistics planning shall be delivered as listed in Section 3.

DID LOG002 - 2 of 10

Alternate Indentured Product Code (AIPC) Data product format modified. Use 2 positions, filled, left justified, beginning with “00” to represent the basic system.

Automatic Data Processing Equipment Code Calibration Interval E Commercial and Government Entity (CAGE) Code

X

CAGE Code - Additional Reference Number

(ARN)

A Used on “HB” record type.

CAGE Code - ARN Item A Used on “HB” record type.

CAGE Code - Support Equipment E End Item Acronym Code X Essentiality Code L Indenture Code X Attaching part/hardware Option 4 X Indentured Product Code (IPC) X Item Category Code X Item Name X Item Name Code X Mean Time Between Failure (MTBF) X National Stock Number and related data Y Federal Supply Classification Y National Item Identification Number Y Next Higher Assembly Provisioning List Item Sequence Number (NHA PLISN)

X

NHA PLISN Indicator X Precious Metal Indicator Code X Provisioning Contract Control Number X Provisioning List Item Sequence Number

(PLISN)

X

Provisioning Remarks X Quantity Per Assembly (Option 1) X Quantity Per End Item (Option 1) X Reference Number X Reference Number - Support Equipment E Reference Number (ARN) – Additional A Reference Number ARN Item X Reference Number Category Code X Reference Number Category Code - ARN X Reference Number Variation Code X Reference Number Variation Code - ARN X Same As PLISN O Shelf Life X Shelf Life Action Code X Source, Maintenance, and Recoverability Code (SMR Code)

X

Type of Price Code X Unit of Issue (UI) X Unit of Issue Conversion Factor X Unit of Issue/Unit of Measure Price X Unit of Measure (UM) X Usable On Code X

DID LOG002 - 3 of 10

ADDENDUM TO LOGISTICS MANAGEMENT INFORMATION (LMI)

DATA PRODUCTS WORKSHEET

A. LMI/PROVISIONING CORRESPONDENCE. All correspondence, Provisioning Technical Documentation (PTD), Logistics Management Information (LMI) data, etc., pertaining to spare or repair parts provisioning and related data items shall be addressed to the FAA Logistics Center (FAALC). The FAALC shall be the sole Government activity with which the Contractor shall interface on initial provisioning matters, unless specifically authorized by the Contracting Officer.

B. VENDORS/SUBCONTRACTORS. When the prime Contractor buys end articles or a portion thereof from a vendor or subcontractor or subcontracts for development of LMI or provisioning data, the Contractor shall impose upon its vendor(s) and subcontractor(s) the applicable requirements, procedures, terms, conditions, and data requirements stated in this addendum, including the applicable portions of the LMI Data Products Worksheet and the Statement of Work. The inclusion of the requirement for such data on Contractor's subcontracts/purchase orders to its vendor(s) or subcontractor(s) shall not relieve the prime Contractor’s obligation to ensure timely delivery of the required PTD and LMI data. If the Government and Contractor concur, the vendor(s) or subcontractor(s) may provide the data required by contract directly to the Government. The Government may not direct that vendor or subcontractor LMI, PTD, or EDFP be delivered direct to the Government. If the Government concurs in direct delivery, the prime Contractor continues to be responsible for timely delivery of data.

C. LMI AND PROVISIONING GUIDANCE CONFERENCES. The Contractor shall host and support a LMI Guidance Conference and a Provisioning Guidance Conference within the time frame(s) specified in the Statement of Work. These Conferences are normally held concurrently but may, in some cases, be held independently. Any subcontractor(s) which will be providing LMI or provisioning efforts on behalf of the prime Contractor should be present at the appropriate Guidance Conference.

D. PROVISIONING AND SUPPLY SUPPORT CONFERENCES. The Contractor shall host and support Provisioning and Supply Support Conferences in accordance with the Statement of Work. Any subcontractor(s) involved in the LMI or provisioning efforts on behalf of the prime Contractor should be present at the appropriate conference. At the Provisioning Conference(s) the Contractor shall provide the following data and services:

1. Provisioning Data.

(a) Drawings. One complete set of drawings approved by the Government during the physical configuration audit

(PCA), both proprietary and non-proprietary, shall be available for use by the Government as reference material.

(b) AN-MS Standards. One set of applicable AN-MS Standards shall be available at the Provisioning Conference.

(c) Manuals. The Contractor shall provide manufacturer or commercial manuals. All publications prepared and printed without regard to Government format and outline, but which include a parts list, will be acceptable as a manufacturer or commercial manual for the purpose of this requirement. This requirement applies only too available manuals for the end item or components thereof. No manuals will be developed to satisfy this requirement. Commercial manuals shall satisfy the requirements for EDFP.

2. Provisioning Services.

(a) The Contractor shall make available for the duration of the Provisioning Conference all equipment(s) on contract.

The Contractor shall also furnish personnel and tools necessary to disassemble the equipment(s) to the extent required by the Government provisioning team.

(b) The Contractor shall furnish facilities with adequate accommodations for the Government provisioning team and for Contractor personnel. The Government will advise the Contractor as to the number of attending Government representatives prior to the Provisioning Conference.

(c) The Contractor shall furnish a representative familiar with the provisioning documentation and a qualified engineering representative.

(d) The Contractor shall provide minutes of the Provisioning Conference and a summary of all action items.

E. GENERAL CONFERENCES. General conferences may be held at various times during the life of the contract, at the Government's discretion, for the purpose of resolving provisioning and/or supply support problems or issues.

DID LOG002 - 4…