1. PROJECT SCOPE

[Instructions for what to include in this section: Define the scope of work that will be undertaken to provide the deliverable(s) mentioned in the Project Charter (PC). Craft this section carefully, as you should use the same content for this QMP, Communications Plan (CP), and the Risk Management Plan (RMP). This approach is normal in the industry.

Remember, this should not be a long section (about one to one and a half pages of text). If you also decide to include a diagram of the technical architecture, make sure that you build this in PowerPoint and import the graphic into Word (do not just copy and paste the one provided in the unit materials). Additionally, don't forget to provide a figure number and introduce the diagram in the lead-in text (which should also refer to the figure number).

The key to writing a Project Scope well is to give the reader a general understanding of the project, so they can then put the information within this document into context. The following structure is recommended as it will help to ensure that there is a clear flow within this section:

1. Begin by providing an overview of the deliverables (what will be provided). Within this first paragraph also explain the ethos of for the solution. For example, think about what we want to get from the project by providing what our clients will want. Think about this in terms of the key points you developed in Section 2.1 of the Project Charter. Keep this short and focussed. One paragraph is usually enough.
2. In the following paragraph provide an overview of that explains how the project will be delivered.This should be a short and clear description of the overall approach to delivery (e.g. implementing the pilots, phasing, etc.). Remember the key is to ensure that a novice who knows nothing about the project will understand how you intend to achieve this objective. When defining this aspect, ensure that you are also explaining how this approach will help to reduce risks. Once again, keep this to one paragraph if possible.
3. From the third paragraph, this is where your focus changes to explain the Scope of Work. If you are going to add in an architecture diagram, this is where it would be placed. This way it gives an overview of the architecture, and you will describe the elements below the graphic. If you have decided not to use a graphic, just use an introductory paragraph that leads into the more detailed scope of work as outlined in the following points. Describe the key points that explain the scope of work required to supply the project deliverables. For instance, you would include statements like:
   1. To implement the EduStream system, we are going to develop three pilot nodes (one in Perth, one in Sydney, and one in Melbourne).
   2. Each of these nodes will comprise... - Cover the elements in the EduStream Technical Architecture Overview material as a very short synopsis (e.g. Web server, Client Database, OCA/Video Streaming device/s, Games Server/s, System Health Management, etc.) to describe what will be delivered.
4. Separate the elements within the Scope of Work using Scan Point bullets. This should cover every aspect of the solution, including the client application, CDN Nodes, Colo Datacentres, Security and Customer Support.For each of these elements provide enough information so that a reader who knows nothing about the project can understand what is being provided and some of the key issues that will need to be addressed to deliver the solution effectively (e.g. enough about the technical issues so that a reader can understand what is important).
5. It is generally a good idea to provide a last paragraph that lists the date for the transition from the project to the full operational environment (e.g. the full market opening). This ensures that your reader can understand the timing issues more effectively.

ICT201 Assignment 2 Information Sheet BACKGROUND The Board of EdMedia International Pty Ltd (EdMI) approved your Project Charter and Project Management Plan. The Planning and Execution phases have therefore been funded for implementation. The timeline for the project milestones has been agreed. You have completed the tender evaluation process and engaged the following contractors and other entities within the project team: StreamTech (ST) demonstrated in their tender response that they had significant capabilities to develop and implement the video streaming and games server solution. Additionally, they indicated that they have the resources necessary to implement this successfully. Their project team is headed by Roy Clark (Project Manager - ST). ST has been contracted to provide the following Scope of Work (SOW): + OCA and Games Servers. ST will implement all aspects of the Open Connect Appliances (OCA) and Games Servers for each of the Content Delivery Network (CDN) nodes. Please note that EAMI will be procuring the hardware, as discussed below. ST will build the associated systems that will allow the hardware to achieve the objectives. ST has indicated that they can complete the baseline developments within three months, once the hardware is made available to them. Client Software. ST will be developing the client software, so it is compatible with PCs (backwards compatible to Windows 7), Apple, Android, and Smart TV hardware. This will require a complete code development. StreamTech is planning to utilise an Agile development process to try to meet the deadline. Their design is currently not complete, but ST has demonstrated in their tender response that they have been able to successfully develop and implement similar client products. Media File Conversion. They will be responsible for the conversion of existing media files into compatible FLV/MP4 formats and uploading these into the OCA systems. ST has said that they have an automated system to do this already, so they believe this to be low risk. Streaming Technologies. ST will integrate appropriate codecs and an H.265 (HEVC)/RTSP solution for both the client and server infrastructure. This will require substantial analysis and development. Batch Update. They will be responsible for implementing the batch update systems for distribution of the OCA and Games Server content between the nodes. This will utilise a COTS capability, which StreamTech has identified as being low risk. At this stage, they are planning to be ready to test the baseline solution as a part of System Test. System Health and Load Sharing. The ST solution involves utilising a tailored version of a COTS product. To provide this, StreamTech has engaged the owner of this software as a subcontractor. This company is called PH and it is a very large multinational organisation. However, at this stage, EdMI has not seen a copy of the subcontract. The large multinational company has indicated that the system modifications for their package should be implemented but are currently unwilling to provide progress reports during the development cycle. Once the system is supplied, the COTS package will be 'black box', and the large multinational company will own all of the associated Intellectual Property. Future Video/Game Uploads. ST will implement a system that will allow EdMI to convert (as necessary) and upload new content readily into the OCA and Games Servers. This is already available and has been demonstrated by ST, but it is untested with this type of environment. DemSet has already engaged its team, which is being Project Managed by Pardeep Kaur. This DemSet team is responsible for developing and implementing the: Web-Front-End. The web-front-end will be developed using PHP and will use calls to some functions that have already been created by DemSet. DemSet has indicated that the required solution will, therefore, be able to reuse about 30% of their existing code base. They have agreed that EAMI will own all of the code base and Intellectual Property for the web-front-end as a result of this Murdoch University Page 2 ICT201 Assignment 2 Information Sheet project, so it can be readily maintained by other contractors as necessary. They currently expect that they would finish the development of the web-front-end on time, so it will be ready for System Testing. + Client Database. DemSet has proposed modifying an existing Oracle Database solution that they have already created. Their proposed solution will deliver a secure client database system that will interface with the web-front-end, the OCA system, and the Games Server. DemSet believe this system will be ready for System Testing. No pricing has been provided for Oracle license costs at this stage. + Database Replication/DR, etc. DemSet is responsible for delivering the database replication, failover and Disaster Recovery (DR) systems for the client database. It is intended that the replication system will leverage standard Oracle protocols. + Security. DemSet will be responsible for developing a standard set of security protocols and systems that will be implemented and monitored across the entire system. Consequently, DemSet will cover all aspects including application (including client, streaming, OCA, web-front-end, and games), firewall, router, network, database, replication, etc. They are aiming to have their security plan available for distribution to StreamTech and other stakeholders as scheduled. . DCPlus is a nationwide shared Colocation (CoLo) datacentre supplier with a good reputation. The Client Manager at DCPlus is Catherine Dobbs. DCPlus have been engaged to provide Tier 3 quality services for the support of each of the nodes (see this web page for a simple synopsis of Tier 3: https://www.colocationamerica.com/data-center/tier-standards-overview.htm). This support will include: + DC Systems and Services. This will include the provision of high redundancy monitored and secure systems within their datacentres. Originally, the plan is just to utilise one rack within a secure data room. + Network Connectivity. DCPlus will coordinate the provision of as much network bandwidth as EdMI needs. They assess the risks associated with this as low because they already have significant fibre 'pipes' with high levels of redundancy in place, and firm service agreements with all of the large telcos. This should mean that future expansion of EduStream will be able to be supported effectively with network connectivity. + DataCentre Management System (DCMS). DCPlus has included utilisation of their integrated DCMS as a part of the CoLo support package. This will facilitate our access to, and control of, pertinent parts of their DataCentre Infrastructure Management (DCIM) system (see https://searchconvergedinfrastructure.techtarget.com/definition/data-center-infrastructure- management-DCIM for more information on DCIM). DCIM can, therefore, be conducted in parallel with the System Health Management (SHM) functionality. To implement this system, EdMI will need to procure and set to work hardware that will run the DCMS application in an operations room at our Perth facility. The entire system will need to be set to work prior to the Pilot 1 (Perth) system going live. . MBSD is an India-based Service Centre. Their Implementation Manager is Mr Rajiv Singh. MBSD has been engaged to begin providing Level 1 services from the Perth go-live date for the Beta. These services will include: + Level 1 Support. They will provide Level 1 support for government/corporate/educational institutions as a part of a service management system. You can find out more about the levels of support on this web page: https://en.wikipedia.org/wiki/Technical support . Level 1 support will be coordinated through an ITIL compliant Service Desk Management System (SDMS) that will need to be populated with information that is to be provided by EdMI. + Escalation. Where a problem cannot be resolved through the Service Centre Level 1 support, it will be escalated back to EdMI. Murdoch University Page 3 ICT201 Assignment 2 Information Sheet . JP-Media has been engaged to develop the mass marketing strategy for EduStream. The JP-Media Client Support Manager (CSM) is Dan Hill. He and his team will be working on a strategy for implementing EduStream sales to the mass market with Kate Lundy (EdMI's Marketing Manager). However, the EdMI project team will need to educate JP-Media and our own Marketing Department on the EduStream product and its capabilities. JP-Media have indicated that they will also want to have input on the design of the user interfaces because they have significant expertise in making user-friendly interactions that will assist in the development of broad market buy-in. Within this contractual engagement EAMI is responsible for the following: You will be responsible to the Project Sponsor, CEO and Board for overall project management, and reporting. . EdMI will coordinate procurement of the OCA, servers and all other hardware (e.g., routers, firewalls, etc.) for the operational environment. Please note that these will be required earlier than system deployment into the node, to allow the contractors to utilise them in their Development/Test Environments and to ensure that they are available for unit, integration, and system testing. Our team will coordinate all legal documents as the prime, including the development of the End User License Agreement. This will be managed by Bill Sykes (the EAMI Lawyer) . We have engaged Don Lemon (an EAMI consultant) to monitor the security system implementation and ensure that the solution will meet the required standards (including those in the Privacy Act). * EdMI will coordinate the provision of the information that will be loaded into the Service Desk Management System, for Level 1 support (Knowledge Base/procedural support system decision tree information, etc.). This will entail drawing information from each of the contractors and developing a step-by-step analysis system. . Integration of all system documentation within a Knowledge Base/Wiki, so EAMI and the contractors can consolidate system information. This system will be used to facilitate Configuration Management and Level 2/3 service support. . Develop and maintain the web site for the FAQ materials that will provide help to non-institutional users. . Implement the Level 2 and Level 3 support systems to deliver services to institutional/educational organisation clients. It is not expected that this will include Field Services (e.g., by our current assessment there should be no need to have someone go out to a client site). Finally, to facilitate beta/acceptance testing, the EdMI marketing team has engaged a total of 22 organisations, who are currently using EAMI's videos and games software. These organisations include seven large primary and secondary schools in each of the cities proposed for the nodes (e.g., Perth, Sydney and Melbourne). Additionally, the National Indigenous Australians Agency (NIAA) (which is coordinated from Canberra) has asked to link into the pilot project, to trial deployment of the educational videos and games to three remote indigenous communities (one in Western Australia, one in New South Wales and one in the Northern Territory). PROJECT MANAGEMENT DELIVERABLES To complete Assignment 2 you will be required to complete the following documentation (each of these templates is provided within the LMS under Assignment 2 Information and Materials): . EVM Cost Analysis. The information provided in the associated EVM-CostAnalysis.docx has been received as a part of the project reporting. You must complete the analysis and fill in the report elements that are required in that document. . Quality Management Plan (QMP). You will be required to develop a Quality Management Plan using the QMP.docx file provided in the LMS. Murdoch University Page 4 ICT201 Assignment 2 Information Sheet . Stakeholder & HR Management. Your team are to develop a Communications Plan (CP) using the CP.docx template supplied in the LMS. Your team's response must address the diverse communications 1ssues that will confront this project. . Risk Management Plan (RMP). As illustrated within the scenario information provided above, there are a range of implicit and explicit risks associated with this project. Your team will need to develop a Risk Management Plan that will explain how you will manage these risks. . Project Closure Review (PCR). The last deliverable will be a Project Closure Review for Assignment 2. Each member of your team will need to complete this individually and upload it with the other documents. This review must be provided as discussed in the PCR template (the PCR.docx file). Use file names which follow this convention. For the team documents: Unit Code-Assignment Number-the first five characters of your group name, the Student Number of the Project Manager-the file identifier. For instance, files uploaded by the 'Super' group, whose Project Manager has a student ID of 12345678 would be named as follows: EVM Cost Analysis. ICT201-2-Super-12345678-EVM-CostAnalysis.docx Quality Management Plan (OMP). ICT201-2-Super-12345678-QMP.docx Communications Plan (CP). ICT201-2-Super-12345678-CP.docx Risk Management Plan (RMP). ICT201-2-Super-123456788-RMP.docx For the PCR, use the following convention: Unit Code-Assignment Number-the first five characters of your name-your Student Number-the file identifier. For example, if your name was Ramandeep Kaur and your student number was 12345678, you would name your files as follows: . Project Closure Review (PCR). ICT201-2-Raman-12345678-PCR.pdf FOR MORE INFORMATION We will be covering these issues in the workshops. Therefore, it will be important for everyone to attend the associated topic workshops. The lecturer will also be available to answer questions. You can, of course, ask such questions during the workshops you will be attending, or you can send an email to your lecturer. We will get back to you with an answer as soon as it is practicable. Please note, that it is recommended you get your questions in early. If you ask questions late in the assignment development cycle, you may not receive the answer in time. ASSIGNMENT MARKING The assignment will be assessed as though it was a set of documents forwarded for review by the CIO (the Project Sponsor). Consequently, you will need to ensure that your materials reflect a high professional standard (Remember in the real world, your job can depend on this). The marks allocated for the Assignment will be allotted in terms of the percentages shown in the following table. Overall % of the Maximum Scores total mark for this allocated per attribute | document Content | Clarity & Logic EVM Cost Analysis 10% 8% | 2% ~Quality Management Plan 30% 25% 5% Communications Plan ' 30% 25% 5% Risk Management Plan 25% 20% 5% _Project Closure Review i 5% 4% 1% Murdoch University Page 5 ICT201 Assignment 2 Information Sheet The second column in this table shows the total percentage of the allotted marks for each required document. You will note that these add up to 100%. Within this allocation, the marks will be assigned in terms of the following: Content. The largest part of the score allocated to each document relates to the content that is provided. As a general rule, if your response covers all of the aspects explicitly provided in the assignment documentation and workshop discussions, you will get a score that equates to 60% of the maximum content mark. If you have not included pertinent information in your solutions, you will get a lower mark. Higher marks will be allocated where it is clear that you have gone beyond the information provided and thought about the real-world implications when developing your content. Clarity and Logic. In this real-world scenario, you are writing the documents to go to a Board. These people are not technologists and want to understand the logic through your clear communication of the issues. Therefore, you will need to deliver the documents in a manner that is logical, readily understandable and well written. Where you write the documents well and make it easy for the Board to understand, additional marks will be allocated. These will equate to a maximum, as shown in the right-hand column of the preceding table. Murdoch University Page 6 EduStream Timeline Overview Board Submission Formal Start Engage Contractors WS1 - Management Initiation RFT Process & Legals Management (Legals, Administration, Documentation, Finances, Meetings, Reports) 1/4/24 29/4/24 24/6/24 Finalise Tech Design Sys Test Go Live Complete AT WS2 - Client Software Preliminary Development/Design Design/Prototype/Test Develop & Test rocure/Tes Rectify AT 17/1/25 30/8/24 11/11/24 6/12/24 Finalise Tech Design Sys Test Go Live Complete AT WS3 - Pilot 1 (Perth) Preliminary Development/Design Design/Prototype/Test Develop & Test Procure & Test STW AT 17/1/25 30/8/24 11/11/24 6/12/24 Sys Test Go Live Complete AT WS4 - Pilot 2 (Sydney) Rectify Procure & Test STWAT 22/1/25 21/2/25 14/3/25 Full Market Sys Test Go Live Opening WS5 - Pilot 3 (Melbourne) Rectify & Test Rectify Procure & Test Rectify STWAT 16/5/25 24/3/25 2/5/25 Service Desk Contract Signature Go Live WS6 - Service Desk Identify Requir ments Develop SDMS Materials SDMS Updates & Rectifications Investigate SD Options 10 Best SD Negotiations STW 4 Deliver SD Support 9/9/24 22/11/24 Go Live WS7 - Level 2/3 Support Develop the Knowledge Base Provide Level 2/3 Support Services Transition to Engage Level 2/3 Support Staff Train Support Staff Develop/Evolve the Knowledge Base Operations 6/12/24 16/5/25 Datacentre Contract Signature Beta 1 Go Live Beta 2 Go Live Beta 3 Go Live WS8 - Datacentres Identify Requirements Develop DC Cookie Cutter Design & Implementation Plan Manage and Maintain DC Systems Transition to Investigate DC Options Negotiations P&T STW DCMS & DC STW STWO Operations 27/9/24 6/12/24 21/2/25 2/5/25 16/5/25 Media available for testing WS9 - Procure/Prep Media Rationalise Existing Media Identify Target Markets Engage & Negotiate with Media Providers Convert media as necessary (update builds as required) Transition to Identify Additional Media Requirements Convert media as necessary Operations 16/9/24 16/5/25 WS10 - Training Develop Training Material Update Training Material & Train Stakeholders Transition to rain Marketing Operations 16/5/25 Commence Marketing WS11 - Marketing Develop Marketing Material Explain new product to existing clients & Seek Beta Participation Transition to Explain new product to new clients & Seek Beta Participation Operations 9/9/24 16/5/25 Formal WS12 - Closure Pilot 13/6/25 Close FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC JAN FEB MAR APR MAY JUN 2024 2024 2024 2024 2024 2024 2024 2024 2024 2024 2024 2025 2025 2025 2025 2025 2025 Development & testing A/R COLOUR KEY Management System Testing General Activities Design (Prototype A/R) Procure & Testing A/R Acceptance Testing Set to WorkEduStream Technical Architecture ICT201 - Information Technology Project Management Overview of the EduStream Technical Architecture This document provides a simplified description of the technical architecture developed for the EduStream system. This architecture is illustrated in Figure 1. CLIENTS w Redundancy & Load Sharing s | Client Application (CODEC & send requests & control) Redundancy & Load Sharing DATA CENTRE _ casssso Fibre: TCP/IP (RTSP RTP VIDEQ/AUDIO: HTTP/FTP: GAMES) H.265/HEVC FLV/MP4/ETC Load Sharing Batch Updates & DB Replication A i 'OPEN CONNECT APPLIANCE u. OR STREAMING SEr Infg SERVER | CLIENT DB pass-Through DATA CENTRE GAMES SERVER WEB SERVERS System Health Management Figure 1: EduStream Simplified Technical Architecture As shown in this diagram, there is a requirement for the development of a client application (shown in the blue box), and the creation of three Pilot Content Delivery Network (CDN) nodes (shown as the yellow boxes). As explained in the Assignment 1 Information Sheet, these Pilot nodes will be located in Perth, Sydney and Melbourne. The key elements of the architecture that you need to consider are: CDN Nodes Each of these nodes will be positioned in a Tier 3 co-located (Colo) Datacentre (see this web page for a simple synopsis of Tier 3: https://www.colocationamerica.com/data-center/tier-standards- overview.htm). All of the equipment shown would be standard 19 inch (482.6 mm) rack-mounted units. The systems required in each node will be: a. Web Servers. The web servers will form the front-end of the system, which will be accessible to the clients. These will require a friendly and intuitive user application, so the people using the system can find and download their game or video easily. Additionally, the web servers will require appropriate hardware. For the web server system to run effectively, it will need to be able to interface with the Client Database (DB) system, and also draw directly from the OCA and games server catalogues, so they can show what content (videos/games) is available. Client Database (DB). The Client DB will store the users' information. This should include data like their names, age (so their access to content can be defined), addresses, billing information, credit card details (so their monthly fees can be debited automatically), type of license, client equipment/environment information, what content they have watched (so recommendations on viewing content can be presented through the web For use with Assignments 1 and 2 Page 1 EduStream Technical Architecture server), and what games they have tokens to play (so they cannot play games if they do not have the appropriate software tokens). The development of this system will require: L. ii. iii. iv. rack-mounted hardware with low latency high volume data access capabilities (it will need to be quick, to allow the system to work well under load); a database environment (in this case it is proposed to be Oracle), which will need to be procured, as license fees are necessary for this application (additionally, we will need to determine exactly what elements of this environment we actually require, as this will make a big difference to pricing); once the database system has been procured, we will need to develop the underlying table structures, and supporting software for control, management and replication of the data; and as this database contains important private information, significant security controls will also be required (including table / cell level encryption as discussed below). c: Open Connect Appliance (OCA). As illustrated in the recommended videos (links for these are provided within the Assignment 1 Information Sheet), the OCA is a video streaming server. This will require: L. . iil. iv. A hardware system that can store the video that will be available through the EduStream system. In practical terms, this will be a specialised type of rack- mounted server, which has been developed by Netflix. It is possible that they may provide this to us at low cost, but we would need to negotiate this with them. Software may need to be tailored/developed so this system can stream our multitude of videos effectively. Remember that this software will need to include a CODEC, RTSP control interfaces, and apply a data compression engine (in this case we are aiming to use HEVC/H.265). Video conversion will need to be conducted on some existing videos, so they are all in MP4 or Flash Video (FLV) format. This will be important, as it will allow the HEVC compression to work optimally. The conversion is not a small task, so it would need to be built into your WBS. An interface will be required between the OCA and Client Database, which is shown in Figure 1. Additionally, it will be important to create a direct interface to the web servers from the OCA, to make it easier to show the latest content that is available (this is not explicitly shown in the diagram, but this is inferred) d. Games Server. The Games Server will be a streaming engine for the available educational games. To implement this system the following will be required: i. ii. iii. Rack-mounted server hardware will be necessary. Software will need to be developed to coordinate the distribution and management of the games within the inventory. An interface will be required between the Games Server and the Client Database, (which is shown in Figure 1). This interface will check the tokens'" stored within 1. A token in this context is an encrypted number that must be found by the software so it can be run. A range of different approaches can be used to implement this, and for the purpose of this For use with Assignments 1 and 2 Page 2 EduStream Technical Architecture the Client DB for that user, with the ones listed against specific software. These will be used in the client software, to determine whether the game can be played or not (e.g. if they have not paid their membership fee, or do not have the rights, they will not be able to access the game even if it is downloaded to their client). iv. Existing and new games will need to be modified appropriately, so they apply a token, which means that the client cannot play the game if the user's monthly fees have not been paid or they do not have the appropriate access. This could be a fairly complex task depending on the inventory of games currently held and whether they are black-box, grey-box, or white-box (e.g. how much access do we have to the underlying code). e. System Health Management. System Health Management requires hardware and a tailored application to monitor activity within the CDN nodes. For example, it should monitor aspects such as network utilisation, disk access loads, server CPU loads, etc. This element will be essential to allow load sharing to be implemented (see the Netflix description video recommended in the Assignment 1 Information Sheet). Client Application The client refers to a downloadable application that will be able to run on Android/Apple (Phones, Tablets, etc.), Apple/PC hardware, smart TVs, or TVs using standard network access boxes. As there will be a range of operating systems, we will need to develop different versions of the App that will run in these environments. Therefore, although we will not be providing the user hardware, we will need to provide the different types of hardware/environments that will be used by clients within our Test Environment (so we can test the systems properly). Additionally, this client software will need to have the RTSP control interfaces, CODECs and a thin-client application that interacts with the appropriate web server. Please note that when load sharing occurs (see below), the client may need to point seamlessly toward another node Web Server/OCA (without the user knowing about the shift it should be transparent). Network For this system to run effectively, it will need access to consistent high-volume network connections. These connections will need to support TCP-IP, which will be used to implement the interconnectivity between clients and CDN nodes. Typically, these will be available within a Colo datacentre. This is particularly true if we are using a Tier 3 Datacentre, as these have to provide multiple/redundant network connections to achieve this rating. Security This system will need to be secure. In practice, this would apply a Defence-in-Depth approach that will include physical security (unauthorised people cannot gain physical access to the servers/OCAs in the Datacentres), wide area network security (WAN secure network connectivity is secure), local area network security (LAN connection between the node elements); application security (for the client, web server, Client DB, Games Server, OCA, System Health Management, etc.), Database (table/cell level controls/encryption), etc. The key is that this needs to be fundamentally built into the design. Therefore, it will require hardware (e.g. firewalls, although you will also use the Datacentre firewalls), software (e.g. virus management software), application protections (built-in during development) and database controls (to protect user data). assignment the actual solution to be applied will not be pertinent. Therefore, just refer to this in your materials, and only go deeper if you really want to learn more for yourself. For use with Assignments 1 and 2 Page 3 EduStream Technical Architecture These are the elements that will need to be implemented for the Pilot 1 solution. This Pilot will be introduced in Perth. The Pilot system will then be tested extensively to find any bugs and other problems (which will invariably be there). Consequently, there will be an extensive testing program implemented prior to deploying the second Pilot Site. In parallel with this activity, the following capabilities will be implemented, and then tested extensively once the second Pilot site also is set to work: (1 (2 (3) Load Sharing. This system will leverage the System Health Management (SHM) capability. When components are under pressure (e.g. they are being used a lot), the SHM will find another node within the network that is under lower load (e.g. will provide less latency/delays to the client). The client will then be pointed to another node to load balance across the entire system. Batch Updates. The ideais that all of the nodes will have the same content all the time. However, shifting large games and video files will use up bandwidth, which could then reduce the users' ability to access the content. Therefore, batch updates are typically done during periods of low utilisation. A system will need to be developed to manage this. DB Replication. 1t will be essential that the data held in the Client Databases is the same in all nodes. Consequently, a technique known as replication is used. Once data is changed in one database, this replicates into the databases in the other nodes. Systems like Oracle provide quite a powerful replication system with relatively little development/tailoring required. Once the final CDN node is implemented, a range of tests will be needed to ensure that the multi-node architecture will work. This broad approach is known as creating 'cookie-cutter' solutions. In practice, it means that once all the bugs/problems are fixed, EAMI can simply deploy the same mix of software/hardware systems into new nodes (e.g. other appropriate Datacentres) as necessary to expand the system. For use with Assignments 1 and 2 Page 4 As a first step, you will need to deliver key project initiation and planning materials to the Board by 9:00 AM on Monday 1 April 2024. These materials must deliver clarity regarding the business case and outline how the project can be implemented successfully (once it is approved). THE PROJECT The objectives of the project The aim of this project is to create a stable, effective and user-friendly streaming solution, which will allow educational training videos and games to be deployed over the internet. For this Pilot Project, the Board has decided to begin by deploying Content Delivery Network (CDN) nodes in Perth, Sydney and Melbourne. The pilot sites should be delivered in the same order as discussed in the previous sentence. In addition to the streaming systems, you will need to implement a range of other elements. A preliminary technical architecture has been developed for this system. This architecture and some descriptions of key system elements are available through the LMS under the Assessment heading. The file is called 'EduStream Technical Architecture Overview'. You will need to ensure that you understand this architecture. Key issues to be addressed To implement this project, the following important issues will need to be addressed: e The Board is still not convinced that this will be a viable solution. The materials that you provide in this Assignment will, therefore, have to be detailed and convincing, or you may find yourself out of a job. You are not an expert in video streaming technologies, and there is no expertise related to these technologies within the company. Additionally, EAMI's knowledge of establishing large scale web-front-ends and databases is minimal. Consequently, you will need to engage one or more experienced contractor, who can coordinate/implement this solution under our control. This identification and selection of contractors will be a high priority for your efforts. When conducting this selection process, it is recommended that you implement a weighted analysis approach as a part of a Request for Tender (RFT) preparation process. This weighted analysis approach will be discussed during the Topic 2 Workshop. e EdMI is not a dedicated technology company. Consequently, setting up 'green-fields' (all new) data centres and systems is beyond our core business. For this reason, outsourcing will be important. Consequently, you will need to identify appropriate Data Centres in each of the pilot cities, and a Call Centre that you can use to provide support. You may also want to think about aspects such as leasing of equipment to help minimise up-front costs. e Atthe end of the project, we will need to ensure that EAMI can maintain and manage the EduStream system that is created. This may mean that we need to bring skills and Intellectual Property (IP) into the company or set up reliable relationships with other organisations, who can do this for us. Key Milestones You will need to achieve the following key milestones, to meet the Board's defined requirements. Please note that these only reflect some of the pertinent high-level objectives. You will need to work out other key milestones involved in this approach. The subordinate milestones that you select must allow the following to be achieved. Page 2 of 7 m Event/Milestone 26 Feb 2024 Preparations Commence. You will begin developing informal team relationships (e.g. start talking to possible contractors and internal stakeholders) and complete the development of the materials required by the Board (your assignment). These discussions can be represented by asking questions of the lecturer (e.g. during the Workshops). Submission to the Board. Submit the required project materials to the Board, so they can make a decision on whether to proceed with the project or not. Planned formal project Start Date. This milestone will trigger formal allocation of project funds from this date, and it will only be initiated if the Board approves your submission. Until this is authorised, other members of staff and contractors cannot be engaged formally on a paid basis. In practical terms, this means that you have to do the initial work on your own, but you can ask questions during the Workshops, which you can consider as team meetings. Engage Contractors. By this date, you need to contractually engage one or more technical contractor to conduct the development work. This activity will require an RFT process. The key steps in this process are outlined in the following cell. Additionally, you will need to engage other contractors to provide Data Centre and Service Desk facilities (an RFT may not be necessary for these). 1 April 2024 29 April 2024 24 June 2024 Project definition and scoping (identify our requirements and the priorities that will Tender Preparation (We prepare the documents that contain questions and key information, which defines what we want from other organisations.) Tender Period (Other organisations answer our questions by explaining their experience, what they can do to meet our needs, and what it would cost.) Tender Evaluation (Our team evaluates the tender responses that are received and determines the most appropriate organisation/s to deliver our needs.) Contract Negotiations & Signature (From the previous step, one or more Preferred Tenderer/s will be selected. We will then do final negotiations with them and once all parties have be used in the weighted analysis); Identify appropriate tenderers (so we can go out to market with the RFT); Develop the tender documentation and draft contracts; and Send out the RFT, so appropriate organisations can respond. Responding organisations answer the questions/points in the RFT (this includes explaining their expertise and providing specific solutions to the needs identified in the RFT); Responding organisations will develop pricing for delivering their proposed solutions; During the tender period the organisation that prepared the tender may answer questions from responding organisations and provide amendments as necessary (to clarify points); and Prior to the closing date/time the responding organisations will provide their RFT responses. The responses are typically short listed to ensure that there are only a few analysed in detail (this is greatly simplified if you only sent the tender to a few contractors); A detailed analysis will be used to determine a total score for proposed deliverables; Each tenderer's total score will be assessed in relation to cost, to determine a Value for Money outcome; and The organisation/s that score best in terms of the Value for Money outcomes will be nominated as Preferred Tenderer (one or more as required). A detailed negotiation will be conducted, which allows the organisation developing the tender and Preferred Tenderer/s to reach a common understanding and agreement on the issues related to the tendered services/systems; and Once the agreement is reached, the contractor and the organisation developing the tender will sign the contract and this initiates the formal agreement. reached an agreement the contract/s will be signed.) 30 August 2024 Finalise the Technical/System Architecture/Design. The EdMI staff and engaged contractors will need to complete the technical design prior to this date, so the developments can be completed prior to the Pilot 1 go-live date. Commence Marketing. The following period will be used to build the client base, so we can get them to participate in the Beta/Acceptance Testing. Prior to sending out the sales personnel, they will need to be trained, so they will understand the new EduStream system. Obviously, we can't do the training for the sales team unless we have completed the design, so they will know what EduStream does and how it will work. Beta goes-live for the first Pilot CDN node (Perth). Once the system is set-to-work, detailed Beta/Acceptance testing will be conducted. Problems identified through the 9 Sept 2024 6 Dec 2024 Page 3 of 7 21 Feb 2025 2 May 2025 16 May 2025 13 June 2025 Your Team Apart from you testing will need to be rectified prior to the go-live date for the second Pilot CDN node. Any changes initiated as a result of problem resolution must also be uploaded to the Perth node prior to the go-live date for the Sydney node. Beta goes-live on second Pilot CDN node (Sydney). Once this node is set-to-work, multi-site Beta/Acceptance testing will be initiated. These tests will focus on aspects such as replication and load sharing across sites and will also provide Acceptance Testing for rectifications initiated after identifying problems in the Perth node tests. Rectifications and updates for the builds at both the Perth and Sydney nodes will need to be completed prior to the Melbourne go-live date. Beta goes-live for the third Pilot CDN node (Melbourne). After this node is set-to- work, full multi-node Acceptance Testing will be commenced. Any problems identified through this testing must be rectified and the builds for all three sites must be updated and retested. Once this is done, an additional round of load tests must be undertaken. These steps must be completed prior to the Full Market Opening. Full Market Opening. This is the date that is set as the full market opening. The Board have identified this as a hard-wall milestone (e.g. it cannot be moved), because it is designed to coincide with EAMI's anniversary of establishment. Prior to this date, there will be a full one-month media blitz to gain mass-market buy-in. To avoid any possible embarrassment after opening, the entire system must be fully operational and stable by this date. Formal Pilot Project Closure. The Pilot Project will be closed (See Topic 11), and final reports and other deliverables must be provided by this date. If the Pilot is successful, it is intended that the project would continue, but the Pilot Project Closure process must still be done by this date. as the Project Manager, the Board has indicated that you will have access to the following people, so they can give the advice needed to prepare the project documentation (that needs to be delivered to the Board). These people/organisations will then be engaged as necessary to support the project. Donna Jenner (CEO) Ben Dover (CIO & Project Sponsor) Roles and additional information The Board's only role will be to determine whether the project will go ahead. If they approve the project, the allocated funds will be controlled by the Project Sponsor, to facilitate the achievement of the project objectives. As much as they will not be highly active participants, you will need to keep the Board informed on progress at a strategic level (typically through the Project Sponsor). However, please remember that they would not normally have any direct day- to-day management involvement. Donna is responsible to the Board and is also the primary Executive Member of the Board. In particular, she is responsible for the operational management of EAMI. The CEO will have some strategic oversight requirements for the Project, and you will need to provide some reports to her through the Project Sponsor. However, she would not normally get involved in the day-to- day management of the project. Ben is the Chief Information Officer (CIO) for the organisation and is therefore primarily focussed on broader aspects than this project. The CIO is therefore responsible to the CEO for all aspects of ICT utilised by EAMI and will be specifically responsible to Joyce Ander. As the Project Sponsor, he will be responsible for the strategic coordination of this project and its budget. You are directly responsible to him for the operational management of the project, and you would, therefore, need to proactively keep him up-to-date on progress. Additionally, you would need to engage him in key operational decisions. However, he would not typically get involved in Page 4 of 7 Pam Duggins (Educational Content Expert) Bill Sykes (Legal Support) Don Lemon (Security Expert) Marketing & Sales team: Technical Development Contractors direct operational management (unless he thinks there is a problem, and you are not doing your job you do not want this to happen). Therefore, you will generally keep him aware of the project through formal and informal communication (as discussed in Topic 8), and you will do the bulk of the management and coordination that is necessary. Pam is the educational content expert in the company, and she will be available (part-time) to help build/evolve the media catalogue/content for deployment through the streaming environment. Eva also knows the main providers of educational videos and games, so she can help you to define engagements that can enhance the existing library of materials (so the product becomes more appealing to clients). He is EMI's legal and contractual expert. In particular, Bill can support contract development and negotiations with suppliers and contractors. Additionally, he can help with the development of the license agreements (e.g., End User License Agreements (EULA)) that will be necessary for client engagement. Don is our expert on security issues and the associated legal requirements (e.g., implementing the solutions in accordance with the Privacy Act). He is an outside consultant but will be available as necessary to provide this support once the project commences. In the interim, he is happy to answer some questions (which will be simulated by you asking questions of the lecturer). Marketing team: EdMI already has a marketing team of five people. These are: Kate Lundy (Marketing Manager). lim Davis (Salesperson Perth) Doug Dundas (Salesperson Sydney) Sue Ledger (Salesperson Melbourne) Joe Bunnings (Salesperson Brisbane) These staff will not work directly for the Project Manager. Forinstance, the Marketing Manager works directly for the CEO and all of her staff are responsible to her. However, the marketing/sales team have committed to providing advice on their existing clients during this preliminary planning period, because they know the existing customers and their needs very well. Additionally, it has been agreed that, if the project proceeds, they will conduct the following activities in support of the project (while not working directly for the Project Manager): e engage existing and new customers to participate in the Beta/Acceptance testing; and e provide some of the on-site liaison with the clients who will be participating in the Beta/Acceptance testing. The marketing and sales team have also indicated that: e for them to conduct the marketing of this product and the liaison with the clients for the Beta/Acceptance testing, they will need detailed training in the EduStream system and the concept of operation for this software; and they don't have expertise in mass marketing, so an outside consulting organisation will need to be engaged to support this aspect of the project. From the preliminary RFT investigation, you have identified three companies that may be able to meet at least part of the needs for this project. These are StreamTech, VidCon, and DemSet. You will need to discuss the issues with these companies, so you can develop ideas, possible solutions and selection criteria. This information will then shape the RFT as discussed above. Please note that the timeline for this contractual engagement is very short, so you will need to start working on this very soon. Please also take into account the following notes: e For this assignment, you will only need to do the Weighted Analysis part of the RFT development. You will not need to do the financial analysis component that would normally also be required. Page 5 of 7 e These organisations are separate from EdMI, and they will not work for you or assist directly in your design work unless they are engaged as a contractor. Consequently, you will need to work with them as openly as possible, but you will not have any control over them until a formal contract is in place. Suppliers You will need to engage appropriate suppliers/service providers for the equipment, Data Centres and other systems (e.g., Telcos, etc.). Additionally, you will need to find an appropriate Service Desk, which will be able to provide support for any Academic or Organisational clients that you engage. Please note that you will not provide Service Desk support to all users, as this would be too expensive. For the mass market users, you will provide a Frequently Asked Questions (FAQ) web site. Other Staff If you need any additional staff/expertise to complete the project successfully, you will have to create proposals to the Project Sponsor. In the real world, you would need to explain the cost, time, quality and scope implications. For this assignment, you will not need to do this. For this assignment, you can assume that you have already identified that you will need staff to support the Project Office, which you will have to establish on the Project Start Date. Some of the additional staff that you will need to engage will be required to support: administration, payments, Quality Assurance, training of the sales staff and clients, procurement, testing, development of key knowledge tools such as a Wiki and Knowledge Base and the FAQ web site. Preliminary Cost/Revenue Information A preliminary analysis has indicated that the following costs and revenues are likely to accrue from the implementation of the Pilot Project. These are Rough Order of Magnitude (ROM) figures only, but they should provide a useful starting position for the analysis. Description Year 0 Year 1 Year 2 Year 3 ROM Costs/Expenditures $1,205,000 $710,000 $820,000 $860,000 ROM Benefits/Revenues $256,000 = $1,115,000 $1,800,000 = $2,500,000 Assumptions The following base assumptions need to be taken into account when analysing the preceding ROM cost/revenue figures and the associated project aspects: e These figures do not take into account the discount effects related to inflation and the cost of capital. e The inflation rate is expected to remain at about 1.8% per annum for the next four years. e This project will be funded through debt (a loan from EdMI's Bank). There will be no establishment costs (as this will be an extension of existing funding agreements), and the bank has offered a fixed loan rate of 3.8% per annum. e Year 0 commences at the Project Start Date. Following years are consecutive. e The ROM expenditures take into account expected personnel (development, maintenance, Service Desk, management, etc.), equipment (hardware and Data Centres), software (products, licenses, etc.), services (network communications, maintenance, etc.), and indirect costs (e.g. applicable ancillaries), which will be required to conduct the project and then maintain/pay for the pilot sites and services with no further expansion. e Revenues in Year 0 relate to the sign-up of clients on the Beta program, and for engagement of clients after Acceptance Tests (AT) have been completed for each Pilot. e Revenues from Year | are based on transitioning many of the existing customers onto the new EduStream plan. This will be additional revenue, as the clients had already paid an up-front fee for use of the existing software and videos. However, to entice them to upgrade, the EduStream product Page 6 of 7 will have to deliver real benefits to the clients (e.g. they are not just going to be paying a monthly Jee to get access to the materials they already possess). The Marketing team has also indicated that they believe that they can deliver some expansion in the customer base, and conservative estimates have already been included in the ROM figures. Most importantly, the Marketing Manager has said that there is also considerable scope for expansion from these figures as the company transitions from its traditional media deployment methods (i.e., revenues may be larger but be aware that this could also impact on demand and the system design). e Interms of revenues, it is intended that individual users would pay a flat monthly fee, which would be kept small to entice them to join the system (e.g., going for mass-market sales). Institutions, such as schools would be charged a monthly rate, based on student numbers/utilisation (this would make seat prices lower because they are working on higher license volumes). ADDITIONAL VIEWING/READING As you are not an expert in streaming technologies, it is highly recommended that you do some preliminary research into this technology. Consequently, in addition to reviewing the URLs listed on Page 1, please use the internet to do some background reading/viewing, so you can understand key aspects of the design and technology. In particular, you might want to begin by viewing these videos: e https://www.youtube.com/watch?v=bUHF-UWGoVU This gives some basic information on video streaming and RTSP; e https://www.youtube.com/watch?v=HgKaKWomh-A This provides some more detailed information on RTSP; e https://www.youtube.com/watch?v=L168ndJZW4g This one also gives some more detailed information on RTSP if you want to get into the detail; e https://www.youtube.com/watch?v=I8k4foAsWVE This video provides another way of understanding RTSP; e https://www.youtube.com/watch?v=AeJzoqtuf-o This video gives a simplified overview of video streaming (Although it discusses the issues in relation to the Real Time Messaging Protocol (RTMP) the concepts are similar for RTSP); and e https://www.youtube.com/watch?v=Fawcboio6g4 This video provides some basic information on video compression and codecs (and in particular H.265), which can give you some useful background information. There are plenty more of these types of video and there is also lots of pertinent information available through various web pages. You will not need to know everything about the protocols and systems, but it will be important for you to have a reasonable understanding of the technology, so you can manage the project effectively (this is a very real-world issue). Additionally, you will need this type of knowledge to fill in the material needed in the Definitions and Acronyms section within the Project Charter. Now proceed to read the EduStream Technical Architecture and Project Implementation Timeline. These documents are provided on the LMS in the section 'Project Scenario Information'. Page 7 of 7