1. File Submission Guidelines (Digital Assets)
Global MCM Operations
File Submission Guidelines (Digital Assets)
August 2015
Version 5.0

2. 1 2 3 4 5 Topics Review Program Dependencies
File Submission Guidelines Overview & Definitions 2
File/Folder Standards, Naming Conventions, Required Deliverables 3
File Transfer Logistics 4
Build File Examples (Only if requested by Merck)
Review Program Dependencies 5
Review Program Dependencies
References 2 2 2

3. File Delivery Guidelines Overview
Global Standards for creative agencies and digital publishers to ensure source files are delivered consistently, audited, and stored in Merck’s official digital asset management repositories
Toolbox/Telescope DAM
Asset scope:
Web / eDetail
Banners
Video
MerckOnCall
Mobile
iPad
Audience:
Creative Network
Editorial
Creative Agencies
Design Support Services
MCM Operations
Digital Publishers 3 3 3

4. Definitions
Asset: The "Job" or "marketing material" delivered to a target audience ( , banner, website, etc)
Assets go through the creative business process (including PRT review)
“Resource”
Creative Artifacts: Creative source files and associated supporting documents (i.e. wireframes, functional specifications, etc.)
Telescope Digital Asset Management (Telescope DAM or “GDAM”): Merck’s global digital asset management repository
Global MCM Digital Publisher (DP-Production Team): Digital publisher that audits creative artifacts from agencies and builds global MCM assets for delivery to regions – Also referred to as Production Team
MultiChannel Marketing (MCM): Integrated approach to marketing using multiple online and digital delivery channels to re-enforce brand messages 4

5. Definitions
Promotional Review (PRT): Merck’s Medical Legal (M/L) review process for promotional assets
Source File: A digital file which can stand alone or be incorporated into and become part of an asset (.psd, .html, .gif, .fla, .swf, etc.)
Source files are compiled using digital publishing tools to “build” assets
Toolbox: User friendly portal providing visibility to Merck’s global assets contained in the digital asset management repositories. Users can view thumbnails of assets, access demo links, get direct links to source files and final medical legal PDFs.
Transfer Site: Wam!net site for sending/receiving files between Merck regional/country teams
Vendor Site: Wam!net site for sending/receiving files to/from specific regional vendors
Wam!net: Secure internet based portal accessible external to the Merck infrastructure. Access credentials are required and visibility to available transfer sites and packages for download is controlled with agency/partner level permissions. Wam!net provides the ability to both send and receive source file packages.
Zinc: Promotional review system 5

6. 1 2 3 4 5 Topics Review Program Dependencies
File Submission Guidelines Overview & Definitions 2
File/Folder Standards, Naming Conventions, Required Deliverables 3
File Transfer Logistics 4
Build File Examples (Only if requested by Merck)
Review Program Dependencies 5
Review Program Dependencies
References 6 6 6

7. Standard Folder Structure
Submit files in this structure via Wam!net
A package will fail the audit if folder structure and naming conventions are not followed.
Fonts: Check with Legacy PMs 7 7

8. Naming Conventions / Standards
Folder Naming:
Top Level Folder = Merck Job Number
Job number format: xxxx
Example
DIAB
Subfolders – follow example on standard folder structure previous slide
Design and Source files are excluded from naming conventions, but structure should be clear and easy to follow 8

9. Naming Conventions / Standards Cont’d
Files at the root directory:
Fonts = Fonts_US.zip
Fully Built asset = xxxx _preaudit_yymmdd.zip (only if requested from Merck, will be stored as a separate package in Telescope DAM)
In Design Files= Only for interactive PDFs, iPad Presentations and Merck Connect (requires use of Telescope Plug in – provided to creative agencies once training for Telescope DAM is completed)
Supporting Documents Naming:
Resource code with no dashes first, followed by underscore followed by descriptor
Ex: DIAB _ref.pdf
Dates and status descriptors: Will be removed by DP (Production Team) prior to final storage in Telescope DAM
Sub folders under “Working”: Will be zipped going into Telescope DAM
Other notes:
Character limit 30 is the expected to keep the files name readable, although the system accepts 64
Avoid using symbols, slashes and other non-standard characters
30 MB PDF file size limit (keep the PDF as small as possible keeping quality into consideration)
1.8 GB file size transfer limit on Wam!net
Agencies are strongly encouraged to start with the required file structure on every job; however, please eliminate an empty subfolder if there is no relevant content for the given job 9

