Constellation Digital Workflow System – Phase One Software Requirements Specification

Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11

Sony Electronics Inc. Solutions Engineering B2B of America San Jose, CA 95112

Control No. 961-502101

Revision 1.11

Revision Date: 11/8/2009 2:40 PM

Approvals:

< Name> Signature Date < Name> <Title> Signature Date < Name> <Title> Signature Date < Name> <Title> Signature Date < Name> <Title> Signature Date 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page i Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Last edited: 08 November 2009 Copyright © 2009 Sony Electronics Inc. All rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission from Sony Electronics Inc. All copyright, confidential information, patents, design rights and all other intellectual property rights of whatsoever nature contained herein are and shall remain the sole and exclusive property of Sony Electronics Inc. The information furnished herein is believed to be accurate and reliable. However, no responsibility is assumed by Sony Electronics Inc. for its use, or for any infringements of patents or other rights of third parties resulting from its use. The Sony name and Sony logo are trademarks or registered trademarks of Sony. All other trademarks are the property of their respective owners 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page ii Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Document History Paper copies are valid only on the day they are printed. Contact the author if you are in any doubt about the accuracy of this document. Revision History Revision Number Revision Date Summary of Changes Author 0.01 03/20/2009 Initial Draft David Carroll 0.02 03/26/2009 Update David Carroll 0.9 06/16/2009 Interim version David Carroll 1.0 07/05/2009 Release version David Carroll 1.1 08/25/2009 Update from developer David Carroll comments 1.11 11/08/2009 Update with SPE comments David Carroll Reference Documents Please see the following documents for more information: Document Name Version Author Constellation White Paper, Sony B2BoA Solutions Engineering 1.0a J. Farney, P. Lude, D. Carroll, G. Mirsky IEEE Std 830‐1998 Rec ‐ Software Requirements Specifications 1998 IEEE SPE‐SEL Functional Process Requirements, services list 5.5 E. Ito, D. Carroll SPE Production Digital Backbone Functional Specifications 1.02 Kalyani Ramajayam Distribution List This document has been distributed to: Name Position Company Action 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page iii Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Table of Contents 1 INTRODUCTION ...... 1 1.1 Purpose of this document ...... 4 1.2 Scope...... 4 1.3 Top Level Requirements...... 5 1.4 Organization Profile ...... 5 1.5 Conformance Notation ...... 5 1.6 Assumptions ...... 7 1.7 Constraints...... 7 1.8 Dependencies...... 7 2 OVERALL DESCRIPTION...... 8 2.1 Product Perspective...... 8 2.2 Functional Requirements - Operating Environment ...... 9 3 FUNCTIONAL REQUIREMENTS ...... 11 3.1 Functional Requirements - Platform...... 12 3.2 Functional Requirements - System ...... 14 3.3 Functional Requirements – Workflow ...... 19 3.4 Functional Requirements – Third Party Products/Services...... 21 3.5 Functional Requirements – Web Services ...... 24 3.5.1 Generic or abstract services...... 24 3.5.2 Derived services...... 25 4 DASHBOARDS...... 29 5 SAMPLE USE CASES...... 35 5.1 Film Process ...... 35 5.1.1 Film to Digital Motion Picture Workflow...... 35 5.1.2 Full Digital Motion Picture Workflow...... 36 5.2 Episodic Television Process ...... 37 5.2.1 Film to Digital TV Workflow ...... 37 5.2.2 Full Digital TV Workflow ...... 38 5.2.3 Other Television Workflows...... 38 5.3 Commercial Workflows ...... 39 6 SYSTEM ARCHITECTURE...... 40 6.1 Media SOA ...... 40 6.2 Media Bus...... 40 6.3 Capacity Requirements...... 41 6.4 User Interfaces...... 41 6.5 System Structure ...... 41 7 REFERENCES ...... 44 7.1 General References...... 44 7.2 Media Format References ...... 44 8 ACRONYMS...... 45 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page iv Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 9 GLOSSARY ...... 47 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page v Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Table of Figures Figure 1 - Traditional Kodak Film Optical Workflow...... 1 Figure 2 - Film to Digital Workflow ...... 2 Figure 3 – Typical Digital Production Pipeline ...... 3 Figure 4 - Typical Media Workflow System Architecture ...... 8 Figure 5 - Dashboards & Monitoring ...... 30 Figure 6 - Film to Digital Motion Picture Workflow...... 36 Figure 7 - Full Digital Motion Picture Workflow...... 37 Figure 8 - Film to Digital TV Workflow ...... 38 Figure 9 - Full Digital TV Workflow ...... 38 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page vi Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 1 INTRODUCTION For the past 20 years, digitization of film and video tape content, coupled with the use of Information Technology (IT) and computers for content processing have steadily transformed the creation and finishing of motion pictures and television programming. While this “computerization” of content creation has offered many new creative tools and efficiencies, it has also disrupted finely tuned processes that had remained largely unchanged for a very long time—over 50 years in the case of film. In its place are a variety of costly ad‐hoc processes that have so far resisted the creation of a uniform, well‐understood workflow that can be applied again and again in an efficient, predictable, and cost‐effective manner. Figure 1 - Traditional Kodak Film Optical Workflow 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 1 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 As media workflow has evolved from those based on tape and film to new workflows based on files, the industry has lagged far behind in building repeatable, efficient methodologies. Like so many early phase technology transitions in other industries, current IT centric media processes are based on simple substitutions of new technology for old—and that is no longer acceptable to customers. Today’s workflow models are inefficient, too reliant on human involvement, and consequently far too expensive and unpredictable. They depend on “hardwired” or “hard coded” implementations that are difficult to change and provide no business agility. In certain activities such as news production, there is a very consistent process or workflow that can be designed once (like SONAPS), and reused as‐supplied by many customers. However, in the production of episodic television, feature films, and most types of programming the reality is that every producer, studio and facility has a different approach—sometimes even from project to project. Many of the studios, content companies, and large media facilities are looking for an approach that overcomes these issues and enables a “factory” approach to content creation. This “content factory” must remain flexible and adaptable to allow for changes in business direction, new opportunities, and replacement equipment cycles—providing much‐needed business agility. These goals are not realistically achievable with current facility designs based on hardwired point‐to‐point equipment connections and hard coded software designs. An entirely new approach is required—one that leverages open standards and the latest IT architectures. Figure 2 - Film to Digital Workflow At the heart of this “content factory” is a Service‐Oriented Architecture (SOA), an architecture based on independent, wrapped business services communicating via published interfaces over a common middleware layer. A wrapped business service is a tangible service such as transcoding or asset management with a business‐level abstraction layer that provides an implementation independent interface to the middleware, effectively making the service appear as a “black box”. SOA exists for one reason—to allow business people to quickly make business decisions that adjust and optimize the operation of the “content factory” without concern for or detailed knowledge about the underlying technology. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 2 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Figure 3 – Typical Digital Production Pipeline Today, making a feature film or dramatic television program involves many specialized skills and creative services, as well as a number of processing steps in the production pipeline. Major studios and production facilities have a number of departments which provide these services and well defined interfaces and deliverables for each step in the process (or workflow). To provide business agility, these workflows must be easily reconfigured without redesigning the hardware or software infrastructures that support them. The Sony Digital Media Workflow System (code name “Constellation”) is a comprehensive software infrastructure and management toolset that incorporates business goals, business rules, operational requirements, schedules, conditional access, and security to orchestrate existing and new components of the “content factory” to achieve maximum efficiency, predictability, and speed while minimizing operational costs. This solution must remain flexible and adaptable, and provide up‐to‐the‐minute visibility and insight into the operation of the facility. To the extent possible, it will utilize and conform to both Media and IT industry standards, and leverage the cost efficiencies of the larger IT industry. Ideally, this system will store the minimum needed elements to provide any and all deliverables as required. This implies storing only the highest quality elements and performing all necessary processing on-the-fly. Although most of the elements of the SOA infrastructure are already well established in the IT industry, it is the special provisions made to handle large media files (the Media Bus) and the media- specific “Media Workflow Engine” and associated middleware that orchestrates and optimizes all the processes of the factory that enable the Sony Digital Media Workflow System or “Constellation” to meet the unique needs of the media enterprise. This document describes the design specifications for the Sony Digital Media Workflow System or “Constellation”. Detailed interface specifications are outside the scope of this document. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 3 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 1.1 Purpose of this document This Functional Requirements document defines the functional and non-functional requirements for the Sony Digital Media Workflow System, Phase One, known as “Constellation”. 1.2 Scope This section defines the scope of the Sony Digital Media Workflow System, Phase One, known as “Constellation”. The system shall handle Ingestion, Storage, Content Processing and Movement of media assets during the post production lifecycle. Scope includes Workflow orchestration, process orchestration, business process management, ESB, application server, generic web services interfaces for major workflow functions, wrappers for existing best of breed media industry hardware products, applications, and services Generic system interfaces to business systems, work order systems, MAM systems, storage management systems, product and production databases, Identity Management systems, other existing proprietary business process systems, and third party web services based systems ** Developing a Library of templates or sample workflows to be provided with the product Developing a Library of Wrappers for specific existing third party and Sony product APIs to be connected as web services Developing applications to bridge between a non‐web service API for a service and provide a web service or other interface to the orchestration engine or application server. Integrating Sony Unique Services exposed as web services and built in functions, like transcoding, compression, codecs, etc. Scope excludes Pre‐production systems Content Production, on set, or on location production systems, except where such systems are used specifically to perform post‐production tasks like ingest, dailies production, picture edit, transcoding, etc. Content Distribution systems used for down‐converting, transcoding, encoding, compressing, packaging, watermarking, or distributing finished content for broadcast, home video, theatrical, or other end use. ** NOTE: Specific interfaces to external systems will be covered in separate interface description documents. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 4 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 1.3 Top Level Requirements Requirement ID Requirement TLR‐00‐0001 The system shall handle Ingestion, Storage, Content Processing and Movement of media assets during the Production Lifecycle. TLR ‐00‐0002 The system shall preserve the quality of high resolution assets through the Production Lifecycle. TLR ‐00‐0003 The system shall provide means of automation of repetitive and non creative tasks in the Production Lifecycle. TLR ‐00‐0004 The system shall enable creative artists to flexibly define workflows based on their production goals. TLR ‐00‐0005 The system shall provide means to decrease the use of Physical Media (tape and portable hard disks) in the Production Lifecycle through use of file based workflow. TLR ‐00‐0006 The system shall allow entities in the Production Lifecycle to access assets in the most effective manner. TLR ‐00‐0007 The system shall maintain Security of assets throughout the Production Lifecycle. TLR ‐00‐0008 The system shall implement a Service Oriented Architecture approach that allows for: Modularity and flexibility: Ability to mix / swap decoupled service components Scalability: Ability to expand system throughput (horizontally and vertically) Reusability: Ability to leverage services across multiple workflows TLR ‐00‐0009 The system shall provide integration of workflow orchestration leveraging SOA based service components to facilitate the automation of content handling during the Production Lifecycle. TLR ‐00‐0010 The system shall facilitate reusability of assets when needed, by providing a robust asset retrieval system. 1.4 Organization Profile This Functional Requirements document is sponsored by the Sony B2B of America Solutions Engineering group in cooperation with the B2BoA Beyond HD Workflow Development project, the Sony Digital Backbone task force, and Sony Pictures DMG. 1.5 Conformance Notation Normative text is text that describes elements of the design that are indispensable or contains the conformance language keywords: "shall", "should", or "may". Informative text is text that is potentially helpful to the user, but not indispensable, and can be removed, changed, or added editorially without affecting interoperability. Informative text does not contain any conformance keywords. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 5 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 All text in this document is, by default, normative, except: the Introduction, any section explicitly labeled as "Informative" or individual paragraphs that start with "Note:” The keywords “must”, "shall" and "shall not" indicate requirements strictly to be followed in order to conform to the document and from which no deviation is permitted. The keyword “must” indicates support is mandatory. The keywords, "should" and "should not" indicate that, among several possibilities, one is recommended as particularly suitable, without mentioning or excluding others; or that a certain course of action is preferred but not necessarily required; or that (in the negative form) a certain possibility or course of action is deprecated but not prohibited. The keywords "may" and "need not" indicate courses of action permissible within the limits of the document. The keyword “reserved” indicates a provision that is not defined at this time, shall not be used, and may be defined in the future. The keyword “forbidden” indicates “reserved” and in addition indicates that the provision will never be defined in the future. Unless otherwise specified, the order of precedence of the types of normative information in this document shall be as follows: Normative prose shall be the authoritative definition, tables shall be next, followed by formal languages, then figures, and then any other language forms.11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 6 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 1.6 Assumptions Assumption Impact Product will use Java J2EE on Linux OS Microsoft shops will be reluctant to adopt Product will use open source and open standards where Some major vendors may not fully support open possible standards 1.7 Constraints Constraint Impact Product must be demonstrable at NAB in April 2010 Some features may be deferred Product must be Beta install at SPE by April 30, 2010 Some features may be deferred Product must be deliverable by September 30, 2010 1.8 Dependencies Dependency Description 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 7 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 2 OVERALL DESCRIPTION The Sony Digital Media Workflow System (known as “Constellation”) is a Service Oriented Architecture (SOA) based system for media workflow management for file based post production operations. This system is “Middleware” that provides workflow orchestration for media operations. In addition, some traditional applications and web services, as well as service wrappers or interface (API) adapters may be provided to support specific required functionality. Phase One of the Sony Digital Media Workflow System is designed to support Post Production only, and has an initial set of features and services that targets Sony Pictures Entertainment requirements. Additional phases of ongoing product development will result in additional features and support for additional services and other parts of the motion picture and television digital production and distribution workflow. 2.1 Product Perspective This system is a new product based on current IT industry Web Services and SOA architecture standards, as well as media industry standards for file based post production workflows. It is intended to be scaleable from relatively small systems for use by boutique post production and effects companies and on location productions to large post production facilities, television networks, and major motion picture studios. Figure 4 - Typical Media Workflow System Architecture 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 8 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 2.2 Functional Requirements - Operating Environment Requirement ID Requirement FR‐00‐0001 The operating environment for this system shall be standard web services based IT technology, including multiple load balanced Application Servers, Enterprise Service Bus (ESB), Business Rules Engine (BRE), Complex Event Processing (CEP) Engine, Process and Workflow Orchestration Engine with visual or graphical design and testing tools, and Web Services interfaces and wrappers as required. FR‐00‐0002 The system should use open standards including XML, SOAP 1.1, WSDL 1.1, UDDI, BPMN 1.0, WS‐BPEL 2.0, BPEL4People 1.0, XPDL, WS-HumanTask 1.0, WS‐policies, XML Schema 1.0. FR‐00‐0003 The system should use J2EE on LINUX (Red Hat Enterprise Server) operating system where possible. FR‐00‐0004 The system shall interface to Oracle 10g or above SQL relational database as the internal and preferred external database, and may also support external Microsoft SQL Server, and other SQL based databases. Note: SPE has selected Oracle 11g as their “standard” database. It is presumed that having the same database interface internally and externally will simplify product development and testing. FR‐00‐0005 The system shall be developed to run on one of the following ESB and application server platforms: Oracle/BEA® WebLogic Server®, IBM® WebSphere® Application and Process Server, Tibco SOA platform, Software AG webMethods® SOA/BPM, Red Hat JBoss® Application Server J2EE, or Sobey MSB, as selected during the platform selection process. FR‐00‐0006 The system shall primarily support “web browser based” user interfaces. These user interfaces shall be compatible with and fully functional with Internet Explorer 6.x and 7.x, FireFox 3.x, and Safari x.x browsers. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 9 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 User Characteristics Role Name No. of Users Responsibility / Activity User 1000‐4000 Receives tasks, performs actions, provides input, makes decisions, completes tasks, receives notifications, modifies media content (creative operations).Estimated 200 concurrent users. Supervisor 100 Monitors specific workflows and services, makes decisions about priorities, resource allocations Manager 20‐40 Has authority over certain departments and/or workflows. Delegates authority and access for projects/productions, assigns task responsibility. Production 20 Has admin permission for a given production. Can assign user Administrators permissions for access and reports Super User (Admin) 2‐3 Resolve operating system, file system issues, including mounting of devices, permissions, etc DB Administrator 1‐2 Manages internal database, optimize performance Business Analyst or 3‐10 Test, modify, and deploy workflows. Define KPIs, reports, Media Engineer dashboard layouts Operations staff 5‐10 Monitors system health, disk space, queues, tracks critical i/o and file transfer workflows. IT Analyst or Software 1‐2 Create, test, modify and deploy workflows. Integrate new web Engineer services. Resolve interface mapping issues. Design business rules. Table 1 — User Roles 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 10 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 3 FUNCTIONAL REQUIREMENTS The overall functional requirement of the Sony Digital Media Workflow System code named “Constellation” is to provide a comprehensive software infrastructure and management toolset that incorporates business goals, business rules, operational requirements, schedules, conditional access, and security to orchestrate existing and new components of the “content factory” to achieve maximum efficiency, predictability, and speed while minimizing operational costs. This solution must remain agile, flexible and adaptable, and provide up‐to‐the‐minute visibility and insight into the operation of the facility. Although most of the elements of the SOA infrastructure are already well established in the IT industry, it is the special provisions made to handle large media files (the Media Bus) and the media-specific “Media Workflow Engine” and associated middleware that orchestrates and optimizes all the processes of the factory that enable Constellation to meet the unique needs of the media enterprise. The Sony Digital Media Workflow System is a flexible system based on programmable workflows, and as such must meet Functional Business Requirements of the media enterprise – that is, enable the automation and orchestration of existing and future media based business processes. There are three main phases of media production: Production, Post Production, and Distribution. “Constellation” Phase One will support cinema and television post production operations only. Post production includes all media operations from the time source media is received and processing begins until the finished program is released to distribution and the elements used to make the program are archived. This functional requirements document for Phase One of the Sony Digital Media Workflow System is the release version that will be updated based on comments from stakeholders including Sony Electronics B2BoA and Sony Pictures Entertainment and the results of the Business Process Analysis investigation at SPE. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 11 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 3.1 Functional Requirements - Platform Requirement ID Requirement FR‐01‐0001 The platform shall accept workflows and process orchestrations described in a digital graphical notation (like Visio) FR‐01‐0002 The platform shall accept and execute workflow or process orchestrations FR‐01‐0003 The platform shall include a Business Rules Engine (BRE) that provides a framework for non‐technical logic maintenance and deployment within server and web‐based applications, primarily the orchestration engine and the media bus framework. This BRE will externalize logic components for business decisions to insure that changes in business logic rules do not require changes in software code. Business rules are expressed in database tables, text files or XML documents as logical expressions. Rules may be deployed on the fly. FR‐01‐0004 The platform shall provide a Complex Event Processing (CEP) Engine. This feature can provide business agility through continuous correlation and visualization of multiple event‐streams. CEP employs techniques such as detection of complex patterns of many events, event correlation and abstraction, event hierarchies, and relationships between events such as causality, membership, and timing, and event‐driven processes. For example, the efficient management of job queues may require the analysis of current jobs in multiple service providers, and the estimation of time to completion. FR‐01‐0005 The platform shall operate in a J2EE Application Server or a container environment to provide infrastructure for executing applications and services in the system. FR‐01‐0006 The platform shall support an Enterprise Service Bus to provide message transport, routing, and translation. FR‐01‐0007 The platform shall support Web Services described by WSDL 1.1, using SOAP 1.1 interfaces and UDDI or other equal service registry, XML Schema 1.0 FR‐01‐0008 The platform should provide a Human Task interface subsystem supporting BPEL4People 1.0 and WS‐HumanTask 1.0 or equivalent, task mailboxes, and notifications by email or other method like SMS messaging or pager FR‐01‐0009 The platform should support non‐Web services through wrapping various types of APIs, creating a SOA environment with services that do not necessarily expose a Web Services Definition Language (WSDL) interface FR‐01‐0010 The platform shall support active deployment of new workflows while other processes and workflows are in flight FR‐01‐0011 The platform shall support process simulation and debugging operations during workflow development, and allow debugging or tracing and restart of failed processes in production environment. FR‐01‐0012 The platform should support open standards including BPMN 1.0, WS‐BPEL 2.0, UDDI, WSDL 1.1, XML Schema 1.0, SOAP 1.1, HTTP, HTML, XHTML, CSS, XML, SSL, WS‐I Basic Security Profile 1.1, WS‐HumanTask 1.0, BPEL4People 1.0. FR‐01‐0013 The platform should support import of BPMN 1.0 or other notation from graphical design products like Visio by direct import of .vsd file or by import of Visio converted to XML 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 12 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐01‐0014 The platform should support Business Analysts or Media Engineers updating workflows after they have been linked to Services (round robin development). FR‐01‐0015 Business Analysts or Media Engineers should be able to create or modify workflows using existing services or sub‐workflows (orchestrated processes) without requiring a Developer to complete and deploy the workflow, unless additional error handling or interface translation or mapping is required. FR‐01‐0016 The platform shall support event, time, and manual triggers to drive the workflow and process orchestration engine. For example: Workflows triggered by the start or completion of other workflows (events) Workflows triggered by the expiration of a timer Workflows triggered by a user action FR‐01‐0017 The platform shall support long running workflows and processes (hours, days, weeks, etc.) FR‐01‐0018 The platform shall support process suspend and resume. FR‐01‐0019 The platform shall provide persistence of the state of workflows, to support long running processes, and the ability to restart the server infrastructure without losing process/workflow state. FR‐01‐0020 The platform shall include an internal SQL relational database for storing asset management information, metadata, tasks, workflows, rules, process information, configuration information, message translation information. FR‐01‐0021 N/A FR‐01‐0022 The orchestration platform shall support debugging, single step and tracing of high level workflows, nested workflows, and process orchestration. FR‐01‐0023 The orchestration platform shall support KPIs and addition of metrics at any point in the workflow. FR‐01‐0024 The rules engine (BRE) platform shall provide a user interface for adding, modifying and deleting business rules. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 13 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 3.2 Functional Requirements - System Requirement ID Requirement FR‐02‐0001 The system shall support multiple top level workflows (connecting workflows between functions or departments). For example: FR‐02‐0001.1 Film Camera Digital Theatrical Workflows (See Section 5, sample use cases). These workflows will be developed by the SPE business analysis project. FR‐02‐0001.2 Digital Camera Digital Theatrical Workflows (See Section 5, sample use cases) These workflows will be developed by the SPE business analysis project. FR‐02‐0001.3 Film Camera Digital Television Workflows (See Section 5, sample use cases) These workflows will be developed by the SPE business analysis project. FR‐02‐0001.4 Digital Camera Digital Television Workflows (See Section 5, sample use cases) These workflows will be developed by the SPE business analysis project. FR‐02‐0002 The system shall support functional level workflows. A functional workflow is a complete task, and may include a number of other workflows or process orchestrations. FR‐02‐0003 The system shall support process level workflows, also called process orchestrations which represent a unit of work. For example the steps needed to copy and verify a file. FR‐02‐0004 The system shall support nested workflows or process orchestrations. FR‐02‐0005 The system shall support Identity Authentication (internal or external database, Kerberos, LDAP, or Active Directory based). FR‐02‐0006 The system shall support User Roles (internal database) FR‐02‐0007 The system shall support Hierarchical Security Model (internal database of roles and authorities) linked to the identity management service (user authentication). FR‐02‐0008 The system shall support an object based security model FR‐02‐0009 The system shall support delegation or assignment of authority by Manager Roles. This means that a manager with “ownership” of a project can assign or delegate selected authorities or permissions for that project or parts of that project to other users. FR‐02‐0010 All project and file permissions and authorizations shall have begin/expire times. FR‐02‐0010 Visibility and access to act on objects in a project shall be inherited with project authority FR‐02‐0011 The system shall support a media project or production database (internal or external) with mapping of fields between internal requirements and external definitions when an external customer database is used. FR‐02‐0012 The system shall provide an internal basic media asset management database for tracking the status, version, and location of Work In Process (WIP) files like DPX, proxies, EDL, LUT, ALE, BWF, etc. FR‐02‐0013 The system shall provide logging of all file transfers, accesses, operations or related activities. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 14 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐02‐0014 The system shall provide logging of all security related activities, including login/logout, addition/deletion of users, assignment of permissions, change of passwords. FR‐02‐0015 The system shall not allow content files to be accessed, transferred, deleted or modified directly by users. All content file access shall be through system interfaces using system security and authentication and logging, and shall conform to business rules. FR‐02‐0016 The system shall provide logging and notification of all errors and exceptions encountered. Notification shall be by email or SMS message. Error logs shall be displayed in a dashboard, sortable by priority, time, type, and class. FR‐02‐0017 The system shall provide configurable error and exception handling: log, stop, notify, retry FR‐02‐0018 The system shall provide multiple levels of exceptions and configurable actions for each type of exception like log, stop, notify, retry FR‐02‐0019 The system shall support “jobs” or tasks, which are logical units of work assigned to a generic service, like a transcoder or a file transfer service. Jobs are identified by a unique ID and are queued for processing by the system. Jobs may be assigned a priority which is used to determine their queue order. By definition, jobs require some finite processing time, are asynchronous, and are not transactional in nature. They may have an estimated execution time based on work needed and size of payload. Jobs may be cancelled, re‐prioritized, restarted, paused, etc. FR‐02‐0020 The system shall support Dynamic Service Dispatch of jobs (automatically selecting a particular service implementation) or “job routing” FR‐02‐0021 The system shall support Dynamic Resource Allocation for jobs (allocating resources to jobs based on priority and job size) FR‐02‐0022 The system shall support project, user, production, and service based job profiles or “recipes” with named commonly used settings or configurations for services like transcoding or file transfer FR‐02‐0023 The system shall support Dynamic Priority Management of jobs (based on priority, project or user) FR‐02‐0024 The system shall support Dynamic Queuing of jobs (based on priority or project or user) FR‐02‐0025 The system shall support changing job queue order, priority, or resources while the job is active and pending execution manually, through a UI. FR‐02‐0026 The system shall support user resource selection for execution of jobs to chose a particular service implementation type (override of Dynamic Resource Selection) FR‐02‐0027 The system shall support MAM Integration with customer and third party MAM products as external web services with wrappers or adapters as required. The system shall be capable of searching, check in, and check out of MAM assets. Specific interfaces supported will be based on each customer’s requirements. FR‐02‐0028 The system shall support online graphical dashboards (web applications) giving statuses of each step in the production process, as well as current and historical metrics and system status and load. Dashboards shall show both business process and system status data. See examples in Section 4. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 15 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐02‐0029 The system should support best efforts for integration with Sony “Ellcami” transcoder and image processing platform if possible within the development schedule for the system. FR‐02‐0030 The system shall enforce business rules for processing files, such as including visible and invisible watermarking on transcoded files, what files can be transferred externally to whom, etc. based on per‐production parameters and requesting user roles and authority FR‐02‐0031 The system shall support version management of content and metadata files using internal or external MAM system. Selected version can be manually selected, latest, or last approved version. An internal MAM system will be provided, possibly based on a third party OEM product. FR‐02‐0032 The system shall “store” and read/interpret metadata and/or essence for media file sequences (clips) of Cineon, DPX, TIFF, OpenEXR, or other “file per frame” formats. The types of supported files should be extensible, and defined outside of code, perhaps using plug‐ins. FR‐02‐0033 The system shall support various industry standard color spaces (Rec 709, XYZ, Cineon Log, PanaLog, S‐Log, Hyper‐gamma, Linear RGB, etc.). The system shall maintain metadata for color spaces for all content and for job profiles for color translations. The types of supported color spaces should be extensible, and defined outside of code, perhaps using plug‐ins. FR‐02‐0034 The system shall support media file packages using QuickTime, MXF, and AVI. These package formats are required for ingest, proxy, and transcoding. FR‐02‐0035 The system shall support input and output of media stream files in various industry standard formats like MPEG2, MPEG4, AVC, DNx, DNxHD, Apple ProRes, BWF, etc. The types of supported files should be extensible, and defined outside of code, perhaps using plug‐ins. Note that each format may have a number of parameters that define the exact encoding and data rates used. FR‐02‐0036 The system shall support all standard frame rates for media, including 23.976, 24, 25, 29.97, 30, 50, 59.98, 60 fps in interlaced and progressive formats. These formats are required for ingest, proxy, and transcoding. FR‐02‐0037 The system shall support mixed audio and picture frame rates – i.e. 23.976 picture and 29.97 audio. These formats are required for ingest, proxy, and transcoding. These formats are required for ingest, proxy, and transcoding. FR‐02‐0038 The system shall support Standard definition (NTSC and PAL), High Definition (720 and 1080), 2K, and 4K image files and file sequences. FR‐02‐0039 The system shall support various standard aspect ratios used in television, home video and cinema, including 4:3, 16:9, 1.85:1, 1.78:1, 2:1, etc. The list of aspect ratios shall be extensible without code changes. FR‐02‐0040 The system shall support time code and film Keycode metadata for ingest, proxy generation, and transcoding. FR‐02‐0041 The system shall support various industry standard LUT metadata in standard formats (1D, 3D, etc.) These LUT formats are required for ingest, proxy generation, and transcoding. FR‐02‐0042 The system shall support storing, processing, and interpreting basic metadata on a per frame, per sequence or clip basis. The system shall support the following metadata fields at a minimum: 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 16 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR-02-0042.0 Production ID FR-02-0042.1 Scene Numbers FR-02-0042.2 Take Numbers FR-02-0042.3 Circled Takes FR-02-0042.4 Camera ID (letter code, like A, B, C, etc.) FR-02-0042.5 Picture Roll Number (or "Tape Name") FR-02-0042.6 Picture Frame Timecode (start, end) FR-02-0042.7 Picture Frame Keycode (Film) (start, end) FR-02-0042.8 LUT (color look) ID FR-02-0042.9 Camera Frame Rate FR-02-0042.10 Sound Roll number FR-02-0042.11 Sound Frame Rate FR-02-0042.12 Sound Timecode FR-02-0042.12.1 Sound Sample Rate FR-02-0042.12.2 Sound bit‐rate FR-02-0042.12.3 Lab Roll FR-02-0042.12.4 Aux TC FR-02-0042.13 Stereoscopic metadata FR-02-0042.14 Camera settings metadata FR-02-0042.15 Lens metadata (i.e. Panahub) FR-02-0042.16 Camera/dolly Positioning metadata FR‐02‐0042.17 Date & Time (Shoot Date & Time) FR‐02‐0042.17.1 Shoot Day FR‐02‐0042.18 Production name FR‐02‐0042.19 GPS camera location data FR‐02‐0043 The system shall support additional user defined metadata fields FR‐02‐0044 The system shall support the use of any metadata field as an input parameter for business rules evaluations, particularly in the Media Bus layer FR‐02‐0045 The system shall support AVID ALE files for ingest of content, for export of clips and proxies, and as metadata associated with ingested material. FR‐02‐0046 The system shall support industry standard EDL files, including Avid XML EDL and CMX3600 format for specifying a sequence or a cut for preview or export to conform. EDL files may be stored and versioned in the project MAM or database. FR‐02‐0046.1 The system shall support conform change lists in XML or other standard fomats. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 17 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐02‐0047 The system shall support importing metadata from SPE CineSlate & Camera Logger and associate that metadata with the appropriate camera reel when ingested. FR‐02‐0048 The system shall support manual inputting and editing of metadata from camera logs, sound logs, script supervisor logs and storing in the internal database upon ingest of the associated camera roll or audio roll. FR‐02‐0049 The system shall support inputting production metadata from the shooting script (Scene name, description, day/night, interior, exterior, location, VFX, sub scene, shot, shot description and storing in the internal production database FR‐02‐0050 The system shall support managing the dailies process using external Digital Dailies system as a supported service, with features based on the external published APIs for that product. FR‐02‐0051 The system shall provide configurable report generation for business process information, user actions, security and system information. It should allow new types of reports to be generated (within the constraints of the existing data model). FR‐02‐0052 The system shall support WS‐I Basic Security Profile 1.1 standards and X.509 v3 security tokens and digital certificates for public keys and message encryption and signing. Support level will depend on features of third party systems used and configuration desired by customer, FR‐02‐0053 The system shall support light weight user interfaces based on web technology standards. FR‐02‐0054 All user interface and web services communications shall be transported via HTTP or HTTPS protocol to insure they will operate through firewalls. FR‐02‐0055 All user interface communications shall support SSL and other security and encryption standards as required. FR‐02‐0056 Security shall be implemented on all database tables and database access calls. FR‐02‐0057 The system shall support accessing arbitrarily defined sequences of highest quality content as logical production reels, and allow the frames included to be renamed to temporary sequential file names for external processing. A mapping or link shall be maintained between the Production Reel Id and frame file name, and the original name of that source file. Similar operations are needed for tracking the various clip in and out point changes and arbitrary clip names assigned during picture editorial. FR‐02‐0058 The system shall support interfacing with an Enterprise work order system (to originate tasks or workflows) FR‐02‐0059 The system shall support interfacing with an Enterprise billing or resource tracking system to report resources used on a task or project basis FR‐02‐0060 The system shall support interfacing with customer Distribution backbone for delivering finished projects. FR‐02‐0061 The system shall support SPE Super ALE files for ingest and dailies processes. FR‐02‐0062 The system shall support interfacing with a customer ingest/metadata database. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 18 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 3.3 Functional Requirements – Workflow Requirement ID Requirement FR‐03‐0000 The system shall provide a library of sample working workflows (templates) and task interfaces for various post production tasks that can be used as a starting point for developing customer specific workflows. Requirement ID Requirement FR‐03‐0001 The system shall provide a Create/Modify Project/Production Interface FR‐03‐0002 The system shall support and provide a Physical Asset Task Interface and workflow. This will allow checking in new camera reels and sound reels or disk media (tapes, <a href="/tags/DVD/" rel="tag">DVDs</a> or other media) and printing labels prior to ingest of content. FR‐03‐0003 The system shall support and provide an Ingest from Tape Task Interface and workflow. Tapes may include HDCAM SR, HDCAM, DVCAM, DVC‐PRO, DV, etc. FR‐03‐0004 The system shall support and provide an Ingest from File Task Interface and workflow. Files may include XDCAM, XDCAM‐HD, Panasonic P2, Sony SxS card, Redcode, or other formats on external disk or memory media. FR‐03‐0005 The system shall support and provide an Ingest from Film Scan Task Interface and workflow. This may include DPX, OpenEXR or Cineon file sequence ingest. FR‐03‐0006 The system shall support and provide an Ingest Sound from BWF File Task Interface and workflow. This may include ingest from DVD, DVD‐ROM, DAT tape, or other storage media. FR‐03‐0007 The system shall support and provide an Ingest Metadata Task Interface and workflow. This may include from email file, or file stored on disk or or memory media. FR‐03‐0008 The system shall support and provide an Ingest LUT Task Interface and workflow. This may include from email file, or file stored on disk or memory media. FR‐03‐0009 The system shall support and provide a Create Dailies Task Interface and workflow. FR‐03‐0010 The system shall support and provide a Sound Sync Task Interface and workflow FR‐03‐0010 The system shall support and provide a Dailies QC Task Interface and workflow FR‐03‐0011 The system shall support and provide a Picture Editorial Task Interface and workflow (receive task/files, publish cut proxy & EDL) FR‐03‐0012 The system shall support and provide a Sound Editorial Task Interface and workflow (receive task/files, publish edit sound proxy) FR‐03‐0013 The system shall support and provide a VFX Task Interface and workflow (send or receive task/files, publish cut proxy) FR‐03‐0014 The system shall support and provide a Conform/Assemble Files Task Interface and workflow FR‐03‐0015 The system shall support and provide a Digital Intermediate Task Interface and workflow 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 19 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐03‐0016 The system shall support and provide a Output for Distribution Task Interface and workflow FR‐03‐0017 The system shall support and provide an Archive Production Task Interface and workflow FR‐03‐0018 The system shall support and provide a Request/Send Files Task Interface and workflow FR‐03‐0019 The system shall support and provide a Receive/Check In Files Task Interface and workflow FR‐03‐0020 The system shall support and provide a sequence or clip approval Task Interface and workflow FR‐03‐0021 The system shall support and provide a cut approval Task Interface and workflow FR‐03‐0022 The system shall support and provide a sound approval Task Interface and workflow FR‐03‐0023 The system shall provide a Create/Modify User/Role/Authority Interface 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 20 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 3.4 Functional Requirements – Third Party Products/Services Requirement ID Requirement FR‐04‐0000 The system shall provide a library of individual web service wrappers or adapters to connect between the generic web services interfaces in Constellation and product specific APIs (typically also web services interfaces) provided by the third party product vendors.* Note: * The actual level of support provided in Constellation services for specific third party products will be dependent upon several conditions: 1. A published third party product API available to Sony Solutions Engineering that exposes useful functionality of the third party product. 2. An API that is Web Services or REST based. Other types of APIs will be considered individually based on value to Constellation and value to customers. 3. It is understood that some functions in the post production process are primarily creative tasks performed by people, such as sound and picture editorial, ADR, sound effects and music creation and recording, Digital Intermediate and Color Correction. These third party product functions and/or systems may not have an API available. In these cases, the support by Constellation may be limited to delivery of assets and metadata to a folder, receipt of work product from the third party product, and monitoring the human task status through a user task interface. Requirement ID Function Support Product Requirement FR‐04‐0001 Transcoding must1 Sony Ellcami FR‐04‐0002 Transcoding must Rhozet Carbon Coder/Carbon Server FR‐04‐0003 Transcoding must Digital Rapids, StreamZHD FR‐04‐0004 Transcoding may Telestream Flip Factory FR‐04‐0005 Transcoding must Anystream Agility FR‐04‐0006 Transcoding must Amberfin FR‐04‐0007 Ingest must1 Sony Ellcami FR‐04‐0008 Ingest may Autodesk Backdraft FR‐04‐0009 Ingest must DVS Pronto, Clipster FR‐04‐0010 Ingest must DVS Centaurus II 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 21 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐04‐0010 Ingest may Max-T Sledgehammer FR‐04‐0011 Ingest must AJA Xena 2K FR‐04‐0012 Ingest must Blackmagic Decklink HD FR‐04‐0013 Ingest may Codex FR‐04‐0014 Overlay must1 Sony Ellcami FR‐04‐0015 LUT Color Boxes/Systems must Thomson LUTher/Technicolor DP Lights FR‐04‐0016 LUT Color Boxes/Systems must Panavision Genesis Display Processor FR‐04‐0017 LUT Color Boxes/Systems may Gamma and Density FR‐04‐0018 LUT Color Boxes/Systems may Rising Sun Cinespace/Cinetal FR‐04‐0019 LUT Color Boxes/Systems must FilmLight Colorlight FR‐04‐0020 File Transfer must Aspera FR‐04‐0021 File Transfer may Sohonet FR‐04‐0022 File Transfer must SFTP FR‐04‐0023 Sound Editing/Sound must Digidesign ProTools (AVID) Mixing FR‐04‐0024 Sound Editing/Sound may Apple ProLogic Mixing Avid Media Composer, DS, Unity & FR‐04‐0025 must Picture Edit (offline editing) Interplay FR‐04‐0026 Picture Edit (offline editing) may Apple FCP 6/Apple FC Studio 3 & Final Cut Server FR‐04‐0027 Picture Edit (offline editing) may Scratch FR‐04‐0028 Conform must Autodesk Smoke / Wiretap FR‐04‐0029 Conform may Scratch FR‐04‐0030 Conform may Digital Vision Data Conform FR‐04‐0031 Conform must Avid DS/Symphony/Media Composer FR‐04‐0032 Dirt and Scratch Removal must Digital Film Technology (GVG) Bones FR‐04‐0033 Dirt and Scratch Removal may Digital Vision ASC3 ME FR‐04‐0034 Color Grading/Digital may Autodesk Lustre / Wiretap Intermediate FR‐04‐0035 Color Grading/Digital must DaVinci Resolve Intermediate FR‐04‐0036 Color Grading/Digital must FilmLight Baselight 8/4 Intermediate FR‐04‐0037 Color Grading/Digital may Quantel iQ Intermediate DVD, Blu-ray Encode and FR‐04‐0038 must Sony BluCode Author 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 22 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐04‐0039 DVD, Blu-ray Encode and must Sony Vegas 9 Author FR‐04‐0040 DVD, Blu-ray Encode and must Digital Rapids StreamZHD Author FR‐04‐0041 File based Ingest/Record must Sony XDCAM/XDCAM EX Sony HDCAM SR/HDCAM, Sony FR‐04‐0042 VTR Ingest/Record must DVCAM FR‐04‐0043 Sony Telefile Import must Sony HDCAM SR FR‐04‐0044 Watermarking, Encryption, must Civolution (Philips) CineFence Digital Rights Management /CompoTrack FR‐04‐0045 Watermarking, Encryption, must Thomson NexGuard Digital Rights Management FR‐04‐0046 Watermarking, Encryption, may Verance Cinavia Digital Rights Management FR‐04‐0047 Watermarking, Encryption, may USVO MediaSentinel Digital Rights Management FR‐04‐0048 Film Scan must DFT Bones FR‐04‐0049 Media Asset Management must Blue Order FR‐04‐0050 File Compression must1 Sony Ellcami FR‐04‐0051 DCP Creation must1 Sony Ellcami FR‐04‐0052 File Transfer Undecided2 DVS Spycer FR‐04‐0053 DCP creation must3 Doremi FR‐04‐0054 Conform must3 Baselight 1 FR‐04‐0055 File Transfer must3 Smart Jog FR‐04‐0056 File Transfer must3 River Bed FR‐04‐0057 Dallies must3 MTI Convey FR‐04‐0058 Dallies must3 DFT Bones Dallies FR‐04‐0059 Restoration must3 MTI Correct DRS V-8 FR‐04‐0060 Restoration must3 Pixel Farm PF Clean FR‐04‐0061 QC must Tektronix Cerify FR‐04‐0062 Dallies must3 SPE Dailies System FR‐04‐0063 File Management must3 Imageworks 2012 system FR‐04‐0064 Metadata must3 SPE Digital Slate 1. Use best efforts to support if product features and API are available 2. DVS Spycer file transfer protocol may be used internally for file transfers 3. SPE / Colorworks Requirement, subject to availability of APIs for 3rd party products 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 23 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 3.5 Functional Requirements – Web Services The system shall include a number of web services tailored to support the Ingestion, Storage, Content Processing and Movement of media assets during the production lifecycle. These services shall include generic or abstract services providing standardized interfaces to the workflow orchestration system, and specific services, adapters of wrappers to support third party products used as service providers in the system. 3.5.1 Generic or abstract services Requirement ID Requirement FR‐05‐0000 The system shall support a number of standardized, abstract, and/or generic web services interfaces (WSDL) for various services used in post production (like ingest, transcoding, watermarking, file transfer, proxy generation, etc.). FR‐05‐0000.01 All long running services (non‐transactional) shall be asynchronous FR‐05‐0000.02 All asynchronous services shall return a job ID to support status query, and pause, resume and cancel operations FR‐05‐0000.03 All asynchronous services shall support a status request FR‐05‐0000.04 All asynchronous services shall support a callback notification upon error or completion. FR‐05‐0000.05 All asynchronous services shall support pause, resume and cancel operations FR‐05‐0000.06 All asynchronous services shall support a timeout callback in case of non‐completion within a predetermined time period Requirement ID Function Description perform conversion of one media format to another, or FR‐05‐0001 Transcode Services one resolution to another FR‐05‐0002 Watermark Services embed a unique visible watermark in a digital media file perform data movement of large media file from one FR‐05‐0003 Transport Services server to another FR‐05‐0004 Repository (MAM) add new asset, search, retrieve or manage existing Services digital asset of a catalog or repository perform analysis or validate specific characteristics of FR‐05‐0005 Media Verification the digital media file, normally as part of the quality Services (QC) assurance process perform forensic fingerprinting analysis of a digital media FR‐05‐0006 Fingerprint Services file FR‐05‐0007 Physical Asset add new asset or manage existing physical asset Management Services (e.g., video or audio tapes) in the catalog or repository Resource Scheduler FR‐05‐0008 schedule new or manage current available resources Services FR‐05‐0009 Rename/renumber perform renaming of files in image sequences for Services specific operations like DI 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 24 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Digital Rights FR‐05‐0010 manage media asset intellectual rights to help Management (DRM) prevent illegal copying or conversation to other format Services support editorial process, like auto ingest, ALE file FR‐05‐0011 Editorial Services generation, etc. FR‐05‐0012 Hot Folder Services Monitor folders for new files and create event Retrieve files and sequences based on EDL or conform FR‐05‐0013 Conform Services list FR‐05‐0014 HSM Migration Manage hierarchal storage migration based on media Services aware rules FR‐05‐0015 Encryption Services Provide encryption or decryption of files Provide version control of files and sequences, and FR‐05‐0016 Versioning Services track approved versions FR‐05‐0017 Metadata Services Manages metadata for files and sequences 3.5.2 Derived services The derived services may be required to perform tasks identified by various functional workflows and process orchestrations used in the post production process. They may be implemented within the generic service classes above, or as individual services or system services of the media bus. For example, FR-06-0011 through FR-06-0014, FR-06-0016, and FR-06-0017 may all be implemented within the FR-05-0003 Transport Services identified above. Requirement ID Function Purpose Description A service that Synchronizes Video FR‐06‐0001 Synchronize Video Sync Service and Audio files within the and Audio backbone. Pull files and handles A service that conforms files FR‐06‐0002 Conform Service based on EDL within the backbone. A service that extracts the file FR‐06‐0003 Retrieve Service Retrieve Files from the repository. FR‐06‐0004 This program looks for files in Monitoring Service Monitor Directories source directories and calls the ingest service. FR‐06‐0005 The Ingestion Service is used to Ingestion Service Ingestion Process facilitate adding content into the system. FR‐06‐0006 A service that extracts, translates, Metadata Service Processes Metadata and processes source metadata and stores it in the database. A Service that sends out a FR‐06‐0007 Notification Service Email Notifications notification message. FR‐06‐0008 The Proxy Service manages the Manage Proxy relationship of files to proxies Proxy Service Relations (create relationship and retrieve relationship between files) Find assets in the A service that submits a search FR‐06‐0009 Search Service Backbone query and retrieves results 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 25 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 FR‐06‐0010 The Security Service verifies / Security Service Authorize Users enforces user roles / privileges / access within the Backbone. FR‐06‐0010 The Transaction Logging Service creates a record in the database Transaction Logging Logs Transactions for every transaction. This record Service shall be used for reporting and tracking purposes. FR‐06‐0011 Modify Asset A service that converts assets into Resolutions to higher/lower resolutions or other Transcode Service Optimize file formats depending on Performance specifications. HTTP or Aspera Client Transfers FR‐06‐0012 Transfer Service (Client File Transfers from local computers to Backbone to Server) (uploads). HTTP or Aspera Client Transfers FR‐06‐0013 Transfer Service File Transfers from Backbone to local computers (Server to Client) (downloads). Backbone Transfers to or from FR‐06‐0014 Transfer Service File Transfers FTP servers, Aspera Console (Server to Server) servers, network directories. FR‐06‐0015 Modify Asset A service that converts assets into Resolutions to higher/lower resolutions or other Transcode Service Optimize file formats depending on Performance specifications. FR‐06‐0016 SFTP, HTTP or Aspera Client Deliver Service (Ext Transfers from external File Transfers Client to Server) computers to Backbone (uploads). SFTP, HTTP or Aspera Client FR‐06‐0017 Deliver Service (Server File Transfers Transfers from Backbone to to Ext Client) external computers (downloads). Watermark Burn In Add visible watermark or burn ins FR‐06‐0018 File Transfers Service (copyright, time code, frames) Resource Utilization FR‐06‐0019 resource monitoring track resources used in processes Service Authenticate and create digital FR‐06‐0020 Message Message signatures and encryption (CA Authentication Service Authentication based) Automated movement of data FR‐06‐0021 Automated file from higher performance storage Data Migration Service transfer between to lower performance storage and storage tiers vice versa Automated backup Automated backup and restore FR‐06‐0022 Backup Service and restore system for disaster recovery. FR‐06‐0023 Takes request for existing asset in format it does not presently exist Create illusion of File Spoof Service in, locate asset and transcoder assets available in all (Virtual File System) and initiate transcoding, advise supported formats requestor it shall be available in x timeframe FR‐06‐0024 Encryption Service Encrypt content Encrypts content as directed. Prepare and store Directs transcode engine, FR‐06‐0025 Deep Archive Service deep archive format manages database, and 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 26 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 supervises placement in deep archive FR‐06‐0026 Render color grading, effects, etc Render Service Render content from existing content or render frames from 3D modeling Packaging & FR‐06‐0027 Packages or wraps Containerization Packages or wraps content content Service FR‐06‐0028 Applies 1D &3D LUTs plus gamma, logarithmic, and LUT Service Applies LUTs exponential curves for direct viewing or to bake in proper corrections in dubs Automatic QC of Automatically QC ingests, FR‐06‐0029 Auto QC Service operations transfers, etc. Retrieve from physical media FR‐06‐0030 Read from Physical Read Physical Media including videotape, audiotape, Media Service optical media. Record on physical media FR‐06‐0031 Write to Physical Media Write Physical Media including videotape, audiotape, Service optical media. Determine which provider of a FR‐06‐0032 Dynamic Service Dynamic resource service should be utilized per Provider Selection allocation request, and forward request to Service that provider. Remove dirt and FR‐06‐0033 Dirt & Scratch Removal scratches from Provide cleanup of ingested film. Service pictures. Gateway to connect with and FR‐06‐0034 Provide access to provide programmatic interface to Service Gateway other departments or other departments or external external vendors. vendors. Picture editing Service that abstracts picture FR‐06‐0035 Picture Editing Service functions. editing process. Color grading Service that abstracts color FR‐06‐0036 Color Grading Service functions. grading process. Visual effects Service that abstracts VFX FR‐06‐0037 Visual Effects Service functions. process. Sound editing Service that abstracts sound FR‐06‐0038 Sound Editing Service functions. editing process. Sound mixing Service that abstracts sound FR‐06‐0039 Sound Mixing Service functions. mixing process. FR‐06‐0040 Ensures that metadata versions Metadata Version Maintain metadata are retained and naming Control Service version control. conventions automatically supported. FR‐06‐0041 Compares local version to latest Ensure operator has network version and provides Metadata Latest latest version of automatic or semi-automatic Version Service metadata. transfer and replacement of any outdated metadata. Ensures that essence versions FR‐06‐0042 Essence Version Maintain essence are retained and naming Control Service version control. conventions automatically 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 27 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 supported. FR‐06‐0043 Compares local version to latest Ensure operator has network version and provides Essence Latest Version latest version of automatic or semi-automatic Service essence. transfer and replacement of any outdated essence. FR‐06‐0044 Automatic (or semi-automatic) Maintain naming and renaming or renumbering of Rename & Renumber numbering filenames to adhere to Filename Service conventions. predetermined naming conventions. FR‐06‐0045 Compares local version to latest Ensure operator has network version and provides Essence Latest Version latest version of automatic or semi-automatic Service essence. transfer and replacement of any outdated essence. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 28 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 4 DASHBOARDS A useful SOA management and monitoring dashboard should provide users with configurable and customizable management options, offering plenty of holistic views of service performance from both business and IT points of view. Furthermore, it will be helpful to understand how a service’s performance (especially failures of the service) may impact various IT and business processes or workflows. Common functional considerations of the dashboard should include: • Web-based and user-defined (custom configurable) dashboard/operations console for real-time monitoring to ensure operational business continuity and control. Robust event monitoring should offer: 1. Insight into the cause or origin of a problem 2. Future impact analysis and assessment 3. Historical mile-stoning of all previous impacts 4. Categorization of events into various types or classes 5. Customizable escalation paths based on incident type 6. Customizable severity levels attached to incident type • Robust metadata about all services and their relationships • Glossary to support all service metadata and semantic references • Simple visualization of complex IT relationships and impact on business processes at any junction in the lifecycle of a given business process. • Service uptime, throughput, and other IT-centric performance metrics. • A common platform where real-time performance monitoring, metrics and KPI can be collected, aggregated, and presented in legible and customizable fashion. KPI’s should: 1. Give a view of how a business process is behaving and being supported by a service 2. Raise alerts based on a pre-defined threshold. • Robust, granular security, authentication and access control (supporting Kerberos and LDAP) to provide controlled access to specific data and views 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 29 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 • Figure 5 - Dashboards & Monitoring 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 30 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 31 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 32 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 33 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 34 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 5 SAMPLE USE CASES 5.1 Film Process Today, theatrical motion pictures are normally shot on Super 16mm or 35mm film or with digital cameras at either 24 fps (frames per second) for film and digital or 23.976 fps for digital. Digital camera images are recorded on video tape, or as files on disk drives, flash cards, or memory packs. These files can be transferred to RAID drives or LTO Data Tape for backup and transport. Audio is usually recorded separately from the picture on a high quality digital audio recorder, although sometimes a lower quality audio feed may be sent to the camera to aid in dailies production. Modern file based digital audio recorders can record at any standard frame rate, including 23.976 fps, 24 fps, 25 fps, 29.97 fps and 30 fps. Audio files are typically stored on DVD-RAM discs or Flash cards in Broadcast Wave format. There are several sound sample rates, like 47.952kHz, 48.000kHz, and 48.048kHz. Sound bit rate is typically 24. Production metadata includes information about each Camera Roll, Scene and Take, related to camera and audio reel and start/stop footage or time code value. Other data might include lens type and if the take was “circled” or good. Additional technical metadata includes the “look” or color LUT used for viewing the images on set. A “slate” or “clapperboard” is used to visually “mark” or record some of the Scene and Take metadata and to synchronize the audio and video start points for each take (when the clapper closes, it creates a sharp sound and can be seen closing on the image). Some electronic slates can display synced audio time code to aid in aligning the picture and sound in post production. 5.1.1 Film to Digital Motion Picture Workflow The first representative workflow is a production shot on film and processed in the digital domain, and thus the film negative moves from the film lab to telecine or Data Scan to begin the dailies process, where the film images are scanned and converted to digital video files. Using the “look” (LUT color tables) established on the set, a single color correction setting (“one light”) is applied to the review copies of the pictures. Sound is manually synced up with picture, and multiple screening versions (DVD, BuRay, XDCAM, Quicktime or Windows Media or a combination) are created manually, along with files for the proxy edit. Typically the dailies process can take four to eight times as long to create as the duration of the original footage Typically Dailies are what the production team reviews and edits. Additionally, studio executives and administration review copies of the dailies, today either on DVD, off the web-based browser like PIX System, or on XDCAM (and sometimes still film!). Since very few movies shot on film today actually cut the negative for the edit of the final print, at some point most productions shall Data Scan high‐resolution images of the needed raw camera negative footage for use for VFX and for DI conform later in the post‐production cycle. Some projects using the above workflow shall only do a data scan of the required parts of the film negative in high resolution for VFX plates and for editorial selects after the edit is completed to save time and money. Others shall do a high resolution data 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 35 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 scan of all or most of the footage and down convert it for editorial proxy, skipping the telecine process. If there are a large number of VFX shots, this approach may be less costly and more efficient than doing multiple film scans on demand as they are needed. Figure 6 - Film to Digital Motion Picture Workflow The relationships between the raw film, the original audio recordings, scanned high‐resolution image files, VFX sequences and all the proxies must be carefully noted and maintained - typically as a manual spreadsheet based process. During the Proxy Edit cycle, multiple viewing copies of work in progress copies must be generated. The Visual Effects work shall require huge sequences of high resolution DPX files to be located and moved and/or copied, as shall the Conform process and eventually the DI color grading render process. When the highest‐quality version of the finished feature is finally approved, it must be transferred back to film and/or encoded and packaged into a digital print and other media formats. And this is just the original-language theatrical version, one of many distribution versions that must be created. 5.1.2 Full Digital Motion Picture Workflow Today, between 10% to 15% of all major motion pictures are shot with most or all of the footage captured using digital cameras. This percentage is rapidly increasing due to the growing acceptance of and improvements to the technology, and the need to drive down production and post production time and costs. A representative all digital workflow is shown below, and it is obvious that it is simpler than film to digital, since expensive film processing, telecine, and most of the film scanning requirements are eliminated. Films with lots of visual effects can especially benefit from the digital workflow. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 36 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Figure 7 - Full Digital Motion Picture Workflow 5.2 Episodic Television Process The creation of episodic TV shows is similar in some ways to the basic motion picture production workflows, but simpler and compressed into much shorter timeframes. Episodic TV shows can be edited and released in 2‐4 weeks. Episodic TV shows are shot with Super 16mm, 35mm or in a few cases digital cameras today. 5.2.1 Film to Digital TV Workflow 70% of prime time episodic TV programs originate on film, in either 16mm or 35mm format. Sound is usually captured separately from picture as with movie productions. Most are shot at 23.98 or 24 fps to maintain a “movie film look” and reduce costs (less film used). Because the delivery requirements of 29.97 fps, for broadcast and the continued use of standard definition proxies for editing TV productions, most TV productions shoot at 23.98 fps to facilitate up conversion to 29.97 fps. TV productions usually do not use film data scans, and do not need to use or archive uncompressed DPX files since they are broadcast in normal HD formats. Delivery format is usually XDCAM HD, HDCAM or HDCAM SR tape. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 37 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Figure 8 - Film to Digital TV Workflow 5.2.2 Full Digital TV Workflow Although film is still predominant for episodic TV production, an all digital workflow from camera to broadcast is becoming more popular. Since it does not require film processing and scanning or telecine, it can be less expensive and can facilitate a faster turnaround in post production. Another benefit of digital production is that many dramatic television series are shot simultaneously with two to four cameras in different locations to reduce camera and lighting set‐up changes and give the editors more material from each take. Processing the increased daily footage is simpler and quicker with digital format. Figure 9 - Full Digital TV Workflow 5.2.3 Other Television Workflows 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 38 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Episodic television is not the only TV media production process that can benefit from improved production workflows. Other types of television productions include: • Game shows • Reality series • Sports shows • Documentary series • Daily soap operas • News productions 5.3 Commercial Workflows Both film and digital cameras are used on commercial (advertisement) productions, and many of the same issues discussed above apply here as well. Of course, the biggest difference in commercial production is the extremely short production and post production schedules that are often needed.11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 39 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 6 SYSTEM ARCHITECTURE The system architecture for the Sony Digital Media Workflow System is based on the Service Oriented Architecture (SOA) used in IT applications for the past 10 years. Traditional SOA systems are used for agile integration of dissimilar IT systems into a loosely coupled system capable of being managed and orchestrated by high level graphical software tools. They are usually based on Web Services components running in an Application Server environment often with an Enterprise Service Bus providing messaging services (transport, routing, translation, notification). An orchestration server providing Business Process Management (BPM) capabilities, with Business Modelling tools and a Business Rules Engine (BRE). Complex Event Processing often is used to identify and track hard to evaluate events that occur across systems or over time. 6.1 Media SOA Recognizing that Media SOA Business Process Management systems have several different requirements than traditional high transaction IT applications, the Constellation architecture includes a number of additional features to support Media SOA. First, Media SOA workflows are often long running processes, sometimes active for hours, days, or even weeks. This places specific persistence requirements of the SOA BPM platform. Servers may be stopped or restarted while processes are running, and the system needs to save state and be able to restart at the same point in the workflow and process orchestration without loss or state or data. Many Media SOA service are external hardware or software based systems that operate in a loosely coupled asynchronous environment. Therefore if servers are stopped or started these services may continue running, and job process state must be recovered after the SOA system restarts. These systems may already have existing web service APIs that do not conform to the Constellation Generic Service Descriptions (WSDL) and wrappers or adapters must be provided. 6.2 Media Bus Additional extensions to SOA called the Media Bus will facilitate storage and file centric operations. Since the system manages the storage and movement of a very large number of large files (millions per project) it is critical that a Media Asset Management system be incorporated into the system core functionality. There will be many copies of file instances and also many versions located in multiple island data storage areas in the system. There will also be many lower resolution video proxy files in the system representing the original high resolution “camera negative” files or file sequences. These proxy files must be tracked and versioned as well. Reliable transfers are also critical, so the capability to provide check sums or other file verification technology is also a function of the media bus. File naming and name management in Post Production workflows is a major issue. File names are often changed when new instances are created to serve the needs of a specific creative task like Picture Editorial or Digital Intermediate. So the same file or sequence may exist in various parts of the system with different file names. It is critical that all of these instances of the same essence be tracked and managed. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 40 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Maintaining the correct metadata for any given file or file sequence (clip) as it passes through the many processing staged in a media workflow is also a big problem. Many processes, both internal and outsourced (like VFX) may change or strip off metadata from the essence and even change the identity of the objects involved. Maintaining a clear relationship between a media object and its original and modified or added metadata is very important. Storage management is also critical due to the large number of large files in a 2K or 4K workflow. The system must facilitate the efficient use of the hierarchal storage system and assist is selecting files to be migrated to tape library storage. 6.3 Capacity Requirements The system is intended to be scalable from a singe user “on-set” production system with one or a few computers to an enterprise system supporting hundreds or thousands of concurrent users. There will be hundreds or thousands of web services managed by the system. Since all services and interfaces are based on web architecture they are intended to be scaled using traditional IT technology like multiple http servers and load balancing. That implies that the process architecture should be stateless and all process context should be persistent cross instances based on login identity management. Redundant servers and load balancing must be supported. Support for database redundancy is required. 6.4 User Interfaces All user interfaces should be web based if possible and should take advantage of the latest web design principles and techniques including CSS 2.0, AJAX, Web 2.0, XML, etc. These user interfaces shall be compatible with and fully functional with Internet Explorer 6.x and 7.x, FireFox 3.x, and Safari x.x browsers. 6.5 System Structure The Sony Digital Media Workflow System is a Service Oriented Architecture (SOA) based system for media workflow management for file based post production operations. This system is “Middleware” that provides workflow orchestration for media processing operations implemented primarily by a collection of third party products. In addition, some traditional applications and web services, as well as service wrappers or interface (API) adapters may be provided to support specific required functionality. The components of Sony Digital Media Workflow System to be based on 3rd party software or platform(s) include: • Application Server • Enterprise Service Bus • Workflow Orchestration Server • Business Process Management Server • Business Rules Engine • Human Task management system • System Status and Historical Dashboards • Complex Event Processing Engine 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 41 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 • Business Modeling Tools • Internal Relational Database • Database Report Generator • Media Asset Management System (may be internally developed) • 3rd Party hardware and software service providers • Hierarchical storage manager (Tivoli) • File transfer managers (Aspera) • Network file systems (GPFS, StorNext) The components of Sony Digital Media Workflow System to be developed internally include: • Workflow Template Library (top level) • Workflow Template Library (functional) • Process or task orchestration library • Web service generic interfaces (WSDL) • User interfaces for tasks (initiation and response) • 3rd party service API wrappers or adapters to generic Web service interfaces • Internal MAM (integrate 3rd party product or build) • File renaming • Production Metadata management • Identity & Authority Management (login, hierarchal project authority, delegation) • Project/production management database • Resource use tracking (for export to billing) • Logging, notification, error resolution • Business Dashboards and KPI’s • Business reporting and status notification • Job Profile or Recipe management • Job Queue Management • Job Priority Management • Business Rules for Dynamic Media service selection (Job routing) • External Interfaces, including o Enterprise MAM(s) o Enterprise Identity Authentication o Enterprise Project/production management database o Enterprise work order system (original workflows) o Enterprise billing or resource tracking The system is intended to be loosely coupled. This will necessarily reduce performance and response time to some extent. No service should be aware of or dependent on any other 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 42 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 service. The system should provide generic service interfaces (WSDL) for each class of service functionality (transcoding, watermarking, file transfer, etc.) Wrappers or adapters will be needed to interface to specific 3rd party product APIs. Callbacks and notifications should be used where possible, but polling and timed triggers must still be used to re-establish job and system status in the event of a system restart or the failure of a service. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 43 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 7 REFERENCES 7.1 General References [1] World Wide Web Consortium (W3C), http://www.w3.org [2] Organization for the Advancement of Structured Information Standards (OASIS), http://www.oasis-open.org [3] Web Services Interoperability Organisation (WS-I), http://www.ws-i.org [4] Advanced Media Workflow Association (AMWA), http://www.amwa.tv [5] Society of Motion Picture and Television Engineers (SMPTE), http://www.smpte.org [6] Open SOA Collaboration (OSOA), http://www.osoa.org [7] Internet Engineering Task Force, Public-Key Infrastructure (X.509) Working Group (PKIX), http://www.ietf.org/ [8] Object Management Group/Business Process Management Initiative, http://www.bpmn.org/ 7.2 Media Format References [9] ANSI/SMPTE 268M-2003, File Format for Digital Moving-Picture Exchange (DPX), Version 2.0 [10] ANSI/SMPTE 268M-1994, File Format for Digital Moving-Picture Exchange (DPX) [11] Kodak Cineon™ file format Version 4.5 DRAFT - Image File Format Proposal for Digital Pictures, Kodak, Nov 30, 1990 [12] Kodak Cineon™ file format (draft, unofficial) http://www.cineon.com/ff_draft.php [13] OpenEXR File Layout, ILM, http://www.openexr.com/openexrfilelayout.pdf [14] Reading and Writing OpenEXR Image Files, ILM, version 1.3 http://www.openexr.com/ReadingAndWritingImageFiles.pdf [15] SMPTE 377M: The MXF File Format Specification [16] ISO/IEC21000 - MPEG-21 Multimedia Framework [17] The MPEG-21 Book, Ian S. Burnett, et al, John Wiley, West Sussex, England, 2006 [18] EBU Tech 3285 - Specification of the Broadcast Wave Format (BWF) - Version 1 - first edition (2001) plus addendums [19] Avid Log Exchange file format, Appendix C of Avid Media Composer 3.0 manual [20] Avid Metadata Logging and Tracking white paper, Avid Corp. 2007, AMLTWP1007 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 44 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 8 ACRONYMS ALE Avid Log Exchange, CSV format text file describing clips and metadata for batch ingest, typically from tape AVI Microsoft media file wrapper for picture and sound essence files BPEL Business Process Execution Language BPM Business Process Management BPMN Business Process Modelling Notation BWF Broadcast Wave File (audio file format) CDL Color Decision List – specifies color processing or looks usually on a per scene basis CG, CGI Computer generated Graphics, 3D animation, rotoscoping, compositing, match moving, and matte painting CIN, Kodak standard uncompressed image file format containing a single frame of a motion Cineon™ picture film scan, 10 bit/channel Kodak Cineon log or linear encoding, typically 2K or 4K resolution, clips are represented as sequences of numbered CIN files in a directory CMX3600 Commonly used simple EDL text file format used for interchange of edit information between various products and systems. Originally developed 25 years ago and now supported by almost every edit and post production or DI system. Very limited format contains in and out source and master time codes, track, effect and clip info. CSV Comma Separated Variable - text file format for simple data sets using commas for variable separation and quotes for string demarcation to handle embedded commas (embedded quotes are escaped with backslashes). DI Digital Intermediate – the final step in image processing for digital motion picture and some television workflows, including color correction and final assembly/conforming DNxHD xxx Codec used by Avid Media Composer for HD file storage, various bit rates in Mb/s (36, 115, 145, etc.) DPX SMPTE standard (based on Cineon) uncompressed image file format containing a single frame of a motion picture, 8 or 10 bit/channel log or linear encoding, typically 2K or 4K resolution, clips are represented as sequences of numbered DPX files (frames) in a directory DRM Digital Rights Management – wrapping and encrypting media files to restrict their use based on rights granted to the user EDL Edit Decision List, text file describing an edited sequence of clips. Used for interchange of the “cut list” of a production between products. Several common EDL formats including CMX3600, GVG, Sony 9000, etc. are used. FPS Frames per second, 24 fps is the standard sound film speed Keycode Kodak Keycode™ is a barcode identifier pre-exposed onto raw film negative stock that, when developed with the image, provides a unique identifier for each frame of film to insure accurate identification of frames for scanning, editing and negative cutting. Film Scanners can read this identifier and insert it as metadata into the scanned image output file for each frame. LUT Look Up Table – a 1D or 3D matrix of color conversion values for color processing of a scene or clip. MAM Media Asset Management (aka Digital Asset Management) – ingesting, tracking and securing digital media assets in both physical (tapes, disks) and file based formats MOV Apple Quicktime media file wrapper for picture and sound essence files 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 45 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 MXF Media file wrapper for metadata and picture and sound essence files OpenEXR OpenEXR is a high dynamic-range (HDR) image file format developed by Industrial Light & Magic for use in computer imaging applications. It is typically used as an image file format containing a single frame of a motion picture for visual effects (a “plate”). Color values for pixels are stored in 16 or 32 floating point with millions of values as compared to DPX and Cineon which are integer formats with a range of 1024 values. Multiple types of lossless compression are supported. ProResHD Codec used by Apple HD file format, various bit rates SOA Service Oriented Architecture, based on web services SOAP Simple Object Access Protocol (w3c) TIF, TIFF Image file format that supports compressed and uncompressed images UDDI Universal Description Discovery and Integration – an XML Standard sponsored by OASIS for a service registry, a searchable directory of service interfaces and information about those services VFX Visual Effects, typically computer generated graphics (CG), 3D animation, rotoscoping, compositing, match moving, and matte painting WIP Work In Process WSDL Web Services Description Language (w3c) WS-policies Web Services standards (WS-I) XML Extensible Markup Language (w3c) 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 46 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 9 GLOSSARY Application server (app server) - the underlying platform, or foundation of the middleware layer, that provides communication and messaging, reliability, enterprise scalability, some elements of security, and unified administration. Business agility - the ability of an enterprise to quickly, easily, and effectively make changes in their operation, whether these changes are driven by equipment replacement cycles, new regulations, competitive changes, or any other internal or external factors. Business Process Management (BPM) - a field of knowledge at the intersection between management and information technology. BPM encompasses methods, techniques and tools to design, enact, control, and analyze operational business processes involving humans, organizations, applications, documents and other sources of information. BPM focuses on the needs of the organization, not the specific details of how that is accomplished. Business rules – a description of the operations, definitions and constraints that apply to an organization in achieving its goals. These rules are then used to help the organization to better achieve goals, communicate among principals and agents, communicate between the organization and interested third parties, demonstrate fulfillment of legal obligations, operate more efficiently, automate operations, perform analysis on current practices, etc. In the context of an SOA system, it is important that these rules are not spread across various code modules, but that instead they are kept in a single location (usually a rules engine) where they can be easily identified, verified and maintained. The processing of these rules can be exposed as a service to the rest of the SOA system. From a technology point of view, business rules are modeled and implemented with tools and languages that ideally can be understood both by business people and by IT people. Data Aggregation - The architectural concept of collecting all business data in an integrated system in a single place so that it can be viewed and analyzed by software or humans. Software architectures that support data aggregation are easily monitored and can provide important feedback to users about the health of the overall system. Enterprise Service Bus (ESB) - the biggest and perhaps the most important part of an SOA middleware layer. It is defined as a distributed, service-oriented messaging channel that provides business communication capabilities to the heterogeneous systems attached to it. Essence – is the digital representation of the creative content (bits) that represents the sound audio or picture image recorded on the set, as modified during the production process. Federation – is a software concept where many components interact without the direction of a central authority. These components might be individual software systems, or they might be entire facilities. Federation is most often encountered when multiple facilities or media enterprises need to collaborate in a software-assisted way. Identity Management - An important aspect of enterprise security policy that deals with the authorization, authentication, and auditing of system users. Identity management technology facilitates the provisioning and sharing of user accounts, and the management of such things as passwords and system rights. Key Performance Indicator (KPI) – A metric that measures the business performance of a system or facility. A KPI is normally constructed from business data aggregate across many systems and addresses a specific business need. KPIs determine whether or not a system or architecture is successful. Layer of Abstraction – SOA, as an enterprise architecture, introduces layers of abstraction into the infrastructure. A layer of abstraction is a level at which all infrastructure components more detailed are encapsulated and hidden from the integrator. These layers are crucial in enterprise integration, because they allow the integrator to focus on business need instead of technical detail. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 47 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Loose Coupling – An infrastructure in which components are independent from one another, and the “ripple effect” of changes to architecture is minimized. A loosely coupled system allows for easy replacement or upgrading of components, giving the implementing facility more agility. LUT - Look-up Table is a data structure, usually an array or associative array, often used to replace a runtime computation with a simpler array indexing operation. The savings in terms of processing time can be significant, since retrieving a value from memory is often faster than undergoing an 'expensive' computation. For this reason, color space mapping in YCUCV or XYZ color space often rely on LUT’s. Middleware - a collection of components that are integrated together to provide a host of services to the rest of the enterprise architecture. The middleware layer serves the role of an integration broker and message exchange medium inside a SOA. It is the fabric or “glue” that connects services, and is responsible for many aspects of the communication infrastructure including security, routing, reliability, and scalability. Portal - An enterprise component that is used to organize data from multiple sources into a single user interface. Many SOA implementations use portal technology to present dashboards, task lists, administrative interfaces, and other views to users. Post production – includes all media operations from the time source media is received and processing begins until the finished program is released to distribution and the elements used to make the program are archived. Process orchestration - a process-driven method for service collaboration which entails the development of business processes to control interaction among services. Process orchestration describes the individual steps taken by a business process in order to invoke the various services used in executing the process and to coordinate their operations. Service - a fundamental building block in an SOA. It represents a set of service operations that can be combined via orchestration to produce business processes. These operations are grouped around an area of business concern. In a Service-Oriented Architecture, the requestor is not concerned about the implementation of services, but instead to their interfaces and interaction. Example - A transcoding service communicates with an asset management system across an SOA. The transcoding service provides the following service operations: “submit new job,” “check job status,” and “cancel job.” The asset management system uses the transcoding service to automatically create a transcoded proxy when a new asset is added. Upon receipt of a new asset, the asset management system shall call the “submit new job” operation on the transcoding service, and shall periodically poll the “check job status” operation until the job is complete. Service Gateway – A component in an SOA that exposes a subset of functionality of the SOA for the benefit of other, external consumers. Gateways are important to provide interaction with outside parties. They can also be used as a protective measure if the security model changes from one domain to the next. Service-Oriented Architecture (SOA) - an architecture of independent, wrapped business services communicating via published interfaces over a common middleware layer. SOAP - Simple Object Oriented Protocol. SOAP is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It is particularly well-suited for messaging within an SOA implementation. Tight Coupling - An architecture in which components are interdependent and configured to optimize one operational workflow. Traditional broadcast and post-production systems are typically understood to be tightly coupled, in that the signal flow and processes cannot be easily reconfigured, and the performance of each process is dependant on the functions of others. Web Services - An XML-based technology for activating remote processes and receiving responses between loosely coupled systems using HTTP protocol and SOAP. It is optimized for transactional, document-style messaging and uses the WSDL standard to represent service interfaces. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 48 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. Solutions Engineering Constellation Software Requirements – Phase One B2B of America Document Control #: 951-502101 ver 1.11 Wrapped business service - a tangible service such as transcoding or asset management with a business-level abstraction layer that provides an implementation-independent interface to the middleware, effectively making the service appear as a “black box”. Wrappers - the components that sit between a service and the middleware layer and transform messages that pass through them. Wrappers provide a layer of abstraction between the service and the middleware layer, allowing a user to change either one without drastically affecting the other, providing business agility. WSDL - Web Services Description Language. An XML-based language that provides a model for describing Web services. The WSDL defines services as collections of network endpoints, or ports. For this reason, it is often selected for messaging within an SOA implementation. 11/8/2009 © 2009 Sony Electronics Inc. • Solutions Engineering Page 49 Company Confidential Information This document contains proprietary information of Sony Electronics Inc. Neither receipt nor possession hereof confers any right to reproduce, use, disclose or distribute, in whole or in part, in written or any other format, any such information without prior written authorization from Sony Electronics Inc. </div> </article> </div> </div> </div> <script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.6.1/jquery.min.js" crossorigin="anonymous" referrerpolicy="no-referrer"></script> <script> var docId = '303c73b72cbf46208c4d84f88b0fb275'; var endPage = 1; var totalPage = 55; var pfLoading = false; window.addEventListener('scroll', function () { if (pfLoading) return; var $now = $('.article-imgview .pf').eq(endPage - 1); if (document.documentElement.scrollTop + $(window).height() > $now.offset().top) { pfLoading = true; endPage++; if (endPage > totalPage) return; var imgEle = new Image(); var imgsrc = "//data.docslib.org/img/303c73b72cbf46208c4d84f88b0fb275-" + endPage + (endPage > 3 ? ".jpg" : ".webp"); imgEle.src = imgsrc; var $imgLoad = $('<div class="pf" id="pf' + endPage + '"><img src="/loading.gif"></div>'); $('.article-imgview').append($imgLoad); imgEle.addEventListener('load', function () { $imgLoad.find('img').attr('src', imgsrc); pfLoading = false }); if (endPage < 5) { adcall('pf' + endPage); } } }, { passive: true }); if (totalPage > 0) adcall('pf1'); </script> <script> var sc_project = 11552861; var sc_invisible = 1; var sc_security = "b956b151"; </script> <script src="https://www.statcounter.com/counter/counter.js" async></script> </html>