OS 2.0.0 Launch Party

Insights from the video:

🌍 The promo standards community is a collaborative and inclusive tech community that brings together suppliers, distributors, and service providers to build something open and free for all.

🤔 The initial objective of standardizing data objects for order status ended up becoming something more significant and impactful.

📦 The new OS 2.0.0 separates the status of an order from the issues with the order, providing more clarity and transparency for distributors and service providers.

📦 Building a streamlined communication system between CSR reps, suppliers, and end users could lead to groundbreaking improvements in order management.

💡 The resolution object array provides recommended answers for specific problems, such as suggesting substitute items for back-ordered products or offering different shipping methods to expedite delivery.

⚙️ Streamlining workflow automation: "This is the direction that systems need to take in order to do workflow automation to really streamline the order process and the communication between the you know suppliers Distributors and service providers."

💡 Digital transformation is often misunderstood, but the launch of OS 2.0.0 is a concrete example of how it can revolutionize communication and automation in the industry.

🚀 The launch of OS 2.0.0 marks a significant step towards supply chain automation and takes us beyond basic order information.

Summary

TLDR: The key idea of the video is that the launch of OS 2.0.0 promotes the development of open standards, improves customer experience, and encourages digital transformation in the industry.

1. 00:00 🚀 The OS 2.0 launch party discussed the development of open standards and improving customer experience, with a focus on standardizing data objects and reducing transactional friction.

   1.1 OS 2.0 launch party happening, press releases coming soon, virtual hackathon in September.

   1.2 Next month, the speaker discusses upcoming events and initiatives, including a service provider committee and a Tech Summit, and then hands over to Raj to begin a PowerPoint presentation.

   1.3 Discussing the development of Status 2.0 and the thought process behind its creation, which occurred before the emergence of chat bots and had a futuristic vision.

   1.4 The speaker discusses the development of OS 2.0, a collaborative effort to create open standards and improve customer experience in the industry.

   1.5 The launch of OS 2.0.0 will reduce transactional friction and force the execution of digital strategies, with a focus on standardizing data objects such as purchase orders and order status.

   1.6 The initial objective of standardizing data objects for work status or inventory in OS 2.0.0 was realized during the development process.

2. 07:13 🚀 The team launched OS 2.0.0, which includes a streamlined communication system, improved data structure, and cleaner code, all aimed at effectively addressing and resolving order issues.

   2.1 The order status provides information on the status and issues of an order, separating them from the previous version and considering how to effectively communicate these issues.

   2.2 The team built a streamlined communication system to effectively address and resolve various problems that occur throughout the life cycle of an order, aiming to achieve something groundbreaking.

   2.3 The data structure was aligned with the PO standard, clarifying product level details and back order situations, while maintaining order metadata and streamlining communication.

   2.4 Version 2.0 has more fields and a cleaner code with string variables instead of integers, while keeping the same query structure as version 1.0.

3. 11:44 📝 The speaker discusses the importance of using UTC for timestamps and introduces two new features: the ability to receive details of specific issues and the option to know which items are part of a returned order status, while also mentioning the benefits of setting certain fields to false for backwards compatibility and the use of order URLs for customer confirmation.

   3.1 The speaker discusses the importance of using UTC for timestamps and introduces two new features: the ability to receive details of specific issues and the option to know which items are part of a returned order status.

   3.2 Setting certain fields to false allows for backwards compatibility and the ability to return a similar object with advanced data, while also indicating whether or not to include specific details in the returned object.

   3.3 The order URL is like a confirmation page tied to the specific order that only the customer can access, making it a better method than sending confirmations via email.

   3.4 The OCTA will be interviewed about query types and animator values, which are cleaner and behave similarly to previous versions.

