NAWCWPNS Procurement Process Architecture


Final Report


July 1996


Walt Scacchi, Mark Nissen, and John Noll
ATRIUM Laboratory,
Information and Operations Management Dept.,
School of Business Administration,
University of Southern California.
213-740-4782, 213-740-8494 (fax)
(Scacchi@gilligan.usc.edu).




Preparation of the report and the research that preceding it were supported under a grant from the Office of Naval Research, N00014-94-0889. No endorsements implied.

Overview

A paper providing an overall description of our process engineering life cycle can be found at http://www.usc.edu/dept/ATRIUM/Papers/Business_Process_Modeling.ps.


Background and Definitions

Strategic Issues
  • Exploit emerging national information infrastructure (Internet/WWW) for EDI, Electronic Funds Transfer (EFT), or Electronic Commerce (EC).
  • 
    

    Tactical Problems
    
    
    
    Solution:
    
    

    Near-term

    
    

    Longer-Term

    
    
    Definitions:

    Sources of Experiences Encountered


    The process/capability life cycle follows.


    Meta-Modeling


    Definition and Modeling

    Return to Overview


    J&A Process


    RFP Process

    Return to Overview


    LNP Process


    Analysis


    Simulation:

    Knowledge-Based

    Discrete-Event


    Visualization


    Prototyping, Walkthrough, and Performance Support (Training On Demand)


    Process Measurement and Diagnosis

    J&A Process Measurement
    Static Structure
    MeasureValue
    Steps31
    Length31
    Breadth1
    Depth4
    Atomics11
    Branches1
    Iterations11
    
    
    J&A Process Measurement
    Static Organization
    MeasureValue
    Organizational Roles8
    Value Chains3
    Department Handoffs6
    IT-supported activities1
    IT-supported comm.0
    
    
    J&A Process Measurement
    Static Derived
    MeasureValueDiagnostic
    Footprint44Small Process
    Parallelism1.00*Linear Flow
    Feedback Ratio0.35Complexity
    Handoff Ratio0.19Departmental
    IT-A Ratio0.03Manual Work
    IT-C Ratio0.00*Paper Communication

    Return to Overview


    Process Redesign and Evaluation

  • Process measurements and domain-independent (re)design heuristics can be used to envision a number of redesign alternatives.
  • A simulation interface screen depicting one redesign alternative for the J&A Process - R1: Joint Review Meetings, can be seen here.
  • The development and application of domain-dependent and instance-specific measures and heuristics is expected to produce more specific redesign alternatives, such as those shown here or below (with simulation results that forecast process cycletime reductions).
    
    
    Process Redesign Cycletime Reductions:
    Simulation Forecast
    Redesign AlternativeTime Reduction
    J&A Joint Reviews67%
    J&A Workflow System67%
    RFP Joint Reviews22%
    RFP Workflow System28%
    RFP Expert Review System33%
    RFP Composition KBS67%
    LCP Workflow System21%
    LCP Composition KBS55%
    LCP EDI-FAST21-59%
    
    
  • Experience: Redesign hueristics often produce differing improvements when applied to different processes. This means that we should not expect a single hueristic to equally improve all processes to which it is applied.
  • A paper describing our approach to process measurement as the basis for guiding process redesign can be found at http://www.usc.edu/dept/ATRIUM/Papers/Process_Measurement.ps.

    Return to Overview



    
    

    Next Steps and Future Directions

    
    

    Return to Overview



    Integration: Data, Tool, User Interface


    Target Support Environment Generation

    • Automatically transforming a process model or instance into a process-based computing environment that selectively presents prototyped or integrated information systems to end-users for process enactment.
    • Experience: Considered a unique capability, not available in other process environments.
    • Experience: Simplifies or eliminates low-level process programming via "application generator" techniques.
    • Image files that show user interface displays of (a) process-encapsulated tool environment that was generated via automated transformation of the modeled and integrated process.

      A description of this mechanism can be found in the paper P.K. Garg, P. Mi, T. Pham, W. Scacchi, and G. Thunquest, "The SMART Approach to Software Process Engineering," Proc. 16th. Intern. Conf. Software Engineering,, IEEE Computer Society, Sorrento, Italy, 341-350, (1994).

      Return to Overview


    Instantiation and Enactment

    • Performing the modeled process using the environment by a process engine that guides or enforces specified users or user roles to enact the process as planned.
    • Return to Overview


    Enactment History Capture and Replay

    • Graphically simulating the re-enactment of a process, in order to more readily observe process state transitions or to intuitively detect possible process enactment anomalies.
    • Experience: Visualizing and replaying process enactment histories is well-received by managers and executives.
    • Experience: Supports "organizational drill-down" when process anomalies are observed.
    • An image file that shows a user interface display of (a) process enactment event history and timing measurements can be viewed when selected.

      Return to Overview


    Conclusions

    • Business process engineering in general, and procurement process engineering in particular, is a dynamic team-based endeavor that can lead to mature, streamlined processes through:
      • understanding existing processes,
      • measuring and diagnozing process structure and throughput,
      • simulating or prototyping of process redesign alternatives,
      • incremental development, iterative refinement, and the reengineering of ad hoc process task instances and models.
    • Process/capability engineering may be most likely to succeed when focused on high frequency, short duration cycle time, or high velocity processes.

    Return to Top


    This interactive presentation page is maintained by Walt Scacchi who can be reached at the e-mail address noted above. This page was last updated on 30 June 1996.