REQUEST FOR PROPOSAL Enterprise Asset Track and Trace System (eATTS) RFP- J0802-EATTS-2015 Response to Clarification Questions II Question #9 Please clarify the technical information to Interface with ECX system. Response It is stated in the RFP that there is an existing warehouse Question #10 Response Question #11 Response Question #12 receipting and inventory management system managed by ECX. As such, there will be information that eATTS will need from ECX or send to ECX. This is to avoid duplicate entry of data and enable both systems to operate as efficiently as possible. For instance, the Goods Received Note (GRN) or Electronic Warehouse Receipt Number is generated by ECX. On the other hand, eATTS tracks and traces every bag but there will need to be a link between the bags being tracked by eATTS and the corresponding GRN numbers created and maintained by ECX. Therefore, a standard interfacing protocol will need to be mutually agreed and implemented to have both systems operate and leverage each other information in an integrated fashion. ECX already has experience in building and implementing similar interfaces. Regarding SMS system, please clarify if there is SMSC to interface with or should we propose SIM bank to send SMS from? ECX currently hosts and offers its own SMS-based service to disseminate market information either on pull or push bases. This service can be leveraged by eATTS. Bidders are of course encouraged to propose and suggest their own solution offering, if deemed necessary. Any requirements to track trucks GPS in the future? The scope of this RFP does not include this requirement. However, the evaluation of each offer does consider the scalability, extensibility, and additional future feature and functions of the proposed solution. Are existing HW IBM Blade Center H and HX5 able to support eATTS capacity requirements? Response Question #13 Response Question #14 Response Question #15 Response Question #16 Response The response to this question is dependent on the bidder’s solution, not on ECX. As such, the RFP clearly requires each bidder to propose the required hardware, system software, and RDBMS with indicative pricing, precisely so that ECX can determine whether or not its existing assets can host the proposed solution and if not, to understand the investment requirements. Do you have database license to support the new eATTS? See response to Question #12 above. To trace and track uniquely for each bag, please clarify if you are interested in RF ID solution. The decision to consider bar code tags is based on weighing the likely higher investment and sustainment costs associated with RFID based solution. However, the proposed solution needs be capable of allowing a migration from bar code tag to RFID tag in the future. Bidders may propose RFID based solution as an alternate option for consideration. Do you have any preference solution for eATTS while network is down? It is expected that the scanning of bar code tags should be designed to operate with or without connectivity to the central system assuming the scanned data can then be transferred/synchronized when connection is up. Bidders are expected to propose their practical and cost effective solution for such and other scenarios. Do you want separate tag to be in each bag for every transfer or you are looking for a single tag with history by removing all the previous tags. History must be maintained in order to ultimately produce a report describing the composition of the coffee origins making up the consignment being shipped to the international buyer as per prearranged contract. As stated in the RFP, the same bar code tag is expected to remain with the bag while the bag is in ECX possession and on arrival at the Exporters/Buyer warehouse and during processing. After processing and re-bagging for shipment to the international buyer, a separate bar code tag will need to be attached as discussed in the RFP. However, it is important to note that this new bar code tag will need to maintain the history of origins of the various bags (now mixed/combined in each bag after processing) collectively being processed to fulfill a specific contract/coffee blend/type.
© Copyright 2020