10. Naming Conventions / Standards Cont’d
Imagery Requirements
Layered, Hi-Res, and Lo-Res flattened Photoshop files are required for all imagery
Hi-Res: Flattened Photoshop files, RGB Interactive, 300 DPI
Layered: Layered Photoshop files, .psd
Lo-Res: Flattened Photoshop files, 72 DPI, “_LR” is to be added to file name before .psd
Charts and Artwork Requirements
See Print File Submission Guidelines
Adobe Illustrator CS6 or lower
Print Requirements and Interactive PDFs
Adobe In Design CS6
Requirements: Link to original requirements – apropriate documents 10

11. Agency File Submission Requirements
Document
Websites / Microsites / eDetail / Mobile Web
Merck Connect
Banner
Video / Audio
Mobile Apps
iPad
Rep Enabled
Mockups
InDesign Files
N/A R
Layered Photoshop Files
Other Creative Files
Font Files ?
High / Low Resolution Image File
Thumbnails
Required Supporting Documents
Contracts and Signed Releases
Permissions / Meta Contact Sheet
Copy Manuscript
PRT Approved PDF
Editable Annotated PDF
R (for Global) *
R (for Global)
Creative Release Notes
Visual Store Mock-Up doc
Quality Assurance Plan (QAP)
Other Supporting Documents
Functional Requirement Specification
Style Guide
Opt
Site Map / Wireframes
Story Board / Schematic
Video / Audio Files
Flash Files
Traffic Workbook
Checklist (US Only)
Mobile: more documents need to be added
* For global projects where ePublish and Merck Connect use the same design and copy for each job, Agency is required to provide Annotated PDFs for each job.
Key: R – Required, Opt – Optional, N/A Not Applicable

12. Agency File Submission Requirements Assumptions (1/3)
Document
Assumptions
InDesign Files
Agencies are required to use In Design Templates provided by Merck for MerckConnect and iPad.
InDesign should also be used for delivering Interactive PDFs.
Font Files
Any non-web based font should be included.
The following formats are required for non-web fonts for HTML projects to ensure they will be rendered on all browsers and computers: wof, oet, ttf and svg.
High / Low Resolution Image File
Hi-Res: Flattened Photoshop files, RGB Interactive, 300 DPI.
Lo-Res: Flattened Photoshop files, 72 DPI, _LR added to file name before .eps or .tif. JPG or PNG preferred.
Vector: Illustrator Art.
Layered Photoshop Files
CS6 format. All graphics need to be on separate layers from text.
Deliver 1 PSD file per page of the assets (eDetail / Website).
Thumbnails
iPad Full image: 1024px by 768px.
iPad Thumbnail file sizes: iRep (Height: 150 pixels, Width: 200 pixels), iSales (Height: 155 pixels, Width: 210 pixels).
Copy Manuscript
See ePublish Copy Manuscript Template for this channel.
All content/text should be included within this documentation, include images, graphs and buttons for Global.
Match copy styles with style guide.
Websites/ Microsites/eDetails/Mobile assets require content metadata to be submitted as part of the copy manuscript and technical metadata to be submitted in a requirements specification.
For iPad the copy manuscript does not need to be provided by the agency as a separate deliverable if all the copy is fully detailed and selectable in the InDesign text layer or the approved editable PDF.
For audio/video projects all copy should have timing information specified for use in adding subtitles or for any editting necessary. 12

