alk_ operations manual v1.6

Alkermes, Inc.Sales and Marketing Data Warehouse

Production Operations Manual

Version: 1.6

Last Updated: May 30, 2007

Prepared by:

Sales & Marketing Data Warehouse Project Alkermes Operations Manual Version 1.5

Document Approval

Approver Signature Date

John Fritch

Director,Sales Operations, Alkermes

________________________________ ______________

Melissa DePalma

Project Leader, Information Technology, Alkermes

________________________________ ______________

Bill LewallenSenior Vice President, Life Sciences Solutions ________________________________ ______________

Kevin HartnettProject Manager,Life Sciences Solutions

________________________________ ______________

of 28


Revision History

Revision Date Revised By Changes Made – Reason for Change

1.0 October 10, 2006 Andrew Pilch Original version.

1.1 April 12, 2007 Sudharm jain Updated for FileParameters-DataMonth and Freezedate.

1.2 April 18, 2007 Kevin Hartnett Incorporated CPDB extract documentation.

1.3 April 18, 2007 Kevin Hartnett Added report QC procedure to Appendix.

1.4 May 1, 2007 Kevin Hartnett Incorporated streamlined MDX file transfer and processing procedure. See Section 4. Data Load and Address Lock Determination.

1.5 May 15, 2007 Kevin Hartnett Incorporated feedback from Melissa DePalma.

1.6 May 30, 2007 Open questions answered

of 28


Contents

1. Introduction....................................................................................................................... 6

1.1 Document Purpose...................................................................................................6

1.2 Intended Audience....................................................................................................6

1.3 Project Documentation References..........................................................................6

1.4 Points of Contact......................................................................................................6

2. System Overview & User Access.....................................................................................7

2.1 Major Functions........................................................................................................7

2.2 Data Flows...............................................................................................................8

2.3 User Access Levels..................................................................................................9

2.4 Getting access to the System...................................................................................9

3. Operational Guidelines...................................................................................................10

3.1 Input File Processing..............................................................................................10

3.1.1 MDX Input Files............................................................................................103.1.2 Data Warehouse Input Files.........................................................................12

3.2 MDX Processing.....................................................................................................14

3.3 DW Processing.......................................................................................................16

3.4 Process To Determine Parameters for Processing Alkermes SMDW Input Files...18

3.4.1 Purpose........................................................................................................183.4.2 Determine Data Month..................................................................................183.4.3 Determine Alignment Cycle..........................................................................183.4.4 Determine Freeze Date.................................................................................193.4.5 Examples......................................................................................................203.4.6 Database Considerations................................................................................1

4. Appendix 2.4 – User Access Request..............................................................................2

5. Appendix 3 – Operations Process Flow............................................................................3

of 28


1. Introduction

1.1 Document Purpose

The purpose of this document is to outline the operational processes required to support the Alkermes Sales and Marketing Data Warehouse.

1.2 Intended Audience

The intended audience would include business and technical users of the system from Alkermes and Alliance Consulting.

1.3 Project Documentation References

This document will be based upon the implementation of the system according to the following documents:

Table 11-1 – Related Documents

Document Name Date

Alkermes Reporting Requirements – Ver 2.0.doc

Alkermes MDX Customer Master Requirements Ver 3.1.doc

Alkermes MDX Customer Master Requirements Ver 4.2.doc

1.4 Points of Contact

The table below lists the people from Alliance Consulting to be contacted for each part of the system.

Table 11-2 – Points of Contact

Person Name System Area Phone # Fax # E-Mail

Kevin Hartnett Data Warehouse / Cognos

(610) 513-6068

(908) 231-1995

[email protected]

Jim Wheatcroft MDX Customer Master

(856) 905-2288

(908) 231-1995

[email protected]

of 28


2. System Overview & User Access

The purpose of this section is to give an overview of the major functions of the system, data flows, the access levels of the system users, and how to grant a user access to each part of the system.

2.1 Major Functions

The major functions of the Alkermes Sales and Marketing Data Warehouse for Release 1.0/1.5 include the following:

Provide a cleansed and conformed customer demographic data set for professionals as well as organizations through the MDX Customer Master platform

