Introduction - staging.construction-institute.org · Web viewKristi Delaney, CII Coordinator for Funded Studies – (512) 232-3002, [email protected]. Michael Burns, CII

CII Funded Studies Committee

CII Guidelines for Project DeliverablesJanuary 2019

CII Project Deliverables Guidelines Last Edited: November 2018 1


Table of Contents

Introduction.............................................................................................................................................2

Expected Deliverables.............................................................................................................................2

Coordination of the Multiple Deliverables..............................................................................................3

Progress Report.......................................................................................................................................4

Presentation............................................................................................................................................5

Final Report.............................................................................................................................................7

Knowledge Base Deliverables................................................................................................................12

Data Guidelines.....................................................................................................................................15

Close-out Report....................................................................................................................................17

Appendix A – Close-out Report Form....................................................................................................18

IntroductionThis document seeks to communicate the expectations and requirements for CII Research Team (RT) deliverables, giving teams high-level guidelines. CII will discuss any exceptions or details separately with each individual team.

During an RT’s life, its members can expect to interface with CII through fellow member-company volunteers and several CII staffers. The volunteers could include members of the Funded Studies Committee (FSC), the Annual Conference Committee, and any sector committees that may have funded the research. The following CII staffers should be able to answer most RT questions:

Daniel P. Oliveira, Manager of Research Services – (512) 232-3050, [email protected] Kristi Delaney, CII Coordinator for Funded Studies – (512) 232-3002, [email protected] Michael Burns, CII Editor – (512) 232-3018, [email protected]

Expected DeliverablesAt a minimum, a “standard” RT is expected to deliver:

A presentation at a CII event (likely an annual conference or a CII Board of Advisors meeting) One or more progress reports, which are deliverables directed to academics and industry

reviewers that inform CII and the Funded Studies Committee (FSC) about the team’s research methodology and results

A final report, which is a publication directed to industry members that describes the value and implementation of the research results

A topic summary and a tagging document, which will enable the research results to be uploaded into the CII Knowledge Base (KB)

Datasets and data dictionaries A close-out report


mailto:[email protected]

mailto:[email protected]


CII will provide specific guidelines and deadlines for progress reports at project kickoff. CII will also schedule a call halfway through the project to provide details about presentation rehearsals, final report development, and other specific deadlines.

Additional deliverables may include:

A proof-of-concept tool (often an Excel spreadsheet) Links to related academic dissertations, theses, and other academic publications that may be

added to the team’s KB page

If the team intends to provide a proof-of-concept tool, the FSC should be notified as soon as possible. CII will then provide feedback on its expectations for tools.

Coordination of the Multiple Deliverables This document provides guidelines for both presentation and final report. It is CII’s intent for each RT to develop its presentation and report in tandem, as is shown in Figure 1. Developing the presentation early in the research process allows the subsequent report to follow a consistent storyline. Figures and other visuals created for the presentation can be used again in the final report to communicate research methods, findings, etc.

Figure 1. Timeline for Year 2 RT Deliverables



Progress ReportEach RT will submit progress reports periodically throughout the research process, with the first progress report due between Project Kickoff and Rehearsal 1. A progress report addresses the following concerns:

Ensure that the research is progressing in a way that will provide value to CII members. Evaluate the research approach and methodology (academic rigor). Evaluate the level of engagement of the team members and identify any staffing or participation

issues. Assist the team with development of its presentation and other deliverables.

Progress reports content are detailed in Table 1.

Table 1. Progress Report Contents

Methodology

Research Objective

State overall research objective.Clearly report changes (if any) to the RT’s original objective for FSC review

and approval.Problem Statement

State current problem statement and research questions.Clearly indicate changes (if any) to the RT’s original problem statement and

research questions.Relevance/ Value

Indicate the value for CII members. In early reports, this is the anticipated value.

This value should be derived from the problem statement but expressed in language appropriate to practitioners and industry members.

Expected Deliverables

