Welcome to the Beta Manual!

July 1st, 2008

This is a first draft of the research administration procedures. Your comments are necessary and welcome. Please let us know where the procedures are hard to follow or unclear by leaving a comment on the procedure itself.

Use the Categories to the right to find a sets of related procedures. The first post in each category lists all the procedures available. The blog format is used to capture comments and encourage discussion. However, the procedures were not written from the first to the last. Trying to navigate the Beta Manual chronologically will be confusing. Ignore most dates.

Be sure to have a copy of the research administration process flow charts handy. While most of the procedures can be presented “in order” the flow chart will indicate which procedures are dependent and which can be undertaken in parallel.

This site is still under construction and is not the permanent location of the final manual. Please bear with us while adjustments are made. The permanent location will be announced in due course and this manual will be replaced.

The Beta Manual was written by many people (spending many long hours locked in a conference room in an undisclosed location). Special thanks go to Faye Farmer and Tracey Sotelo for their limitless patience.

Define Opportunity (in order of process)

July 1st, 2008

Develop Proposal (in order of process)

June 30th, 2008

Obtain Approvals (in order of process)

June 30th, 2008

Submit & Negotiate (in order of process)

June 30th, 2008

Set up award (in order of process)

June 29th, 2008

Execute Project - Unit (in order of steps)

June 27th, 2008

Execute Project - ORSPA Process (in order of steps)

May 23rd, 2008

Managing Change Requests

Invoicing and Financial Reporting

Closeout Project Process (in order of steps)

May 22nd, 2008

Follow limited submissions process

December 14th, 2007

Specific Responsibility: Research Advancement Staff
Owner: OVPREA Research Advancement
Assigned Writer: Faye Farmer

Pre-requisites

  • Access to the opportunity announcement
  • Access to ASU’s institutional guidelines
  • Access to the human resources database
  • Access to principal investigator(s)’ information
  • Internet
  • Email

Summary

  • Review the opportunity announcement and determine whether it requires limited submission through ASU.
  • Contact PRIDE regarding submission of proposal in response to the opportunity announcement.

Read the rest of this entry »

Archive project documents

November 28th, 2007

Summary

There are sponsor and legal requirements to keep project documents for a defined period of time and to destroy them after this time has expired. Variable requirements from sponsor to sponsor.

Policy

  • ASU Sponsored Fiscal Management (SFM 1506) Records Retention Policy

Close accounts in financial system

November 28th, 2007

Summary

After receipt of final payment has posted to sponsored account, account is closed in the financial system.

Receive and confirm final payment

November 28th, 2007

Prerequisites

  • Mail (checks)
  • Award Database (Coeus)
  • Invoice Database
  • Invoice Bin
  • K and I drive access
  • Web Check Log
  • Financial System (Advantage)
  • Computer with fax modem
  • Bamtrac information (banking activity download)

Read the rest of this entry »

Issue final invoice and report(s)

November 28th, 2007

Prerequisites:

  • Coeus, Advantage, Advantage web reports, ApplicationXtender
  • K drive access
  • Document Center account file(s)
  • Knowledge of A-21 Cost Allowability

Summary

  • Determine allowable expenses.
  • Organize documentation to support allowable expenses.
  • Clear encumbrances
  • Adjust indirect costs
  • Confirm total revenue
  • Determine direct cost deficit
  • Prepare check request for sponsor refund
  • Prepare final invoice/report.

Read the rest of this entry »

Inactivate accounts

November 28th, 2007

Unit Responsibility: GCA
Specific Responsibility: Accountant
Owner: GCA Manager - Michele Wrapp

Prerequisites:

  • Access to and knowledge of Coeus, Advantage, Advantage web reports
  • K drive access
  • Document Center account file(s)

Summary:

  • Perform GCA Account Closeout Checklist Pre-final Closeout tasks
  • Record completion of tasks on GCA Account Closeout Checklist
  • File GCA Account Closeout Checklist in Document Center account file(s)

Read the rest of this entry »

Post final expenditures

November 28th, 2007

Summary

  • Ensure that all project expenditures including cost transfers have been posted to the correct project accounts.

Complete final budget review and make adjustments

November 28th, 2007

Summary

  • Org Manager/designee conducts ongoing, timely reconciliations to facilitate a detailed final close out review.
  • Review the project budget and ensure all charges were incurred correctly and posted to the correct account.
  • Initiate cost transfers as required.

Confirm Deliverables

November 28th, 2007

Summary

  • Confirm that project deliverables including parts, systems, reports, etc. meet sponsor requirements based on original proposal as well as any approved changes.
  • Prepare the report and give to ORSPA for review and submission to the sponsor. For some sponsors with electronic submission process, PI and/or unit staff may submit without ORSPA review.

Identify appropriate timing for project closeout

November 28th, 2007

Summary

Determine if project will require early closeout or if it will terminate according to original agreement on performance period.

Process Flow: Closeout Project

Prepare final draft of proposal material

November 27th, 2007

Specific Responsibility: Research Advancement Staff
Owner: OVPREA Research Advancement
Assigned Writer: Faye Farmer

Prerequisites

  • Microsoft Word
  • Internet connection and browser
  • Email, with read receipt ability
  • Opportunity announcement
  • Adobe portable document file software

Summary

  • Receive the proposal draft from the proposal editing team.
  • Review the opportunity announcement and sponsor requirements to ensure that documents are organized accordingly.
  • Review ASU’s document requirements to ensure that required documents are attached.

Read the rest of this entry »