Provide the service bureau SMDW infrastructure for source data processing (FTP, dimension and fact processing)

Provide the Alkermes business users with the source listing reports through the Cognos interface

Provide an environment for ad-hoc reporting capabilities

Provide the capability to request a CPDB extract for a given timeframe

2.2 User Access Levels

The purpose of this section is to list the users of the system and a description of the access level each user has to each part of the system.

Table 22-3 – Users of the Alkermes Sales & Marketing Data Warehouse

SME Name Title MDX Customer Master

Cognos License Ad-Hoc Reports

John Fritch Sales Operations Program Manager and Business Lead

Full access rights Professional Author Full access rights

Melissa DePalma

IT Project Manager

Full access rights Business Author Full access rights (No SQL querying rights)

Wendy Davis Sales Operations Analyst

Full access rights Professional Author Full access rights

Sathya Koteesh

Technical Processing within Sales Operations

Full access rights Full access rights Full access rights (No SQL querying rights)

of 28


2.3 Getting access to the System

The purpose of this section is to provide the steps required to establish a user within each part of the system.

1. First, print and fill out the User Access Request form in Appendix A – User Access Request.

2. Get appropriate signature from Alkermes business system owner

3. Send User Access Request form to [email protected] Alliance Consulting via e-mail.

of 28

mailto:[email protected]


3. Operational Guidelines

The purpose of this section is to provide a general walkthrough of the system from initiation through exit. The logical arrangement of the information shall enable the functional personnel to understand the sequence and flow of the system. A process flow representation of the operation process can be view in Appendix B – Operations Process Flow.

3.1 Input File Processing

The purpose of this section is to outline the processing of input files for each part of the system. This section will be split into input files specific for customer data, which will be sent to MDX, and input files which contain activity data, which will be sent to the Data Warehouse.

3.1.1 MDX Input Files

Figure 33-4 – Data Warehouse Input Data Flow Diagram

The diagram above displays the flow of customer-centric input files from Alkermes to the MDX FTP server.

The following table displays the MDX FTP Server Properties:

Table 33-5 – MDX FTP Server Properties

of 28

CPDB Professionals

CPDB Organizations

CPDBCPDB

MDXFTP

MDXFTP

Lash Professionals / Organizations

WoltersKluwer Professionals

IMS Organizations

Cephalon Professionals


IP Address ID Password Folders

12.159.77.24 Alkermes Send an email to MDX_Support LS Support @allian ce-consulting.com for password. Or call (800) 718-3123.Fax (800) 865-4814.

Service hours:Tentatively (8AM-5PM)

Wait Listed – This folder will be used to store incoming files from Alkermes

Process – This folder will be used to store files ready for processing within MDX. MDX will poll this directory automatically. Once a file exists, MDX will pick it up and process the file.

Archived – Once the input file has been processed by MDX, it will be moved from the Process directory to this directory.

The following table lists the process steps for sending customer-centric files to MDX:

Table 33-6 – Processing Customer-Centric Files for Input to MDX

Step # Input Source Process Step Owner

1 WoltersKluwer Raw demographic file is received from WK and then renamed to data month format prior to transferring to MDX.Example: ADMPPADDALLDOC.txt ADMPPADDALLDOC_20060824.txt

Sathya Koteesh

2 IMS Raw DDD file is received from IMS, and then renamed to data month format prior to transferring to MDX.Example: CLI907.R20.txt CLI907.R20_20060824.txt

Sathya Koteesh

3 Lash Raw shipment file is received from Lash and then renamed to data month format prior to transferring to MDX.Example: Cephalon_datafeed.txt Cephalon_datafeed_20060824.txt

Sathya Koteesh

4 Cephalon Raw demographic file is received from Cephalon and then renamed to data month format prior to transferring to MDX.Example: OBW_ADM_Profile.txt OBW_ADM_Profile_20060824.txt

Sathya Koteesh

5 CPDB Extract files for profiles, addresses, and 1-M profile attributes are generated from the CPDB database:1. CPDB_Physician_Profiles_YYYYMMDD.txt 2. CPDB_Physician_Locations_YYYYMMDD.txt3. CPDB_Physician_Derived_Attributes_YYYYMMDD.txt 4. CPDB_Outlets_YYYYMMDD.txt5. CPDB_Outlet_Derived_Attributes_YYYYMMDD.txt

