I agree.
You need to make management aware of the alternatives.
For each one, once implemented, what will they be able to do, and not do,
unless modifications. Ball park how long to implement each (6 months?), and
how much added work load to maintain the different ways.
They not only have to hire more people in IT, but also engineering, other
areas, just to stay current with current work load, if they go certain
routes. That's good for the current economy, but not good for company
profitability.
Example: If you go total separation route, you probably cannot get same
amount of work from existing staff (at both companies combined) of
engineers, customer service, marketing, production, etc. Provide them a
copy of THE MYTHICAL MAN MONTH book to explain that there will be MORE work
for the combined operation than when the companies were separate.
If you go the parallel facility route, here's all the areas where there can
be economy of scale, but it could take a year or more conversion to get
there.
What I have experienced is management apparently having a learning process
of their own, as they go down some path, then determine that it is not a
good match to what they wanted, so they keep returning to me with a new
story of what their goal is.
1. Have separate environment for the other division stuff, and have them
sign onto our 400 from their location, with printer there for their stuff.
Check BPCS license on # users authorized. Start using some BPCS modules we
had not needed before, such as DRP, and add new transaction effects for
moving inventory between the divisions.
2. Put their stuff into our environment with different facility, and the
various reports that go outside of the company (invoices, shipping
paperwork, PO's etc.) to show old name of acquisition, because until end of
fiscal year, continue keep the books separate on the two companies.
3. Revert reports that go outside of the company, so that facility no longer
treated as independent company.
-
Al Mac
-----Original Message-----
From: bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+macwheel99=wowway.com@xxxxxxxxxxxx] On Behalf Of
cfgwizard@xxxxxxx
Sent: Friday, December 04, 2009 1:19 PM
To: bpcs-l@xxxxxxxxxxxx
Subject: Re: [BPCS-L] New company in BPCS
Bill,
It may be true that all this separation is necessary but it has hazards. If
the objective is to make the acquisition and dress it up for a sale, then I
agree with separate everything. But if this is a long term strategic move,
the separation will make it more difficult to come back in the future and
look for ways to improve overall performance by integrating any of the
typical cost saving areas such as Engineering, Materials planning,
Production planning, Purchasing, Order processing, Credit management,
Costing, and so on. No rebalancing of plant product mix or capacities. How
will this impact your support costs? My guess is that hardware and software
costs go up. Will you need a clone to support their system? Eventually you
will have your "highly modified' version and they will have theirs, and the
reporting will very likely never agree.
You need to get management to the table to review what were the objectives
of the acquisition. Do they intend to be a holding company of several
independent job shops or will they be an integrated solution for their
customers?
Best Regards, Larry Costain
-----Original Message-----
From: Bill Brosch <bbrosch@xxxxxxxxx>
To: BPCS ERP System <bpcs-l@xxxxxxxxxxxx>
Sent: Fri, Dec 4, 2009 11:01 am
Subject: Re: [BPCS-L] New company in BPCS
Total separation in this case means no shared items, no shared customers, no
ombined reports, etc. It literally could be on a separate compute (as is
ow).
The only things that they want in common is the Chart of Accounts.
Bill
On Fri, Dec 4, 2009 at 8:35 AM, Bailey, Dick <Dick.Bailey@xxxxxxxx> wrote:
BPCS provides for multiple companies. You must be operating with
one company number; can't you set up a second company number and avoid
separate library lists? Does "total separation" mean a different computer?
Dick Bailey
MFCA, Inc.
(In soon to be snowy Houston)
________________________________________
From:
bpcs-l-bounces+dick.bailey=mcfa.com@xxxxxxxxxxxx[bpcs-l-bounces+dick.bailey=
mcfa.com@xxxxxxxxxxxx] On Behalf Of Bill Brosch [bbrosch@xxxxxxxxx]
Sent: Thursday, December 03, 2009 5:02 PM
To: BPCS-L@xxxxxxxxxxxx
Subject: [BPCS-L] New company in BPCS
Hi All,
Currently running 8.2, and the company is looking to buy a new
division/company/whatever. And they will be going onto BPCS.
Management has decided that they want total seperation of the two
companies. To me, that says Library Lists. No big deal. But we're
heavily
modified, so I'm going thru things now (and pretty new to BPCS as well).
So what is the best way to create a new set of libraries? I can put them
out & clear the files, but that's going to cause grief with security,
menus,
etc. Is there a "Clear application data" type of command, or something
similar?
Thanks in advance,
Bill
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: Dick.Bailey@xxxxxxxx
--
This is the BPCS ERP System (BPCS-L) mailing list
To post a message email: BPCS-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
or email: BPCS-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/bpcs-l.
Delivered-To: bbrosch@xxxxxxxxx
-
his is the BPCS ERP System (BPCS-L) mailing list
o post a message email: BPCS-L@xxxxxxxxxxxx
o subscribe, unsubscribe, or change list options,
isit:
http://lists.midrange.com/mailman/listinfo/bpcs-l
r email: BPCS-L-request@xxxxxxxxxxxx
efore posting, please take a moment to review the archives
t
http://archive.midrange.com/bpcs-l.
Delivered-To: cfgwizard@xxxxxxx
As an Amazon Associate we earn from qualifying purchases.