Component Management – LDARtools

Editing a component

Find the component in a tour, or search for the tag number.
Tap the tag number to enter the Quick View and tap View Details.
On the Component Details screen, find the property you wish to edit — properties are grouped under section headings, and you may have to look across the tabs — then tap it. How it opens depends on the property type:
- Text and number properties open an editor just below the row, with a blue tick to accept the value and a red cross to cancel. The row above keeps showing the current value until you accept. A number property brings up the number pad; a text property brings up the full keyboard.
- Yes/No properties switch in the row itself, using a Yes / No toggle.
- Lookups, Type, SubType and Profile open a bottom sheet. It is headed with the property name and how many values are available — for example 0 values · clearable — and has Cancel and Confirm at the bottom, with Confirm staying grayed out until you pick something. A property shown as clearable is one whose value you can remove. The list can legitimately be empty: SubType and SubSubType are driven by the component's Type, so a Type with no subtypes shows 0 value.
Confirm by tapping Save. The Change Why is asked for at this point, not as you go — see below. Profile is the one exception.

Nothing is saved as you go — each change is held so you can review it first:

The row is outlined and marked CHANGED, with the previous value shown struck through underneath the new one, so you can see exactly what you are about to change. A bar across the bottom keeps a count — for example "1 field changed" — with Discard to abandon all of them and Save to keep them. Discard asks you to confirm first ("Discard 1 change?"), so you cannot lose a batch of edits with a stray tap.

You are asked for the Change Why once, when you save. The same reason applies to every field you changed in that edit, and the sheet tells you how many it covers — for example "One reason applies to all 1 field change in this edit". Use the Filter box to find the reason you want, select it, then tap Save. The sheet's own button reads Save 1 change (with the count), and stays grayed out until you pick a reason.

Changing the Profile

Profile is handled separately from the other properties, because it is a transition rather than a simple edit. As the screen puts it, a profile change carries its own reason and effective date, separate from the component's Change Why.

Tapping Profile opens Edit Profile. It shows the Current profile and, under New Profile, every profile you can move the component to — the current one is not offered, so from Active you see DeActivated, ReAct, TUinService and TUPurged. Choosing one reveals the Profile Change Why reasons that apply to it, headed with the profile name so you can see which set you are looking at, along with an Effective Date that defaults to today. If you choose a TUx profile — TUinService or TUPurged — the TU Source and TU Date Available fields appear as well. Apply change stays grayed out until the profile and its required fields are set.

After you save

If you have the Approver role, the change will be implemented upon checking in.

If you do not, the change is recorded as a suggestion for someone else to approve. The staged look is replaced: the outline, the struck-through previous value and the CHANGED badge all disappear, and the row shows the new value with a blue note beneath it — Suggested by [name] · pending approval — so you can see it has been captured and is waiting on an approver. Until then the component keeps its original value everywhere else.

Adding a Component via Copy to Add

Find a component similar to the one you are trying to add, search for its tag number, and open its Quick View screen.
Tap View Details if you wish to confirm properties other than what is available in Quick View.
Tap the 3-dot icon to open the Action Menu, select Copy to Add.
Select an appropriate Active Why.
Chateau Mobile will copy the exact specs and add an “x” behind the tag number. Enter a real tag number and edit any properties that do not match the new component.
Confirm by clicking Save in the top-right corner.
Perform the initial inspection if necessary. The InspectionWhy will automatically be assigned as “New.”

Editing Several Components at Once

From the component list you can select more than one component and act on all of them together.

Tap Select. Checkboxes appear beside every component, the button changes to Select all, and the back arrow becomes an × for leaving select mode. As you tick components the count above the list changes to read, for example, 2 selected of 15 shown. Tap the components you want, or Select all to take everything the list is currently showing. The count at the top reads, for example, "3 selected of 362 shown" — the selection is scoped to what is in the list, so a search or filter narrows what Select all picks up. Tap the × at the top to leave selection mode.

With components selected, tap Actions · N selected at the bottom of the screen. Each option tells you how many components it will affect, and an option you cannot use is grayed out with the reason why — Re-base tag group shows "Needs components sharing one base tag" when the components you picked do not share one.

Multi-edit properties

The Multi-edit screen is headed with the component count and the instruction Set a value to apply it to all N selected, and lists the fields you can set. Where every selected component already has the same value it is shown; where they differ you will see Multiple values.

Set a value and the row is highlighted with a note such as "applies to all 3", so you can see it will be written to every selected component. Fields you leave alone are not touched. A counter at the bottom keeps track — for example "2 fields → 3 components" — and Save becomes available once you have changed something.

Profile behaves as it does on a single component. It opens Set Profile, which carries its own reason and effective date separate from the Change Why. Choosing a TUx profile adds the TU Source and TU Date Available fields, and the Profile Change Why list is then narrowed to the reasons that apply to that profile.

When you save you are asked for the Change Why once, with a search box to help you find the reason, and it applies to the whole edit.

Re-base tag group

Use this to renumber a base tag and its subtags together. Every component you select has to share the same base tag.

The sheet tells you what will happen — the part of the tag before the first "." is replaced and the suffixes are kept — and previews every tag before and after as you type the new base. Typing 417new against 417, 417.1 and 417.2 gives 417new, 417new.1 and 417new.2. Check the preview, then tap Apply.

Did Not Monitor

This option only appears when the Did Not Monitor field event is enabled for your database. If it is switched off in Chateau, the Actions sheet will not list it. The sheet is headed Did Not Monitor · N components and states what it will do: "Records a field event with a reason. GPS is captured at your current location. Inspection requests remain unsatisfied for review." Choose the reason — Changed To Insulated, Changed To Welded, Could Not Locate, Deactivated, Difficult To Monitor, Insulated, Other, Temporarily Unavailable or UTM — then tap Record for all, which stays grayed out until a reason is selected.

GPS is captured at your current location for the whole batch. The inspection requests for those components remain unsatisfied so they can be reviewed — recording Did Not Monitor does not clear them.

What the component list shows afterwards

Back on the list, components carry chips showing what has happened to them. A change you saved as a suggestion shows a purple Pending chip alongside the component's existing status chip, so Pending and Due sit together on a component that is both awaiting approval and still due. DNM appears where a Did Not Monitor event has been recorded.

Adding a Component via Copy To Add

Find a component similar to the one you are trying to add, search for its tag number, and open its Quick View screen.
Tap View Details if you wish to confirm properties other than what is available in Quick View.
Tap the 3-dot icon to open the Action Menu, select Copy to Add.
Chateau Mobile asks for the reason first, in a Select An Active Why dialog — "Select a reason why you are adding a new component." The choices are Field Find, Field Find AVO, New Construction, New Rule, New Rule Interpretation, New Unit and See Document.
Chateau Mobile will copy the exact specs and add an “x” behind the tag number. Enter a real tag number and edit any properties that do not match the new component.
Confirm by clicking Save in the top-right corner.
Perform the initial inspection if necessary. The InspectionWhy will automatically be assigned as “New.”

Adding Components Via Photo

Enter the Quick View of any tag to access the 3-dot icon for the Action Menu. Tap it and select Add Via Photo.
Add Via Photo opens the device camera straight away. Take a photo of the general vicinity where the batch of new components is located.
Select Active Why, LUnit, Stream, Location Description and Physical State in the Primary Properties page, and tap Continue.
Select an appropriate tag numbering method. You can choose between:
- Automatic: Chateau Mobile will assign tag numbers consisting of the dates and other elements. This is useful as a placeholder and indexing it for a later day to enter a real tag number.
- Series: This is great for bulk-adding consecutive tags.
- Manual: Allows for manually entering tag numbers, if the amount of work is manageable and the tag numbers are non-consecutive.
  - Note: Turn on SubTag Logic if you wish to add connectors, associate them with parent valves, and automatically advance their tag numbers behind the decimal point.

If you select Series, you will have to define the start and end tag numbers. We recommend using integers for valves. Tap Create Components when the starting and ending tag numbers are defined.
In the photo, identify the valves, mark them, and enter their details individually. The tag numbers will automatically advance from the first tag number.
After adding valves, add other components between them, such as connectors.
Tap Review to view or edit the newly-created components.
When ready, on the Review New Components screen, tap Save & Add New Photo to save the components in this photo, and then start adding another photo. Or you can tap Save and Inspect to finalize and begin performing initial inspections.
If you choose Save & Add New Photo, you can return and find a New Components tour, if you wish to perform initial inspections on them later.

Note: When the component type or size is changed in Chateau Mobile, the component will not get an updated inspection sample time until the change is checked in and approved.

If you wish to inspect the component with the correct sample time, please check in, ask the MOC to be approved (if you are not an approver), and then check out again.