Reporting Field Details

Roles: Principal Investigator, Core Administrator, Institutional Administrator

This article provides additional information on the fields that are available from the Reporting‍ interface, specifically all the fields that are included in the "Source Data as CSV/XLS" option under "Export".  A selection of these fields are also available as report filters.


Charge Reporting Fields

Field
Description
Service ID
If the charge is part of a service requests, this field will contain the the service request ID (as visible within iLab), otherwise blank
Customer Name
The name of the customer associated with this charge
Customer Title
The title of the customer (if available)
Customer Lab
The lab to which this charge is or will be billed
Customer Department
The department the customer belongs to (if departments are configured for the customer's institution)
Customer Institute
The institution the customer belongs to
Charge Name
The name of the charge. This is typically the name of the service as defined under Editing Services. For generic charges, this field contains "(charge)", followed by the name of the charge as entered.
Notes
Any notes associated with the charge
Payment Information
The payment information used for billing the charge (if already provided)
Custom Field
For customers with integrations, iLab has the ability to set up to 3 custom fields. If applicable, this information will feed into this field. Note: This field is not retroactive and will only populate once custom field information has been entered and forward.
Status
The "work" status of the individual charge:
  • proposed: The charge has been proposed to the customer, but has not yet been accepted by the customer. 
  • financials_approved: The charge has received financial approver (typically from the PI or lab/group manager, but potentially from a Departmental administrator or Institutional Administrator).
  • processing: The work associated with the charge is in progress.
  • completed: The work associated with the charge has been completed.
  • canceled: The charge has been canceled. 
Billing Status
The billing status of the charge:
  • canceled: The charge is canceled and will not be billed.
  • not_ready_to_bill: The charge is not (yet) ready to be billed. 
  • ready_to_bill: The charge is ready for billing 
  • billing_initialized: The charge has been billed
  • not_billable: The charge has been marked as not billable
  • pro_bono: The charge has been marked as pro bono (i.e. no charge to the customer)
Quantity
The quantity component of the charge (i.e. number of "units")
Price
The price per unit of this charge
Total Price
The total price of the charge (i.e. price x quantity)
Price Type
The price type applied to this charge (e.g. internal, external, corporate, etc.)
Creation Date
The date the charge was created in iLab
Purchase Date
The date the charge was entered in iLab. Typically equal to the creation date, unless the core back-dated the charge (if allowed)
Completion Date
The date the work associated with the charge was marked as complete
Billing Date
The date of the billing event in which the charge was included
Created By
iLab user that created the charge.
Core Name
The name of the core that created the charge.
Invoice Num
The number of the invoice associated with the charge (if the charge was billed)
No Charge Justification
The provided justification for not charging for this item
Ad-hoc Charge Justification
The provided justification for an ad-hoc (flexible) charge
Organization Name
The name of the organization the lab has been added to (not configured for most institutions)
Company Organization Name
The name of the organization the core is a part of (not configured for most institutions)
Charge ID
The unique identifier of this charge
Reviewed
If Peer Review Status is enabled, this column will populate with Peer-reviewed or Non peer-reviewed. If not enabled, No Status Yet will appear
Center
The center the users' lab belongs to.
Category
The category of the charge, as defined in the service associated with the charge
Usage Type
The usage type of the schedule associated with the charge ‍
UNSPSC Code
For Storeroom cores, this is the code entered when a product is entered in the system. If not provided, this number will be 12000000.
UNSPSC Name
For Storeroom cores, this is the name entered when a product is entered in the system
Facility Catalog Number
For Storeroom cores, this number is specific to the storeroom itself.
Central Catalog Number
For Storeroom cores, this number comes from the procurement group but is typically the same as the Facility Catalog Number.

Service Request Reporting Fields

Field
Description
Service ID
The identifier of this service request
Customer Name
The name of the customer associated with this charge
Customer Lab
The lab to which this charge is or will be billed
Customer Title
The title of the customer (if available)
Customer Department
The department the customer belongs to (if departments are configured for the customer's institution)
Customer Institute
The institution the customer belongs to
Custom Field
For customers with integrations, iLab has the ability to set up to 3 custom fields. If applicable, this information will feed into this field. Note: This field is not retroactive and will only populate once custom field information has been entered and forward.
Actual Cost
The actual cost of the service request (based on all included services and charges)
Projected Cost
The originally projected costs for the service request
Current Milestone
The most recently completed milestone for this service request
Status
The status of the request, as discussed in Request Status
Number of Line Items
The number of line items included in the service request (equal to the number of charges if split billing is not used)
Creation Date
The date the service request was created
Submission Date
The date the service request was submitted. Typically equal to the creation date, unless the core back-dated the charge (if allowed)
Completion Date
The date the service request was marked as complete.
Created By
The iLab user that created the service request.
Core Name
The name of the core that created the charge.
Organization Name
The name of the organization the lab has been added to (not configured for most institutions)
Reviewed
If Peer Review Status is enabled, this column will populate with Peer-reviewed or Non peer-reviewed. If not enabled, No Status Yet will appear
Center
The center this core belongs to.

Event Reporting Fields

Field
Description
User Login Email
The e-mail address the user used to login to iLab
PI email
The e-mail address of the user's PI
Equipment Name
The name of the equipment that was used
Customer Name
The name of the customer associated with this charge
Customer Lab
The lab to which this charge is or will be billed
Customer Title
The title of the customer (if available)
Customer Department
The department the customer belongs to (if departments are configured for the customer's institution)
Customer Institute
The institution the customer belongs to
User Permission
This is the permission group the user belongs to for this instrument. Permissions are defined at the core level but assigned at the calendar level
Price Type
The price type applied to this charge (e.g. internal, external, corporate, etc.)
Event Type
This will say reservation, unavailable (for maintenance scheduling) or cancelled (for cancelled events).
Scheduled Start
The originally scheduled start time of the event
Scheduled End
The originally scheduled end time of the event
Scheduled Hours
The originally scheduled total number of hours
Actual Start
The actual start time of the event
Actual End
The actual end time of the event
Actual Hours
The actual total number of hours
Creation Date
The date the event was created
Core Name
The name of the core where the event was created
Organization Name
The name of the organization the lab has been added to (not configured for most institutions)
Reviewed
If Peer Review Status is enabled, this column will populate with Peer-reviewed or Non peer-reviewed. If not enabled, No Status Yet will appear
Center
The center this core belongs to.
People Who Found This Helpful