ARMY MATERIAL COMMAND (AMC)

INTEGRATED DATA ENVIRONMENT (IDE)

OVERVIEW/STATUS BRIEFING

SOLE/HCIG

17 OCTOBER 95


WHY IDE?

NEED:

  • Integration, validation and demonstration in the Army environment of emerging systems.
  • Digitization of wholesale and retail levels leads to improved combat support.

HOW

  • Optimize integration of tools, programs and technologies being delivered.

TASKING

"To develop a strategic plan for achieving data integration across systems."

  • Lead Command (MICOM) will interface and work with responsible program managers, developers, and providers of automation and communication infrastructure.
    • Integration
    • Validation
    • Training
    • Deployment
  • Program/Managers will continue to provide the management and oversight of their systems.
  • Lead Command will work with Program Managers on Integration of their systems for training, testing, and development.

ARMY DIGITZED ACQUISITION DATA POLICY

  • JCALS and JEDMICS programs were initiated to provide the mechanism for creating both an integrated information system and a shared data environment for acquisition and logistics
    • JCALS provides thesystems, distributed hardware and software core infrastructure needed to manage, acquire, store, publish, distribute, and improve digitized data
    • JEDMICS provides the data repository for technical data/engineering drawings
  • New purchases must meetsystems standards and be capable of Integrating with the JCALS/JEDMICS environment
  • All Army major system acquisition support activities/PMs will plan for CALS implementation as part of their initial program acquisition strategy
    • Programs currently in development will convert data available only in paper or proprietary formats based on economics and life cycle support needs
    • Sustainment programs will convert data to digital format when:
      • major modification
      • Operational benefits justify conversion expense

IDE CONCEPT

  • Establish validation site for:
    • Early Integration
    • Testing
    • Training
    • Deployment
  • Automate logistics business processes
    • Re-engineer/improve
    • Implement metrics
  • Deploy Products: Tools/Systems
    • LSAR
    • CMIS
    • JEDMICS
    • JCALS
    • MMSS
    • SDS-MRP
    • EC-EDI
    • Other System Initiatives


IDE BENEFITS

  • General
    • Reduced cycle times in all aspects of weapon system acquisition and support
  • Functional
    • Improved quality and consistency of support functions
    • Reduced cost and increased efficiencies in cycle time
    • Impproved processes by utilization of work flow management tools
  • Techncial
    • Faster
    • Cheeper
    • Better
    • Hardware
    • Software
    • Communications
    • Data integration
  • Integration
    • Linking current tools
    • Adding additional tools
    • Integrating data
    • Automating/Integrating business processes

LEAD INTEGRATION/VALIDATION ACTIVITY

  • Aggressive medium risk plan
    • MICOM validation team mitigates risk prior to full fielding
    • Traditionally the greatest uncertainty is in the integration of massive product data bases
    • We will capitalize on what is already being done and quickly incorporate lessons learned
  • TEAM REDSTONE
    • Integration and Validation
    • Covers all phase of the weapon system life cycle
      • PM, CMS (development)
      • PM, JAVELIN (production)
      • PM, MLRS (production)
      • PM, Patriot (post production modification)
      • WSM, HAWK (sustainment)
      • Organic Depot maintenance
      • Contractor Depot Maintenance

    • IDE MANAGEMENT CONCEPT (MATRIX)

      • Management
        • Executive Director for IDE (LAISO)
        • Functional director for IDE (IMMC)
        • Technical Director for IDE (CIC)
      • Matrix support composed of
        • MSC/SRA organic across Functional/Technical lines
        • IDE POCs
        • CALS POCs
        • BPMs
      • OSD Level Contractor Support

      IDE STATUS

      • Draft IDE Implementation Plan submitted to AMC (July 95)
      • IDE PM Day (July 95)
        • Overview Briefing
        • Tools Demo
      • IDE missions and functions submitted to AMC (Aug 95)
      • IDE incorporation into Army CALS Implementation Plan (Aug 95)
      • RSA Site survey completed for prototype PMs and supporting elements (Aug 95)
        • Identified/Defined Communications and Hardware Requirements
        • Generated Bills of Material
      • IDE Funding approved (Aug 95)
      • IDE Funding Received (Sep 95)

      FUNCTIONAL SUPPORT

      • Project Concept Paper
      • IDE GCO
      • Data Collection Plan
      • "As-Is" Baseline
        • Policies and Procedures
        • Work Processes
        • Infrastructure
      • "To-Be"
      • Workflows
        • Functional Activities
        • Data Requirements
        • Infrastructure
        • Controls
      • Templates
      • Business Plan (by PM)
      • Project Implementation Plan

      TECHNICAL SUPPORT

      • Technical Design
      • Engineering Installation Plan
      • Technical Integration
      • Establish Hub
      • Infrastructure Deploy
      • System Design
      • System Deploy
      • System Test
      • Demo
      • Training

      ONGOING/NEAR TERM ACTIONS

      Stand Up Lead Command Validation Site Aug - Sep 95
      Extend Site Survey Across MICOM/TACOM Aug - Sep 95
      Develop Government concept of Operations (GCO)
      CALS POCs at MSCs/SRAs
      Aug - Sep 95
      Validate CMIS/JEDMICS Sep - Nov 95
      Incorporate Prototype PM Business Process into JCALS WFM BPMs Sep - Nov 95
      Develop Detailed Program Plans for FY 96 and Beyond IDE POCs Sep - Dec 95
      Incorporate Standard Metrics into Business Work Flow - BPMs Oct - Nov 95
      Build functional Templates Nov - Dec 95

      Conclusion

Association for Electronic Business Main Frame Articles catalogue

hcig.org v 4_2