RE: Design Question

If you have some order that a salesman has promised and it requires jumping the line ahead of already scheduled work in progress, then some systems have a capability of inserting that job as far forward in the process as possible.  

For example, it wouldn’t stop building an individual spool of wire, but if some customer was getting 100 spools of quarter inch wire it might stop at an integral multiple of a single spool length and start a priority job to create three sixteenths inch wire instead.  

Any repository the shop floor machines can read if the power is on in the shop that can accumulate a backlog of work for your machines that takes longer to process than the allowed ERP system outage usually will suffice.  

The tricky bit is if you get a priority job just before the outage and that priority doesn’t make it to the repository that the shop floor machines can read. Or if your machines are very fast and you don’t have enough jobs to keep them busy through the outage because business rules allow cancellations and changes so you can’t commit jobs from ERP to the shop floor yet.  

Stuff like that. Selling and building actual widgets can get very complicated and in some lines of business mistakes can be very expensive.  

mwf  

From: Vishalaksha Vyas [mailto:vishalaksha_at_gmail.com] Sent: Tuesday, January 16, 2018 10:59 PM To: Mark W. Farnham
Cc: oracle-l_at_freelists.org
Subject: Re: Design Question  

Thanks Mark for the suggestions. Can you please explain what do you mean by priority construction insertion? We are not going to have more than 24 hours of the downtime for ERP but during that time Oracle database based standalone application will be up and running and this application will keep talking with the shop floor machines and will queue up all the WIP and inventory transactions.  

Do you have an idea about any other better mechanism for communication between ERP and standalone application for live data exchange and the scenario when the main data source (ERP) is not available but still standalone application is able to work independently?    

Thanks & Regards
Vishalaksha Vyas  

On Tue, Jan 16, 2018 at 9:04 AM, Mark W. Farnham <mwf_at_rsiz.com> wrote:

Start by making certain that all test systems are prevented from sending instructions to the machine floor that might cause unwanted <anything> to be built.  

Do you know what the service levels of backlog, priority construction insertion, and allowed outages are for the systems upstream from the machine floor? (include your network risks.)  

The longer those lags, the easier, except if you do have priority construction insertion abilities into the work queue, that makes it more difficult to pre-stage a backlog of work on the shop floor.  

Depending on what you’re making and what sorts of late delivery penalties might be in your contracts, configuring this incorrectly could be very expensive. I have given you only the most lightweight minimums for a start.  

mwf  

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Vishalaksha Vyas Sent: Tuesday, January 16, 2018 8:47 AM
To: oracle-l_at_freelists.org
Subject: Re: Design Question  

Does anyone have suggestions on this one?

Thanks & Regards
Vishalaksha Vyas  

On Mon, Jan 15, 2018 at 4:58 PM, Vishalaksha Vyas <vishalaksha_at_gmail.com> wrote:

Hello Experts,  

I need an advice on the interface design between two Oracle systems. These two systems would be Oracle ERP (R12, DB: 11g R2) and standalone application using Oracle Database 12c.  

The standalone application running on Oracle DB 12c works as the bridge between ERP and the shop floor machinery in a typical manufacturing plant. Shop floor users will work 75% of the time on the standalone application and they need to login into ERP system only for 25% of the time. Oracle ERP is the owner of all kind of data. Functionalities within the standalone application use live data from the ERP database and if the ERP system is not available then the standalone application will not work.  

ORACLE ERP (11g R2) ç===è STANDALONE APPLICATION (Oracle DB, 12c) ç===è Shop floor machinery  

The requirement is to design such an interface between ERP and standalone application which will allow the standalone application to work in isolation even if the ERP system is not up. I am thinking about below option to achieve this.  

Inbound Information (ERP to standalone):- Use of staging table in the standalone DB. This staging table will work as the source of data instead of directly reaching to ERP. There will be a scheduled job which will keep updating this staging table with the latest live data from ERP system so that when ERP is not available, still standalone application will be able to use the live data.

---> There is an assumption here that the live data is not changing frequently which actually matches the current business process as well.
 

Outbound (standalone to ERP):- Use of Oracle advanced queues to push the shop floor transaction like sub inventory transfers or WIP completion to ERP. Standalone application will write the data into these queues and when ERP system is not available then these queues will hold the data and will push again whenever ERP system is up.  

I would really appreciate if anyone can suggest some innovative ideas or have suggestions for the current design.  

Thanks

Vishalaksha      

--
http://www.freelists.org/webpage/oracle-l