13. Agency File Submission Requirements Assumptions (2/3)
Document
Assumptions
Contracts and Signed Releases
Signed agreements, model releases.
Permissions / Meta Contact Sheet
Invoices that document usage rights , not agreements.
Refer to the image submission guidelines.
Functional Requirements Specifications
Websites/Microsites/eDetails/mobile assets require technical metadata as well as all functionality descriptions to be submitted in a functional requirements document.
For iPad, outline the Navigation Functions throughout the presentation.
Style Guide
Brand/product colors (HEX and RGB values)
Font styles matching copy manuscript, including font family, color, and size (ie. Header – Arial Regular, 12 px, blue)
General measurements, including width, margins and global elements (the DP/Production Team cannot guarantee exact measurements will be used if information is not provided here) – Required for all channels
All measurements and sizes should be provided in pixels
For global: Any direction notes for local markets on possible modifications
For audio/video projects directions on font styles for on-screen text, and directions for subtitles (size, location, font, color) should be included
Merck Connect does not require style guide, as this platform has a standard style guide that must be followed for all ptojects
Site Map / Wireframes
Site Map can be included in “Functional Requirements Specifications”.
For iPad, refer to the new template provided by the Creative Network team.
Story Board / Schematic
A storyboard/schematic needs to be provided for all non low complexity animations included on all projects types, and for all iPad projects.
PDF or MS Word format.
Detailed description of the animation/interactivity should be included, as well as all timing information (stops/pauses, etc).
For iPad, selectable copy must match the approved PDF and contain all copy present in the animations. 13

14. Agency File Submission Requirements Assumptions (3/3)
Document
Assumptions
Video / Audio Files
Editable video files for final video and all animations included. For example After Effects or Final Cut files
Rendered MP4 file. Max. size 300 MB (under 100 MB preferred) (must confirm format with PM, since it may vary according to requirements)
Clean voice over audio file
Clean background audio file
Clean SFX audio file
For iPad videos being used within the iSales/iRep platform, agencies must review the iPad Cookbook – Creative Guide for video file size limitations, resolution, and bit rate requirements.
Flash Files
For any content in Flash format.
Include .fla and .swf.
Visual Store Mock-Up doc
This form ensures that only proper data (including all wording, screenshots and icons) is displayed on the app store.
Quality Assurance Plan (QAP)
For Mobile Apps, this document describes what the scope is of the app, identify who is responsible for testing the app per phase, what kind of test scenarios are expected, etc.
For all other asset types, this document enumerates the asset specific functionality that should be tested in addition to the standard test scripts.
Creative Release Notes
Document listing all the files included in the assets package with any relevant notes by the Creative Agency.
Traffic Workbook
For banners only
Checklist (US Only)
The Digital PM provides the initial checklist to the agency.
The agency provides the URLs and footer guidance.
PRT Approved PDF
Approved reference PDF
Editable Annotated PDF
Required for global projects only.
Guidelines to create the Editable Annotated PDF can be found on the ZINC website (zinc.merck.com).
To get access to zinc.merck.com, all creative agencies need to complete mandatory training.
* For global projects where ePublish and Merck Connect use the same design and copy for each job, Agency is required to provide Annotated PDFs for each job. 14

15. Required Documents at Key Steps
Initial Estimates
Initial Audit
Final Asset Submission
Project Scope
Creative Schedule
Action Memo, if available
Assets package with required documents based on the file submission requirements
For a simple asset update to an existing resource: Change Log, creative files (if needed), and revised PDF (if creative source files are to be updated)
All remaining documents required based on the Final Delivery Audit checklist results
Change Log and revised Screenshots PDF, if source files were updated
Final Estimates
Project Scope
Reference PDF
Site Map / Wireframes
High Level Functional Requirements
Action Memo, if available 15