Sathya Koteesh

6 All renamed input files

All renamed input files from all data sources are to be sent via FTP to the “Wait Listed” folder on the MDX FTP Server.

Sathya Koteesh

of 28





3.1.2 Data Warehouse Input Files

Figure 33-7 – Data Warehouse Input Data Flow Diagram

The diagram above displays the flow of input files from Alkermes to the Data Warehouse FTP server.

The following table displays the Data Warehouse FTP Server Properties:

Table 33-8 – Data Warehouse FTP Server Properties

IP Address ID Password Folders

10.2.70.10 alksftp Send an email to MDX_Support LS Support @allian ce-consulting.com for password

alksftp – This folder will be used to store incoming files from Alkermes.

Load – This folder will be used to store files ready for processing within the Data Warehouse.

(MMDDYY) Archived – Once the input file has been processed by the Data Warehouse, it will be moved from the Process directory to this directory.

The following table lists the process steps for sending files to the Data Warehouse:

Table 33-9 – Processing Files for Input to the Data Warehouse

Step # Input Source Process Step Owner

1 WoltersKluwer Raw retail file is received from WK and then renamed to data month format prior to transferring to the Data Warehouse.Example: ADMPPDATA.TXT ADMPPDATA _20060824.txt

Sathya Koteesh

2 WoltersKluwer Readme file for current WoltersKluwer is received from WK and then renamed to data month format prior to transferring to the Data Warehouse.Example: Readme_ADMPPDATA.TXT Readme_ADMPPDATA _20060824.txt

Sathya Koteesh

of 28

DataWarehouse

FTP

DataWarehouse

FTP

Lash Shipments

WoltersKluwer Retail

IMS DDD Non-Retail

Alkermes – Product Definition

Product Brand DefinitionsMarket Definition

Product Brand – Market DefinitionMMD Hierarchy Alignment & Roster

MMD Zip-Terr Alignment

Cephalon – Zip-Terr Alignment

ADM Roster & Hierarchy AlignmentNAM Roster & Hierarchy Alignment





3 IMS Raw DDD file is received from IMS, and then renamed to data month format prior to transferring to the Data Warehouse.Example: CLI907.R20.txt CLI907.R20_20060824.txt

Sathya Koteesh

4 IMS Readme file is created for IMS DDD and named in data month format prior to transferring to Data Warehouse:Example: Readme_CLI907.R20_20060824.txt

Sathya Koteesh

5 Lash Raw shipment file is received from Lash and then renamed to data month format prior to transferring to the Data Warehouse.Example: Cephalon_datafeed.txt Cephalon_datafeed_20060824.txt

Sathya Koteesh

6 Lash Readme file is created for Lash and named in data month format prior to transferring to Data Warehouse:Example: Readme_Cephalon_datafeed_20060824.txt

Sathya Koteesh

7 Cephalon Raw files are received from Cephalon and then renamed to data month format prior to transferring to the Data Warehouse as shown below: CephalonNAMSTerritory_YYYYMMDD.txt CephalonNAMSZipToTerritory_YYYYMMDD.txt CephalonSalesTerritory_YYYYMMDD.txt CephalonSalesZipToTerritory_YYYYMMDD.txt

Sathya Koteesh

8 Cephalon Readme files are generated for Cephalon and named in data month format prior to transferring to Data Warehouse: ReadMe_CephalonNAMSTerritory_YYYYMMDD.txt ReadMe_CephalonNAMSZiptoTerritory_YYYYMMDD.txt Readme_CephalonSalesTerritory_YYYYMMDD.txt ReadMe_CephalonSalesZiptoTerritory_YYYYMMDD.txt

Sathya Koteesh

9 Alkermes All files are generated and named with data month format prior to transferring to the Data Warehouse as shown below: Alkermes_Roster_YYYYMMDD.txt AlkermesBrand_YYYYMMDD.txt AlkermesMarketDefinition_YYYYMMDD.txt AlkermesMktDefBrandXref_YYYYMMDD.txt AlkermesMMDTerritory_YYYYMMDD.txt AlkermesMMDZipToTerritory_YYYYMMDD.txt AlkermesProduct_YYYYMMDD.txt

