SOLICITATION NOTICE
R -- Professional, Administrative and Management Support Services
- Notice Date
- 2/22/2002
- Notice Type
- Solicitation Notice
- Contracting Office
- NAVICP-Mech, Code 0272.20, PO Box 2020, 5450 Carlisle Pike, Mechanicburg,PA 17055
- ZIP Code
- 17055
- Solicitation Number
- N0010402QQ343
- Response Due
- 3/1/2002
- Archive Date
- 3/31/2002
- Point of Contact
- D. A. McLeod 717-605-4239 D. A. McLeod, Code M0272.20, 717605-4239
- Description
- The Government intends to negotiate using open market procedures to procure programming support for ARAMS Web update for Military Sealift Command. The contractor shall provide in part 1.0 REQUIREMENT 1.1 The contractor shall provide Web Objects programming support to update the ARAMS WEB application hosted at the MSC ARAMS warehouse Chesapeake, VA. The application was developed using WEB OBJECTS 4.5 and uses a Sybase ASA 7.x database. The application supports multiple warehouses. The contractor shall update the application at MSCHQ (Washington, DC) and MSC ARAMS Warehouse (Chesapeake, VA) and provide source code and documentation of changes to MSCHQ, Bill Merkle in accordance with the deliverables format. These warehouses provide used parts to MSC ships. The application can be viewed at http://164.231.46.15/ 2.0 TASKING 2.1 The contractor shall provide WEB O BJECTS programming, testing and installation services to update the existing ARAMS Web Code. 2.2 The conctractor shall fix Transaction Report. The dba assigned to this project is Jason Jardine from SYSBASE, (202) 685-5623. See Enclosure (2.1) of SOW. 2.2.3 End Value (24) = Begin Value (3) + ((Receipts (17) + Haystack (Gain) (21) + Merges (Gain) (22)) ? (Issues (18) + Losses (19) + Surveys (28) + Turn-ins (20) + Haystack (Loss) (21) + Merges (Loss) (22))) for any transaction period 2.2.4 End Line Item Count (25) = Begin Line Item Count (4) + (Receipts (11) ? (Issues (12) + Losses (13) + Surveys (27) + Turn-ins (14) + Merges (16))) for any transaction period. 2.3 The contractor shall change 1348-1A format. See enclosure (2.3) of SOW. 2.4 The contractor shall add the Special Material Identification Code (SMIC) field to the Stock Record Card (SCR). See enclosure (2 .4) of SOW. SMIC is a two-digit alpha or numeric weapon system code. This code identifies the end item for which a requirement has been submitted. 2.5 The contractor shall add Date validated, SMIC, and COG to the advanced search. See enclosure (2.5) of SOW. 2.6 The contractor shall allow batch printing of 1348-1A for turn-ins. 2.7 The contractorshall change the import routine to search under National Item Identification Number (NIIN). The current import routine looks at NSN (NSN = Federal Supply Class (FSC) + NIIN). Ignore the FSC of the NSN (the first 4-digits) and search using the 9-digit NIIN. The last 9 positions (00-123-4567) are the National Item Identification Number (NIIN) and identify the specific item. The part / cage search capability should be retained. 2.8 The contractor shall add the capability to change unit of issues without generating losse s or gains. I.e., If you have 12 parts with the unit of issue of each (ea) and the unit of issue is changed to dozen (dz), the current system creates a loss for the 11 parts. The system should change the unit of issue, the quantity and the price without generating a loss. I.e., If you have 12 (ea) parts at $1.00 each and based on a Haystack or manual validation you change it to 1 (dz) at $24.00. You should not gain or lose any items. The price different would be reflected on the transaction report under Haystack. 2.9 The contractor shall standup the software on a test site for MSC users acceptance testing. 2.10 The contractor shall correct any problems noted during acceptance testing or as problems arise. 2.11 The contractor shall update code at MSCHQ and MSC Chesapeake. 3.0 SOFTWARE DELIVERABLE FORMAT 3.1 MEDIA All software will be delivered either via diske tte or compact disk. Software will not be accepted via e-mail. This includes any changes to software resulting from Independent Verification and Validation (IV & V) testing. 3.2 DETAILED DELIVERY FORMAT The deliverable will be composed of two main directories, the existing productions environment and the current release being delivered. The directories will be named with the appropriate version and application name abbreviation (e.g. TMS V1.0, TMS V1.01). The first main directory will consist of a number of sub-directories representing the major components of the application's production environment (e.g., dlls, scripts, reports, executable, source code, documentation, etc.) The number of sub-directories will obviously vary from application to application. The naming convention for each directory will be left up to the discretion of the developer and must remain c onsistent from release to release. The second main directory will consist of only those sub-directories having changes. For example; if a maintenance release only consists of adding a few dlls, the only sub-directories would be a dll sub-directory and its contents would only be those added dlls. If a functional change required a new documentation and a resulting new user manual, the documentations sub-directory would only include the new user manual. On the subsequent release, the above examples would be rolled into the production environment directory. If during IV & V testing it becomes necessary to make changes, the above format will still be required. During the IV & V testing period all changes will be rolled into the original deliverable with each subsequent IV & V deliverable reflecting all previous changes. The result is each IV & V deliverable being abl e to stand on its own as a final deliverable. Absolutely no deliverables containing only partial changes will be accepted. 3.3 DELIVERY LETTER A delivery letter will accompany all deliverables. This document will be required in addition to any other MSC specified documentation. The letter will provide: ? A detailed description of what is being delivered to include a complete list of files in each sub-directory. ? What type of change (new functionality, fix a problem, etc.). ? Detailed instructions for installation (e.g., the order of scripts requiring to be run). ? A point of contact with phone number of the developer. 4.0 PLACE OF PERFORMANCE ARAMS EAST COAST, Chesapeake, VA. MSCHQ, Washington Navy Yard, Washington, D.C. 5.0 PERIOD OF PERFORMANCE One year from date of award 6.0 FURNISHED EQUIPMENT/MATERIAL/SERVICE ARAMS Web Source Code as of 11/02/2001 (MSC will FTP as required) 7.0 SECURITY None ****
- Record
- SN00030076-W 20020224/020222213457 (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 |