Describe the expected or actual deliverables generated by the RT (e.g., proof-of-concept tools, checklists, or guides).

Highlight any changes from the original deliverables.Research Methodology

Describe the overall methodology.Describe the data collection plan.Describe the methods used to generate results. Teams can map each result

to supporting methods and data.Outline the research validation approach.

Results and Findings

Provide an update on the team’s results up to the date of the progress report.

Contextualize results and make them easy to understand.Effectively present the results. Consider how graphics contribute to this goal.

Logistics and Staffing

Current Project Schedule

Provide an up-to-date schedule with activities and milestones.When applicable, update schedule with actual progress on activities and

milestones.Identify any delayed activities and potential delays, as well as mitigation

plans.Issues and Concerns

Identify any issues or concerns (e.g., leadership issues, participation concerns, or staffing needs).

The progress reports can be submitted as Excel files. CII will share a template with teams at the project kickoff.



PresentationEach RT is expected to present its results at a CII event. Traditionally, teams present their results during the CII Annual Conference, but other events may also be considered (such as the CII Board of Advisors (BOA) meetings).

Previous presentations are available as a reference (log-in required): https://www.construction-institute.org/resources/knowledgebase/annual-conference-downloads

CII also developed a training video that can be accessed via this link: http://youtu.be/Qu0GQL2PQk0

Expectations for PresentationsThe presentation should have a narrative that focuses on the value of the research results and entices the audience to apply its findings. This means that the presentation should start with the end in mind, providing clear insights on the benefits of the research results and the problems they address.

The presentation development phase includes, at a minimum, the following events:

A conference call with CII to discuss the presentation storyline. The goal is to help the team identify the structure of the narrative. Note that at this point, the team may not have all results at hand. The storyline should be based on the best possible assessment of what the results will be and build the discussion about value based on these assumptions. The FSC will schedule and participate in the call and provide feedback to the outline. For projects sponsored by sector committees, the sponsoring committee will also attend and provide feedback.

One to three conference calls to rehearse the presentation (dry runs), with call frequency depending on the team’s schedule. (One-year projects should have fewer sessions than two-year projects.) Early rehearsals will focus on developing the storyline for the presentation, and later session(s) will focus on the slides and improving the storyline. The goal is to prepare a set of slides that supports an enticing narrative, and to have them ready for the dress rehearsal. After the last rehearsal before the Dress Rehearsal, the team is expected to implement the changes captured during rehearsal(s) and provide an updated set of slides to a designer contracted by CII. The FSC will schedule and participate in the dry runs. For projects sponsored by sector committees, the sponsoring committee will attend and provide feedback.

A Dress Rehearsal, scheduled by CII and attended by the CII Conference Committee, the CII Funded Studies Committee, and CII staff. The Dress Rehearsal presentation should use the final slides provided by the graphic designer and the team’s final script, and both should be close to their final version. It is expected that some feedback can be provided regarding the narrative and slides, but the main emphasis will be on how each team member presents the slides.

Presentation ScheduleAfter the planning conference call, each team should review its meetings and deliverable schedule for the course of the project. Prior to every rehearsal, the team should prepare a complete draft of its presentation so CII can provide appropriate feedback and the team can get the most out of the session.


http://youtu.be/Qu0GQL2PQk0

https://www.construction-institute.org/resources/knowledgebase/annual-conference-downloads

https://www.construction-institute.org/resources/knowledgebase/annual-conference-downloads


Figure 2 below summarizes the steps of the presentation development process for a presentation to be delivered at the CII Annual Conference (AC).

Figure 2. Presentation Development Process


Conference call~6-7 months before the Dress RehearsalDrives the team to define a storylineTeam estimates "Findings Complete" milestoneIntegrates rehearsal and team meeting scheduleOrganized by the FSCAttended by research team, FSC, and, if applicable, sponsoring sector committeeTeam should provide/update an abstract to promote the presentation at the AC (CII to provide rough draft)

Planning Conference Call

