All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

Data Center Management
Start now
More

Features

Industries

Reference

More

Data Center Management · Available now

See the service, asset and site work behind each decision.

Data Center Management keeps service ownership, equipment, rack placement and cable work alongside the service team's incident, change and request records. A service has an owner and criticality; an asset belongs to a service; a rack position belongs to an asset.

Start now Download Proto
  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewOpen incidents
Data Center Management · Incidents

Open incidents

Incidents in one list

New incident
Incidents in view
6
Low
2
Medium
2
High
1
Low2
Replace Rack B11 PDUVirtual machine cluster
27 Oct
Patch firewall pairMonitoring and alerts
12 Oct
Add
Medium2
Investigate east fabric lossPrivate network transit
20 Oct
Recover compute node 08Backup storage platform
02 Nov
Add
High1
Restore failed backup diskIdentity access platform
02 Nov
Add
Critical1
Tune west aisle coolingMonitoring and alerts
01 Nov
Add
Replace Rack B11 PDUIncidents · INC-58980
Low
StatusOpen
ServiceVirtual machine cluster
AssetRack B11 power distribution unit
Assigned toJonah Brooks
Opened at27 Oct
Request approvalINC-58980 · Replace Rack B11 PDU

The Request Coordinator approves or rejects submitted service work.

Waiting for Request Coordinator
ApproveReturn
Example screen with sample data
Tables, ready to use
12
Saved views
14
Roles with set permissions
7
Reports and dashboards
9
Features

Service and site work in context

Every feature works on the same records. Pick one to see the screen your team works in.

Service and asset context

Connect service ownership, equipment, location and operating state.

  • Service ownership
  • Equipment identity
  • Affected work
  • Services
  • Assets
  • People
  • Incidents
  • Rack positions
Explore service and asset context
OverviewIncident intake
Data Center Management · Service and asset context

Incident intake

Investigating waits for the service manager

New
SummaryPriorityServiceAssetAssigned toOpened at
Replace Rack B11 PDULowMonitoring and alertsRack C03 console serverRavi Shah24 Oct
Investigate east fabric lossMediumIdentity access platformRack C03 console serverNadia Chen19 Oct
Restore failed backup diskHighCustomer application hostingRack D02 backup applianceRavi Shah21 Oct
Tune west aisle coolingCriticalObject storage gatewayRack A12 compute node 03Priya Nair02 Nov
Patch firewall pairLowPrivate network transitRack A08 firewall pair ALuis Romero21 Oct
6 of 6 records
Replace Rack B11 PDUIncidents · INC-92420
Low
ServiceMonitoring and alerts
AssetRack C03 console server
Assigned toRavi Shah
Opened at24 Oct
Example screen with sample data
Process

From request to recorded finish

Service request to completed work ships ready to use. One step needs a named approval before the work moves on: Request approval (Request Coordinator).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Service context

    Confirm the owned service and the equipment involved.

    Replace Rack B11 PDUINC-58980 · Service Manager
    Service contextBy Service Manager

  2. Request intake

    Record requester, type, service and due date.

    Replace Rack B11 PDUINC-58980 · Request Coordinator
    Request intakeBy Request Coordinator

  3. Request approval

    The Request Coordinator decides whether work may proceed.

    Replace Rack B11 PDUINC-58980 · Request Coordinator
    Request approvalBy Request Coordinator
    ApprovalThe Request Coordinator approves or rejects submitted service work.

  4. Request fulfillment

    The technician begins approved work.

    Replace Rack B11 PDUINC-58980 · Service Technician
    Request fulfillmentBy Service Technician

  5. Completion

    Record the actual finish of work.

    Replace Rack B11 PDUINC-58980 · Service Technician
    CompletionBy Service Technician

  6. Service review

    Compare the outcome with the service and original request.

    Replace Rack B11 PDUINC-58980 · Service Manager
    Service reviewBy Service Manager

Start with Request to completion

Inside a record

Connect event and equipment sources

Open any incident to see its cable connections, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Status, Service, Asset and Assigned to.

  2. 2
    Cable connections

    Each line is linked to this incident.

  3. 3
    Who works on it

    Admin, Service Manager and Incident Coordinator, each with their own permissions.

  4. 4
    Process stages

    Incident intake and Incident acknowledgment, with the role that acts.

  5. 5
    Approvals

    Request approval, with who decides.

Open incidentsReplace Rack B11 PDU
Data Center Management · Incidents

Replace Rack B11 PDU

Virtual machine cluster · Low

Log activity
1
Record details
StatusOpen
ServiceVirtual machine cluster
AssetRack B11 power distribution unit
Assigned toJonah Brooks
2
Cable connections

Replace Rack B11 PDU

Cable IDFrom portTo port
FIB-A12-B04-01A12-SW1 Eth1/1B04-SW1 Eth1/12
FIB-A12-B04-02B04-SW2 Eth1/8A12-SW2 Eth1/2
COP-C07-D02-01C07-ST1 Port 2D02-BK1 Port 4
Cable connections
6
3

Who works on it

  • AdminManage Users, People, Services, Assets
  • Service ManagerManage Services, Problems
  • Incident CoordinatorManage Incidents, incident updates
4

Process stages

  • Incident intakeIncident Coordinator
  • Incident acknowledgmentIncident Coordinator
5

Approvals

  • Request approvalRequest Coordinator
    Approved
Example screen with sample data
Approvals

Decisions before work begins

OverviewApprovals
Data Center Management · Overview

Approvals

Signed in as Request Coordinator

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • SR-18955Rack installation
    Customer application hostingRequested by Jonah Brooks
    Submitted3dActions
  • SR-21362Cross-connect request
    Private network transitRequested by Luis Romero
    Submitted2dActions
  • SR-10534Power capacity review
    Monitoring and alertsRequested by Omar Haddad
    Submitted2dActions
  • SR-55027Remote hands support
    Identity access platformRequested by Omar Haddad
    Submitted5dActions

Who approves what

DecisionApprover
Request approvalThe Request Coordinator decides whether work may proceed.Request Coordinator
Approve service requestsRequest Coordinator
2 approval rules · set per role in Proto
Example screen with sample data
Who can approve what
Roles

A workspace for each role

Everyone opens Data Center Management to the work that is theirs. Pick a role to see what it starts with.

Admin

Configures access, references and imports across the app.

  • Manage Users, People, Services, Assets
  • View Incidents, Changes, service requests, rack positions, cable connections, integration receipts

Roles and permissions

Reports

Read the work behind the numbers

Review incident load, planned work, rack power and event outcomes.

Overview
Data Center Management · Overview

Data Center Management dashboard

This quarter

Changes in view
6
Approved
3
Implementing
3

Incidents by status

How far records got this quarter

StageReachedStep
Open41
Acknowledged2971%
Investigating1759%
Resolved1059%

Number of incidents by status

Sample counts per stage

800
50Open
30Acknowledged
20Investigating
60Resolved
80Closed
Example screen with sample data
  1. 01Incident work by priority

    Count incidents by priority and status for each affected service.

  2. 02Time to acknowledgment

    Compare incident opening and acknowledgment dates by service and assignee.

  3. 03Open incident load

    Group open and investigating incidents by service, asset and assigned person.

  4. 04Change window review

    List approved and implementing changes with their scheduled start and end dates.

  5. 05Request completion

    Compare requested, due and completed dates by service and request type.

  6. 06Rack power register

    List recorded power by rack code, unit start and linked asset.

  7. 07Cable work by incident

    Group cable identities and ports under their linked incident.

  8. 08Problem ownership

    Compare open, investigating and known-error problems by service and owner.

  9. 09Inbound event outcomes

    Count integration receipts by provider and receipt status.

All reports and dashboards

Who it's for

Built around your operating shape

See how Data Center Management fits your kind of team.

Enterprise data centers

Keep owned services and physical equipment in the same operating review.

Colocation operations

Track rack and cable observations with service work in shared facilities.

Managed infrastructure teams

Coordinate service ownership, incidents, changes and inbound event review.

Controls

Keep each handoff reviewable

