Technology and Management International, LLC Home | About Us | Contact Us  

Technology and Management International, LLC

  Browse our areas of expertise:
     Communications & Marketing
     Computer Science & Database Development
     Configuration Data Management
     Contract Vehicles
     Logistic Support
     Manufacturing Support
     Materials Science
     Network Consulting Services
     Program & Acquisition Management
     Systems Engineering
     Technology Transfer

TAMI personnel have been providing system engineering and software development services to the U.S. Army Armament Research, Development & Engineering Center (ARDEC) for over 20 years. The Quality Engineering Directorate (QED) is responsible for configuration management (CM) and status accounting of the Army's weapon systems.

CM is a discipline applied to a configuration item (CI) for its entire life cycle. Effective CM ensures that the defined user requirements of a CI are met. The four functions of CM are:
  • Configuration Identification (CI) - Identifies the item, and establishes and maintains a basis for control and status accounting for an item throughout its life cycle.
  • Configuration Control (CC) - Controls the proposal, justification, evaluation, and coordination of all changes to a CI (e.g., ECPs, RFDs, RFWs, ERRs, etc.) and its documentation.
  • Configuration Status Accounting (CSA) - Records and reports information required to manage the documentation; the status of the proposed changes, deviations, and waivers; the implementation status of approved changes; and the management of CIs in the operational inventory. CSA ensures effective logistic support.
  • Configuration Audit (CA) - Consists of a functional (FCA) and physical (PCA) configuration audit conducted by the government prior to accepting a CI and establishing a product baseline. The CA verifies that the CI complies with its corresponding configuration information.
TAMI's support of the CM process at ARDEC includes designing and developing the software systems that interface with the Technical Data Configuration Management System (TDCMS), including but not limited to the Engineering Changes at Light Speed (ECALS) System, Concurrent Engineering Action System (CEAS), and the Computer Aided Requirements System (CARS).

Our CM engineers are well trained in MIL-STD-973 procedures and standards, and are familiar with the alternatives and innovative approaches to current CM practices recommended by the Functional Support Templating approach.

The compilation, review, analysis, certification, and acceptance of technical data for armament systems and assigned materiel are a substantial undertaking. TAMI has provided continuous technical data management (TDM) support to several DOD organizations. We are familiar with many methods of Technical Data Package (TDP) validation and have conducted desktop audits (DTAs), configuration audit reviews (CARs), build-to-print validation, and a combination of the above for assemblies, subassemblies, and components within a system, depending on the technical complexity and manufacturing risk involved.

TAMI personnel have modified and validated drawings, operated the aperture card data repository, reviewed and analyzed past and current TDM processes, and provided a variety of quality assurance services in association with the TDCMS. We are intimately involved with the Joint Engineering Data Management and Information Control System (JEDMICS), as well as many ancillary software programs, such as ECALS, CEAS, CARS, etc., that have been developed at the QED.

Integral to the CM process is JEDMICS, which stores over 1.2 million weapon systems drawings used to prepare TDPs. TAMI has performed all system administration functions for JEDMICS since its installation at ARDEC. In addition, TAMI has implemented all JEDMICS software modification releases, including:
  • TECP 44 - Issued for scanners and noncompliant C4 images.
  • TECP 45R1- Provided dialects for the various types of punch data on aperture cards.
  • TECP 38 - Implemented a number of software "bug" fixes to JEDMICS and provided enhanced functionality, such as the Generic Import Server, Generic Output Server, and a Locator Index utility to allow the interface of JEDMICS with MEDALS.
  • TECP 51R2 C1 - Expanded the distribution of TECP 51R2 (issued only to MICOM to implement a number of enhancements and bug fixes to JEDMICS 2.5).
  • TECP 51R2 C2 - Bug fixes for 51R2 C1 release.
  • TECP 51R2 C4 - Bug fix for Generic Output Service.
  • TECP 52 4- Implemented the Batchload Automation Tool, which automates the Army procurement bid set pull process.
  • TECP 52 C3 - Provided fixes for GOS/BOS utilities for full compatibility with the 2.5.1 API Client.
  • TECP 61 C1 - A baseline install that bundled patches and previous releases.
  • TECP 81 - Issued electronically as replacement binaries for the Index Import application delivered in TECP 74.
  • TECP 83 C1 - Issued to enable all JEDMICS sites to accurately capture and report system usage data points through a standard Oracle procedure.
  • TECP 84 C1 - Issued to provide a fix for the Y2K date conversion problem for digital migration data.
  • TECP 89 C1 - Deployed to solve a problem when the ADL hangs loading or unloading a platter during a period of heavy usage or during coop of platters.
  • TECP 93 C1 - Issued to implement an enhancement to Index Export logging.
  • TECP 98 - Deployed the Solaris 2.5.1 Recommended Patch Cluster.
  • TECP 99 - Deployed with updates to DOS devices.
  • TECP 100 - Issued to correct a problem with converting Fast Upload OPTOC files from KOSI to Multistore.
  • TECP 107 C1 - Deployed with the IRIX6.2 upgrade to the database server.
  • TECP 109 - Deployed to deliver the Solaris 2.6 upgrade.
  • TECP 115 - Delivered a multi_store_kill_cache script to resolve a bug in multi-store.
  • TECP 118 - Delivered a multi_store_reset_errors_counts script to clean error counts.
  • TECP 121 - Issued to address SPR G50219 (JOB_SERVER Stack Limit Exceeded).
TAMI personnel supported stand-down procedures for the Digital Storage and Retrieval of Engineering Data System (DSREDS), as well as stand-up operations for JEDMICS (which has supplanted DSREDS). We are intimately familiar with the JEDMICS operational and managerial environments, as well as all affiliated QED business process systems that JEDMICS interfaces with and/or indirectly supports, including but not limited to CEAS/VIEWER, TDCMS, TDP-Web System, and ECALS.

The QED currently employs many operational systems within its Integrated Data Environment (IDE), including:
  • VIEWER System
  • ECALS System
  • CEAS
  • CARS
  • Vendor Database System (VDS)
  • TDP-Web System
  • Drawing Number Assignment (DNA) System
  • Windchill Product Data Manager
  • Intralink
Many of these systems operate on multiple platforms, e.g., JEDMICS is Unix-based; TDP-Web is Linux-based; and VDS is NT-based. Many utilize different databases, e.g., JEDMICS employs Oracle, VIEWER employs Sybase, and TDCMS employs Informix. Furthermore, many of the systems are written in a variety of software languages, including C, C++, Java, Perl, Javascript, Visual Basic, and others. TAMI has designed and developed several of the aforementioned systems and retains the subject-matter expertise to maintain all of the QED's systems in a comprehensive and proactive manner.