Ce Project Guideline Edition 5

Visayas State University
College of Engineering and Technology

Department of Civil Engineering
CEng 156
Civil Engineering Project
Guidelines
Edition 5
January 2020
Vision: A globally competitive university for science, technology, and environmental conservation
Mission: Development of a highly competitive human resource, cutting-edge scientific knowledge and innovative
technologies for sustainable communities and environment
SECTION 1
PROCEDURE AND TIMELINE
101 General Procedure and Timeline

The Civil Engineering Project course (CEng 156), or referred to as “CE Project” in
other instances of this document, shall follow this general procedure and timeline:
101.1 CE Project offering schedule and requisites

The CE Project course (CEng 156) shall be offered every second semester of the
school year only. For a student to be permitted by the academic adviser to take the
course, all the following requisites have to be satisfied:
a) 5th year standing
b) Passed all the regular offered courses of the 1st semester in 5th year
c) Attendance to the CE Project Meeting of the same school year the course is
taken
101.2 Appointment and Role of the CE Project Coordinator

At the beginning of the first semester of each school year, the Head of the Department
of Civil Engineering (DCE) shall appoint a CE Project Coordinator among the
members of the faculty of DCE. The CE Project Coordinator, referred to as
“Coordinator” in other instances of this document, shall have the following
responsibilities (a to h):
a) act as official instructor for the course
b) orient or organize the orientation of the qualified students on the course
activities and guidelines
c) guide the students on the course requirements
d) organize meetings, deliberations, and presentations relating to the course
e) facilitate the rating of students
f) represent the class in official communications, decisions, and concerns
g) set specific dates for the course activities and deadlines
h) make decisions for concerns not covered by this set of guidelines
101.3 CE Project Meeting

Within the 1st semester of the referred school year, the Coordinator shall call a CE
Project meeting to be attended by all students qualified to take the course according to
Section 101.1. The meeting shall include the following activities as necessary (a to c):
a) Orientation on the CE Project course
b) Assignment of CE Project teams
c) Setting of tentative schedules and deadlines
Page 1 of 43
101.3.1
The specific schedule and other details of the CE Project Meeting shall be set by the
Coordinator as approved by the Head of the Department of Civil Engineering.
101.4 Appointment of the Chairman for the CE Project Panel of Deliberators

After the appointment of the CE Project Coordinator, the Head of DCE shall also
appoint the chairman of the CE Project Panel of Deliberators. Automatically, the rest
of the faculty will be the members for the panel of deliberators.
101.4.1
The CE Project Panel of Deliberators, which is referred to as “Panel” in other
instances in this document, shall be composed of one chairman, and not less than
three but not more than six members.
101.4.2
Only members of the faculty of the Department of Civil Engineering at Visayas State
University may be appointed as members or chairman.
101.5 Submission and Deliberation of Project Proposals

Each team shall compose and submit a Project Proposal to the Panel through the
Coordinator. Project Proposals shall comply with Section 302. After submission, each
team shall privately meet with the Panel to briefly present and deliberate the project
proposal. This meeting is referred to as Project Proposals Deliberation detailed in
Section 303.
101.5.1
The specific deadline and other details for the submission of project proposals shall be
set and announced by the Coordinator.
101.5.2
The specific schedule and other details for the Project Proposals Deliberation shall be
set and announced by the Coordinator.
101.6 Pre-conduct Activities

When granted project approval after Project Proposal Deliberation, a team shall
perform and complete the necessary pre-conduct activities as given in Section 401.
101.6.1
The specific time period and other details of the pre-conduct activities shall be set and
announced by the Coordinator.
101.6.2
A special time frame for the pre-conduct activities may be arranged with the
Coordinator upon request by a team.
Page 2 of 43
101.7 Start of Conduct of the Project
After completion of the necessary pre-conduct activities, a team shall be granted
permission by the Coordinator to begin the formal conduct of the project.
101.8 Project Progress Report

On the 8th week of the 2nd semester, each team conducting a project shall submit to
the Coordinator a Project Progress Report detailing the current progress of the project
conduct. The guidelines for this report is given by Section 5.
101.8.1
The specific deadline and other details for the submission of Project Progress Report
shall be set and announced by the Coordinator.
101.9 Submission of Project Manuscript for Project Defense

All teams actively involved in CE projects shall compose and submit to the Panel,
through the Coordinator, a complete project manuscript compliant with Section 7 and
endorsed by their adviser/s, to be used for the Project Oral Defense.
101.9.1
The specific deadline and other details for the submission of the project manuscript
shall be set and announced by the Coordinator. This deadline shall be set not later
than three (3) days before the scheduled first Project Oral Defense Session.
101.10 Project Oral Defense

After submission of the complete project manuscript, each team shall meet with the
Panel to present and defend the project. The Panel shall decide for the approval,
disapproval, or other special verdict for each project. This activity shall be referred to
as Project Oral Defense. The guidelines for this activity shall be referred from Section
6.
101.10.1
The specific schedule and other details for the Project Oral Defense shall be set and
announced by the Coordinator.
101.11 CE Project Presentations

All teams that have successfully completed the project conduct shall publicly present
their project during a formal academic gathering organized or designated by the
Coordinator.
101.12 Submission of Approved Project Manuscript

All teams granted “Approved” status by the Panel for their CE Project shall submit a
complete and revised Project Manuscript approved by the Panel. Each team is
required to submit (a to b):
Page 3 of 43
a) two (2) hard copies of the approved Project Manuscript compliant with
Section 7.
b) digital copy of the approved Project manuscript compliant with the digital
format prescribed by the Coordinator.
101.12.1
The specific deadline and other details for the submission of the approved Project
Manuscript shall be set and announced by the Coordinator.
101.13 Rating
After submission of the approved Project Manuscript, each team member is required
in the rating procedure according to Section 8.
Page 4 of 43
SECTION 2
PROJECT CATEGORIES
201 Description of CE Project categories

The following items enumerate and describe the categories of CE Projects.
201.1 Community Solution / Community Extension
201.1.1 Goal
The goal of a community solution project is to help a community by providing
solution/s or introduce opportunities for development using concepts, knowledge, or
techniques related to Civil Engineering.
The community extension variant project involves helping the community by teaching
or training members of the community in addressing the problem/s or introduce
opportunities for development using concepts, knowledge, or techniques related to
Civil Engineering.
201.1.2 Project Summary

In this category of project, a team immerses into a community and scouts for
community concern/s or opportunities for development that may be addressed by
Civil Engineering concepts, knowledge, or techniques. When a suitable community
concern is noted, the team meets with community leader/s (e.g. barangay captain,
Mayor) or members to plan out solutions or actions. The team develops a solution
through Civil Engineering knowledge and application, then presents it to the
community and/or to a higher authority that can facilitate implementation. If the
conditions permit especially in view of funds and time, the team may opt to pursue
implementation of the proposed solution. For the extension variant, the team equips
the community members with the required knowledge and skills required for
addressing the problem. The team documents the entire work to produce a short
documentary.
201.1.3 Project Output

