Data Processing & Security
An overview of how supported customer workloads move through the MERCY Systems processing workflow.
1. Processing Architecture
MERCY Systems separates its public-facing business infrastructure from the proprietary Naamah production processing environment.
The Naamah engine is not provided as a public web service and is not exposed through this website.
2. Domain Review
Submitted jobs may be reviewed before processing to determine whether the requested workload falls within the engineering domains supported by MERCY Systems.
Domain review is intended to determine whether the application is appropriate for the service. Mathematical difficulty alone does not determine whether an otherwise supported engineering problem is accepted.
3. Offline Processing
Approved production workloads are intended to be transferred into an isolated processing environment for execution by the proprietary Naamah mathematical engine.
The processing architecture is designed so that customers receive completed processing results rather than direct access to the Naamah engine.
4. Verification
Completed processing results may undergo independent verification against the original problem and applicable output requirements before being approved for customer delivery.
5. Delivery Formats
Depending upon the engagement and problem type, supported result packages may include solution-vector, tabular or matrix-oriented outputs. Current planned production formats include VEC, CSV and MTX where appropriate to the workload.
6. Customer Data
Customers should provide only the information and datasets necessary for the agreed processing engagement. Additional handling, retention, deletion or confidentiality requirements should be established before sensitive production data is transferred.
7. Security Limitations
Isolation and controlled processing can reduce particular categories of exposure, but no technical or operational system can guarantee absolute protection against every possible security event. MERCY Systems therefore avoids representing any system as universally or permanently immune from security risk.
8. Production Workflow
9. Contact
Organizations interested in discussing processing, confidentiality or data-handling requirements may contact [email protected].