1. CONTRACT ID CODE P AGE OF PAGES
AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT
2. AMENDMENT/MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/P URCHASE REQ. NO. 5. P ROJECT NO.(If applicable)
6. ISSUED BY CODE N00421 7. ADMINISTERED BY (If other than item 6) CODE
NAVAL AIR WARFARE CENTER AD (PAX)
CODE 126.96.36.199.2 BLDG 441 See Item 6
21983 BUNDY ROAD
PATUXENT RIVER MD 20670
8. NAME AND ADDRESS OF CONT RACT OR (No., Street, County, State and Zip Code) X 9A. AMENDMENT OF SOLICIT AT ION NO.
X 9B. DAT ED (SEE IT EM 11)
10A. MOD. OF CONT RACT /ORDER NO.
10B. DAT ED (SEE IT EM 13)
CODE FACILIT Y CODE
11. T HIS IT EM ONLY APPLIES T O AMENDMENT S OF SOLICIT AT IONS
X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.
Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:
(a) By completing Items 8 and 15, and returning copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;
or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE
RECEIVED AT THE P LACE DESIGNATED FOR THE RECEIP T OF OFFERS PRIOR TO THE HOUR AND DATE SP ECIFIED MAY RESULT IN
REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter,
provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.
12. ACCOUNT ING AND APPROPRIAT ION DAT A (If required)
13. T HIS IT EM APPLIES ONLY T O MODIFICAT IONS OF CONT RACT S/ORDERS.
IT MODIFIES T HE CONT RACT /ORDER NO. AS DESCRIBED IN IT EM 14.
A. T HIS CHANGE ORDER IS ISSUED PURSUANT T O: (Specify authority) T HE CHANGES SET FORT H IN IT EM 14 ARE MADE IN T HE
CONT RACT ORDER NO. IN IT EM 10A.
B. T HE ABOVE NUMBERED CONT RACT /ORDER IS MODIFIED T O REFLECT T HE ADMINIST RAT IVE CHANGES (such as changes in paying
office, appropriation date, etc.) SET FORT H IN IT EM 14, PURSUANT T O T HE AUT HORIT Y OF FAR 43.103(B).
C. T HIS SUPPLEMENT AL AGREEMENT IS ENT ERED INT O PURSUANT T O AUT HORIT Y OF:
D. OT HER (Specify type of modification and authority)
E. IMPORT ANT : Contractor is not, is required to sign this document and return copies to the issuing office.
14. DESCRIPT ION OF AMENDMENT /MODIFICAT ION (Organized by UCF section headings, including solicitation/contract subject matter
The purpose of this amendment is 1)Revise the POC listed under Section L "Instructions, Conditions, and Notices to Bidders", under 4.0
Proposal Submission 2) Update Section C "Specifications and Descriptions" to include changes per the Questions and Answ ers listed in
Section A of this amendment.
Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.
15A. NAME AND T IT LE OF SIGNER (T ype or print) 16A. NAME AND T IT LE OF CONT RACT ING OFFICER (T ype or print)
15B. CONT RACT OR/OFFEROR 15C. DAT E SIGNED 16B. UNIT ED ST AT ES OF AMERICA 16C. DAT E SIGNED
(Signature of person authorized to sign) (Signature of Contracting Officer)
EXCEPT ION T O SF 30 30-105-04 ST ANDARD FORM 30 (Rev. 10-83)
APPROVED BY OIRM 11-84 Prescribed by GSA
FAR (48 CFR) 53.243
Page 2 of 27
SECTION SF 30 BLOCK 14 CONTINUATION PAGE
SUMMARY OF CHANGES
SECTION A - SOLICITATION/CONTRACT FORM
QUESTIONS FOR RFP N00421-05-R-0118
Questions Received 01/02/2009-01/06/2009
Overhaul of T700-GE-401/401C Turbo Shaft Engines
Cold Section Modules, and Power Turbine Modules
1. On page 7 of the subject RFP (para 2.0 "Applicable Documents), there is a reference to
AMCOM Engineering Directive (AED-P3441). It is our understanding that this document has been
cancelled. If this is correct, we request that the reference to this document be removed from the
RFP via an amendment.
Answer: Yes, Ch 8 to the DMWR has changed. The change occurred after the re-compete
commenced. The AED was added as appendix L. Appendix L still only applies to the T700-GE-401
and T700-GE-401C engines and modules. The Enhanced Engine Performance Work scope MEO
P3863 for the T700-GE-401 and T700-GE-401C listed in Appendix will be added to Applicable
Documents via amendment.
2. On page 9 of the subject RFP, item 3.4 talks about ensuring external components are tested and/
or repaired (from engines) as necessary. Our question is:
The DMWR for the engine has a matrix for functional test of these external components like the
HMU, AI valve, etc. during engine test. Is this functional test (during actual engine testing) an
acceptable way to test the components for the Navy?
Answer: Yes this functional test is acceptable, provided if component fails it is repaired. The intent
of this paragraph is, should the component fail functional test it will be repaired with no additional
cost. Functional testing verbiage will be added via amendment.
3. Page 8 3.0 Requirements states that each whole engine consists of the following:
A whole engine also would require a complete hot section (GG rotor/stator, stg 1 nozzle, OBP seal
and combustion liner) and a complete accessory module package. When we receive a whole engine
will it only be the cold section and PT module?
Answer: No, the engine will ship complete with all the internal components (GG rotor/stator, Stg 1
nozzle OBP seal and combustion liner). External components include accessory gearbox, HMU,
4. Page 16 Appendix B. Government furnished equipment
The list of furnished equipment is not sufficient to test both 401 and 401C Cold sections and PT
modules. For instance:
- There is no GG rotor/stator, stg 1 nozzle, OBP seal, combustor for either the 401 or 401C
- There is no 401 cold section or PT module
Page 3 of 27
- There is not a complete set of LRU's listed for the gearbox
Our assumption is the Navy will supply all the required test equipment to allow testing of both 401
and 401C cold sections and PT modules. If that is not the case we need to know so we can price in
the missing equipment needs.
Answer: Updates to the GFE list have been added via amendment.
5. Page 47 4.0 Proposal Submission
Reference to volume 2. Should this be volume 3 ("Past Performance")?
Answer: Yes, correction should be Volume 3, correction will be made via amendment.
6. Page 48 part B specific instructions item iv. references volume 6 - this should be volume 5,
Answer: Yes, correction should be Volume 5, correction will be made via amendment.
7. Page 51 3.1 General references technical volume 3 - this should be volume 2, correct ?
Answer: Yes, correction should be Volume 2, correction will be made via amendment.
8. After reading clause 252.239-7001 (Information Assurance Contractor Training And
Certification) and DoD 8570.01-M, it is our understanding that this clause applies to contracts
where the contractor's personnel would be performing an Information Assurance function. We
believe this to mean performing job responsibilities that have to do with protecting the DoD's
computer network, information systems, and other IT assets such as servers, routers, etc. It is our
position that this requirement would not be applicable to the scope of work set forth in the subject
RFP. If you concur, we request that an amendment to the solicitation be issued to remove DFARS
Answer: The clause will remain in the RFP, access to government databases will be needed.
NO EXTENSION WILL BE GIVEN AS A RESULT OF AMENDMENT 0002 TO RFP
Page 4 of 27
SECTION C - DESCRIPTIONS AND SPECIFICATIONS
The following have been modified:
STATEMENT OF WORK (SOW)
COMMERCIAL REPAIR OF THE
USN/USMC T700-GE-401/401C ENGINES, COLD SECTION MODULES, AND POWER
No Department of Defense Contract Security Classification Specification (DD254) level for this contract.
CERTIFICATE OF CONFORMANCE
The Contractor shall provide in writing a certificate of conformance with each delivery stating that
the item supplied is in accordance with the specifications contained in the statement of work of this
contract. The certificate of conformance shall be consistent with Contractor’s commercial practice
for sign-off of FAA Form 8130 or its equivalent.
This scope of work is for the minimum repair requirements for Standard Depot Repair of United States Navy (USN)
and United States Marine Corps (USMC) T700-GE-401/401C Turboshaft Engines, Cold Section Modules (CSMs)
and Power Turbine Modules (PTMs). The intent is to provide cost-effective, on-time availability of Ready-For-
Issue (RFI) USN and USMC T700-GE-401/401C Engines, CSMs, and PTMs to meet National Military Strategy.
The Contractor shall be a FAA certified repair station for CT7/T700 series engines and modules or its equivalent.
The term “shall” is used throughout this SOW to indicate mandatory constraints. The term “may” indicates optional
1.1 Historical Background
The T700-GE-401/401C Engine is used in the USN’s H-60 Seahawk and USMC H-1 Helicopter’s (Gun ships, troop
lift, insertion/extraction, and special operations). Since 11 September 2001, the impact of the existing shortfall of
operational T700-GE-401C Engines was exacerbated by the dramatically increased operational tempo and
deployment schedule in support of the Global War On Terrorism (GWOT). Decreased engine availability had a
negative impact that jeopardized overall Fleet aircraft readiness and support of our USN and USMC forces. In
August 2003, a commercial rework contract was awarded and in concert with Corpus Christi Army Depot (CCAD),
our core depot, the existing backlog of Non Ready For Issue (NRFI) Engines, CSMs, and PTMs was cleared and all
bare firewalls were filled.
2.0 Applicable Documents
The Contractor shall comply with the following documents:
• Depot Maintenance Work Requirement (DMWR 1-2840-248-1 and 1-2840-248-2 and changes)
• AMCOM Engineering Directive (AED-P3441)
• Enhanced Engine Performance Work scope MEO P3863 for the T700-GE-401 and T700-GE-401C
listed in Appendix.
• Standard Practice for Commercial Packaging (ASTM-D-3951-98)
• Quality Engineering Standard for Flight Safety Parts, QE-STD-2 (Revision A)
Page 5 of 27
• NAVAIRINST 13700.15 (series)
• Naval Aviation Maintenance Program (CNAF 4790.2 (series), Volume I, Chapter 13)
NAVAIR shall provide the contractor electronic copies of all active AEDs to ensure that any and all recent engine
build improvements that affect the 401/401C engine, CSM or PRM performance are adhered to.
Each T700-GE-401/401C Whole Engine consists of the following:
ENGINE MODULE PART NUMBER NATIONAL STOCK NUMBER
T700-GE-401X Cold Section 6043T82G01 2840-01-476-1721
T700-GE-401CX Cold Section 6064T26G01 2840-01-317-6673
T700-GE-401L Power Turbine 6043T81G01 2840-01-486-3044
T700-GE-401CL Power Turbine 6064T27G01 2840-01-316-9791
3.1 Program Management
The Contractor shall plan, manage, and organize effective internal controls to meet the requirements specified in this
SOW. The Contractor shall maintain a Program Management Office, led by a Program Manager specifically
charged with the responsibility, accountability, and authority for the T700-GE-401/401C program cost, schedule,
and performance. In addition, the Program Manager shall coordinate all contract deliveries, schedules, and
3.2 Receipt of Engines/CSMs/PTMs
The Government will ship T700-GE-401/401C Engines, CSMs, and PTMs to the Contractor’s repair facility in
approved and serviceable Government furnished containers.
The Contractor shall notify the Administrative Contracting Officer (ACO) and request disposition instructions for all
received containers which are damaged and unusable to a point that would not adequately protect Engines/CSMs,
and PTMs. The Contractor shall obtain replacement containers by contacting the Naval Inventory Control Point,
Philadelphia (NAVICP-P) Container Manager at the phone number listed in Appendix A. Authorized shipping
containers are listed in Appendix A.
Upon receipt of the engines and/or modules, the Contractor shall verify the proper configuration of the Engines,
CSMs, and PTMs, i.e., that all harnesses and fuel nozzles, Hydro Mechanical Control Unit (HMU), particular
separator blower, etc are installed.
After inspection, the Contractor shall compile a Shortage List document and notify the T700 Deputy Assistant
Program Manager Logistics/Fleet Support Team (DAPML/FST) of missing items. The Contractor may use the
USN’s Equipment History Card (EHC) repository to obtain data for reconstructing history on life-limited parts by
contacting the Engine Composition Tracking (ECOMTRAK) manager at Fleet Readiness Center (FRC) East Cherry
Point NC. The ECOMTRAK manager information can be found in Appendix A.
The Contractor shall ensure Engines, CSMs, and PTMs serial numbers remain intact and traceable to associated
engine logbooks if all or parts of the modules are removed.
3. 3 Repair of Navy T700-GE-401/401C Engines/CSMs/PTMs
The Contractor shall repair, rework, modify and test items as necessary to conform to the DMWR contained in
paragraph 2.0 of this SOW. The Contractor is encouraged to take advantage of Best Commercial Practices (BCP).
When BCP are in conflict with the DMWR, authorization to proceed with the BCP repair/rework must be obtained
from Fleet Support Team (FST) engineering. The Contractor shall provide all necessary government approved
vendor parts, materiel labor, tooling, special tooling, test equipment, and facilities required to perform this contract
Page 6 of 27
unless specifically directed by the Contracting Officer or except for Government Furnished Equipment listed in
3.4 T700-GE-401/401C Repairable External Components
The Contractor shall use a functional test to ensure all repairable external components HMU, AISBV etc, which
are shipped with Engines/CSMs/PTMs, are tested or repaired as necessary, and properly preserved to ensure proper
Engines and modules shall meet the test requirements of the DMWR after repair and/or modification. Each engine
shall pass the applicable acceptable limits set forth in the DMWR for each required test and achieve 100% rated
power in the test cell as a minimum. Test run records shall be maintained by the Contractor and be available for
Government review at anytime. The Contractor shall include copies of the final engine run sheets with the
applicable engine logbooks.
3.6 Configuration Management
The Contractor shall maintain compliance with the USN’s Technical Directive Status Accounting (TDSA) System.
The Contractor shall report the incorporation compliance of the directives to the Government In Accordance With
(IAW) CDRL A001. The Contractor shall only make configuration changes when authorized by the T700 Lead
Engineer, after they have been approved by the Configuration Change Board and placed on contract by the PCO.
The T700 Lead Engineer will provide the configuration directives to accomplish this task. The T700 Lead Engineer
can be reached at 301-995-7672.
The Government retains the right to approve all non-conforming deviations from the approved parts in the
configuration baseline for components repaired under this contract.
The Contractor shall repair, rework, modify and test items, as necessary, to conform to the applicable documents
contained in paragraph 2.0 of this SOW when requested by the T700 Engineering support team. All non-
standard/standard configuration builds utilizing an experimental or unapproved process and hardware shall be
authorized at the discretion of USN engineering. All builds shall comply with the specifications contained in
paragraph 2.0 of this SOW or Best Commercial Build Practices, as approved by USN engineering.
Configuration catch-up builds that forces the replacement or scrap of superseded hardware, regardless of reuse limit
criteria, shall be at the discretion and cost of USN engineering.
As directed by and subsequently reported to USN engineering, all engine/CSM/PTM/hardware inspections that are
outside the scope of the DMWR requirements for engine inspections shall be conducted. Any additional
dimensional measurements or clearances, FPI/MPI inspections, and or other non-destructive component testing at
standard commercial cost may be requested by USN engineering.
4.1 Engine Testing
The following tests and conditions, as requested by and reported to USN engineering, are as follows: standard
engine testing ATP run (green run) with Data Reduction Program (DRP) data recording with heated inlet
conditioning, a 13 point steady state performance calibration run along with data transfer via DRP recording with
heated inlet conditioning, and any other additional steady state performance points with DRP data recording shall be
reported as requested.
Page 7 of 27
Engine/CSM/PTM teardown and layout for engineering inspection. Parts to be displayed in as-received condition
5.0 Performance Metrics
Performance metrics define the minimum acceptable levels of performance that must be met to satisfy the
requirements of this. The metrics are defined and established as follows:
Repair Turnaround Time (RTAT) thresholds for:
Engines: 90 calendar days
Cold Section Modules: 90 calendar days
Power Turbine Modules: 60 calendar days
The Contractor shall meet a maximum RTAT of 90 calendar days for all engine and CSM repairs and 60 calendar
days for PTM repairs. RTAT shall begin when the Contractor receives serviceable, Not-Ready-For-Issue (NRFI)
Engines, CSMs, or PTMs and a work order is issued to induct the Engines, CSMs or PTMs for repair it ends when
the Engines, CSMs, and PTMs are signed off, by the Government or appointed representative, as Ready-For-Issue
(RFI), which includes completion of all entries in logbooks and records, and are ready for shipment by the
Contractor. Contractor shall forward a copy of the Engine/CSM/PTM log books/component cards to the
ECOMTRAK manager for review/correction upon induction for repair. Upon completion of repair contractor shall
forward Engine/CSM/PTM log books/component cards with replaced/repaired component serial numbers with Time
Since New/Time Since Repair (TSN/TSR) to the ECOMTRAK manager for review prior to shipment.
Note: The 90-day CSM and 60-day PTM RTAT metrics DO NOT pertain to modules installed on
Engines. RTAT for these modules shall be subsumed by engine RTAT. CSM and PTM RTAT only
pertains to those modules received as separate items.
Customer Hold Time (CHT) may be deleted from the total repair processing time when calculating RTAT. CHT is
defined as the elapsed calendar days that the Contractor must halt the repair process to await required Government
action, i.e., funding, respond to repair estimates, await Government inspection, await for Government to provide
status on parts on shortage list (Para 3.2), and await Government provided material such as Power Plant Change
(PPC) kits, etc. Periods in which the Contractor can continue repair processing while waiting for Government action
shall not be included in CHT.
The Contractor shall justify to the Contracting Officer Representative (COR) that the RTAT threshold has been met
including any reported authorized CHT. During performance of contract, the Contractor shall be evaluated on the
basis of whether RTAT has been properly met. Excess RTAT days are computed by subtracting verified CHT days
from the actual elapsed RTAT, less the appropriate RTAT metric, as described below:
• For Engines and CSMs:
o Excess RTAT = Actual elapsed RTAT – CHT days - 90 days
• For PTMs:
o Excess RTAT = Actual elapsed RTAT – CHT - 60 days
6.1 Engine Transaction Reporting
Page 8 of 27
The Contractor shall submit Engine Transaction Reports (ETR) to report changes in Engine, CSM, and PTM status
in accordance with DeckETR, the DECision Knowledge Programming for Logistics Analysis and Technical
Evaluation (DECKPLATE) database per NAVAIRINST 13700.15 (series). Guidance may be obtained from the
DECKPLATE Project Manager. The Government will provide access to DECKPLATE software and training to
Contractor personnel if required. ETR’s shall be submitted using the ETR function of DECKPLATE, DECision
Knowledge Engine Transaction Reports (DECKETR). The Contractor shall submit ETRs IAW A002 when the
following situations occur:
• Receipt of an uninstalled engine or module from another activity for repair, or Quality Deficiency Report
• Induction of an engine or module for rework, repair or modification.
• Removal or installation of a module on an engine.
• Work Stoppage due to Awaiting Parts (AWP).
• Completion of the repair process and RFI report when engines and modules are ready for shipment.
• Shipment of an engine or module following completion of repair, warranty repair, or QDR processing.
• Changes in series numbers for engines and modules due to modification.
6.2 Monthly Repairs/Status/Report
The Contractor shall provide a monthly report that provides information on all completed, repaired or modified,
Engines, CSMs, and PTMs during the previous month. The report shall provide the following information and shall
be reported IAW CDRL A003.
6.2.1 Performance Part Replacement
The report shall document all performance related hardware replaced during the repair or modification process. The
report shall contain; part number, nomenclature, quantity replaced and a brief description of the defects causing
replacement. Unusual degradation or damaged parts may provide detection of emerging trends caused by
environmental, design or Governmental process anomalies (problems). Performance parts include:
• All Blisks and Impellers
• All Gas Generator Turbine (GGT) Blades
• All Power Turbine (PT) Blades
• Midframe Diffuser
• All GGT Disks – Life Limited Hardware
• All PT Disks – Life Limited Hardware
• PT Shaft – Field Interest Item
• Combustor Liners
• Other Life Limited Hardware
6.3 Information Technology (IT) Systems Authorization Access Request (SAAR)
Page 9 of 27
5252.204-9505 INFORMATION ASSURANCE AND PERSONNEL SECURITY REQUIREMENTS FOR
ACCESSING GOVERNMENT INFORMATION TECHNOLOGY SYSTEMS (OCT 2007)
(a) Contractor personnel assigned to perform work under this contract may require access to Government IT
Systems. Contractor personnel requiring access to Government IT Systems shall comply with AIR-7.2/7.4 Policy
Memo 5510, “Information Technology (IT) Positions” dtd 17 May 2007 or latest version thereof, available at IT
POSITIONS.pdf as amended IT Policy Amendment 6 June 07 or through the Procuring Contracting Officer (PCO)
provided as an attachments 3 and 4. Prior to accessing any Government IT System, contractor personnel shall
submit a completed Systems Authorization Access Request (SAAR), DD Form 2875, Annual Information
Assurance (IA) training certificate, and initiate the requisite background investigation (or provide proof of a current
background investigation) to the Contracting Officer’s Representative (COR). For purposes of this clause, reference
to the COR shall mean the PCO for contracts that do not have a designated COR. In order to maintain access to
required systems, the contractor shall ensure completion of annual IA training, monitor expiration of requisite
background investigations, and initiate re-investigations as required.
(b) Contractor personnel shall complete, sign and date Part I of the SAAR (available at DD2875 12 June 2006.pdf
provided as an attachment 5 and coordinate with the COR to designate in Part III, block 28c, the appropriate IT
level designation (IT-1, IT-2, or IT-3). The completed SAAR and proof of a current background investigation is to
be provided to the COR. The COR will review the SAAR submitted by the contractor, and if the COR concurs that
the contractor requires the IT access designated, the COR will complete and sign Part II. When a background
investigation is required, contractor personnel shall coordinate with Command Personnel Security, AIR-7.4, and
follow the procedures as described at the NAVAIR website IT Positions Process for Contractors.doc.
(c) The contractor shall provide separate Information Technology Personnel Security Reports to the COR
and to NAVAIR Security in accordance with CDRLs A004 and A005. The report submitted to the COR shall not
contain Social Security information that is required in the report submitted to NAVAIR Security. Both reports shall
show that all contractor personnel meet the requirements for obtaining access to Government IT Systems, and that
all requirements are verified and validated thereafter on an annual basis. All prime, subcontractor, consultants, and
temporary employees shall be included in the reports. Revised reports shall be submitted when gains and/or losses
of employees occur to ensure that all employees comply with these requirements prior to accessing Government IT
7.0 Disposition Instructions for Condemned Parts and Material
The Contractor shall request disposition guidance from the Technical Point of Contact (TPOC) for all material.
8.0 Maintenance/Update of Records/Logbooks
8.1 Contractor Responsibility
The Contractor shall maintain and update manual records for those T700-GE-401/401C Engines, CTMs, and PTMs
in their custody for repair or modification. Instructions for maintaining these records are detailed in the Naval
Aviation Maintenance Program (CNAF 4790.2 (series), Volume I, Chapter 13).
The Contractor shall maintain and update the following specific records IAW CNAF 4790.2 (series), Volume I,
Chapter 13 with emphasis to the following:
• Paragraph 13.3.14 Aeronautical Equipment Service Record (AESR) (OPNAV 4790/29)
• Paragraph 13.3.3 Inspection Record – (OPNAV 4790/22A)
• Paragraph 13.3.4 Repair/Rework Record – (OPNAV 4790/23A)
• Paragraph 13.3.5 Technical Directives – (OPNAV 4790/24A)
Page 10 of 27
• Paragraph 13.3.6 Miscellaneous/History – (OPNAV 4790/25A)
• Paragraph 13.3.7 Preservation/Depreservation Record – (OPNAV 4790/136A)
• Paragraph 13.3.9 Inventory Record – (OPNAV 4790/27A)
• Paragraph 13.3.15 Equipment Operating Record (EOR) (OPNAV 4790/31A)
• Paragraph 13.3.16 Module Service Record (MSR) (OPNAV 4790/135)
• Paragraph 13.3.17 Assembly Service Record (ASR) (OPNAV 4790/106A)
• Paragraph 13.3.18 Equipment History Record (EHR) Card (OPNAV 4790/113)
• Paragraph 13.3.19 Scheduled Removal Component (SRC) Card (OPNAV 4790/28A)
Logbook Form requirements, specified below, are provided by module/component:
• Power Plant – Whole Engine Assembly
o Gas Generator Turbine/Stator (ASR)
o Hydro Mechanical Unit - HMU (EHR)
• Cold Section Module – CSM (MSR)
o No. 4 Bearing (EHR)
o AISBV (EHR)
o Compressor Rotor/Stator Assembly (ASR)
o Power Take Off (PTO) (EHR)
• Power Turbine Module – PTM (MSR)
o Power Turbine Rotor Assembly (ASR)
o Power Turbine Shaft (SRC)
8.2 Engine Composition Tracking
In addition to the manual records listed in paragraph 8.1 above, the USN requires all tracked components of the
T700-GE-401/401C Power Plant be reported and tracked through the ECOMTRAK and Parts Life Tracking (PLTS)
programs. Specific instructions for Contractor’s responsibilities to provide documentation to ECOMTRAK and
PLTS will be provided by the T700 DAPML/FST as Government Furnished Information (GFI) within 30 days of
The Contractor shall report into ECOMTRAK and PLTS as required by the Government. Contractor shall forward
an electronic copy of the Engine/CSM/PTM logbooks/component cards to the ECOMTRAK manager for
review/correction upon induction for repair. Upon completion of repair, contractor shall forward Engine/CSM/PTM
logbooks/component cards with replaced/repaired component serial numbers with TSN/TSR to the ECOMTRAK
manager for review prior to shipment.
8.3 Retention of Records
Page 11 of 27
The Contractor shall retain copies of engine logbooks and module records for a period of 5 years from the date of
repair. The Contractor shall provide copies of engine and module records in response to Government requests in the
event the original records are lost or destroyed.
9.1 Engine Assignment Responsibility
NAVICP-P, Code 0331 is the NAVAIR engine assignment agent. NAVICP-P directs the shipment of repaired
engines to Fleet customers in order to optimize Fleet readiness postures. The Contractor shall contact the NAVAIR
NAVICP representative located at Corpus Christi Army Depot at telephone 361-961-6768 for engine assignment
9.2 Shipping Documentation and Instructions
The Contractor shall ship Engines/CSMs/PTMs to the destinations directed by the engine assignment sequence
numbers. The Contractor shall ship Engines/CSMs/PTMs to the locations designated using shipping instructions
provided by the Government.
10.0 Packing/Handling/Storage and Transportation (PHS&T)
10.1 Shipping Containers
The Contractor shall ensure sufficient containers are available to facilitate shipping RFI Engines/CSMs/PTMs
within the RTAT metrics. The Contractor shall immediately notify the NAVAIR T700 DAPML or the NAVICP-P
Container Manager for assistance if suitable containers are not available (Appendix A).
10.2 Shipment of RFI ENGINEs/CSMs/PTMs
The Contractor shall ensure that all logbooks and records are protected from damage and enclosed with their
associated RFI Engine/CSM/PTM when placed in shipping containers for shipment.
Page 12 of 27
APPENDIX A: TABLE OF REUSABLE USN T700-GE-401/401C ENGINE/CSM/PTM CONTAINERS
The ECOMTRAK information is available through the ECOMTRAK Manager, telephone (252)-444-6023, email
The following reusable shipping and storage containers have been developed for the T700-GE-401-401C
Engine/CSM/PTM. These reusable shipping and storage containers shall be utilized to ship the components
identified below. All reusable shipping and storage containers are available through the NAVICP-P Container Item
Manager Code 03312.28, telephone (215) 697-5924.
NSN Container NSN Drawing Number
NA 8145-01-302-1026 80132-15483
NA 8145-01-302-1026 80132-15483
Cold Section Module
2840-01-476-1721 8145-01-164-4070 80132-15715
Cold Section Module
2840-01-317-6673 8145-01-164-4070 80132-15715
Power Turbine Module
2840-01-486-3044 8145-01-164-4071 80132-15628
Power Turbine Module
2840-01-316-9791 8145-01-164-4071 80132-15628
Page 13 of 27
APPENDIX B: GOVERNMENT FURNISHED EQUIPMENT
NOMENCLATURE Part Number Serial Number
DEC 6068T81P13 ECDT7664
HMU 4046T52G27 11486915
COMB. LINER 6064T54G08 GGM8TL4J
GEARBOX 6039T19G07 FIA9G992
STG 1 NOZ 6071T04G02 AMDA5934
BLOWER 234-34-1 SVS01995
PT MODULE 6064T27G02 133-019
CS MODULE 6064T26G01 766760
HMU 4046T52G27 13248902
401C Hot Section Module (including one nozzle) One (1) EA
401 Hot Section Module (including one nozzle) One (1) EA
401C Hydraulic Mechanical Unit (HMU) One (1) EA
401 Hydraulic Mechanical Unit (HMU) One (1) EA
401C Digital Electronic Control Unit (DECU) One (1) EA
401 Electronic Control Unit One (1) EA
401C Power Turbine Module (PTM) One (1) EA
401 Power Turbine Module (PTM) One (1) EA
401C Accessory Module One (1) EA
401 Accessory Module One (1) EA
401C Cold Section Module One (1) EA
401 Cold Section Module One (1) EA
Page 14 of 27
APPENDIX C: LIST OF ACRONYMS AND TERMS
ACI – Analytical Condition Inspection. Analytical process conducted by the AMCOM Depot Maintenance
Engineering Team (DMET) to determine the necessary depot work specifications changes, e.g., tighten tolerances,
increase parts replacement. Work specification changes are developed and approved by DMET in cooperation with
the Navy Fleet Support Team (FST) and published as AMCOM Engineering Directives (AEDs).
ACC – Aircraft Controlling Custodian. A term applied to Aircraft Type Commanders (TYCOMs) for exercising
administrative control of assignment, employment, and logistic support of certain aircraft and aircraft engines.
ACO – Administrative Contracting Officer. Performs assigned functions, duties, or responsibilities related to the
administration of a contract.
AED – AMCOM Engineering Directive (AED)
AESR – Aeronautical Equipment Service Record.
AISBV – Anti-Ice Start Bleed Valve.
AYC – Accessory Change.
AMCOM – U.S. Army Aviation and Missile Command.
ASR – Assembly Service Record.
ATP – Acceptance Test Procedure.
AWP – Awaiting Parts.
BCP – Best Commercial Practices.
Contractor – Prime commercial repair station/depot contractor and any sub-contactors and/or vendors under this
CCAD – Corpus Christi Army Depot.
CDRL – Contract Data Requirements List.
CHT – Customer Hold Time.
CSM – Cold Section Module.
DAPML – Deputy Assistant Program Manager for Logistics.
DCMA – Defense Contract Management Agency.
DECKPLATE – DECision Knowledge Programming for Logistics Analysis and Technical Evaluation.
An automated engine management system that provides on-line status and condition of any propulsion system
engine or module. Navy Aircraft Controlling Custodians (ACCs) and other managers use the system to manage and
maintain visibility of engine assets. Reporting procedures are found in NAVAIR Instruction 13700.15(series).
DECKETR – DECision Knowledge Engine Transaction Reports. Data base used to report changes in
Engine/Module Status, changes in ownership/receipts/transfers etc…. Reporting procedures are found in NAVAIR
Page 15 of 27
DMISA – Depot Maintenance Interservice Support Agreement. The DMISA is an agreement constituting a
contractual obligation whereby one Service (called the Agent) accomplishes depot-level maintenance work for
another Service (called the Principal). The DMISA is cited in this SOO for work requirements applicable to private
contractor performing standard depot repair under commercial contract.
DMWR – Depot Maintenance Work Requirement. A DMWR is defined as the maintenance serviceability standard
for depot maintenance operations; it bounds the “standard depot repair” to be done. It prescribes the scope of work
to be performed on an item by depot maintenance facilities including contractors, types and kinds of materiel to be
used, quality of workmanship, repair methods, procedures and techniques, modification requirements, fits and
tolerances, equipment performance parameters to be achieved, and other essential factors to ensure that an
acceptable and cost effective product is obtained.
DoD – Department of Defense.
ECOMTRAK – Engine Composition Tracking. The ECOMTRAK System is an automated system used for tracking
the composition, location, and operating time/cycle counts or life usage indexes of aircraft engines, propulsion
systems, modules, and life limited components. ECOMTRAK is used to develop long-range schedules for
inspections, removals, replacements, procurements, and rework schedules for these components, based on usage
requirements and fixed or variable usage rates. It provides important support to the Reliability Centered
Maintenance (RCM) Program.
EOR – Equipment Operating Record.
ETR – Engine Transaction Reports.
FST – Fleet Support Team. FST is the Integrated Product Team assigned the responsibility to perform specified in-
service engineering and logistics functions for the PMA.
FPI – Floresant Penetrate Inspection.
FRC – Fleet Readiness Center.
GEDRP – General Electric Data Reduction Program.
GGT – Gas Generator Turbine.
GWOT – Global War On Terrorism.
HMU – Hydro Mechanical Unit.
IAW – In Accordance With.
MPI – Magnetic Particle Inspection.
Modification – To make basic or fundamental changes to configuration of the engine and/or module. These changes
are usually published in the form of a Technical Directive that may include approved Navy Interim Rapid Action
Change (IRAC), Power Plant Bulletins (PPBs) or Power Plant Changes (PPCs).
MSR – Module Service Record.
NAVAIR – Naval Air Systems Command. The Naval Aviation Systems Command, also known as NAVAIR
TEAM, in partnership with industry, serves the Nation and the Navy by developing, acquiring, and supporting naval
aeronautical and related technology systems with which the operating forces, in support of the Unified Commanders
and our allies, can train, fight, and win.
Page 16 of 27
NAVICP-P – Naval Inventory Control Point, Philadelphia. The mission of the NAVICP-P is to provide program
and supply support for the weapons systems that keep our Naval forces mission ready.
NRFI – Non Ready For Issue.
OPNAV – Office of Chief of Naval Operations
PLTS - Parts Life Tracking System. PLTS is an automated system used for tracking the composition, location, and
operating time/cycle counts or life usage indexes of aircraft engines, propulsion systems, modules, and life limited
components. PLTS is used to develop long-range schedules for inspections, removals, replacements, procurements,
and rework schedules for these components, based on usage requirements and fixed or variable usage rates. It
provides important support to the Reliability Centered Maintenance (RCM) Program.
Performance Thresholds – Defines the minimum acceptable repair process and engine performance values necessary
to meet the requirements of the contract.
PCO – Procurement Contracting Officer. The government contracting officer directing and administering the
acquisition through the award of the contract. Administration of the contract after award may be delegated to an
PMA – Program Management Air.
PPC – Power Plant Change.
Propulsion System – The complete propulsion system comprises the engine, modules, accessories and/or
components and parts used for powering flight and is specified in the applicable Illustrated Parts Breakdown (IPB)
for the T700-GE-401/-401C the IPB is A1-T700A-MMI-200/-210. A T700 engine turned in for depot repair does
not include the Electronic Control Unit (ECU) for the –401 and the Digital Electronic Control Unit (DECU) for the
PT – Power Turbine.
PTM – Power Turbine Module.
QAR – Quality Assurance Representative.
QDR – Quality Deficiency Report.
Repair – Necessary preparation, fault correction, disassembly, inspection, replacement of parts, adjustment,
reassembly, calibration, or tests accomplished in restoring items to serviceable status.
RTAT – Repair Turnaround Time.
Rework – Restorative or additive work performed on aircraft engines and modules at depots, commercial or
Government, and includes the necessary refurbishment of components to restore clearances and performance
specifications to specifications.
SOW – Statement Of Work.
Standard Depot Repair Specification – Repair, rework, modification, testing and documentation done to the DMWR
TDSA – Technical Directive Status Accounting.
Page 17 of 27
Technical Directive (TD) – A document authorized and issued by NAVAIR to provide technical information
necessary to properly and systematically inspect or alter the configuration of propulsion systems (engines, modules
and components) subsequent to establishment of each respective baseline configuration. Basic TD compliance
procedures are referenced in the Naval Aviation Maintenance Program (CNAFINST 4790.2 (series), Volume I,
Chapter 13. Additional instructions on TD compliance and reporting will be detailed in the DMWR.
TSN/TSR – Time Since New/Time Since Repair
TYCOM – Type Commander. For aircraft, these commanders provide the tactical commands with the means to
conduct tactical operations including administration of training, supply, and repair of Fleet units. Included in their
mission is the control of aircraft engines assigned to them as part of their Aircraft Controlling Custodian (ACC)
responsibilities. TYCOMs include COMNAVAIRFORCES, COMNAVAIRESFOR, COMNAVAIRSYSCOM and
USMC – United States Marine Corps
USN – United States Navy.
Workscope – Term used by AMCOM DMET in AEDs, which when invoked for the Navy T700 adds or supersedes
processing requirements to the Standard Depot Repair detailed in the T700 DMWR.
SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO BIDDERS
The following have been modified:
L-1 CONTENT OF PROPOSALS (SUPPLIES OR SERVICES)(AUG 2008)
PART A GENERAL INSTRUCTIONS
Offerors are required to submit sufficient information concerning the following areas to enable Government
personnel to fully ascertain capabilities of the offeror to perform the requirements. The proposal must be sufficient
in detail and scope to permit evaluation and provide the evaluators a clear understanding of the offeror’s approach,
expertise, experience and capability as required by the solicitation. All proposals must clearly and convincingly
demonstrate that the offeror has a thorough understanding of the requirements, associated risks and is able, willing
and competent to devote the resources necessary to meet the requirements and has valid and practical solutions for
all requirements and potential risk areas. Respond to all requirements of the solicitation. Do not alter or rearrange
the solicitation. The burden of proof for all the evaluation factors identified in this solicitation rests with the offeror.
The offerors are advised that the Government may incorporate into the final contract enhancing features included in
the Offeror’s proposal deemed beneficial to the Government. With the exception of the Price Volume, no cost or
pricing information should appear in any other volume.
In presenting material in the proposal, the offeror is advised that quality of information is more important than
quantity. Clarity, brevity, and logical organization should be emphasized during proposal preparation. It is the
responsibility of the offeror to present enough information to allow the various work efforts, support, and
management approaches, as well as price, to be meaningfully evaluated without discussions. Statements that the
prospective offeror understands, can or will comply with the specifications, and paraphrasing the requirements or
parts thereof without supporting information are considered inadequate and may render a rating of unsatisfactory.
For the purpose of this acquisition, relevance is defined as something that has a logical connection with the matter
under consideration. Such aspects or relevance include the type of effort (e.g. development, production, repair), the
type of requirements (e.g. weapon systems, information systems, engineering services, scheduled depot
maintenance), service similarity, service complexity, contract type, contract dollar value, the division of the
Page 18 of 27
company that will perform the work, and participation of Principal Subcontractors, Team Members, or Critical
The offeror must include any data necessary to illustrate the adequacy of the various assumptions, approaches,
and solutions to problems. Failure to clearly and positively address a specific factor or subfactor may be considered
a deficiency. There is no need to repeat information in more than one volume if an overlap exists; the detailed
information must be included in the most logical place and summarized and referenced in other areas.
Unnecessarily elaborate brochures or other presentation materials beyond that sufficient to present a complete and
effective proposal is neither necessary nor desired.
Offerors are expected to comply with all requirements of the RFP. The Government advises offerors that
taking exception or deviating from any term or condition of the RFP may make an offer unacceptable, and the
offeror ineligible for award, unless the RFP expressly authorizes such an exception or deviation with regard to that
specific term or condition. The Government may consider any exception or deviation to any term or condition of
the RFP that is not expressly authorized by the RFP to be a deficiency, as defined in FAR 15.001. Offerors are to
detail the particular section, clause paragraph and page to which they take exception. In evaluating an Offeror’s
capability, the Government will consider how well the Offeror complied with the instructions in this solicitation.
An Offeror may eliminate a deficiency in its offer only through discussions as prescribed in FAR 15.306. The
Government also reserves the right to change any of the terms and conditions of this solicitation by amendment at
any time prior to contract award and to allow Offerors to revise their offers accordingly, as authorized by FAR
NOTE: Offerors must respond to all requirements for the solicitation document. Offerors are cautioned not to
alter the solicitation document (other than completing the appropriate “fill-in” blocks and certificates).
Throughout these instructions, “Principal Subcontractors” are defined as a subcontractor who provides at least
30% of the proposed total cost/price (excluding the offeror’s profit/fee), for the contract. Team Members are the
entities that make up a joint venture or any other partnership or teaming arrangement that is formed for the purpose
of responding to this solicitation. Critical team members are entities of the offeror that perform a critical function in
the performance of the resulting contract, whether it is technical or financial, and/or have important roles in any high
or medium risk areas identified in the offeror’s proposal.
2.0 PROPOSAL FORMAT
Written proposals must be formatted using a Times New Roman 12 pt normal font (no reduction permitted),
single-spaced with 1-inch margins all around, and formatted for standard 8.5 x 11 inch paper. All pages should be
numbered with section and page numbers. When foldout pages are used they must not exceed 11 x 17 inches and
will be counted as 1 page. Drawings may be provided separately and may be any size but should be folded to
approximately 8.5 x 11 inch standard size and will count as 1 page. Graphs shall be presented in no smaller than a
10 pt font and should contain a grid, which allows values to be read directly from the graph to the same accuracy
that a 10 x 10 to the ½ inch grid provides. Graphic resolution should be consistent with the purpose of the data
The offeror will provide one complete copy of the written proposal to the PCO as electronic files fully
compatible with Microsoft Office 2000 and for information not supported by MS Office products, with the latest
Adobe Acrobat reader on a CD-ROM. The offeror will ensure that the Price Volume is provided on a separate CD-
ROM. Each CD-ROM is to be labeled for content and the Offeror’s name. If a discrepancy exists between the
original paper copy of the proposal and the disk copy, the paper copy will take precedence.
The offeror must present its proposal information in a manner that facilitates a one to one comparison between the
information presented and this Proposal Instruction. Proposal information must be structured such that its paragraph
number/letter is identical to the Proposal Instructions paragraph number to which it is responding, although the
offeror may add lower tier subparagraphs. The offeror must provide reasons it will not provide information for a
Page 19 of 27
particular paragraph. The proposal information instructions are structured by paragraph numbers where first,
second, third and fourth parts correspond to the volume, book, section, and element, etc., in offeror’s proposal.
3.0 PROPOSAL CONTENT AND VOLUMES
Each volume of the proposal shall be submitted as one original and additional copies as specified in the table
below. Submission of all volumes of the Original proposal to the address provided in section 4.0.will determine
timeliness of receipt. Page limitations for each volume if any, are also specified in the table below as follows (title
and table of contents pages do not count towards page limit). Proposal pages beyond a specified maximum limit, if
any, will not be reviewed as part of the evaluation.
Information submitted as an Annex to the proposal includes manuals, specifications, plans, procedures, and
policies that exist as an official document of the company or facility, as well as other information requested in Part B
Specific Instructions. Annexes do not have page limitations. The authorized Annexes are summarized in the table
Volume Number Volume Title Recommended Page Limit Copies Required
1 No Page Limit 1 Original/1 Copy/ 1 CD ROM
2 TECHNICAL 50 1 Original/3 Copies/ 1 CD ROM
3 50 1 Original/3 Copies/ 1 CD ROM
4 PRICE No Page Limit 1 Original/1 Copy/ 1 CD ROM
5 DEVIATIONS AND No Page Limit 1 Original/1 Copy/ 1 CD ROM
Each volume must contain the following information:
Cover and title page
Title of proposal and proposal number as applicable
Offeror’s name, address and POC
Proposal volume/book number
Table of Contents (The table of contents must provide sufficient detail to enable easy location of important
Use tabs and dividers
The offeror shall submit a Cross Reference Matrix (CRM) for the Technical Volume, similar to the example
below, to help ensure that all solicitation requirements are addressed and to facilitate the evaluators’ review of the
offeror’s proposal. The CRM should be a single integrated matrix and cross-reference the proposal volumes and
paragraphs to specific RFP requirements, as well as other parts of the proposal that contain relevant information.
The offeror’s CRM may be identical to the example below or revised such as to add columns to indicate the page
number on which information may be found, identify where other relevant information in the proposal is located, or
provide other comments. The CRM does not count against any of the proposal page limitations.
EXAMPLE OF A CROSS REFERENCE MATRIX (CRM)
Page 20 of 27
Section L – Section M –
Proposal Evaluation CLIN
Instructions Government PWS/SOW Factor Offeror’s Proposal Reference Reference
Example: Para 3.1 3.A Provide reference to your Proposal
Volume 3 Note: This column shall Volume I - Technical. Example:
Technical address all paragraphs in Refer to appropriate page number
Sections xx and xy of the in your written proposal
4.0 PROPOSAL SUBMISSION
Clearly mark all packages with the solicitation number. The submission date for all Volumes shall be no later
than the date and time specified in Block 8 of Standard From 1449 of the RFP. However it is requested that the
Volume 3, Past Performance information in paragraphs 2.1 and 2.2 and the Volume I, Executive Summary
“Offeror’s Summary Table”, 1.0 (ii) should be submitted three weeks prior to the submission date/time specified on
Standard Form 1449 (Block 8).
Proposals shall be submitted via United States Postal Service or through a commercial carrier using the address
provided below. Proposals are not to be submitted by facsimile or electronically via email.
Naval Air Systems Command
Code: AIR-188.8.131.52.1.4, Tonecia Porter
21983 Bundy Road, Bldg 441
Patuxent River, MD 20670
Solicitation Number: N00421-08-R-0118
Hand carried proposals may be delivered to the address above, attention Chris Schimek and/or Rita Pegg.
5.0 PROPOSAL PACKAGING
The offerors shall package the proposal volumes in cartons or equivalent packaging containers in the most
efficient manner possible grouping like volumes to the maximum extent possible. Also each carton shall be single
person portable. However, the Master Set, as described below, shall be packaged separately and marked as the
Master Set. Each box should include a packing slip detailing the contents to include the volume number, title, and
copy number. Also, each box should be stamped or marked “For Official Use Only” and “Source Selection
Information -- See FAR-2.101 and 3.104”. The Master Set shall include all original proposal volumes including the
original/signed documents submitted as part of Volume 1 Executive Summary.
6.0 CLASSIFIED DATA
All proposals must be UNCLASSIFIED
7.0 SOLICITATION CHANGES
Page 21 of 27
For any changes and additional information for the solicitation please go to website:
PART B SPECIFIC INSTRUCTIONS
1.0 VOLUME: 1 – EXECUTIVE SUMMARY
Note: This volume shall not contain any reference to cost or price aspects of the offer.
The purpose of the Executive Summary is to provide the evaluators with an overview of the Offeror’s proposal
and strategy. The Offeror shall include the following in this volume:
i. Offeror Summary Table: The offeror shall complete the table below. The offeror should include all
subcontractors and team members who will be involved with the performance or management of the program work
and should list all sites where the work will be performed. If a teaming or subcontracting arrangement is proposed,
identify the work share, distribution elements, and ratios that each contractor will perform using the table below.
Also provide a definition of the legal relationship between the entities if it is other than a Prime/subcontractor
Contractor Name Place of Performance/DUNs Brief Work Description % of Total
(Indicate Prime, Team Member #, if applicable and/or Program Proposed Price
or Sub) Responsibility
ii. Signed SF1449 for basic solicitation and each amendment
iii. Signed Representations, Certifications and Acknowledgements or OnLine Representations and
Certifications Application (ORCA) reference
iv. Affirmation of no Exceptions, Deviations or Waivers if Volume 5 is not being submitted as part of the
2.0 VOLUME: 2 - TECHNICAL
Note: This volume shall not contain any reference to cost or price aspects of the offer.
2.1 The offeror shall provide all information and data required to conduct a thorough and complete technical
evaluation. The offeror shall address the following in the proposal:
The offeror shall provide a complete description of its plant facilities and the facilities of any major
subcontractors. This description shall be limited to no more than eight (8) pages (not including graphs, charts, or
diagrams, which are to be limited to two (2) pages). Any pages beyond the eighth page will be removed from your
proposal and will not be evaluated. If facilities are not currently available, furnish evidence of the ability to obtain
such facilities in a time frame required to successfully perform the contract. If any work in any of the shop areas
described in i-vi below is to be subcontracted out, explain/provide the contract vehicle used for the subcontracting
effort, a description of the facilities, and provide evidence that subcontracted facilities comply with
OSHA/EPA/ODC requirements. The following information should be furnished for all efforts (including
i. Description, number, type, size and location of buildings
Page 22 of 27
ii. A schematic of the facilities detailing the flow of the engine overhaul and the areas to be
available for use in this overhaul contract.
iii. A plan for accomplishing the overhaul program per the Depot Maintenance Work
Requirement (DMWR) and the AMCOM Engineering Directives (AEDs). This plan should be broken into the
following sections: Disassembly, Cleaning, Inspection, Repair/Overhaul, Reassembly, and Functional Test. In the
appropriate sections of the plan, ensure that all of the General Maintenance Procedures in Chapter 3 of the DMWR
are discussed and can be clearly identified. Detail what procedures/work is to be done in-house, and what is to be
off-loaded to subcontractors. Detail the rationale used for selecting particular subcontractors for the work that is to
be off-loaded, provide details on the subcontractors’ qualifications to perform the work, and provide their Federal
Aviation Administration (FAA) repair/overhaul facility certification showing approval for overhaul/repair of T700
series or equivalent gas turbine engines. If parts are to be replaced in lieu of repaired, detail this also. Include in the
plan the method for flowing the specific DMWR and AED requirements down to the shop level.
iv. Fully describe the bearing facilities to be utilized for cleaning/inspection of the engine
v. Evidence of Compliance with OSHA/EPA/ODC requirements.
vi. Number of test cells capable of running the T700 engine acceptance tests. In addition, the test
cells shall be fully described, including type of instrumentation, instrument accuracies, range of both airflow and
fuel flow capabilities, power absorption type, test data parameter recording capabilities, and ability to record
transient data. Provide the test cell calibration/correlation information, including the master cell it was correlated to.
vii. FAA repair/overhaul facility certification showing approval for overhaul/repair of T700 series
or equivalent gas turbine engines.
2.2.2 Understanding of the Work
Provide your proposed technical approach that demonstrates your understanding and capability to perform
the technical requirements of the Statement of Work (SOW). The Government will evaluate if you correctly
identified all significant activity staffing, labor mix, timeliness and potential problems as well as effective proposed
solutions. The Government will also evaluate if you implemented those solutions in an effective manner that
efficiently mitigated risks to the customer.
2.2.3 Relevant Corporate Experience
Provide information that describes the offeror’s, the offeror’s principal subcontractors’ and critical team
members’ (as defined in Part A, Section 1.0) experience similar to that required for the instant contract. Identify
Depot-level repair experience such as to the efforts required by this solicitation within 5 years prior to the date of
this solicitation. Provide examples of experience related to: (1) performed work similar to that required by the
solicitation, (2) managing work similar to that required by the solicitation, and (3) coordinating with Government
program and contracting team regarding work similar to that required by the solicitation. Explain why the
experience should be considered relevant and the degree of relevance that the experience has to the solicitation
requirements. For each example, provide the point of contact, contract number and title of the program, as well as
the dates under which the experience was gained. Offerors will include their experience in any joint ventures, single
legal entity arrangements as well as acting as an independent prime. Identify the period of time and the related
contracts. In general, recent experience will be considered more relevant than older experience. In addition, provide
a copy of the Offeror’s Summary Table requested in Part B, Section 1.0, however, the column entitled
“Approximate % of Total Proposed Price” is not needed for this volume.
The Offeror shall provide a description of its warranty provisions in accordance with NAVAIR Clause
5252.246-9502 for the following items: T700-GE-401 Engine, T700-GE-401C Engine, T700-GE-401L Power
Turbine Assembly, T700-GE-401CL Power Turbine Assembly, T700-GE-401X Cold Section Assembly, and T700-
GE-401CX Cold Section Assembly.
2.2.5 Small Business/Small Disadvantaged Business Strategy
Page 23 of 27
184.108.40.206 Strategies for using Small Business (SB) Concerns which consist of Small Business, Small
Disadvantaged Business (SDB), Women-Owned Small business, HUB Zone Small Businesses, Veteran-Owned
Small Business, Service-Disabled veteran-Owned Small Business Concerns as well as Historically Black
Colleges or Universities and Minority Institutions (HBCU/MIs).
Large Businesses (unless exempt pursuant to FAR 19.702) shall address their strategies for utilizing
Small Business (SB) Concerns and HBCU/MIs in the performance of this contract, whether as a joint venture,
teaming arrangement or subcontractor. (This strategy is separate from, but shall be consistent with, the Small
Business Subcontracting Plan.) Additionally, pursuant to FAR 19.1202, all Offerors (Large and Small Businesses)
shall address their strategies for utilizing Small Disadvantaged Business (SDB) concerns in the performance of this
contract. In describing its overall strategies for this contract, the Offeror shall, as applicable:
(a) Describe its approach to identifying SB Concerns, SDB Concerns, and HBCU / MIs;
(b) Describe the extent of participation of SB Concerns, SDB Concerns, and HBCU / MIs on this contract,
especially as principal subcontractors;
(c) Describe the extent of commitment to use such SB Concerns, SDB Concerns, and HBCU / MIs;
(d) Describe the complexity and variety of the work SB Concerns, SDB Concerns, and HBCU / MIs are to
(e) Demonstrate that its SB Concerns strategy is consistent with its SB Subcontracting Plan.
(f) Provide targets, expressed as dollars and percentages of total contract values for Small Disadvantaged
Business participation. Targets of subcontractors must be listed separately.
(g) Demonstrating Realism through Submission of Reports: To demonstrate the realism of the utilization
plan, the Offerors shall provide copies of three final or most recent SF 294s for the most current three relevant
contracts, that best demonstrate the offerors ability to achieve the proposed subcontracting goals. If the Offeror is a
participant in the DoD Comprehensive Subcontracting Test Program, they shall provide copies of three final or most
recent SF 295s. Explain how the results shown in the recent SF 295 demonstrates the realism of the plan.
220.127.116.11 SB Subcontracting Plans
The Offeror (Large Business only) shall provide its SB Subcontracting Plan conforming to the
requirements of FAR 19.7 and DFARS 219.7 as Annex 1. If the Offeror is a participant in the DoD Comprehensive
Subcontracting Test Program specified in DFARS 219.7, the Offeror shall describe how SB participation on this
contract will contribute to its overall Comprehensive Subcontracting goals. Offerors shall describe its specific efforts
to ensure the resulting contract meets or exceeds proposed goals. These efforts shall include, but are not limited to:
sponsoring program specific outreach programs and industry conferences, establishing Mentor-Protégé relationships
with SDB and using the NAVAIR SUBNet website http://www.navair.navy.mil/osbp to locate small business
concerns and to post requirements.
3.0 VOLUME: 3 - PAST PERFORMANCE
The offeror shall identify contracts whose performance is within five years of this proposal submission and
contains efforts similar to those efforts, e.g., tasks, contract type, location, contract dollar value, etc., required by this
solicitation for you, your principal subcontractors, and critical team members. Commercial contracts may be
included. NAVAIR is particularly interested in contracts directly related to the repair of complete T700 engines or
component repairs for similar type related engines. List the contracts from the most relevant to the least relevant. In
general, recent performance will be considered more relevant than older performance. These contracts should be the
same contracts identified in the Technical Volume 2 but only those that are within five years of this proposal
submission. When possible, these contracts should include at least five of the most relevant contracts for the Prime
Contractor, five of the most relevant contracts for each Critical Team Member, and two of the most relevant
contracts for each principal subcontractor (as defined in Paragraph I, General Instructions). If proposing as joint
venture/single legal entity (JV/SLE), the offeror should provide the 5 past performance references for the JV/SLE.
Page 24 of 27
If less than the 5 past performance references are available for the JV/SLE, each member of the JV/SLE should
individually submit the 5 references in addition to their JV/SLE references.
For each contract identified, provide contract data, relevancy, past performance and systemic improvement
information as described below. Demonstrate the relevancy of the Offeror’s, and if applicable, the Offeror’s
principal subcontractors’ or critical team members’ past performance and systemic improvements with respect to the
solicitation requirements. For each past performance problem identified, describe the status of the systemic
improvement efforts and, where applicable, demonstrate the impact that the systemic improvement effort had on
resolving the problem such that it would not reoccur.
For contracts that have CPARs that are more than 6 months old, i.e., the completion date is more than 6 months
before the due date for this Past Performance Volume; the offeror will forward a copy of the CPARs Update
Questionnaire (Attachment 6) to that contract customer’s Program Manager. For all contracts identified which do
not have CPARs, the offeror will forward a copy of the Past Performance Questionnaire (Attachment 7) to that
contract customer’s PCO, Administrative Contracting Officer and Program Manager. All questionnaires shall be
forwarded within two weeks from the RFP release date with enough lead-time so that responses can be received by
the Government concurrent with the Government’s receipt of the offeror’s Past Performance information submitted
as per paragraph 3.1 and 3.2 The offeror shall include instructions for the customers to send completed
questionnaires within two weeks of it’s receipt via e-mail to Chris Schimek, Contract Specialist, at Email
firstname.lastname@example.org or via fax number 301-757-2526, thereby allowing the customer approximately 2 weeks to
complete their response. This submittal information is provided at the top of the questionnaires to facilitate the
offeror’s effort in meeting these instructions. The offeror shall not conduct follow-up actions with regard to this
questionnaire. The Government will ensure that the customers have received and will respond to the questionnaires.
The Government may send any other questionnaires as necessary.
Offerors shall provide written consent from their principal subcontractors and critical team members that will
allow the Government to coordinate their Past Performance issue(s) with you as the Prime offeror. If Offerors do
not submit such written consent, then the Government will address any past performance issues directly with the
principal subcontractor or critical team member and the Offeror will forfeit the opportunity to participate in any
related discussions. Consequently, for any principal subcontractors and critical team members that do not provide
such written consent, provide a point of contact (name, address, phone number, and email address) with which the
Government may coordinate these issues and obtain any responses as needed.
Offerors are reminded that the Government may use information other than that provided by the offerors in their
proposals to evaluate past performance. The Government may use Past Performance information obtained from
sources other than those identified by the offeror. The Past Performance Information Reporting system (PPIRs) will
be the primary method used to evaluate Past Performance. It is incumbent upon the offeror to explain the relevance
of the data provided. The Government does not assume the duty to search for data to cure the problems it finds in
the information provided by the Offeror. The burden of providing thorough and complete past performance
information remains with the Offeror.
(a) Contract Data
Provide all the information identified below separately for each contract. Additionally, provide this information
electronically as a separate file on CD-ROM, which contains your Past Performance proposal in a Word Table in the
format depicted below:
Relevant Contract Data
Prime (P), or Sub (S)
1. Contractor Name P1 P2 P3 P4 PX S1 SX
2. Title of contract
Page 25 of 27
3. Contract number/type
4. Procuring agency
5. Description of product or service
6. Period of performance
7. Place of performance 1 and CAGE Code/ DUNs #
8. Dollar value of contract
9. Acquisition Phase(s) of Contract, e.g., SDD,
10. CPARs? - CPAR completion date - on DOD PPIRS? 2
12. Relevancy 3
• Place of Performance should be the same as being proposed in this solicitation. If different please include
• CPARs (yes/no) - CPAR completion date - on DOD PPAIS (yes/no) (Indicate whether or not any CPARS
have been completed and identify the last CPAR completion date and if it is currently on DoD PPAIS)
• Relevancy - Concise assessment of the degree of relevancy the past performance for that contract has to
the solicitation, identifying tasks and/or aspects of the effort undertaken on the contract that are relevant to
the program. Also provide your assessment of the relevancy of the contract in terms of one of the
following ratings: Somewhat Relevant (S), or Very Relevant (V).
• Note whether the contract met or exceeded small business, small disadvantaged business, small business
HUB Zone, veteran-owned small business, service disabled veteran owned small business, women-owned
small business participation and subcontracting goals.
Offerors are required to explain what aspects of the contract are deemed relevant to the proposed program,
and to what aspects of the proposed effort they relate. At a minimum, identify key or critical tasks of the solicitation
and indicate the relevancy of the “past performance” contract to these tasks. Also identify where contract
performance took place and provide rationale why it is relevant to the solicitation if the location is different from
where the related effort is proposed to take place.
(c) Past Performance Information
For each contract identified in response to paragraph (a), describe performance efforts and the extent to which
they are relevant to this solicitation when addressing the areas below. Discussion of the areas below should provide
a brief description of performance in delivering quality products in each of the following areas: 1) meeting technical
requirements (i.e., the quality of your technical performance, e.g., performing analysis, design, testing)., 2) meeting
schedule requirements, (i.e., schedule performance, e.g., on time or late delivery, modification of original schedules
and reasons for any changes), 3) controlling contract cost, i.e., cost performance, (e.g., on time or late delivery,
modification of original schedules and reasons for any changes)., and 4) managing the contracted effort, (e.g.,
program management, cooperation with customer, subcontract management).
(d) Demonstrated Systemic Improvement
Identify those systemic improvement actions taken to resolve past problems, identified in (c), and
demonstrate the extent to which it will benefit the instant contract. Provide the records of such results and indicate
where they are documented, preferably in Government record systems. Describe the techniques, elements, and tools
used to correct problems on the contract and, if applicable, how these techniques, elements, and tools will be used
during this program.
3.2 Past Performance Data Requirements
Page 26 of 27
Provide all the information identified below separately for each contract. Provide a summary of the
Customer’s Points of Contact in a MS Word Table using the format below which is illustrated with an example.
Include an electronic copy of this table in MS Word on a CD.
1. Offeror’s Name 1. Contract #, Customer’s 1. CPARS? Recent? Point of Contact’s
(Prime, Principle Name 2. Questionnaire # __ Name;
Sub, or Critical Team Sent? Phone Number,
Member, JV/SLE, 4. Offeror’s Role (e.g. 3. For Subs - Agreement Fax Number and
JV/SLE Member) prime or sub) to allow Coordination E-mail address
AB (prime) 1. N009, RYP 1. CPARs: No Al (PM)
2. Questionnaire #1: 444-444-4444, fax
- Sent 5/4/05 555-555-5555,
4. Prime 3. N/A Al@RYP
1. CPARs: No Sue (PCO)
2. Questionnaire #2: 333-333-3333
- Sent 5/4/05 fax 222-222-2222
3. N/A Sue@RTP
1. CPARs: No Joe (ACO)
2. Questionnaire #3: 111-111-1111
- Sent 5/4/05 fax 888-888-8888
3. N/A Joe@ RYP
AB (prime) 1. N008, L&M 1. CPARs: Yes/No Sue (PCO)
2. Questionnaire # 1: - 333-333-3333
Sent 5/4/05 fax 222-222-2222
4. Sub 3. N/A Sue@AB
NNB (sub) 1. N007, RST 1. CPARs: Yes/Yes Sue (PCO)
2. Questionnaire: - 333-333-3333
4. Prime Not Sent fax 222-222-2222
3. Agreement: Yes Sue@NNB
4.0 VOLUME: 4 - PRICE PROPOSAL
4.1 Volume Content
(a) This Volume shall contain the information requested below and shall include a copy of Section B with the
Contract Line Item (CLIN) Unit Prices and for evaluation purposes, the Total Prices filled in using the maximum
quantities/value in the solicitation and the instructions below.
(b) All price and price supporting information shall be contained in section B and the price proposal. No
price or pricing information shall be included in any other technical volume including cover letters. Offerors are
responsible for submitting sufficient information to enable the Government to fully evaluate their price proposal.
4.2 Ground Rules and Assumptions
(a) As this is a competitive acquisition with adequate price competition anticipated, the price documentation
requested is not considered cost or pricing data and shall not be certified in accordance with FAR 15.406-2.
However, in the event that adequate price competition does not exist after receipt of proposals, the PCO will need to
obtain cost or pricing data pursuant to FAR Part 15.
Page 27 of 27
(c) The offeror shall provide sufficient information to support its price as well as an explanation of all ground
rules and assumptions that affect the price estimates. Any apparent imbalances in the pricing, high or low proposed
prices as compared to historical data, or any other anomalies should be fully explained. Topics to be addressed
include, but are not limited to, investments, programmatic variables (e.g., inflation/escalation, location, make/buy
decisions, prime/subcontractor relationships, and business base concerns), etc.
4.3 Price Information
(a) Reasonableness and Consistency between the Technical and Price Volumes. Demonstrate that the unit
prices and the total evaluated price are reasonable and are commensurate with the work required by the solicitation.
Refer to specific sections in the technical volume as needed to illustrate the consistency between the Price and
Technical Volumes. Any inconsistency between promised performance and price should be explained in the
proposal as well as any appearance of unbalanced pricing.
(b) The Government is not soliciting any investments.
(c) Identify the proposed prices for each contract line item number (CLIN) as specified in Section B of this
solicitation. The offeror shall sum up the proposed Total Prices by contract year, and provide a total overall price of
the proposal using maximum quantities, and submit a complete Section B.
4.4 Other Costs
Identify additional costs, if any, that would be incurred in performance of this effort that has not been
identified in the solicitation. Identify in detail the costs that would be incurred and describe in detail the
performance that would cause these costs. Identify and justify reductions, if any, that the offeror believes should be
applied by the Government to adjust the evaluated price. Also, describe any assumptions with regard to
Government’s actions (e.g. providing resources whether it be equipment or people) that enabled the proposed price
to be lower and identify the amount by which it is lower.
5.0 VOLUME 5 - EXCEPTIONS, DEVIATIONS AND WAIVERS
This volume must include a certification that it contains all exceptions, deviations, and waivers that the offeror
takes from the provisions of the solicitation and its applicable documents. An exception is where an offeror states it
will not comply with a requirement, usually involving contract terms and conditions. A deviation is where an
offeror states it will not comply with a requirement but proposes an alternative to meet the intent of the requirement,
usually involving a specification. A waiver is where an offeror requests authorization for the Government to accept
an item, which will depart from, specified requirements, but would nevertheless be considered suitable. Exceptions,
deviations, and requests for waivers may cause proposals to be considered deficient. An assumption or condition
shall not be considered an exception, deviation, or request for waiver as defined herein.
Provide a detailed description for each exception, deviation or request for waiver. Indicate your difficulty with
the applicable requirement and your proposed solution. Specifically identify the portion of the solicitation and your
proposal, which are affected. If there are no exceptions, deviations or waivers, provide a one page Volume 5 in the
Executive Summary stating so.
(End of Summary of Changes)