Attach J.02 CDRLs and DIDs _Amend 00002.pdf

Attachment J.2

Contract Data Requirements List (CDRL) and Data Item Description (DID)

CDRL/DID Index

CDRL TITLE DID

L001 Integrated Support Plan L001

L002 RESERVED L002

L003 Contracting Depot Logistics Support (CDLS) Tracking, Trending and Cost Reporting

L003

L004 Support Equipment Candidate List L004

SIR 693KA8-20-R-00008

CDRL INSTRUCTIONS

A. Contract Line Item No. Contract Line Item Number (CLIN) associated with this Contract Data

Requirements List (CDRL).

B. Exhibit. Exhibit identifier for this CDRL item.

C. Category. TDP, TM, or Other.

D. System/Item. System, item, project designator or name, or title of services being acquired that the data will support.

E. Contract/PR No. Procurement Instrument Identification Number (PIIN) (i.e., the contract number, the Purchase Request (PR) number, the Screening Information Request (SIR) number, or other appropriate designator.

F. Contractor. Contractor’s name.

G. Prepared by. Preparer’s organization responsible for preparing the CDRL.

H. Date. Date the form was prepared.

I. Approved by. Office responsible for approving the CDRL. The approving official’s signature appears on the last page of exhibit.

J. Date. The date the CDRL was approved.

1. Data Item No. The 4-character Exhibit Line Item Number (ELIN). The first position consists of the exhibit identifier and the remaining positions are assigned sequentially.

2. Title of Data Item. The title of the Data Item Description (DID) cited in item 4.

3. Subtitle. Further identification of the data item to supplement the title, if required.

4. Authority (Data Acquisition Document No.) DID identification number where detailed preparation instructions are provided.

5. Contract Reference. The specific paragraph number of the applicable contractual document that contains the tasking that generates a requirement for the data item. Normally, this will be a Statement of Work (SOW) paragraph.

6. Requiring Office. The technical office having responsibility for ensuring the technical adequacy of the data.

7. FAA Acceptance Form 256 Required.

8. APP Code. Identification, by entry of an “A,” of a requirement for advance written approval prior to final distribution of an item of data. An “A” in this item indicates that one or more draft submittals are required. Item 14 will show length of turn-around time for the Contractor to resubmit the data after Government approval/disapproval has been issued.

9. Distribution Statement Required.

10. Frequency. The frequency of data submittal. Entries in this item are explained in Table 1. If the data is of a recurring type, it is to be submitted at the end of the reporting period established in this item unless otherwise indicated in item 14.

11. As of Date. Date for cutting off collection of the data. If the data is to be submitted multiple times, a numeral will be entered to indicate the number of calendar days prior to the end of the reporting period, established in item 10, that data collection will be cut off. For example, “15” would place the “as of date” for the data at 15 days before the end of the month, quarter, or year, depending upon the frequency established in item 10; a “0 or blank” would place the “as of” date at the end of each month, quarter, etc.

12. Date of First Submission. Due date for initial data submission. This is normally the postage date or date the data is delivered to the Contracting Officer or keyed to a specific event or milestone, using a code from Table 2.

13. Date of Subsequent Submission. Due date(s) for subsequent data submission(s), if data is to be submitted more than once. If submittal is constrained by a specific event or milestone, the constraint will be given using a code from Table 2.

14. Remarks. Contains all pertinent information not specified elsewhere and any amplification of other items on this format (e.g., DID tailoring, approval criteria and authority, inspection and acceptance clarification, distributions statements, specific submission instructions, explanation of reproducible copy and delivery requirements, alternative medium for delivery of the data item, etc.)

15. Distribution. Addressees and the number of draft and final copies (regular or reproducible) to be provided to each. FAA facility designator and/or office symbols/codes may be used; however, an explanation of these will be provided in the Addressee Listing. When reproducible copies (e.g., magnetic diskettes/tape, vellum, negative, etc.) are required, an explanation will be provided in item

14. If deferred delivery is required, amplification will be given in item 14.

CODE

ANNLY

ASREQ

BI-WE

DAILY

MTHLY

OTIME

R/ASR

WEKLY

See Item #14

FREQUENCY

Table 1. Data Submittal Frequency Codes

CODE

FREQUENCY

Annually As required Every two weeks Daily Monthly One time (does not include draft submissions) Revisions as required Weekly

ASGEN

BI-MO

CP/RQ

DFDEL

ONE/R

QRTLY

SEMIA

“N”TIME

As generated Every two months Change pages as required Deferred delivery One time with revisions Quarterly Every six months Multiple separate submittals (2time, 3time, etc.)

Requirement is described in item #14. Used in lieu of other codes where such are inadequate to define requirement, or used in addition to other codes requiring amplification in item #14.

Table 2. Data Submission Codes Code

ASGEN

DFDEL

“N”DACM

“N”DARC

NLT EOM

See item #14

Definition As generated Deferred delivery Days after contract modification Days after receipt of comments No later than End of month

Code Definition ASREQ As required “N”DAC Days after contract award “N”DARP Days after reporting period “N”DTC Days after test completion EOC End of contract EOQ End of quarter

Use to indicate requirement is described in item 14. Used in lieu of other codes where such are inadequate to define requirement or used in addition to other codes when amplification is included in item 14.

The “N” is assigned a value indicating the number of days, e.g., 30 DAC

16. Total. Total number of draft and final (regular/reproducible) copies required.

17. Price Group. Not used.

18. Estimated Total Price. Not used.

DD FORM 1423-1, FEB 2001 PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages

Adobe Professional 8.0

17. PRICE GROUP

18. ESTIMATED

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.

0011, 1011, 2011, 3011, 4011

B. EXHIBIT C. CATEGORY:

TDP TM OTHER Contract Base Award

D. SYSTEM/ITEM

DC BUS Logistics

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

L001

2. TITLE OF DATA ITEM

Integrated Support Plan (ISP)

3. SUBTITLE

N/A

4. AUTHORITY (Data Acquisition Document No.)

DID L001

5. CONTRACT REFERENCE

SOW Section C.3.4.1.1

6. REQUIRING OFFICE

NAS Power Systems Group, AJW-22

7. DD 250 REQ

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

Initial/As Revised

12. DATE OF FIRST SUBMISSION

See 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

See 16 Draft Final

Reg Repro

16. REMARKS

The Contractor must submit the ISP, or the applicable portions of their ISO 9000 Series documentation, or a copy of internal documentation that supports both the scope and intent of the ISP.

1. Block 12 - Date of First Submission. The Contractor must provide the first submission of the ISP not later than 21 working days after award. The FAA will and comment or approve the ISP, ISO 9000 Series documentation, or internal corporate documentation within 30 calendar days after receipt from the Contractor.

2. Block 13 - Date of Subsequent Submissions: The Contractor must update and resubmit the ISP or substituted corporate documentation, as revisions occur or within 10 calendar days of FAA comment.

3. Block 14(a) - Addressee. The Contractor must provide copies of the ISP, in Contractor format, to the Contracting Officer and Contracting Officer's Representative.

4. Block 14(b) - Copies. The Contractor must provide the FAA with an electronic copy.

See Block 16*

15. TOTAL 0 0 0

G. PREPARED BY

Jaron Mengel

H. DATE

10/22/19

I. APPROVED BY

AJW-222

J. DATE

10/22/19

17. PRICE GROUP

18. ESTIMATED

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.

0011, 1011, 2011, 3011, 4011

B. EXHIBIT C. CATEGORY:

TDP TM OTHER Contract Base Award

D. SYSTEM/ITEM

DC BUS Logistics

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

L003

2. TITLE OF DATA ITEM

Contractor Depot Logistics Support (CDLS) Tracking, Trending, and Cost Reporting

3. SUBTITLE

N/A

4. AUTHORITY (Data Acquisition Document No.)

DID L003

5. CONTRACT REFERENCE

SOW Section C.3.5.3

6. REQUIRING OFFICE

NAS Power Systems Group, AJW-22

7. DD 250 REQ

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

See 16

12. DATE OF FIRST SUBMISSION

See 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE 11. AS OF DATE

See 16

13. DATE OF SUBSEQUENT

SUBMISSION

See 16 Draft

Final

Reg Repro

16. REMARKS

The Contractor must submit the CDLS Tracking, Trending, and Cost Reporting report in accordance with the SOW.

1. Block 10 - Frequency. The Contractor must submit the report Quarterly and Annually.

2. Block 11 - As of Date. The Contractor must submit the report at the end of each quarter, and at the end of each year of performance.

3. Block 12 - Date of First Submission. The Contractor must submit the Quarterly report not later than 10 calendar days after the end of each quarter.

4. Block 13 - Date of Subsequent Submissions: The Quarterly report must be a cumulative.

The Contractor must submit the Annual report not later than 20 calendar days after the end of each year of performance.

5. Block 14(a) - Addressee. The Contractor must provide copies of the CDLS Tracking, Trending, and Cost Reporting report, in Contractor format, to the Contracting Officer and Contracting Officer's Representative.

6. Block 14(b) - Copies. The Contractor must provide the FAA with an electronic copy.

See Block 16*

15. TOTAL 0 0 0

G. PREPARED BY

Jaron Mengel

H. DATE

10/22/19

I. APPROVED BY

AJW-222

J. DATE

17. PRICE GROUP

18. ESTIMATED

CONTRACT DATA REQUIREMENTS LIST

(1 Data Item)

Form Approved OMB No. 0704-0188

The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to the Department of Defense, Executive Services Directorate (0704-0188). Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please do not return your form to the above organization. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.

A. CONTRACT LINE ITEM NO.

0011C, 1011C, 2011C, 3011C, 4011C

B. EXHIBIT C. CATEGORY:

TDP TM OTHER Contract Base Award

D. SYSTEM/ITEM

DC BUS Logistics

E. CONTRACT/PR NO. F. CONTRACTOR

1. DATA ITEM NO.

L004

2. TITLE OF DATA ITEM

Support Equipment Candidate List (SECL)

3. SUBTITLE

N/A

4. AUTHORITY (Data Acquisition Document No.)

DID L004

5. CONTRACT REFERENCE

SOW Section C.3.4.2.4

6. REQUIRING OFFICE

NAS Power Systems Group, AJW-22

7. DD 250 REQ

N/A

9. DIST STATEMENT

REQUIRED

10. FREQUENCY

As Equipment Changes

12. DATE OF FIRST SUBMISSION

See 16

14. DISTRIBUTION

a. ADDRESSEE

b. COPIES

8. APP CODE 11. AS OF DATE 13. DATE OF SUBSEQUENT

SUBMISSION

See 16 Draft Final

Reg Repro

16. REMARKS

The Contractor must submit the Support Equipment Candidate List (SECL) report in accordance with the SOW.

1. Block 12 - Date of First Submission. The Contractor must submit the SECL not later than 21 working days after contract award and must consist of DC BUS equipment listed in Section B. The FAA will review, comment, approve and/or disapprove.

2. Block 13 - Date of Subsequent Submissions: The Contractor must update and submit the SECL not later than 90 calendar days prior to revisions to existing DC BUS models/units, and when the Contractor introduces a new DC BUS product line.

3. Block 14(a) - Addressee. The Contractor must provide copies of the SECL, in Contractor format, to the Contracting Officer and Contracting Officer's Representative.

4. Block 14(b) - Copies. The Contractor must provide the FAA with an electronic copy.

See Block 16*

15. TOTAL 0 0 0

G. PREPARED BY

Jaron Mengel

H. DATE

10/22/19

I. APPROVED BY

AJW-222

J. DATE

DATA ITEM DESCRIPTION

1. TITLE:

INTEGRATED SUPPORT PLAN (ISP)

2. IDENTIFICATION No

DI-FAA-L001

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 Logistic Support (ILS) Plan.

3.2 The ISP consists of the following sections:

1. Introduction.

2. Summary of System Characteristics.

3. ILS Program Management, Organization, and Execution.

4. Milestone Schedules.

3.3 The Contractor may demonstrate compliance with the

requirement to provide ISP by providing the Government with either; an ISP, the applicable portions of their ISO 9000 series certification documentation, or a copy of internal corporate documentation that support both the scope and intent of the ISP as described in this paragraph and others within this DID.

3.4 The ISP or equivalent documentation is used by the

Government 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

10/22/2019

5. RESPONSIBLE OFFICE

NAS Power Services Group

6. REFERENCE SOW

Section C.3.4.1.1

7. APPLICATION/INTERRELATIONSHIP

This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific task requirements as delineated in the contract.

8. PREPARATION INSTRUCTIONS

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

8.2 General. The ISP or Contractor's ISO series 9000 documentation must document the Contractor's management plans for gathering and analyzing data; management, control, and execution; integration and interface of the ILS Program Task(s) delineated in the contract. The Contractor's management plans must demonstrate that the new system or equipment, when fielded, will satisfy all supportability criteria.

8.3 Format and Content. Contractor format may be used for either their ISO 9000 series documentation or internal corporate documentation. The format and content requirements for the ISP must be as follows:

8.3.1 Organization and Preparation. The ISP must be organized into four (4) major sections. The specific content of each major section must be in accordance with the requirements set forth herein. The ISP must be submitted in electronic copy.

8.3.2 Sections. The ISP must contain all sections identified in this paragraph even if there are no data or narratives required for a section or element (e.g., if there are no tasks, requirements, or other standards, the Contractor must enter "NOT APPLICABLE" and state the reason(s), e.g., "NOT REQUIRED BY CONTRACT".

INTEGRATED SUPPORT PLAN (ISP) SECTION 1 - INTRODUCTION

SECTION 1 - Introduction. This section must identify the ISP Requirements as specified in the Statement of Work (SOW). This section must be formatted and contain the data as shown below:

Purpose and Scope. Provide a concise statement on the scope and intended purpose of the ISP as the document for managing and executing the contractual ILS Program.

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.

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

INTEGRATED SUPPORT PLAN (ISP) SECTION 2 - SUMMARY OF SYSTEM CHARACTERISTICS

SECTION 2 - Summary of System Characteristics. This section must be a summary of the details contained in the Contractor's System Specifications and must provide an understanding of the significant characteristics of the system and the manner in which the system must be employed in its intended operational environment. This Section must be formatted and contain the data as shown below:

System/Equipment Description. Provide a brief description of functional and physical characteristics of the system and its major subsystems for each model and type of system provided. Also, include a description of the physical and functional relationships between the contract end item and associated systems with which they must 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.

8. PREPARATION INSTRUCTIONS Continued:

INTEGRATED SUPPORT PLAN (ISP) SECTION 2 - SUMMARY OF SYSTEM CHARACTERISTICS continued:

Availability Requirements. State the operational availability as contained in the Contractor's System Specifications.

Include predicted and demonstrate values, when available.

Reliability Requirements. State the reliability as contained in the Contractor's System Specifications. Include Mean time Between Failure (MTBF) and Mean time To Repair (MTTR). Include predicted and demonstrate values when available.

Quantitative Maintainability Requirements. State the Quantitative Maintainability Requirements contained in the Contractor's System Specifications. Include requirements for test points, and built-in- test, manpower and personnel constraints, and other requirements, as applicable.

Maintainability Design Criteria. Summarize the Maintainability Design Criteria developed in response to the Maintainability Requirements.

Other Requirements. Summarize any other logistic-related requirements no listed above.

INTEGRATED SUPPORT PLAN (ISP) SECTION 3 - ILS PROGRAM MANAGEMENT, ORGANIZATION, AND

EXECUTION

SECTION 3 - ILS Program Management, Organization, and Execution. This Section must provide a description of the overall process, involving both the FAA and the Contractor that must be used in managing and executing the contractual ILS Program. This Section must be formatted and contain the data as shown below:

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.

Sub-Contractor 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.

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

INTEGRATED SUPPORT PLAN (ISP) SECTION 4 - MILESTONE SCHEDULES

SECTION 4 - Master Milestones. This section must contain the Master Milestones as planned and scheduled for the ILS effort. This section must be formatted and contain the data shown below:

Master Milestone Chart. The Master Milestone Chart to include all program milestones and all ILS Program Tasks as defined in the NAILS CDRLs/DIDs.

1. TITLE

CONTRACTOR DEPOT LOGISTICS SUPPORT (CDLS)

TRACKING, TRENDING, AND COST REPORTING

2. IDENTIFICATION NUMBER

DI-FAA-L003

3. DESCRIPTION/PURPOSE

3.1 The CDLS Report is used to collect data from the logistic support contractor.

3.2 The data is used to track field and second level assistance requirements and parts usage. The cost data is also used to evaluate contract performance, identify the magnitude and impact of actual or potential problem areas causing significant cost and schedule variances and provide timely program status information.

4. APPROVAL DATE

10/22/2019

5. RESPONSIBLE OFFICE

NAS Power Services Group

6. REFERENCE

SOW Section C.3.5.3

7. APPLICATION/INTERRELATIONSHIP

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

7.2 This DID is applicable when a contractor is required to perform logistic support.

8. PREPARATION INSTRUCTIONS

8.1 Format and Content. The report must consist of a cover letter and spreadsheet data on supply support and technical assistance support. The cover letter must display the report title, date, the period covered by the report, the current contract number, and the preparing and approving official's signature block and signature. This information must be provided in Electronic Media per the CDRL. Electronic media and spreadsheet format will be approved during the Logistics Guidance Conference.

8.1.1 Supply Support Required Data

Column A: SITE. The three (3) letter FAA Site Designator, or the actual FAA equipment name and city of the FAA Site goes in this block.

Column B: CDLS P/N. If applicable, this is the part number assigned by the CDLS to track Line Replaceable Units (LRU’s) made by the CDLS contractor and any Original Equipment Manufacturers (OEM) parts for consistency in ordering and tracking.

Column C: OEM P/N. This is the part number used by the Original Equipment Manufacturer to identify OEM LRU’s.

Column D: OEM MFGR. Noun name of the OEM manufacturer. (If the CDLS contractor manufactures parts for the system under CDLS, he is also an OEM manufacturer)

Column E: C/E. Abbreviations for “Consumable”/“Expendable”. Enter the single letter code to identify the type of LRU.

Column F: NOMENCLATURE. This is the noun name associated with the CDLS contractor and OEM LRU part numbers.

Column G: END ITEM SUBASSEMBLY USED ON. The LRU to be replaced is installed in a “Subassembly” which ultimately goes into the “System End Item”.

Column H: DATE ORDER RECV’D @contractor’s. Date the order was received from the FAA Logistics Center (FAALC) CLS Desk.

Column I: FAALC VOUCHER NUMBER. This is an eight (8) digit number assigned by the CDLS Desk at the FAALC to track LRU’s being ordered by the FAA Sites.

Column J: PRI. This is the priority assigned by the FAA site, when the LRU is ordered. FAA priorities are defined in SOW 3.6.3.7.

Column K: DATE NEW LRU SENT TO SITE. This is the date that the CDLS actually sends the LRU to the FAA Site, or has the LRU drop shipped to the FAA Site by an OEM Vendor.

Column L: QTY SHIPPED. Total quantity of the individual LRU that has been ordered by an FAA Site, and then shipped to that FAA Site.

Column M: SHIP MODE. Type of shipping mode used by the CDLS to ship the LRU to the FAA Site. (FEDEX, UPS, etc.)

Column N: BILL OF LADING NUMBER. Shipping Companies (FEDEX, UPS, etc.) tracking number.

Column Q: LRU DISCREPANCY. If available, list the LRU discrepancy originated by the FAA Site.

Column T: COST OF ITEM. Cost to repair or replace an LRU that is being returned to CLS Stock as ready for issue.

8.1.2 Technical Assistance Data This section contains information concerning man-hour accounting for contractor personnel at each maintenance site (this includes Travel, On-site and In-plant Technical Assistance) for the period being reported. This report must be in contractor format, as approved by the FAA. It must be delivered in “Electronic Media.” Data points and contractor format must be submitted by the contractor at the Logistics Guidance Conference for FAA approval.

8.1.3 Monthly CDLS Cost Report. CDLS cost reporting will be used by the FAA Program Manager to evaluate contract performance, identify the magnitude and impact of actual and potential problem areas causing significant cost and schedule variances. Recommended data points and contractor format must be submitted by the contractor at the Logistics Guidance Conference for FAA approval.

8.1.4 Annual Consolidated/Cumulative Maintenance and Cost Report. The Contractor must submit an Annual Consolidated/Cumulative Report based on the Monthly reporting requirements of this DID, and must be in the same format as approved by the FAA for the monthly reporting.

1. TITLE

SUPPORT EQUIPMENT CANDIDATE LIST (SECL)

2. IDENTIFICATION NUMBER

DI-FAA-L004

3. DESCRIPTION/PURPOSE

The recommended Support Equipment Candidate List identifies the test parameter requirements for maintenance, test, alignment, and calibration to support maintenance during the operational lifecycle of the DC BUS. This list also identifies the unique and special tools, materials, and test equipment required to support maintenance. This recommended requirements list provides the basis for the using activity to determine if existing general purpose test equipment can be utilized. The unique and special tools, materials, and test equipment list provides the basis for the acquisition and subsequent support of each new item

4. APPROVAL DATE

10/22/2019

5. RESPONSIBLE OFFICE

NAS Power Services Group

6. REFERENCE

SOW Section C.3.4.2.4

7. APPLICATION/INTERRELATIONSHIP

This data item contains the format and content preparation instructions for the data product generated by the specific and discrete task requirement delineated in the contract.

8. PREPARATION INSTRUCTIONS

The recommended Support Equipment Candidate List includes the support equipment, tools, and materials, including computer maintenance and support hardware and software required to maintain the system or equipment at the level of maintenance identified in the contract. The recommended support equipment list must contain two separate parts, a general purpose support equipment list and a special purpose support equipment list.

General purpose support equipment recommendations. This part includes the generic support equipment that is commercially available and can normally be used for more than one purpose. (Sample format Figure 1.)

Special purpose support equipment recommendations. This part lists unique jigs, fixtures, and special support equipment, including single source and proprietary items. (Sample format Figure 2.)

Item Information. Provides the following information for each item of recommended support equipment on the list. Pertains to both general and special purpose recommended support equipment lists.

System or equipment under test.

Identifies the application of a recommended test item, system, or component. Items subject to test must be identified by the following:

Manufacturer/Government Entity (CAGE) code.

Model/Part Number Item Name

Parameters to be tested.

Describe the test, adjustment, or calibration to be performed. Be as general as possible, including only absolute requirements.

This information reflects the actual characteristics required by the prime equipment rather than the characteristics of the particular model of support equipment recommended. Include the following:

Nature of test Value or range of values Tolerance of these values

8. PREPARATION INSTRUCTIONS continued… General purpose support equipment List the generic name for each item, such as, oscilloscope, voltmeter, hydrometer, etc.

Special purpose support equipment When a specific item of support equipment is recommended, include the Manufacturer/CAGE code, the Model/Part Number, and the item name. Include a statement justifying the selection of each item of special purpose support equipment.

Include the unit price for each of these items.

Quantity On-Site Record the number of each support equipment item required to perform the test described at the local site.

SAMPLES FORMATS

GENERAL PURPOSE SUPPORT EQUIPMENT

SE ITEM

NO

SYSTEM/

EQUIPMENT

UNDER TEST

PARAMETERS

TO BE TESTED

RECOMMENDED

TEST

EQUIPMENT

QTY ON SITE

1 ACCUDATA

117 DC

AMPLIFIER

(0BC28)

30 HZ - 20 KHZ

@ 1 VRMS +/- 5%

BANDPASS

RMS VOLTMETER 1

2 SAME 10 V P-P FROM

30 HZ - 20 KHZ

VISUAL

DISTORTION

OSCILLOSCOPE 1

3 SAME DC PWR SUPPLY

5 VDC +/- 0.01V

10 VDC +/- 1V

14.5 VDC +/- 0.1V

W/100 KOHM MIN

INPUT

IMPEDANCE

DC VOLTMETER 1

4 GENERAL/

MULTIPLE USE

AC LINE

CORD

CONTINUITY

MULTIMETER 1

FIGURE 1, Sample Format

SPECIAL PURPOSE TEST EQUIPMENT

SE

ITEM

NO

SYSTEM/

EQUIPMENT

UNDER TEST

PARAMETERS

TO BE TESTED

RECOMMENDED

SUPPORT

EQUIPMENT

QTY ON SITE

1 85-02277-002 (33875)

HEATSINK

ASSY

RECTIFIER

INSTALLATION

ADJUSTMENT

ALIGNMENT

TOOL GE

118C8388P1

2 441C RECORDER

PRECISION ECHO

(54089)

TAPE TENSION

ADJUSTMENT

TAPE

TENSION

GAGE

T2-H20-1

TENTEL

(54632)

3 HP-3964A

(28580)

RECORDER

POWER

REGULATION 85-135

VAC

TRANSFORMER

VARIABLE MT3A

GENRAD (24655)

Justification statement:

1. This alignment tool is specifically designed for replacement of the rectifier and if not used will cause early failure of the rectifier due to insufficient heat transfer via the heat sink. No other tool available meets the requirements. Unit cost is

$XX.XX EA

2. This is the only known gage that will accurately measure tape tension for this adjustment. Unit cost $XXX.XX EA

3. No other transformer available meets requirements. Unit cost is $XXX.XX EA

FIGURE 2, Sample Format