For this category of project, the following items are the required tangible outputs (a to
c):
a) Project Manuscript – The required content and specifications of this item is
detailed in Section 7.
b) Short Documentary – The team shall create a short video documentary
summarizing their work. The video shall contain brief depictions about the
community, the community problem being addressed, the work done by the
team in attaining a solution, and the conclusion of the entire work. The
duration of the video is preferably within 8 to 15 minutes. This output is
required for the CE Project Presentations. Additional specifications for this
output, if there be any, shall be set by the Coordinator.
Page 5 of 43
c) Presentation Kit – The team shall produce a kit to be used for the CE Project
presentation of the project. This kit shall include an illustrated poster and
digital presentation (e.g. Powerpoint presentation). Additional specifications
for this output, if there be any, shall be set by the Coordinator.
201.2 Innovation / Invention
201.2.1 Goal
The goal of invention or innovation is to help improve technology by presenting
unique concepts for structures, machines, or systems that feature improved efficiency,
economy, safety, sustainability, environmental conservation, or newly discovered
functions.

In this category of project, a team proposes a concept that potentially contributes to
the development of technology. An invention or innovation concept may be in a form
of a structure, machine, physical product, or system. The team produces prototype/s of
the concept then determines and performs relevant tests to establish the proof of
concept. The team continuously improves or revises the details of the concept until
the proof of concept is attained. The team documents the tests and discusses their
implications and potentials for development.

For this category of project, the following are the required tangible outputs (a to c):
b) Prototype/s for Presentation – The team shall produce at least one prototype
that will show the proof of concept of the invention or innovation. This output
is required for the CE Project Presentations. The prototype/s shall be
constructed as such that it is safe for public presentation.
c) Presentation Kit – The team shall produce a kit to be used for CE Project
presentation. This kit shall include an illustrated poster and digital presentation
(e.g. Powerpoint presentation). Additional specifications for this output, if
there be any, shall be set by the Coordinator.
201.3 Design / Development
201.3.1 Goal
The goal of design or development project is to render technical service to a client by
producing detailed plan/s for a proposed structure, system, or area development
requiring Civil Engineering knowledge and techniques.
Page 6 of 43
In this category of project, a team first with the client to gather information on the
client needs and preferences on the building or development project. The team then
performs necessary survey and site investigation procedures in preparation for actual
design or development. With the use of Civil Engineering knowledge and techniques,
the team produces detailed plans for the structure, system, or area development. Plan/s
should be compliant with the recognized standards, such as building codes, structural
codes, plumbing and electrical codes, and fire safety codes, among others, whichever
are relevant. Finally, the team submits the detailed plan/s to the clients for review or
further decisions. The designs and documents produced by the team shall be
considered interim documents properly notated “for review only” and should be
subject to proper review and approval by licensed professionals wherever necessary.

For this category of project, the following are the required tangible outputs (a to c):
b) Visualization product – The team shall create a product that will help visualize
the design or development plan. This may be in a form of a scaled model, 3D
digital model, set of augmented reality images, etc. This output is required for
the CE Project Presentations.
c) Presentation Kit – The team shall produce a kit to be used for CE Project
presentation. This kit shall include an illustrated poster, digital presentation
201.4 Experimental Research
201.4.1 Goal
The goal of experimental research is to produce reliable scientific knowledge through
a defined experimental method that is replicable and reproducible.

In this category of project, the team proposes hypothesis/es or research objective/s
within the scope of the Civil Engineering science or technology. The team designs
and conducts an acceptable experimental procedure in order to draw conclusions on
the hypotheses or address the research objectives. The team collates the experimental
observations, analyzes them in detail, and makes thorough discussions to arrive at
objective conclusions. Finally, the team provides recommendations to help direct
further research efforts on the topic.
Page 7 of 43
For this category of project, the following are the required tangible outputs (a to b):
a) Research Manuscript – The required content and specifications of this item is
b) Presentation Kit – The team shall produce a kit to be used for CE Project
presentation. This kit shall include an illustrated poster, digital presentation
(e.g. Powerpoint presentation), and tangible research samples or products if
applicable. Additional specifications for this output, if there be any, shall be
set by the Coordinator.
201.5 Theoretical Study
201.5.1 Goal
The goal of theoretical study is to derive further knowledge on theoretical aspects of
the science of Civil Engineering.

In this category of project, a team determines a theoretical problem related to Civil
Engineering and discusses it in detail. The problem may be in the form of
optimization, development of a computational method, scrutiny of possible flaws in a
current design method, or other studies of theoretical nature that are related to Civil
Engineering.

a) Manuscript – The required content and specifications of this item is detailed in
Section 7.
201.6 Feasibility Study
201.6.1 Goal
The goal of feasibility study is to determine whether a proposed project is possible,
reasonable, and practical, or not. The purpose of the study is to increase confidence in
decisions pertaining to the proposed project before it is undertaken.

In this category of project, a team considers a proposed project by a client to be
evaluated for feasibility. The team gathers all the necessary information to establish
the concept of the proposed project. The team defines specific criteria to be evaluated
and develops the methods for analyzing each. The team then performs the evaluation
Page 8 of 43
and makes detailed discussions for each criterion in relation to the feasibility of the
proposed project. Finally, a general conclusion is drawn from the discussions and
communicated to the client/s or proponents of the project, if applicable.

201.7 Case Study
201.7.1 Goal
The goal of case study is to derive knowledge from a particular case related to Civil
Engineering through a thorough examination.

In this category of project, a team considers a specific case related to Civil
Engineering. The type of case depends on the purpose of the study. An illustrative
case study may be performed to confirm and show the occurrence of a specific
phenomenon previously theorized. An exploratory case study may be performed to
investigate an underlying phenomenon that have not been previously theorized, or to
reinforce those that have been trivialized. A cumulative case study can be performed
by aggregating information about a particular subject to create a more generalized
information about the subject. And a critical instance case study may be performed by
examining a case of unique interest with little concern for generalizability, rather to
call into attention possible flaws of a previous assertion or make a new assertion. The
team documents their findings, analyses and discusses them. Then the team derives
conclusions and recommendations from the analysis.

Page 9 of 43
202 Off-category Projects
Projects that cannot be categorized according to Section 201 may be conducted as a
result of approval of such through Section 302.2. These projects are referred to as
“off-category projects” in other instances of this document.
202.1
Teams to conduct or conducting off-category projects shall follow the same general
timeline as provided in Section 1.
202.2
The pre-conduct procedures, required project outputs, manuscript contents and
specifications, and other specifications of off-category projects shall be set by the
Coordinator upon due discussion with the team and adviser.
Page 10 of 43
SECTION 3
PROJECT PROPOSALS
301 General Guidelines

The following are the general guidelines on CE Project Proposals.
301.1
The Coordinator, with consultation with the faculty of Civil Engineering, shall set
and announce during the CE Project meeting the categories of project available or
open for proposal submission for the referred school year.
301.2
The Coordinator shall encourage and perform measures that will likely result in the
diversity of project categories of the teams. The Coordinator, with consultation with
the faculty of Civil Engineering, may set a reasonable limit for the number of projects
to be accepted for a given category of project.
301.3
In the case that the number of submitted project proposals for one or more categories
exceeds the set limit, the Panel, during the Project Proposals Deliberation, shall grant
approval only to a number of project proposals such that the set limit for each
category is satisfied.
302 Project Proposals Submission

The Project Proposals to be submitted for deliberation shall comply with this section
for the contents and discussion.
302.1 Content of Project Proposal

The contents of Project Proposal specific for each category shall compose the
following.
302.1.1 Community Solution / Extension
I. TITLE
This is the statement of the proposed title of the project.
II. THE TARGET COMMUNITY

This chapter shall contain a brief description of the community where the project is
targeted on. It should include for the least the details on the location, size, estimated
population, dialect, safety concerns, estimated distance from the university, etc.
Page 11 of 43
III. COMMUNITY CONCERN OR OPPURTUNITIES
This chapter shall contain a brief description of the observed problem/s in the
community or opportunity/ies for development that may be addressed by Civil
Engineering. This also includes the indication of the proposed type of project whether
Solution type or Extension variant.
IV. IMPORTANCE OF THE PROJECT

This chapter shall contain a brief discussion on the perceived importance of the
project based on its possible impact to the community.
V. FUNDING OR SUPPORT PLAN

This chapter shall contain an enumeration and estimate of all possible expenses on
conducting the project (e.g. transportation, materials, printing services, etc), and the
team’s plan on how these expenses will be addressed (e.g. personal expenses, funding
agency, client’s funding, government agency, etc.). If funding or support has already
been secured, describe its mechanics and explain the level of its security.
302.1.2 Innovation / Invention
I. TITLE
II. INNOVATION CONCEPT *(if invention, INVENTION CONCEPT)

This chapter shall contain a brief discussion on the proposed innovation or invention
concept.
III. IMPORTANCE OF THE CONCEPT

This chapter shall contain a brief discussion on the importance of the invention or
innovation concept based on its potential for development and its impact to science
and technology.
IV. PROTOTYPING AND EVALUATION METHODS

This chapter shall contain the discussions on the possible methods of producing the
prototypes, and the foreseen preliminary tests that have to be done in order to evaluate
or establish the proof of concept of the invention / innovation concept.

Page 12 of 43
302.1.3 Design / Development
I. TITLE
II. PROJECT DESCRIPTION

This chapter shall present the following information about the proposed structure to
be built or development to be made: Physical description (type of structure/s, location,
conceptual shape and size, estimated number of floors etc.); Client information
(Name, location; if company or agency: company name and address); Client’s Project
Rationale (Brief explanation on the client’s rationale on proposing the structure or
development); Estimated budget of the project; Estimated project time frame.
III. KNOWLEDGE & WORK REQUIREMENT

This chapter shall contain the discussion about the engineering topics or subjects
necessary for the design or development process, and the nature of work required
during the planning and design stage. This chapter is meant to evaluate whether
additional specific knowledge is needed for the project, as well as assess if there are
health and safety risks to the team.
IV. FUNDING OR SUPPORT PLAN

302.1.4 Experimental Research
I. TITLE
II. INTRODUCTION
This chapter shall contain the following items:
Nature and Background of the study – this explains how the proposed study was
conceptualized, and its foreseen importance.
Objectives / Hypotheses – this item contains the explicit statement of the objectives or
hypotheses of the study.
Scope and Limitations – this item explains the extent of the study.
Time and Place of the study – this item contains the proponents’ declaration of the
preferred time period and place of conduct of the study
Page 13 of 43
III. REVIEW OF LITERATURE
This chapter shall contain an organized review of some related studies that help
establish the viability of the objectives or hypotheses, and serve as guide to the
materials and methods.
IV. MATERIALS AND METHODS

Materials – this item shall contain the enumeration and description of the materials
needed for the study.
Methods – this item shall contain the discussion on the procedure in testing the
hypotheses or in attaining the objectives. The Experimental Design and Statistical
Analysis method, if necessary, should be discussed in this item.
V. REFERENCES
This chapter shall contain the list of referenced literature and documents mentioned in
the proposal.
VI. FUNDING OR SUPPORT PLAN

302.1.5 Theoretical Study
I. TITLE
II. THEORETICAL PROBLEM

This chapter shall contain the statement of the theoretical problem. It may contain a
discussion on the background, nature, or history of the theoretical problem, etc.
III. IMPORTANCE OF THE STUDY

This chapter shall contain the discussion on why it is important to find the solution to
the theoretical problem stated.
IV. KNOWLEDGE, METHODS AND TOOLS

This chapter contains an enumeration of the background knowledge needed for the
solution, the possible procedure in finding the solution, and the tools needed for
finding the solution (e.g. high end computer, surveying equipment, specific software,
etc.)
Page 14 of 43
302.1.6 Feasibility Study
I. TITLE
II. PROPOSAL IN QUESTION

This chapter shall contain the description of the proposed system or structure, (e.g.
proposal two-story commercial) that must be checked for feasibility, the relevant
background details about the client, and the client’s rationale for proposing the
project.

This chapter discusses why it is important to undertake a feasibility study for the
specific proposal in question.
IV. FEASIBILITY CRITERIA AND METHODS

This chapter shall contain the enumeration of the feasibility criteria that have to be
considered and, under each criterion, the discussion on the procedure of evaluating
each criterion.

302.1.7 Case Study
I. TITLE
II. THE CASE

This chapter shall contain the general description of the case. It may contain a
discussion on the background, nature, or history of the case, etc.
Page 15 of 43
This chapter discusses why it is important to investigate the particular case.
IV. METHODS
This chapter shall contain the discussion on the procedures to be performed to
investigate the case, and the method of analysis.

302.2 Off-category project proposals

The Panel shall consider project proposals that cannot be classified into the given
categories in Section 201, or called off-category projects with the conditions stated in
Section 302.2.1.
302.2.1
The contents (chapter titles and discussions) of off-category project proposals will be
based on the proponent’s prerogative, as long as it satisfies the following (a to f):
a) The proposal shall contain, for the least, the following mandatory chapters:
TITLE and FUNDING OR SUPPORT PLAN.
b) The proposal contains evidences that the nature of the project is in line with
the BSCE program targeted outcomes and should involve knowledge and
skills in the science of Civil Engineering.
c) The proposal contains evidences that the project will benefit a client, a certain
community, or the scientific community.
d) The proposal discusses the importance of the project.
e) The proposal discusses the possible safety and health risks to the team in
conducting the project.
f) The proposal includes evidences that the project can be conducted within the
period of time permitted by the CE Project course.
302.3 Formatting Specifications and Illustrations

