Business Case (BC) - ynuwenhof/TINF22F_Team4_EDZ_Viewer_and_Converter GitHub Wiki
Changelog
| Version | Date | Author | Comment |
|---|---|---|---|
| 0.1 | 13.10.2023 | Mohammad Alomari | Create first draft |
| 0.2 | 19.10.2023 | Mohammad Alomari | Add costs |
| 0.3 | 19.10.2023 | Mohammad Alomari | Add offer |
| 0.4 | 19.10.2023 | Mohammad Alomari | Add purpose and Scope |
| 0.5 | 19.10.2023 | Mohammad Alomari | Add value for the customer |
| 0.6 | 19.10.2023 | Mohammad Alomari | Add expected restrictions and risks |
| 0.7 | 20.10.2023 | Mohammad Alomari | Add changelog |
| 0.8 | 20.10.2023 | Mohammad Alomari | Add timeframe |
Purpose and Scope
The EDZ Viewer and Converter is driven by a dual purpose: to enhance the usability of proprietary EDZ file formats used in ECAD component models within the EPLAN ecosystem and to facilitate the transition to the AASX format, aligning with the evolving Industry 4.0 standards. The project's scope includes the development of a user-friendly EDZ Viewer, comprehensive concept development, and implementation. Notably, it will also feature a vital EDZ to AASX conversion capability, enabling compatibility with the emerging industry standard. To ensure quality and usability, the project will undergo tests and include a documentation. Overall, it plays a crucial role in advancing ECAD component model management and contributing to the broader industry-wide shift towards Industry 4.0 compliance.
Value for the customer
| Value | Description |
|---|---|
| Improved Usability | Enhanced user-friendliness for easier visualization and management of ECAD component models, leading to increased efficiency. |
| Interoperability | Conversion feature allows transitioning from proprietary EDZ formats to AASX standard, promoting compatibility with the industry's standards and enhancing integration. |
| Cost Reduction | Simplifies ECAD component model management, reducing costs associated with maintaining and updating legacy EDZ file formats. |
| Time Savings | User-friendly interface and conversion capabilities significantly reduce the time required for EDZ file-related tasks, saving time and resources. |
| Enhanced Collaboration | Improved usability and AASX compatibility promote smoother collaboration among team members, departments, and organizations, fostering innovation and efficiency. |
| Data Integrity | The conversion process maintains data integrity during the transition from EDZ to AASX, reducing the risk of data loss or corruption. |
Expected restrictions and risks
While the project aims to be completed on time, it is important to acknowledge potential risks and restrictions. One key risk is the complexity of EDZ file formats, which may lead to unforeseen technical challenges during the development and implementation phases. Additionally, the availability of key team members is a potential restriction as they may have other commitments or unexpected disruptions, such as urgent projects from their employers or unforeseen personal events. These factors could impact the project timeline and may require contingency plans to address any delays. Furthermore, post-implementation, ongoing maintenance and updates may be necessary to address any remaining bugs or unforeseen issues, which should be factored into the project plan.
Costs
The costs are divided in several categories:
- Project Analysis: The estimation for project analysis, which includes determining the current project scope and identifying potential improvements, is approximately $8,500. These analyses will be used to present a solution to the customer via a prototype.
- Design and GUI Development: A budget of $4,250 is allocated for designing a user-friendly interface (GUI). This includes creating a concept and a prototype that meets specific customer requirements.
- Programming and Implementation: The implementation of the prototype and other points specified in the project requirements is budgeted at $18,750.
- Quality Assurance and Testing: To ensure a bug-free and functional program, $7,500 is allocated for comprehensive testing.
- Project Management: Project management, including planning, resource optimization, communication, and regular meetings, is estimated to cost $25,000.
- Documentation: The creation of all necessary documents and meeting notes for project explanation and future project understandability requires a budget of $13,000.
- Additional Costs: An additional budget of $10,000 is reserved for unforeseen expenses, such as new licenses and local costs.
| Role | Hourly Rate (in €) |
|---|---|
| Project Leader (PL) | 100 |
| Product Manager (PM) | 85 |
| System Architect (ST) | 90 |
| Test Manager (TM) | 95 |
| Technical Documentation (TD) | 90 |
| Cost Category | Estimated Cost (in €) |
|---|---|
| Project Analysis | 8,500 |
| Design and GUI Development | 4,250 |
| Programming and Implementation | 18,750 |
| Quality Assurance and Testing | 7,500 |
| Project Management | 25,000 |
| Documentation | 13,000 |
| Additional Costs | 10,000 |
| Total Cost | 87,000 |
Offer
A 20% profit margin is not only essential for business viability but also for the ability to deliver projects successfully and meet client needs in a dynamic environment. It allows us to manage risks, invest in innovation, and ensure client satisfaction throughout the project's lifecycle. Thus our initial price offer will be at 104,400€.
Timeframe
This is the initail estimated timeframe
