Why shouldn’t Petrie’s staff build their own unique system in-house?
Practical Management Science
6th Edition
ISBN:9781337406659
Author:WINSTON, Wayne L.
Publisher:WINSTON, Wayne L.
Chapter2: Introduction To Spreadsheet Modeling
Section: Chapter Questions
Problem 20P: Julie James is opening a lemonade stand. She believes the fixed cost per week of running the stand...
Related questions
Question
5-32. Why shouldn’t Petrie’s staff build their own unique system in-house?
![Although the customer loyalty project at Petrie's Electronics had gone slowly at first, the
past few weeks had been fast paced and busy, Jim Watanabe, the project manager,
thought to himself. He had spent much of his time planning and conducting interviews
with key stakeholders inside the company. He had also worked with the marketing group
to put together some focus groups made up of loyal customers, to get some ideas about
what they would value in a customer loyalty program. Jim had also spent some time
studying customer loyalty programs at other big retail chains and those in other
industries as well, such as the airlines, known for their extensive customer loyalty
programs. As project manager, he had also supervised the efforts of his team members.
Together, they had collected a great deal of data. Jim had just finished creating a high-
level summary of the information into a table he could send to his team members (PE
Table 5-1 D).
From the list of requirements, it was clear that he and his team did not favor building a
system from scratch in-house. Jim was glad that the team felt that way. Not only was
building a system like this in-house an antiquated practice, it was expensive and time
consuming. As nice as it might have been to develop a unique system just for Petrie's,
there was little point in reinventing the wheel. The IT staff would customize the system
interface, and there would be lots of work for Sanjay's staff in integrating the new system
and its related components with Petrie's existing systems, but the core of the system
would have already been developed by someone else.
Just as he was finishing the e-mail he would send to his team about the new system's
requirements and constraints, he received a new message from Sanjay. He had asked
Sanjay to take the lead in scouting out existing customer loyalty systems that Petrie's
could license. Sanjay had conducted a preliminary investigation that was now complete.
His e-mail contained the descriptions of three of the systems he had found and studied
(PE Table 5-2 L). Obviously, Jim and his team would need to have a lot more
information about these alternatives, but Jim was intrigued by the possibilities. He sent a
reply to Sanjay, asking him to pass the alternatives on to the team, and also asking him
to prepare a briefing for the team that would include more detailed information about
each alternative.](/v2/_next/image?url=https%3A%2F%2Fcontent.bartleby.com%2Fqna-images%2Fquestion%2F44ba84ef-fbb4-4f4d-b035-37a11112949f%2F810d466d-a188-4261-999c-21ac2b0dfa97%2Fvh4dwl3_processed.png&w=3840&q=75)
Transcribed Image Text:Although the customer loyalty project at Petrie's Electronics had gone slowly at first, the
past few weeks had been fast paced and busy, Jim Watanabe, the project manager,
thought to himself. He had spent much of his time planning and conducting interviews
with key stakeholders inside the company. He had also worked with the marketing group
to put together some focus groups made up of loyal customers, to get some ideas about
what they would value in a customer loyalty program. Jim had also spent some time
studying customer loyalty programs at other big retail chains and those in other
industries as well, such as the airlines, known for their extensive customer loyalty
programs. As project manager, he had also supervised the efforts of his team members.
Together, they had collected a great deal of data. Jim had just finished creating a high-
level summary of the information into a table he could send to his team members (PE
Table 5-1 D).
From the list of requirements, it was clear that he and his team did not favor building a
system from scratch in-house. Jim was glad that the team felt that way. Not only was
building a system like this in-house an antiquated practice, it was expensive and time
consuming. As nice as it might have been to develop a unique system just for Petrie's,
there was little point in reinventing the wheel. The IT staff would customize the system
interface, and there would be lots of work for Sanjay's staff in integrating the new system
and its related components with Petrie's existing systems, but the core of the system
would have already been developed by someone else.
Just as he was finishing the e-mail he would send to his team about the new system's
requirements and constraints, he received a new message from Sanjay. He had asked
Sanjay to take the lead in scouting out existing customer loyalty systems that Petrie's
could license. Sanjay had conducted a preliminary investigation that was now complete.
His e-mail contained the descriptions of three of the systems he had found and studied
(PE Table 5-2 L). Obviously, Jim and his team would need to have a lot more
information about these alternatives, but Jim was intrigued by the possibilities. He sent a
reply to Sanjay, asking him to pass the alternatives on to the team, and also asking him
to prepare a briefing for the team that would include more detailed information about
each alternative.
![PE TABLE 5-1:
Requirements and Constraints for Petrie's Customer Loyalty Project
Requirements
Effective customer incentives-System should be able to effectively store customer activity and convert to rewards and other incentives
Easy for customers to use-Interface should be intuitive for customer use
Proven performance-System as proposed should have been used successfully by other clients
Easy to implement-Implementation should not require outside consultants or extraordinary skills on the part of our staff or require specialized hardware
Scalable-System should be easily expandable as the number of participating customers grows
Vendor support-Vendor should have proven track record of reliable support and infrastructure in place to provide it
Constraints
• Cost to buy-Licenses for one year should be under $500,000
Cost to operate-Total operating costs should be no more than $1 million per year
Time to implement-Duration of implementation should not exceed three months
Staff to implement-Implementation should be successful with the staff we have and with the skills they already possess
PE TABLE 5-2:
Alternatives for Petrie's Customer Loyalty Project
Alternative A
Data warehousing-centered system designed and licensed by Standard Basic Systems, Inc. (SBSI). The data warehousing tools at the heart of the system were designed and developed by SBSI, and work with standard relational database
management systems (DBMSS) and relational/object-oriented (00) hybrid DBMSS. The SBSI tools and approach have been used for many years and are well known in the industry, but SBSI-certified staff are essential for implementation, operation,
and maintenance. The license is relatively expensive. The customer loyalty application using the SBSI data warehousing tools is an established application, used by many retail businesses in other industries.
Alternative B
Customer relationship management (CRM)-centered system designed and licensed by XRA Corporation. XRA is a pioneer in CRM systems, so its CRM is widely recognized as an industry leader. The system includes tools that support customer
loyalty programs. The CRM system itself is large and complex, but pricing in this proposal is based only on modules used for the customer loyalty application.
Alternative C
Proprietary system designed and licensed by Nova Innovation Group, Inc. The system is relatively new and leading edge, so it has only been implemented in a few sites. The vendor is truly innovative but small and inexperienced. The customer
interface, designed for a standard Web browser, is stunning in its design and is extremely easy for customers to use to check on their loyalty program status. The software runs remotely, in the "cloud," and data related to the customer loyalty
program would be stored in the cloud too.](/v2/_next/image?url=https%3A%2F%2Fcontent.bartleby.com%2Fqna-images%2Fquestion%2F44ba84ef-fbb4-4f4d-b035-37a11112949f%2F810d466d-a188-4261-999c-21ac2b0dfa97%2Fkxkqv2l_processed.png&w=3840&q=75)
Transcribed Image Text:PE TABLE 5-1:
Requirements and Constraints for Petrie's Customer Loyalty Project
Requirements
Effective customer incentives-System should be able to effectively store customer activity and convert to rewards and other incentives
Easy for customers to use-Interface should be intuitive for customer use
Proven performance-System as proposed should have been used successfully by other clients
Easy to implement-Implementation should not require outside consultants or extraordinary skills on the part of our staff or require specialized hardware
Scalable-System should be easily expandable as the number of participating customers grows
Vendor support-Vendor should have proven track record of reliable support and infrastructure in place to provide it
Constraints
• Cost to buy-Licenses for one year should be under $500,000
Cost to operate-Total operating costs should be no more than $1 million per year
Time to implement-Duration of implementation should not exceed three months
Staff to implement-Implementation should be successful with the staff we have and with the skills they already possess
PE TABLE 5-2:
Alternatives for Petrie's Customer Loyalty Project
Alternative A
Data warehousing-centered system designed and licensed by Standard Basic Systems, Inc. (SBSI). The data warehousing tools at the heart of the system were designed and developed by SBSI, and work with standard relational database
management systems (DBMSS) and relational/object-oriented (00) hybrid DBMSS. The SBSI tools and approach have been used for many years and are well known in the industry, but SBSI-certified staff are essential for implementation, operation,
and maintenance. The license is relatively expensive. The customer loyalty application using the SBSI data warehousing tools is an established application, used by many retail businesses in other industries.
Alternative B
Customer relationship management (CRM)-centered system designed and licensed by XRA Corporation. XRA is a pioneer in CRM systems, so its CRM is widely recognized as an industry leader. The system includes tools that support customer
loyalty programs. The CRM system itself is large and complex, but pricing in this proposal is based only on modules used for the customer loyalty application.
Alternative C
Proprietary system designed and licensed by Nova Innovation Group, Inc. The system is relatively new and leading edge, so it has only been implemented in a few sites. The vendor is truly innovative but small and inexperienced. The customer
interface, designed for a standard Web browser, is stunning in its design and is extremely easy for customers to use to check on their loyalty program status. The software runs remotely, in the "cloud," and data related to the customer loyalty
program would be stored in the cloud too.
Expert Solution
![](/static/compass_v2/shared-icons/check-mark.png)
This question has been solved!
Explore an expertly crafted, step-by-step solution for a thorough understanding of key concepts.
This is a popular solution!
Trending now
This is a popular solution!
Step by step
Solved in 2 steps
![Blurred answer](/static/compass_v2/solution-images/blurred-answer.jpg)
Recommended textbooks for you
![Practical Management Science](https://www.bartleby.com/isbn_cover_images/9781337406659/9781337406659_smallCoverImage.gif)
Practical Management Science
Operations Management
ISBN:
9781337406659
Author:
WINSTON, Wayne L.
Publisher:
Cengage,
![Operations Management](https://www.bartleby.com/isbn_cover_images/9781259667473/9781259667473_smallCoverImage.gif)
Operations Management
Operations Management
ISBN:
9781259667473
Author:
William J Stevenson
Publisher:
McGraw-Hill Education
![Operations and Supply Chain Management (Mcgraw-hi…](https://www.bartleby.com/isbn_cover_images/9781259666100/9781259666100_smallCoverImage.gif)
Operations and Supply Chain Management (Mcgraw-hi…
Operations Management
ISBN:
9781259666100
Author:
F. Robert Jacobs, Richard B Chase
Publisher:
McGraw-Hill Education
![Practical Management Science](https://www.bartleby.com/isbn_cover_images/9781337406659/9781337406659_smallCoverImage.gif)
Practical Management Science
Operations Management
ISBN:
9781337406659
Author:
WINSTON, Wayne L.
Publisher:
Cengage,
![Operations Management](https://www.bartleby.com/isbn_cover_images/9781259667473/9781259667473_smallCoverImage.gif)
Operations Management
Operations Management
ISBN:
9781259667473
Author:
William J Stevenson
Publisher:
McGraw-Hill Education
![Operations and Supply Chain Management (Mcgraw-hi…](https://www.bartleby.com/isbn_cover_images/9781259666100/9781259666100_smallCoverImage.gif)
Operations and Supply Chain Management (Mcgraw-hi…
Operations Management
ISBN:
9781259666100
Author:
F. Robert Jacobs, Richard B Chase
Publisher:
McGraw-Hill Education
![Business in Action](https://www.bartleby.com/isbn_cover_images/9780135198100/9780135198100_smallCoverImage.gif)
![Purchasing and Supply Chain Management](https://www.bartleby.com/isbn_cover_images/9781285869681/9781285869681_smallCoverImage.gif)
Purchasing and Supply Chain Management
Operations Management
ISBN:
9781285869681
Author:
Robert M. Monczka, Robert B. Handfield, Larry C. Giunipero, James L. Patterson
Publisher:
Cengage Learning
![Production and Operations Analysis, Seventh Editi…](https://www.bartleby.com/isbn_cover_images/9781478623069/9781478623069_smallCoverImage.gif)
Production and Operations Analysis, Seventh Editi…
Operations Management
ISBN:
9781478623069
Author:
Steven Nahmias, Tava Lennon Olsen
Publisher:
Waveland Press, Inc.