Sathya Koteesh

of 28


10 Alkermes All Readme files are generated and named with data month format prior to transferring to the Data Warehouse as shown below: Readme_Alkermes_Roster_YYYYMMDD.txt ReadMe_AlkermesBrand_YYYYMMDD.txt Readme_AlkermesMarketDefinition_YYYYMMDD.txt ReadMe_AlkermesMktDefBrandXref_YYYYMMDD.txt ReadMe_AlkermesMMDTerritory_YYYYMMDD.txt ReadMe_AlkermesMMDZiptoTerritory_YYYYMMDD.txt ReadMe_AlkermesProduct_YYYYMMDD.txt

Sathya Koteesh

11 All renamed input files

All input and Readme files from all data sources are to be sent via FTP to the “alksftp” folder on the Data Warehouse FTP Server.

Sathya Koteesh

3.2 MDX Processing

Once the input files have been sent by Alkermes to the MDX FTP Server, the next step in the processing cycle of the Data Warehouse is for MDX is produce the current customer extracts. The table below lists the processing steps required to complete this task:


Step # Process Step Owner

1 Once all customer input files have been sent to the “Wait Listed” folder on the MDX FTP Server and are ready for processing, the next step is for Alkermes to push those input files ready for processing to the “Process” folder on the MDX FTP Server. The following is a listing of the release 1.0 preferred schedule for customer input files to MDX:

Sathya Koteesh

Source Name

Frequency Date/Time of Delivery

Daily Weekly Monthly Other

Lash X The Lash data will be delivered on Monday morning of each week to MDX.

WoltersKluwer X The WK data will be delivered to MDX Monday morning of the first week of each month to MDX. In case the file is not received by the prescribed timeline, the file will be made available at the earliest opportunity. This will be communicated manually.

IMS X The IMS data will be delivered to MDX Monday morning of the first week of each month to MDX. In case the file is not received by the prescribed timeline, the file will be made available at the earliest opportunity. This will be communicated manually.

Cephalon X The Cephalon data will be delivered to MDX Monday morning of the first week of each month to MDX. In case the file is not received by the prescribed timeline, the file will be made available at the earliest opportunity. This will be communicated manually.

of 28


CPDB X The CPDB data will be delivered to MDX Monday morning of the first week of each month to MDX. In case the file is not received by the prescribed timeline, the file will be made available at the earliest opportunity. This will be communicated manually.


2 MDX will process the input files and refresh the reports. Once completed, MDX will notify Alkermes by e-mail that the data is ready within MDX for data stewardship.

Jim Wheatcroft

3 Once Alkermes has completed the data stewardship processing, an e-mail will be sent to MDX, stating that the data stewardships activities have ended.

4 Upon receiving the e-mail from Alkermes that data stewardship has completed, MDX will send the following customer extract files to the Data Warehouse FTP Server:X_PARTY_IND_YYYYMMDDHHNNSS.TXT – Professional Master Profile ExtractX_PARTY_IND_XREF_YYYYMMDDHHNNSS.TXT – Professional Cross-Reference Profile ExtractX_ALKERMES_EXTENDED_ATTRIBUTES_IND_YYYYMMDDHHNNSS.TXT – Professional 1-1 Extended Profile Attributes ExtractX_ALKERMES_DERIVED_ATTRIBUTES_IND_YYYYMMDDHHNNSS.TXT – Professional 1-M Extended Profile Attributes ExtractX_ADDRESS_IND_YYYYMMDDHHNNSS.TXT – Professional Master Address ExtractX_ADDRESS_IND_XREF_YYYYMMDDHHNNSS.TXT – Professional Cross-Reference Address ExtractX_PARTY_ORG_YYYYMMDDHHNNSS.TXT – Organization Master Profile ExtractX_PARTY_ORG_XREF_YYYYMMDDHHNNSS.TXT – Organization Cross-Reference Profile ExtractX_ALKERMES_EXTENDED_ATTRIBUTES_ORG_YYYYMMDDHHNNSS.TXT – Organization 1-1 Extended Profile Attributes ExtractX_ALKERMES_DERIVED_ATTRIBUTES_ORG_YYYYMMDDHHNNSS.TXT – Organization 1-M Extended Profile Attributes ExtractX_ADDRESS_ORG_YYYYMMDDHHNNSS.TXT – Organization Master Address ExtractX_ADDRESS_ORG_XREF_YYYYMMDDHHNNSS.TXT – Organization Cross-Reference Address ExtractX_PARTY_IND_ORG_RELATION_YYYYMMDDHHNNSS.TXT – Lash Affiliations ExtractX_SLN_IND_XREF_YYYYMMDDHHNNSS.TXT – Professional State License Extract