The formatting specifications for Project Proposals shall be provided by the
Coordinator. Inclusion of relevant photos or other illustrations in the Project Proposal
is encouraged.
Page 16 of 43
303 Project Proposals Deliberation Procedure and Rules
After submission of a Project Proposal, the team shall present and discuss the
proposal with the Panel in a scheduled Project Proposals Deliberation session. The
following items describe the procedure and rules for the Project Proposals
Deliberation.
303.1
During the Project Proposals Deliberation session, each team shall be allotted a total
of 20 minutes for presentation and deliberation of the proposal with the Panel. A
maximum of 10 minutes shall be allotted for the team to personally present their
Project Proposal with any preferred aid (e.g. digital presentation, drawings, models).
Immediately after the presentation, the remaining time shall be allotted for oral
deliberation with the Panel.
303.1.1
The presentation should contain for the least the following:
Team name
Names of the proponents
Brief version of each chapter in the project proposal
303.1.2
The given time allotment mentioned in Section 303.1 shall be considered prescribed
values only. The Coordinator has the prerogative to use different time allotment
values to optimize the conduct of the Project Proposals Deliberation session/s.
303.2
After the deliberation with each team, the Panel shall privately discuss to decide
whether to approve or disapprove the project proposal. This procedure and its details
shall be facilitated by the Coordinator.
303.2.1
The Panel may decide to give a proposal “conditionally approved” status if it requires
only minor revisions for it to be considered acceptable.
303.3
If after the Project Proposals Deliberation session, one or more proposals are not
approved, the teams with disapproved proposals shall submit another Project Proposal
and meet with the Panel on a remedial Project Proposals Deliberation session
organized by the Coordinator.
303.3.1
Teams with proposal on “conditionally approved” status have two options as follows
(a to b):
a) apply the necessary revisions on the first proposal and submit the revised
Page 17 of 43
proposal for the remedial Oral Deliberation
b) submit a new proposal for remedial Oral Deliberation
303.4
The specific schedule, procedure, and other details for the remedial Project Proposals
Deliberation shall be set and announced by the Coordinator.
303.5
If a team’s Project Proposal is not approved after the remedial Project Proposals
Deliberation session, all members of the team shall not be permitted by their academic
advisers to enroll the CE Project course on the referred school year, or shall be
dropped from the CE Project course in case they are already enrolled in the course.
303.6
Immediately after all necessary Project Proposals Deliberation sessions have been
concluded, the Coordinator shall produce a report of the teams whose proposals have
been approved and shall distribute copies of this report to the Head of DCE and to the
academic advisers of all the concerned students.
303.7
Other details on the Project Proposals Deliberation not mentioned in Section 303,
such as dress code and ordering of presentations, shall be set and announced by the
Coordinator.
Page 18 of 43
SECTION 4
PRE-CONDUCT ACTIVITIES AND DOCUMENTATION
401 Pre-conduct Activities

When a project proposal receives approval from the Panel, the referred team shall
perform necessary activities to prepare for the conduct of the project. These activities
shall be referred to as “pre-conduct activities” in other instances of this document.
401.1 General Guidelines
401.1.1
A team may only be granted permission by the Coordinator to begin formal conduct
of the project when all necessary pre-conduct activities are accomplished.
401.1.1.1
The necessary pre-conduct activities shall compose of the mandatory pre-conduct
activities as given by Section 401.2, and other necessary pre-conduct activities
determined by the Coordinator and the team depending on the nature of the project.
401.1.2
For other necessary pre-conduct activities not covered by Section 401.2, the
Coordinator shall prescribe the guidelines for such.
401.2 Mandatory Pre-conduct Activities

The following items enumerate and describe the pre-conduct activities that are
required for all projects.
401.2.1 Call for Project Adviser/s

Each team to conduct a project is required to have at least one and at most two project
adviser/s.
401.2.1.1
The responsibilities of a project adviser shall be as follows (a to d):
a) Provide general advice for the team pertaining to the project.
b) Decide for the endorsement of the team’s project for Project Oral Defense.
c) Decide for the endorsement of the team’s Final manuscript for submission to
the Faculty of Civil Engineering.
d) Participate in the rating of the team members according to Section 8
401.2.1.2
If a team opts to call one project adviser, he/she should have the following
qualifications (a to c):
Page 19 of 43
a) should be a member of the faculty of the Department of Civil Engineering of
Visayas State University
b) should be in regular appointment status
c) should be in active working status (not on study leave or sabbatical leave or
the like)
401.2.1.3
If the team decides to call two project advisers, it is mandatory that one of the
advisers satisfy the qualifications in Section 401.2.1.2. The second adviser should
have following qualifications (a to c):
a) should be a licensed Civil Engineer or an expert in the field relating to the
team’s project
b) should be a member or affiliated to the faculty of a recognized tertiary
academic institution
c) should have good personal standing, without criminal record or the like
401.2.1.4
In calling for project adviser/s, each team shall send a formal letter/s stating the
request.
401.2.1.4.1
The letter of request for project adviser shall include the statement of the roles of the
adviser according to Section 401.2.1.1.
401.2.1.4.2
The letter of request for project adviser shall be signed by all members of the team
and noted by the Coordinator.
401.2.1.4.3
Each team shall submit one original copy of the request letter to the Coordinator and
submit another copy to the Department of Civil Engineering administrative office for
archiving.
401.2.1.5
If the request is approved, the team shall accomplish an acceptance note to be signed
by the project adviser.
401.2.1.5.1
The specific format for the acceptance note shall be provided by the Coordinator.
401.2.1.5.2
Each team shall submit one original copy of the acceptance note to the Coordinator
and submit another copy to the Department of Civil Engineering administrative office
for archiving.
Page 20 of 43
401.2.2 Project Planning
Each team to conduct a project shall create an overall Project Plan to guide the
conduct of the project.
401.2.2.1
The Project Plan shall be accomplished before processing the Parental Consent
document as given by Section 401.2.3.
401.2.2.2
The printed Project Plan may be in the form of a Gantt chart, Precedence Diagram or
the like, and supplemented by discussions or notes if necessary.
401.2.2.3
Other specifications for the printed Project Plan shall be set by the Coordinator.
401.2.2.4
The Project Plan may be continuously revised as the project progresses. Whenever
there are revisions, the team shall carefully document the changes including the exact
dates.
401.2.3 Parental Consent

Each student to involve in the conduct of a project shall accomplish a printed and
signed Parental Consent document and duly notarized by an attorney-at-law.
401.2.3.1
The specific format of the Parental Consent document shall be set by the Coordinator.
401.2.3.2
Each student shall submit one original copy of the notarized Parental Consent
document to the Coordinator and submit another copy to the Department of Civil
Engineering administrative office for archiving.
402 Official Communication Documents

Depending on the nature and extent of work in a project, a team may need to
accomplish certain official communication documents. These documents may include
the following:
a) Letter of request for permission
b) Letter of request for assistance
c) Letter of request for information
d) Other communication documents
Page 21 of 43
402.1
Formal communications with any authority, client, agency, or individual shall be
properly supplemented with printed documents.
402.2
All official communication documents addressed to an authority, client, agency, or
individual shall be signed by all members of the team and noted by at least one project
adviser and the Head of DCE.
402.3
Each team shall submit one original copy of the official document to the Coordinator
and submit another copy to the Department of Civil Engineering administrative office
for archiving.
Page 22 of 43
SECTION 5
PROJECT PROGRESS REPORT
501 Contents of the Project Progress Report

The following are the required contents of the report.
501.1 Title Page

The title page shall contain the title of the project, the team name, and complete
names of the project proponents.
501.2 Primary Contents

The report shall contain the following chapters:
I. WEEKLY ACTIVITIES
This chapter contains the brief narration of activities done per week from the
beginning of conduct to the 8th week of the second semester.
II. PROBLEMS / CONCERNS

This chapter contains an enumeration and discussion of some problems or concerns
encountered so far in the conduct.
501.3 Updated Project Plan

The team shall attach to the Project Progress Report the latest Project Plan complete
with graphical indication of the progress for each activity and the overall progress.
502 Formatting Specifications and Illustrations

The formatting specifications for the Project Progress Report shall be set by the
Coordinator. Inclusion of relevant photos or other illustrations in the report is highly
encouraged.
Page 23 of 43
SECTION 6
PROJECT ORAL DEFENSE
601 Project Oral Defense Procedure and Rules
601.1
During the Project Oral Defense session, each team shall be allotted a total of 30
minutes for presentation and deliberation of the project with the Panel. A maximum
of 15 minutes shall be allotted for the team to personally present their Project with
any preferred aid (e.g. digital presentation, drawings, models). Immediately after the
presentation, the remaining time shall be allotted for deliberation with the Panel.
601.1.1
The presentation should contain for the least the following:
a) Title of the Project
b) Team name
c) Names of the proponents
d) Brief version of each chapter in the project manuscript
e) Overall reflections or outstanding lessons
601.1.2
The given time allotment mentioned in Section 601.1 shall be considered prescribed
values only. The Coordinator has the prerogative to use different time allotment
values to optimize the conduct of the Project Oral Defense session/s.
601.2
During the Project Oral Defense session, each member of the Panel shall rate the
team according to Section 8.
601.2.1
In the case that the team’s adviser is a member of the Panel, he/she shall not
participate in rating the team for the Project Oral Defense Session.
601.3
After the deliberation with each team, the Panel shall privately discuss to decide to
approve or disapprove the project. This procedure and its details shall be facilitated by
the Coordinator.
601.3.1
Team members of projects that have been given “disapproved" status by the Panel
shall be marked “failed” in the CE Project course.
Page 24 of 43
601.3.2
The Panel may decide to give a project “conditionally approved” status if it requires
only minor revisions for it to be considered acceptable.
601.4
If after the Project Oral Defense session, one or more projects are given
“conditionally approved” status, the teams shall submit a revised project manuscript
and meet with the Panel on a remedial Project Proposals Oral Defense session
organized by the Coordinator.
601.4.1
The specific schedule, procedure, and other details for the remedial Project Oral
Defense shall be set and announced by the Coordinator.
601.4.2
During the remedial Project Oral Defense session, each member of the Panel shall
rate the team according to Section 8. The rating for this session shall govern the
team’s rating for Project Oral Defense.
601.4.3
In the case that the team’s adviser is a member of the Panel, he/she shall not
participate in rating the team during the remedial Project Oral Defense Session.
601.4.4
If a team’s project is not approved after the remedial Project Oral Defense session, all
members of the team shall be marked “failed” in the CE Project course.
601.5
Other details on the Project Oral Defense not mentioned in Section 601, such as dress
code and ordering of presentations, shall be set and announced by the Coordinator.
Page 25 of 43
SECTION 7
PROJECT MANUSCRIPT
701 Manuscript Contents

This section describes the required contents of the CE Project manuscript to be
published.
701.1 General
701.1.1
The primary contents provided in Section 701.3 shall be considered prescribed
contents. Deviation from these prescribed contents is permitted if there is evidence of
the need as validated by the primary project adviser.
701.1.2
The chapter contents in Section 701.3 not prescribing specific items should be
organized into items and sub-items as necessary.
701.2 Summary of Contents
701.2.1 Contents and Arrangement

The Project Manuscript shall contain the following elements arranged in the specific
order as follows (a to l):
a) Title Page
b) Abstract
c) Approval
d) Transmittal
e) Acknowledgement
f) Table of Contents
g) List of Figures
h) List of Tables
i) List of Appendices
j) Primary Contents as described in Section 701.3
k) References
l) Appendices
701.2.2 Definition of Contents

The manuscript contents are defined as follows (a to l):
a) Title Page – the first page of the manuscript displaying the title of the project,
the category of project, the names of the proponents, and the month and year
of publishing.
b) Abstract – a brief textual summary of the primary contents usually contained
in one or two pages.
Page 26 of 43
c) Approval – certifies that the project has been subjected to deliberation and is
approved by the panel of deliberators.
d) Transmittal –the document declaring the approval of turnover of the project
and manuscript from the project adviser to the department or faculty.
e) Acknowledgement –the author/s’ textual recognition of the project
contributors.
f) Table of Contents –the section listing all contents of the manuscript and their
respective page assignments.
g) List of Figures – the list of all figures contained in the manuscript and their
h) List of Tables – the list of all tables contained in the manuscript and their
i) List of Appendices – the list of all appendices contained in the manuscript and
their respective page assignments.
j) Primary Contents – see Section 701.3.
k) References – the section listing the references or sources cited in the primary
contents. See Section 702.5 for formatting details.
l) Appendices – the section/s containing the information, text, or illustrations
that are not intended to be placed within the primary contents.
701.3 Primary Contents

The primary contents of project manuscript for each category of project shall be as
follows.
701.3.1 Community Solution / Extension

For a project under Community Solutions / Extension category, the manuscript
primary contents shall compose the following chapters.
CHAPTER I. OBJECTIVES
This chapter only contains the formal statement of the project’s objective/s. For an
objective to be considered acceptable, it should be specific, direct, and verifiable. For
an objective to be considered verifiable, the proponents should be able to clearly state
at the end of the project whether that objective was accomplished or not.
CHAPTER II. COMMUNITY & PROBLEM

The purpose of this chapter is to give the readers a picture of the community and the
problem. The readers should also understand how the problem is affecting the
community. This chapter contains the information about the community where the
problem was discovered, and the discussion about the community problem. It should
discuss the implications of the problem to the community life, its effects to the
community if not addressed properly.
Page 27 of 43
CHAPTER III. INVESTIGATION & ANALYSIS
The purpose of this chapter is to make the readers know how the proponents
investigated the problem, and how they analyzed the problem towards coming up with
the solution. This chapter contains the discussion on the methods performed by the
proponents to investigate the community problem, and the analysis of the information
gathered after investigation.
CHAPTER IV. PROPOSED SOLUTION & WORK

This chapter is meant for explaining to the readers the solution proposed after the
analysis. It also aims to let the readers understand the work ahead to be done to
ultimately address the problem in the community. This chapter contains the proposed
solution to the community problem based on the analysis, and the discussion on how
this solution will be properly implemented.
CHAPTER V. RECOMMENDATIONS
This chapter enumerates and briefly discusses the recommendation/s for further work
to be done to enhance the solution or to make it more sustainable.
701.3.2 Innovation / Invention

For a project under Innovation / Invention category, the manuscript primary contents
shall compose the following chapters.
CHAPTER II. INNOVATION CONCEPT *(if invention, INVENTION CONCEPT)

The purpose of this chapter is to let the readers understand the flow of ideas that led to
the formation of the innovation / invention concept. The chapter should also give the
readers a scientific basis of the concept presented. This chapter contains the
discussion on the innovation / invention concept and the explanation of its scientific
background or basis.
CHAPTER III. METHODS & TESTING

This chapter explains to the readers how the concept was furnished and implemented
into a prototype or pilot product. Through this chapter, the readers should also be
informed about the testing procedures performed on the prototype and understand
how these tests relate to the development of the innovation / invention concept. This
chapter outlines the procedures performed by the proponents about the development
of the innovation / invention concept towards the creation of a prototype. It also
contains a comprehensive discussion of the tests performed on the prototype.
Page 28 of 43
CHAPTER IV. RESULTS & DISCUSSION
This chapter reports to the readers the results of the tests performed on the prototype,
and to make them understand the meaning of such results. This chapter contains the
report of the results of the tests performed and their corresponding interpretations and
further discussions.
This chapter enumerates and briefly discusses the proponents’ recommendation/s for
further development concerning the study.
701.3.3 Design / Development

For a project under Design / Development category, the manuscript primary contents
shall compose the following chapters.
CHAPTER II. PROJECT BACKGROUND

Project Description – this item informs the readers about the client’s desired
description of the structure to be built (e.g. type of structure, location, conceptual size
and shape, number of stories, functionalities, etc.)
Client Information – this item briefly informs the readers about the client (e.g. Name,
location; if company or agency: company name and address, etc.)
Project Rationale – this item explains the client’s rationale of proposing the structure
or development.
Estimated Budget and Timeframe – this item informs the readers about the client’s
budget for the project and preferred period of implementation.
*More items may be included in this chapter as necessary to discuss about the
proposed design / development project’s background.
CHAPTER III. DESIGN PROCESS *(if development, DEVELOPMENT PROCESS)

The purpose of this chapter is to explain to the readers the entire process of the design
/ development. This chapter discusses in detail the complete design / development
procedure performed by the proponents in producing the proposed design /
development plan. This includes discussions on the design considerations,
computational analysis, methods of implementation, etc.
Page 29 of 43
CHAPTER IV. PROPOSED DESIGN *(if development, PROPOSED
DEVELOPMENT)
This chapter discusses to the readers the general description of the proposed design /
development produced by the proponents. This chapter preferably contains the
discussion of the conceptual shape and size of the final structure or development,
features, materials, methods of implementation, etc. This chapter should also contain
the quotations of the location of the design / development drawings and project plans
in the appendices.
This chapter enumerates and briefly discusses the proponents’ recommendation/s for
further work or improvement and sustainability of the design or development project.
701.3.4 Experimental Research

For a project under the experimental research category, the primary contents shall
follow the prescribed chapters in the experimental research type undergraduate thesis
manuscript of the university where the manuscript will be published.
CHAPTER I. INTRODUCTION
Nature and Importance of the study – this explains to the readers how the proposed
study was conceptualized, and its foreseen importance.
Objectives / Hypotheses – this item explicitly states the objective/s or hypothesis/es of
the study. For an objective or hypothesis to be considered acceptable, it should be
specific, direct, and verifiable. For an objective or hypothesis to be considered
verifiable, the proponents should be able to clearly state at the end of the project
whether that objective was accomplished or not, or the hypothesis answered with true
or false.
Scope and Limitations – this item explains the extent of the study.
Time and Place of the study – this item contains the information about the time period
and place of the conduct of the study
CHAPTER II. REVIEW OF RELATED LITERATURE

This chapter elaborates each element involved in the study, quoting established
related knowledge from previous studies.
CHAPTER III. METHODOLOGY

Materials – this item shall contain the enumeration and description of the materials
used in the study.
Methods – this item shall contain the discussion on the procedure in testing the
hypotheses or in attaining the objectives of the study. The Experimental Design and
Statistical Analysis method, if necessary, should be discussed in this item.
Page 30 of 43
CHAPTER IV. RESULTS & DISCUSSION
This chapter reports to the readers the results of the methods performed, and discusses
its interpretation based on scientific analysis.
CHAPTER V. CONCLUSION & RECOMMENDATIONS

Conclusion – this item states and explains the answer/s to the hypothesis/es or
objective/s.
Recommendations – this item enumerates and briefly discusses the recommendations
for further study.
701.3.5 Theoretical Study

For a project under Theoretical Study category, the manuscript primary contents shall
compose the following chapters.
CHAPTER II. THE PROBLEM

This chapter contains the explicit statement of the problem, discussions on its
background and importance, related studies, and other discussions related to the
problem.
CHAPTER III. METHODS & ANALYSIS

This chapter explains to the readers in detail the methods and analysis performed in
tackling the problem.
CHAPTER IV. RESULTS & DISCUSSIONS

This chapter presents to the readers the results of the analysis and discusses their
implications.
This chapter enumerates and briefly discusses the recommendations for further study.
701.3.6 Feasibility Study

For a project under Feasibility Study category, the manuscript primary contents shall
Page 31 of 43
CHAPTER II. PROPOSED PROJECT

This chapter shall describe and explain to the readers the project being proposed to be
evaluated for feasibility. This may include the project’s nature, client information,
purpose, project rationale, estimated budget, timeframe, etc.
CHAPTER III. FEASIBILITY CRITERIA

This chapter enumerates and briefly discusses each feasibility criterion to be
evaluated and the method of evaluation for each.
CHAPTER IV. METHODS & ANALYSIS

This chapter discusses in detail the method and analysis performed for evaluating
each criterion.

Conclusion – this item states and explains the answer to whether the proposed project
is feasible or not based on the analysis.
for the proposed project.
701.3.7 Case Study

For a project under Case Study category, the manuscript primary contents shall
CHAPTER II. THE CASE

This chapter contains the description of the case, the discussions on its background
and importance, related studies, and other discussions related to the case.
CHAPTER III. METHODOLOGY

This chapter discusses the procedures performed in investigating the case.
CHAPTER IV. ANALYSIS & DISCUSSION

This chapter contains the detailed presentation and discussions of the findings and the
logical analysis of the findings towards formulating conclusions about the case.
Page 32 of 43
Conclusion – this item states and explains the resolution of the objectives or
question/s concerning the case.
for further study on the case or related case.
701.3.8 Off-category Projects

The manuscript contents and specifications of off-category projects shall be set by the
Coordinator upon due discussion with the team and adviser.
701.4 Other Content Details

Other manuscript content details not mentioned in Section 701 shall be prescribed by
the Coordinator, or described in a sample manuscript provided by the Coordinator.
702 Manuscript Formatting and Specifications

This section shall serve as a guide for formatting of the project manuscript.
702.1 Text
702.1.1 Text Style

The style to be used for all text in the project manuscript shall have the following
specifications:
Font Times New Roman
Font Size 12 points
702.1.2 Line spacing

Line spacing shall be set to 2.0.
702.1.3 Text Alignment

All paragraphs shall be justified, but not forced justified.
702.2 Page Layout
702.2.1 Page Size and Orientation

The page size shall be the standard ISO (International Organization for
Standardization) A4 (210 x 297 mm). Page shall be oriented portrait.
702.2.2 Page Margins

