OneWorld Worldwide Roll-out

KBohn

Active Member
Hi everyone,

We are starting to plan rolling out OneWorld to our offices in the U.K.,
France, Germany & Japan. We are a Canadian company & have been live in
B73.3.2 since May/00 with local fat clients only. I am hoping that if any
of you have done a similar roll-out, you might share some of the
watchouts/stories of your implementation. Some of my questions are:

1. What Remote Access Strategy worked for you? Windows Terminal Server?

2. How did you handle the multi-lingual issues? How does JDE OW handle the
multi-lingual as far as the application goes - ie. how is it set up & how
does it work? How can you tell if languages have been installed on the
current OneWorld install?

3. How did you handle the project management and implementation to other
countries? Did you use consulting companies?

4. Are there country specific regulations that must be met?

5. How long does it take per country to implement financials & Sales Order?

I really appreciate any stories/suggestions.

Regards,

Kimberley Bohn
QNX Software Systems Ltd.
Canada - EST 10:15 am
 

owguru

Well Known Member
Kimberly,

First I'll start by saying I'm a consultant, not a customer...so my answers
(opinions) cover a number of customers from that angle. Second, I've worked
on a number of multi-national implementations and seen a different approach
in each one.

1 - Remote Access...Having been in it since the "dawn of oneworld", I can
attest (probably no surprise) that fat clients are not an option. At this
point the most robust strategy is WTS (or Citrix for those willing to buck
the system). OneWorld being the administrative challenge that it is gets a
huge boost from this strategy...and the performance benefits sell
themselves. Of course, you can look into the web strategy (OneWorld Java or
HTML client), or using some third party storefront add-on for sales order.
Chat with someone about the performance benefits of these strategies. I
personally don't recommend these for companies that don't want to be on the
cutting edge. Implementations are tricky enough without the added overhead
of this technology unless you have strong business reasons.

2 - The multi-lingual thing is far too complicated to discuss here...but a
few quick notes: 1 - A user is assigned a language preference in his user
profile. When he signs onto oneworld, if that language is installed, then
he gets it. Otherwise, he sees the base language. 2 - When a package is
built, you specify which languages to include. Those languages then exist
wherever that package is deployed. If you are administering this
implementation from a central location (recommended), I would build as few
packages as possible and include all the necessary languages. This would be
especially true if I was using the WTS solution. That way all the WTS
servers would have all languages installed, and the user base would connect
to any of the servers (based on load balancing and all that stuff) and be
able to access the system and languages appropriately.

3 - Obviously, I've been involved as a consultant so the customers used
consulting services...usually from a variety of consulting companies due to
consultant expertise and availability. A universal note on this one...the
customer should always own the project! Don't just hand it over to some
consulting firm and hope for the best. At some point we all go home and you
have to run the system, so act that way from the start (ok, my ranting is
over :).

4 - ???

5 - As you can imagine, timing is totally dependent on your strategy. Are
you going country by country, module by module? What are you starting with?
Are all the countries you mentioned currently on one system or are they
each doing their own thing? Is the implementation team going to be a joint
effort with representation from each site? The questions are endless, but
the goal is the same...enforceable ground rules and a single comprehensive
plan with a sign-off from all the powers that be will get you off to a good
start.

Lastly, if you are running the show from your current installation in
Canada, you are probably way ahead of the curve. If you do decide on the
terminal server solution, you have a small learning curve administratively.
Most of the work will be shifting the business processes of the current
systems to oneworld and fighting off each site's demand for customization
beyond localization requirements.

Good Luck




>From: KBohn <[email protected]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: OneWorld Worldwide Roll-out ~~0:1998
>Date: Thu, 30 Nov 2000 07:16:51 -0800 (PST)
>
>Hi everyone,
>
>We are starting to plan rolling out OneWorld to our offices in the U.K.,
>France, Germany & Japan. We are a Canadian company & have been live in
>B73.3.2 since May/00 with local fat clients only. I am hoping that if any
>of you have done a similar roll-out, you might share some of the
>watchouts/stories of your implementation. Some of my questions are:
>
>1. What Remote Access Strategy worked for you? Windows Terminal Server?
>
>2. How did you handle the multi-lingual issues? How does JDE OW handle
>the
>multi-lingual as far as the application goes - ie. how is it set up & how
>does it work? How can you tell if languages have been installed on the
>current OneWorld install?
>
>3. How did you handle the project management and implementation to other
>countries? Did you use consulting companies?
>
>4. Are there country specific regulations that must be met?
>
>5. How long does it take per country to implement financials & Sales
>Order?
>
>I really appreciate any stories/suggestions.
>
>Regards,
>
>Kimberley Bohn
>QNX Software Systems Ltd.
>Canada - EST 10:15 am
>
>
>
>
>--------------------------
>To view this thread, visit the JDEList forum at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=1998
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************
>

