POSM Crossbore Elimination

Several changes were made to POSM to meet the specification for the cross bore template. We have added a function to allow nonstandard DVD file and folder layouts letting the files be up to 250 characters instead of 64. We have also updated the POSM Lateral Launcher application so that it can start Lateral Inspections for a POSM in another folder. Because the file naming scheme for mainline and laterals is different we decided to have a Mainline POSM and Lateral POSM folder.
The overall procedure for inspection will be as follows.
Perform a mainline inspection using the Mainline POSM filling out all the forms of the PACP including the Cross bore 1 and Cross bore 2 tabs. Each tap to an address will be noted in the mainline inspection.
When the mainline inspection is complete, the user will exit POSM. The Lateral Launcher application will be used to start an inspection for each tap (lateral) in the mainline inspection. It will start these inspections the Lateral POSM folder. The Unique ID from the mainline inspection is stored in the header of the lateral inspection. The Unique ID of the Lateral Inspection is stored for the Mainline Inspection’s Data point (Tap). This way the inspections can be cross referenced back to one another when imported into a larger database.
When all inspections are complete they may be exported to a removable hard drive to send to the client.
Setup of POSM for Crossbore Inspection.

There will be two folders: Lateral POSM and Mainline POSM. There will also be three shortcuts. Lateral Launcher, Lateral POSM and Mainline POSM. The short cuts are generally placed in the Public\Desktop folder so all users of the computer will have access to POSM.
The mainline file / folder setup is as follows:

This setup produces a file that includes the Project Name _ Contactor Name _ Street Name of Sewer _ Upstream Cross Street _ Downstream Cross Street _ City _ YYYYMMDD (date). Mp4
If there are two sewers inspected on the same day on the same street POSM will auto generate a four digit random number to the extra lines.
The Lateral File setup is as follows.

This produces a file that will generate: Project Name _ Contractor Name _ Street Number _ Street Name
_ City _ Segment ID (with Branch ID and Lateral Number) _ YYYYMMDD .mp4
Also for laterals POSM has an Auto ID Generator setup of:

This will produce a lateral ID of:
Project Name _ Contractor Name _ Street Number _ Street Name _ City _ Segment ID (with Branch ID
and Lateral Number) into the Lateral Segment Reference field.
Some additions to the lateral launcher have been made to start inspections into another folder. This allows the mainline inspection taps to be used to start the lateral inspections.

The lateral launcher is started from the mainline POSM folder. The Start LACP in another Folder checkbox is check and the path the Lateral POSM is set with Set LACP Path.
The user will select the most recent PACP session on top (they will be listed in reverse order). The user then select the tap distance that they are located currently. Once selected, the user will press Start LACP Session which will launch POSM from the Lateral POSM folder and start a new LACP session with the header data from the PACP data.
The Unique ID of the POSM session is then added to the LACP session. The LACP Unique ID is added to the LinkedInspection table of the Mainline POSM folder. Because there can be more than one Lateral inspection on a Tap Data ID from the mainline inspection we choose to put this in its own table so multiple inspections can be linked back to one DataID.

By using the lateral launcher almost all of the fields for the LACP inspection are pre-filled. The unique ID of each session is now linked as well. Using the Generate ID button the Lateral Segment Reference is generated for this segment as well.