Oracle PL/SQL and DBA
Packages, procedures, tuning, migrations, backup and recovery, patching, monitoring, and hardening.
Where the engagement includes it, packages are exercised with utPLSQL.
Enterprise ETL and reporting sit beside the database work: Informatica, OWB, ODI, OBIEE, and
shell + PL/SQL pipelines, plus object types, finance functions, migration, and data-quality checks.
Oracle Fusion
Finance and SCM techno-functional support, reporting, and data conversion.
Oracle Utilities WAM and IBM Maximo
Deep, hands-on delivery across work orders, job plans, asset hierarchies, data quality, conversion, and cutover,
with the Oracle data and integration work beside it.
Enterprise practice
Oracle Utilities WAM and IBM Maximo EAM
Practical AI Ops drafts and classifies around this work. It does not replace it. Delivery is hands-on Oracle Utilities Work and Asset Management and IBM Maximo: work orders, job plans, asset hierarchies, data quality, conversion, and cutover. Beside that sits Oracle DBA and PL/SQL, including utPLSQL, and enterprise ETL pipelines (Informatica, OWB, ODI, OBIEE, shell + PL/SQL). Production multi-agent AI orchestration has run beside this delivery since mid-2025. The engineer who can support the database and the EAM schema owns every change that touches production.
Enterprise practice
Practical AI Ops
Practical AI Ops is research, classification, and drafts with a human gate. Specialists stay on a bounded job, partitioned so untrusted input, privileged credentials, and external egress do not sit in the same lane. A coordinator keeps a queue a person can see. The gate exists because a bad send is harder to undo than a delayed one. The same person can support the Oracle Utilities WAM or IBM Maximo schema the draft is about.
Review path
Infrastructure as code
This site’s check, build, and publish steps are written down. Pilots are written down for the same reason: a stack that only exists on one machine cannot be reviewed, and it cannot be rebuilt when that machine is wrong.
How delivery is defined
Automation
Intake, classification, and a periodic digest exist so a person reviews a queue instead of raw input. Drafts are a starting point. A person decides what is sent. We do not publish a turnaround time.
Intake pipeline
Data pipelines
Public-sector procurement and RFP signals are scored, deduplicated, and imported into the system of record already in use. Separately, private documents stay on systems we operate so agents can query them without copying the corpus to a public model. Sources and volumes are not listed here.
Document lookup
Cloud architecture
ai.skeen.biz is a static site. Operational systems—the document store, the agent runtime, access to systems of record—are not this website. A public host is the wrong place for operational credentials. The failure mode is a marketing page becoming a door into the practice.
How this site ships
Systems engineering
External actions wait for a person. Access to systems of record is narrow and strongly authenticated. Secrets stay out of the repository. Changes to this site are reviewed before they are public. We describe the principles here, not an inventory of tools, locks, or connected systems.
Principles