Conference call~3-4 months before the Dress RehearsalFocuses on the development of slides and storylineTeam presents the first draft of its slidesAttended by research team, FSC, and, if applicable, sponsoring sector committeeCII to provide speech coach

Dry Run 1

Conference call~1-2 month before the Dress RehearsalFocuses on the revision of slides and improving the narrativeTeam provides a list of speakers (with correct usual and phonetic spellings of personal and company names)Attended by research team, FSC and, if applicable, sponsoring sector committeeCII to provide speech coach

Dry Run 2

Provided by CIITeams should send the final slides one week after the second dry runBetween Rehearsal 2 and the Dress RehearsalCII send the final slides back to the teams no later than one week before the Dress Rehearsal

Slide Design

In-person rehearsal organized by CIIFocuses on presentation (slides should be final)Attended by research teams, Annual Conference Committee, FSC, and CII staff

Dress Rehearsal

Typically, the CII Annual Conference Alternatively, another CII event, such as a CII Board of Advisors Meeting

Final Presentation


Final ReportThe final report is a summary of the team’s research and its deliverables, written for the industry practitioner (a project management or business unit decision-maker). While the progress report has an academic emphasis (on the methodology), the final report emphasizes the value and implementation of the results for the CII industry member. In other words, while the progress report starts with the research question(s) and builds up the methodology and results, the final report starts with the end in mind by discussing the value of the results, explaining how the results can be implemented, and only then providing insights on the methodology used to achieve the results. Figure 3 below illustrates this distinction.

Progress Report Sequence

Final Report Sequence

Figure 3: Content Sequences for the Progress and Final Reports

The final report must accomplish the following objectives:

Clearly communicate the value and benefits of the results, following a narrative similar to the team’s presentation.

Explain and illustrate how the results can be deployed in capital projects and organizations. Address the interests and concerns of project management and business decision-makers in the

construction industry. (This report is not aimed at academia.) Be written, preferably, by industry practitioners. CII expects that the RT’s principal investigators

(PIs) and Chair may coordinate the development of the final report; however, the actual writing is expected to be performed by industry members of the team. One suggestion is that members could write the section they are presenting in order to leverage their familiarity with the topics. The final report should be written in language and at a level of detail suitable to its intended audience.

The sections below describe the expectations for the report content. Note that these are not recommendations for how to organize the report, but only guidelines for its content.

Describing the ValueThe final report can leverage the presentation’s approach to communicate the value of the research findings to CII members. For instance, RT-DCC-02 (i.e., the Construction Readiness team) summarized potential challenges faced in construction projects as shown in Figure 4. The team also illustrated the value of implementing its tool by showing that “ready projects” outperform not-ready projects (Figure 5).


Research Question

Reserach Methodology Results Value Implementation

Value Implementation Examples Results High-level Methodology


Figure 4. Example Illustration of Research Motivation

Figure 5. Example Figure to Describe Research Findings’ Value

Implementation How the final report describes the implementation of project findings may vary significantly, depending on the results’ level of complexity. For instance, the results may range from a simple checklist to an ambitious practice that requires the user to implement major organizational changes (e.g., Advanced Work Packaging).

The implementation recommendations should cover the following considerations:

Complexity and implementation requirements (How complex is implementation?) The timing of implementation and project phases (When?) Overall process (How?) Which main roles (stakeholders) are expected to be involved in the implementation (Who?)

The items above can be described according to the scales and examples presented in Table 2. Note that Table 2 is only a general recommendation and RTs are free to adapt and expand upon it.



Table 2. Practice/Tool Implementation Summary

Complexity (1–5) 5 – Complex: Probably requires major organizational changes across the project and company organization.1 – Simple: Can be implemented by one or two people in the project team with minimal support, and the results can be used in most project management processes.

Timing (1,2, or 3) 3 – Implementation spans several projects phases between Front End Planning (FEP) and Startup (e.g., Advanced Work Packaging (AWP))2 – Multiple implementation points within a single phase (e.g., FEP)1 – One-time implementation at specific project phase (e.g., project complexity tool)

Project Phases o FEPo Engineeringo Procuremento Constructiono Commissioning/Startup

Overall Process A short description of the process.

Involved Stakeholders A short description of the key roles that are responsible and accountable for the implementation (this should exclude some support roles or roles that are only consulted or informed).

Table 3 below provides an example of how implementation timing can be illustrated in the final report. In this instance, asterisks indicate the timing of implementation.

Table 3. Example Implementation Timing Guide for a Front End Planning PracticeFront End Planning * * *EngineeringProcurementConstructionCommissioning

*Indicates Timing of Implementation

The implementation of proposed practices and processes can also be explained by presenting one or more case studies and/or through a process flowchart. In preparing supporting figures and tables, please remember that the final report is produced on letter-sized pages (8.5” x 11”). Complicated charts that are difficult to read in a larger format will become illegible in the final format. Please contact the CII Editor with any concerns or questions.

The Research MethodologyThe research methodology should be addressed at a high level. The intent is to provide insight on how the team collected data and evaluated the results, and to convey the academic rigor in the process. This means that a high-level explanation of the methods should be provided; for instance, explaining why certain methods were adopted, and their objectives. If the researchers developed a model to predict the probability of high-impact accidents, insights could be provided by describing the objective of the model



and the variables used for the prediction. The formulae and results of statistical software could be provided in an appendix. CII assumes that details of the methodology will be provided in separate publications (e.g., academic journal articles, conference papers and presentations, and M.S. theses and Ph.D. dissertations). CII will ask PIs to notify it when any such documents are published, so links to these documents can be added to the CII Knowledge Base.

Finally, the final report should convey the results in a clear and fair manner. The RT should avoid making unfounded extrapolations of the results and should state benefits strictly supported by the research findings.

The Final Report ProcessThe FSC will work with each RT on the development of its final report. (This process also applies for projects sponsored by sector committees.) Figure 6 below summarizes the “standard” process, where the final presentation is at the CII Annual Conference and contract close-out occurs three months after the conference. Note that the process may vary according to each team’s particular deliverables and timeline.



Figure 6. Final Report Process


A first outline is expected immediately after the first dry run and should drive the team to define the report narrative (building on the presentation narrative)A second and final outline is expected following the second dry runOutlines should be submitted to the CII Coordinator and will be reviewed by FSC sponsors and, if applicable, sponsoring sector

Report Outline

Graphic designer provides conference slides no later than one week before the Annual ConfeenceGraphics can be used, where appropriate, in the final report

Graphic Design

~2 months, between the dress rehearsal and Annual Conference, depending on the project's specific timelinePrincipal investigators coordinate the writing and are not expected to write the report themselvesIndustry members contribute by writing sections of the report

Report Writing

As a rule, delivered expected before the Annual Conference (or other presentation event, as applicable)Draft should be submitted to the CII Coordinator

Final Draft Delivery

Final draft is reviewed by CII staff, including the CII Editor, and by the FSC sponsors and reviewers (reviewers should ideally include one contractor, one owner, and one academic)The CII Editor manages the review processPerformed after the Annual Conference, which allows reviewers to become familiar with the topic by attending the team's presentation

CII Review

~1 month after receipt of the final draft

CII Provides Feedback

The CII Coordinator receives the submissionThe CII Editor verifies the revisions and approves/rejects the documentUpon draft approval, CII moves to close out the project by editing and laying out the final report~2-3 months after the Annual Conference

Final Delivery


The team should develop the final report in coordination with its development of other deliverables:

The presentation can lend the final report graphics and a framework for its narrative. The progress report’s description of results and value statements can carry forward to the final

report. The progress report can also provide graphics for the final report. The CII Knowledge Base summary should overlap with the final report and focus on two or three

main findings that will drive readers to read the final report.

