OSN 2.0 with Steven Stanley and the Standards Committee

Insights from the video:

Standardization and Updates

📈 Stephen Stanley will be discussing the advancements and updates in order shipment notification 2.0, providing valuable insights into the cycle of promo standards.

🔄 The purpose of OSN 2.0 was to update the standard, align it with other standards, and add missing capabilities based on feedback from end users.

🔄 The structure of OSN 2.0 is aligned with other services and the PO spec, indicating a more standardized approach to order shipping notifications.

📦 OSN 2.0 allows for more granular tracking of locations, quantities, and specific box contents, which is particularly useful for apparel suppliers.

📦 The PO standard and product data standard were crucial in making sure that the early standards created by promo standards were compatible with purchase orders, which are essential in the transactional piece.

📝 OSN 2.0, or shipment notifications, has gone through a peer review process, months of beta testing, and a vote from the membership to become a production-ready standard.

📦 Ship notification is the biggest piece of information that people need when trying to figure out what has and hasn't shipped.

Member Engagement and Feedback

🌴 Provo standards is planning a Tech Summit in February 2024 on the beach in Florida, which sounds awesome!

🗣 Members have the ability to participate in the RFS process and provide feedback to the standards committee, ensuring that their voices are heard in the decision-making process.

📝 The committee is open to considering and incorporating new information and ideas, even if they were not initially included, in order to improve the standardization process.

Summary

The key idea of the video is that Order Shipment Notification 2.0 aims to standardize and improve the clarity and implementation of standards for various aspects of order shipment, providing granular details and compatibility with product data and purchase orders.

📅 00:00 Steven Stanley discusses the advancements and implementation of order shipment notification 2.0, updating and aligning the standard with other standards and making details more granular for distributors and service providers.

• Looking for volunteers for future event planning, including the 2024 Tech Summit and a technology mentorship program, as well as mentioning the virtual Tech Summit and the partnership with promo kitchen.
• This video is about the official release party for the first release of the education session, which will be held on the third Tuesday of every month.
• Steven Stanley, a long-time member of the promo standards board, will provide a deep dive walk-through of the standard and explain how to post endpoints and find information for suppliers, distributors, service providers, and consumers.
• Stephen Stanley, a technology guru and member of the standards committee, discusses the advancements and implementation of order shipment notification 2.0 in the promo standards world.
• Shipment 2.0 was created to update and align the order shipment notification standard with other standards, incorporating feedback from end users.
• The speaker discusses the need to align purchase order information and order shipment notifications, update enumerations, and make the details more granular for distributors and service providers in the new version of the standard.

📦 08:32 The Order Shipping Notification 2.0 standardizes sales orders with multiple shipments and packages, improves naming conventions, includes supplier and distributor information, and provides clarity on shipping methods and product identification.

• Sales orders can now have multiple shipments and packages, with the sales order array being required for package information, which is a change from the previous standard.
• The transcript discusses changes in the naming convention of the shipment array, including address details, shipment type, carrier and service information, tracking number, dimensions, and a pre-production proof field.
• The 2.0 spec allows for supplier and distributor information, as well as the quantity unit of measure, to be standardized and easily referenced, even if the specific tracking number does not have detailed product information.
• The key takeaways from the Order Shipping Notification 2.0 are that it aligns with other services, has more required fields and detailed descriptions, makes it easier to identify products and parts, provides clarity on shipping methods, and offers a larger set of enumerated values.

📦 14:59 Suppliers should set up a Sandbox environment with test URLs and put all quantity and item information on the first item, while also considering that the math may not always be straightforward when determining the number of boxes based on the total quantity; OSN 2.0 aims to address issues with standardization and compatibility with product data and purchase orders, improving clarity and implementation of standards for various aspects of order shipment.

• Suppliers should set up a Sandbox environment with test URLs and put all quantity and item information on the first item, while also considering that the math may not always be straightforward when determining the number of boxes based on the total quantity.
• If you don't have specific package details, you can use OSN 2.0 to infer the weight and dimensions of each unit and learn how suppliers package items for shipping.
• The speaker discusses the availability of order shipment notification 2.0 endpoints and the upcoming release of order status 2.0.
• OSN 1.0 was developed in 2016-2017 and had issues with standardization and compatibility with product data and purchase orders, which is now being addressed in OSN 2.0.
• The organization aims to improve the clarity and implementation of standards for product data, purchase orders, invoices, shipping data, and tracking data, including minor details such as service levels and carriers.

