provide a Rough-Order of-Magnitude (ROM) cost estimate for each defined work package and Provide a ROM time estimate for each defined work package for the information provided below

Q a Project Scope Management - Saved v /0 Search Word Activity 9 File Home Insert Layout References Review View Help 9 El Comments A,- Catch up j Editing v (Jose Chm 'iv Elv g TimesNewRo... V12 v A\" AV B I Q ale Aav iv Av gv /v ,Ov l: l; @v f v not: V EU) Description It involves physically installing the EAS tags Teams sensors at designated locations within 99% g Murphy Stores. This includes mounting the % sensors, connecting them to the system, and 5m Edmsuggesm Asslgnme ensuring proper calibration. The output is a fully functional sensor network ready for 3 operation. Calendar ROM ' C0\" ROM - Time Q) Responsible Organization Installation and Deployment team Calls Level 3 D WBS Code 1.3.4 Hes Element Name Surveillance cameras installation Description It involves installing and conguring Q surVeillance cameras at strategic locations Word within Murphy Stores as part of the EAS tags capital project, This includes mounting the cameras, running necessary wiring, and ensuring proper connectivity. The output is a fully functional surveillance camera system integrated with the EAS tags system, ROM - Cost Apps ROM - Time Responsible Organization Installation and Deployment team Level 4 W35 Code 1.2.lrI Element Name Conduct Stakeholder Interviews and Workshops Description It involves engaging with key stakeholders through interviews and workshops to gather insights, requirements, and feedback 7. 7 regarding the EAS system. It seeks to ensure ' a thorough understanding of stakeholder needs and expectations. Completion Criterion: Stakeholder interview and workshop summaries capturing key insights, requirements, and feedback. 6) He'\" Page 5 of8 1,197 words English (U S) Text Predictions On Editor Suggestions Showing l + 80% I], Fit GlVE Feedback to Microsoft Q I'll Activity 9 Chat ' File not: EU) Teams % Asslgnme Calendar % Calls D Files Q Word ADD: 6) Hal\" Page 6 of8 'vag Home Insert Layout /0 Search Word Project Scope Management - Saved v References Times New Ro... v12 v 1,197 words English (U S) Text Predictions On Review View Help AVBI Q ale Aav v Av a wComments \"VCatch up iEditing V Close ,'A/v Work to be Completed 1, Schedule interviews and workshops with key stakeholders. Coordinate and set up meetings with relevant stakeholders, including store managers, security personnel, and IT representatives. 2, Prepare interview and workshop materials. Develop interview questionnaires, workshop agendas, and any other necessary materials to facilitate effective communication and data gathering. 3. Facilitate interviews and workshops to gather requirements. Conduct one-on- one interviews and group workshops to engage stakeholders, discuss their needs, and gather their requirements for the EAS system. ROM - Cost ROM - Time Responsible Organization Murphy Stores Level 4 WBS Code 1.2.12 Element Name Review Existing Documentation and Systems Description It entails collecting and analyzing relevant documentation and existing systems related to the EAS system. Its goal is to evaluate the current state, functionality, and constraints to provide guidance on the design and implementation of the new system. Completion Criterion: Report on document review that highlights results, observations, and emphasizes gaps or opportunities for improvement. ROM - Cost ROM - Time Responsible Organization Murphy Stores Editor Suggestions Showing pvnc l + gm 80% \" [1 Fit 99% f See! ram suggestion Give Feedback to Microsoft Search . . . PS W Project Scope Management - Saved v Search Word Activity File Home Insert Layout References Review View Help MD SY Comments Catch up Editing v 82 Share v Close Chat Times New Ro... v 12 v A I U ab Aav DV Av ... EVE AV Ov : V . . . Level 4 Teams WBS Code 1.2.1. 99% Element Name Document Functional and Non-Functional Requirements See 1 Editor suggestion Assignme... Description The project team documents the functional and non-functional requirements of the EAS system based on stakeholder input and Calendar industry best practices. Functional requirements describe system features and capabilities, while non-functiona Calls requirements focus on performance, security, and other system attributes. Completion Criterion: Requirement specification document outlining clear Files functional and non-functional requirements for the EAS system. WE Work to be Completed 1. Categorize and prioritize Word requirements. Analyze the gathered requirements and categorize them as functional or non-functional. Prioritize . . . requirements based on their importance 2. Define clear and concise requiremen 8 8 statements. Refine the requirements to Apps ensure they are specific, measurable, achievable, relevant, and time-bound (SMART). 3. Document requirement traceability and dependencies. Identify dependencies among requirements to ensure their coherence and consistency. ROM - Cost ROM - Time Responsible Organization Murphy Stores Level 4 WBS Code 1.2.1.4 Element Name Identify Technical or Environmental Constraints Help Page 7 of 8 1,197 words English (U.S.) Text Predictions: On Editor Suggestions: Showing + 80% Fit Give Feedback to MicrosoftSearch . . . PS W Project Scope Management - Saved v Search Word Activity File Home Insert Layout References Review View Help MD SY Comments Catch up Editing 82 Share v Close Chat Times New Ro... v 12 v A B I U ab Aav DV Av ... V Ev Agv Ov : V . . . Teams 99% See 1 Editor suggestion Assignme... Description It involves identifying any technical or environmental constraints that may impact the implementation and operation of the EAS Calendar system. Its goal is to evaluate infrastructure, compatibility, and environmental elements such as store layout and power supply. Calls Completion Criterion: Technical and environmental constraint analysis report emphasizing identified constraints, associated risks, and recommended mitigation Files strategies ROM - Cost WE ROM - Time Word Responsible Organization Murphy Stores . . . Level 4 WBS Code 1.2.1.5 Element Name Validate Requirements with Stakeholders 8 8 Description It focuses on validating the documented Apps requirements with key stakeholders. It entails presenting the requirements for review and comment, addressing any issues, and achieving alignment between the project team and stakeholders on the anticipated capabilities of the system. Completion Criterion: Stakeholder-approved ents document with validation and sign-off. Cost ROM - Time Responsible Organization Murphy Stores Help Page 7 of 8 1,197 words English (U.S.) Text Predictions: On Editor Suggestions: Showing + 80% Fit Give Feedback to Microsoft