Final Report FormattingAfter the RT has made final delivery of its final report and the CII reviewers have accepted it, CII will proceed to editing and layout. Although CII will create the final layout in Adobe InDesign, CII needs the RT to provide every element of its final report in the original file formats. (For instance, if the team used Visio and PowerPoint to create the figures contained in its Word document of the final report, CII will need to receive the original files for all of these elements as native Visio, PowerPoint, and Word files.) Please contact the CII Editor with any concerns or questions.

In preparing the report graphics, please remember that the final report is produced on letter-sized pages (8.5” x 11”). Large charts that may be difficult to read in a letter-size format should be avoided and, if necessary, need to be discussed with the CII editor.

Knowledge Base DeliverablesEach RT must provide two deliverables that allow the dissemination of the research results in the KB:

The topic summary is a concise description of the research. It is served to any user who accesses the KB (not only CII members). It draws attention to the final report and any other available publications and deliverables, and it motivates users to access these resources. A template for the topic summary is provided at https://utexas.box.com/v/rt-resources and many examples can be found in the CII Knowledge Base.

The tag checklist is an Excel file that provides the metadata that connects the topic summary to other parts of the KB. A template of this checklist is provided at https://utexas.box.com/v/rt-resources.

Topic SummaryThe topic summary should contain the following content. (Note that a team should limit its topic summary to three to four pages.)

Topic Summary Heading

The heading should provide the RT’s number and title (e.g., Research Team 283, Industrial Modularization).

Overview/Conclusions

The summary should concisely summarize the topic, establishing its importance, identifying the key conclusions and recommendations, and conveying the value and benefits of implementing the findings. Each piece of information should be bookmarked to give the location(s) in the research publications where effectively explanation(s) can be found.


https://utexas.box.com/v/rt-resources


https://www.construction-institute.org/resources/knowledgebase/knowledge-areas/safety/topics/pac-safety



Overview/conclusions section – This section should be no longer than one page. Bookmarks – Each should be identified with a document number, page (locations), and/or

figure/graphic location(s) (e.g., IR283-2, page 10, Figure 3).

Key Findings (Supporting Graphics and Information)

The topic summary should list the key findings, data, and information that support the conclusions presented in the overview/conclusions section. Limit the material to only the most relevant and necessary data, with no more than eight key findings. This presentation of key findings should not be so exhaustive as to eliminate the need for the reader to obtain any of the research publications, especially since this summary will be available to all readers online. It should only give enough detail to establish the value of the research and to motivate the reader to obtain the publications.

For each key finding, the team should provide:

Provide the document number, page number, and/or graphic location at which each finding appears in the research publication (e.g., Provide the document number, page number(s), and/or graphic location(s) where each finding appears in the research publication (e.g., RR283-11, page 44).

Key finding illustration – If appropriate, suggest a graphic that illustrates each finding cited, and import it into the template as shown in the examples below.

Key Finding #1 – Business Case ProcessThe modularization business case process should

be applied at the earliest opportunity (RS283-1, page 11 or IR283-2, page 5).

IR283-2, page 2

Key Finding #2 – Execution Plan DifferencesThe RT identified more than 100 differences in

planning modularization projects. These different planning scenarios were organized into the

appropriate implementation phases, with more than half applicable to the design phase (RS283-1, page 14 or IR283-2, page 59).

IR283-2, page 59

Figure 7: Example of Figures Illustrating Key Findings



When reporting the key findings, the team should leverage the graphics from the final presentation. For instance, Figure 8 below shows a graphic from a presentation that summarizes the benefits RT-DCC-02 found for “construction ready” projects. Figure 8 shows some of the same results portrayed in charts obtained from a statistical software. CII recommends that teams should use figures like Figure 8 and avoid figures like Figure 9.

Figure 8. Example of a Figure that Summarizes Findings (Recommended)

Figure 9. Example of a Figure Obtained from Statistical Software (Not Recommended)

Implementation ToolsIdentify and list key spreadsheets, checklists, directions, and other implementation guidance. Provide bibliographic information to direct readers to the tool(s), as is demonstrated above in the samples of key findings.

Key Performance IndicatorsIdentify which key performance indicators the research topic area affects.

Research PublicationsProvide a list of all research publications the team has produced. This list will be used to create links to each publication.



Supporting ResourcesThe team’s page in the CII Knowledge Base will include additional resources that the RT can contribute to, but that other CII groups will probably finalize after the team has closed out:

Presentations – The KB will reference any presentations (including to the CII Annual Conference, CII Board of Advisors meetings, or workshops) that support the team’s recommendations or show how to implement its materials.

Educational materials – The KB will list any CII educational resources that support the topic area. The team is welcome to volunteer information for this listing.

Other ItemsThis section can be used if the review of the research material identifies special items of interest, such as key definitions, key synonyms, and related follow-on research.

Other Academic Publications

CII wants to provide links from the KB to any academic publications that result from the research. Most of these links are expected to be provided after the project completion, and CII asks PIs to provide this information as soon as these publications become available. When the RT delivers its topic summary, it should provide links to any publications that are already available. CII will only include a link to these external publications, and it is understood that some may require purchase (particularly papers in academic journals).

Tag ChecklistThe tag checklist is an Excel file (a template is provided at https://utexas.box.com/v/rt-resources) that allows metadata to be connected to the Topic Summary. Research teams will choose metadata such as: Knowledge Areas, applicable Project Phases, relevant Project Functions or Roles, etc.

Data GuidelinesCII expects any data generated by this RT to be handed over to CII at the project close-out report and this will include:

Data in Excel or other database format as approved by CII, Data dictionary (following the format in Table 4), Copies of surveys used, including:

Project data survey, and/or Opinion survey.

Survey DevelopmentThe use and purpose of RT’s surveys should be carefully planned and evaluated as the team develops its methodology. Surveys may be used to solicit ideas, suggestions, and to identify specific project improvement practices, as well as to collect quantitative data on project performance. Broad based surveys that solicit opinioned-based conclusions are strongly discouraged. Researchers should also recognize that the use of surveys directed only to the CII membership may not result in the desired innovation and broadening of CII member perspectives. There is risk that CII member only surveys could simply reinforce existing practices, processes, and perspectives denying members the benefits of far-reaching opportunities and innovations. Additionally, sample bias may be introduced, further impeding




the research. Structured interviews and case studies afford the RT an opportunity to obtain high quality data that may be used to supplement broad statistically based surveys. Although much data often comes from the RT companies, teams should seek data from other CII companies and non-member companies where possible. This is particularly critical for the validation of findings.

When teams solicit project data, they will request CII’s standard project data survey template, which includes basic definitions of terms.

Survey Approval Prior to fielding these survey instruments, they must be submitted to the CII Associate Director for Research for approval via email. Teams should allow two weeks for review and approval. RTs can submit surveys for approval on or before Progress Update 2: Methodology. If the RT intends to distribute surveys at CII events such as the CII Annual Conference, surveys will need to be submitted and approved prior to these events. If surveys need to be approved by the Board of Advisors (BOA), they will need to be submitted prior to the BOA meetings, typically in early April and late October.

DeliverablesTeams will deliver the following with their project close-out report:

Data in Excel or other database format as approved by CII, Data dictionary (following the format in Table 4), Copies of surveys used, including:

Project data survey, and/or Opinion survey.

Data DictionaryThe data dictionary will allow users to understand what type of data are collected by RTs. Table 1 below is an example of a data dictionary.

Table 4. Example Data Dictionary

Field Name Data Format Description ExampleProject Construction Start Date

MM/DD/YYYY Date project started construction

01/05/2017

Project Construction Cost

Project cost of construction, excludes cost of permits, engineering and design

$1,000,190.00 USD

When terms can have multiple meanings or are ambiguous, teams are required to provide a specific definition. Below is an example:

Overtime can be calculated in two ways: any hours above 40 hours in a week OR any hours about 8 hours in one day. In this study, Overtime is defined as any hours above 40 hours in a week (a week is a 7 day period starting on Monday).



Close-out ReportThe close-out report must be submitted within 60 days following the submission and approval of the Final Report. The close-out report template can be found in Appendix A.



Appendix A – Close-out Report FormThe following pages include the close-out report form due 60 days after the submission and approval of the Final Report.


Name/# of Research Team:

Closeout Reporting

The required components required to close out a CII research team include:

Publications submitted to and accepted by the CII Editor and Associate Director for Funded Studies, including the following:

Final Report Date Submitted: _____ Date Accepted: _____ Topic Summary Date Submitted: _____ Date Accepted: _____ Knowledge Base Update Date Submitted: _____ Date Accepted: _____ CII Event Presentation Date of Presentation: _____ Copyright Registration Date Submitted: _____ Date Accepted: _____

Final Expenditure Report:

The submission and approval of the Final Expenditure Report (template attached) Date Submitted: _____

PDH certification:

The submission of PDH certification hours request Date Submitted: _____ for RT members

Recommendations to CII:

Education Module – Would this research benefit from development of an education module?

Date Recommendation submitted to Associate Director, Professional Development : __________

Recommendations to CII for follow-on research?Date Recommendation submitted to Associate Director, Funded Studies : __________

Input to CII Knowledge Base – Where should the RT products be placed in the CII KB Structure? Date Recommendation submitted to Associate Director, Funded Studies: __________

Input to Deployment Committee What are the critical elements for assessing implementation of this research? Are there any terms to be added to CII’s Glossary?

Date Recommendation submitted to Associate Director, Deployment: __________

Chair Date Principal Investigator Date

Vice-Chair Date Co-Principal Investigator Date* if applicable



Final Expenditure Report Template

The expenditure report should match the budget format that was submitted with your proposal. All travel must be itemized by trip. This report is due 60 days following the submission and approval of the Final Report. The final payment will be made upon receipt of all items listed in the Closeout Report.

Year 1 Year 2 TotalSalaries – Faculty PI – Enter Name (# weeks/yr) Co-PI-Enter Name (if applicable) Fringe Benefits (xx.x%)

Total Faculty Salaries

Salaries – Graduate Students Enter Student/Department Name (# hrs/week) Enter Student/Department Name (# hrs/week) Fringe Benefits (xx.x%)

Total Student Salaries

Supplies/Equipment/Services*

TOTAL DIRECT COSTS

F&A Costs (University Overhead xx.x%)

Tuition

TOTAL INDIRECT COSTS

Travel Amount Amount Total

Miscellaneous*

Total CII funding requirements

Total Institutional Cost-Sharing/Matching Contributions (if applicable)

TOTAL PROJECT COST*include an itemized list



Copyright Registration Template

The required components required to close out a CII research team include the following:

When CII registers your research summary, implementation resource(s), and research report, the U.S. Copyright Office asks whether the works are based on or incorporate pre-existing material. Material is pre-existing if it has been previously registered, previously published, is in the public domain, or is not owned by the research team authors.

Check the appropriate box (es) below to exclude any preexisting material in your documents. You may use the “Other” space to specify a pre-existing work or to give a more detailed description of the material excluded from the claim. If any of the material included has a previous copyright registration, please provide the registration number and year. (If the registration is pending, enter the word “pending” in the space for the registration number.) For new material, check the appropriate box (es) to identify all new or revised material being claimed in this registration. Use the “Other” space to give a more specific description of the new material created by the author(s).

Material Excluded: Text Artwork Photograph(s) Computer ProgramOther: ____________________

Previous Registration:1st Prev. Reg. #: __________

Year: __________

2nd Prev. Reg. #: __________

Year: __________

New Material Included: Text Artwork Photograph(s) Computer ProgramOther: ____________________


Documents

Introduction - staging.construction-institute.org · Web viewKristi Delaney, CII Coordinator for Funded Studies – (512) 232-3002, [email protected]. Michael Burns, CII