Jim Wheatcroft

5 MDX will move the files in the “Process” directory to the “Archived” directory on the MDX FTP Server

Jim Wheatcroft

6 MDX will notify the Data Warehouse Point of Contact as well as Alkermes that the current MDX Extract is available via e-mail.Note: Data Warehouse processing cannot begin until this step has been completed

Jim Wheatcroft

of 28


3.2.1 CPDB Ad-hoc Extract

In release 1.5, the capability to request an ad-hoc CPDB extract was added to the system in addition the regularly scheduled monthly extract. The process for requesting this extract is as follows:

1. Contact MDX (Phone: (800)723-3703; Email: [email protected])

2. Provide the start date of the extract and the end date of the extract. MDX will process the request within 24 hours.

3. Login to the ftp server to retrieve the files.4. MDX ([email protected]) will notify Alkermes IT (Sathya) to

run associated reports from Console. Once reports are available, Alkermes IT (Sathya) will notify Alkermes Business (Wendy).

3.3 DW Processing

Once the extract files from MDX as well as the alignment, roster, and product files from Cephalon and Alkermes are ready for processing in the Data Warehouse, the next step in the processing cycle of the Data Warehouse is for MDX is to refresh the dimension andfact tables. The table below lists the processing steps required to complete this task:


Step # Process Step Owners

1 Once all input files have been sent to the “alksftp” folder on the Data Warehouse FTP Server and are ready for processing, the next step is for Alkermes to send the DW point of contact (Ashish) an e-mail requesting to push those input files ready for processing to the “load” folder on the Data Warehouse FTP Server. The following table is a listing of the Release 1.0 preferred schedule for input files to the Data Warehouse:

Sathya KoteeshJim Wheatcroft (MDX files only)

Source Name

Frequency Date/Time of Delivery

Daily Weekly Monthly Quarterly

Lash X The lASH data will be delivered to the Data Warehouse Tuesday evening of the first week of each month for processing of retail data. This is assuming lLash profile data is processed by MDX on the prior day (Monday). In case the Lash data is not processed by Monday, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance after the files have been received. It will be the responsibility of Alkermes to inform Alliance of availability of data.

of 28





WoltersKluwer X The WK data will be delivered to the Data Warehouse Tuesday evening of the first week of each month for processing of retail data. This is assuming WK profile data is processed by MDX on the prior day (Monday). In case the WK data is not processed by Monday, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance after the files have been received. It will be the responsibility of Alkermes to inform Alliance of availability of data.

IMS X The IMS data will be delivered to the Data Warehouse Tuesday evening of the first week of each month for processing of non-retail data. This is assuming IMS profile data is processed by MDX on the prior day (Monday). In case the IMS data is not processed by Monday, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance after the files have been received. It will be the responsibility of Alkermes to inform Alliance of availability of data.

Cephalon ADM & NAM Zip-Terr, & Hierarchy Alignment

X The Cephalon data will be delivered to the Data Warehouse Tuesday evening of the first week of each quarter for processing of alignment data. In case the data is not available on the prescribed day, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance after the files have been received from Cephalon. It will be the responsibility of Alkermes to inform Alliance of availability of Cephalon Zip-Terr, & Hierarchy Alignment data.

Cephalon ADM & NAMRoster

X The Cephalon data will be delivered to the Data Warehouse Tuesday evening of the first week of each month for processing of roster data. In case the data is not available on the prescribed day, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance after the files have been received from Cephalon. It will be the responsibility of Alkermes to inform Alliance of availability of Cephalon Roster data.

Alkermes Product & Market Definitions

