SOLICITATION NOTICE
V -- Engine Module Movements and Tracking
- Notice Date
- 3/17/2003
- Notice Type
- Solicitation Notice
- Contracting Office
- N00140 700 Robbins Avenue, Building 2B Philadelphia, PA
- ZIP Code
- 00000
- Solicitation Number
- N0014003RTBD
- Archive Date
- 4/17/2003
- Point of Contact
- John Striano 215-697-9603
- Description
- FISC Norfolk Det Philadelphia will be conducting an industry forum in Philadelphia, PA on 19 March 2003 at 9:00 AM EST. Industry is invited to attend the conference to comment on the upcoming Engine Tracking requirement on behalf of the Naval Support Activity, Philadelphia, PA. Anyone interested in attending must contact John Striano at FISC Norfolk Det Philadelphia, (215) 697-9603 no later than 18 March 2003. The intent of the proposed engine tracking solicitation is to ascertain the feasibility of and projected costs to expedite, monitor, transport, and report on the movement of an estimated 2000 annual ready-for-issue (RFI) and non-RFI aircraft engine and engine module movements. This effort does not include local movements of less than 50 miles. For shipments originating Outside Continental United States (OCONUS), movement will occur from Continental United States (CON US) Air Mobility Command (AMC) ports at Naval Station (NS) Norfolk, VA; Travis Air Force Base (AFB), CA; Dover AFB, DE; McGuire AFB, NJ; Charleston AFB, SC; and McChord AFB, WA for further transfer to destination. Movements are primarily made between Naval Air Stations, commercial and organic repair sites, defense depots, and AMC ports. Visibility of all movements must be achieved by feeding pick up and delivery data to the Global Transportation Network (GTN). The contractor is expected to coordinate and monitor the movement of all aircraft engines and engine modules moving within CONUS. Engines and engine modules range from 150 to 9000 lbs (see attach 1) and some require flatbed to move. Transit times should not exceed an average of 3 business days from notification (before 12 noon) for movements moving between 50 and 1000 miles and an average of 5 business days for mov ements over 1000 miles. Contractor is responsible for being able to identify the location of the shipments during transit and providing signed proof of deliveries upon request. The contractor will establish a link between GTN and NAVAIR?s Aircraft Engine Management System (AEMS). A recent study showed that of 553 in-transit engines more than 5 days old, 305 of the transfers had Transportation Control Numbers (TCNs). Of the 305 transfers with TCNs, 123 were not yet visible in GTN, and numerous transfers had improperly formatted TCNs. Therefore, one of the biggest problems is proper TCN assignment. The Contractor must address this problem in their proposal- including a plan on how coordination with squadrons, AMC, commercial contractors, the Defense Logistics Agency, Navy Transportation Officers, and other holders of aircraft engines might resolve this problem. In summ ary, Navy is interested in movement, visibility, and accountability for aircraft engine and engine module movements within CONUS, Navy goals are to reduce transit time, increase in-transit visibility, develop reporting capabilities, and eliminate loss of assets.
- Record
- SN00281235-W 20030319/030317213747 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |