IoT & Connectivity

Data Model Implementation Guide Part 3Step 7: Unique Components Thing TemplatesStep 8: Data Tables and Data ShapesStep 9: SystemConnections ImplementationStep 10: Next Steps Data Model Implementation Guide Part 3 Step 7: Unique Components Thing Templates All of the shared component groups have been created. The next stage is creating the unique component group of ThingTemplates. Each of the below sections will cover one ThingTemplate, how the final property configuration should look, and any other aspects that should be added. The breakdown for the unique component group ThingTemplates is as follows: Robotic Arm Properties The properties for the RoboticArm ThingTemplate are as follows:NameBase TypeAspectsData Change TypeTimeSincePickupNUMBER, Min Value: 0Persistent and LoggedALWAYSAxis1StringPersistent and LoggedVALUEAxis2StringPersistent and LoggedVALUEAxis3StringPersistent and LoggedVALUEClampPressureNUMBER, Min Value: 0Persistent and LoggedALWAYSClampSt

Data Model Implementation Guide Part 2Step 4: SystemConnector Thing TemplateStep 5: HazardousAsset Thing TemplateStep 6: InventoryManager Thing ShapeData Model Implementation Guide Part 2 Step 4: SystemConnector Thing Template After grouping our second set of common functionality and information, we came up with the list below for the second Thing Template to create, SystemConnector with 3 Properties. The breakdown for the SystemConnector Thing Template is as follows: Follow the below instruction to create this Entity and get the implementation phase of your development cycle going. System Connector Properties Let's jump right in.In the ThingWorx Composer, click the + New at the top of the screen.      2. Select Thing Template in the dropdown.3. In the name field, enter SystemConnector and select a Project (ie, PTCDefaultProject).4. For the Base Thing Template field, select Gen

Data Model Implementation Guide Part 1OverviewStep 1: Completed ExampleStep 2: Data Model ScenarioStep 3: LineAsset Thing TemplateData Model Implementation Guide Part 1 Overview This project will introduce you to methods for creating the data model that you have designed and are ready to implement. Following the steps in this guide, you will implement the Data Model you've already designed. After having insight into your desired Data Model, this guide will provide instructions and examples on how to build out your application using the ThingWorx platform.We will teach you how to utilize the ThingWorx platform to implement your fully functional IoT application. NOTE: This guide’s content aligns with ThingWorx 9.3. The estimated time to complete ALL 3 parts of this guide is 60 minutes. All content is relevant but there are additional tools and design patterns you should be aware. Please go to this link for more details.  Step 1: Completed Example Download th

Design Your Data Model Guide Part 3Step 7: PrioritizeStep 8: Largest GroupStep 9: IterateStep 10: ValidateStep 11: Next Steps Design Your Data Model Guide Part 3 Step 7: Prioritize  The first step in the design process is to use the Thing-Component Matrix to identify and prioritize groups of Components that are shared across multiple Things. These groups will be prioritized by number of shared Components, from highest to lowest, enabling is to break out the most commonly used groups of Components and package them into reusable pieces.Let’s examine our example Thing-Component Matrix to identify and prioritize groups.In the table below, we have done this and recognized that there are FOUR groups. NOTE: Each item in our unique Thing-Component Matrix would also count as a group on its own. This can be dealt with almost separately from our process, though, because there is no overlap between different Things. The "Templates for Uni

