Assess a Six-Device Fleet in GLPI

Assess a six-device fleet with ownership, maintenance, and reports in GLPI.

Introduction

30 Second Summary

A list of office devices can look complete while hiding the questions that matter most. Without clear ownership or service history, damaged equipment can stay in use while replacement decisions become guesswork.

In this project, you will assess a fictional six-device fleet in GLPI. You will produce a report pack that shows which assets are healthy, incomplete, damaged, or ready for replacement.

What You'll Build

A manager can open your saved action list to trace every repair, replacement, or record-completion recommendation back to the affected device.

By the end of this project, you'll have:

A searchable six-device register that lets you find four computers, one printer, and one monitor under consistent BPS names.
Evidence-rich asset records where you can inspect ownership, hardware, software licensing, lifecycle dates, and a resolved printer repair.
A manager-ready assessment pack with a saved action-required view, an inventory export, built-in status reports, and linked printer maintenance evidence.
Secret Mission: Turn the healthy laptop record into a reusable template for faster future onboarding.

Are there any prerequisites?

You need a Windows device with an existing local GLPI 12.0.1 instance. Step 1 checks that your account can create and update every record used in the assessment before you add fictional data.

Before We Start

Before any hands-on work begins, commit to building a clearly fictional six-device BluePeak Services assessment. This boundary lets you assess ownership, condition, maintenance, and replacement actions without affecting real inventory.

Confirm Access and Protect Existing Data

Your local GLPI instance may already hold real inventory. Fictional BluePeak Services records need a clear boundary so they never blend into that asset register.

This access check catches missing permissions before you create any records. The naming rule protects existing equipment from accidental changes.

In this step, get ready to:

Confirm the local instance version plus its current entity.
Verify access to every required project workflow.
Establish the naming boundary that protects existing data.

Confirm the instance and working context

The current entity defines where your project records belong. Keeping one entity selected prevents the six-device assessment from being scattered across different contexts.

Navigate to your existing local GLPI sign-in page using its saved bookmark or local address.
Sign in with the account you plan to use for this project.
Find the displayed GLPI version in the signed-in interface.
Confirm the displayed version is 12.0.1.
Identify the current entity in the signed-in interface.
Record the entity here: your current entity.
Keep your current entity selected throughout the project.

You should see GLPI version 12.0.1. The selected entity should match the value you recorded.

That clears the first safety check. Every BluePeak Services record now has one consistent destination.

Verify the required permissions

Menu visibility confirms that your account can reach each required area. Creation controls plus local permission information confirm that the account can complete the later workflows.

Open Computers from the Assets section to confirm the list page loads.
Open Printers from the Assets section to confirm the list page loads.
Open Monitors from the Assets section to confirm the list page loads.
Open Users from the Administration section to confirm the user list loads.
Open Ticket from the Assistance section to confirm the ticket area loads.
Open Reports from the Tools section to confirm the report area loads.
Open Dropdowns from the Setup section to confirm the configuration area loads.

The required top-level modules are now visible. Each destination opens without changing any existing record.

Missing an area?

An absent destination usually means the current account lacks permission for that module. Leave existing records unchanged while you resolve the access gap.

Sign out of the current account.
Sign back in with a local account that has equivalent create and update rights.

If the area remains hidden, help me identify which GLPI permission is missing.

Return to the Computers list from earlier.
Confirm the computer list provides search controls.
Confirm Export is available above the results.
Open Software from the Assets section.
Confirm the software area provides creation or update controls without submitting a form.
Use the left menu to open the license workflow available in your instance.
Confirm the license area provides creation or update controls without submitting a form.

The remaining permission check covers the records you create later. Confirm each right without saving a test record.

Confirm with the local instance owner that this account can create and update computer records.
Confirm with the local instance owner that this account can create and update printer records.
Confirm with the local instance owner that this account can create and update monitor records.
Confirm with the local instance owner that this account can create and update user records.
Confirm with the local instance owner that this account can create and update ticket records.

Why check access before creating records?

A partially permitted account can leave the assessment unfinished halfway through. Verifying each workflow now keeps the later inventory work focused on assessment evidence.

Confirm with the local instance owner that this account can create and update software records.
Confirm with the local instance owner that this account can create and update license records.
Confirm with the local instance owner that this account can create and update dropdown values.
Confirm with the local instance owner that this account can create and update saved searches.
Confirm with the local instance owner that this account can export search results.
Confirm with the local instance owner that this account can run reports.

That is the permission check complete. You can now build the assessment without discovering a blocked workflow halfway through.

Establish the safe data boundary

Prefixes make every exercise record recognisable at a glance. They also give you a precise rule for deciding which records belong to the project.

Record this data boundary exactly in your project notes:

Only records named with the prefixes BPS, BP-, or bps. are fictional BluePeak Services exercise records. All existing unprefixed inventory is protected from modification, linking, trashing, and deletion.

Record the confirmed working context beneath the data boundary:

Local GLPI version 12.0.1. The current entity is recorded for every project record. Account access is verified for the required asset workflows. Access is also verified for ticket workflows. User workflows are available. Dropdown workflows are available. Software workflows are available. License workflows are available. Search workflows are available. Export workflows are available. Report workflows are available.

Use BPS at the start of every fictional asset name.
Use BPS at the start of every fictional status or software record.
Use BPS at the start of every fictional saved search or ticket title.
Use BP- at the start of every fictional inventory number.
Use bps. at the start of every fictional user login.
Keep every project record in your current entity.
Leave every unprefixed record unchanged.

Before the final check, which three prefixes do you expect to separate project data from real inventory?

Return to the signed-in GLPI page from the permission check.
Confirm the displayed version remains 12.0.1.
Confirm the selected entity matches your current entity.
Confirm the left menu shows Assets, Assistance, Tools, Administration, and Setup.
Confirm every required destination from the permission check still opens.
Compare your project notes with the three protected prefixes.

GLPI still shows version 12.0.1. The selected entity matches the value you recorded.

Your notes reserve BPS, BP-, and bps. for project records. Unprefixed inventory remains outside the exercise.

Your working context is verified. Next, you will create the six-device BluePeak Services inventory inside this protected boundary.

Build the Six-Device Inventory

Your safe BPS boundary is now in place inside GLPI. It keeps this training inventory separate from every unprefixed record in the current entity.

A structured asset register gives each device a consistent identity. It creates the first visible inventory for BluePeak Services.

This first pass deliberately leaves the User field empty. It also leaves the Status field empty.

These gaps prevent the list from explaining accountability or condition.

In this step, get ready to:

Prepare the exact fictional asset dataset.
Create four computer records with the planned assessment gaps.
Complete both remaining asset types.

Prepare the fictional register

Consistent names make the six training assets easy to find later. Unique inventory numbers give each device its own internal reference.

Confirm that the displayed entity matches the entity you recorded earlier.
Refer to the BPS Data Boundary from the previous step before creating any record.

Your Six Fictional Assets

Every value below is fictional training data. Copy the spelling exactly so later searches return the expected records.

Computer record. Set Name to BPS-LT-001. Set Inventory number to BP-0001. Set Serial number to BPS-L1001. Set Comments to Healthy support laptop.
Computer record. Set Name to BPS-LT-002. Set Inventory number to BP-0002. Set Serial number to BPS-L1002. Set Comments to Laptop with damaged keyboard.
Computer record. Set Name to BPS-LT-003. Set Inventory number to BP-0003. Leave Serial number blank. Set Comments to Laptop with incomplete inventory data.
Computer record. Set Name to BPS-DT-001. Set Inventory number to BP-0004. Set Serial number to BPS-D1001. Set Comments to Old, underperforming desktop.
Printer record. Set Name to BPS-PR-001. Set Inventory number to BP-0005. Set Serial number to BPS-P1001. Set Comments to Shared printer with repair history.
Monitor record. Set Name to BPS-MN-001. Set Inventory number to BP-0006. Set Serial number to BPS-M1001. Set Comments to Unassigned spare monitor.

Use each Name exactly once.
Use each Inventory number exactly once.
Keep the User field empty on every record.
Keep the Status field empty on every record.

The missing serial number on BPS-LT-003 is deliberate. It gives the later assessment a visible record-quality gap.

Create the four computer records

Computer records use the same creation workflow. Repeating that workflow keeps their identity fields consistent.

Select Assets in the left menu.
Select Computers.
Confirm that the current entity still matches your recorded entity.
Start a computer record with the creation control in the horizontal menu.
Populate the form from the BPS-LT-001 register entry above.
Leave User empty.
Leave Status empty.
Create the record with the visible form validation control.

Good start. Your first BluePeak Services laptop is now an active computer record.

Return to the Computers list.
Create BPS-LT-002 by repeating the same sequence with its register entry.
Search the computer list for BPS-.

You will see two BPS computer records. Their inventory numbers are BP-0001 and BP-0002.

Create BPS-LT-003 by repeating the same sequence with its register entry.
Create BPS-DT-001 by repeating the same sequence with its register entry.
Search the computer list for BPS- again.

You will now see four computer records. The result contains three laptops plus one desktop.

Missing a Computer Record?

Confirm that you created every record in the current project entity.
Check each Name for the exact BPS- prefix.
Compare every Inventory number with the fictional register above.
Use this troubleshooting prompt if the count is still different from four.

Add the remaining asset types

Printers and monitors live in separate asset lists. Using the same naming pattern makes all three lists part of one searchable training register.

Select Assets in the left menu.
Select Printers.
Confirm that the current entity still matches your recorded entity.
Start a printer record with the creation control in the horizontal menu.
Populate the form from the BPS-PR-001 register entry above.
Leave User empty.
Leave Status empty.
Create the record with the visible form validation control.

The printer list now contains the fictional shared printer. Its role description preserves the maintenance context you will use later.

Select Assets in the left menu.
Select Monitors.
Start a monitor record with the creation control in the horizontal menu.
Populate the form from the BPS-MN-001 register entry above.
Leave User empty.
Leave Status empty.
Create the record with the visible form validation control.

The monitor is now active as unassigned stock. Its blank User field preserves that intended state.

Before you run the three searches, do you expect this first-pass register to explain who owns each device?

Return to the Printers list.
Search the printer list for BPS-.

You will see exactly one fictional printer named BPS-PR-001.

Return to the Monitors list.
Search the monitor list for BPS-.

You will see exactly one fictional monitor named BPS-MN-001.

Return to the Computers list.
Search the computer list for BPS-.

You will see exactly four fictional computer records. Across the three filtered lists, the active BPS inventory contains six devices.

Every Name is unique. Every Inventory number is unique.

The blank User fields mean ownership is unknown. The blank Status fields mean condition is unknown.

Why the Gaps Matter

The six records prove that the equipment exists in the register. They cannot yet show who is accountable for each assigned device.

They also cannot separate healthy equipment from damaged stock. This limitation is the intended result of the first-pass inventory.

Count Different From Six?

Confirm that the computer search shows four records.
Confirm that the printer search shows one record.
Confirm that the monitor search shows one record.
Check that every asset Name begins with BPS-.
Use this inventory-check prompt if one asset type still has the wrong count.

That is your six-device baseline complete. Next, you will add ownership plus the technical and lifecycle evidence needed for a real assessment.

Add Ownership and Asset Evidence

Your six BluePeak Services devices now form a visible asset register. Their blank User fields leave custody unclear.

This step adds accountability to those records inside GLPI 12.0.1. The new evidence will also show whether selected equipment is fit for use.

In this step, get ready to:

Establish device ownership with fictional employee records.
Document the selected computers' technical evidence.
Capture lifecycle evidence for the selected assets.

Create fictional users and assign custodians

An active user becomes an asset custodian when selected in an asset's User field. This relationship makes responsibility visible from both the user record and the asset record.

Fictional User Details

The bps.maya record uses Maya in Firstname. Its Surname is Chen.
The bps.luis record uses Luis in Firstname. Its Surname is Romero.
The bps.priya record uses Priya in Firstname. Its Surname is Nair.
Each record stays Active in your current entity. None receives an administrative profile.

Select Administration in the left menu.
Select Users.
Click Add user.
Complete the user creation form for bps.maya using the details above.
Use the form's final creation control to add the user.
Repeat the Add user workflow for bps.luis.
Repeat the Add user workflow for bps.priya.
Confirm all three records show Active without an administrative profile.

That is the identity layer in place. Your three fictional employees can now appear as asset custodians without receiving administrative access.

Return to the Assets area from earlier.
Select Computers.
Filter the computer list for Name containing BPS-.
Assign Maya Chen to BPS-LT-001 through its User field.
Assign Luis Romero to BPS-LT-002 through its User field.
Assign Priya Nair to BPS-LT-003 through its User field.
Assign Maya Chen to BPS-DT-001 through its User field.
Leave every computer's Status field empty.

The four computers now show who is responsible for them. Their condition remains unclassified.

Select Printers under Assets.
Assign Maya Chen to BPS-PR-001 through its User field.
Leave the printer's Status field empty.
Select Monitors under Assets.
Open BPS-MN-001.
Confirm its User field remains empty because the monitor is unassigned stock.

Return to the Users area from earlier.
Open bps.maya.
Select Used items.

You should see BPS-LT-001, BPS-DT-001, and BPS-PR-001 associated with Maya Chen. This confirms her three custodian assignments.

Review Used items for bps.luis.
Review Used items for bps.priya.

Luis Romero should show BPS-LT-002. Priya Nair should show BPS-LT-003.

User Missing From the Asset Field?

Confirm the fictional user is active.
Confirm the fictional user belongs to the current entity from earlier.
Confirm the login begins with bps. before editing anything.

If the user still does not appear, help me troubleshoot why an active GLPI user is missing from an asset's User field.

Record technical and licensed software evidence

Hardware components show whether a computer can support its role. A software installation links the application version to the equipment that uses it.

A software license adds entitlement evidence to that installation. Together these records make the selected computers easier to assess.

Return to Computers under Assets.
Open BPS-LT-001.
Select the Components tab.
Use the visible component creation control to record Memory of 16 GB.
Use the visible component creation control to record a Hard Drive of 512 GB.
Open BPS-DT-001.
Record Memory of 4 GB from its Components tab.
Record a Hard Drive of 128 GB from the same tab.

You should now see 16 GB of memory with a 512 GB hard drive on BPS-LT-001. BPS-DT-001 should show 4 GB of memory with a 128 GB hard drive.

Components Not Appearing?

Confirm you added each component from the correct computer's Components tab.
Check that the memory and hard-drive values use the specified units.
Reopen the computer record to confirm the new components were retained.

For help with the component relationship, help me check why my GLPI computer is not showing its Memory or Hard Drive evidence.

Return to the Assets area.
Select Software.
Use the creation control in the horizontal menu to start a software record.
Enter BPS Support Desk in the Name field.
Use the form's final creation control to add the software.
Open BPS Support Desk.
Add software version 1.0.

The fictional software record now has an installable version. This version can be linked to individual computers.

Create an associated license named BPS-SD-6 from the BPS Support Desk record.
Set the license Number to 6.
Use the license form's final creation control to retain the record.

The license now represents six fictional seats of BPS Support Desk. The next link shows which computers consume that entitlement.

Return to Computers under Assets.
Open BPS-LT-001.
Select the Software tab.
Select BPS Support Desk as the application.
Select version 1.0.
Install the selected version.
Associate the installation with license BPS-SD-6.

The laptop's Software tab should now show BPS Support Desk version 1.0 with license BPS-SD-6.

Open BPS-DT-001.
Install BPS Support Desk version 1.0 from its Software tab.
Associate the desktop installation with license BPS-SD-6.

Both selected computers now show the same application version. Both installations point to the six-seat fictional license.

License Association Missing?

Confirm version 1.0 exists under BPS Support Desk.
Confirm BPS-SD-6 is associated with the same software record.
Check the asset's Software tab after reopening the computer.

If the installation appears without its license, help me trace the GLPI relationship between my software version, license, and computer.

Complete the lifecycle assessment

Lifecycle dates reveal how old an asset is and how recently someone checked it. Warranty evidence shows whether repair costs may still be covered.

Lifecycle Evidence to Enter

The BPS-LT-002 evidence uses Purchase date 2024-01-15. Startup date is 2024-01-18. Last physical inventory is 2026-09-10. Warranty period is 12 months from purchase.
The BPS-DT-001 evidence uses Purchase date 2020-03-20. Startup date is 2020-03-23. Last physical inventory is 2024-01-05. Warranty period is 36 months from purchase.
The BPS-PR-001 evidence uses Purchase date 2023-02-01. Startup date is 2023-02-03. Last physical inventory is 2026-10-15. Warranty period is 36 months from purchase.

Return to Computers under Assets.
Open BPS-LT-002.
Select the Management tab.
Activate financial and administrative information using the visible control.

The lifecycle and warranty fields are now available for BPS-LT-002.

Complete the visible fields with the BPS-LT-002 lifecycle values above.
Use the form's final update control to retain the information.

You should see the purchase, startup, physical-inventory, and warranty evidence retained on the laptop. Its 12-month warranty period has expired.

Open BPS-DT-001.
Select the Management tab.
Activate financial and administrative information using the visible control.

The desktop can now hold lifecycle evidence without changing the global default for other assets.

Complete the visible fields with the BPS-DT-001 lifecycle values above.
Use the form's final update control to retain the information.

The 2020 purchase date now supports the replacement concern recorded in the desktop's comments. Its 2024 physical inventory date also shows that the record is overdue for review.

Return to the Assets area.
Select Printers.
Open BPS-PR-001.
Select the Management tab.
Activate financial and administrative information using the visible control.

The printer now has the same lifecycle fields as the representative computers.

Complete the visible fields with the BPS-PR-001 lifecycle values above.
Use the form's final update control to retain the information.

You should see the printer's recent 2026 physical inventory date. Its 36-month warranty period has expired.

Lifecycle Dates Not Staying Saved?

Confirm financial and administrative information is active on the affected asset.
Enter each date using the format configured by your local instance.
Reopen the Management tab to confirm the values were retained.

If a date or warranty period keeps disappearing, help me troubleshoot the Management information on my GLPI asset.

Before you check the finished evidence, which computer do you expect to show the stronger technical profile?

Open BPS-LT-001 from the computer list.

You should see Maya Chen in the User field. The Status field should still be empty.

Select the Components tab.

You should see Memory of 16 GB with a Hard Drive of 512 GB.

Select the Software tab.

You should see BPS Support Desk version 1.0 associated with license BPS-SD-6.

Open BPS-DT-001.

You should see Maya Chen in the User field. The desktop's Status field should remain empty.

Select the Components tab.

You should see Memory of 4 GB with a Hard Drive of 128 GB.

Select the Management tab.

You should see the 2020 purchase evidence with the 2024 physical inventory date. The expired 36-month warranty reinforces the desktop's replacement case.

You have closed the assessment gap. The fleet now shows ownership, technical capacity, licensed software, and lifecycle evidence.

Your asset records can now explain who owns each device and why selected equipment may need attention. Next, you will turn condition findings into traceable service evidence.

Record Statuses and Maintenance

Your fleet now has custodians plus technical and lifecycle evidence. The remaining gap is proof of each device's current condition.

Free-text comments cannot prove when a fault was reported or what resolved it. GLPI asset statuses make each condition searchable.

A linked Incident records the printer fault as a dated support event. Its completed task plus solution create the maintenance trail an assessor needs.

In this step, get ready to:

Create five reportable BPS asset statuses.
Apply a current status to every fictional device.
Create a resolved printer incident with complete repair evidence.

Create and apply assessment statuses

A consistent Status value turns each assessment finding into something you can search or report. Every project status needs visibility for the three asset types in your fictional fleet.

Why statuses and tickets?

Native statuses keep the current condition visible on each asset. They also support inventory searches plus status reports.

Linked tickets preserve the work behind a condition change through tasks, solutions, and history. This approach creates assessment evidence without installing a condition plugin.

Click Setup in the left menu.
Select Dropdowns.
Expand Common.
Select Statuses of items to reach the item-status list.

You are now in the shared list that controls which statuses can appear on different asset types.

Click the + creation control in the horizontal menu.
Enter BPS - In Service in the Name field.
Choose the assistance behavior that makes the status available when an asset is linked to a ticket.
Enable visibility for Computers.
Enable visibility for Monitors.
Enable visibility for Printers.
Click + Add to create the status.

Good progress. BPS - In Service now appears in the status list with the required asset visibility.

The remaining statuses use the same assistance behavior plus the same three visibility selections. Repeating one configuration keeps the assessment consistent across the fleet.

Create BPS - Needs Repair by repeating the completed status workflow.
Create BPS - Replace by repeating the completed status workflow.

The list now includes separate conditions for repair work and replacement planning.

Create BPS - Inventory Incomplete by repeating the completed status workflow.
Create BPS - Stock by repeating the completed status workflow.

You should now see exactly five statuses whose names begin with BPS -. Each status is available for Computers, Monitors, and Printers.

The five labels become useful once every device carries its assessment result. Apply the computer findings first.

Select Assets in the left menu.
Select Computers.
Search for BPS- to isolate the four fictional computers.
Apply BPS - In Service to BPS-LT-001 through its Status field.
Apply BPS - Needs Repair to BPS-LT-002 through its Status field.
Return to the Computers list.

The list now separates the healthy support laptop from the laptop awaiting keyboard repair.

Apply BPS - Inventory Incomplete to BPS-LT-003 through its Status field.
Apply BPS - Replace to BPS-DT-001 through its Status field.
Return to the Computers list.

All four computers now show distinct outcomes for service, repair, record completion, and replacement.

Select Printers from the Assets module.
Search for BPS- to isolate the fictional printer.
Apply BPS - In Service to BPS-PR-001 through its Status field.
Select Monitors from the Assets module.
Search for BPS- to isolate the fictional monitor.
Apply BPS - Stock to BPS-MN-001 through its Status field.

Before you check the fleet, which three computer records do you expect to remain outside the in-service condition?

Return to the Computers list.
Search for BPS-.
Confirm that each of the four computers shows its assigned BPS status.

You should see BPS-LT-002 marked for repair. You should also see BPS-LT-003 marked as incomplete plus BPS-DT-001 marked for replacement.

Status missing from an asset?

Return to the affected status in Statuses of items. Confirm that visibility is enabled for the asset's type.

Check that you created the status in the same entity as the fictional fleet. Help me troubleshoot a missing GLPI asset status.

Record and resolve the printer incident

The printer's Comments field says it has a repair history. That sentence contains no dated fault report or completed intervention.

Before you inspect the printer, do you expect its current record to prove when the repair happened?

Return to Printers in the Assets module.
Open BPS-PR-001.
Select the Tickets tab.

You will not find a linked repair event yet. The Comments field alone cannot show a reported fault, a completed task, or a solution.

Choose New ticket for this item.
Set the Type to Incident.
Enter BPS-PR-001 paper-feed fault in the Title field.
Enter Shared printer repeatedly jams during paper feeding. in the Description field.
Validate the ticket form using the visible form control.

The incident now exists as a dated support record linked directly to BPS-PR-001.

A task records the technical intervention performed during the repair. Its completion state plus time spent provide operational evidence.

Open Processing in the new incident.
Use the task creation control in Processing.
Enter Clean rollers and run 10-page test as the task description.
Record the time spent completing the simulated repair in the time-spent field.
Set the task status to Done.
Validate the completed task using the visible form control.

The processing timeline now shows a completed repair task with recorded effort.

The solution captures the repair outcome. Adding it moves the incident into a resolved state.

Choose Add a solution.
Enter Rollers were cleaned and the 10-page test completed without a jam. as the solution comment.
Click + Add to record the solution.

That is the maintenance work captured. The printer incident now contains the fault, completed intervention, recorded time, and successful test result.

Incident not showing as resolved?

Confirm that the solution was added to BPS-PR-001 paper-feed fault. Check that the task inside Processing is marked Done.

Make sure the incident remains linked to BPS-PR-001. Help me inspect this GLPI incident workflow.

Inspect the maintenance trail

The linked records now provide several views of the same service event. Together they show the fault, the work performed, the outcome, and the relationship to the printer.

Before you inspect the records, where do you expect the strongest proof of the completed repair to appear?

Return to the Tickets tab on BPS-PR-001.
Open BPS-PR-001 paper-feed fault.
Select Processing to inspect the completed repair task plus solution.
Open the ticket's Historical information.
Return to the BPS-PR-001 asset record.
Select the asset's History.
Open BPS-LT-002 from the Computers list.
Confirm its Status remains BPS - Needs Repair.

The printer's Tickets view shows the linked resolved incident. Processing shows the completed task plus solution.

Historical information and asset History show the recorded relationship or status changes. BPS-LT-002 remains visibly unresolved through its repair status.

Your fleet now has reportable conditions plus an auditable printer repair. Next, you will turn these records into an action-required assessment and manager-ready report pack.

Create the Assessment Report Pack

Your work in GLPI 12.0.1 now proves when the printer fault was reported. It also proves how the fault was resolved.

A manager needs a fleet-level view of that evidence. The report pack turns your individual asset records into a repeatable assessment.

The export captures the complete fleet. The action-required view keeps unresolved computers visible.

The built-in reports summarize the equipment picture. The printer record supplies the maintenance evidence.

In this step, get ready to:

Export the complete BPS fleet as a CSV inventory.
Create a private saved search for computers that require action.
Run GLPI's built-in fleet reports.

Build and export the master inventory view

Global search combines different asset types in one result set. This gives the assessment pack a complete inventory view.

Switch back to the same GLPI instance from earlier.
Select Assets in the left menu.
Open Global.
Set the search field to Name.
Set the operator to contains.
Enter BPS- as the search value.
Run the search.

You'll see exactly six BPS records. Four are Computers.

One record is a Printer. One record is a Monitor.

Good work. Your fictional fleet is now visible as one manager-facing inventory.

Use the result-column controls to show Type.
Use the result-column controls to show Name.
Use the result-column controls to show User.
Use the result-column controls to show Status.
Use the result-column controls to show Serial number.
Use the result-column controls to show Inventory number.

The result table now shows asset type plus ownership. It also shows condition plus both identifiers.

Click Export above the search results.
Select All pages.
Choose CSV to create the inventory export.

Your browser downloads the complete BPS fleet inventory. The export covers all six records instead of only the visible page.

Missing Assets From the Export?

Confirm the search value is BPS-.
Confirm the current entity matches the entity retained earlier.
Select All pages before choosing the export format.
Ask for help with the missing records by using this GLPI export troubleshooting prompt.

Create the action-required assessment

A saved search preserves the assessment query for future reviews. The exclusion rule removes the healthy computer from the action list.

Return to Assets.
Open Computers.
Set the first search field to Name.
Set the first operator to contains.
Enter BPS- as the first value.
Add a second search criterion.
Set the second connector to AND NOT.
Set the second field to Status.

Set the second value to BPS - In Service.

Before you run this search, which computer do you expect the exclusion rule to remove? The next check tests your prediction.

Run the search.

You'll see three computers that still require assessment action.

How Should I Read These Results?

BPS-LT-002 has a damaged keyboard. Its current status shows that repair work remains outstanding.
BPS-LT-003 has no serial number. Its record still needs inventory completion.
BPS-DT-001 has low specifications. Its lifecycle evidence supports replacement.

Seeing the Wrong Computers?

Confirm the first criterion uses Name plus contains plus BPS-.
Confirm the second criterion uses AND NOT plus Status plus BPS - In Service.
Ask for help with the criteria by using this saved-search troubleshooting prompt.

Use the search page's save control.
Enter BPS Asset Assessment - Action Required as the search name.
Set the saved search visibility to Private.
Save the search.

Select Tools in the left menu.
Open Saved searches.
Open BPS Asset Assessment - Action Required.

The saved search returns the same three computers. Its private visibility keeps the assessment specific to your account.

Can't Find the Saved Search?

Confirm the search name is BPS Asset Assessment - Action Required.
Confirm its visibility is Private.
Ask for help locating it by using this saved-search prompt.

Run the built-in reports and assemble the pack

Built-in reports provide summaries without adding a reporting plugin. The Default report shows the equipment picture.

The Status report groups equipment by its current status. This makes the five BPS assessment labels reportable.

Return to Tools.
Open Reports.
Run Default report.

You'll see an overall equipment summary. You'll also see computers summarized by operating system.

Before you run the next report, which five BPS labels should appear in the status summary? The report tests the current state of your fleet.

Return to the reports list.
Run Status.

You'll see the fleet summarized by equipment status. Each status comes from the values applied earlier.

Use the downloaded CSV as the master inventory evidence.
Use the private saved search as the action-required evidence.
Use Default report as the overall equipment evidence.
Use Status as the condition summary evidence.
Use the BPS-PR-001 Tickets view from earlier as the maintenance-history evidence.

Your assessment pack now covers inventory scope. It also covers ownership accountability.

The pack identifies unresolved action. It preserves proof of completed maintenance.

Before your final check, which three computers should appear in the action list? Which five labels should appear in the status summary.

Return to Tools.
Open Saved searches.
Open BPS Asset Assessment - Action Required.

You'll see BPS-LT-002. You'll see BPS-LT-003.

You'll also see BPS-DT-001. The result count remains three.

Return to Reports.
Run Status again.

You'll see BPS - In Service. You'll see BPS - Needs Repair.

You'll see BPS - Inventory Incomplete. You'll see BPS - Replace.

You'll also see BPS - Stock. The status summary now represents the entire fictional fleet.

That's the assessment complete. Your six-device register is now backed by an export, an action list, fleet summaries, and maintenance evidence.

Reports Missing BPS Statuses?

Confirm every BPS asset still has one of the five project statuses.
Confirm the report uses the same entity as the BPS fleet.
Ask for help with the report by using this status-report troubleshooting prompt.

Secret mission

Build a Reusable Laptop Template

Turn BPS-LT-001 into a reusable laptop template for faster onboarding. You will prove the defaults with a temporary computer before returning the active fleet to six devices.

Clean Up Your Resources

Choose whether to retain the fictional assessment, sign out until your next session, or remove every project record. These records remain inside your existing local GLPI 12.0.1 instance with no additional service cost.

Resources you used:

A six-device asset register containing four computers, one printer, and one monitor.
A temporary test computer named BPS-LT-TEMPLATE-TEST that is already in the trash.
Three fictional user records with logins beginning with bps..
Five custom asset statuses with names beginning with BPS -.
A software record named BPS Support Desk with version 1.0.
A six-seat software license named BPS-SD-6.
A resolved maintenance incident named BPS-PR-001 paper-feed fault with its task and solution.
A private saved search named BPS Asset Assessment - Action Required.
A fleet inventory CSV export saved on your Windows device.
A reusable computer template named BPS Standard Laptop.

The built-in Default report and Status results did not create separate project records. They require no cleanup.

Keep everything running

No action is needed while you want the BluePeak Services assessment available. The project prefixes keep the fictional records distinguishable from your existing inventory.

Leave the six active device records in the current entity.
Keep BPS Standard Laptop for future onboarding practice.
Retain BPS Asset Assessment - Action Required for future fleet reviews.
Store the fleet inventory CSV with your assessment evidence.
Continue using the BPS, BP-, and bps. prefixes for fictional practice records.

Pause - I'll come back to this later

Signing out pauses your work without changing the completed assessment. The six active devices remain ready for your next session.

Use the account menu in GLPI to sign out.
Close the browser tab after the sign-out page loads.

Your local records remain intact. No hosted service or paid project resource needs to be stopped.

Delete - I don't want to use this again

Complete removal returns the current entity to its pre-project state. The sequence begins with linked evidence so each dependency stays identifiable.

Protect Your Existing Data

Permanent deletion looks severe because it cannot be undone. Check every selection before you confirm it.

Remove only records beginning with BPS, BP-, or bps. in the current entity. Stop if any unprefixed record is selected.

Delete the linked maintenance incident:

Return to Assistance in the left menu.
Select Ticket.
Search for BPS-PR-001 paper-feed fault.
Select only the resolved project incident.
Use Actions to choose Put in trashbin.
Switch the ticket list to its trash view.
Search for BPS-PR-001 paper-feed fault again.
Select only the trashed project incident.
Use Actions to choose Delete permanently.

The printer incident is now removed with its completed task and recorded solution.

Move the four active computers to the trash:

Return to Assets in the left menu.
Select Computers.
Search for BPS-.
Confirm that the active results are BPS-LT-001, BPS-LT-002, BPS-LT-003, and BPS-DT-001.
Select only those four active computer records.
Use Actions to choose Put in trashbin.

The active computer list now contains no project records beginning with BPS-.

Move the printer to the trash:

Return to Assets.
Select Printers.
Search for BPS-.
Select only BPS-PR-001.
Use Actions to choose Put in trashbin.

Move the monitor to the trash:

Return to Assets.
Select Monitors.
Search for BPS-.
Select only BPS-MN-001.
Use Actions to choose Put in trashbin.

Permanently delete the computer records:

Return to the Computers list.
Switch the computer list to its trash view.
Search for BPS-.
Confirm that the results contain the four fleet computers and BPS-LT-TEMPLATE-TEST.
Select only those five project records.
Use Actions to choose Delete permanently.

Permanently delete the printer record:

Return to the Printers list.
Switch the printer list to its trash view.
Search for BPS-.
Select only BPS-PR-001.
Use Actions to choose Delete permanently.

Permanently delete the monitor record:

Return to the Monitors list.
Switch the monitor list to its trash view.
Search for BPS-.
Select only BPS-MN-001.
Use Actions to choose Delete permanently.

The current entity now contains no project asset records beginning with BPS-.

Delete the reusable computer template:

Return to Computers.
Select Templates in the menu bar.
Find BPS Standard Laptop.
Select only the project template.
Use Actions to choose Put in trashbin.
Switch the template list to its trash view.
Select only BPS Standard Laptop.
Use Actions to choose Delete permanently.

Delete the software license:

Return to the license list from earlier.
Search for BPS-SD-6.
Select only the fictional six-seat license.
Use Actions to choose Put in trashbin.
Switch the license list to its trash view.
Search for BPS-SD-6 again.
Select only the trashed project license.
Use Actions to choose Delete permanently.

Delete the software version:

Return to Assets.
Select Software.
Open BPS Support Desk.
Open the software version list.
Select only version 1.0.
Use Actions to choose Put in trashbin.
Switch the software version list to its trash view.
Select only version 1.0.
Use Actions to choose Delete permanently.

Delete the parent software record:

Return to the Software list.
Search for BPS Support Desk.
Select only the fictional software record.
Use Actions to choose Put in trashbin.
Switch the software list to its trash view.
Search for BPS Support Desk again.
Select only the trashed project software.
Use Actions to choose Delete permanently.

Delete the private saved search:

Return to Tools in the left menu.
Select Saved searches.
Find BPS Asset Assessment - Action Required.
Select only the private project search.
Use Actions to choose Put in trashbin.
Switch the saved-search list to its trash view.
Select only BPS Asset Assessment - Action Required.
Use Actions to choose Delete permanently.

Delete the five custom statuses:

Return to Setup in the left menu.
Select Dropdowns.
Select Common.
Select Statuses of items.
Search for BPS -.

You should see the five project statuses. No unprefixed status belongs in this selection.

Select only the five BPS status records.
Use Actions to choose Put in trashbin.
Switch the status list to its trash view.
Search for BPS - again.
Select only the five trashed project statuses.
Use Actions to choose Delete permanently.

Delete the fictional users last:

Return to Administration in the left menu.
Select Users.
Search for bps..

The project results should be bps.maya, bps.luis, and bps.priya.

Select only the three fictional user records.
Use Actions to choose Put in trashbin.
Switch the user list to its trash view.
Search for bps. again.
Select only the three trashed project users.
Use Actions to choose Delete permanently.

Remove the local inventory export:

Return to the folder where you saved the BPS fleet inventory CSV.
Select only the CSV export created for this project.
Delete the selected file through Windows File Explorer.

Your fictional BluePeak Services assessment is now removed. Existing unprefixed inventory in the current entity remains untouched.

Nice Work!

You did it! You completed a six-device BluePeak Services assessment in GLPI with clear evidence for every management decision.

You've learned how to:

Build an accountable six-device asset register across three asset types. Connect each device to ownership evidence. Add technical evidence. Add lifecycle evidence.
Translate device condition into searchable statuses. Capture the printer repair as an auditable Service Desk trail.
Isolate the three computers needing attention with a private saved search. Package the fleet evidence into a manager-ready assessment pack.
Secret Mission: Create the reusable BPS Standard Laptop template. Verify its prefilled defaults with a temporary test asset.

Ready to quiz yourself?