Frequently Asked Questions
Question: Will I have to change my business processes to use COLTS?
Answer: Generally no. Even though the features of COLTS are tightly integrated, COLTS is designed to adapt to your workflow. COLTS is also fully tailorable -- you decide which features you need. You can even control what each user sees and what functions they can perform.
Question: Do end users need to install special software to run COLTS?
Question: Can COLTS be used by US Government organizations?
Answer: COLTS is currently used by several US Government organizations around the world. It is even running behind the .mil firewall on US Government servers. COLTS has received the following approvals:
- Navy NMCI – server qualified
- Department of the Navy Application and Database Management System (DADMS)
- Approved Department of Navy application listed in DITPR – DON
- Certificate of Networthiness – U.S. Army 9th Signal Command
- HP Fortify Scan 5 Star security rating, no DISA STIG vulnerabilities
- Section 508 compliant -- contact us to request a copy of the COLTS VPAT
Question: What advantages does COLTS offer over standard US military supply and maintenance applications?
Answer for Full Asset Visibility
Unlike most US military supply and maintenance applications, COLTS offers true full asset visibility. COLTS maintains a complete history for each serialized asset throughout its life cycle, even while it is installed as a component in an end item. End item configurations are maintained as top-down breakdown structures, with a complete history of configuration changes. Operational metrics are also maintained to drive COLTS automatic condition-based maintenance feature.
Answer for Contractor and Performance Based Logistic Support
COLTS is also designed to support PBL and CLS programs by granting both government and contractors access to the same COLTS instance. Contractors are granted limited access to record supply and maintenance activities directly in COLTS, where both government and contractors can instantly access critical information, such as government and contractor supplied material status, readiness, and maintenance status. This approach substantially reduces the requirement for contractor-generated reports and audits of contractor-operated applications, and helps to avoid duplication and potential inconsistencies that arise from separate government and contractor systems.