0% found this document useful (0 votes)
18 views6 pages

Ekit2 0 Docs Docx1

Uploaded by

sagar.dutt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
18 views6 pages

Ekit2 0 Docs Docx1

Uploaded by

sagar.dutt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

EKIT 2.

Draft -1.0

Surjeet Kaur
Table of Contents
Overview:....................................................................................................................................................................................... 1
SCOPE:............................................................................................................................................................................................. 1
STAKEHOLDER ANALYSIS:.................................................................................................................................................... 1
USER PEROSNAS......................................................................................................................................................................... 2
PROCESS OVERVIEW:............................................................................................................................................................... 3
PROCESS OVERVIEW DIAGRAM:.........................................................................................................................................4
Overview:

The Fulfilment 2.0 e-Kit Process is a strategic initiative aimed at enhancing the efficiency and autonomy of the
fulfilment operations within our organization. The primary objective of this project is to eliminate the
dependency on the CareWin system for processing eKits, transitioning to a more streamlined and self-
contained solution within our Fulfilment microservice architecture.

SCOPE:
In the initial phase, the focus will be on removing the reliance on CareWin and implementing the new e-Kit
process within the Fulfilment microservice solution. This entails designing and deploying the necessary
infrastructure, data handling mechanisms, and communication protocols to facilitate eKit processing
independent of CareWin.

Phase 2 (Not Required for Day 1): Future enhancements in Phase 2 will aim to optimize the e-Kit email
templates and delivery mechanisms. This includes minimizing the number of email templates and delivering
eKits as attachments in emails, thereby eliminating the need for landing pages for downloading eKits.

STAKEHOLDER ANALYSIS:

Stakeholder
Stakeholder Name Stakeholder Role Department Stakeholder Rationale

Steven Fonrigrno IT Fulfillment Manager IT Fulfillment Business Requirement


Kristina Adams AVP of Project Operations Business Requirement
Management
Martin Schneider AVP of PP&L PP&L Business Requirement

USER PEROSNAS
1. USER/Customer
2. Database team – Carelynx and Fullfimnet DB
3. ITFF/PP&L team
1. User/Customer:

 Role: The User/Customer persona represents individuals or entities external to the


organization who interact with the fulfilment process. This could include customers,
clients, or stakeholders who request and receive eKits.

 Initiating fulfilment requests.

 Receiving eKits and utilizing them for their intended purposes.

2. Database Team (Carelynx and Fulfilment DB):

 The Database Team persona comprises individuals responsible for managing and
maintaining the Carelynx and Fulfilment databases.

 Designing and implementing database structures.

 Managing data migration and integration processes.

 Ensuring data accuracy, integrity, and security.

 Efficient handling of data flows between systems.

 Seamless synchronization of data between Carelynx and Fulfilment databases.

3. ITFF/PP&L Team:

 The ITFF team would be involved in reviewing feedback provided by the PP&L team
and addressing content-specific fixes or data-related issues as part of the live
approval process.
 The PP&L team would be responsible for reviewing generated PDFs and printed
materials, providing feedback, and possibly approving or rejecting workflows as
part of the live approval process.

PROCESS OVERVIEW:

1. User Request Initiation:

 The fulfilment process begins when a user initiates a request through the Fulfilment
Database (DB). The user provides necessary details such as request type, recipient
information, and any specific requirements.

2. Data Retrieval from Carelynx DB:


 The Fulfilment DB retrieves relevant information from the Carelynx Database using
data merge stored procedures. This ensures that all necessary data for the fulfilment
request, such as recipient details, product information, and delivery preferences, is
available within the Fulfilment DB.

3. Review and Approval by ITFF/PP&L Team:

 Once the fulfilment request is assembled, it is forwarded to the ITFF and the PP&L
team for review and approval. These teams verify the completeness and accuracy of
the request before proceeding further.

4. Template Selection using INSPIRE Tool:

 The INSPIRE tool plays a crucial role in determining the appropriate template to be
used for each fulfilment request. Based on the group/design code information
stored in the Fulfilment DB, the INSPIRE tool identifies the most suitable template
for the specific request. This involves mapping template codes to design codes to
ensure alignment with the intended content and formatting requirements.

5. Completion Flag Update and Email Trigger:

 Upon completion of the template selection process, the fulfilment request status is
updated to indicate that INSPIRE has finished its assignment. Simultaneously, a
trigger is activated to initiate the email notification process using the SendGrid API.

6. Email Notification to Customer:

 The customer receives an email notification confirming the status of their fulfilment
request.

7. Landing Page Link in Email:

 Within the email, a link is provided to a dedicated landing page. This landing page
serves as a central hub for accessing PDF or Ekit.

8. PDF Download Option:

 Upon clicking the link to the landing page, the customer is presented a functionality
offered on this page is the ability to download the requested PDF file associated with
their fulfilment request. This enables the customer to access and utilize the eKit or
provided by the organization.

PROCESS OVERVIEW DIAGRAM:

You might also like