Page margins shall be as follows:
Page 33 of 43
Top margin 1.0 inch
Bottom Margin 1.0 inch
Left Margin 1.5 inch
Right Margin 1.0 inch
702.2.3 Page numbers

Page numbers shall be displayed on the top right portion of the page. Page numbers
on the first page of each chapter of the primary contents should not be displayed.
702.2.3.1
The pages within the primary contents until the Appendices shall be provided with
Hindu-Arabic numeral page numbers, the first page of the primary contents being
page “1”.
702.2.3.2
Pages from the Title Page to the List of Appendices shall be provided with Roman
numeral page numbers, with the Title Page being page “i”.
702.3 Hierarchy Formatting

Hierarchy formatting pertains to how the contents, sub-contents, and items are
arranged and organized in a hierarchy.
702.3.1
The hierarchy formatting of the project manuscript shall follow the hierarchy
formatting prescribed by the sample manuscript provided by the Coordinator.
702.4 Illustrations and Tables

An illustration may be in the form of a photo, image, drawing, or chart.
702.4.1
All illustrations and tables shall have a top and bottom text wrap. This means that no
textual content shall appear at either sides of the illustration or table.
702.4.2
Illustrations or tables shall not be placed beside each other.
702.4.3
All illustrations shall be labelled at the bottom-centered portion with a figure number
followed by its title or description.
702.4.4
All tables shall be labelled at the top-centered portion with a table number followed
by its title or description.
Page 34 of 43
702.4.5
All illustrations and tables shall be placed after its quotation in the text.
702.4.6
All text inside table cells should have a centered vertical alignment.
702.5 References
Any information, illustration, and table that have been taken from an identifiable
source shall be provided with proper referencing.
702.5.1
The format for citing references shall follow the APA (American Psychological
Association) style.
702.6 Publishing
702.6.1
The printed manuscript shall be hard bound with plain or textured covers of a uniform
color and texture as prescribed by the Coordinator.
702.6.2
The front cover of the bound manuscript shall display for the least the following
elements (a to e):
a) Title of the manuscript in bold letters
b) Category of the project
c) Name/s of the author/s
d) Month and year of publishing
e) Logo of the university wherein it will be published
702.7 Other Formatting Details

Other manuscript formatting details not mentioned in Section 702 shall be prescribed
by the Coordinator, or described in a sample manuscript provided by the
Coordinator.
Page 35 of 43
SECTION 8
GRADING SYSTEM
801 General
The Coordinator shall be responsible for organizing the performance evaluation of
each student enrolled in CEng 156 (Civil Engineering Project).
801.1
The overall percentage rating of a student shall be computed as the weighted average
of the following components of evaluation as shown in Table 801.1. For details on
each component, see Section 802 to Section 805.
Table 801.1
Rating components
Component Weight Evaluator/s
Oral Deliberation Rating 30% Panel
Coordinator’s Prerogative Rating 40% Coordinator
Adviser’s Prerogative Rating 20% Primary adviser
Teammate’s Assessment Rating 10% All teammates (see Section 805)
801.2
The final grade shall be derived from the computed weighted average from Section
801.1 following Table 801.2.
Table 801.2
Final Grade Equivalent
Range (%) Final Grade
95.56 – 100 1.00
91.11 – 95.55 1.25
86.67 – 91.10 1.50
82.22 – 86.66 1.75
77.77 – 82.21 2.00
73.33 – 77.76 2.25
68.89 – 73.32 2.50
64.44 – 68.88 2.75
60 – 64.43 3.00
Below 60 5.00
Page 36 of 43
801.3
The evaluation shall be carried out using evaluation sheets or any valid equivalent to
be filled up by the corresponding evaluator/s for each component.
801.3.1
The Coordinator shall be responsible in preparing, administering, and processing of
evaluation materials.
801.3.2
The date, venue, and other details of the procedure for evaluation shall be announced
by the Coordinator.
801.4
All documents and data involved in the evaluation procedure shall be considered
confidential and shall be handled only by the Coordinator or his/her authorized
assistant.
801.4.1
After the evaluation, only the final grade will be disclosed by the Coordinator.
802 Oral Deliberation Rating

Each member of the Panel, excluding any who acts as Adviser of the team, shall
evaluate each team during the Oral Deliberation session as follows:
802.1
The criteria and respective weights for evaluation for this component is shown on
Table 802.1. A team shall be evaluated for each criterion on a scale of 1 to 5, 1 being
“Not evident” and 5 being “Very evident”.
Table 802.1
Criteria and weights for Oral Deliberation Rating
Criteria Description Weight
Presentation
The presenter/s have mastered the flow,
Mastery 10%
order, and details of the presentation.
The elements in the presentation are
Arrangement arranged so that the whole presentation 5%
can be easily understood.
The visual aspect of the presentation
Visual impact elevates the effectiveness of conveyance 5%
of the contents.
Page 37 of 43
The duration of presentation is well
Time 5%
within the allocated time.
Manuscript
The submitted manuscript contains all the
Completeness 10%
necessary parts.
The discussions in the manuscript are
Order and Clarity 10%
clear and coherent.
Contents of the manuscript are faithful to
Validity 10%
scientific principles.
Details presented in the manuscript are
Accuracy correct, and the manuscript is free of 10%
clerical errors.
Defense
Validity of The content of answers during defense
10%
answers are faithful to scientific principles.
The answers during defense relate well to
Relevance the question given and clearly address the 10%
question.
The manner of stating the answer is
Manner 5%
professional and reasonable.
Presence and conduct
The presenter/s conform to the prescribed
Attire 5%
attire
The presenter/s show relevant and proper
Body language 3%
body language.
The presenter/s tone and volume of
Tone and volume
speech correctly match the intended 2%
of speech
levels for every element being presented.
Total (100%)
802.1.1
The ratings (1 to 5) for each criterion will be multiplied by the corresponding weights,
and summed up to a rating (ranging from 1.000 to 5.000). This rating will then be
converted to percent and taken as the Oral Deliberation Rating for the team.
802.2
The average Oral Deliberation Rating for the team from all evaluators in the Panel
shall be taken as the Oral Deliberation Rating for each member of the team.
Page 38 of 43
803 Coordinator’s Prerogative Rating
The Coordinator shall evaluate each team as follows:
803.1
Table 803.1
Criteria and weights for Coordinator’s Prerogative Rating
Course Requirements
Adherence to the deadline of submission
Project Proposal of project proposal, and the quality of 5%
proposal
Quality of performance during the
Proposal Review 5%
deliberation of project proposal
Adherence to the deadline for compliance
Pre-conduct
of pre-conduct documents, and the 5%
documents
completeness and quality of content
Project Objectives of project objectives, and the 5%
completeness and quality of content
Adherence to the deadline of compliance
of project bulletin, completeness and
Project Bulletin 5%
quality of contents, and timeliness of
updates
Progress Report of the Project Progress Report, 5%
completeness and quality of contents
Adherence to the deadline submission of
Manuscript for
manuscript for defense, completeness and 5%
Defense
quality of contents
Project Quality of performance during the Oral
10%
Deliberation deliberation session/s
Project
Quality of performance during the project
Presentation / 10%
presentation and/or exhibit
Exhibit
Final Manuscript of final manuscript, completeness and 15%
quality of contents
Page 39 of 43
Project Handling Skills, Attitudes and Ethics
The team can decide accurately within

