SOURCES SOUGHT
D -- Shipping Container Inventory Software
- Notice Date
- 7/25/2005
- Notice Type
- Sources Sought
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- Department of the Air Force, United States Air Force Europe, Bagram Contracting, CJTF-76, Joint Contracting Center Bldg. 90; Bagram, Afghanistan, APO, AE, 09354
- ZIP Code
- 09354
- Solicitation Number
- W913TY-05-R-0068
- Response Due
- 8/5/2005
- Archive Date
- 8/20/2005
- Description
- 25 July 05 REQUEST FOR COMMENTS ON BAGRAM DRAFT STATEMENT OF WORK FOR A SHIPPING CONTAINER INVENTORY SYSTEM 1. Potential offerors are requested to provide the Government with written comments improving the clarity and quality, as well as challenging the requirements, of the Shipping Container Inventory System draft Statement of Work (SOW). It is the Governments? desire to issue a final RFP in Aug 05. Therefore, potential offerors are requested to thoroughly scrutinize the SOW and submit recommended improvements and clarification requests by the date/time specified in paragraph 3 below. 2. Draft Statement of Work (SOW) dated 25 July 05. Industry comments submitted in response to our 25 Jul 05 posting of the draft SOW will be considered and where applicable, or in the best interest of the government will be incorporated into the final SOW. We again ask/encourage you to carefully review the draft SOW and ensure a complete and thorough understanding of the services described therein. 3. Please forward your responses to SrA Stacy Bailey, Bagram Joint Contracting Cell, via e-mail, af.stacy.bailey@baf.afgn.army.mil, NLT 5 Aug 05. 4. Thank you for your time and interest in the Shipping Container Inventory System acquisition. We look forward to your constructive comments and assistance in development of a quality contract. Stacy Bailey Contingency Contracting Officer Bagram Joint Contracting Office STATEMENT OF WORK FOR CONTAINER INVENTORY SYSTEM 25 July 05 SECTION C.1. GENERAL. C.1.1. NEED. Contractor must provide personnel, software, hardware, and other materials as required to implement a shipping container inventory system for Bagram Air Field (BAF), Afghanistan C.1.2. BACKGROUND. The Joint Logistics Command (JLC) requires a shipping container inventory management system to be used for on-post container inventories and accounting at BAF. Pending successful implementation at BAF, scope would likely expand to other logistics hubs within the CJOA. Container management is a high priority within the Combined Joint Task Force-76 logistics area of responsibility. To date, there are over 13,000 containers located within the CJOA and there is no automated system in place to track, inventory, and manage them. The need exists for an inexpensive, automated, rugged, and technologically advanced system that can be incorporated within existing logistics management computer systems. Current inventories are conducted on foot with pencil and paper and are consequently very cumbersome and manpower intensive. Accuracy of the inventories is also limited due to normal human error and time between inventories. C.1.3. PERSONNEL. C.1.3.1. Personnel will be employed in a dry, high desert region and must be generally healthy enough to operate under such conditions. C.1.3.1.1. Contractor must be in place by 1 October 2005. The contractor will remain in place for a 6 month period, with the government maintaining options to extend beyond this initial duration. C.1.4. PHYSICAL SECURITY. NA. C.1.5. QUALITY CONTROL. C.1.5.1. The contractor shall establish and maintain a complete Quality Control Plan to ensure that the requirements of the contract are provided as specified. One copy of the contractor?s Quality Control Plan shall be provided to the contracting officer not later than the pre-performance conference. An updated copy must be provided to the contracting officer on the contract start date and as changes occur. C.1.5.2. The plan shall describe the methods for identifying and preventing defects before the level of performance becomes unacceptable. C.1.6. QUALITY ASSURANCE. The government will evaluate the contractor?s performance under this contract using the method of surveillance specified at in a Technical Exhibit. All surveillance observations will be recorded by the government. When an observation indicates defective performance, the Contracting Officer?s Representative (COR) will obtain the contractor representative?s initials on the record of the observation. C.1.6.1. Performance Evaluation Meetings. The contract manager may be required to meet periodically with the COR and contracting officer at the beginning of contract performance. Meetings will be scheduled as needed. The contractor may request meetings whenever a Contract Discrepancy Report is issued. The written minutes of these meetings shall be signed by the contracting officer, and COR. If the contractor does not concur with the minutes he shall state any areas of non-concurrence within 5 days of receipt of the signed minutes. C.1.6.2. Performance Requirements. Contractor performance will be evaluated using several surveillance methods. See Performance Requirements Summary (PRS) in technical exhibits section. C.1.7. HOURS OF OPERATION. C.1.7.1. Basic hours of operation are 0800 Local to 2000 Local. C.1.7.2. All major federally recognized holidays may be observed. C.1.7.3. The contractor must be available to meet any required emergency services on a 24 hour a day, 7 days a week basis, with the exception of the aforementioned holidays. C.1.8. CONSERVATION OF UTILITIES. NA. SECTION C.2. DEFINITIONS. C.2.1. STANDARD DEFINITIONS C.2.1.1. Acceptable Quality Level (AQL). The AQL is the maximum percent defective that, for purposes of sampling inspections can be considered satisfactory. C.2.1.2. Contracting Officer. A person duly appointed with the authority to enter into and administer contracts on behalf of the U. S. Government. C.2.1.3. Contracting Officer Representative (COR). An individual designated by the contracting officer to act as his representative to assist in administering a contract. The source and authority for a COR are contained in the written letter of designation. C.2.1.4. Customer Complaint. A means of documenting certain kinds of contract service problems. A government program that is explained to every organization that receives service under this contract which is used to evaluate a contractor? performance. C.2.1.5. Defective Service. A service output that does not meet the standard of performance associated with it in the Performance Requirements Summary (PRS). C.2.1.6. Government Property. All property owned or leased to the Government or acquired by the Government under the terms of the contract. Government property includes both Government furnished property and contractor acquired property as defined in FAR 45.101. C.2.1.7. Government Property Administrator. An authorized representative of the Contracting Officer appointed in writing to administer contract requirements and obligations relative to Government Property (FAR 45.101). C.2.1.8. Lot. The total number of service outputs in a surveillance period, as defined in the Performance Requirements column of the PRS. C.2.1.9. Performance Requirement. The point that divides acceptable and unacceptable performance. When the method of surveillance is other than random sampling, the performance requirement is the number of defectives or maximum percent defective in the lot before the government will effect the price computation system in accordance with the Performance Requirements Summary and the Inspection of Services Clause. C.2.1.10. Performance Requirements Summary (PRS). Identifies the specific tasks of the contract that will be evaluated by the government to assure contract performance standards are met by the contractor. C.2.1.11. Quality Assurance. Those actions taken by the government to assure services meet the requirements of the Statement of Work (SOW) and all other service outputs. C.2.1.12. Quality Assurance Surveillance Plan (QASP). An organized written document used for the quality assurance surveillance. The document contains specific methods to perform surveillance of the contractor. C.2.1.13. Quality Control. Those actions taken by a contractor to control the performance of services so that they meet the requirements of the PWS. C.2.1.14. Random Sampling. A sampling method in which each service output in a lot has an equal chance of being selected. C.2.1.15. Sample. A sample consists of one or more service outputs drawn from a lot. The number of outputs in the sample is the sample rate. C.2.1.16. Sampling Guide. The part of the surveillance plan which contains all the information needed to perform surveillance of the service outputs by the random sampling method of surveillance. C.2.2. TECHNICAL DEFINITIONS. None. SECTION C.3. GOVERNMENT FURNISHED PROPERTY AND SERVICES. Office space with local area network connectivity will be provided by the government. Basic services and utilities will be provided to the contractor to include utilities, postal or installation distribution, telephone, custodial services, refuse collection, insect or rodent control, grounds maintenance, police or fire protection, emergency medical treatment, housing, dining facility access, laundry, and all other services normally provided to deployed personnel. SECTION C.4. CONTRACTOR FURNISHED ITEMS AND SERVICES. Contractor will provide all other required services, hardware, software, and other material needed to perform the container inventory system. C.4.1. GENERAL. Except for those items or services specifically stated to be Government furnished in Section C.3., the contractor shall furnish everything required to perform this contract. SECTION C.5. SPECIFIC TASKS. C.5.1. SYSTEM SETUP TIMELINES. The system must be setup with a prototype sample inventory (approx 10% or 600 containers) by 1 November 2005. The remainder of BAF containers should be inventoried by 1 Jan 2006. C.5.2. GROWTH AND FLEXIBILITY. As a new, as yet undefined requirement, the contractor must retain the ability to adapt and tailor the system as mission requirements develop and as the JLC directs. For example, additional data fields may be added, graphic interfaces may change, maps may be adjusted, etc. C.5.3. LABELING. Each individual container must be labeled with a specific, unique label or tag. Labels must be rugged, easily replaced, heat-resistant, weather-resistant, durable, and easily accessed by inventorying personnel. Due to the large number of containers, labels must also be inexpensive. Roving inventory teams must have the ability to replace missing, worn, or damaged labels on-the-spot and make minor additions/modifications to the data. C.5.4. INVENTORIES. The primary requirement is that at any given time, the JLC will have access to a complete, accurate inventory of containers on post at BAF. The level of detail is initially limited to individual shipping containers and generalized cargo contained within. Detailed inventories of container contents are not required, but could potentially be an expanded requirement. C.5.5. DATA. Some specific fields of data will be required for each individual container. These fields will be at a minimum: Container Number, Type (Dry, Refrigerated, Flat Rack, etc.), Location, Owner, General Contents, Date Arrived Station, and Leased/Detention. This list of fields is not all inclusive and must be flexible to change. C.5.6. QUERIES. JLC must have access to the database and have the ability to query specific details. Queries should be easily tailored. Examples: a count of 20 foot, refrigerated, Class I containers located in a specific yard. C.5.7. MOBILE DATA COLLECTION. The system should allow for mobile data collection and inventories. Inventory teams (US Army or KBR personnel) will conduct walk-around inspections and inventories of container yards and must have the ability to collect data and input data into the automated system on the spot. For example, during the course of a mobile inventory, if a container is discovered to be empty, the team must be able to record the new data using hand held devices and immediately update the centralized database. The system must allow for automated scanning of the container labels, utilizing some form of hand-held or mobile interrogator that has scan capability and data entry/modification capability. Labels or tags on double-stacked containers must be reachable. C.5.8. RFID. The system must be able to download SAVI Active Radio Frequency Identification (RFID) tag data. C.5.9. TRAINING. The contractor will provide training on system use to two primary military personnel who will utilize the system on a regular basis. Training will include management of the database, data entry, equipment use, trouble shooting, etc. The contractor will also develop a training package to be used by the primary military personnel to train additional users. C.5.10. GRAPHIC REPRESENTATION. A graphic, map-based function, showing general locations of containers on BAF grounds is required. The graphic interface should be user friendly and should easily drill down from visual representations to data fields. SECTION C.6. APPLICABLE PUBLICATIONS AND FORMS. None.
- Place of Performance
- Address: Bagram Joint Contracting Cell, BLDG 90, Bagram AB, AFG, APO, AE
- Zip Code: 09354
- Country: Afghanistan
- Zip Code: 09354
- Record
- SN00853980-W 20050727/050725212117 (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 |