Clear answers.
A confident next step.

Trident is Neptune’s connection layer for JobBOSS Classic. It gives approved applications and compatible AI clients defined ways to read information, produce business outputs and carry out supported JobBOSS operations. JobBOSS remains your system of record; you do not migrate to a second ERP.

Trident is not the AI model or a replacement chat application. You choose the AI client or application that uses the connection. Neptune develops and supports Trident, and ECI is an authorized reseller.

Integration, also called Connect, supplies the REST API for application-to-application connections. It does not require AI.

Insights supplies read-only Reports & Analysis, Forms & PDFs and JobBOSS Knowledge for a compatible AI client. It does not include the machine Integration API or transactional AI writes.

Automation, also called Act, combines Insights with the Integration API and supported transactional AI access. Start with the outcome you need: connect software, investigate information or perform approved work.

For Insights and Automation, you bring a compatible AI client and the subscription it requires. Trident is not tied to one AI provider. ChatGPT and Claude are examples to discuss during setup; the specific product, plan, connection method and administrator settings must support the intended Trident connection.

We recommend a company-managed business workspace for business information. AI subscription charges are separate from Trident. Integration can connect another application directly through the REST API without an AI subscription.

JobBOSS Knowledge gives a compatible assistant curated JobBOSS-specific reference context through Trident. It helps the assistant interpret terminology, explain processes and work with the product’s reports and operations rather than rely only on general ERP knowledge.

It complements live report results; it is not a copy of your current company database. Knowledge is included in Insights and Automation. As with other AI output, check consequential advice and results against the source information and your business process.

Trident runs alongside JobBOSS in your environment. Your ERP database remains there; Trident does not move it into a new cloud ERP. However, information returned to a cloud AI client—such as a requested report or transaction result—is processed by that provider. A connected external application has its own information flow as well.

Installing an AI desktop app does not make its model run locally. During setup, identify the information the workflow needs, where it will be processed and which connections your IT team approves. On-premises Trident is not a promise that every connected workflow stays on premises.

That depends on your AI provider, product, plan and settings. OpenAI states that ChatGPT Business and Enterprise data is not used for model training by default. Anthropic states the same default for its commercial products. Optional data-sharing or feedback settings can change the treatment; individual consumer plans have their own policies.

No model training does not mean no processing or retention. Review those controls separately. Neptune’s Product Terms do not permit use of your ERP content to train a general-purpose AI model without a separate express agreement; your independently selected provider is governed by its own terms.

A local or privately hosted AI arrangement can be assessed where the chosen model and client can use Trident’s supported interfaces. Your IT team needs to review the complete path: model hosting, client, connected tools, network access and any external services.

A desktop application that calls a cloud model is not local inference. Tell us at the start when information must stay within a particular network or approved environment, so we can assess the deployment before it is ordered. A fully isolated AI environment is not included simply by purchasing Trident.

User-connected AI access uses the Trident Agent and the authenticated JobBOSS user and company context. The user must be signed into JobBOSS, with the appropriate access; normal JobBOSS seat requirements still apply. Your administrators decide which workstations and AI accounts are enabled.

Machine API integrations use separate API credentials. Those credentials do not automatically inherit an individual JobBOSS user’s permissions. Treat them as privileged integration credentials and agree the integration’s access and operating scope during implementation.

Insights is read-only and cannot create, update or delete JobBOSS records. Automation can request supported changes within the user’s authorized access. With human approval enabled, the operator reviews the proposed action before Trident executes it.

Approval behavior is configurable, so not every setup requires a fresh click for every request. Start with explicit review for consequential writes, agree any broader approval settings and verify the saved result. Unattended API integrations use their configured machine authority, not the interactive AI approval process.

Trident records activity around its requests and operations, including the relevant context, approval decisions and outcomes. Those records help investigate a reported issue and check a consequential action against JobBOSS.

This is not a recording of everything a user does in an AI application. Conversation history, model reasoning and actions performed through other connected tools are separate. Review the available logs and your retention requirements during setup, and retain the business records you need.

Start with the specific information and requirements, not the industry label. Neptune can work with your IT/security team to review Trident’s role, the selected AI service and the proposed data flow before enabling access.