X Alkermes will deliver product/market definitions to the Data Warehouse Tuesday evening of the first week of each month. In case the data is not available on the prescribed day, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance after the files have been received from Alkermes. It will be the responsibility of Alkermes to inform Alliance of availability of Product & Market data.

of 28


Alkermes MMD Zip-Terr & Hierarchy Alignment

X MMD Zip-Terr & Hierarchy Alignment will be sent Tuesday evening of the first week of each quarter. In case the data is not available on the prescribed day, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance. It will be the responsibility of Alkermes to inform Alliance of availability of MMD Zip-Terr and Hierarchy data.

Alkermes MMD Roster

X MMD Roster will be sent Tuesday evening of the first week of each month. In case the data is not available on the prescribed day, the data will be processed based on a mutually agreed-upon timeline between Alkermes and Alliance. It will be the responsibility of Alkermes to inform Alliance of availability of MMD Roster data.

MDX X The MDX Customer data will be delivered to the Data Warehouse each Tuesday evening for processing of Professional and Organization demographic data as well as Lash Affiliations. This is subject to MDX receiving the required files as per the timelines prescribed in the Customer Master Requirements document.


2 The Data Warehouse will refresh the dimension data, base facts, and reporting facts. In case a new report has been generated, an email will be sent by Ashish.

Ashish Choudhary

3.4 Determine Parameters for Processing SMDW Input Files

Here is brief summary of how to determine parameters needed to process Lash (weekly), WK (monthly) and IMS (monthly) files in the current system (R1 and R1.5).

3.4.1 Purpose

For what business purpose do we need to calculate the Data Month, Alignment Cycle and Address lock date?

Data Month is needed for getting the Employee information as well to find out the alignment cycle it is falling in.

3.4.2 Determine Data Month

Notes:

o This is what implemented in the code.

o Cognos reports display reports unto the Data Month.

o Weekly files are loaded in the database but not displayed in the monthly reports until all data for the data month is received.

of 28


o Reports are used for sales planning purposes.

o Should we put something in here how the DATE In the SUBJECT OF EMAILS is determined? Or not, because this will be removed in R2 when we have Cognos for all… IGNORE this comment … just pointing it out but now that I have written it I don’t think we need to update.

Find out the data month of the file:

a. For IMS ( Monthly ) ( Usually received on 23rd of the Month)

Find the Max ( IMS_DT) in the IMS data file.

b. For WK ( Monthly) ( Usually received on 23rd of the Month)

Find the max (Current Data Month) and max (Current Data Year) in WK data file.

c. For Lash (Weekly) Find the date appended to the lash file Find the Month Data Month will be Month -1

3.4.3 Determine Alignment Cycle

Find the Alignment cycle in which the Data Month lies.

For example if data month is Jan 2007 for a file as determined in step 1 and alignment period is Jan 1 2007 to Mar 31 2007 say for MMD alignment. It means that the file with data month of Jan 2007 belongs to that alignment cycle.

Note: Establish a business rule that alignment cycle must start on the first day of the month and end on the last end of the month.

3.4.4 Determine Address Lock Date

Find the address lock date

a. Business alerts Operations Manager (Alliance) that Cephalon file for specified date is the “address lock” date for the alignment cycle.

b. The file will be processed by MDX

c. MDX extract will be processed by DW

d. Address lock date will be the data warehouse processing date of the MDX primary addresses plus 1 day.

While Processing the files , use the address lock date for that alignment cycle where the data month lies to get the following information

a. Professional attributes when the address lock date lies between the start date and end date. In case the Professional was created after the alignment address lock date, determine the first PROF_PIT_SID assigned to the Professional after the address lock date

b. Professional address info when the address lock date lies between the start date and end date. In case the Professional was created after the alignment address

of 28


lock date, determine the PROF_ADDR_PIT_SID of the first primary address assigned to the Professional after the address lock date.

c. Based on the above zip_code for the address derived above, get ADM ALIGN PIT SID, MMD ALIGN PIT SID , ZIP TERR XREF PIT SID from dim_zip_terr_xref table when the address lock date lies between the start date and end date.

d. Based on the above ADM TERR ID and MMD TERR ID get EMP PIT SIDs,

