Repository navigation
Presenter Notes
Introduce ServiceOps as a connected operational workspace, built by Anushka Wijesundara. The deck illustrates product capabilities, not customer adoption or measured business outcomes. Screenshots are existing documentation examples; their visible versions and sample counts are not current production metrics.
Sources: ServiceOps/README.md; ServiceOps.wiki/Home.md
Frame these as intended benefits of connected workflows, not quantified ROI claims. ServiceOps combines service work with infrastructure and governance.
Sources: ServiceOps.wiki/Home.md
This is a product map. The iOS companion is introduced only on the final slide.
Sources: ServiceOps/README.md; ServiceOps.wiki/App-Guide.md
Show the dashboard as an interface example. The counts shown are sample data from documentation, not live service statistics.
Sources: ServiceOps.wiki/App-Guide.md; docs/readme/dashboard.png
Explain the end-to-end incident workflow. Records retain state and activity; access follows the signed-in user permissions.
Sources: ServiceOps.wiki/Operations-Manual.md; docs/readme/incident_detail.png
Service requests, requested items and fulfillment tasks are separate records. Approval decisions are not ordinary work tasks.
Sources: ServiceOps.wiki/Operations-Manual.md; docs/readme/catalog.png
Approval requirements vary with change type and configured governance. Do not imply that every change uses all approval paths. Planned dates, implementation, test and backout plans make change review concrete.
Sources: ServiceOps.wiki/Operations-Manual.md; ServiceOps.wiki/docs/diagrams/change_governance.png
CMDB and asset data depend on the records maintained or imported into the platform. Rack/location capabilities do not imply automatic discovery of every physical dependency.
Sources: ServiceOps/README.md; ServiceOps.wiki/Operations-Manual.md; docs/screenshots/cmdb.png
Task boards complement record workflows. Analytics, SLA tracking, knowledge and service status provide separate views for service performance. Do not describe a screenshot count as an adoption metric.
Sources: ServiceOps/README.md; docs/readme/task_board.png
AI is optional. Provider selection, data-sharing policy and permissions are configured by administrators. Outputs need human review; this is not a claim of autonomous safe change execution or flawless field population.
Sources: ServiceOps/README.md; ServiceOps.wiki/Home.md
Describe controls without claiming formal compliance certification. Consult the security and deployment guides for configuration responsibilities, MFA, passkeys and identity requirements.
Sources: ServiceOps.wiki/Security-and-Compliance.md; ServiceOps.wiki/Deployment-and-Recovery.md
Conceptual architecture, not an exact deployment inventory. Web and background workers share PostgreSQL and managed uploads. Identity, notifications, NetBox and AI are configured external integrations. Actual topology depends on deployment choices.
Sources: ServiceOps.wiki/Home.md; ServiceOps.wiki/Deployment-and-Recovery.md; ServiceOps/README.md
Use the repository and wiki to explore installation and workflows. This slide summarizes the web platform before the final iOS companion slide.
Sources: ServiceOps/README.md; ServiceOps.wiki/Home.md
Close with the native SwiftUI iPhone companion. The mounted iOS README documents local/LDAP sign-in with MFA, rotating access/refresh tokens, passkeys, biometric app lock, Home, work, approvals, CMDB, knowledge, diagnostics and notification inbox. Capabilities depend on permissions and server configuration. Existing simulator screenshots use fixture records. iOS repository: https://github.com/awijesundara/ServiceOps_iOS .
Sources: ServiceOps_iOS/README.md; ServiceOps_iOS/docs/screenshots/iphone-home.png; ServiceOps_iOS/docs/screenshots/iphone-work.png