Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to Somnetics-PMS
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

Side Menu

  • Overview
  • Roadmap
  • Work packages
  • Documentation
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDocumentation
        • Expanded. Click to collapseCollapsed. Click to showProject Plan
          • Expanded. Click to collapseCollapsed. Click to show1) Introduction
            • Hierarchy leaf1.1) Executive Summary
            • Hierarchy leaf1.2) Business Drivers
            • Hierarchy leaf1.3) Scope
            • Hierarchy leaf1.4) Out of Scope
            • Hierarchy leaf1.5) Assumptions
            • Hierarchy leaf1.6) Risks
            • Hierarchy leaf1.7) Deliverables
          • Expanded. Click to collapseCollapsed. Click to show2) Execution
            • Hierarchy leaf2.1) Methodology
            • Hierarchy leaf2.2) Tracking & Oversight
            • Hierarchy leaf2.3) Version Control
            • Hierarchy leaf2.4) Team Structure
            • Hierarchy leaf2.5) Stakeholder Matrix
            • Hierarchy leaf2.6) Reporting
            • Hierarchy leaf2.7) Effort & Schedule
          • Expanded. Click to collapseCollapsed. Click to show3) Quality Assurance
            • Hierarchy leaf3.1) Test Strategy
            • Hierarchy leaf3.2) User Acceptance
            • Hierarchy leaf3.3) Release Management
            • Hierarchy leaf3.4) Change Management
            • Hierarchy leaf3.5) Project Closure
        • Expanded. Click to collapseCollapsed. Click to showRequirement Analysis
          • Hierarchy leaf1) Introduction
          • Expanded. Click to collapseCollapsed. Click to show2) Requirements
            • Hierarchy leaf2.1) Business Requirements
            • Hierarchy leaf2.2) Functional Requirements
            • Hierarchy leaf2.3) Data Requirements
          • Hierarchy leaf3) Assumptions and Dependencies
          • Expanded. Click to collapseCollapsed. Click to show4) Use Cases
            • Hierarchy leaf4.0) Use Case Diagram
            • Expanded. Click to collapseCollapsed. Click to show4.1) Agent Usecase
              • Hierarchy leaf4.1.1) Read Config
              • Hierarchy leaf4.1.2) Login
              • Hierarchy leaf4.1.3) Logout
              • Hierarchy leaf4.1.4) Refresh
              • Hierarchy leaf4.1.5) Read Data and Decide
              • Hierarchy leaf4.1.6) Grab
              • Hierarchy leaf4.1.7) Notify
              • Hierarchy leaf4.1.8) Communication with Scheduler
            • Expanded. Click to collapseCollapsed. Click to show4.2) Scheduler Use case
              • Hierarchy leaf4.2.1) Read Config
              • Hierarchy leaf4.2.2) Log
              • Hierarchy leaf4.2.3) Communication with Agent
            • Hierarchy leaf4.3) Agent Scheduler Both-way connection
          • Expanded. Click to collapseCollapsed. Click to show5) Non-Functional Requirement
            • Hierarchy leaf5.1) Performance
            • Hierarchy leaf5.2) Security
            • Hierarchy leaf5.3) Response Time
            • Hierarchy leaf5.4) Reliability and Availability
            • Hierarchy leaf5.5) Scalability and Extensibility
            • Hierarchy leaf5.6) Legal and Compliance
          • Hierarchy leaf6) Process flowchart diagram
          • Hierarchy leaf7) Technology Stack
        • Hierarchy leafTest Case Analysis
You are here:
  • Documentation
  • Project Plan
  • 1) Introduction
  • 1.1) Executive Summary

Content

1.1) Executive Summary

  • More
    • Print
    • Table of contents

The order entry process begins with grabbing an incoming order from the intranet system. Once the order is grabbed it is further processed through detailing proofing and eventually AS400 entry. Grabbing being a manual process depends largely on the efficiency and promptness of the operator. Recently it has been observed that the grabbing process efficiency has declined considerably and therefore the revenue has declined noticeably.  After due consideration and initial fact-finding, it has been concluded that competitors seem to be using automated scripts to grab items from the screen. A business decision was taken to develop and deploy a similar automated bot which shall make the grabbing process automated and efficient by mimicking human users to evade any deployed server-side flood/bot control mechanism. The objective of the current process is to design, develop, and deploy such bot processes to meet the aforesaid business objectives.

Loading...