16. 1 2 3 4 5 Topics Review Program Dependencies
File Submission Guidelines Overview & Definitions 2
File/Folder Standards, Naming Conventions, Required Deliverables 3
File Transfer Logistics 4
Build File Examples (Only if requested by Merck)
Review Program Dependencies 5
Review Program Dependencies
References 16

17. Transfer Logistics for Files – New Asset
Global AMS posts and facilitates transfer of Print and MCM assets internationally through Toolbox. 4
Editorial certifies the M/L PDF in Zinc and the Promotion Admin updates the asset status in Telescope DAM (if applicable) 6
ToolBox
(Asset Browsing)
Zinc
Demo Servers
Telescope DAM
(Asset Repository)
WAM!NET
(Download Portal) 5
Global MCM DP (Production Team) uploads digital build/source files to Telescope DAM. AMS uploads print.
Telescope DAM Hot Folders
Global MCM DP (Production Team) hosts a demo of the asset on demo servers for review/approval and uploads the M/L PDF to Zinc.
WAM!NET
(Upload Portal) 3
MSD Multichannel Digital Publisher
899729
Agency uses Wam!net account to trade files with Merck
Merck_GDAM_PROD
(883529) 1 2
Global MCM DP (Production Team) audits and builds the digital assets.
Digital
Print
Notes:
International Print files go to Telescope DAM directly
Agency A
Agency B
Agency C

18. Transfer Logistics of MCM Files – Update to existing asset
Update - PDF or “Agency” build files affected
Agency sends full creative source package including update and revised PDFs over Wam!net
Include change description and summary of files affected in release notes
DP (Production Team) audits and updates creative source files/agency build files
DP (Production Team) updates annotated pdf and uploads into ZINC
Editorial provides certification in ZINC
DP (Production Team) uploads final assets to Telescope DAM
Asset Management Services (AMS) updates Toolbox when necessary
QC issues - PDF not affected and Agency build files not affected
Agency sends updated creative source files only over Wam!net
Agency includes change description and summary of files affected in creative release notes
DP (Production Team) audits and updates changed creative source files
DP (Production Team) updates changed build files to Telescope DAM
As soon as the annotated PDF is changed, the change will be categorized as an update 18

19. Wam!net http://portal.wamnet.com/ Audience: Creative Agencies
Source Files for an MCM asset are transferred between Merck global, regional, and local MCM delivery hubs, their agencies, and the Production Team partners via Wam!net
Wam!net is a secure internet based portal accessible external to the Merck infrastructure
Access credentials are required and visibility to available transfer sites and packages for download is controlled with agency/partner level permissions
Wam!net provides the ability to both send and receive source file packages 19

20. MSD Multichannel Digital Publisher
Wam!net Transfer Sites
MSD Multichannel Digital Publisher
899729
Merck_GDAM_PROD
(883529)
MSD Multichannel Digital Publisher (Production Team) (899729)
For delivery of MCM assets and source files to Merck’s global DP (Production Team) for audit and build (International and U.S.)
Merck_GDAM_PROD (883529)
For delivery of M/L approved International Print assets to Asset Management Services for loading into Telescope DAM 20

21. On-Boarding New Agencies to Wam!net
New Agencies need to request setup on Wam!net
Print
Please contact to request a Wam!Net account with access to Merck &Company Inc. (754701), as well as Merck_GDAM_PROD (883529).
Please request a Wam!net account for your agency. (Note, one may already exist in which case you will be provided the login credentials)
MCM Assets
Send request to
Please request a Wam!net account for your agency (Note, one may already exist in which case you will be provided the login credentials)
Please also request trading permissions with the MSD Multichannel Digital Publisher (Production Team) (899729) site 21

