jdel6654
VIP Member
Let me start by saying I have worked in E1 CNC for over 10 years. The question has come up about the number of environments needed to support a new, phased implementation.
This is a new install for a customer new to E1. This is a non-coexistant configuration for a customer going from World to E1 9.0. AS400 enterprise server with WebSphere web servers. No windows clients. Mfg, Fin, SC, Dist modules. ~750 concurrent users. ~15 Full-time developers. 3 AS400 partitions and 5 subsystems.
I have the following standard environments setup:
PS/JPS
DV/JDV
PY/JPY
PD/JPD
Over the course of the project I have set up several other non-std environments:
DVSAVE - Save environment for DV code
ES/JES - ESU Environment for pristine + ESUs (ES pathcode)
TR/JTR - training environment (QA pathcode)
DV2 / JDV2 - For developers that uses some World integration (DV pathcode)
XX/JXX - Environment that uses Windows enterprise servers for specific E1 features. (PY pathcode)
QA/JQA - custom pathcode for pre-production testing
MD/JMD - master data staging environment for pre-production setup (PD pathcode)
CV/JCV - conversion environment for Phase 1 (DV pathcode)
CV2/JCV2 - conversion environment 2 for Phase 2 (DV pathcode)
I have been asked to set up another environment. This environment is for "production bug fixes". This environment will use the prod pathcode and a daily copy of the production data. I really don't know exactly what production bug fixes are in distinction to regular bug fixes tested in a different environment. We can copy our data selectively to most of the environments at just about any time.
I have a handful of other environments that were aborted not too long ago. I am of the opinion that given OCMs, ESUs, etc., we are about right for environments. More environments, IMHO, will contribute to more inpredictability.
Long story short, I am curious to know what other CNC people consider the "right" number of environments for a similar situation. While I would appreciate any comments, "it depends" and "every company is different" doesn't really help.
Let me know what you think.
This is a new install for a customer new to E1. This is a non-coexistant configuration for a customer going from World to E1 9.0. AS400 enterprise server with WebSphere web servers. No windows clients. Mfg, Fin, SC, Dist modules. ~750 concurrent users. ~15 Full-time developers. 3 AS400 partitions and 5 subsystems.
I have the following standard environments setup:
PS/JPS
DV/JDV
PY/JPY
PD/JPD
Over the course of the project I have set up several other non-std environments:
DVSAVE - Save environment for DV code
ES/JES - ESU Environment for pristine + ESUs (ES pathcode)
TR/JTR - training environment (QA pathcode)
DV2 / JDV2 - For developers that uses some World integration (DV pathcode)
XX/JXX - Environment that uses Windows enterprise servers for specific E1 features. (PY pathcode)
QA/JQA - custom pathcode for pre-production testing
MD/JMD - master data staging environment for pre-production setup (PD pathcode)
CV/JCV - conversion environment for Phase 1 (DV pathcode)
CV2/JCV2 - conversion environment 2 for Phase 2 (DV pathcode)
I have been asked to set up another environment. This environment is for "production bug fixes". This environment will use the prod pathcode and a daily copy of the production data. I really don't know exactly what production bug fixes are in distinction to regular bug fixes tested in a different environment. We can copy our data selectively to most of the environments at just about any time.
I have a handful of other environments that were aborted not too long ago. I am of the opinion that given OCMs, ESUs, etc., we are about right for environments. More environments, IMHO, will contribute to more inpredictability.
Long story short, I am curious to know what other CNC people consider the "right" number of environments for a similar situation. While I would appreciate any comments, "it depends" and "every company is different" doesn't really help.
Let me know what you think.