SOLICITATION NOTICE
D -- OPAL INTEGRATION UPGRADES
- Notice Date
- 7/9/2003
- Notice Type
- Solicitation Notice
- Contracting Office
- Department of the Air Force, Air Force Materiel Command, AFFTC - AF Flight Test Center, 5 S WOLFE AVE, Edwards AFB, CA, 93524-1185
- ZIP Code
- 93524-1185
- Solicitation Number
- Reference-Number-FQ280531610200
- Response Due
- 7/18/2003
- Archive Date
- 8/2/2003
- Point of Contact
- Evelyn Ross, Contract Negotiator, Phone 661-277-7799, Fax 661-275-7853,
- E-Mail Address
-
evelyn.ross@edwards.af.mil
- Description
- The Air Force Flight Test Center (AFFTC), Edwards AFB (EAFB) intends to solicit and award a sole source, Firm-Fixed Price contract, under Federal Acquisition Regulation (FAR) Part 12, Acquisition of Commercial Items and FAR 13, Simplified Acquisition Procedures, to Bridge Technologies, 4474 Clipper Cove, Destin, FL. This acquisition is unrestricted. The Standard Industrial Classification Code is 7373. The NAICS code is 541512. The following services will be procured: 1. OBJECTIVE: the mission of the Civil Engineer /Transportation directorate is to provide facility and transportation support for the Air Force Flight Test Center and 49 associate units; to operate, maintain, and repair over 7 million square feet of facilities and 60 miles of lakebed runways; to manage all vehicle operations and surface/air transportation. Train military and civilians in support of Air Expeditionary Forces. The objective of this Statement of Work (SOW) is to provide EAFB with efficient, effective implementation of required updates, changes and improvements to the OPAL Integration tool to maintain and upgrade the interface between our current Commercial Maintenance Management System (CMMS), Maximo, and the Air Force legacy system, Interim Work Information Management System (IWIMS). With the exception of the items/services specified as being government-furnished in Section III hereof, the contractor shall provide all resources (labor and materials) to perform the work within this SOW in a manner that meets the objectives stated herein. 2. INTEGRATION MODIFICATION REQUIREMENTS: Provide all necessary work, training, documentation, processes, test and validation of modifications to OPAL integration tool and CMMS databases to ensure interface between systems supports work processes of CE. Work in conjunction with other necessary CE personnel and contract personnel to complete modifications by 30 September, 2003. 3. COMPLETE ALL WORK NECESSARY TO TRANSFER WORK ORDER DATA FROM MAXIMO TO IWIMS: Provide transfer process documentation in digital and hardcopy formats, complete implementation of process, and validate data transfer for new work orders and update work orders. 3.1. New Work Orders: 3.1.1. New work order transfer process documentation. The documentation will include the rules and field mapping of the MAXIMO data structures to the IWIMS application fields to be implemented in the OPAL project files. The rules and mappings will be created from the client?s user requirements for new work orders, at attachment A. Acceptance will be through a meeting with client technical team to review the documentation?s inclusion of the required client user requirements, and acceptance by client government representative. 3.1.2. New work order process implementation. Create or modify OPAL Project file(s) to implement the transfer of MAXIMO data to the mapped IWIMS application fields as outlined in the accepted ?New work order transfer process documentation?. Acceptance is based on the acceptance of the ?New work order data transfer validation? component. 3.1.3. New work order data transfer validation. The validation for the transfer of MAXIMO data to IWIMS will be conducted by successfully processing no more than one month of production MAXIMO new work order data. Acceptance will require verification that the data values in IWIMS contain the values from MAXIMO as outlined in the accepted ?New work order transfer process documentation ?. 3.2. Update work orders: 3.2.1. Update work order transfer process documentation. The documentation will include the rules and field mapping of the MAXIMO data structures to the IWIMS application fields to be implemented in the OPAL project files. The rules and mappings will be created from the client?s user requirements for update work orders. Acceptance will be through a meeting with client technical team to review the documentation?s inclusion of the required client user requirements and acceptance by client government representative. 3.2.2. Update work order process implementation. Create or modify OPAL Project file(s) to implement the transfer of MAXIMO data to the mapped IWIMS application fields as outlined in the accepted ?Update work order transfer process documentation?. Acceptance is based on the acceptance of the ?Update work order data transfer validation? component 3.2.3. Update work order data transfer validation. The validation for the transfer of MAXIMO data to IWIMS application interface will be conducted by successfully processing no more than one month of production MAXIMO update work order data. Acceptance will require verification that the data values in IWIMS contain the values from MAXIMO as outlined in the accepted ?Update work order transfer process documentation?. 4. Complete all work necessary to process labor hours data from MAXIMO to IWIMS. Provide transfer process documentation in digital and hardcopy formats, complete implementation of process, and validate data transfer. 4.1. Regular labor hours. 4.1.1. Regular labor hours transfer process documentation: The documentation will include the rules and field mapping of the MAXIMO data structures to the IWIMS application fields to be implemented in the OPAL project files. The rules and mappings will be created from the client?s user requirements for regular labor hours. Acceptance will be through a meeting with client technical team to review the documentation?s inclusion of the required client user requirements, and acceptance by client government representative. 4.1.2. Regular labor hours transfer process implementation: Create or modify OPAL Project file(s) to implement the transfer of MAXIMO data to the mapped IWIMS application fields as outlined in the accepted ?Regular labor hours transfer process documentation?. Acceptance is based on the acceptance of the ?Regular labor hours data transfer validation? component. 4.1.3. Regular labor hours data transfer validation: The validation for the transfer of MAXIMO data to IWIMS application interface will be conducted by successfully processing no more than one month of production MAXIMO regular labor hours data. Acceptance will require verification that the data values in IWIMS contain the values from MAXIMO as outlined in the accepted ?Regular labor hours transfer process documentation?. 4.2. Overtime labor hours: 4.2.1. Overtime labor hours transfer process documentation: The documentation will include the rules and field mapping of the MAXIMO data structures to the IWIMS application fields to be implemented in the OPAL project files. The rules and mappings will be created from the client?s user requirements for overtime labor hours. Acceptance will be through a meeting with client technical team to review the documentation?s inclusion of the required client user requirements, and acceptance by client government representative. 4.2.2. Overtime labor hours transfer process implementation: Create or modify OPAL Project file(s) to implement the transfer of MAXIMO data to the mapped IWIMS application fields as outlined in the accepted ?Overtime labor hours transfer process documentation?. Acceptance is based on the acceptance of the ?Overtime labor hours data transfer validation? component. 4.2.3. Overtime labor hours data transfer validation: The validation for the transfer of MAXIMO data to IWIMS application interface will be conducted by successfully processing no more than one month of production MAXIMO Overtime labor hours data. Acceptance will require verification that the data values in IWIMS contain the values from MAXIMO as outlined in the accepted ?Overtime labor hours transfer process documentation?. 5. Complete all work necessary to process 561 schedule data from MAXIMO to IWIMS. Provide transfer process documentation in digital and hardcopy formats, complete implementation of process, and validate data transfer. 5.1. 561 schedule: 5.1.1. 561 schedule transfer process documentation: The documentation will include the rules and field mapping of the MAXIMO data structures to the IWIMS application fields to be implemented in the OPAL project files. The rules and mappings will be created from the client?s user requirements for 561 schedules. Acceptance will be through a meeting with client technical team to review the documentation?s inclusion of the required client user requirements, and acceptance by client government representative. 5.1.2. 561 schedule transfer process implementation: Create or modify OPAL Project file(s) to implement the transfer of MAXIMO data to the mapped IWIMS application fields as outlined in the accepted ?561 schedule transfer process documentation?. Acceptance is based on the acceptance of the ?561 schedule data transfer validation? component. 5.1.3. 561 schedule data transfer validation: The validation for the transfer of the MAXIMO data to IWIMS application interface will be conducted by successfully processing no more than one month of production MAXIMO 561 schedule data. Acceptance will require the verification that the data values in IWIMS contain the values from MAXIMO as outlined in the accepted ?561 schedule transfer process documentation?. 5.2. 561 back processing: 5.2.1. After the acceptance of the validated 561 schedule processing, all schedules from October 1, 2002 to the present that transferred from MAXIMO to IWIMS will be processed. Review by client technical team will occur within one (1) business day after written notification of the completed effort. The client resource management and technical team will have one (1) business day to review and comment on the results. The client government representative will accept the processing results as completed, in writing, and acceptance will be delivered to the vendor within the time frame provided. The notification of completion will contain the date and time of completion and required response time. 5.2.2. The client technical team will verify the data within the ORACLE table ?OPAL_561?. Contractors interested in this requirement should submit a complete technical package, which provides clear and convincing evidence that they can meet the Government?s requirements. In addition, the response should include any special requirements for a commercial contract (i.e., Commercial Financing, Warranty Provisions, Delivery Information, etc.) in accordance with FAR Part 12. Responses must be received no later than (NLT) 2:00 p.m., Pacific Standard Time, July 18, 2003. Responses should be submitted to: Directorate of Contracting, AFFTC/PKS (Evelyn Ross), 5 South Wolfe Avenue, Building 2800, Edwards AFB, CA 93524-1185, Fax: (661) 275-7853. This notice of intent is not a request for competitive proposals. However, the Government will consider all responses received within 10 days of the publication of this notice. A determination by the Government not to compete this acquisition based upon responses to this notice is solely within the discretion of the Government. Information received will normally be considered solely for the purpose of determining whether to conduct a competitive procurement. Facsimile responses are acceptable and must be received on or before the closing date. Telephone requests to be placed on a mailing list will not be honored.
- Place of Performance
- Address: EDWARDS AFB, CA
- Zip Code: 93524
- Zip Code: 93524
- Record
- SN00367371-W 20030711/030709213524 (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 |