The meeting focused on reviewing updates to the Operations Maturity Model document, with Bill presenting his revisions and modifications to the content. The discussion covered terminology clarifications around OTT vs live streaming, the structure of document sections, and the addition of new topics like energy optimization and security. Bhavesh explained the document's purpose as an internal expert tool to help organizations assess and improve their streaming operations capabilities rather than a public-facing guide. The group discussed how to properly categorize and introduce different sections of the document, with Bill suggesting moving some introductions to be more contextually relevant. They also addressed the need to link to official SVTA documents for acronyms and definitions, and Jacob, a new member from Apple's livestream engineering team, joined the discussion to learn more about the project's goals.
Â
- All relevant section authors - Review and expand on the maturity model levels and examples for their respective areas (e.g., transcoding, content management, etc.) to provide more discrete examples and detail.
- Bhavesh - Add a comment in the document to ask the group for examples of what they consider to be OTT live streaming versus live streaming, to clarify terminology.
- Bhavesh - Add a note to link the acronym/definition section to the official SVTA glossary document.
- Bhavesh - Review and update the acronym/definition descriptions to ensure they are in line with official group definitions.
- Bhavesh - Move the player-specific note to the first sentence of the relevant section as discussed.
- Bhavesh - Work through the document later to remove edits/comments that can go away after acceptable edits are finalized.
- Bhavesh - Consider energy optimization and security topics for possible inclusion in a 1.1 version of the document, and monitor group feedback to determine if they should be included in 1.0 or deferred.
- Bill - Add his name to the contributors section of the document.
Â
- Antitrust Statement & Operations Maturity Model Project Update
- The meeting participants discussed the status of an operations maturity model document project.
- Bhavesh clarified that he was not the head of the group but was working on the document and seeking volunteers due to sporadic attendance.
- Bill mentioned making significant updates to the document, and the group agreed to review these changes together, with Bhavesh offering to access the document from Google Drive.
- The meeting appeared to be a smaller group session, as the main meeting was postponed due to NAB.
OTT vs Live Streaming Terminology
- Bill and Bhavesh discussed the terminology used in the document, specifically the distinction between "OTT live streaming" and "live streaming."
- Bhavesh explained that the term was changed from "streaming" to "OTT live streaming" during a member meeting based on JT's recommendation to narrow the scope.
- They agreed to seek examples from the group to better define the difference between the two terms and potentially include the terminology in an SVTA glossary.
Document Structure Improvement Discussion
- Bill and Bhavesh discussed improving the structure of their document by moving introductions for each section from the scope to where they are needed, making the content more contextually relevant.
- They agreed to create more concise introductions for each axis, potentially with the help of AI, to provide better context without overwhelming the reader.
- Bill suggested that each axis could have a primary author or proponent, and he expressed comfort in letting others review the updated content.
Control Layers and Sustainability Terminology
- Bill and Bhavesh discussed the distinction between vertical and horizontal control layers in their system, with vertical pillars handling specific content workflows from preparation to delivery and horizontal layers providing observability and management capabilities across all verticals.
- They also touched on the importance of security in this context.
- Bill shared insights about terminology preferences in sustainability discussions, noting that the US delegation prefers "energy optimization" over "sustainability" or "energy efficiency" to avoid regulatory implications.
Data Column Consolidation Discussion
- Bill and Bhavesh discussed the consolidation of data columns, noting that the original dataset had 14 columns which were reduced to the current 10, with Bill’s addition making 11.
- Bhavesh mentioned that adding one more column could be considered for discussion.
- Bill shared an example from the Canadian Broadcast Company where energy usage reporting led to significant efficiency improvements in their advertising pipeline, highlighting the potential importance of including energy optimization metrics.
- The conversation touched on security considerations related to including energy data, though Bill acknowledged not being an expert in this area.
Document Version 1.0 Release Strategy
- Bill and Bhavesh discussed the approach for releasing a document version 1.0, agreeing to focus on core features and leave energy optimization and other complex topics, like security and VOD, for version 1.1 to avoid delays.
- They emphasized the importance of getting the initial version out quickly while maintaining focus on live events due to additional challenges with VOD.
- Bill highlighted the need to clearly state what is not included in the document to help readers understand its scope, which Bhavesh confirmed was intended as a conversational technique rather than a documentation requirement.
Media Flow and Metadata Processing
- Bill presented a diagram showing media flow, control layers, and transverse elements, explaining how metadata is created and processed along the media path.
- The discussion highlighted metadata loss that occurs between organizations during transitions.
- Bill also updated the document from discussion style to documentation style, compiled a list of acronyms with definitions, and noted that the document is intended for industry operators rather than external readers.
- Bhavesh agreed to link to the actual definitions document for acronyms.
System Maturity Levels Development Framework
- Bhavesh and Bill discussed the development of maturity levels and capabilities for different paths in their system, emphasizing the need for internal expert-based documentation to guide progress.
- They highlighted the importance of defining capabilities and metrics rather than technology, with the goal of achieving predictive and preventative measures to eliminate user-facing failures.
- The discussion included clarifying terminology and ensuring accurate definitions for terms like OTT and QOE, with plans to review descriptions and involve relevant champions to further develop the framework.
Transcoding Integration Discussion
- Bhavesh and Bill discussed the definition and capabilities of transcoding integration, focusing on optimizing video quality based on factors like audience size and content type.
- They clarified the scope of the player-related discussions, ensuring it focused solely on live streaming capabilities rather than broader player functions.
- Bill made several edits to align the document format and content, and Bhavesh suggested adding a placeholder for cross-references to related standards, which Bill approved.
- They agreed to review and clean up remaining edits later, and Bhavesh requested Bill's contribution be acknowledged in the document.
Streaming Operations Maturity Working Group
- Jacob, who is new to the working group, joined the meeting and shared his background from the livestream engineering team at Apple, where he works on events like baseball, soccer, and F1.
- Bhavesh explained the purpose of the working group, which aims to improve streaming operations using a maturity model to help organizations assess and evolve their streaming capabilities.
- Bill, who joined through a merger in March, shared his experience with maturity models and how the concept was developed to help organizations understand and communicate their current levels of maturity regarding software development capabilities.
Next Meeting: Friday, May 8, 2026 8am PDT