Loren Data's SAM Daily™

FBO DAILY ISSUE OF SEPTEMBER 24, 2005 FBO #1398
MODIFICATION

D -- Automated System for In Transit Visibility/Total Asset Visibility of Ocean Shipments

Notice Date

9/22/2005
 

Notice Type

Modification
 

Contracting Office

Surface Deployment and Distribution Command - W81GYE, ATTN: SDAQ, 200 Stovall Street, Alexandra, VA 22332-5000
 

ZIP Code

22332-5000
 

Solicitation Number

W81GYE-05-S-0003
 

Response Due

9/23/2005
 

Archive Date

11/22/2005
 

Point of Contact

Judy Stevens, 703-428-2035
 

E-Mail Address

Email your questions to Surface Deployment and Distribution Command - W81GYE
(stevensj@sddc.army.mil)
 

Small Business Set-Aside

N/A
 

Description

QUESTIONS AND ANSWERS Answers below are provided in response to questions pertaining to the Request for Information (RFI) W81GYE-05-S-0003 posted on 9/16/05 . No further questions pertaining to the subject RFI will be accepted. 1. Is G3 or G6 sponsoring this requirement? It makes a difference in our response. Answer: G3 2. Is this part of the Container Management requirement that was put on hold for a while? Answer: No 3. Is there an incumbent for this requirement? Or is it a new requirement? If so, could you provide the incumbents name, contract #, contract value and dates? Answer: There is no incumbent contract. This is a request for information only for market analy sis. 4. Is the response date of 23 Sept correct? Answer: Yes, responses are due by 3 p.m. on 23 Sep 05. 5. Is there a current program with an incumbent working on this or an associated requirement? Answer: No 6. Will the government provide a 1 week extension for the closing date on the RFI? Answer: No, this is time sensitive. 7. Is the government looking for an existing COTS Supply Chain system? Answer: COTS preferred due to quicker implementation and potentially lower costs, however; COTS is not a requirement. 8. The first paragraph state provide an automated system to track ocean shipments. Later in the document there is reference to track 24,000 domestic shipments. Are we to assume that the domestic shipments are the shipment movements from the Origin to the s eaport of embarkation --- or is the system actually intended to track domestic shipments, i.e. the New Cumberland to Ft Bragg shipments, that are no Ocean shipments? Answer: The system is to track domestic shipments that are the first leg of an ocean movem ent (e.g., Fort Hood unit move by rail to SPOE and then ocean movement to destination) and domestic movements that have origin/destination in CONUS. 9. Who are the expected users of this system? Answer: G3 10. What is the definition of a shipment? For example, is a shipment a container or a single package. As a follow-up, if a shipment is not a container, then what is the relationship to a pallet and container? Answer: For containerized shipments, shipment is the conveyance (e.g., truck trailer, container). For breakbulk shipments (normally vehicles), shipment is the piece. 11. What is real-time NIPR? Our understanding is the NIPR is the NIPRNET. Is this true? Answer: NIPR is NIPRNET. 12. Is the system boundary around the back-end? That is, the system being addressed does not include the actual collection of information (e.g. RFID). It is the IT infrastructure to interface to collection elements, store the data and make it available. Answer: True, looking for a system that accesses available data. 13. How many system users are projected and at how many locations are they? By system users we mean, people who will access the system to get status information, reports, etc. Number of people and locations has not been determined. Answer: Number of peop le and locations has not been determined. Answers to both will be multiple. 14. You requested information on number of people to provide O&M support. We are assuming (based on our Question #3 above) that O&M is limited to the IT infrastructure as opposed to maintaining and operating the field collection components. Is that true? Answer: True, O&M is limited to IT infrastructure. 15. You mention interfaces to our legacy system. Can you provide some examples? We are aware of some potential system such as WPS BPS, but would like to know what other you envision. Answer: WPS, IBS, GFM are examples of legacy systems. 16. Is it possible to have an extension until September 29, 2005? The deadline for questions (4 working days form release of the Sources Sought on September 16th) is Sept. 22nd which gives less than 24 hours to incorporate the answers into the submission due on Sept 23rd? Answer: Unfortunately, no extension. We are trying to provide estimates on a very tight timeline. 17. Should this RFI response address an automated software system? Or should it include the provision of infrastructure? Answer: Both. Ultimately, we would envision a contractor tying into systems of record that have our tracking data. 18. Is this proposal to address provisioning of services and/or software? Answer: Both 19. Should the response address the communication (software) systems? Answer: Yes 20. Is the provider expected to build interfaces into legacy systems? How many legacy systems?Answer: Yes. Legacy systems are WPS, IBS, and GFM. What Operating Systems do the legacy systems utilize? Answer: Unix HP Unix and Sun Solaris 21. Based on the wireless requirement, are there security requirements? (FIPS140, encryption/decryption) Answer: Yes. Must meet DoD standards.
 

Place of Performance

Address: Surface Deployment and Distribution Command - W81GYE ATTN: SDAQ, 200 Stovall Street Alexandra VA

Zip Code: 22332-5000

Country: US
 

Record

SN00901673-W 20050924/050922212249 (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 |