ERP Linking and Interface
JobLink/SQL (our proprietary SQL Import technology) is the standard means of interfacing the JobTime5 production scheduling software system to your Enterprise Resource Planning (ERP), your Manufacturing Execution System (MES) or even to a homegrown ERP or an local order entry system. Data can be refreshed as often and as frequently as re-scheduling is desired, which typically ranges from hourly to daily. For ERP systems also based on relational systems such as SQL Server, Oracle, DB2. Import execution requires about one second per thousand operations, on state of the art servers. For example, 1000 shop orders of 10 operations per order will import in about 10 seconds. This does not include time the ERP may require to prepare and load data into our companion JobTime Import Database, which typically can take 15 seconds to 2 minutes additional time, depending on local equipment, network speeds and the geographic location of your ERP database. . Imports can also be executed unattended, such as overnight, just prior to 1st shift, or at the end of each shift, or upon demand.
The JobLink/SQL companion JobTime Import Database contains all staging tables which are tailored to exactly match the structure of your local host data system. The data to be imported includes work orders (sometimes called shop orders or factory orders), the operation steps for each order, and secondary resources required, if any. Once data is imported into the staging tables, the next query moves relevant client data into corresponding tables and fields in JobTime5's data formats. JobLink/SQL also executes a stored procedure to automatically validate all of your imported data to verify data consistency with JobTime's requirements. For example, if an operation refers to a work center, this work center also needs to exist. If a job refers to a part number, this part number needs to exist. Each operation must have time standards defined as either setup and/or process rate. The most typical import data includes work orders, operation steps, BOM assembly links between work orders. Other optional data tables may include operation alternate route steps, and multiple resources required per operation. The client ERP can supply each operation's current completion status, as any combination of units complete, units to-go, hours spent, hours to go, or simply as operation percent complete. Validated data is moved into JobTime's official tables automatically.
Data which may need to be temporarily quarantined are reported in a Data Consistency report which displays reason codes for each quarantined data element.
JobLink/SQL assures that the host/ERP data will be imported consistent with JobTime’s data requirements, including referential integrity. This capability enables JobTime's finite scheduling to execute rapidly, accurately and seamlessly. Once installed and running smoothly for 30 days, follow-on support required is minimal.
JobLink/SQL can also be easily customized to populate JobTime's production scheduling constraints. This is typical where the host ERP system may not any features to reflect more advanced production scheduling models supported by JobTime5. These items might include operation overlap-codes, setup-matching traits, secondary resources, or product-specific constraints on resource sub-sets of labor and/or tooling. We solve these problems so that your advanced scheduling needs are fully met in JobTime5, even though your ERP might not even contain data fields related to these features. Our import database is very flexible and can contain rules and data to support your application. We routinely tailor data-imports to "auto-populate" JobTime's advanced modeling fields.
Our JobLink/SQL integration technology makes it possible to interface with most ERP systems expeditiously. Your situation will depend on your unique set of conditions. For an ERP we have previously interfaced having no additional special requirements, the typical level of effort to define, develop and certify an import can from 1 to 3 weeks. Where substantial features are needed, the import development can range from 1 to 2 months. The two key factors affecting integration time are the type of database used by your ERP and also the skills of your own IT staff and production schedulers to support the integration development & delivery.
We also provide follow-on training, report customizing, and ROI audit and tracking as additional optional services.
JobLink/SQL is not a substitute for a real-time on-line MES or Shop Floor Execution System. However, JobTime also offers a companion service to customize a basic batch shop-floor reporting module ("JobTrak"), for the purpose of keeping task percent complete status accurate and up to date for clients who do not have MES or any shop-floor data collection system. JobTime built-in updating and tracking screens are ideal for companies to initially "cut their teeth" in shop-floor data collection at a reasonable budget.
JobTime's most frequent use is a short interval (3 to 90 day) planning tool. However, JobTime can also support longer term planning horizons such as 3 to 18 months into the future. JobLink/SQL can link ERP and/or MES systems to JobTime.
Copyright © 2012 JobTime Systems, Inc. All rights reserved