AIMLUX.ai Consulting Solutions (ACS) onboard client forms

"Mapping Your Enterprise Digital Infrastructure"

__________________________________________________________________________________

AIMLUX.ai Consulting Solutions (ACS) onboard client forms bridge the gap between high-level operational requirements and the technical specificities of the Equitus.us ecosystem (KGNN, ArcXA, EVS, and ICAM).

The following onboarding flow is designed to capture the "mission profile" of the user while mapping them to the correct software modules.

• Identity: Sector classification and organizational profile.

• Scale: Number of users and deployment type (Cloud/Hybrid/On-Prem).

• System Type: Alignment with Transactional Core, Portals, or Batch Processing.

• Architecture: Selection of specific Equitus modules.

---

STAGE 1.    Initial Engagement: The "Mission Profile" Form: Sign Up $10,000 Consulting Credit

This is the "Identity" phase. It establishes who the user is and the scale of their operational footprint.

Client Identity & Scope

• Organization Name: (e.g., USSOCOM, Dept of Energy, Global Logistics Corp)

• Sector: [ ] Military [ ] Intelligence [ ] Civil Government [ ] Enterprise

• Total User Base: * [ ] Tier 1: Small Team (<50)

• [ ] Tier 2: Regional/Division (50–500)

• [ ] Tier 3: Enterprise/Command (500–5,000)

• [ ] Tier 4: Global/National (>5,000)

• Security Requirement: [ ] Unclassified [ ] FOUO [ ] Secret [ ] TS/SCI [ ] SAP/CAP

---

Stage 2.    Infrastructure & Environment Form

 

Intelligent Ingestion Systems (IIS) Form:  will be deployed and which hardware (like IBM Power10/11) is required.

Technical Environment

• Primary System Type: * [ ] Transactional Core (Legacy ERP/Mainframe migration)

• [ ] Real-Time Edge (IoT/Camera/Sensor feeds)

• [ ] Analytical Sandbox (Big Data/R&D)

• Deployment Architecture:

• [ ] On-Premise (Air-Gapped): (Zero external cloud connectivity)

• [ ] Hybrid: (Local ingestion with cloud-based analytics)

• [ ] Public Cloud: (GovCloud, AWS, Azure, IBM Cloud)

• Hardware Status:

• [ ] Existing x86 Cluster

• [ ] IBM Power System (10/11) Native

• [ ] Requires Edge Appliance (Equitus Fusion/Ruggedized)

---

Stage 3.    Product-Specific Ingestion Config (The "ACS Blueprint")

This section routes the client to the specific Equitus module based on their data needs.

If the goal is...	Module to Configure	Form Data Needed
Unifying Siloed Data	KGNN (Knowledge Graph)	Type of data (PDFs, Logs, Databases), Number of sources, Ingestion frequency.
Migration/Integration	ArcXA (Mapping Layer)	Legacy system type, Mapping complexity (Semantic vs. Logic), Target destination.
Video/Imagery AI	EVS (Video Sentinel)	Number of camera feeds, Detection requirements (Faces, Objects, Behavior).
Secure Access	ICAM (Identity Access)	Current Auth provider (Active Directory, LDAP), Clearance level mapping.

---

Stage 4.    Consultation Request: "MaaP" Onboarding:

Client selection :  Engagement model for the consulting phase.

Consulting Model

• [ ] Migration as a Product (MaaP): Fixed-price migration of legacy systems into a modern knowledge graph.

• [ ] Intelligence as a Service: AIMLUX-managed exploitation of data using Equitus tools.

• [ ] Rapid Prototyping: 30-day "Sprint" to prove Ai Video EVS/KGNN efficacy on a sub-dataset.

---

Onboarding Flow Diagram

Next Steps for ACS

Once the user submits these forms, the ArcXA Semantic Alignment Layer can automatically begin mapping the client's metadata into a KGNN-ready blueprint, allowing for a "Low-Touch" transition from consulting to production.