Team 1
Team Member
Project Result
Team 1
Problems Encountered:
- Absence of vertical support, length of certain beams was too long.
- Addition of columns, reduce the span of beams, readjustment of flange size.
Team 2
Problems Encountered:
- The span of the beam was too long at certain points. Some places lacked vertical support.
- The structure was partially unstable.
- Shorten the length of the beam to no longer than 5 m. Add columns to places where vertical support and beam joint was needed.
Team 3
Problems Encountered:
- The span of the beam was too long at lower span. Vertical supports were almost inexistent.
- Shorten the length of the beam to no longer than 5 m, in this case add another beam. Add columns to places where vertical support was needed.
Team 4
Problems Encountered:
- Use of reinforced concrete, structure rather large, absence of vertical and longitudinal support.
- Use concrete frames (reinforced concrete) instead of traditional steel beams and columns. Shorten the span of beams and increase the number of longitudinal supports.
Team 5
Problems Encountered:
- Length of beam too long on both ends, enticing absence of vertical supports.
- Use concrete frames (reinforced concrete) instead of traditional steel beams and columns. Shorten the span of beams and increase the number of longitudinal supports.
Discussion Process
Week1:第一次會議
- 各校自我介紹
- 介紹VBR
- 成大向各校介紹模型
- 討論模組化、預鑄可能性
- 臺大:結構分析
- WSU:4D模型模擬施工
- 提出結構不完善的部分與原模型設計討論
- 臺大:優化結構
- WSU:優化4D模型
- 將建案定案,討論修改過的模型
Tools
為了交換檔案、訊息、視訊等等需求,我們使用多種通訊軟體以便進行各種資訊交換,並使用ETABS進行結構分析
通訊軟體:
通訊軟體:
- Sococo
- Google drive
- Line
團體內部與外部溝通工具簡圖
結構分析軟體:ETABS
按照成大所提供的模型,繪製結構,以靜力分析檢驗原本設定的結構是否足夠強韌或是足夠經濟。
按照成大所提供的模型,繪製結構,以靜力分析檢驗原本設定的結構是否足夠強韌或是足夠經濟。
Lesson Learned
Although described from a broader standpoint, most experiences in our group can be summarized in the following points.
- The end in mind must be very clear from the onset, with the start-point, end-point and the development part of transition points in between kept in view. What we wanted to achieve as a group? What was NTU role? How do we share a common goal?
- We need to stay focused on strategic goals and objectives of the project at all times, but remain flexible in our tactical approach.
- At the end of the day, implementation and execution of the project counts a lot on getting things done by following up and following through what has been laid out in the project plan, efficiently and effectively.
Also, we could include the following tactical initiatives that entail:
- Specific, prioritized and executable tasks that need to be accomplished at each transition point until the end-point.(Clearer common goals per week)
- Metrics for measuring progress or milestone achievements
- Accountability
- Resources that are needed to get all the work done (Software, etc.)
- Timetable for scheduled completion of each predefined task need to be spelled out clearly, as they form the strategic heartbeat of the project plan.
Key Factor to Success
- Active Participants. Without the right team in place, any strategy and plan has the potential of completely falling apart. Because of this, the core project staff should be part of the team dynamic. All of those involved must have commitment to the group, share similar visions for the projects and strive for overall success.
- Smart Planning. Comprehensive planning sets up a project for success from the start. Planning can help the team to meet deadlines and stay organized. Good planning not only keeps the project team focused and on track, but also keeps stakeholders aware of project progress.
- Open Communication. Looking closely at details and listening to outside sources of information is vital to the success of a project. Keeping open communication within the team is absolutely essential. When working under a specific timetable, it is important that the team remains well-informed. If a problem arises on one part of a project, it can negatively impact other parts as well. Communication is the best way to prevent problems from occurring.
- Careful Risk Management. As a team we know things rarely go off exactly as planned. During the planning process, it is vital to produce a risk log with an action plan for the risks that the project could face. If something happens, then the team can quickly resolve the issue with the management plan that has already been set in place. This will give the team confidence when facing project risks and help the clients feel comfortable with the project’s progression.
- Strong Project Closure. If a project does not have strong closure, then it has the potential to continue to consume resources. The project team must be firm and agree with the customer that all critical success factors have been met. Confirmation of the project delivery, testing, and release must be agreed upon and signed off. Satisfaction surveys are good forms of documentation to log and file for future reference and valuable information for use in the future.