BrightSign Expectations

• The BrightSign OS is under continuous development and although we try to provide advance notice and roadmap guidance, the OS may be updated with minimal notice. It is the responsibility of the individual partners to manage player upgrades to ensure OS stability in their environment.

• BrightSign will share code examples to provide guidance to partners, but BrightSign does not write partner-oriented production code.

• BrightSign does not provide quality assurance for partner products.

Partner Expectations

• Partners are responsible for writing the software that integrates their systems with BrightSign players.

• Partners are responsible for qualifying BrightSign OS updates (see Operating System Releases).

• Partners should have a public web page listing supported BrightSign players.

• Refer to the earlier sections in this document on technical and operational best practices to optimize your BrightSign partner experience.

Built-in Partner Expectations 

• We expect partners to have a basic understanding of BrightSign’s products and features.

• We expect partners to follow the design practices as outlined in the BSB Hardware Manual (this includes available I/O, and thermal management). 

• Partner devices must pass any supplied functional and stress tests.

• Partners must sign the BSBI OEM VAR agreement.

• Partners must provide BrightSign with a production for inspection, testing, and possible demonstration.