22. On-Boarding New Agencies to Telescope DAM
Audience: Creative Agencies and Asset Librarians
Telescope DAM ( is Merck’s official digital asset management repository in the Presto suite of applications (launched July 2011)
Agencies can request files using the File Request Form. Further instructions for this can be found in the Supplier Onboarding slide deck on the ePublish cookbook site. 22

23. 1 2 3 4 5 Topics Review Program Dependencies
File Submission Guidelines Overview & Definitions 2
File/Folder Standards, Naming Conventions, Required Deliverables 3
File Transfer Logistics 4
Build File Examples (Only if requested by Merck)
Review Program Dependencies 5
Review Program Dependencies
References 23 23 23

24. Build File Examples Web/Mobile Site eMail Banner Video MerckOnCall
Mobile App
iPad 24

25. Structure of Build Files (Website & Mobile Website Example)
DIAB _build_preaudit_ zip
The image on the left illustrates an example of the folder structure for a Merck website contained in the “Job Number_build_preaudit_version date.zip” file.
The htdocs folder structure holds all images, style sheets, documents (such as PDFs), Flash animations, JavaScript files, and files for download
The java folder structure holds all JSP files
For mobile web, java and flash folders aren’t needed. The top folder must be called m.xxx.com
All directory and file names must be descriptive; if the name has multiple words, place underscores (_) between each word.
ALL FILE NAMES ARE TO BE LOWERCASE.
NOTES:
When working with an existing website, please do not change the folder structure that is provided by Merck IS. If there is a need to change folder names or remove folders, contact Merck IS first to discuss the impact. New folders may be added and must comply with the naming guidelines stated above
In the case that Merck sends filenames in mixed-case to the agency, please convert the filename to lowercase and adjust all HTML accordingly.
This is just an example, some projects may not have all the folders or may contain a different structure based on the needs of the website. 25

26. Structure of Build Files (Email Example)
DIAB _build_preaudit_ zip
Note: The images can be placed in a subfolder named “images” 26

27. Structure of Build Files (Banner Example)
DIAB _build_preaudit_ zip
Note: Banners can be placed in a subfolder named “images” with a index.html file
that references the banners. 27

28. Structure of Build Files (Video Example)
DIAB _build_preaudit_ zip
The build folder for videos is used to hold just the files that are needed to run the video properly.
Some video formats may not require additional files to run (i.e. .mov). In that case, a single file will be in the zip file.
Any file that was used to create the video but not necessary to run it will be storage in respective folders inside “sources” zip file. (Working folder) 28

29. Structure of Build Files (MerckOnCall Example)
DIAB _build_preaudit_ zip
All Directory names should not contain any spaces (being replaced by underscores) and should be lower case (e.g., The directory "Merck Medical Forums" should be changed to "merck_medical_forums").
Style sheets (if used) shall reside in the “css” folder.
Any Flash animations or .flv video files shall reside in the “flash” folder (Flash no supported on Veeva, iSales and BTC presentations).
All images as well as the “thumbnails” folder with all thumbnails shall reside in the “images” folder as per the displayed example.
root_folder
 css
*.css
 flash
*.swf
*.flv
 images
*.gif (.jpg, .png)
 thumbnails
page00thumb.jpg
page01thumb.jpg
page00.html
page01.html 29

30. Structure of Build Files (Mobile app Example)
DIAB _build_preaudit_ zip
Note: the folder structure for mobile apps may vary from one project to another. 30

31. Structure of Build Files (iPad Example)
Note: iPad assets may include multiple zip files with the structure above depending on the need for tracking individual key messages on the iPad players . 31

32. 1 2 3 4 5 Topics Review Program Dependencies
File Submission Guidelines Overview & Definitions 2
File/Folder Standards, Naming Conventions, Required Deliverables 3
File Transfer Logistics 4
Build File Examples (Only if requested by Merck)
Review Program Dependencies 5
Review Program Dependencies
References
Jai: Before submitting the assets, please review checklist 32 32 32

33. References Global MCM Operations Cookbooks
ePublish Cookbook Website (cookbook.epublishmerck.com)
iPad Resources Website
(cookbook.epublishmerck.com/ipad-resources//) 33