Q1: Is the solution a Cloud-Based or On-Premise application?

A: SOCKETWorx is installed on client Windows Servers using Internet Information Services (IIS).  
Server Requirements: >V2012

Server Services: IIS, .Net Framework

Q2: SOCKETWorx connects to SQL Databases, so what versions are supported and where can they be located?

A: SQL Server (Full or Express) V2016 or greater is recommended and required if deploying ECE Worx Plugin DIAGRAMS.  SQL or SQL Express, depending upon scope, can be located on the same Window Server as SOCKETWorx, or on a different server. 

The IIS Application Identities must be set so that SOCKETWorx can communicate with the SQL instances.  All SOCKETWorx/SQL Connections must be established using SQL Authentication.

Q3: What external communications are required for SOCKTEWorx?

A: SOCKETWorx will communicate with ECE's Azure server. This server manages licenses, interface configurations, users roles, and permissions. ECE will whitelist the SOCKETWorx application server public IP so that it can communicate with it.

SOCKETWorx Azure is located within the Central US Region.   

The latest Gateway IP Addresses can be found here: 


The Gateway IP Addresses are:                                                                     

Gateway IP addresses Gateway IP address subnets
Central US13.67.215.62,,,,,

Q4: What internal communications are required for SOCKETWorx?

A: SOCKETWorx Connects to one LAN/WAN directory connection.  The purpose of this directory is to store PDF, and other, documents that SOCKETWorx will render for review, markup and export.  The SOCKETWorx IIS Application Pool Identity will require LAN/WAN access so SOCKETWorx can read these documents.


Q5: What client, or workstation, requirements must be met?

A: Workstations will require an HTML5 browser like Edge, or Chrome.  They will browse to the established SOCKETWorx URL/IP Address, log in, and go to work.  There are no browser add-ins or extensions required or available.

Q6: Are any Site-to-Site VPN or data gateways required?

A: No.

Q7: Are there any requirements to open specific ports?

A: Yes, SOCKETWorx outbound Port 587 to send email communication through the ECE Design hosted Socketworx Email Server.  If an internal email server is used then this outbound port is not required.  In addition, Socketworx communicates to the SQL Servers using port 1433.

Q8: Are there any network latency/response time requirements?

A: No

Q9: Is a proxy service (installed on-prem) used to create a communication bridge?

A: No.

Q10: Is there a mobile app for your solution?

A: No, but the application is a website and can be loaded using HTML5 browsers.  SOCKETWorx has been optimized for Tablets.


Q11: Is there a need for and does the solution support language localization?

A: SOCKETWorx is only supplied using the English language.

Q12: Who installs, deploys, and maintains SOCKETWorx?

A: IT professionals generally are responsible for configuring the Application and Data Servers; IIS and SQL respectfully. They establish application logins that SOCKETWorx will use to communicate with network directory locations and SQL databases.  Typically installation and establishing SQL Connection #1 can be accomplished within a couple of hours.

IT Professionals are usually tasked with SOCKETWorx service pack updates, which amounts to backing up and replacing the website directories and files.  Always, this is accomplished in 10-15 minutes.

Q13: What role does IT have in configuring SOCKETWorx, Connecting to SQL databases, and Adding users?

A: Generally, these roles are satisfied by CAD Administrators who are establishing CAD Projects that connect to SQL.

Q14: What login capabilities are provided for users?

A: SOCKETWorx requires users to login using email addresses and user-controlled passwords that are configured through the SOCKETWorx Application.

Q15: How are non-employee login credentials/authentication handled?

A: All users are set up and managed via the built-in SOCKETWorx user interface where credentials are established.

Q16: What options are available for integrations with the solution?

A: SOCKETWorx is a self-contained website.  It interacts with any SQL Database, reads the schema, and is able to display, edit and report on the data.

Q17: Is there an API?

A: There is a private API that allows incoming communication from the Worx Plugins.  No public API is available.

Q18: How is data stored?

A: SOCKETWorx is a web application that accesses and accumulates data and files. Since customer have deployment options data and file storage can vary amongst these three cases. 


Some SOCKETWorx modules like Electrical, CRM, SPECWorx, MTOWorx Snapshots, ISOWorx LineList, Work Orders, Reports Revisions, and Datasheet Revisions are deployable where all data and files stored under hosted services; Azure and AmazonS3.

IIS Basic: SOCKETWorx Enterprise Standard
SQL data and SQL documents are stored on client's sql instances and LAN/WAN file storage locations. Setup & Configuration Information is stored in an ECE Azure SQL Database dedicated to a specific customer. SPECWorx, WorxOrders, CRMWorx, RealityWorx, Datasheets, Report Revisions and other SOCKETWorx processing data and files are stored under SOCKETWorx hosted AmazonS3 buckets and ECE Azure SQL Database dedicated to a specific customer.  Elevated Tiers for performance and storage are available for purchase as usage as content grows.  

NOTE: Enterprise Standard customers may use their own Amazon S3 Buckets.  However, MTOWorx Snapshot, Datasheet Revisions, Specworx and RealityWorx store data in the ECE Azure SQL Database dedicated to a specific customer.


