Question
Kelly Services Malaysia Sdn. Bhd.
MY
Last activity: 30 Jul 2018 1:51 EDT
Question about ECS (Enterprise Class Structure)
The question goes like this
"A company sends a standard email when a case is created. In which layer of the Enterprise Class Structure do you apply the email correspondence?"
1) Implementation
2) Enterprise
3) Division
What would be the correct answer?
Pegasystems Inc.
US
I chose Enterprise. Even though the Enterprise Layer is called Organization, I would assume that you would put this in the Enterprise ( or Organization) layer, since it is a company wide . Division might work also ,but since the question said, "company wide" which to me would mean Enterprise, and does NOT say any Department ( which I would take for Division), then I would choose Enterprise, as the everyone below that can use it a standard email.
Anyone else chose Enterprise ?
Tech Mahindra
IN
I will also choose the same, if we have different location (div) they will have different languages, in that situation i will prefer division layer.
Kelly Services Malaysia Sdn. Bhd.
MY
Hi moghr, thank you for your reply.
My issue with this question is that there is no "Enterprise" layer in ECS in the self study guide. I know that it may represent "Organization" layer but for me, it is automatically discarded as an answer, because as mentioned earlier this is what is mentioned about ECS in the Pega Academy, no where "Enterprise" layer is mentioned at any where:
Pega Platform layer
The Pega 7 layer contains the built-in assets necessary for processing cases and other work in Pega applications. This layer also contains assets used by Pega 7.
Hi moghr, thank you for your reply.
My issue with this question is that there is no "Enterprise" layer in ECS in the self study guide. I know that it may represent "Organization" layer but for me, it is automatically discarded as an answer, because as mentioned earlier this is what is mentioned about ECS in the Pega Academy, no where "Enterprise" layer is mentioned at any where:
Pega Platform layer
The Pega 7 layer contains the built-in assets necessary for processing cases and other work in Pega applications. This layer also contains assets used by Pega 7.
Organization layer
The Organization layer contains the assets used on an enterprise-wide basis. Such assets are rules for enterprise-wide business logic such as standard properties, decision tables, and service level rules. For example, a property that holds a customer's account number would be reused on an enterprise-wide basis. As a result, the applications used across the enterprise can rely on the same account number property without having to make copies of the property in every application.
The Organization layer also contains enterprise-wide data assets such as classes and rules for data stored in the system, and classes and rules for access to data in external systems, via connectors. For example, access to an external customer database is an integration point that may be added to the Organization layer.
Division layer
The Division layer contains the assets used on a division-wide basis. Assets in the Division layer may be applicable to a line of business, or for regions, brands, or departments. For example, a line of business wants to reuse a service level rule that defines the expected response time to a customer complaint in all of its applications. Placing the service level rule in the Division layer helps ensure all applications have access to the service level rule without having to create separate copies.
The Division layer is an optional layer. When used, the Division layer is parallel to the Framework layer.
Framework layer
The Framework layer contains the assets used to create generalized, reusable applications. A framework application is then extended by specific implementations.
For example, a finance company provides auto loans. An auto loan framework is created that contains all of the assets needed for the standard auto loan process. Each line of business may extend the basic auto loan application to meet specific business needs. For example, the commercial business line division's auto loan application needs to handle loan requests that are distinct from that of the personal line division.
Implementation layer
The Implementation layer defines an implementation of a framework that is customized for a specific division, or line of business. For example, the commercial business line's auto loan application reuses assets from the commercial business line division layer and from the auto loan framework layer. The personal line's auto loan application reuses assets from the personal line division layer and the auto loan framework layer.
Pegasystems Inc.
US
Hi,
here is an article where in the PDN what is now called the org layer is referred to as the Enterprise Reuse layer.
he layers depicted in the enterprise class structure image are:
| Layer | Purpose |
|---|---|
| Enterprise Reuse | For assets that need to be reused on an enterprise-wide basis. Such assets are rules for enterprise-wide business logic (such as standard properties, decision tables, Service Level rules) and enterprise-wide data assets (such as classes and rules for data stored in the system, and classes and rules for access to data in external systems, via connectors).
For example, the MyCo enterprise wants to reuse the property that holds an employee's serial number on an enterprise-wide basis, so that the various applications used by that employee across the enterprise can consistently rely on the same serial number property for the same employee. |
Hi,
here is an article where in the PDN what is now called the org layer is referred to as the Enterprise Reuse layer.
he layers depicted in the enterprise class structure image are:
| Layer | Purpose |
|---|---|
| Enterprise Reuse | For assets that need to be reused on an enterprise-wide basis. Such assets are rules for enterprise-wide business logic (such as standard properties, decision tables, Service Level rules) and enterprise-wide data assets (such as classes and rules for data stored in the system, and classes and rules for access to data in external systems, via connectors).
For example, the MyCo enterprise wants to reuse the property that holds an employee's serial number on an enterprise-wide basis, so that the various applications used by that employee across the enterprise can consistently rely on the same serial number property for the same employee. |
| Divisional Reuse | For assets that need to be reused on a division-wide basis. Such assets are rules for division-wide business logic (such as standard properties, decision tables, Service Level rules) and division-wide data assets (such as classes and rules for data stored in the system, and classes and rules for access to data in external systems, via connectors).
For example, a division wants to reuse a service level rule that defines the expected response time to a customer complaint in all of its applications, so that it can consistently enforce a focus on meeting its customer relationship commitments. |
| Framework | Defines a common work-processing foundation that is extended by the specific implementations.
For example, the MyCo enterprise makes auto loans, and has an auto loan framework that is comprised of all of the assets needed for MyCo's standard auto loan process. Each division of MyCo extends that basic auto loan application to meet their specific divisional needs: the commercial business line division's auto loan application needs to handle loan requests distinct from that of MyCo's personal line division. |
| Implementation | Defines an implementation of a framework that is customized for a specific division.
For example, the commercial business line's auto loan application reuses assets from the commercial business line division layer and from the auto loan framework layer, while the personal line's auto loan application reuses assets from the personal line division layer and the auto loan framework layer. |
| PRPC Base Product | Consists of the PRPC system's built-in classes and rules necessary for processing cases and other work in PRPC applications, as well as for areas of PRPC itself. |
Kelly Services Malaysia Sdn. Bhd.
MY
Hi moghr, thank you for the link.
I have no issue about the layer being called "Enterprise" in PRPC 6.1+ and 6.2+
This question I asked at the beginning of the topic was actually a replication of a question asked during the exam I took recently for CSSA 7.2, which means whatever was listed in 6.1+ and 6.2+ should be obsolete.
Either Pega is intentionally screwing us up by not updating the exam questions, or there is something wrong with the self study guide.
Pegasystems Inc.
US
I think it's a question of terminology. In my mind, even though we have different version of PRPC, there is still a huge history of shared language between the various versions. I know that in 7 series, new things have come about, however, I 'm guessing that part of the issue might be that it is expected that if we are well versed in Pega 7, we should be also familiar with the totality of the product line. I do agree with you that there might be a miscommunication or a carry over of terminology from a previous version of the terminology. But either way it is good fun looking back and seeing how things have evolved. I always like the Enterprise Reuse better, but this could be a marketing decision to change the name to Organizational.