📝 21:47 The speaker emphasizes the importance of being logged in to access all content on the website, including the endpoint listing, documentation, validator, and best practices, while discussing the limitations of the current membership tool and the need for a custom solution.

• The speaker discusses the process of launching a service and how to communicate and distribute information to members, emphasizing the importance of being logged in to access all content on the website.
• To access the endpoint listing and documentation, log in to the member section on the website, which also includes the validator and best practices.
• The speaker discusses the limitations of the membership tool used for hosting Provostandards.org and the need for a custom solution.

📝 25:32 The speaker discusses the transition from beta to approved services, with a focus on OSN 2.0, and provides links to view and download the necessary documentation, while also mentioning the deprecation of services and the importance of upgrading to ship notification for tracking shipments.

• The speaker discusses the transition from listing beta services to officially posting services that have been peer reviewed and approved by the membership, specifically mentioning the transition of OSN 2.0 or shipment notifications from a request for standard to a production ready standard.
• The transcript provides a link to view the basic details of the documentation, as well as a download link for a Word document containing all the necessary components to implement the service.
• Deprecation of services will be posted and remain indefinitely, with the Standards Committee no longer accepting RFs or listing them on the site, but there is still support for order shipment notification 1.0 and product data 1.0.
• Upgrade to ship notification if you have purchase order and product data endpoints, as it helps consumers, distributors, and service providers track shipments.

📝 30:27 The OSN 2.0 has launched with a service and endpoint listing, allowing users to view supplier information, request credentials, and manage their endpoints and services through integration with Wild Apricot.

• The OSN 2.0 has been launched with a service listing and an endpoint listing of 2350 endpoints available on chromostandards.org.
• Raj has posted the OS end service, which allows users to view supplier information, endpoint URLs, and request credentials.
• Starline has order shipment notification available for users with existing credentials, and they can request credentials if they don't have them, and the speaker will demonstrate how suppliers can post this onto their specific supplier account.
• The speaker explains how the integration with Wild Apricot allows users to log in using their promostandards.org membership login to manage their endpoints and services as a supplier.
• Click the icon in the top right to access a list of menus, including contacts and users who receive emails, where you can find basic company information.

📝 36:15 New endpoints should be tested and verified before being posted, live and test URLs should be listed in OSN 2.0, and there is a Sandbox environment for testing web services and validating their compatibility with promoscenters.org.

• New endpoints should only be posted if they have been tested and verified to adhere to the standard, as there is currently no official process for indicating that an endpoint is in production.
• List your live and test URLs in the OSN 2.0 system, and make sure to keep current data for the date range filter.
• The speaker discusses the process of requesting credentials for Starline OSN 2.0 and the importance of improving endpoint authentication for suppliers.
• There is a Sandbox environment available for testing web services and validating their structure and compatibility with promoscenters.org, where you can select endpoints and fill out basic parameters.
• OSN 2.0 is now available on promoscenters.org, allowing suppliers to post their endpoint and others to test the listed endpoints in the validator.
• Covered everything, any questions?

📝 43:20 The Standards Committee is developing a company information service to address the issue of optional features in endpoints, and they welcome feedback to improve standardization and future road map information.

• Some suppliers may or may not implement optional features in their endpoints, and there is a company information service being developed to provide important details about endpoints to help address this issue.
• Suppliers posting their data in a structured manner would allow for electronic access to information, and there is an RFS process for members to provide feedback to the standards committee.
• The Standards Committee is actively developing and updating specifications for the company information service, and they welcome feedback on data elements to improve standardization and future road map information.
• Feedback is welcomed early on and is important for improving standards, but it is also necessary to respect companies' investments and make changes when the timing is right, as seen in the transition from OSN 1.0 to 2.0.
• Service providers are encouraged to get involved in volunteer opportunities, the mentorship program, Tech Summit planning, and hackathon planning, as input is needed and appreciated, and the video will be posted on YouTube for those who missed it.