1Executive Summary 4
1.1Contact 4
1.2Document Organization 5
1.3MovieLabs as Agent 5
2Overview 6
2.1Trusted Device List (TDL) Overview 6
2.2Context 6
2.3System Architecture 6
2.4References 8
1Proposal and Bidding Process 9
1.1Proposal Format and Content 9
2.4.1Cover Letter 9
2.4.2Proposal Content 9
Additional information to be included 10
1.2Timing 10
Key Events 10
Intent to Submit a Proposal; Acceptance of RFP Terms 11
Proposal Closing Time 11
Duration of Offer 11
2.5Questions, Meetings, Down Selection 12
Pre-Proposal Questions 12
2.5.1Meetings Before Submitting Proposal 12
2.5.2Meetings After Proposals are Submitted 12
2.5.3Down Selection and Best and Final Offers 12
2.6Revisions to the RFP 12
2.7Cancellation of RFP 12
1.3RFP Proposal Evaluation Process Criteria 12
Evaluation Committee 12
Evaluation Criteria 13
1.4Confidentiality of Proposals 14
2Proposal Requirements 15
2.8Minimum Vendor Qualifications 15
2.9Vendor Teams 15
2.10Complete Versus Partial Bids 15
2.11Alternative Paths 15
2.12Contract Type 15
2.13Pricing 16
2.14Term 16
2.15Languages 16
2.16System Updates 16
2.17Ownership 16
2.17.1TDL and Ancillary Data 17
2.18System Rollout 17
2.19Oversight 17
2.20General Terms 18
Vendor Costs 18
Accuracy of Information 18
Improper Conduct 18
Responsibility for Subcontractors and Vendor Personnel 19
Severability 19
Applicable Law 19
Disclaimer of Liability 19
3Statements of Work 21
3.1Task 1: Build TDL 21
Primary Functions 21
Deliverables 22
3.2Task 2: TDL Deployment and Operations 22
Primary Functions 22
Deliverables 23
3.3Task 3: TDL Operational Support 23
Primary Functions 23
Deliverables 24
3.4Task 4 – TDL Automation Framework 24
Task 4.1 Automation Technology and Standardization 24
Task 4.2 Build Exhibitor Tool 24
Task 4.3 Build Reference Code 25
3.5Documentation 25
3.6Software Updates 26
4TDL Requirements 27
4.1Data 27
Data Sources 27
Facility Data 27
Participant Data 28
Device information 29
Access Control Data 29
TDL Historical Data 30
Log Data 30
Database Historical information and rollback 30
Data Integrity, Fraud and Malicious Behavior Detection Data 30
4.2Interfaces 30
REST Interface 31
Web Interfaces 32
Bulk Ingest Interface 33
Bulk Database Replication Interface 33
Notification Subscription Interface 34
Notification of Facility Data Integrity problems 34
Automated Interfaces Not Supported 34
4.3Data Integrity 34
Consistency Checks 34
Disallowed Devices 35
Database Inconsistency Resolution 35
4.4Data Access Controls 36
4.5Reporting and Dashboards 36
4.6 Authentication and Data Protection 36
4.7Other requirements 36
Conventions 36
Threats 37
Compatibility with other features 37
4.8Regulatory Requirements 38
5TDL Operations Support 39
5.1System Operations 39
Account Administration 39
System Administration 40
User Training and Help 40
5.2Database Operations 40
5.3Phone, chat and email Support 41
Support functions 41
Support Tracking 41
6Automation 43
6.1Technology and Standardization 43
6.2Exhibitor Tool 43
6.3Reference Code 44
7Service Level Agreement (SLA) 45
7.1Reliability 45
Reliability Calculations 45
Availability Requirements 45
Defect SLA 45
Scheduled Maintenance 46
7.2Response Times 46
7.3Deployment Assumptions 46
Sizing Minimums 46
7.4Attack and Catastrophe 47
7.5Support Availability 48
8Deployment 49
8.1Geography Rollout 49
8.2Languages 49
9Appendix A – Pricing 51
9.1Pricing Summary 51
9.2Supporting Data 52
10Exhibit A. Intent to Submit a Proposal 53
11EXHIBIT B. General Release 55
The TDL will contain all information necessary for service providers and other ecosystem members to generate Key Delivery Messages (KDMs) to enable the exhibition of Digital Cinema Packages (DCP). Information will be made available to authorized subscribers. The registry would not be involved in the actual KDM or DCP generation. The goal of a TDL system is to maintain timely and accurate information on participating Devices so that participating subscribers can obtain information needed to issue KDMs.
The TDL will be capable of receiving facility list information directly via an automated Facilities List Message (FLM-X) and through a web interface. The information will come either directly from the facility or through an authorized intermediary such as a deployment entity, system integrator, or country-specific centralized TDL. Each authorized distributor in a territory would subscribe to the TDL to take a snapshot (replicate the information) of the registry in order to generate KDMs.
Vendor(s) will be providing a proposal that includes four primary functions. These are: