One Project Authority: Cloud Save, Recall, and Local Integrity in API/NDE 2.0
In inspection work, the most dangerous project copy is often the one everyone assumes is current.
A technician saves a local project. The office saves another copy. A cloud backup is created. An Android device returns an updated assignment. Someone recalls an older project file to check a drawing. Before long, several versions exist, each containing part of the inspection.
That creates familiar problems: outdated CML data, missing drawing changes, duplicate entry, and uncertainty about which file should become the final report.
API/NDE 2.0 addresses that problem by placing local saves, cloud saves, cloud recall, project loading, and Android imports on the same project authority.
The goal is direct:
One project should produce one trusted project state.
Cloud Save and Cloud Recall improvements in API/NDE 2.0 are designed to protect that principle. Additional integrity checks validate project data before it becomes an authoritative backup. Small projects and larger chunked projects follow the same validation path. Invalid or tampered data is rejected instead of silently becoming the version the team relies on.
That matters because inspection data is not just a collection of files. It includes equipment identity, CMLs, drawings, NDE callouts, photos, calculations, field results, and report content that must remain connected from the first inspection activity through final issue.
The problem with disconnected project copies
Traditional inspection workflows make it easy to create separate versions of the same project.
A project may begin in the office with a vessel drawing and inspection checklist. A technician then receives a field copy on an Android device. The technician adds readings, photos, and drawing information. Meanwhile, the office team may continue updating the original project.
When the field data returns, someone has to decide which version is current and how to combine the changes.
That is where manual reconciliation begins.
You may have to compare file dates, open several project copies, review drawings side by side, re-enter thickness readings, or rebuild a report after discovering that the recalled project did not include the latest field changes.
The same problem appears when cloud storage is treated as a simple backup location rather than part of the project workflow. If a cloud save accepts incomplete, malformed, or altered project data without validation, the backup can become the source of a new problem.
A backup is only useful if it can be trusted.
API/NDE 2.0 is built around a different approach: every save and load operation must respect the same project structure and authority.
One project authority across every operation
In API/NDE 2.0, Local Save, Load, Cloud Save, Cloud Recall, and Android Import are no longer treated as separate paths with separate assumptions.
They all operate from the same project authority.
That means the project identity, equipment structure, inspection data, and drawing information remain connected regardless of where the operation occurs:
Local project → Cloud Save → Cloud Recall → Local project
Or:
Master project → Android Import → Validated project state → Reporting
The purpose is not to create another layer of administration. It is to prevent different parts of the workflow from quietly producing different versions of the truth.
When a project is saved locally, the same authority governs what is stored. When it is saved to the cloud, the cloud version is checked before it is accepted. When it is recalled, the project is reconstructed from the validated project data instead of being treated as a loose collection of unrelated files.
When Android inspection work is imported, the returned information is brought back into that same project authority.
This gives inspectors and reviewers a clear answer to a basic question:
Which project state are we working from?
The answer is not “the newest file in the folder.” It is the validated project state recognized by the workflow.
Cloud Save now checks before it becomes the backup
Cloud Save is most valuable when it protects project continuity without introducing a second source of uncertainty.
API/NDE 2.0 adds integrity checks around cloud saves so project data is evaluated before it becomes the authoritative cloud backup.
Those checks apply to both small projects and larger projects handled in chunks. The size or transfer method does not create a separate standard for acceptance. The project still passes through the same integrity path before it is treated as valid.
This is important for real inspection projects because they rarely contain only one type of information. A project can include:
- Equipment and component information
- CML and thickness data
- Inspection checklists
- Photos and comments
- Sketches and digital drawing information
- NDE locations and callouts
- Engineering assessment results
- Report settings and supporting documents
A save that contains only some of those elements is not necessarily a usable project backup. The project must remain structurally coherent.
The improved Cloud Save process is designed to reject project data that is invalid or has been tampered with. It does not silently accept that data and allow it to replace the trusted cloud version.
That removes a dangerous form of guesswork from project management. The team does not have to discover later that a backup was incomplete or unusable after the local copy has already been lost or overwritten.
The dashboard view makes that control practical. You can see the full project overview in one place, including active projects, current assignments, cloud actions, and recently updated projects. Instead of checking scattered folders or asking which copy was touched last, you can work from a single operational view that shows what belongs to the current project authority.
Cloud Recall reconstructs the project, not just the file
Saving the right data is only half of the problem. The project must also be recalled correctly.
Cloud Recall improvements in API/NDE 2.0 focus on reconstructing the correct project state, including the drawing information that makes the inspection usable in the field and in the final report.
That distinction matters.
An inspection drawing is not merely a picture attached to a report. In NDT Integrity workflows, digital drawings can contain equipment structure, CML locations, inspection objects, NDE callouts, and other information used by inspectors. If a recalled project loses the relationship between those objects and the project structure, the team is forced back into manual reconstruction.
That can mean redrawing equipment, recreating CML locations, checking whether a callout matches the correct component, or comparing the recalled project against an older local version.
A reliable recall must restore the project as a working inspection record.
API/NDE 2.0 is designed to bring back the correct state and drawing information through the same project authority used by Save and Cloud Save. This supports continuity between office preparation, field execution, review, and reporting.
The Registry view supports that same control by keeping equipment identity and planning tied to the project instead of split across separate tools. You can review the equipment registry, see due-date planning clearly, and confirm what is coming due without breaking the connection to the active project record. That matters when the recalled project needs to restore not just files, but the equipment structure and timing the inspection depends on.
The result is a practical workflow:
- Build or update the project.
- Save it locally or to the cloud.
- Recall the validated project when needed.
- Continue working from the same project structure.
- Use the same connected data for review and reporting.
That eliminates the need to guess which copy contains the latest drawing or whether a field update belongs to the project being reviewed.
Android Import returns work to the same authority
Field mobility only helps when field data returns cleanly to the project.
NDT Integrity supports Android-based field workflows, including tablet checklists, direct Bluetooth UT gauge readings, and SketchMapp for CMLs, equipment sketches, and NDT callouts. Those tools are useful because they let technicians collect information where the work occurs rather than writing it down for later transcription.
But the return path is just as important as the field collection.
In API/NDE 2.0, Android Import operates from the same project authority as local and cloud operations. The imported project data is not treated as an unrelated copy that must be manually reconciled with the office project.
This supports the broader workflow:
Office setup → Android field work → Import → Validation → Review → Report
The same principle applies whether the technician is collecting readings, adding photographs, updating a drawing, or placing an NDE callout. The imported information must remain connected to the project and its equipment.
That removes duplicate data entry between the tablet and the report. It also reduces the risk of transferring a reading into the wrong component or rebuilding a drawing after the field work is complete.
Local integrity protects the working copy
Cloud controls are important, but inspectors and technicians still need dependable local project handling.
Local Save and Load are often used during active inspection work, especially when teams are working with field devices, intermittent connectivity, or staged review processes. A local project must remain just as reliable as the cloud version.
The API/NDE 2.0 approach is to keep local and cloud operations aligned instead of allowing each to develop its own interpretation of the project.
That means:
- Local Save uses the same project authority.
- Local Load reconstructs the project from the same controlled structure.
- Cloud Save validates data before accepting it.
- Cloud Recall restores the correct project state.
- Android Import returns field work through the same authority.
A project is not considered correct simply because it opens. It must retain the information needed to continue the inspection and produce the report.
This is especially important when a project contains digital drawings, CML layouts, photos, assessment results, and inspection findings that depend on one another.
The workflow supplies only what the data says. It does not ask an inspector to guess which project copy is newer or which drawing should be treated as authoritative.
From validated project state to final report
A controlled project authority also strengthens reporting.
NDT Integrity’s API inspection workflows connect CML management, automated calculations, digital sketching, photos, inspection documentation, and professional report generation. The API inspection platform is designed to carry field data into a client-ready deliverable without recreating the inspection by hand.
The same principle extends to the folder-based workflow: place the project documents in the project folder, use the one-click upload process to create a report that is up to 98% complete, add photo comments directly, and print the report. Each step depends on having a reliable project record behind it.
If the project state is uncertain, the report is uncertain.
If the project state is validated and recalled correctly, the report can reflect the approved inspection data, drawings, photos, calculations, and supporting information that belong to that project.
User-controlled branding, custom cover sheets, and report colors can then be applied without changing the underlying inspection authority. The presentation can be adjusted while the source data remains controlled.
Built for field-built inspection workflows
API/NDE 2.0 is being developed around the way inspection teams actually work: across offices, field devices, technicians, reviewers, and report preparation.
That work includes more than entering readings into a form. It includes maintaining component identity, updating drawings, attaching evidence, completing engineering assessments, and preserving the relationship between field observations and final conclusions.
The Cloud Save and Cloud Recall improvements strengthen that complete workflow by ensuring that each operation works from the same project authority.
Invalid or tampered data is rejected. Small and chunked projects are validated through the same path. Cloud recall reconstructs the correct project state and drawing information. Local Save, Load, Cloud Save, Cloud Recall, and Android Import no longer represent disconnected copies of the inspection.
They are different operations on the same authoritative project.
That is the foundation required for dependable inspection reporting:
Save once. Recall correctly. Continue from the validated project state.
Explore the API/NDE 2.0 release direction, or see how SketchMapp connects digital drawings to field inspection and reporting workflows.
One platform. One project. One authority.