Sales Have Ended
Sales Have Ended
The OMA TestFest events are open to OMA and non-OMA member companies. To attend the OMA TestFest event it is a prerequisite to bring a LWM2M implementation (Client or Server) or other OMA enabler to test to the event. You will specificy which Enabler you will be testing during the registration process. There is a symbolic charge per implementation of $50.00; engineers attendance is free.
When you register for the TestFest event, you are automatically registered for the Seminar that will place on Thursday, January 21 from 17:00 to 20:00 immediately following the TestFest event. There is no need to register again for the seminar and the event is free for TestFest attendees. The Seminar is titled, "Bridging the Gap between Standards and Developers in the IoT Space". Read more about the Seminar here.
Note: The TestFest event is limited to 50 engineers only.
- Sunday 17 January
- 13:00 to 18:00 Setup (Optional)
- Monday 18 January
- 9:00 to 17:30 Setup and Testing
- Tuesday 19 January
- 9:00 to 17:30 Testing
- Wednesday 20 January
- 9:00 to 17:30 Testing
- Thursday 21 January
- 9:00 to 17:00 Testing
- 17:00 to 20:00 IoT Seminar
What is OMA LWM2M?
LWM2M stands for LightWeight Machine to Machine Enabler, developed by Open Mobile Alliance. This enabler targets constrained devices in the Internet of Things, IoT. It provides a light and compact protocol as well as an efficient resource data model that can be adapted to represent any type of service.
The LWM2M TestFest is open to any organization with a LWM2M based implementation to test. The test cases to use at this event can be found in OMA LWM2M test specifications, (at the bottom of the page).
Reference for further information: OMA Developer ToolKit
What is an OMA TestFest?
The OMA Interoperability Process (IOP) defines Interoperability Testing Events designed to help achieve a number of goals for OMA and its Members. These goals are:
- Ensuring the quality of OMA specifications, and
- Enabling vendors to verify and test the interoperability of their product implementations.
The OMA Interoperability Process (IOP) has been established around the concept of regularly held Testing Events which are commonly known as ‘OMA TestFests’. These are hosted by OMA in connection with an operator or vendor, in a confidential and secure testing environment, where member companies can bring their implementation(s) to test in multiple multi-vendor combinations.
Who is able to attend an OMA TestFest? Do I have to be an OMA member?
Both OMA member and non-member companies are invited to participate in TestFest events. The evevent is open to OMA and non-OMA member companies that have a LMW2M implementation (Client or Server) available for testing and/or any Enabler for which we have 3 clients and 3 servers for testing registered. Not more than 4 engineers may accompany any one registered product/implementation unless permission has been sought from OMA staff.
Are TestFests confidential?
All OMA TestFests are run as confidential events and therefore all participating companies are be required to agree to sign a Non-Disclosure Agreement (NDA) preventing the discussion or distribution of testing information and results beyond the community of participants in the TestFest.Where a participating company wishes to bring engineers from another company to assist in their testing efforts, please note that it is the responsibility of the participating company to ensure that the 3rd party engineers attending are legal covered and obey the requirements of the OMA NDA. OMA will work with participants to ensure a full level of confidentiality is available to ALL participants, including protecting product identities, designs, product capabilities, test results, etc. Companies who do not have a signed NDA on file with OMA prior to the start of the TestFest will not be permitted to participate.
I have registered, now what?
At the close of registration, OMA will evaluate whether there is enough clients and servers for each enabler for them to test against each other. If you are the only client or server registered for a particular enabler and you have no one to test against then unfortunately we will have to cancel the testing for that enabler.
Once registration closes on December 11, OMA still will begin to create a formal testing agenda that will be distributed to participants on-site. More detailed travel and event information along with FAQs will be distributed via email to all participants once registration closes.
Where do I stay? What are my transport/parking options getting to the event?
OMA will offer a block of discounted rooms at the rate of $165 USD per night (including breakfast and in-room WiFi) at the DoubleTree Hilton Mission Valley. Once you register, more information on how to book the hotel will be provided. Self and valet parking are offered at the DoubleTree Hilton Mission Valley. Discounted self parking is offered at a rate of $10 for Day Use or Overnight to event attendees.
Where can I contact the organizer with any questions?
Event Manager Megan Leonard may be reached via email at: MLeonard@omaorg.org or via telephone at: 858-623-0744.
Can I update my registration information?
Registration information cannot be updated on EventBrite. For any updates on your registration, attendance, ticket, and/or implementation information, please email Megan < MLeonard@omaorg.org >.
Is my registration/ticket transferrable?
Yes, if you would like to transfer your ticket to another employee of your company, please just email Megan < MLeonard@omaorg.org > with your update.
Do I have to bring my printed ticket to the event?
No, this is not required. Please do bring an ID or business card for check-in.
What is the refund policy?
Refunds for implementations will not be issued. You may change your implementation up until the registration deadline of Friday, December 11 by emailing Megan < MLeonard@omaorg.org > with your updated implementation information, including which enabler you will be testing. Any cancellations or no-shows will not be refunded. Refunds will only be issued to those implementations that are cancelled due to not enough clients and servers registered for a particular enabler.