- About Us
New features in PackNGo (PNG) 12.1.2
01/15/2014: A patch has been released to fix the following :
Lean times warrant more cost effective solutions. Over the past few years government and private agencies groping with the looming budget cuts have begun charting plans to align spending with the reduced funding. These cost-cutting measures are impacting government and private businesses in the form of scale-backs on the number of new contracts, program stretch-outs, and cuts in funding levels available for procurement of new equipment.
The fact that funding vehicles being restructured and re-purposed towards maximizing the utilization of current capabilities has led the industry to put increased focus on extending the life of their current equipment. Several defense journals and newsweeklies cite the increased impetus on maintenance and sustainment of existing fleet. Aviation Week article (dt. Sept 25, 2012) cites the U.S. Air Force as “… pushing to more than double the life of its stalwart F-15 Eagles…” and “…delay fleet retirements…” while Defense News (dt. Aug 31, 2012) mentions the same military arm is planning F-16’s modifications to “…extend the life and upgrade more than 300 jets in the coming years…”. Stripes (dt. Apr 26, 2012) talks about Congressional momentum to “…extend the service life of the Navy’s nuclear ballistic missile submarines…”. Defense News (dt. May 31, 2011) also says this about US Navy and service lives of ships “…Revised U.S. Fleet Plan Extends Some Ships…”.
This has intensified the spotlight on MRO operations. Over the recent years the MRO markets have scaled up and the MRO landscape continues to expand ever so rapidly.
The development of IT in the MRO sector has evolved into a vital part of fleet operations. Many operators have begun updating/upgrading their IT infrastructure software, into a more capable and powerful tool for managing maintenance costs. Current proposed solutions include “…software upgrade that is focused on the health management…” (Aviation Week, dt. Nov 5, 2012) and “…integrating (more storage-capable) software into existing hardware on newer airplanes…” (Defense News, dt. Dec 31, 2012).
QSI has long been a provider of niche software solution which is a perfect fit for MRO IT infrastructure. QSI’s software interfaces are designed to work with existing legacy architecture, and at the same time can be integrated within enterprise systems. For the past two decades the TEAMS Tool-set has been an integral part of industry forecasting, maintenance-planning and scheduling processes thereby improving fleet reliability. QSI provides a suite of reliability-centered maintenance management products designed to eliminate mechanic research time, minimize excess inventory on hand, and increase service levels.
Learn more about QSI’s Integrated Diagnostics philisophy and the legacy of 20 years of providing cutting-edge fleet health management solutions:
We believe that a partnership with QSI will go a long way in reducing supplier-side working capital costs and creating customizable service packages driven by innovative solutions. Let us be a principal factor driving your business strategies in this rapidly evolving world.
We have been building TEAMS-Designer and TEAMS-RDS in both 32bit and 64bit versions. However, for most users, we recommend the 32bit version. This is based on the following considerations:
See the following table for our performance test results for different models of different sizes.
|Model Size||Testability Analysis Memory Usage||GUI/Reachability Memory Usage||Testability Analysis Runtime|
|10,000||293MB||288MB||1 min, 44s|
|14,000||280MB||301MB||4 min, 4s|
|20,000||1.88GB||311MB||8 min, 11s|
|39,000||1.79GB||1.29GB||19 min, 1s|
QSI is happy to announce the general availability of TEAMS 12.0.5. We strongly recommend all users of TEAMS 12.0.3 or earlier upgrade to this version.
Some features and bug fixes in this release include:
Are you finding it cumbersome to create a test that only detects a single failure mode or failure modes on the same hierarchy level? Try using a Direct Test. A Direct Test has all the functionality of a regular test without the complexity. The complexity is caused by having to create a new unique function and attach it to the tests and applicable failure modes. With Direct Tests all you need to do is specify which failure modes are detected by the test, eliminating the need to create and attach a new function to the failure modes and test. Try it!