Rapid Response Team Formed
Design Data has formed a Rapid Response Team to provide current customers a speedy turnaround on bug fixes. Members of this newly assembled team of programmers will respond faster to posts on the support forums, and other issues that Design Data is alerted to.
Led by Lead Programmer-Analyst Michael Cornelius, an 18-year veteran of Design Data, the Rapid Response Team is committed to solving important issues in SDS/2 and getting fixes into releases as quickly as possible. This team of programmers will increase their level of direct engagement, with help from the Support department and current customers, to resolve day-to-day issues. Team members will attempt to replicate problems and prioritize them quickly, matching the issue to the appropriate programmer outside the team when necessary.
"Software stability is vital to customer satisfaction. We want to respond to user input and include those responses as early as possible in the release cycle," said Damon Scaggs, Design Data's president. "This initiative will result in a higher level of customer service, reducing delays in fixing issues."
The assembly of a Rapid Response Team demonstrates Design Data's commitment to interactive exchange of information to troubleshoot and provide feedback to current customers. This revamped workflow will move many issues through the response process with more precision, and get fixes into releases faster.
Douglas Steel Fabricating Corporation's Ottawa Street Power Station Project Featured in MSC
The December 2010 issue of Modern Steel Construction featured an article titled "An Inside Job," which highlighted the Ottawa Street Power Station project in Lansing, Michigan.
The project -- fabricated by Michigan-based Douglas Steel Fabricating Corporation -- required construction of a 10-story steel-framed office building inside the existing power station structure without disturbing its historic exterior.
The project's structural engineer of record created a Revit model of the structure; a CIS/2 version of the model was then imported into SDS/2.
Using a 3D SDS/2 model, Douglas Steel was able to visually demonstrate new steel members and existing members that were being incorporated into the new structure.
To read "An Inside Job" in the December 2010 issue of Modern Steel Construction, click here.
Ensuring the Best Experience With Support
To ensure you have the best possible working relationship with its Support department, Design Data assigns a personal Support representative to your company.
For Support to respond to serious issues more quickly, it is necessary to prioritize as follows:
1. Multiple SDS/2 stations down
2. Single SDS/2 station down
3. Hard bugs - bugs that stop a user from working completely
4. Soft bugs - bugs that have solutions or workarounds
5. Phone calls/messages providing a brief description of the question
6. Errors and questions emailed to firstname.lastname@example.org
When calling Support, please remember to leave your name, company name, number and a brief description of the problem when leaving a message. This allows your Support representative to be better prepared when calling you back. This also allows Support to prioritize according to the above guidelines.
When working with Support, please give as much information as possible. Try to imagine all the information you would require to be able to recreate a problem. Information that is helpful is the version of SDS/2 being used, the computer operating system, member types and sizes, steel grades, loads, etc. Sending screenshots, RFIs, sketches, etc., also help.
Everything mentioned above is extremely helpful to Support when users are reporting bugs. We must be able to recreate the issue and report the exact steps when creating a problem report (PR) for the issue.
If you run into errors that cannot be resolved on your own, please select the email button on the error which by default will email the error to the address that is set in User options under the site tab. You can also use the save button on the error, which will save it as a basic text file; this can then be attached in an email to email@example.com with a description of the issue.
Sending errors to Support the two ways mentioned above rather than taking a screenshot provides us with more information about the issue and can help us to resolve it more quickly. If the error is a bug, these methods can help us track down the problem as well.
Along with the error, it is also helpful to detail the steps taken in SDS/2 that caused the error.
If you experience issues with export files from SDS/2, it is helpful for us to have the same export file that you are having issues with. This allows us to open the file here and see the information that is output. In some cases we can open the file in the same software to see the same results.
To read the rest of this article, click here.