Recently active
Please join us at PTC LiveWorx Europe 2015, November 17-18, Stuttgart, Germany. At this event, you will join the fastest-growing network of IoT professionals responsible for product innovations and new business models for creating, connecting, analyzing and servicing “smart products”. At PTC LiveWorx Europe, you will:Learn from Experts - Access dozens of sessions hosted by customers, PTC product experts and business leaders sharing vital best practices to accelerate your IoT journey and help you drive tangible business results. Be Inspired - See visionary keynotes up close and personal. PTC will host a series of engaging keynotes featuring industry luminaries, leading manufacturers, customer spotlights and much more.Connect with Partners - Learn how to leverage solutions and innovations, and engage in meaningful conversations in the Partner Pavilion and IoT Solution Showcase.Experience Breakthrough IoT Technologies – In the first of its kind IoT Solution Showcase, you will
From Mike Mahoney's blog:"There’s a few pieces you need in place to do a file transfer. Transfers can be executed in either direction: edge->platform or platform->edge. To do a transfer the edge component must be configured with a set of virtual directories. For the EMS, the configuration section would look like this:"file": { "virtual_dirs":[ { “In" : "./in" }, { “Out": "./out" }, { "staging": "./staging" } ], "staging_dir": “staging"}This is important because you will need to virtual dir names in the parameters to the Copy call. In the above example assumes that there are three directories in the same location as the EMS executable: ‘in’, ‘out’, ‘staging’. You can specify absolute paths as well.For the example I’m about to give, assumer the following:A RemoteThingWithFileTransfer named RT1.That the files a
"The scanRateResolution setting controls the frequency at which the main loop of a thing script executes in the LSR. Once a ‘thing’ script is started it enters into a loop that executes until the script resource is shutdown. Each iteration of this main loop takes a number of actions. At a high level it does the following:Goes through all your configured properties. If each property’s ‘scanRate’ amount of time has expired, then the property is evaluated to see if it should be pushed. To do this, the property handler read method for each property is called and the new value is compared to the old (if necessary). If the property needs to be pushed to the server its is added to a temporary list of properties to be pushed.The temporary list of properties is pushed to the server. If no properties have been evaluated, or no properties need to be pushed, then this list will be empty and nothing is pushed.The thing’s registration with the EMS is checked
"During edge testing we ran into the bug PLATFORM-1841. When a connection was lightly loaded and had little or no activity, a multipart message sent from the server to the edge would fail to send the last chunk until it received a message of any sort from the edge. The end result would be a message timeout on the server. Quite often the timeout would be avoided because of the fact that the edge regularly sends pings to the server, but since the default ping rate is longer than the default message timeout you would often see multipart messages from the server to the edge timing out.We were able to resolve this issue by modifying the SO_SNDBUF value that Tomcat uses for sockets. This controls the size of the output buffer used by TCP. Setting it to something larger than our message chunk size of 8192 prevented the timeouts and ensured that all the chunks were delivered as expected.This config option can be set in the Tomcat Connector configuration in y
Reposted from Mike Mahoney's blog:"'Pings' are the mechanism that our websocket clients (both EMS and SDKs) use to maintain an active connection with the server. There are two primary reasons for pings:Proxies/routers between our clients and server might automatically disconnect idle connections after some period of time.In some cases, if a TCP connection is dropped the client or server might not immediately become aware of the lost connection. If the server expects a ping within some predefined amount of time, but does not receive one, then it can assume the connection is dead and close it. Similarly, if a client sends a ping and does not receive a response within some amount of time, then the client can assume the connection is dead.The server, by default, has an Idle Connection Timeout of 60 seconds (found in the WSCommunicationSubsystem). This means that any websocket that has been inactive for 60 seconds will be closed. Therefore, clients must send so
Reposted from Mike Mahoney's blog post:The EMS creates the config.json.booted file after a successful startup and connect. It writes out its current configuration as a backup. If, on later restarts, the config.json is corrupted for some reason the EMS will fall back on the config.json.booted.A common problem is that a user will edit their config.json and inadvertently insert an error. Then, on startup, the EMS will fall back on the config.json.booted. This will often go unnoticed unless you are closely watching the error log of the EMS. During initial development and configuration it is usually a good idea to delete the .booted file if you are trying different configuration settings.
Reposting Mike Mahoney's blog post:"There’s two Lua properties in tw_server that you can use to discover information about the EMS's availability and connection status:tw_server.available – set to true if the script resource can connect to the EMS.tw_server.online – set to true if the script resource detects that the EMS is connected.Here’s how they work. Everytime the tw_server API is used to make a HTTP request to the EMS it checks the EMS status:If the HTTP response is 200, it considers the EMS available and onlineIf it is a an error, is calls the new isConnected propertyIf the result is a 200:Set tw_server.available to trueChecks the result of the response to set tw_server.onlineIf the result is a 503 with a JSON response:Set tw_server.available to trueChecks the result of the response to set tw_server.onlineIf the result is a 503 without a JSON response:Sets tw_server.available to falseSets tw_server.online to falseKeep in mind that these variables can be stale if the LSR ha
Reposting Mike Mahoney's blog post:"The 5.0 version of the Lua script resource has improved support for InfoTables. By using the tw_infotable library you can create and manipulate InfoTables:---- Create a DataShape. This definition will place the DataShape into-- the global 'DataShape' table. This definition would typically be-- found in your template file.--dataShapes.MeterReading( { name = "Temp", baseType = "INTEGER" }, { name = "Amps", baseType = "NUMBER" }, { name = "Status", baseType = "STRING", aspects = {defaultValue="Unknown"} }, { name = "Readout", baseType = "TEXT" })-- Lock around this chunk of code. Must always lock around-- access to the global DataShape table.tw_mutex.lock()---- Access the DataShape we want to use and then clone it. DataShapes-- must always be cloned before being used to create an InfoTable.--local ds = DataShape.MeterReading:clone()---- Create an InfoTable based on the DataShape. If this fails the -- function will return nil plus an error message.
Re-posting Mike Mahoney's blog post:"Websockets disconnects can happen by choice, or due to exceptional/error conditions. Here is some information about what happens in each case:Clean disconnect: During a clean disconnect, the user or application will initiate a disconnect sequence. This has two steps. First, if one or more things are bound to the websocket, the client will send an UNBIND message to the PLATFORM. This will cause Things bound to the websocket to appear as offline (their isConnected property will be set to false). Then, the client will close the websocket according to the websocket protocol.Exceptions/Errors: In many cases, the underlying network interface will be aware of unexpected disconnects. For example, if you forcefully kill an EMS, the Platform's network interface will be notified, the websocket will be closed, and Things will be cleanly unbound. In those cases, the updating of the isConnected property will o
Re-posting Mike Mahoney's blog post:"I've explained the connection process for 5.x web socket based clients a lot of times, so I thought it would be useful to just write it up. The SDKs and the EMS both follow a three step process when connecting to the Platform:Establish the physical websocket: The client opens a websocket to the Platform using the host and port that it has been configured to use. The websocket URL exposed at the Platform is /Thingworx/WS. If configured, TLS will be negotiated at this time as well.Authenticate: The client sends a AUTH message to the platform, containing either an App Key (recommended) or username/password. The AUTH message is part of the Thingworx AlwaysOn protocol. If the client attempts to send any other message before the AUTH, the server will disconnect it. The server will also disconnect the client if it doesn't not receive an AUTH message within 15 seconds. This time is configurable in the WS
Supporting Large Scale IoT Data RequirementsThingWorx 6 Overview–Flexible Storage Option–DataStax option–Upcoming plansThingWorx Edition Strategy–Overview of all editionsScaling ThingWorx – When to use Enterprise EditionThingWorx 6 Enterprise Edition–Packaging changes
Market Segment IntroductionConnected Product ConsiderationsTarget Buyer PersonasCommand of the MessageThe Solution - How We Do ItValue Proposition - How We Do It BetterCustomer Proof PointsCompetitionCompetitive DifferentiationDiscovery Questions
ThingWorx: Data Hub for the Connected Enterprise
IoT Sales Training - Concepts and TerminologyWhat is IoT?Market OpportunityIoT BasicsCustomer ExperienceA recorded version of this presentation is available here: Video Link : 1148
IoT Sales Training - Concepts and TerminologyWhat is IoT?Market OpportunityIoT BasicsCustomer Experience
Support.com's Nexus cloud software for Support Interaction Optimization (SIO) wins the 2015 Customer TMC Lab's Innovation Award: TMC Announces Winners of the 2015 CUSTOMER Magazine TMC Labs Innovation AwardIn July, Nexus won the 2015 TMC Labs' Contact Center Technology Award: Support.com Receives TMC Labs’ Contact Center Technology Award for Improving Customer Experience with Nexus® - Support.c…The ThingWorx Ready Nexus Connect extension adds a UI widget to the ThingWorx development environment which, when embedded in a mashup or dashboard and configured, will allow a user to contact a Nexus support agent who can assist them remotely. The extension provides a communication channel from the ThingWorx product to the Nexus support platform and allows:The user of a ThingWorx solution to chat with a Nexus agentThe agent to review diagnostic information about the user’s ThingWorx environmentThe agent to remotely take corrective actions to resolve the user’s issue. Get the N
This presentation was given at PTC Live 2015. It is intended for use with customers that have just purchased ThingWorx and are looking for guidance on how to organize and launch their IoT program. It is a great way to show thought leadership around PTC and IoT.
I am very excited to announce our plans and offer you a sponsorship opportunity at the all new PTC LiveWorx Europe, the premier customer and prospect event that infuses PTC’s world-class agenda for product development professionals with the IoT. This will be the most important pan-European event PTC hosts this year, and it will be everything you have come to expect and experience in Stuttgart -- only bigger and better than ever. PTC LiveWorx Europe is an industry-defining event, featuring two days packed with keynotes, announcements, break-out sessions and customer networking opportunities. You will be able to showcase your company to the largest and most important pan-European community of professionals responsible for the development of smart connected products, systems and operations. At the IoT Partner Expo and IoT Showcase Area, you will reach hundreds of customer and prospect attendees from medical device manufacturing, industrial manufacturing, high tech, telec
Manufacturers are increasingly adding software, sensors, and wireless connectivity to their products,providing a foundation for the Internet of Things (IoT), which IDC defines as a network of uniquely identifiable endpoints (or "things") that communicate without human interaction using IP connectivity. IDC forecasts that by 2020, there will be 30 billion connected devices in use by consumers and businesses. These smart and connected products in turn become critical components in the connected supply chain and smart manufacturing. IoT is fast becoming a reality: IDC survey results show that 55.0% of discrete manufacturers are researching, piloting, or in production with IoT initiatives. And IDC forecasts the worldwide IoT market will grow from $1.3 trillion in 2013 to $3.04 trillion in 2020. Yet, the lack of industry standards and well-defined best practices for IoT regarding connectivity, data storage, and even security presents substantial challenges to manufacturers as they ramp up t
Smart, Connected Applications Maximize Agricultural Business PerformanceThingWorx Platform gives OnFarm Go-to-Market Capabilities
The IoT Value Roadmap (v.2.0) is a guide to help organizations create value in a smart, connected world. Key IoT use cases (some including AR) from hundreds of customer interactions are defined and linked to their business impact in the form of value driver and metrics. Start your connected journey here.NOTES:This version includes the KTM Motorcycle AR Welcome Experience. Requires the Vuforia View phone app. Use with: IoT Use Case ebook
Release 5
Key Insights• Digital disruption has the potential to overturn incumbents and reshape markets faster than perhaps any force in history. • The Global Center for Digital Business Transformation (DBT Center), an IMD and Cisco initiative, is dedicated to original research and to creating opportunities for executives to innovate new business models for the digital age. To learn more about the current state of digital disruption and the outlook for industries, the Center surveyed 941 business leaders around the world in 12 industries. • The results of our survey several troubling findings about the potential for disruption, and incumbents’ readiness to adapt. Survey respondents believe an average of roughly four of today’s top 10 incumbents (in terms of market share) in each industry will be displaced by digital disruption in the next five years. • Despite these dire ramifications, digital disruption is not seen as worthy of board-level attention in about 45 percent of com
By Eric Auchard 6 hours ago By Eric Auchard FRANKFURT (Reuters) - The top executives of many a corporate giant must feel like the fictional character Gulliver, waking up to find themselves under attack from modern-day Lilliputians, small start-up companies which overwhelm their established rivals with new technologies. The old powers of market incumbents - massive scale, control over distribution, brand power, millions of customer relationships - are no longer seen as the obstacles they once were to agile rivals with innovative business models. A new survey finds business leaders believe four out of 10 top-ranked companies in their industries worldwide won't survive the next five years.They blame the accelerating change in technology, shifting business models and a need to merge to cut costs in order to ensure they don't become footnotes in someone else's corporate history. "Not just lone companies, but
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.