Decisiveness 2%
the available time.
They are well-paced according to the

Good pace 5%
project plan.
They are dedicated as a team to work on
Dedication 2%
what has to be accomplished.
They respect appointments, schedules,
Punctuality 4%
and deadlines.
Organization They are well organized in all aspects. 2%
They can foresee possible events or

Foresight concerns and able to address them 2%
effectively.
They are open to take advices, and able to

Openness 2%
accept criticisms objectively.
They are able to adjust and cope with

Adaptability 2%
various situations and environments.
They can sustain effective work even in

Resilience 2%
stressful situations.
They are able to make on-the-spot

Responsiveness 2%
decisions whenever necessary.
They are able to transact business

Professionalism professionally, and show professional 5%
courtesy to others.
Total (100%)
803.1.1
converted to percent and taken as the Coordinator’s Prerogative Rating for the team.
803.2
The Coordinator’s Prerogative Rating for the team shall be taken as the Coordinator’s
Prerogative Rating for each member of the team.
Page 40 of 43
804 Adviser’s Prerogative Rating
Each team shall be evaluated by their primary adviser as follows:
804.1
Table 804.1
Criteria and weights for Advisers’ Prerogative Rating
Teamwork values
All members clearly understand and
Responsibility 10%
fulfill their individual roles as a team.
Mutual respect All members respect one another. 5%
They can arrive at project decisions
Relational security 5%
without fear of relational consequences.
Mutual motivation They are able to motivate each other. 5%
Each member is willing to sacrifice
Selflessness personal gain for the sake of the team’s
5%
overall benefit.
Each member is sensitive and considerate
Mutual concern 5%
to each other teammate’s concerns.
The team can decide accurately within
Decisiveness 5%
the available time.
They are well-paced according to the
Good pace 10%
project plan.
They are dedicated as a team to work on
Dedication 5%
what has to be accomplished.
They respect appointments, schedules,
Punctuality 5%
and deadlines.
Organization They are well organized in all aspects. 5%
They can foresee possible events or
Foresight concerns and able to address them 5%
effectively.
They are open to take advices, and able to
Openness 5%
accept criticisms objectively.
Page 41 of 43
They are able to adjust and cope with
Adaptability 5%
They can sustain effective work even in
Resilience 5%
They are able to make on-the-spot
Responsiveness 5%
decisions whenever necessary.
They are able to transact business
courtesy to others.
Total (100%)
804.1.1
converted to percent and taken as the Adviser’s Prerogative Rating for the team.
804.2
The Adviser’s Prerogative Rating for the team shall be taken as the Adviser’s
Prerogative Rating for each member of the team.
805 Teammate’s Assessment Rating

Each team member shall be evaluated by all other members of the team as follows:
805.1
Table 805.1
Criteria and weights for Teammate’s Assessment Rating
Teamwork values
He/she clearly understands and fulfills
Responsibility 10%
his/her individual role as a team member.
Respect He/she respects all members of the team. 5%
He/she openly participates in project
Relational security decisions without fear of relational 5%
consequences or inflicting such.
He/she is able to motivate other team
Encouragement 5%
members.
Page 42 of 43
He/she is willing to sacrifice personal
Selflessness gain for the sake of the team’s overall 5%
benefit.
He/she is sensitive and considerate to
Thoughtfulness 5%
other teammates’ concerns.
He/she helps to decide accurately within
Decisiveness 5%
the available time.
He/she is well-versed of the project plan

Good pace 10%
and is sensitive to the pace of the project.
He/she is dedicated to work on what has

Dedication 5%
to be accomplished.
He/she respects appointments, schedules,
Punctuality 5%
and deadlines.
He/she is well organized in all aspects of
Organization 5%
the project.
He/she can foresee possible events or
Foresight 5%
concerns and able to communicate them.
He/she is open to take advices, and able
Openness 5%
to accept criticisms objectively.
He/she is able to adjust and cope with
Adaptability 5%
He/she can sustain effective work even in
Resilience 5%
He/she actively contributes in making on-
Responsiveness 5%
the-spot decisions whenever necessary.
He/she is able to transact business
courtesy to others.
Total (100%)
805.1.1
and consequently summed up to a rating (ranging from 1.000 to 5.000). This rating
will then be converted to percent.
805.2
The Teammate’s Assessment Rating of a member is computed as the average rating
received from evaluation by all of his/her teammates.
Page 43 of 43

Ce Project Guideline Edition 5

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ce Project Guideline Edition 5

Uploaded by

Copyright:

Available Formats

Visayas State University

College of Engineering and Technology

101 General Procedure and Timeline

101.1 CE Project offering schedule and requisites

101.2 Appointment and Role of the CE Project Coordinator

101.3 CE Project Meeting

101.4 Appointment of the Chairman for the CE Project Panel of Deliberators

101.5 Submission and Deliberation of Project Proposals

101.6 Pre-conduct Activities

101.8 Project Progress Report

101.9 Submission of Project Manuscript for Project Defense

101.10 Project Oral Defense

101.11 CE Project Presentations

101.12 Submission of Approved Project Manuscript

201 Description of CE Project categories

201.1 Community Solution / Community Extension

201.1.2 Project Summary

201.1.3 Project Output

201.2 Innovation / Invention

201.2.2 Project Summary

201.2.3 Project Output

201.3 Design / Development

201.3.3 Project Output

201.4 Experimental Research

201.4.2 Project Summary

201.5 Theoretical Study

201.5.2 Project Summary

201.5.3 Project Output

201.6 Feasibility Study

201.6.2 Project Summary

201.6.3 Project Output

201.7 Case Study

201.7.2 Project Summary

201.7.3 Project Output

301 General Guidelines

302 Project Proposals Submission

302.1 Content of Project Proposal

302.1.1 Community Solution / Extension

II. THE TARGET COMMUNITY

IV. IMPORTANCE OF THE PROJECT

V. FUNDING OR SUPPORT PLAN

302.1.2 Innovation / Invention

II. INNOVATION CONCEPT *(if invention, INVENTION CONCEPT)

III. IMPORTANCE OF THE CONCEPT

IV. PROTOTYPING AND EVALUATION METHODS

V. FUNDING OR SUPPORT PLAN

II. PROJECT DESCRIPTION

III. KNOWLEDGE & WORK REQUIREMENT

IV. FUNDING OR SUPPORT PLAN

302.1.4 Experimental Research

IV. MATERIALS AND METHODS

VI. FUNDING OR SUPPORT PLAN

302.1.5 Theoretical Study

II. THEORETICAL PROBLEM

III. IMPORTANCE OF THE STUDY

IV. KNOWLEDGE, METHODS AND TOOLS

302.1.6 Feasibility Study

II. PROPOSAL IN QUESTION

III. IMPORTANCE OF THE STUDY

IV. FEASIBILITY CRITERIA AND METHODS

V. FUNDING OR SUPPORT PLAN

302.1.7 Case Study

II. THE CASE