Design Your Data Model Guide Part 2Step 4: Data Sources – Component BreakoutStep 5: Data Sources – Thing-Component MatrixStep 6: Model BreakdownDesign Your Data Model Guide Part 2 Step 4: Data Sources – Component Breakout Component Breakout  Once you have a full list of Things in your system (as well as requirements for each user), the next step is to identify the information needed from each Thing (based on the user's requirements).This involves evaluating the available data and functionality for each Thing. You then align the data and functionality with the user's requirements to determine exactly what you need, while eliminating that which you do not. This is important, as there can be cost and security benefits to only collecting data you need, and leaving what you don't.NOTE: Remember from the Data Model Introduction that a Thing's Components include Properties, Services, Events, and Subscriptions. Factory Example Using the Smart Factory example,

Design Your Data Model Guide Part 1OverviewStep 1: Data Model MethodologyStep 2: User StoriesStep 3: Data Sources – Thing ListDesign Your Data Model Guide Part 1 Overview This project will introduce the process of taking your IoT solution from concept to design.Following the steps in this guide, you will create a solution that doesn’t need to be constantly revamped, by creating a comprehensive Data Model before starting to build and test your solution.We will teach you how to utilize a few proposed best practices for designing the ThingWorx Data Model and provide some prescriptive methods to help you generate a high-quality framework that meets your business needs. NOTE: This guide’s content aligns with ThingWorx 9.3. The estimated time to complete ALL 3 parts of this guide is 60 minutes. All content is relevant but there are additional tools and design patterns you should be aware of. Please go to this link for more details.  Step 1: Data Model Methodology&nbs

Hello, community, I am trying to back up my project on ThingWorx. I have created a subscription that listens to a scheduled event.I also made a user and password property on my "helper thing" that I use in my subscription.I followed this article:  https://www.ptc.com/en/support/article/CS210224However, no exports are being created in the ThingWorx storage folder.  What might be the reason for this? Regards,Jay_nisa. 

Hi community team,I want to set the limitation of selecting dates on the TWX datepickers within the range of 30 days only. If the selected date’s duration is more than 30 days then the data should not be accessed.Like,  There are two date pickers, In the first date picker (StartDate) I want that the user can select any date (For example user selects the date of 7th June 2022 ) then I want that in the second date picker (EndDate), Only those dates are visible which are next to the 30 days from the start date (For eg: till 5th July 2022) and all the other dates and the year dropdown will be disabled.OrIn the second date picker, it should show only dates till 30 days from the first date picker (Start Date).Is it possible in ThingWorx Date Picker widget to set it for the specified dates only?  ThingWorx Version 9.3.2 @PEHOWE @PaiChung @slangley  @

Using the Solution Central APIPitfalls to Avoidby Victoria Firewind, IoT EDC IntroductionThe Solution Central API provides a new process for publishing ThingWorx solutions that are developed or modified outside of the ThingWorx Platform. For those building extensions, using third party libraries, or who just are more comfortable developing in an IDE external to ThingWorx, the SC API makes it simple to still utilize Solution Central for all solution management and deployment needs, according to ThingWorx dev ops best practices. This article hones in one some pitfalls that may arise while setting up the infrastructure to use the SC API and assumes that there is already AD integration and an oauth token fetcher application configured for these requests. CURLOne of the easiest ways to interface with the SC API is via cURL. In this way, publishing solutions to Solution Central really involves a series of cURL requests which can be scripted and automated as part of a mature de

Build a Predictive Analytics Model Guide Part 2Step 5: ProfilesStep 6: Create ModelStep 7: Refine ModelStep 8: Next StepsBuild a Predictive Analytics Model Guide Part 2 Step 5: Profiles The Profiles section of ThingWorx Analytics looks for combinations of data which are highly correlated with your desired goal.On the left, click ANALYTICS BUILDER > Profiles.Click New....The New Profile pop-up will open. NOTE: Notice the Text Data Only section which is new in ThingWorx 9.3.       3. In the Profile Name field, enter vibration_profile.4. In the Dataset field, select vibration_dataset.5. Leave the Goal field set to the default of low_grease.6. Leave the Filter field set to the default of all_data.7. Leave the Excluded Fields from Profile field set to the default of empty.8. Click Submit.9. After ~30 seconds, the Signal State will change to&nbsp

Build a Predictive Analytics Model Guide Part 1OverviewStep 1: ScenarioStep 2: SettingsStep 3: Upload DataStep 4: SignalsBuild a Predictive Analytics Model Guide Part 1 Overview This project will introduce ThingWorx Analytics Builder. Following the steps in this guide, you will create an analytical model, and then refine it based on further information from the Analytics platform. We will teach you how to determine whether or not a model is accurate and how you can optimize both your data inputs and the model itself. NOTE: This guide's content aligns with ThingWorx 9.3. The estimated time to complete ALL 2 parts of this guide is 60 minutes.   Step 1: Scenario MotorCo manufactures, sells, and services commercial motors. Recently, MotorCo has been developing a new motor, and they already have a working prototype. However, they've noticed that the motor has a chance to FAIL CATASTROPHICALLY if it's not properly serviced to replace los

Manufacturing Apps Extension Comes with this Project  This Project Usually helps the user to create the tables based on DataShape, and do some operations like insert as shown below     var result = Things["PTC.SCA.SCO.PostgresDatabase"].Insert({ infoTable: MaterialClasses, dataShapeName: "PTC.SCA.SCO.MaterialClass" });     Similar way for the query, update Code Snippets can be used. This is the very Optimized way to avoid the Performance issue of DataTables (if there are more than 20,000 or 100,000 Records ).But this Project comes with Manufacturing Apps only1. How this can be achieved in Thingworx where there is no Manufacturing Apps ? 2. Is there a way to use PTC.SCA.SCO.DataConnection in Thingworx without Manufacturing Apps ?

Hi ,Creating/Working on the Custom Widgets, is there any already made widgets available for PTC side or through any Github, where team can explore and experiment the custom widgets for Thingworx 9.3 version.   @slangley @c_lowy @CarlesColl @paic Thanks,Shashi.

Hi,Trying to develop an Google Chart widget extension, when imported the Extension in to the TWX shows following error: Attached the Extension Zip File for reference@slangley  @c_lowy @PaiChung @CarlesColl  @VladimirRosu_116627 @VladimirN @Rajkumar_20673 Thanks,Shashi.  

Hello Guys,Is it possible to do a State Formatting not by fixed values for a label chart? For example  the main value is 24 581  and  I want that the bar is red when it hits below 25 percentage of that value.

Hello, Thingworx version 9.3. our customer has two Thingworx environments, Test and Production, respectively.Application development and tests  are performed in Test environment,Final deployment in Production environment is done by importing the project from the Test environment. Since data and property values differ between the two, the import is done without overwriting property values (i.e., the "Overwrite property values" option is deselected in the Import panel). Now, let's suppose we change an existing Thing in Test enviroment by adding some new Services and Properties.We need to import such changes in Production, without overwriting property values.However, after the import process, the new Properties and Services of the Thing are not present in Production. They are correctly exported in the generated xml.. Can anybody confirm this behavior?How to import new added Services/Properties of a Thing without overwriting Property values? Best,Pietro&n

Create Industrial Equipment Model GuideOverviewStep 1: Learning Path OverviewStep 2: Create Thing ShapeStep 3: Create Thing TemplateStep 4: Next StepsCreate Industrial Equipment Model Guide Overview This project introduces how to model industrial equipment in ThingWorx Foundation. NOTE: This guide’s content aligns with ThingWorx 9.3. The estimated time to complete this guide is 30 minutes.  Step 1: Learning Path Overview This guide explains the steps to get started modeling industrial equipment in ThingWorx Foundation and is part of the Connect and Monitor Industrial Plant Equipment Learning Path. You can use this guide independent from the full Learning Path. Other guides are available for more complete Data Model Introduction. When using this guide as part of the Industrial Plant Learning Path, you should already have ThingWorx Kepware Server installed and sending data to ThingWorx Foundation. In the next guide in the Learning Pa

Build an Equipment Dashboard Guide Part 2Step 5: Display DataStep 6: Test ApplicationStep 7: Next StepsBuild an Equipment Dashboard Guide Part 2 Step 5: Display Data Now that you have configured the visual part of your application, you need to bind the Widgets in your Mashup to a data source. Add Services to Mashup In the top-right, ensure the Data tab is selected.Click the green + symbol.In the Entities Filter field, search for and select MyPump.In the Services Filter field, type GetPropertyValues.Click the right-arrow beside GetPropertyValues. Note how GetPropertyValues was added to the right-side under Selected ServicesCheck the checkbox for Execute on Load. This causes the Service to execute when the Mashup starts.      7. In the Services Filter field, type QueryPropertyHistory.8. Click the right-arrow beside QueryPropertyHistory.9. Check the checkbox for Exe

Build an Equipment Dashboard Guide Part 1OverviewStep 1: Learning Path OverviewStep 2: Create ThingStep 3: Store Data in Value StreamStep 4: Create Application UIBuild an Equipment Dashboard Guide Part 1 Overview This project will introduce you to the principles of ThingWorx Foundation by creating an eqipment dashboard. Following the steps in this guide, you will create the building blocks of your first IoT application, including Things and Streams. We introduce the basics for creating an IoT application.NOTE: This guide's content aligns with ThingWorx 9.3. The estimated time to complete ALL 2 parts of this guide is 30 minutes.  Step 1: Learning Path Overview This guide explains the steps to create an Industrial Eqipment Dashboard, and is part of the Connect and Monitor Industrial Plant Equipment Learning Path. You can use this guide independently from the full Learning Path. If you want to learn the basics of creating an eqipment

I'm new here and starting to work with Kepware. For this new site, in the Properties of the RTAC device, if we leave the Block Sizes, Internal Registers at the default setting of 32, the last 11 tags show "Unknown" Value in the Quick Client. If we change the setting to 16, there are 3 Unknown. At 8 there are 3 Unknown, but 9 there are 4. I've tried several other Register numbers and the Unknown tags varies up and down, with no discernible pattern.   We just can't determine the logic behind what is set in Internal Registers and how many tags show an Unknown value. We currently have the setting at 1 and it's showing all the tags.   Anyone know how to properly determine what the Internal Registers should be? I'm attaching 4 screenshots showing the Registers setting and the Tags that are Unknown.   Thanks! Mike    

Configure Permissions Guide Part 2Step 5: PermissionsStep 6: Application KeysStep 7: OrganizationsStep 8: Next StepsConfigure Permissions Guide Part 2 Step 5: Permissions These permissions can be accessed on any Entity created on the platform. All Entities have permission control for both design time and run time.Permission TimeControlDesign timeControls what Users are able to do with Entities themselves while building the solution.Run timeControls what the Users are able to do with the data for an Entity when they use the solution. Permission TypeDescriptionProperty ReadRead property valuesProperty WriteUpdate property valuesService ExecuteExecute Services in this EntityEvent ExecuteQueue or fire Events in this EntityEvent SubscribeAbility to subscribe to Events in this Entity Access TypeDescriptionAllowAllow the User's access to this feature.DenyDeny the User's access to this feature.InheritSet the User's access to this feature b

Configure Permissions Guide Part 1OverviewStep 1: Completed ExampleStep 2: Common TermsStep 3: UsersStep 4: User GroupsConfigure Permissions Guide Part 1 Overview This project will introduce you to permissions inside of the ThingWorx platform. Permissions are used to control usage during development, runtime, and experience. Following the steps in this guide, you will be able to create Users, User Groups, Application Keys, and Organizations and tie them together. We will teach you how to create functional permission schemes in the ThingWorx platform to create a secure application and development environment. NOTE: This guide's content aligns with ThingWorx 9.3. The estimated time to complete ALL 2 parts of this guide is 30 minutes.  Step 1: Completed Example Download and unzip the completed files attached to this tutorial: PermissionsEntities.zip. In this tutorial, we walk through security concepts within ThingWorx. Utilize this file to see

Step 5: Log to Value StreamStep 6: Visualize the DataStep 7: Next Steps  Step 5: Log to Value Stream Now that you have explored the Properties of IndConn_Tag1, you’ve seen how ThingWorx Kepware Server feeds information to ThingWorx Foundation. To get an even better indication of changes and confirm continued connectivity, we will log the changes to a Value Stream in order to record the values with a TimeStamp. Create Value Stream Return to the ThingWorx Foundation New Composer browser.Click Browse.Click Data Storage -> Value Streams.Click + New.In the Choose Template pop-up, select ValueStream.Click OK.Type IndConn_ValueStream in the Name field.If Project is not already set, click the + in the Project text box and select the PTCDefaultProject.In the Description field, enter an appropriate description, such as Value Stream to record changes

Data Model IntroductionOverviewStep 1: BenefitsStep 2: EntitiesStep 3: Inheritance ModelStep 4: Scenario Step 5: Next StepsData Model Introduction  Overview This project will introduce the ThingWorx Foundation Data Model. Following the steps in this guide, you will consider data interactions based on user needs and requirements, as well as application modularity, reusability, and future updates. We will teach you how to think about a properly constructed foundation that will allow your application to be scalable, flexible, and more secure. NOTE: This guide's content aligns with ThingWorx 9.3. The estimated time to complete this guide is 30 minutes.  Step 1: Benefits A Data Model creates a uniform representation of all items that interact with one another.There are multiple benefits to such an approach, and the ability to break up items and reuse components is considered a best practice. ThingWorx has adopted this model at a high level t

How to Display Data in Charts Guide Part 3Step 6: Configure ChartsStep 7: Next Steps How to Display Data in Charts Guide Part 3 Step 6: Configure Charts You now have a test Thing that has an Info Table Property and Time Series Property with values appropriate for display in various Chart Widgets, as well as a Mashup with those charts inside.However, in order for the Widget to display data, you need to bind it to the data source. Bring Data into the Mashup Select the Data tab in the top-right section of Composer. Click the green + button under Data. In the Entity Filter field, search for and select DDCThing.In the Services Filter field, type GetProperties.Click the right-arrow beside GetPropertiesThe GetProperties Service will now appear on the right under Selected Services.Check the Execute on Load box under Selected Services.This will cause the GetProperties Service to execute