_____________________________________________________________________________________
Get more from the Web. FREE MSN Explorer download : http://explorer.msn.com



owguru (at least I'm trying :)
>all versions
>all platforms
 

KBohn

Active Member
Hello owguru,

Thanks for your response. This is extremely helpful!

Re: question #4 - one of my co-workers has a concern that Germany dictates
what software can be used and how it can be used. I don't know specific
details, but he has expressed this on several occasions so I was looking for
clarification.

Do you know if there are any Server specific or database specific (SQL)
requirements to support DBCS?

Thanks again,
Kimberley
 

Mike Dupaix

VIP Member
re[2]: OneWorld Worldwide Roll-out

Kimberly,

In regards to country requirements, these are very difficult to pin down Perhaps your accounting firm can be of assistance in helping you determine some of the specifics. I know, from working in France three years ago, that the government does not allow there to be gaps in document sequence numbers. They also require specific report formats for tax remittances and informational reports. JDE provides some of these and the rest must be created.

If you look on menu G74, there are several processes and reports listed by country. These can be executed, printed and evaluated for the government reporting needs.

> Hello owguru,

Thanks for your response. This is extremely helpful!

Re: question #4 - one of my co-workers has a concern that Germany dictates
what software can be used and how it can be used. I don't know specific
details, but he has expressed this on several occasions so I was looking for
clarification.

Do you know if there are any Server specific or database specific (SQL)
requirements to support DBCS?

Thanks again,
Kimberley




--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=2038
*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************

<



Mike Dupaix
JDE Certified Professional
(630) 904-5373 – Office/Fax
(630) 750-2500 - Cell
 
Discover how to build no-code data integrations and business process automations.

achev

Member
Hi, Kimberly and owguru,
1. We use WTS and Citrix. It is very convenient. It is easy to say who is in
the system, easy to support, easy to help remotely. I like this solution. I
would recommend you to use it :))
2. We have Spanish and French languages. I haven't had any problem so far.
It is easy to install. You have to build a full package and deploy it. You
have to check in all languages when you build newer packages later. I think
that languages are only for user's convinience. They don't affect the system
functionality.
3. Yes, I agree that customers have to support their systems. It is more
reliable. We have several technical consultants. Now two of them in
Vancouver, one is in Calgary. How will they help us if we have a real
trouble? %-(

Regards,
Alexander.
CNC administrator
Royal Group Technologies Ltd - IT Dept.
1 Royal Gate Blvd.
Woodbridge, ON L4L 8Z7
(905) 326-7381
 
Re[3]: OneWorld Worldwide Roll-out

hello jde friends.
i am reading the exchange below and would like to clarify: if we are
connecting our thin clients via windows terminal services, do we still need
citrix, or vice versa? we've been advised that we need both citrix and
windows terminal services for the clients --- is this accurate?
thanks very much.
melo




Melo Portugal
12/02/2000 08:03 AM

To: JDETeam/[email protected]
cc:

Subject: Re: OneWorld Worldwide Roll-out ~~1998:2028


---------------------- Forwarded by Melo Portugal/Unilab on 12/02/2000
07:50 AM ---------------------------


owguru <[email protected]>@jdelist.com on 12/01/2000 03:24:07 AM

Please respond to [email protected]

Sent by: [email protected]


To: [email protected]
cc:

Subject: Re: OneWorld Worldwide Roll-out ~~1998:2028


Kimberly,

First I'll start by saying I'm a consultant, not a customer...so my answers
(opinions) cover a number of customers from that angle. Second, I've
worked
on a number of multi-national implementations and seen a different approach
in each one.

1 - Remote Access...Having been in it since the "dawn of oneworld", I can
attest (probably no surprise) that fat clients are not an option. At this
point the most robust strategy is WTS (or Citrix for those willing to buck
the system). OneWorld being the administrative challenge that it is gets a
huge boost from this strategy...and the performance benefits sell
themselves. Of course, you can look into the web strategy (OneWorld Java
or
HTML client), or using some third party storefront add-on for sales order.
Chat with someone about the performance benefits of these strategies. I
personally don't recommend these for companies that don't want to be on the
cutting edge. Implementations are tricky enough without the added overhead
of this technology unless you have strong business reasons.

2 - The multi-lingual thing is far too complicated to discuss here...but a
few quick notes: 1 - A user is assigned a language preference in his user
profile. When he signs onto oneworld, if that language is installed, then
he gets it. Otherwise, he sees the base language. 2 - When a package is
built, you specify which languages to include. Those languages then exist
wherever that package is deployed. If you are administering this
implementation from a central location (recommended), I would build as few
packages as possible and include all the necessary languages. This would
be
especially true if I was using the WTS solution. That way all the WTS
servers would have all languages installed, and the user base would connect
to any of the servers (based on load balancing and all that stuff) and be
able to access the system and languages appropriately.

3 - Obviously, I've been involved as a consultant so the customers used
consulting services...usually from a variety of consulting companies due to
consultant expertise and availability. A universal note on this one...the
customer should always own the project! Don't just hand it over to some
consulting firm and hope for the best. At some point we all go home and
you
have to run the system, so act that way from the start (ok, my ranting is
over :).

4 - ???

5 - As you can imagine, timing is totally dependent on your strategy. Are
you going country by country, module by module? What are you starting
with?
Are all the countries you mentioned currently on one system or are they
each doing their own thing? Is the implementation team going to be a joint
effort with representation from each site? The questions are endless, but
the goal is the same...enforceable ground rules and a single comprehensive
plan with a sign-off from all the powers that be will get you off to a good
start.

Lastly, if you are running the show from your current installation in
Canada, you are probably way ahead of the curve. If you do decide on the
terminal server solution, you have a small learning curve administratively.
Most of the work will be shifting the business processes of the current
systems to oneworld and fighting off each site's demand for customization
beyond localization requirements.

Good Luck




>From: KBohn <[email protected]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: OneWorld Worldwide Roll-out ~~0:1998
>Date: Thu, 30 Nov 2000 07:16:51 -0800 (PST)
>
>Hi everyone,
>
>We are starting to plan rolling out OneWorld to our offices in the U.K.,
>France, Germany & Japan. We are a Canadian company & have been live in
>B73.3.2 since May/00 with local fat clients only. I am hoping that if any
>of you have done a similar roll-out, you might share some of the
>watchouts/stories of your implementation. Some of my questions are:
>
>1. What Remote Access Strategy worked for you? Windows Terminal Server?
>
>2. How did you handle the multi-lingual issues? How does JDE OW handle
>the
>multi-lingual as far as the application goes - ie. how is it set up & how
>does it work? How can you tell if languages have been installed on the
>current OneWorld install?
>
>3. How did you handle the project management and implementation to other
>countries? Did you use consulting companies?
>
>4. Are there country specific regulations that must be met?
>
>5. How long does it take per country to implement financials & Sales
>Order?
>
>I really appreciate any stories/suggestions.
>
>Regards,
>
>Kimberley Bohn
>QNX Software Systems Ltd.
>Canada - EST 10:15 am
>
>
>
>
>--------------------------
>To view this thread, visit the JDEList forum at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=1998

>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************
>

_____________________________________________________________________________________

Get more from the Web. FREE MSN Explorer download :
http://explorer.msn.com



owguru (at least I'm trying :)
>all versions
>all platforms
--------------------------
To view this thread, visit the JDEList forum at:
http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=2028

*************************************************************
This is the JDEList One World / XE Mailing List.
Archives and information on how to SUBSCRIBE, and
UNSUBSCRIBE can be found at http://www.JDELIST.com
*************************************************************
 

Jack_Crouch

Well Known Member
If you will have multiple WTS servers, then Citrix's main deal is to load balance those terminals (in addition to providing some extras like alternative clients and another network protocal - ICA). WTS is like a catered lunch without the drinks included. You can do it...but.

This comes in handy for us because we can maintain certain servers by bringing them down / up without worrying to much about a user finding an open server.

Nfuse is a product from Citrix that might be interesting with JDE, we have not used it yet, but if anyone else has... Pipe in.

AS400 V4R4, B733.2, SP10USER2, NTSQL7
 

altquark65

Member
for a full demonstration of how nFuse works - check out
http://www.appzrent.com - it provides the ability to be able to
dramatically reduce the effort of deploying applications through Citrix -
and utilizes web or Java based clients instead of the C compiled
client. Very cool !

Jon Steel
Xe Upgrade Specialist
ERP Sourcing LLC
http://www.appzbiz.com
(303) 883 9168
[email protected]

At 04:50 PM 12/4/2000 -0800, you wrote:
>If you will have multiple WTS servers, then Citrix's main deal is to load
>balance those terminals (in addition to providing some extras like
>alternative clients and another network protocal - ICA). WTS is like a
>catered lunch without the drinks included. You can do it...but.
>
>This comes in handy for us because we can maintain certain servers by
>bringing them down / up without worrying to much about a user finding an
>open server.
>
>Nfuse is a product from Citrix that might be interesting with JDE, we have
>not used it yet, but if anyone else has... Pipe in.
>
>AS400 V4R4, B733.2, SP10USER2, NTSQL7
>--------------------------
>Visit the forum to view this thread at:
>http://198.144.193.139/cgi-bin/wwwthreads/showflat.pl?Cat=0&Board=OW&Number=2151
>
>*************************************************************
>This is the JDEList One World / XE Mailing List.
>Archives and information on how to SUBSCRIBE, and
>UNSUBSCRIBE can be found at http://www.JDELIST.com
>*************************************************************



_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
 
Top