Benefit from Our Service: Save 25%Along with the first order offer - 15% discount (with the code "get15off"), you save extra 10% since we provide 300 words/page instead of 275 words/page
Pizza Delivered Quickly (PDQ) is a domestic and remote chain comprising 40 stores of eat-in and residence delivery pizza places. In recent times, PDQ has lost approximately 30 percent of sales income because of a drop in its residence delivery business. This assignment seeks to analyze the situation of PDQ by assessing RBS for the Inventory Management sub-system using the appropriate model. The paper selects the appropriate agile model to address the situation in PDQ situation. There is a need to develop the RBS for the factory location software application and the logistics sub-system development project using INSPIRE approach.
The RBS for the Inventory Management Sub-system Project
The RBS is a hierarchical illustration that depicts what the solution has to solve in order to meet clients needs. In PDQ scenario, home delivery productivity reduced and prompted a loss to the company as a result of competition. To counter the effects of competition, the management has proposed development of subsystems to assist in boosting customers (Project Management Institute, 2013). The subsystem to be used by PDQ will be as the figure below.
Fig 1: RBS for inventory management system
On the basis of subsystem process flow is possible to generate the RBS.
The ranking of models from best fit to worst fit will be from: extreme, adaptive, iterative, incremental and to linear in that order. The rationale for choosing the ranking is based on the client involvement level, in which extreme provides the best while linear provides the worst result.
The subsystem to develop with agile model is Logistics Subsystem, since it involves a lot of uncertainties. The precise agile model is adaptive because it handles a high level of improbabilities in the solutions potential to attain the projected objectives for the project. The advantage of the model is that there must be a process of accountability for the customer to make appropriate decisions to handle requests.
RBS for Factory Location Software Application
1st Subsystem: Pizza Factory Locator
The subsystem involves the existing PDQ delivery and production facilities. It also caters for tertiary, secondary, and primary markets to establish fresh sites for pizza factories. The process has to take into account the influence of a fresh site on the accomplishment criteria.
Function 1.1: Collective sales information and order access to order implementation time using census block
Function 1.2: Compute market infiltration by census block
Function 1.3: Assess home base market region through survey
Function 1.4: Identify prospective pizza-factory sites
Function 1.5: Recognize survey blocks that are not underused
Function 1.6: Evaluate influence on accomplishment criteria of each possible pizza-factory location
Function 1.7: Document pizza factory sites
2nd Subsystem: Order Entry
This subsystem manages customer requests. A client places an order into the system. It is possible through the use of mobile or telephone, online, or store visit.
Function 2.1: Recognize client
Function 2.1.1: Name, address, etc.
Feature 2.1.2: Customer history
Function 2.2: Acquire order
Feature 2.2.1: Requested products
Feature 2.2.2: Options selected
Feature 2.2.3: Quantity ordered
Feature 2.2.4: Condition either baked or unbaked
Feature 2.2.5: Document order history
Function 2.3: Obtain delivery instructions
Feature 2.3.1: Delivery residence
Feature 2.3.2: Delivery options
Feature 2.3.2: Delivery timeframe
Function 2.4: Cost (Price) order
Feature 2.4.1: Use promotions
Feature 2.4.2: Compute price
Feature 2.4.3: Sustain pricing chart
Function 2.5: Verify order
Feature 2.5.1: Payment mode
Feature 2.5.2: Exhibit order
Feature 2.5.3: Option: Accept, Cancel or Change
Function 2.6: Submit order information to subsequent subsystem (Logistics Subsystem)
Feature 2.6.1: Order submission
Feature 2.6.2: Verify order receipt
3rd Subsystem: Logistics
The subsystem constantly checks workloads across the entire preparation sites and all delivery options. Based on existing portfolio, the system makes a decision where to organize the pizza and which van will transport the order.
Function 3.1: Select preparation site
Feature 3.1.1: Obtain preparation-site workload
Feature 3.1.2: Obtain next-order information
Feature 3.1.3: Approximate production and delivery time
Feature 3.1.4: Allocate preparation site
Function 3.2: Move order to preparation site
Feature 3.2.1: Submit order
Feature 3.2.2: Document preparation site portfolio
Function 3.3: Select delivery van
Feature 3.3.1: Approximate distance
Feature 3.3.2: Estimate time for pick-up and delivery
4th Subsystem: Order Submission
Regarding output obtainable from the Logistics Subsystem, the preparation site gets the order for scheduling.
Function 4.1: Accept order feature from Logistics Subsystem
Function 4.2: Arrange order for preparation
Feature 4.2.1; Prioritize fresh order
Feature 4.2.2: Access preparation queue
Function 4.3: Verify order condition
Feature 4.3.1: Assess the time the order will be ready
Feature 4.3.2: Assess the time the order will be delivered
Feature 4.3.3: Advice the driver of delivery van concerning pick-up time
Feature 4.3.4: Notify the driver when the order is complete
Feature 4.3.5: Document Inventory Management Subsystem appropriately
Function 4.4: Calendar order delivery and pick-up
Feature 4.4.1: Get confirmation from the delivery van driver concerning pick-up time
Feature 4.4.2: Acquire route of location from Routing Subsystem
Feature 4.4.3: Verify order delivery
Feature 4.4.4: Verify payment receipt
Feature 4.4.5: Record delivery-van destination and time
5th Subsystem: Routing
The subsystem provides the driver with destination from the preparation site to the client location. It is accompanied by a COTS submission for this subsystem.
Function 5.1: Update delivery-van destination
Function 5.2: Upload client delivery contact details
Function 5.3: Download driving instructions
Function 5.4: Verify order delivery
6th Subsystem: Inventory Management
The subsystem checks real-time inventory stages at all preparation sites, automatically provides refill directives to the trucks to refill preparation-site inventories, and automatically re-orders record from the seller.
Function 6.1: Obtain inventory-use information
Feature 6.1.1: Gather inventory-reduction data by preparation site
Feature 6.1.2: Keep posted on-hand inventory by commodity
Function 6.2: Recognize reorder requirements
Feature 6.2.1: Send reorder routinely to seller
Feature 6.2.2: Notify each preparation site of reorder amount and time for every product
Function 6.3: Obtain reorder
Feature 6.3.1: Examine and accept reorder consignment
Feature 6.3.2: Parcel orders for every preparation site
Feature 6.3.3: Transport orders to each preparation site
Logistics Subsystem Development Project
This subsystem will use INSPIRE to execute project mandates. INSPIRE is an interactive approach that iterates an unspecified number of stages in search of the goal. The question to ask here is whether there is a clear delineation of roles between the client and the team and whether there is a well defined process calendar with responsibility timelines (Carroll, 2012).
Revised Project Overview Statement (POS): It is essential for a project manager to have a clear understanding of the setting or organization methodology required prior to commencing the project. There are external and internal factors concerning each project that may assist to clarify what PMLC model would be best appropriate for the planned project.
The paper has provided a clear project process for PDQ to implement and gain market share. The RBS generated are hierarchical procedures that give a breakdown of what the project entails and solutions relevant. PMLC models are assessed and extreme found to be best fit since it is the most clients involving model. The project is to attract more home delivery clients and it entails more interactive approach to the clients to know their decisions. The INSPIRE usage in logistics subsystem prompts the management question that leads to reassessment of POS perception. It leads to revision of POS to reflect the revised POS.