4. 16:38 📝 The speaker discusses the changes in version 2.0.0, including the separation of status and issue category, the availability of proof URL, and the addition of a contact option for ordering and approval, as well as the use of arrays to connect suppliers with specific contacts and provide details of any problems with the order.

   4.1 The speaker discusses the status of open or pending orders and explains that issues can either be open with no action taken or pending review before being resolved.

   4.2 The status of an order can be determined by querying the order object, which includes information on open, closed, and all issues related to the order.

   4.3 In version 2.0.0, the status and issue category are separated, the proof URL is now available separately, and there is a contact option for ordering and approval.

   4.4 Array is similar to the purchase order and allows suppliers to connect with specific contacts for different issues, while the issue array provides details of any problems with the order.

   4.5 The speaker discusses the product object, sales order line number, purchase order line number, and the status and issue of the order, as well as the contact object and the new issue object for communicating issues with distributors and third-party providers.

5. 23:25 📝 Customer service reps can now provide due dates for issue responses, resolution URLs can be used to fix problems with recommended solutions, and the resolution object allows for customizable UI and data mapping in HTML forms.

   5.1 Use animated values and include a specific name or ticket number when using the issue category in Asana or Jira.

   5.2 Customer service reps can now provide due dates for responses to issues, as failure to respond by a certain date may result in order cancellation or hold.

   5.3 The speaker discusses the use of resolution URLs as a way for customers to fix problems, with the option for third-party providers to iframe the URLs, and suggests providing a list of recommended solutions for different issues.

   5.4 You can use a resolution object to provide recommended addresses and generate possible solutions, with the ability to indicate the blocking status and contact information for resolving issues.

   5.5 Passing the product ID, power ID, unique ID, resolution name, details description, and parameter array allows for the interface of the resolution object with various systems and data science engines to build a customizable UI.

   5.6 You can customize the display order, data type, name, ID, length, and mapping of parameters in the HTML form, including indicating required fields, versioning, and valid responses for dropdowns.

6. 31:17 🚀 Shift methods in OS 2.0.0 improve HTML form generation and problem-solving, while new features like handling back orders and toggling fields off streamline the order process; digital transformation is encouraged regardless of current systems in place.

   6.1 Shift methods are used to generate HTML forms and resolve problems in a futuristic way, and there is guidance on how to implement and populate objects for contact details.

   6.2 The speaker discusses the new features and improvements in OS 2.0.0, including the ability to handle back orders and toggle certain fields off, while still maintaining a similar data structure.

   6.3 Developing future-proof standards for workflow automation is crucial for streamlining the order process and communication between suppliers, distributors, and service providers, even if current systems cannot support them.

   6.4 Splitting out issues from order statuses allows for better communication along the supply chain, leading to improvements in credit holds, inventory management, and back orders, ultimately forcing digital transformation regardless of the ERP or system in place.

   6.5 They are updating and adding features to their system to allow customers to make changes to their orders, and they plan to deploy an application internally to customer service before making it available externally.

   6.6 The speaker demonstrates how a code snippet can pull open orders, update shipping addresses, and resolve order management issues using the new OS 2.0 with order management.

7. 38:18 🚀 The industry is undergoing digital transformation with automated systems and promo standards, as the new OS 2.0.0 is launched, allowing for supply chain automation and encouraging community involvement.

   7.1 This is the next stage of digital transformation in the industry, where person-to-person communication is replaced by automated systems using promo standards for updates and order management.

   7.2 Resolve URLs for proof resolution and credit settlement, as it is the closest evidence of digital transformation.

   7.3 The speaker announces that the standard has been posted live, with order status 2.0 in production and available for viewing and downloading, and mentions that Starline and Hit have published their OS 2.0 endpoints.

   7.4 Suppliers who were part of the beta group are actively using the next level service for supply chain automation, which is a significant step forward and something the community should be proud of.

   7.5 There was a delay in releasing the new software due to a bug found during the final review stages, but it was necessary to ensure that it had been implemented correctly by suppliers, distributors, and service providers.

   7.6 The speaker praises the committee for their work on the new OS 2.0.0 launch and encourages viewers to get involved and implement the new services, as the committee is ready to drive digital transformation in the industry.

8. 44:43 👏 Raj did a great job and everyone should reach out to him or Jessica for any questions or issues regarding promo standards.