[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-242799-105":53,"doc-detail-242799-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","standard-operating-procedure-153-ilab-core-charge-and-event-reporting","Standard Operating Procedure 153 - iLab Core Charge and Event Reporting","","Standard Operating Procedure 153 defines how Pitt shared research facilities/cores use the iLab reporting functionality to produce analysis and generate charges and events reports. The SOP covers role scope for Core Administrator and Core Manager, explains how to view iLab event reporting for scheduling cores, and how to export charges and event data to a Pitt Excel workbook template. It also outlines how the workbook’s multiple sheets support data visualization, pivot updates, and monthly or annual reporting for improved business awareness and facility oversight.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/standard-operating-procedure-153-ilab-core-charge-and-event-reporting/242799/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/standard-operating-procedure-153-ilab-core-charge-and-event-reporting/242799.png","ImageObject",442,249,{"name":88,"@type":89},"Fez","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-11","2026-09-12",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What is the purpose of SOP 153 in iLab reporting?","Question",{"text":108,"@type":109},"SOP 153 explains how shared research cores use iLab reporting to perform analysis, generate reports, and extract monthly or annual charge and event data.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Which iLab reports does the SOP focus on?",{"text":113,"@type":109},"The SOP highlights two report types: charges (financial charges generated by core facilities) and events (data related to scheduled events).",{"name":115,"@type":106,"acceptedAnswer":116},"How is exported iLab data used in the Excel workbook template?",{"text":117,"@type":109},"Users export CSV/XLS from iLab, copy the data into the corresponding workbook sheets (charge export or event export), then refresh pivot tables on each report tab to generate or update figures.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},242799,1791305180,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":135,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":76},2336478940794,"https://ap-avatar.wpscdn.com/davatar_9964176cb1d06d4a9deccf72a44ae3dc","Standard Operating Procedure 153 for Pitt iLab System iLab Role: Core Administrator, Core Manager Revision \\# : 0 Date: 10/2025  \nContents  \nPurpose: ...................................................................................................................... 1  \nScope: ......................................................................................................................... 1  \niLab Event Reporting Page for Scheduling Cores ..........................................................2  \nDirections for Exporting Data to Excel Template: .........................................................4  \niLab Charge and Event Report Workbook Template ......................................................6  \nPurpose:  \nThis SOP describes how shared research facilities/cores can use iLab reporting functionality to perform analysis, generate reports and extract monthly or annual report data. The reporting tab in iLab provides access to useful data. The two types of reports highlighted in this document are 1) charges: report on the individual financial charges generated by core facilities and 2) events: report on data related to scheduled events.  \nMost shared research cores can be categorized as either a scheduling core or a service core, although a few provide both options. Scheduling cores primarily offer equipment reservations, such as booking time to use a wire bonder. Service cores primarily offer specific services, such as a gene sequencing request. The reporting functionality groups a core into one of these general categories.  \niLab reports are great for performing a quick check on key performance parameters for your shared research core facility. However, for more detailed analysis and control of the output, excel offers more options. To reduce facility director work, a Pitt-designed Excel template is provided on the shared research facilities website. This Excel template produces graphs for data visualization and simplifies figure generation for analysis and reports. The reporting features and template described in this SOP are intended to enhance business awareness.  \nScope:  \nThis SOP pertains to the Core Administrator and Core Manager roles in iLab. Institutional administrators also have this capability.  \niLab Event Reporting Page for Scheduling Cores  \nThe reports created on the iLab event reporting page can provide visualizations and details about equipment usage for scheduling cores.  \n1. Navigate to the ‘Reporting’ tab and ‘Events’ sub-tab of the core’s iLab page.  \n2. Click on ‘Load default’.  \n3. Set the Date Range for the desired range (e.g. first and last day of the month) .  \n4. Click on ‘Run report!’.  \nThe default iLab event report displays an overview of highly used instruments and the most active labs for that core. Additionally, the individual equipment graphs of scheduled vs actual time could provide useful information for a scheduling core.  \ni. Graph example displaying top users by week:  \nii. Graph example displaying highly used instruments by day of the week:  \niii. Individual equipment graphs of scheduled vs actual time:  \n5. The dashboard display may not show all the reportable information , or you may wish to import the reports into a report . The export file that is obtained in the next section includes a comprehensive set of data regarding core use.  \nDirections for Exporting Data to Excel Template:  \n1. Navigate to the ‘Reporting’ tab and ‘Charges’ sub-tab of the core’s iLab page.  \n2. Click on ‘Load default’.  \n3. Set the Date Range for the desired range (e.g. first and last day of the month) .  \n4. Click on ‘Run report!’.  \n5. Click on ‘Export’ and select ‘Source data as CSV/XLS’ to download the CSV file.  \n6. Open the CSV file and click on the top left corner of the sheet to select all the data. Right click to copy the entire sheet.  \n7. Paste the data into the ‘iLab Charge Export’sheet of the iLab Charge and Event Report Workbook.  \n8. Navigate to the ‘Reporting’ tab and ‘Ev","cbCaitWPTrJv5ny8","https://ap.wps.com/l/cbCaitWPTrJv5ny8","pdf",1160096,10,8,"English","# Purpose\n# Scope\n# iLab Event Reporting Page for Scheduling Cores\n## Steps for generating event reports\n# Directions for Exporting Data to Excel Template\n## Steps for exporting charge data\n## Steps for exporting event data\n## Refreshing workbook reports with pivot tables\n# iLab Charge and Event Report Workbook Template\n## Scheduling cores sheets\n## Service cores sheets\n## Both types: department and lab revenue","[{\"question\":\"What is the purpose of SOP 153 in iLab reporting?\",\"answer\":\"SOP 153 explains how shared research cores use iLab reporting to perform analysis, generate reports, and extract monthly or annual charge and event data.\"},{\"question\":\"Which iLab reports does the SOP focus on?\",\"answer\":\"The SOP highlights two report types: charges (financial charges generated by core facilities) and events (data related to scheduled events).\"},{\"question\":\"How is exported iLab data used in the Excel workbook template?\",\"answer\":\"Users export CSV/XLS from iLab, copy the data into the corresponding workbook sheets (charge export or event export), then refresh pivot tables on each report tab to generate or update figures.\"}]","Standard Operating Procedure 153 - iLab Core Charge and Event Reporting | PDF",1789194938]