ECE uses a Tiered Pricing Model for SOCKETWorx.  This pricing model is based on Data Transmission Units as well as Storage - both Database and AWS S3 Storage.   SOCKETWorx relies on a single company specific dedicated Azure SQL Database for setup and configuration items and in some instances pure data.  The communication to the Azure Database affects overall SOCKETWorx performance.  The more Data Transmission Units (DTU's) the better the performance.  The greater the number of users and data requirements, the greater the need for DTU's and a higher Tier.  The Tiered approach allows ECE to provide a fixed cost based on a set of resources assigned to your database that your instance of Socketworx uses. The Azure Database is fully isolated and optimized for your workload as Socketworx provides a somewhat predictable level of performance based on user count. 

The performance number has 2 parts - Data Throughput and Storage.  Further, ECE uses the Tiers to further estimate storage numbers we host for our clients on our Amazon S3.


Tier 0 - Base Installation - Limited to 10 DTU, Limited to 2GB of database storage, 2GB Amazon S3

Tier 1 - Standard Usage - Limited to 20 DTU, 20 GB database storage, 10GB Amazon S3  $1100

Tier 2 - Plus Usage - Limited to 50 DTU, 40 GB database storage, 20GB Amazon S3  $2100

Tier 3 - Performance Usage - Limited to 100 DTU, 60 GB database storage, 50GB Amazon S3  $3250

Tier 4 and Beyond - Variable Pricing and will be evaluated on a case by case basis.

a.  How is data stored within the solution?
A: Project Data is stored and accessed on user-configured and maintained SQL, or SQL Express, Servers inside the company firewall. SOCKETWorx Setting, Configuration, and License Information is stored on Azure SQL Server. As described above somedata is store in the client Azure SQL Database depending on the module in use. In addition, some data is stored in Amazon S3 Buckets

b.  Is the data encrypted while at rest and in transit?
A: Azure SQL Database employ encryption at rest Transparent Data Encryption and in-transit encryption with Transport Layer Security (TLS)

c. What is the limit of total storage or max individual document size?  
A: Documents are stored on a Client Specified Network location size limits are enforced by the company only. SOCKETWorx file storage is via Amazon and hosted services storage is offered in tiers to accommodate demand.

d.  What is the maximum historical length allowed for customer data?
A: No maximum historical length is maintained by SOCKETWorx.

e.  What retention and cleansing capabilities do you provide to manage the data for internal compliances?  
A: Internal SQL Server Data Centers are managed by the Client.  The Azure SQL Server Database is maintained by ECE.  All 'retention and cleansing' is controlled by SOCKETWorx user whilst under subscription.  Hosted data retention shall be for a period of 1 year post subscription lapse and can be provided on demand.


Q19: What search capability does the solution provide?

A: One of the core roles of SOCKETWorx is to find data and documents.  Users have numerous points of search entry and in many interfaces users can set data views based upon data set where clauses.  No SQL Query Language understanding is required by the userbase.

Q20: What type of reporting capabilities does the solution provide?

A: Reporting is a core SOCKETWorx role and it delivers Excel workbooks.  Users create and save data views that can be filtered and exported as workbooks.  Report templates are formatted in Excel or in the application.  Workbooks can be exported one at a time or in bulk.

Q21: Are users able to create their own reports?

A: Yes, and highly encouraged if added to user roles.

Q22: Is data available to be queried using external tools?

A: Since SOCKETWorx is reporting on data from internal SQL databases, any other means can be used to query that data.

Q23: What training is provided or available that supports this?

A: ECE provides all self-help content inclusive of What's New Articles and Videos, Training Videos, Solution Articles & Manuals at no charge.

Administrative and User training is facilitated through Net Meetings.

On average users adopt their roles with the following one-on-one or one-on-many net meeting hours.

(6) IT/DBA - Server SOCKETWorx Installation & IIS Setup, Support/Training 

(10) SOCKETWorx Admin -  Setup and Connection Management                

(4) SOCKETWorx Admin - (SSMS) Introduction & Basics             

(8) SOCKETWorx User - Module-specific on topic (SPOT) training  

Q24: Can Non-Prodroduction be set up for development purposes?

A: Since many have formal Development, QC, GoLive procedures, how does the solution provide unique instances of the solution to develop, test, and promote between the environments?

SOCKETWorx is licensed for one environment. Additional Subscriptions can be purchased to accommodate preproduction requirements. Contact us for pricing.


Q25: What is the process of recovery to a point-in-time?

A: The SOCKETWorx application can be backed up with the IIS Windows Server and can be restored as needed.  The SQL Server Databases can be backed and restored as needed.  The customer has complete control of these functions.  The Azure SQL Server housing the client license & setup information is backed up on a daily basis and can be restored within 24 hours if required due to any unforeseen environmental or data corruption issue.

Q25: What is the Upgrade/Release Strategy?

A: SOCKETWorx Service Packs are released many times annually.  They are all-encompassing and require only minutes to apply.  Not all Service Packs will warrant deployment, so please review the What's New to find the compelling updates to do so.  One of those will be the 2 Year Policy, where only versions within the last 2 years will be supported.

Q26: What level of support exists?

A: All application support is processed by this help desk, by entering tickets.  Support Retainers are purchased in hourly blocks and then are consumed on an as-need basis.  Support Retainer hours must be consumed within one year and can be renewed as frequently as needed.   Support tickets have 4 urgency levels.  ECE Support is available Mon-Fri 8am-5pm CST by phone, email, and help desk ticket submittal, and then if necessary net meeting sessions.  Contact us for pricing.

Q27: Can custom services be created for our consumption by your development/consulting teams?

A: ECE is constantly enhancing SOCKETWorx and offers services.  Approximately, 25% of SOCKETWorx customers have requested enhancements to support specific use cases.