 |
|
EP Bridge FAQs
What is EP Bridge?
Why does EP Bridge require its own Windows 2000 Server?
Since QAD Enterprise Applications 2008® was written in Progress, why wasn't EP Bridge?
Why did you choose the OLE Automation and ODBC to interface to QAD Enterprise Applications 2008®?
Do you support printers and devices from different manufacturers?
Which QAD Enterprise Applications 2008® transactions does EP Bridge support?
What is meant by "Smart Label" Technology?
Is EP Bridge a standard, off-the-shelf solution? If so, how can it be customized to meet customer and internal data collection needs?
Is EP Bridge cost effective?
How long does it take to install EP Bridge?
Where is EP Bridge being used now?
A: EP Bridge is a state-of-the-art, user configurable (point and click) shop floor data collection interface to QAD Enterprise Applications 2008®. EP Bridge is designed not only to automate shop floor data collection, but to eliminate errors in data collection as well. In addition, EP Bridge features direct device interfacing with its Error Proof module , which, in addition to other functions, permits data acquisition from Programmable Logic Controllers (PLCs), scales and other shop floor devices while both controlling processes and collecting data for parts produced on the shop floor.
Q: Why does EP Bridge require its own Windows 2000 Server?
A: A data collection application is the perfect opportunity to off-load some of the burden that is often put on a host computer, especially since customer requirements have ratcheted up the intensity of data management associated with labeling. First of all, customer specific formats contain dynamic data that often comes from the host system via EDI. As such, it no longer makes sense to print a large batch of labels ahead of time. In addition, activities such as Lot Control and the trend toward "Error-Proofing" may drive up the need for labeling at work centers.
If there's one place where performance is paramount, it is on the shop floor. With a separate server, shop floor users won't have to compete with accounting for system resources. Additionally , EP Bridge operates in real-time mode, therefore error messaging and transaction posting occur with little or no delay.
In addition, a separate Win2000 server enables performing transactions even when QAD Enterprise Applications 2008® is not available , such as when the data line drops. Transactions will get queued up and submitted in proper sequence as soon as the host becomes available; with no impact to the end user. This is particularly handy in a 3-shift operation when there is daily scheduled downtime for performing system backups.
Having a separate server also enables fail-over functionality via MSCS clustering. This is the same technology used in website hosting that transfers application processing to another server, in the event that the primary server becomes unavailable. All this together allows a "High Uptime" system for the shop floor end user.
Q: Since QAD Enterprise Applications 2008® was written in Progress, why wasn't EP Bridge?
A: Though it can be done, Progress is not the best tool for accessing shop floor devices such as scales, PLCs, vision systems, etc. When originally developing EP Bridge , Freedom had a choice of using any language available. Microsoft tools were chosen as the source for language and database options. This provides the best environment for accessing devices as well as multiple databases. In addition, Microsoft provides flexibility, long-range support, as well as a platform with a solid enhancement path.
Q: Why did you choose the OLE Automation and ODBC to interface to QAD Enterprise Applications 2008®?
A: No source code modifications, ever. It also precisely mimics the NET UI interface that QAD is now favoring. In other words, it's how QAD does it .
More technically, of the several methods used to interface to QAD Enterprise Applications 2008®, OLE Automation has the most superior advantages. OLE Automation uses the current and stable QAD Enterprise Applications 2008® Frame formats for inputting data. ODBC is used to query the Progress database for data as well as messages. Performance benefits aside, this method provides robustness, system redundancy, upgrade simplicity and complete transaction history support. Better yet, it provides flexibility, scalability and substantially lower total cost of ownership. Lastly, this environment allows the capability of summarizing and verifying transactions before they are input into QAD Enterprise Applications 2008®, thus reducing or even eliminating input errors.
Writing in Progress certainly has its benefits, but it is not without issues. Development in Progress requires significant effort each time an QAD Enterprise Applications 2008® upgrade is performed. The initial cost of this may be appealing, but once a change or an upgrade (or fix) is required, you'll need everything from a project plan to a Purchase Order (and spare weekends). In addition to potential (and likely) performance issues, extra care is required to maintain true transaction history. Fortunately, the technologies available today have rendered obsolete the notion that everything should be done on the host.
CIM loading has its place as well. Experience has shown that the CIM interface does not necessarily behave reliably. In addition, the error message support is not as robust. This interface is best saved for other purposes that have lower transaction volume requirements. Hence, we do not use the CIM interface.
Q: Do you support printers and devices from different manufacturers?
A: Yes. We can provide a copy of Loftware's label design and print program, tightly integrated with EP Bridge , or you may elect to use our standard "IPL Label Designer". The IPL Label Designer allows you to design labels for Intermec "IPL" printers. This provides support to an entire array of printing devices including Intermec, Zebra and many others. In addition, EP Bridge currently interfaces with a vast assortment of input devices including Intermec, Keyence, Toledo Scales, Symbol and others.
Q: Which QAD Enterprise Applications 2008® transactions does EP Bridge support?
A: We support all common QAD Enterprise Applications 2008® transactions normally utilized on the shop floor. This includes (and is not limited to) Shipping, Receiving, Production Reporting, Cycle Counting, etc. We also enhance and automate many of the transactions through the use of labels. For example, once a container is received and a label is produced, other QAD Enterprise Applications 2008® transactions can be performed including the Transfer of location, Cycle Counting, Inventory Issue, etc., merely by scanning the serial number.
Q: What is meant by "Smart Label" Technology?
A: "Smart Label" refers to the way data is attached to a label's serial number. EP Bridge stores a wealth of information associated with each label, including part number, quantity, lot, etc. This way, just a scan of the label's serial number is required. The system is "smart" enough to grab all the peripheral data required to complete the transaction. This is a great way of streamlining input as well as reducing errors.
Q: Is EP Bridge a standard, off-the-shelf solution? If so, how can it be customized to meet customer and internal data collection needs?
A: Yes, EP Bridge is a standard, off-the-shelf solution. It supports all current versions of QAD Enterprise Applications 2008®. It also supports both Progress and Oracle databases. The solution contains an advanced user definable interface which allows for user security and automation of data collected to be set up at the administrator level. Thus, shop floor screens can be customized to meet unique requirements. Label printing is also controlled at the administrator level. It becomes easy to modify labels to meet the needs of the organization and customers.
Q: Is EP Bridge cost effective?
A: In many instances, employee time saved in shipping preparation and increased accuracy of functions pays for the system. The increase in inventory accuracy and the related results dramatically improve operations. A recent study completed by the Gartner Group found that real-time shop floor data collection improves the return on investment for ERP systems by 50 percent.
Q: How long does it take to install EP Bridge?
A: Once the Windows 2000 server is available and the RF equipment is received, the actual installation, setup and training averages less than one week, with two to three days being the norm.
Q: Where is EP Bridge being used now?
A: There are over 100 EP Bridge installations at manufacturers with large, multi-site operations as well as with those small, single-site installations. EP Bridge is being used in the Commercial Packaging Products industry, the Consumer Products industry, the Automotive industry, as well as the Electronics industry.