e. one for ADM and one for MMD, from DIM_EMPLOYEE based on the LAST DAY of the data month.

of 28


3.4.5 Examples

Please see when the alignment changed: (Different alignment cycle used in Alkermes till date)

ALIGN_BEGIN_DT|ALIGN_END_DT

1/1/2007|

11/11/2006|12/31/2006

10/1/2006|11/10/2006

8/1/2006|9/30/2006

The table below has all Lash, WK and IMS files processed for a quarter, including the week before and the week after the new quarterly Cephalon file is received.

The table below illustrates how to apply the rules above to input files provided for processing.

File Name Processed on File Source Data Month

Address lock date

Alignment Cycle Start

Alignment Cycle End

Cephalon_datafeed_20070325.txt 20070331 LASH Feb 2007

2/7/2007 1/1/2007


2/7/2007 1/1/2007


2/7/2007 1/1/2007


2/7/2007 1/1/2007

CLI907.R20_20070131.txt 20070317 IMS Jan 2007

2/7/2007 1/1/2007

of 28


File Name Processed on File Source Data Month

Address lock date

Alignment Cycle Start

Alignment Cycle End

ADMPPDATA_20070131.TXT 20070317 WK Jan 2007

2/7/2007 1/1/2007

Cephalon_datafeed_20070218.txt 20070227 LASH Jan 2007

2/7/2007 1/1/2007

Cephalon_datafeed_20070204.txt 20070217 LASH Jan 2007

2/7/2007 1/1/2007

ADMPPDATA_20061231.TXT 20070206 WK Dec 2006

12/12/2006 11/11/2006 to 12/31/2006

12/31/2006

CLI907.R20_20061231.txt 20070206 IMS Dec 2006

12/12/2006 11/11/2006 to 12/31/2006

12/31/2006

Cephalon_datafeed_20070121.txt 20070124 LASH Dec 2006

12/12/2006 11/11/2006 to 12/31/2006

12/31/2006

Cephalon_datafeed_20070114.txt 20070122 LASH Dec 2006

12/12/2006 11/11/2006 to 12/31/2006

12/31/2006

of 28


3.4.6 Database Considerations

Here is how the DataMonth and Address lock date are stored in the database:

SOURCE CURR_DATA_MO COMM_FREEZE_DT MMD_FREEZE_DT ADM_FREEZE_DT NAM_FREEZE_DT

IMS 200701 02/07/2007 00:00:00

WK 200701 02/07/2007 00:00:00

LASH 200702 02/07/2007 00:00:00

of 28


4. Standard Operating Procedures

4.1 Data Load and Address Lock Determination

Step # Description Owner (Primary/Secondary)

1 Manually move files to two different FTP servers, one for MDX (IP Address/login information), the other for the Data Warehouse (IP Address/login information). Once completed, notify MDX (Phone: (800)723-3703; Email: [email protected]) that files are ready for processing.

Sathya/TBD

3 MDX processes the new files and notifies Alkermes Data Steward(s) when processing is complete.

Dinesh Kumar/Jim Wheatcroft

4 Alkermes Data Steward(s) perform adjudication. When completed, contact MDX to initate data extracts for Alkermes SMDW.

Wendy Davis/Backup?

7 MDX notifies Data Steward(s) and Alkermes IT when extracts are completed.

Dinesh Kumar/Jim Wheatcroft

8 For every alignment cycle, manually determine the alignment freeze date for each data source based on the Cephalon profile file to be used for freeze addresses.

8.1 John/Wendy indicate via email to MDX which Cephalon Profile file they want to use to lock primary address for aligning the customers and organizations.

John Fritch/Wendy Davis

8.2 Once John/Wendy indicate which Cephalon Profile file they want to use to lock primary address, the outcome of Step 1 through Step 7 above will yield an MDX extract that contains output from this file.

John Fritch/Wendy Davis

8.3 Once the MDX extract is received, note is made of the exact date on which this MDX extract was loaded in Data Warehouse. One day is added to that date and that is what determines the alignment freeze date for the new alignment cycle.

Sudharm Jain/Backup?

