Development of Environmentally Friendly Amphicar

Development of Environmentally Friendly Amphicar AMPHICAR II System Specifications 1 Statement of work Our team has aimed to produce an energy efficient, environmental friendly personal consumer vehicle that is capable of travelling on road and operating as a fun filled water vehicle. The project idea of AMPHICAR II is to introduce the vehicle to the public; the first prototype will be used in crossing in the English Channel, beating Richard Bransons record set in the Gibbs Aquada. The project background given by AdSing systems engineering, world leaders in revolutionary new system development, has undertaken the challenge of developing a state of the art amphibious vehicle for the consumer market. This is defined as the first phase of the project and the budget for this phase is $80000. This phase of the project will be completed in 30 days. After completion of the conceptual design of the AMPHICAR II project, it shall be placed as a proposal put forward by AdSing to independent sub-contractors for further iterations of the system development cycle. For the successful completion of this phase of the project, we will have guided by our tutor (Bill Daniels) who is the systems Engineering Expert. The requirements of the vehicle is achieved by incorporating safety features, capability of travelling on road and water, customer satisfaction, robust design, lower operational cost, and after all the project should be completed within the budget. IEEE 1220 standard specifies the system engineering process and it is primarily targeting our product (Amphicar) oriented system, which defines the inter-disciplinary tasks that are required to our project throughout the lifecycle to transform stakeholder (Customer)needs, requirements and constraints in to our product development. Therefore our group has emphasized to bring ideas in brainstorming session and initially conducted a assessment on potential customers before beginning the conceptual design. Here we have the conceptual design of the AMPHICAR project comprises of four different stages namely System engineering and management plan, Systems requirement specification, functional analysis allocations and final stage of system specification. The project planning in fact it refers to SEMP which includes statement of work, work schedule, cost analysis, product testing methods, program management, risk management, resources required, deliverables, etc., System requirements specification stage are identified based on the needs and the project requirements. Functional analysis allocation stage comprises with functional breakdown is done to determine the system physical design overview, functional analysis and component details. At the final stage of system specification, AMPHICAR II project undergoes evalu ation and final documentation. 2. Referenced documents AMPHICAR concept http://en.wikipedia.org/wiki/Amphicar Referred on 06/01/2010 The AMPHICAR Story http://books.google.com/books?id=C-PeNY12Ss8Cpg=PT12dq=Amphicar+designei=ZQlIS5ezBpv-lASmprT3DQcd=4#v=onepageq=Amphicar%20designf=false Referred on 07/012010 IEEE 1220 Standard readings http://ieeexplore.ieee.org.ezlibproxy1.unisa.edu.au/stamp/stamp.jsp?tp=arnumber=1631953isnumber=34216 Referred on 09/01/2010 3. Work breakdown structure (this phase of the AMPHICAR project) 3.1 Schedule In fact we have 30days time from 8th January 2010 till 8th February 2010 to complete an attractive high level conceptual design of AMPHICAR II. The Systems specification preparation towards the Amphicar project will be worked in four different stages, under each stage the preparation compiled as draft and submitted through Assign IT on weekly basis. The weekly submission would ensure the timely completion of each stages include the project plan, system requirements specification and the functional analysis allocation and the final systems specification preparation of the AMPHICAR II project to be submitted. The complete details of the schedule can be seen in the Gantt chart on 1. The cost analysis and workout is also shown on Table 1. AMPHICAR II System Specifications 3.2 Cost Sl No. Planned Tasks Budget (S$) No. of hrs Actual Cost (S$) Balance (S$) System Engineering Management Plan 20000 7 days 17850 2150 1 Statement of work 4 500 19500 2 Referenced Documents 6 3000 16500 3 Work Breakdown Structure 3.1 Work Schedule 4 1000 15500 3.2 Cost 12 1500 14000 3.3 Product Testing Methods 15 3500 10500 4 Program Management 8 1750 8750 5 Risk Management 8 1500 7250 6 Resources Required 4 2000 5250 7 Deliverables 4 1250 4000 8 Organizational Structure 4 850 3150 9 Operational Concept 4 1000 2150 Total 20000 73 17850 2150 System Requirement Specification 24000 7 days 20500 3500 10 Scope 10.1 System Overview 6 1500 22500 11 Referenced Documents 5 1250 21250 12 Needs 12 4000 17250 13 Requirements 13.1 General Requirements 8 2000 15250 13.2 System Capability 12 2500 12750 13.3 Safety Requirements 8 2000 10750 13.4 Personnel Related Requirement 8 1750 9000 13.5 Security and Privacy Requirement 10 1500 7500 13.6 Logistics related requirement 12 2500 5000 13.7 Other Requirements 6 1500 3500 Total 24000 87 20500 3500 Table 1 continued†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. Functional Analysis Allocation 24000 7days 18500 5500 14 Scope 14.1 System Overview 7 1750 22250 14.2 Document Overview 4 1000 21250 15 Referenced Documents 9 2250 19000 16 Functional Analysis 24 4000 15000 17 Physical Design Overview 24 6250 8750 18 Component Details 8 3250 5500 Total 24000 76 18500 5500 Final System Specification 12000 7 days 11250 1750 19 System Description 8 2000 11000 20 Operational Requirements 5 1500 9500 21 Operational Constraints 5 1500 8250 22 System Evaluation 16 3000 4250 23 Final Documentation 12 3250 1000 Total 13000 46 11250 1000 Final Total 80000 282 68100 11900 Table1. Cost Note * 1 day = 8hrs and 5days per week (Monday to Friday) 3.3. Product testing method Product testing method is one of the most important steps in bringing out of our conceptual design of AMPHICAR II Project, which demands the recognition in the future when the product shall complete and reached at the market. The final product here is the AMPHICAR which is capable of travelling both road and water. The intention of the product testing method is to Ensure that the conceptual design of the product meets the design standards for employability, consistency, and user friendliness towards its functionality. Ensure the design meets the business goals and user needs. Ensure the design does not permit any changes at the final stage of its requirements and concept Ensure the behaviour of the system can be easily understood by the design engineers. Make sure that the design provides proper guidance to the designers to resolve any issues that may arise. Make sure that the design shall not distract the copyright of other brand in the global market. Ensure that the design is properly employed by the design engineers which can be easily interacted by the users and other products. Ensure the physical design matches up with the initial art design Ensure the safety features incorporated in the product shall always be enabling and These reviews are carried out at different phases precisely Project plan, system requirement specification, functional analysis and allocation and final system specification. At the end of each and stage a discussion session is made where all the team members and the manager (who assess the detail of design from the sub-system level to the component level), are gathered to review their respective tasks in each phase and the ideas are taken for any necessary changes of any improvement that can be done for bringing the project successful. The assessed document upon the end of each discussion will be sent as a draft to the project who verifies and evaluates the design and make a note to the manager and the team members if changes that are required for the design improvement and further evaluates after getting his job done by the team and approve the design and promote to the next phase. Thus the design of the final system specification is drawn and reviewed by the project director and approve the design for its release 4. Program management Program management is the mechanism by which the work of various operating functions within a company is integrated to create an effective business model. When program management is properly conceived and executed, it helps to execute business strategies much more effectively than an uncoordinated approach. The program manager must possess operational competencies, including project management methods and tools, to effectively manage the tactical elements of the program. Another important aspect of this core discipline set is that of becoming proficient in the specific processes and practices of the company that the program manager is a part of. Knowing how things get done, the policies and procedures that must be adhered to and who must be involved and approve various aspects of their program are critical for the successful completion of every program. During the early stages of conceptual design, it is essential that good communication between the producer and the customer be established from the beginning. The Design Engineer must fully understand the user requirements of the product to be designed. This can be achieved only we have a good communication between users. The communication modes used are Teleconference, E-mails, Fax and formal meeting between the project team members and others. Meeting agenda ( 2a) will be formatted for all meetings and distributed to all members before one day. And minutes of meeting ( 2b) are drafted and distributed to all members to follow up. The primary objective of our program management plan is to facilitate the timely integration of numerous design considerations into a functioning and Physical system that will be of high value to the user. Our program management consists of SEMP which already Stated in Gantt chart (System Engineering Management Plan), Statement of work (SOW), Work break down structure, schedule of tasks, Projecting costs for program task and interfacing with other planning activities. Our project has mentioned a configuration management plan to track the changes done from the beginning to the final review. During the later stage of our conceptual design we shall develop a comprehensive system engineering management plan (SEMP) to ensure the implementation of a program that will lead to a well coordinated and integrated product. a program is to exploit economies of scale and to reduce coordination costs and risks. programs deliver outcomes, program management is concerned with doing the right projects according to this view, successful projects deliver on time, to budget and to specification, whereas successful program deliver long term improvements to an organization design of the new product this delivers a design specification, modifications to the production factory Program and project management are both practical disciplines, Program management also emphasizes the coordinating and prioritizing of resources across project. Program management may provide a layer above the management of projects and focuses on selecting the projects, defining us in terms of their objectives and prov iding an environment where projects can be run successfully. Our organizations use the concept of Systems engineering where others use program management, ensure there are regular reviews; there is accountability, and that management of projects, allocation of resources influences the cost and success of the program. Infrastructure might cover offices, version control, and IT. A project must always have a specific end date, else it is an ongoing program. A project is designed to deliver an output or deliverable and its success will be in terms of delivering the right output at the right time and to the right cost. Program management is the mechanism by which the work of various operating functions within a company is integrated to create an effective business model. When program management is properly conceived and executed, management includes management of projects which, together, improve the Program management is the mechanism by which the work of various operating functions wit hin a company is integrated to create an effective business model. When program management is properly conceived and executed, performance of the organization. A programs success will be measured in terms of benefits. Program Management comprises a comprehensive suite of services addressing the full program life cycle and implemented by dedicated and highly skilled team members. PMP (Project Management Professional Program management practices put a continual focus on the business aspects of developing products, services and infrastructure. A skilled and competent program manager is the primary business manager on a program. We have Projects Managers that are certified and have decades of experience applying project management techniques and disciplines to client engagements in all industries. During our conceptual design phase we have scheduled a series of formal design reviews at discrete points where the design configuration involves from one level of definition to another. That is conceptual system, evolutions and design reviews. The successful implementation of system engineering principles and concepts is dependent not only on the technology issues and the process, but on management issues as well. Our BLR Engineering prepared a program management plan comprising series review meeting, audits, approval from user, risk managements, and some essential contingency plans. This program management plan guides all over activities throughout the project. 5. Risk management Risk management can therefore be considered the identification of the potential areas of risk. It is a part of the requirements and design stages in a project. Our team of experienced engineers has gone through the assessment and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities. One of the first steps of our risk management is the identification of the potential areas of risk. Risk shall include funding, schedule, and contract, relationships, political and technical. All of these hazardous shall be identified and evaluated and risk mitigation performed. Risk analysis should be performed as part of the risk management process for each project. Once a hazard identified as below, the steps of the risk managements process are as follows, Assess the current risk Define the acceptable level of the risk Decision on the response of the risk. Our risk management plan consists of four processes such as 1. Identification 2. Assessment 3. Analysis 4. Controls/Implementation 5. Responsibility As far as concerned about conceptual design process we may have these few types of risk only. Which are? 1. Technical Risk The possibility that technical requirement of the system will not be achieved. That is our design wont meets the system requirements adequately. We have planned to tackle such risk by remedial actions given in the table below 2. Schedule Risk The possibility that the project will fail to meet the scheduled milestones, such as those mentioned in our project plan. To tackle this issue we have identified possible cause and effects and of course the remedial actions to be taken respective 3. Cost Risk The possibility that the project will fail to meet the scheduled milestones and the cost of the project will go up and difficult to meet the budget. These are the probable risk that might be encountered and the contingency plan to overcome in the planning phase: Potential Risk 1 Difficulties in meeting up for our group member to discuss on the project due to different working schedule. Possible Solution to Risk1 Meeting to be done on every Saturday afternoon so the plans can be executed in the weekends before submitting the drafts. Ideally, meeting could also be schedule after 8 pm for a brief update on progress. Potential Risk 2 Group members have difficulties in meeting at convenient venue. Possible Solution to Risk2 Meeting can be done at any National Libraries or APMI campus when not only the environment is convenient for learning Potential Risk 3 Group member/s might fall sick and might not be able to meet for discussion. Possible Solution to Risk3 Work progress should be continually updated through email. Potential Risk 4 Group member/s may face problems in software incompatibility and in data sharing. Possible Solution to Risk4 Group member must work on common PC platform to avoid compatibility issues (e.g. one works on LINUX, and another one works on Mac Operating System and may result in unintended data corruption unable to read or edit documents. Better to work on common platform PC like Microsoft OFFICE and OpenProj for common means of compatibility. Any need of using unfamiliar program must be made known and shared so that each and everyone of the member can learn and use the new program. Potential Risk 5 Anyone of the Group member might encounter risk of data loss or corruption. Possible Solution to Risk5 Group member must regularly backup their data on their PC and must have a secondary means of backup (eg. Thumb drive or external hard drive). Seek advice from Mr. Bill Daniels through the discussion Board provided on course website. Initial Project Risk Assessment SNo Identify Hazard Hazard Assessment Causes Effects Implement / Controls Responsi- bility 1 Budget estimation unlikely 1. Substantial cost increase in the project 1. Source for more economical alternative to control spending. 2. Maintain strict accounting practice. Balaji 2 Unrealistic Projected timeline Frequently 1. Delay in project 2. Bad image for team 3. Loss due to time delay Strict to the time frame set for the work schedule and Gantt chart. Balaji 3 Disruption to System Equipment Frequently 1. Loss of Equipment 2. Delay in project 1. Constant backup. 2. Escalate of any unusual encounter. Rakesh 4 Manpower management Frequently 1. Delay in project 2. Overload of team member 1. Co-ordinate meeting regularly to delegate task and work discussion. 2. Meeting to be done on Saturday Lakshmanan 5 Group members have difficulties in meeting at convenient venue Likely 1. Delay in project 2. Substantial delay in all phases of the project Meeting can be done at any National Libraries or APMI campus when not only the environment is conducive for learning but laptop user could have access to internet wireless connection. Lakshmanan 6 Face problems in software incompatibility and in data sharing. Likely 1. Delay in document work 2. Delay in project Group member must work on common PC platform to avoid compatibility issues (e.g. one works on LINUX, and another one works on APPLE Operating System and may result in unintended data corruption unable to read or edit documents. Better to work on common platform PC like Microsoft OFFICE and OpenProj for common means of compatibility. Any need of using unfamiliar program must be made known and shared so that each and everyone of the member can learn and use the new program Rakesh 7 Group member might encounter risk of data loss or corruption. Likely 1. Loss of all details and documents. Group member must regularly backup their data on their PC and must have a secondary means of backup (e.g. Hard disk, Thumb drive). Rakesh 8 Vendor and Supplier co-ordination issue. Frequently 1. Delay in project 2. Bad image for team 3. Loss due to time delay Plan early and have back-up resources in the event existing vendor meet constraint. Lakshmanan 9 Having doubt in preparing draft. Frequently 1. Delay in project Seek advice from Mr Bill Daniels through the discussion Board provided on course website. Balaji Lakshmanan Rakesh Table2. Initial Project Risk Assessment 6. Resources required Resources are also a very important in the course of a project development. Availability of the different kinds of resources must be used satisfactorily. It is critical to establish a credible schedule because the timing of activities not only depends on the logical dependencies between them, but also on the availability of the required resources. Our group member has used as many as facilities available to achieve the required satisfaction of the information. The resources we use to accomplish the goal of acquiring the conceptual design of an amphibious car are, Hardware I. Computer  § To work on the project report development II. Computer peripherals  § To copy the draft data.  § To print the draft copy for verification. Software III. Core University 5.0 by Vitech Corporation  § To have the breakdown of the requirements  § To display the conceptual design through Flow Functional Block Diagram and Hierarchy Application Packages IV. Microsoft Project Professional 2003  § To create schedule for the entire project plan  § To design the chart for the work task allocation  § Ensure the time limited for the task is look upon V. Microsoft Word  § To type the final specification report of the project Facilities VI. Internet media  § To gain access to the video media regarding amphibious vehicle such as you tube  § To search related information regarding amphibious vehicle  § To gain access to the related websites  § To have communication with the project supervisor  § To have a convenient place to discuss the project development matters  § The usage of this media is vastly great VII. Money/Time Funds  § To have food/refreshments for members attending discussion for the entire project plan  § Towards the expenses like photocopying, phone calls, printing / copying  § To have transport facilities  § To make free ourselves on the discussion planned days. 7 Deliverables For our projects deliverables are the stuff/function that can be the result for the task implementation, it consists of things or stuff such as presentation (MSPowerpoint Slideshows), documentation requirements, total design documentation etc. The documents as deliverables used here are namely the System Engineering Management Plan, System Requirement, Functional Analysis and Allocation, and Final System Specification. System Engineering Management Plan (SEMP) This plan consists of the Scope of the Project, Work Breakdown Structure as Schedule, Cost and Product Testing method, Operation concept. It has to be executed in such a way to get the best result by assigning individual task to the respective team members thereby lead the project together with proper planning to bring the required outcome. System Requirements and Specifications (SRS) This emphasise the task that determines the needs for the product, users, designers, system and subsystems. It identifies the needs of each stakeholder. Functional Analysis and Allocation (FA A) This transforms the system level requirement into functions and analyse the behaviour of the system to get the desired result. And these functions are allocated into a physical design (component level). It can be seen in detail through Functional flow block diagram. Final system specification This document comprises all the above three documents which seeks approval from the Project director for the release of the design to Production. 8. Organisational structure We believe on team work, so at all phases the task has been evenly distributed to our team members according to their role. The process flow is as follows, getting the instruction from project director the task has been distributed to the Project Design engineer by the Project manager and also the whole project is monitored by the Project director. 9. Operational Concept The world is in needs of better and more effective and efficient vehicle that could save money, earth, resources and time of travelling which will be having the various good features when operates in both the environments. Keeping that in mind our Engineering team with the engineering skills would like to design an amphibious vehicle having capable of travelling both in road and water. i.e user friendly navigation system safety protection which will meet the customer needs as customer is mainly dependent on the effective and efficient transportation to commute in his day to day life. As the name goes, the designed Amphibious Car having the capability to travel both on land and on water promises to be more environmental friendly than any other amphibious car compared to existing or future market .The idea behind this is from the automobile researchers who have been done and many have succeeded but unable to market the vehicle as it still needs more work has to be done. Some engineers also did research beyond their imagination but some have succeeded and some are still a long way. The conceptual design of amphibious vehicle will be aimed to provide comfortable journey, trouble free service, energy efficient and environment friendly with Safety features for the customers and the features include well designed with double secured protection against water leak and corrosion of vehicles body parts by using the anti corrosive materials and fail safe controls , fuel efficient, operating at an economical way by giving good mileage and the vehicle would be engineered in way of reducing carbon dioxide emission and reducing pollution to Mother Nature as analysed by our expert engineers it would also benefit the market as a new breed of automobile needs many suitable workshop and fuel station. The vehicle has a robust designed in such a way it is very compatibility for both the conditions either it is in water or on the land. The vehicle will be operated as a boat when in water and navigation system made easy during high tides water currents and during windy seasons. The vehicle will be like normal cars when it operates on the road. The design of the bigger wheels will be providing a better ride in terrain, mud and snow and excellent traction capability with 4 gear power transmission and will provide excellent driving experience. The Vehicle will be designed to have a sportive external look. The look and feel of the designed vehicle is such that it would posses pleasant Interior colours , leg rooms spacious comfortable seatings and incorporating entertainment systems which ensures smooth and comfortable rides both on land and water. The vehicle would be cost effective under long run as the he vehicle has been designed in a way that would have less maintenance. The rugged a nd robust design assures reliability of the vehicle. The vehicle will equipped with a spare tyre and necessary tools. Our team has scheduled the conceptual design tasks and our expertise will fulfil every aspect of the customer requirement in terms of operational, maintenance and service needs and to make it big success in the market. 1. Scope 1.1 System overview Our project â€Å"Amphicar II† as the name suggests the vehicle is designed such that is viable both on land and water. It is a sports convertible full rear seat, well designed family size customer vehicle taking into account for the complete luxury as well as the safety of the customer. Customer can plan to drive right off a road or beach onto any lake or river as it is not only a luxurious car once on land but safely floats on water also because the bottom of the vehicle consists of rubber seals which forms a watertight seal. Some of the key design specification of the Amphicar II are: Its proficient 4 cylinder engine has 4 speed auto transmission forward speeds, Front wheels act as twin rudders for fast responsive handling, rear mounted for superior traction on the road, fitted with accelerator control system making the vehicle to run fuel economically both in road and water fitted with 2 rear lamps each and inbuilt side indicators, Speed O meter (digital) to display the ca rs speed, Coming to the functional aspect of the Amphicar II, once the doors are checked to be closed the customer can just drive into the water edge, and once when the car is into water, the customer is required to put land gear into neutral and then can use the facilities of the propeller or Amphibian jet by engaging it with the smaller stick which has three positions forward, neutral and reverse. Although virtually it is identical to the rest of the Amphibious vehicles, our Amphicar II distinct itself from other late models by having some of the technologies like heater placement, shock mountings, lower body lip and dash treatment and most importantly safety aspect is also considered like emergenc Development of Environmentally Friendly Amphicar Development of Environmentally Friendly Amphicar AMPHICAR II System Specifications 1 Statement of work Our team has aimed to produce an energy efficient, environmental friendly personal consumer vehicle that is capable of travelling on road and operating as a fun filled water vehicle. The project idea of AMPHICAR II is to introduce the vehicle to the public; the first prototype will be used in crossing in the English Channel, beating Richard Bransons record set in the Gibbs Aquada. The project background given by AdSing systems engineering, world leaders in revolutionary new system development, has undertaken the challenge of developing a state of the art amphibious vehicle for the consumer market. This is defined as the first phase of the project and the budget for this phase is $80000. This phase of the project will be completed in 30 days. After completion of the conceptual design of the AMPHICAR II project, it shall be placed as a proposal put forward by AdSing to independent sub-contractors for further iterations of the system development cycle. For the successful completion of this phase of the project, we will have guided by our tutor (Bill Daniels) who is the systems Engineering Expert. The requirements of the vehicle is achieved by incorporating safety features, capability of travelling on road and water, customer satisfaction, robust design, lower operational cost, and after all the project should be completed within the budget. IEEE 1220 standard specifies the system engineering process and it is primarily targeting our product (Amphicar) oriented system, which defines the inter-disciplinary tasks that are required to our project throughout the lifecycle to transform stakeholder (Customer)needs, requirements and constraints in to our product development. Therefore our group has emphasized to bring ideas in brainstorming session and initially conducted a assessment on potential customers before beginning the conceptual design. Here we have the conceptual design of the AMPHICAR project comprises of four different stages namely System engineering and management plan, Systems requirement specification, functional analysis allocations and final stage of system specification. The project planning in fact it refers to SEMP which includes statement of work, work schedule, cost analysis, product testing methods, program management, risk management, resources required, deliverables, etc., System requirements specification stage are identified based on the needs and the project requirements. Functional analysis allocation stage comprises with functional breakdown is done to determine the system physical design overview, functional analysis and component details. At the final stage of system specification, AMPHICAR II project undergoes evalu ation and final documentation. 2. Referenced documents AMPHICAR concept http://en.wikipedia.org/wiki/Amphicar Referred on 06/01/2010 The AMPHICAR Story http://books.google.com/books?id=C-PeNY12Ss8Cpg=PT12dq=Amphicar+designei=ZQlIS5ezBpv-lASmprT3DQcd=4#v=onepageq=Amphicar%20designf=false Referred on 07/012010 IEEE 1220 Standard readings http://ieeexplore.ieee.org.ezlibproxy1.unisa.edu.au/stamp/stamp.jsp?tp=arnumber=1631953isnumber=34216 Referred on 09/01/2010 3. Work breakdown structure (this phase of the AMPHICAR project) 3.1 Schedule In fact we have 30days time from 8th January 2010 till 8th February 2010 to complete an attractive high level conceptual design of AMPHICAR II. The Systems specification preparation towards the Amphicar project will be worked in four different stages, under each stage the preparation compiled as draft and submitted through Assign IT on weekly basis. The weekly submission would ensure the timely completion of each stages include the project plan, system requirements specification and the functional analysis allocation and the final systems specification preparation of the AMPHICAR II project to be submitted. The complete details of the schedule can be seen in the Gantt chart on 1. The cost analysis and workout is also shown on Table 1. AMPHICAR II System Specifications 3.2 Cost Sl No. Planned Tasks Budget (S$) No. of hrs Actual Cost (S$) Balance (S$) System Engineering Management Plan 20000 7 days 17850 2150 1 Statement of work 4 500 19500 2 Referenced Documents 6 3000 16500 3 Work Breakdown Structure 3.1 Work Schedule 4 1000 15500 3.2 Cost 12 1500 14000 3.3 Product Testing Methods 15 3500 10500 4 Program Management 8 1750 8750 5 Risk Management 8 1500 7250 6 Resources Required 4 2000 5250 7 Deliverables 4 1250 4000 8 Organizational Structure 4 850 3150 9 Operational Concept 4 1000 2150 Total 20000 73 17850 2150 System Requirement Specification 24000 7 days 20500 3500 10 Scope 10.1 System Overview 6 1500 22500 11 Referenced Documents 5 1250 21250 12 Needs 12 4000 17250 13 Requirements 13.1 General Requirements 8 2000 15250 13.2 System Capability 12 2500 12750 13.3 Safety Requirements 8 2000 10750 13.4 Personnel Related Requirement 8 1750 9000 13.5 Security and Privacy Requirement 10 1500 7500 13.6 Logistics related requirement 12 2500 5000 13.7 Other Requirements 6 1500 3500 Total 24000 87 20500 3500 Table 1 continued†¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦Ã¢â‚¬ ¦. Functional Analysis Allocation 24000 7days 18500 5500 14 Scope 14.1 System Overview 7 1750 22250 14.2 Document Overview 4 1000 21250 15 Referenced Documents 9 2250 19000 16 Functional Analysis 24 4000 15000 17 Physical Design Overview 24 6250 8750 18 Component Details 8 3250 5500 Total 24000 76 18500 5500 Final System Specification 12000 7 days 11250 1750 19 System Description 8 2000 11000 20 Operational Requirements 5 1500 9500 21 Operational Constraints 5 1500 8250 22 System Evaluation 16 3000 4250 23 Final Documentation 12 3250 1000 Total 13000 46 11250 1000 Final Total 80000 282 68100 11900 Table1. Cost Note * 1 day = 8hrs and 5days per week (Monday to Friday) 3.3. Product testing method Product testing method is one of the most important steps in bringing out of our conceptual design of AMPHICAR II Project, which demands the recognition in the future when the product shall complete and reached at the market. The final product here is the AMPHICAR which is capable of travelling both road and water. The intention of the product testing method is to Ensure that the conceptual design of the product meets the design standards for employability, consistency, and user friendliness towards its functionality. Ensure the design meets the business goals and user needs. Ensure the design does not permit any changes at the final stage of its requirements and concept Ensure the behaviour of the system can be easily understood by the design engineers. Make sure that the design provides proper guidance to the designers to resolve any issues that may arise. Make sure that the design shall not distract the copyright of other brand in the global market. Ensure that the design is properly employed by the design engineers which can be easily interacted by the users and other products. Ensure the physical design matches up with the initial art design Ensure the safety features incorporated in the product shall always be enabling and These reviews are carried out at different phases precisely Project plan, system requirement specification, functional analysis and allocation and final system specification. At the end of each and stage a discussion session is made where all the team members and the manager (who assess the detail of design from the sub-system level to the component level), are gathered to review their respective tasks in each phase and the ideas are taken for any necessary changes of any improvement that can be done for bringing the project successful. The assessed document upon the end of each discussion will be sent as a draft to the project who verifies and evaluates the design and make a note to the manager and the team members if changes that are required for the design improvement and further evaluates after getting his job done by the team and approve the design and promote to the next phase. Thus the design of the final system specification is drawn and reviewed by the project director and approve the design for its release 4. Program management Program management is the mechanism by which the work of various operating functions within a company is integrated to create an effective business model. When program management is properly conceived and executed, it helps to execute business strategies much more effectively than an uncoordinated approach. The program manager must possess operational competencies, including project management methods and tools, to effectively manage the tactical elements of the program. Another important aspect of this core discipline set is that of becoming proficient in the specific processes and practices of the company that the program manager is a part of. Knowing how things get done, the policies and procedures that must be adhered to and who must be involved and approve various aspects of their program are critical for the successful completion of every program. During the early stages of conceptual design, it is essential that good communication between the producer and the customer be established from the beginning. The Design Engineer must fully understand the user requirements of the product to be designed. This can be achieved only we have a good communication between users. The communication modes used are Teleconference, E-mails, Fax and formal meeting between the project team members and others. Meeting agenda ( 2a) will be formatted for all meetings and distributed to all members before one day. And minutes of meeting ( 2b) are drafted and distributed to all members to follow up. The primary objective of our program management plan is to facilitate the timely integration of numerous design considerations into a functioning and Physical system that will be of high value to the user. Our program management consists of SEMP which already Stated in Gantt chart (System Engineering Management Plan), Statement of work (SOW), Work break down structure, schedule of tasks, Projecting costs for program task and interfacing with other planning activities. Our project has mentioned a configuration management plan to track the changes done from the beginning to the final review. During the later stage of our conceptual design we shall develop a comprehensive system engineering management plan (SEMP) to ensure the implementation of a program that will lead to a well coordinated and integrated product. a program is to exploit economies of scale and to reduce coordination costs and risks. programs deliver outcomes, program management is concerned with doing the right projects according to this view, successful projects deliver on time, to budget and to specification, whereas successful program deliver long term improvements to an organization design of the new product this delivers a design specification, modifications to the production factory Program and project management are both practical disciplines, Program management also emphasizes the coordinating and prioritizing of resources across project. Program management may provide a layer above the management of projects and focuses on selecting the projects, defining us in terms of their objectives and prov iding an environment where projects can be run successfully. Our organizations use the concept of Systems engineering where others use program management, ensure there are regular reviews; there is accountability, and that management of projects, allocation of resources influences the cost and success of the program. Infrastructure might cover offices, version control, and IT. A project must always have a specific end date, else it is an ongoing program. A project is designed to deliver an output or deliverable and its success will be in terms of delivering the right output at the right time and to the right cost. Program management is the mechanism by which the work of various operating functions within a company is integrated to create an effective business model. When program management is properly conceived and executed, management includes management of projects which, together, improve the Program management is the mechanism by which the work of various operating functions wit hin a company is integrated to create an effective business model. When program management is properly conceived and executed, performance of the organization. A programs success will be measured in terms of benefits. Program Management comprises a comprehensive suite of services addressing the full program life cycle and implemented by dedicated and highly skilled team members. PMP (Project Management Professional Program management practices put a continual focus on the business aspects of developing products, services and infrastructure. A skilled and competent program manager is the primary business manager on a program. We have Projects Managers that are certified and have decades of experience applying project management techniques and disciplines to client engagements in all industries. During our conceptual design phase we have scheduled a series of formal design reviews at discrete points where the design configuration involves from one level of definition to another. That is conceptual system, evolutions and design reviews. The successful implementation of system engineering principles and concepts is dependent not only on the technology issues and the process, but on management issues as well. Our BLR Engineering prepared a program management plan comprising series review meeting, audits, approval from user, risk managements, and some essential contingency plans. This program management plan guides all over activities throughout the project. 5. Risk management Risk management can therefore be considered the identification of the potential areas of risk. It is a part of the requirements and design stages in a project. Our team of experienced engineers has gone through the assessment and prioritization of risks followed by coordinated and economical application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities. One of the first steps of our risk management is the identification of the potential areas of risk. Risk shall include funding, schedule, and contract, relationships, political and technical. All of these hazardous shall be identified and evaluated and risk mitigation performed. Risk analysis should be performed as part of the risk management process for each project. Once a hazard identified as below, the steps of the risk managements process are as follows, Assess the current risk Define the acceptable level of the risk Decision on the response of the risk. Our risk management plan consists of four processes such as 1. Identification 2. Assessment 3. Analysis 4. Controls/Implementation 5. Responsibility As far as concerned about conceptual design process we may have these few types of risk only. Which are? 1. Technical Risk The possibility that technical requirement of the system will not be achieved. That is our design wont meets the system requirements adequately. We have planned to tackle such risk by remedial actions given in the table below 2. Schedule Risk The possibility that the project will fail to meet the scheduled milestones, such as those mentioned in our project plan. To tackle this issue we have identified possible cause and effects and of course the remedial actions to be taken respective 3. Cost Risk The possibility that the project will fail to meet the scheduled milestones and the cost of the project will go up and difficult to meet the budget. These are the probable risk that might be encountered and the contingency plan to overcome in the planning phase: Potential Risk 1 Difficulties in meeting up for our group member to discuss on the project due to different working schedule. Possible Solution to Risk1 Meeting to be done on every Saturday afternoon so the plans can be executed in the weekends before submitting the drafts. Ideally, meeting could also be schedule after 8 pm for a brief update on progress. Potential Risk 2 Group members have difficulties in meeting at convenient venue. Possible Solution to Risk2 Meeting can be done at any National Libraries or APMI campus when not only the environment is convenient for learning Potential Risk 3 Group member/s might fall sick and might not be able to meet for discussion. Possible Solution to Risk3 Work progress should be continually updated through email. Potential Risk 4 Group member/s may face problems in software incompatibility and in data sharing. Possible Solution to Risk4 Group member must work on common PC platform to avoid compatibility issues (e.g. one works on LINUX, and another one works on Mac Operating System and may result in unintended data corruption unable to read or edit documents. Better to work on common platform PC like Microsoft OFFICE and OpenProj for common means of compatibility. Any need of using unfamiliar program must be made known and shared so that each and everyone of the member can learn and use the new program. Potential Risk 5 Anyone of the Group member might encounter risk of data loss or corruption. Possible Solution to Risk5 Group member must regularly backup their data on their PC and must have a secondary means of backup (eg. Thumb drive or external hard drive). Seek advice from Mr. Bill Daniels through the discussion Board provided on course website. Initial Project Risk Assessment SNo Identify Hazard Hazard Assessment Causes Effects Implement / Controls Responsi- bility 1 Budget estimation unlikely 1. Substantial cost increase in the project 1. Source for more economical alternative to control spending. 2. Maintain strict accounting practice. Balaji 2 Unrealistic Projected timeline Frequently 1. Delay in project 2. Bad image for team 3. Loss due to time delay Strict to the time frame set for the work schedule and Gantt chart. Balaji 3 Disruption to System Equipment Frequently 1. Loss of Equipment 2. Delay in project 1. Constant backup. 2. Escalate of any unusual encounter. Rakesh 4 Manpower management Frequently 1. Delay in project 2. Overload of team member 1. Co-ordinate meeting regularly to delegate task and work discussion. 2. Meeting to be done on Saturday Lakshmanan 5 Group members have difficulties in meeting at convenient venue Likely 1. Delay in project 2. Substantial delay in all phases of the project Meeting can be done at any National Libraries or APMI campus when not only the environment is conducive for learning but laptop user could have access to internet wireless connection. Lakshmanan 6 Face problems in software incompatibility and in data sharing. Likely 1. Delay in document work 2. Delay in project Group member must work on common PC platform to avoid compatibility issues (e.g. one works on LINUX, and another one works on APPLE Operating System and may result in unintended data corruption unable to read or edit documents. Better to work on common platform PC like Microsoft OFFICE and OpenProj for common means of compatibility. Any need of using unfamiliar program must be made known and shared so that each and everyone of the member can learn and use the new program Rakesh 7 Group member might encounter risk of data loss or corruption. Likely 1. Loss of all details and documents. Group member must regularly backup their data on their PC and must have a secondary means of backup (e.g. Hard disk, Thumb drive). Rakesh 8 Vendor and Supplier co-ordination issue. Frequently 1. Delay in project 2. Bad image for team 3. Loss due to time delay Plan early and have back-up resources in the event existing vendor meet constraint. Lakshmanan 9 Having doubt in preparing draft. Frequently 1. Delay in project Seek advice from Mr Bill Daniels through the discussion Board provided on course website. Balaji Lakshmanan Rakesh Table2. Initial Project Risk Assessment 6. Resources required Resources are also a very important in the course of a project development. Availability of the different kinds of resources must be used satisfactorily. It is critical to establish a credible schedule because the timing of activities not only depends on the logical dependencies between them, but also on the availability of the required resources. Our group member has used as many as facilities available to achieve the required satisfaction of the information. The resources we use to accomplish the goal of acquiring the conceptual design of an amphibious car are, Hardware I. Computer  § To work on the project report development II. Computer peripherals  § To copy the draft data.  § To print the draft copy for verification. Software III. Core University 5.0 by Vitech Corporation  § To have the breakdown of the requirements  § To display the conceptual design through Flow Functional Block Diagram and Hierarchy Application Packages IV. Microsoft Project Professional 2003  § To create schedule for the entire project plan  § To design the chart for the work task allocation  § Ensure the time limited for the task is look upon V. Microsoft Word  § To type the final specification report of the project Facilities VI. Internet media  § To gain access to the video media regarding amphibious vehicle such as you tube  § To search related information regarding amphibious vehicle  § To gain access to the related websites  § To have communication with the project supervisor  § To have a convenient place to discuss the project development matters  § The usage of this media is vastly great VII. Money/Time Funds  § To have food/refreshments for members attending discussion for the entire project plan  § Towards the expenses like photocopying, phone calls, printing / copying  § To have transport facilities  § To make free ourselves on the discussion planned days. 7 Deliverables For our projects deliverables are the stuff/function that can be the result for the task implementation, it consists of things or stuff such as presentation (MSPowerpoint Slideshows), documentation requirements, total design documentation etc. The documents as deliverables used here are namely the System Engineering Management Plan, System Requirement, Functional Analysis and Allocation, and Final System Specification. System Engineering Management Plan (SEMP) This plan consists of the Scope of the Project, Work Breakdown Structure as Schedule, Cost and Product Testing method, Operation concept. It has to be executed in such a way to get the best result by assigning individual task to the respective team members thereby lead the project together with proper planning to bring the required outcome. System Requirements and Specifications (SRS) This emphasise the task that determines the needs for the product, users, designers, system and subsystems. It identifies the needs of each stakeholder. Functional Analysis and Allocation (FA A) This transforms the system level requirement into functions and analyse the behaviour of the system to get the desired result. And these functions are allocated into a physical design (component level). It can be seen in detail through Functional flow block diagram. Final system specification This document comprises all the above three documents which seeks approval from the Project director for the release of the design to Production. 8. Organisational structure We believe on team work, so at all phases the task has been evenly distributed to our team members according to their role. The process flow is as follows, getting the instruction from project director the task has been distributed to the Project Design engineer by the Project manager and also the whole project is monitored by the Project director. 9. Operational Concept The world is in needs of better and more effective and efficient vehicle that could save money, earth, resources and time of travelling which will be having the various good features when operates in both the environments. Keeping that in mind our Engineering team with the engineering skills would like to design an amphibious vehicle having capable of travelling both in road and water. i.e user friendly navigation system safety protection which will meet the customer needs as customer is mainly dependent on the effective and efficient transportation to commute in his day to day life. As the name goes, the designed Amphibious Car having the capability to travel both on land and on water promises to be more environmental friendly than any other amphibious car compared to existing or future market .The idea behind this is from the automobile researchers who have been done and many have succeeded but unable to market the vehicle as it still needs more work has to be done. Some engineers also did research beyond their imagination but some have succeeded and some are still a long way. The conceptual design of amphibious vehicle will be aimed to provide comfortable journey, trouble free service, energy efficient and environment friendly with Safety features for the customers and the features include well designed with double secured protection against water leak and corrosion of vehicles body parts by using the anti corrosive materials and fail safe controls , fuel efficient, operating at an economical way by giving good mileage and the vehicle would be engineered in way of reducing carbon dioxide emission and reducing pollution to Mother Nature as analysed by our expert engineers it would also benefit the market as a new breed of automobile needs many suitable workshop and fuel station. The vehicle has a robust designed in such a way it is very compatibility for both the conditions either it is in water or on the land. The vehicle will be operated as a boat when in water and navigation system made easy during high tides water currents and during windy seasons. The vehicle will be like normal cars when it operates on the road. The design of the bigger wheels will be providing a better ride in terrain, mud and snow and excellent traction capability with 4 gear power transmission and will provide excellent driving experience. The Vehicle will be designed to have a sportive external look. The look and feel of the designed vehicle is such that it would posses pleasant Interior colours , leg rooms spacious comfortable seatings and incorporating entertainment systems which ensures smooth and comfortable rides both on land and water. The vehicle would be cost effective under long run as the he vehicle has been designed in a way that would have less maintenance. The rugged a nd robust design assures reliability of the vehicle. The vehicle will equipped with a spare tyre and necessary tools. Our team has scheduled the conceptual design tasks and our expertise will fulfil every aspect of the customer requirement in terms of operational, maintenance and service needs and to make it big success in the market. 1. Scope 1.1 System overview Our project â€Å"Amphicar II† as the name suggests the vehicle is designed such that is viable both on land and water. It is a sports convertible full rear seat, well designed family size customer vehicle taking into account for the complete luxury as well as the safety of the customer. Customer can plan to drive right off a road or beach onto any lake or river as it is not only a luxurious car once on land but safely floats on water also because the bottom of the vehicle consists of rubber seals which forms a watertight seal. Some of the key design specification of the Amphicar II are: Its proficient 4 cylinder engine has 4 speed auto transmission forward speeds, Front wheels act as twin rudders for fast responsive handling, rear mounted for superior traction on the road, fitted with accelerator control system making the vehicle to run fuel economically both in road and water fitted with 2 rear lamps each and inbuilt side indicators, Speed O meter (digital) to display the ca rs speed, Coming to the functional aspect of the Amphicar II, once the doors are checked to be closed the customer can just drive into the water edge, and once when the car is into water, the customer is required to put land gear into neutral and then can use the facilities of the propeller or Amphibian jet by engaging it with the smaller stick which has three positions forward, neutral and reverse. Although virtually it is identical to the rest of the Amphibious vehicles, our Amphicar II distinct itself from other late models by having some of the technologies like heater placement, shock mountings, lower body lip and dash treatment and most importantly safety aspect is also considered like emergenc