June, 2021
www.us-tech.com
Integrating ERP with BPM Programmers Using an API
Continued from previous page
ponent Object Model interface technology is the basis for several other Microsoft frame- works, including OLE, ActiveX, COM+, and DCOM, among others. With a basic understanding of the BPM
API, it is then possible for the customer’s internal development team to write the API. It is also possible to outsource the project. BPM and its European partner, Adaptsys Group, have extensive experience writing custom APIs. Competent third-party devel- opers have also been successful in building
APIs, though this usually requires at least some interaction with BPM’s technical team and a thorough project specification.
Applications in Manufacturing
It is fairly straightforward to
hook real-time monitoring into an MES or ERP to notify when a job is completed or if there is an issue that a technician must address. Moving raw goods inventory (blank programmable devices) into finished goods (pro- grammed/tested devices) is also fairly easy. The API can also be set up to alert the supervisor or technician (by text message or email) upon completion of jobs, or to notify them when it is time to switch out trays or reels. One large European automo-
tive contract manufacturer tasked BPM’s partner Adaptsys Group with developing an API that functions as an automated work order to integrate its BPM automated programming sys- tems with its MRP system. In production, the system creates an electronic work order, operator checklist and performs finished goods allocation. The automated work order is
written in OPC UA, a machine- to-machine communication pro- tocol for industrial automation developed by the OPC Foundation. OPC UA is an open- source, java-based programming language that is focused on com- municating with industrial equipment and systems for data collection and control. BPM’s API is agnostic when it comes to pro- gramming — as long as it inter- faces with COM. The interface is a simple
web-based form. The data entry process is used to set up the ini- tial data for a given program- ming job. The first field in the form specifies the programmed device name. It is later cross-ref- erenced in a second form as a unique name for the parts to be programmed. This programming name can
then be used multiple times to program the same device type with the same program code, yet still made unique by the use of a
“Job ID” from BPWin. Other fields are used to set specific information related to the job, which is later called upon to create the job sheet. The job sheet can be used by a produc- tion operator to scan barcodes to automate the setup of the BPM Microsystems device handler. The job sheet is a PDF that is created
after the original data is saved to the SQL database. The system pulls in all the linked data to populate the PDF, which is then auto- matically downloaded. This PDF contains the required job data in the form of barcodes
Page 47
that can be used by the operator to set up the system.
Setting Up and Running the APS Following is an example of a manufac-
turing process flow to handle devices to be programmed, from the time they enter the production environment to the time they are programmed and tested, and finally when they move to finished stock.
l Receive Job Sheet. The sheet contains required fields in barcode format.
l Barcode Job. This contains a link to the .abp file (BPM’s proprietary job file format
Continued on page 51
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76