9 Alliance Project Team processes new MDX ext ract files are ready to be processed in the Data Warehouse as well as any new fact data (currently, Lash on a weekly basis, IMS and WK on a monthly basis). If starting a new alignment cycle, a new alignment freeze date will calculated for each source for that alignment cycle.

Sudharm Jain/Backup?

10 All report & base fact tables are refreshed and aligned based on the alignment freeze date.

Sudharm Jain/Sreenivasa Avula

of 28



This process will be used until Release 2.0 is live in production, at which time the operations will be turned over to the Alliance Operations Team. Coordination of operations and support will be managed by the Alliance Life Sciences Practice.

of 28


5. Appendix A: User Access Request

Date Requested: ___________________________________________

MDX User Request:

User Name Read-Only – Run queries and reports only

Data Steward – Full MDX Functionality

Alkermes Approval

Cognos User Request:

User Name Consumer – provides ability to perform queries and browse data

Business Author – provides Consumer capability with additional ability to construct basic reports

Professional Author – provides “developer” capability to construct complex reports and analytic scenarios

Alkermes Approval

of 28


6. Appendix B: Operations Process Flow

of 28


7. Appendix C: Monthly Report QC Procedure

7.1 General Information

Data Month :1. Max(Data Month in the IMS & WK file) for IMS & WK 2. Current month - 1 for LASH.

7.2 Acronyms and Definitions

Acronym Definition

ADM Addiction Medicine

MAT Moving Annual Total (Rolling 12 Months)

MMD Manager, Market Development

MQT Moving Quarterly Total (Rolling 3 Months)

RD Regional Director

YTD Year to Date

SMDW Sales and Marketing Data Warehouse

WK Wolters Kluwer

R1 Release 1.0

R2 Release 2.0

MDX Master Data Exchange

DW Data Warehouse

The Cognos server we use is web1(10.2.69.10) for creating all the report outputs. This server is mapped to the D: in the procedure below.

of 28


7.3 Procedure steps

Data Month: <Enter data month>

Data Source: <Enter data source – IMS, WK, Lash>

Steps Owner Test Case Completion Date

Remarks

1. Validate the Drill Through reports

Alliance/Sree Avula

Validate the data in all the reports, check the totals from monthly match to the:Year to Date (YTD) – January through the current data monthMoving Annual Total (MAT) – sum of the previous 12 data monthsMoving Quarterly Total (MQT) – sum of the previous 3 data months.Other Validations?Totals for Territories, Regions and Nations levels.

2. Run all the three jobs to generate IMS, LASH and WK report outputs for all the Alkermes territories and regions.

Alliance/Sree Avula

Check the status of the jobs and all the reports to make sure there are no errors.

3. Check the report outputs in the Cognos connection for the data.

Alliance/Sree Avula

Validate all the data in the reports. Match the monthly totals to the YTD, MAT, PMAT, MQT, etc and the totals for Territory to Region and Nation.

4. Inform Wendy to QC the drill through reports and distribution reports

Alkermes/ Wendy Davis

Check with Wendy if she finds any errors and correct the errors.

5. Check the output directory on the Cognos server.

Alliance/Sree Avula

Check the output directory, D:/C8_OutPut, for the report outputs.There should be Total 96 outputs, it could vary from 93-96 depending on the unknown territory. The Unknown territory may or may not occur based on all the zip codes are mapped to one of the territories.MMDs (28 MMD Territories and 1 Unknown

Page 1 of 28


Steps Owner Test Case Completion Date

Remarks

Territory) 29*3 = 87,RDs – 3*3 =9.

6. Run the script to convert all the mht files to excel

Alliance/Sree Avula

Check for the count of reports converted to Excel format in the directory, D:\C8_Output\XLSFiles Should be same as above,96, as in Step 5.

7. Run the renaming script

Alliance/Sree Avula

Check for the total number of reports renamed in the directory D:\C8_Output\XLSFiles\RepOutputs, and the count should be 96.

8. Run the script to distribute the reports by email

Alliance/Sree Avula

Check the number of emails sent out in the scripts log. Check with Wendy to make sure all the reports are sent out and present in the [email protected] inbox.

Page 2 of 28

alk_ operations manual v1.6

Documents

alkermes sales

document purpose

system users

mdx processing

data warehouse input

data flows

user access levels

mdx input files