Each stage of service request to completed work names the role that acts and the status it records, so a change is never anonymous.

OverviewService request to completed work
Data Center Management · Process

Service request to completed work

Each stage, the role that acts and the status it records

Process stages
11
Approval steps
1
Roles involved
6
Tables touched
6
Request approvalApproval
Request Coordinator
StatusSubmitted → Approved
Request fulfillment
Service Technician
StatusApproved → in progress
RecordsServices
Completion
Service Technician
StatusIn progress → Completed
RecordsServices
Service request to completed work
  1. Start
    Request approvalSubmitted → Approved
    Request Coordinator
  2. Step
    Request fulfillmentApproved → in progress
    Services
  3. Step
    CompletionIn progress → Completed
    Services
  4. Step
    Change reviewReview → Approved
    Changes
  5. Step
    Problem follow-upOpen → Investigating → known error → Resolved
    Problems
Example screen with sample data

See each stage in detail

AI agent

Ask Proto to prepare the review

Prepare service operations review with the people responsible for each decision.

It can

  • Incident Coordinator: Show open incidents by priority, assigned person and affected service.
  • Change Manager: List changes in review with their risk, scheduled window and rollback plan.
  • Asset Manager: Compare rack positions with their linked asset tags and services.
  • Service Manager: Summarize failed and rejected integration receipts by provider.

Stays with a person

  • The Request Coordinator decides whether submitted work is approved.
  • The Change Manager and service owner review the risk of planned work.
  • The Service Technician checks rack, power and cable observations against the physical installation.
  • Proto can prepare lists and explain linked records, but the responsible person checks the evidence and makes the decision under their access.

Set up an agent

Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • Data Center Management
  • Event source
  • Identity source
  • Equipment inventory
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 12 tables
12tables
  • Service and asset context5
  • Rack space and power3
  • Cable connections4
  • Incident response6
  • Changes and windows3
  • Requests and fulfillment3
  • Problems and receipts5
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Agree the service boundary

    Name the services in scope, their owners, criticality and the Request Coordinator who approves requests and the Change Manager who checks planned work.

  2. Check the equipment register

    Compare asset tags, serial numbers and locations with the physical equipment. Agree rack code, port label and power conventions.

  3. Load linked records

    Add people and services first, then assets, rack positions and a sample incident with updates and cable work.

  4. Rehearse work decisions

    Run a submitted request through approval and completion. Review a complete and incomplete change plan. Check an incident with missing priority and an already advanced case.

  5. Check event intake

    If a source sends events, reconcile provider and external identity across received, applied, rejected and failed receipts.

Read the implementation plan

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for Data Center Management.

All questions
How do I get started?

Click Get started, then use Proto to configure Data Center Management for your business. Pilot one owned service, a known set of tagged assets, an incident and a request with named decision owners.

What physical information can the team record?

Rack positions hold a rack code, starting unit, occupied height, power and linked asset. Cable connections hold endpoints, cable identity, type, installation date and a linked incident.

Can an incident show affected equipment?

Yes. An incident links to a service, asset and assigned person. Dated updates retain their author and incident reference.

How does request approval work?

The Request Coordinator reviews submitted work. Approved requests can enter delivery; in-progress requests can be completed with the actual finish date.

What must be present before a change is approved?

A change in review needs risk, a scheduled start and end, and a rollback plan. The Change Manager reviews the planned work for the affected service.

Can we track longer investigations?

A problem record keeps the service, owner, statement, root cause and investigation state. It sits alongside the immediate incident response.

How do incoming events appear?

Integration receipts retain the provider, external event identity, received date, payload hash and processing state. Agree the sender and event mapping during setup.

Can we import equipment from another register?

Yes, after agreeing stable asset tags, service references, location text and the source of each value. Reconcile a pilot group against physical labels.

Who can enter rack and cable observations?

Give authorized Service Technicians access to those screens and check their submissions against the linked asset or incident and observed values.

What drives the cost?

Use the pricing page for the current platform policy and plan any imports, connections and agent usage during implementation.

Set up Data Center Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

Start now Download Proto

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appData Center Management

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.