A Trident licence or a generic “Enterprise” AI plan does not by itself establish CMMC compliance, FedRAMP High authorization or permission to process controlled information. Validate the exact service offering, deployment boundary and contractual controls against your requirements. Sensitive information should only enter a connection your organization has approved.

Trident is built for SQL Server-based JobBOSS Classic, with version 17 and later as the starting baseline. Confirm your exact version, build, database configuration and intended operations during the environment review.

It is not a connection for the older Microsoft Access-based JobBOSS database, and this offering is not for JobBOSS². Keep the required JobBOSS licences and infrastructure in place. Server moves or major environment changes should be coordinated with Neptune before switching the connection.

A hosted environment needs a joint review with the hosting provider. Trident installation, user-session and Agent access, the chosen AI connection and permitted network traffic all need to fit the host’s policies.

As of October 20, 2026, Summit-specific validation is being coordinated; it is not yet a completed compatibility sign-off. An AI app being allowed on a terminal server is not the same as the full Trident workflow being tested. Bring your host into the initial review so the deployment path is clear.

Trident supplies defined JobBOSS capabilities. An application integration still needs a technical owner to map the data, implement the connection and test the result. An AI workflow needs clear inputs, supported operations and an agreed review process. The subscription is not a prebuilt connector for every system or a completed custom automation project.

Bring one concrete use case—such as a warehouse handoff, AP workflow or scheduling requirement. Neptune can identify what the existing interfaces support and what additional software or scoped work is needed. Trident does not automatically replace a scheduling engine or reproduce every JobBOSS screen and custom workflow.

Yes, this is a practical Automation use case when the requested operations are supported. A compatible AI client can interpret supplied order or RFQ information, prepare structured values and ask Trident to create the JobBOSS record through the configured approval workflow.

Review the customer, part, quantities, pricing and other required values before the write, then verify the saved record. Reading a mailbox, extracting a document and sending email are capabilities of the chosen AI client or separately connected systems—not a mailbox service supplied by Trident. Confirm the document formats and mapping in your first scenario.

Insights and Automation provide Reports & Analysis and Forms & PDFs. Supported reports can return structured results and reusable Excel output; supported document forms can generate PDFs for the business process.

Existing custom Crystal Reports layouts are not automatically imported or reproduced by Trident. Also distinguish a Trident-generated report from a narrative or file an AI creates from its results. Show us the report, layout or document you need so we can confirm existing coverage or scope additional work.

Start with one useful outcome and a process owner. Neptune reviews the JobBOSS environment and intended connection with your IT or hosting team, establishes the licensed installation and access, and connects the agreed application or AI client.

Then we test a representative scenario, verify its results and orient the users to the relevant permissions, approvals and support process. Keep your ECI representative involved for the commercial and services coordination. Installation, onboarding and further workflow development are separately scoped; timing depends on the environment and readiness, not just the package name.

An active paid subscription includes Trident product maintenance and support for the purchased capabilities. Neptune investigates its connectivity, authentication, supported operations and documented functionality, and supplies applicable fixes and updates.

A Trident defect is different from an AI’s interpretation, a prompt, a custom workflow or an unrelated JobBOSS/infrastructure issue. Prompt coaching, broader AI training, integration development and general consulting are separately scoped. For a product issue, contact Neptune with the operation, time, expected result, actual result and relevant error details. We can help identify the appropriate next step without promising a particular external AI answer.

Trident is not priced per user. The order defines the customer, licensed scope, capabilities and term. A machine-API entitlement covers one configured JobBOSS database at a time; user-connected access follows the authenticated user’s authorized JobBOSS databases and permissions. Trident does not add JobBOSS seats or include AI subscriptions.

Budget separately for the selected AI service and any installation, onboarding or customer-specific implementation work. ECI can quote the subscription and applicable services, including annual billing and co-termination arrangements where agreed. The accepted order determines pricing, dates, billing and renewal—not a monthly-equivalent marketing figure.

Start with a short recorded demonstration, or try the interactive sample-data walkthrough. For a deeper view, the full workflow demo follows a session through quotes, documents, approval, orders, inventory and fulfillment.

Then use “Find your starting point” to describe the system, recurring question or task you want to improve. Include your ECI representative so Neptune can coordinate the conversation. We will help confirm the package, environment and first practical step. The public interactive walkthrough uses sample data; it is not a live connection to your JobBOSS system.