EPOCH Configuration Management Applications

The EPOCH CM software solution, like its predecessor PDMPlus, is a rapidly-deployable best-in-class configuration management application for use in industries with long-life products, equipment, systems and other assets that may operate for years undergoing numerous upgrades, repairs, refurbishments. and configuration changes in the field.

These industries include: aviation, aerospace & defense, marine, rail, transportation, industrial equipment, and other high-tech industries. Example application uses of EPOCH CM in these industries include:

  • Hardware Configuration Management
  • New Product Development & Deployment Configuration Management
  • In-Service Asset and Fielded Equipment Configuration Management
  • As-Designed, As-Manufactured, As-Deployed, As-Repaired Configuration Management
  • Fleet Maintenance Configuration Management
  • MRO Configuration Management
  • Aftermarket Service, Repair and Refurbishment Configuration Management
  • Digital Twin Configuration Management
  • Tech Pubs, Manuals, & Documentation Configuration Management
  • Procurement, Logistics & Supply Chain Configuration Management
  • Regulatory Compliance Configuration Management
  • R&D Lab and Testbed Configuration Management
  • Site and Network Configuration Management
  • Systems Engineering Configuration Management

These application all share in common the need to perform rigorous configuration management over the long tail of the As-X product lifecycle beyond the OEM’s original As-Designed or As-Released configuration.

Configuration Lifecycle

The use of Configuration Management software within these different industries and varied applications is driven by many of the same challenges, problems, and pains. Which of these configuration management challenges does your organization experience?

  • Sheer volume, complexity, and variations in configurations of component parts, design requirements, product deployments, and complete systems overwhelms legacy methodologies and tools
  • The actual as-deployed or as-maintained configuration has evolved to be very different from what was as-shipped or as-installed
  • Time and effort required to find and verify accurate configuration information eats into the project schedule
  • Lack of confidence in producing upon demand real-time live configuration of deployed assets by specific lot number or serial number
  • Discovery of where-used and analysis of change-impact on as-deployed configurations is unwieldy or untrustworthy, especially for systems operating far downstream of the OEM’s engineering release
  • Management of processes that create, use, or revise configuration data is absent, ad hoc, or broken; much less automated or optimized
  • Losing track of the change process due to changes being made without approval or enterprise awareness, or change history information unavailable, inaccurate, or obsolete
  • Losing configuration control prior to delivery with products produced that are not conforming to requirements, or data and document deliverables not conforming to what was released
  • Losing configuration control after delivery from not being able to track what components are installed on serialized end items
  • What’s actually bid or delivered by the contractor is not what was specified or bought by the customer
  • Failing the Product Configuration Audit mandated by the contract or program office
  • Lack of Baseline Configuration Management along with inability to identify and track Configuration Items over their individual lifecycles
  • Processes and procedures for mass customizations and variant management are themselves one-off customizations
  • Difficulty in keeping all the different or downstream BOMs accurate and synchronized with engineering changes across all product variants or lot/serial numbers
  • Installing unauthorized parts, purchasing obsolete parts, and work stoppage due to lack of approved parts
  • Parts produced for the wrong configuration without visibility to alternate or substitute parts that are authorized due to lack of proper communication and documentation
  • Software versioning and releases not compatible with hardware releases
  • Manufacturing inventory, tooling, and processes are misaligned with product configurations
  • Reject, rework, or scrap rates are too high due to old or wrong specifications
  • Installation instructions, work orders, test procedures, training manuals and service bulletins are often obsolete because of configuration inaccuracies
  • Integration and complexity of CM for the supply or service chain that has design and change authority
  • Configuration of digital twin models for service is hard to create or maintain, much less synchronize with the actual physical asset
  • Service contractors not having access to the OEM’s product configuration data or being overly-constrained to use only that product data
  • Completeness, accuracy, and security of data retention and document repository is undependable
  • Extended lifecycles of assets that are in-service for decades creates extraordinary LOTAR burden on CM data
  • Sustainment groups are unable to locate documentation or other historical artifacts
  • Failure to maintain, document, and track ITAR Compliance
  • Certification and other documentation records not matching the true status of the deployed configuration
  • Without a CM Plan the requirement for CM processes and tools are constantly in flux
  • Program management and project budget suffers due to a lack of visibility into CM problems and challenges

Next learn about the capabilities of EPOCH CM that allow it to address these challenges by examining EPOCH CM Capabilities.

Copy link