Provisioning and Other
Tools (POT)
9 March 2010
Roger Gillman, Team ITSS
1
Title
04/02/09
OUTLINE
•
•
•
•
•
•
Why Provision?
Provisioning Data in powerLOG-J
Importing Data
Provisioning Utilities and Data Generation
Provisioning Review
Provisioning Product Reports
2
Title
04/02/09
Why Provision?
Bridging the gap from Initial
Fielding to Lifetime Sustainment
The process of provisioning is critical to assure initial
support for end items entering the DOD inventory.
• The primary objective of provisioning is to ensure that
minimum initial stocks of support items and associated
technical documentation are available at using units and
supporting organizations.
• The initial stocks are required to sustain the
programmed operation of systems and end items until
normal replenishment can be accomplished. Initial
stockage will be provided to support the stated system
availability or system readiness objectives (SRO).
•
3
Title
04/02/09
But Really, why Provision?
• Contract requirement (you’ve got to).
– Provisioning List(s)
• Documentation for supporting organization to
determine the Initial Spares “range and depth” using
demand based or sparing to availability models
– Parts Manual Lists
• Documentation for maintainers to identify, provide
authorization for, and order initial or replenishment
repair parts.
• Performance Based Logistics (you should)
– Use as basis for projecting program costs and
thresholds for negotiating PBL terms.
– Use for parts identification and use.
4
Title
04/02/09
Where is Provisioning Data?
5
Title
04/02/09
But Really, where is
Provisioning Data?
•
H Provisioning Data tables
–
–
–
–
–
–
–
–
–
–
–
–
–
**HA Part Identification – 31 elements - Start Work Area of CAGE/Refno View
HB Additional Reference Numbers – 0 elements (multiples of HA values)
HD UI Price – 1 element
HE UM Price – 1 element
HF Item Packaging Requirement – 1 element
**HG Part Application – 33 elements - Start Work Area of PLISN View
HH NHA/Kit Overhaul PLISN – 3 elements (with multiple values)
HI Provisioning Remarks – 1 element
HJ Reference Designation – 2 elements (with multiple values)
HK Parts Manual Documentation – 6 elements (with multiple values)
HL Parts Manual Nomenclature – 1 element (with multiple values)
HM Parts Manual Tools Basis of Issue – 1 element (with multiple values)
UOC – 1 element (with multiple values) by either:
• HN Serial No UOC (via XD)
• HO UOC (via XC)
– HP Design Change Information – 9 elements
– HQ Design Change Serial Number Effectivity - 1 element (with multiple values)
– HR Design Change UOC - 1 element (with multiple values)
6
Title
04/02/09
Here’s the Provisioning Data?
7
Title
04/02/09
Getting Started
Data Sources
• Type of program – sources of information are the
keys to how to add/update PTD.
– A Full Developmental Program may have Other
Functional Data available to use, e.g., Requirements,
RAM, Task Analysis and SSP data for testing. Data
may need to be integrated into an LSAR database.
– A COTS/NDI may have electronic data in commercial
formats that can be used/modified and imported.
– A Product Improvement/Modification may have original
PTD as GFI.
8
Title
04/02/09
Getting Started
Full Development Program
• Use hierarchical structure and LCNs of previous
development phases.
– Import/reuse powerLOG-J/GEIA/MIL-STD-1388-2B
files from previous development effort.
– Expand on LCN structure to add Reference Numbers,
and LCNs for piece parts.
• Engineering BOM in Spreadsheet formats
– Use BOM relationship to create LCN structure.
Drawing Parts lists to create the Reference Numbers
and CAGEs.
– Expand the data either in the spreadsheets or using
the powerLOG GUIs/MRE.
9
Title
04/02/09
Getting Started
COTS/NDI Program
• Use product information provided from
Supplier/OEM.
– Parts Ordering Lists
– User Manual
– Other electronic data that can be available to import,
e.g., OEM website about product.
• Data requirements should be tailored to take
advantage of the NDI’s existing commercial
support
10
Title
04/02/09
Getting Started
Product Improvement
• Use Original product data as baseline for
improvement changes.
– MIL-STD-1388-2B database
– LSAR-036/MIL-STD-1552 PMR data as Government
Furnished Information (GFI)
– Newer programs – powerLOG-J/GEIA data
11
Title
04/02/09
powerLOG Imports
• Comma Separated Variable (CSV)
• LSAR-036 A/B files
• 1552/PMR files
12
Title
04/02/09
Excel (CSV ms-dos) File Import
• With some alterations, Spreadsheet data can be imported
directly into powerLOG-J.
-1
0
1
REFNUMHA
A3325400
87T0148
CAGE
CAGECDXH
CAGE/NCAGE
STATUS CODE
(STAT)
REFERENCE
NUMBER
CATEGORY CODE
(RNCC)
REFERENCE
NUMBER
VARIATION CODE
(RNVC)
REFERENCE
NUMBER ACTION
ACTIVITY CODE
(RNAAC)
DOCUMENT
AVAILABILITY
CODE (DAC)
MAJOR
ACQUISITION
SOURCE OF SUPPLY
ORGANIZATIONAL
ADVICE CODE (AAC)
CODE (SOS)
ENTITY CODE (MOE)
NHA
INDCODHG
80063
19207
A
A
3
3
2
2
1
1
ZZ
ZZ
DA
DA
H
A
B16
AKZ
TM: 6DB
A3325400
A
3
2
1
ZZ
DA
Z
B16
A3325400
B
A3325432
A3325432
A3325432
A3325432
C
C
C
C
2
A3325432
80063
2.01
2.02
2.03
2.04
A3325442
205-0045
A3325431
A3325443
80063
0C8U3
80063
80063
A
3
2
1
ZZ
DA
D
B16
A
B
3
MK-3104/VRC
80058
M
5
2
3
ZZ
DA
B
B16
A3325400
B
4
5
6
7
8
9
AB-1386/U
013-1981-020
A3325433
A3325407
AS-3900A/VRC
MK-3094/VRC
80058
13499
80063
80063
80058
80063
M
A
5
3
2
2
4
D
ZZ
ZZ
DA
DA
B
D
B16
SMS
A
M
M
3
5
5
2
2
2
1
4
3
ZZ
CL
ZZ
DA
DA
DA
D
D
B
B16
B16
B16
A3325400
A3325400
A3325400
A3325400
A3325400
A3325400
B
B
B
B
B
B
10
MK-2955/V
80058
M
5
2
5
ZZ
DA
B
B16
11
A3325473
12
A3325450
12.01 27-AGM
12.02 A3325451
12.03 A3325452
12.04 A3325454
12.05 A3325459
12.06 A3325464
12.07 A3325465
12.08 M24243/1A402
12.09 MS21333-77
12.10 MS35207-265
12.11 MS27183-42
12.12 96278A411
12.13 MS35338-43
12.14 MS35690-505
12.15 MS27183-13
12.16 MS35338-45
12.17 A3325463-005
80063
80063
94598
80063
80063
80063
80063
80063
80063
81349
18076
80205
96906
3A054
80205
96906
96906
96906
80063
A
3
2
1
ZZ
DA
D
B16
M
M
J
M
A
J
M
M
M
2
5
3
2
3
3
5
2
5
2
9
2
2
2
2
9
2
9
E
4
E
4
E
E
4
4
4
KZ
KZ
ZZ
SE
ZZ
ZZ
9Z
KZ
KZ
DA
DA
DA
DA
DA
DA
D
D
D
D
Z
D
SMS
SMS
SMS
SMS
SMS
SMS
DA
DA
D
D
SMS
SMS
A3325400
B
A3325400
A3325400
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
A3325450
B
B
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
ITNAMEHA
NET CONTROL STATION
TRUCK,UTILITY
TOP ASSEMBLY,TRUCK
BODY,DETACHABLE
HARDTOP SHELL
AIR FILTER
BLOWER,EXHAUST
SEAL KIT, HARDTOP
INSTALLATION KIT,ELECTRONIC
EQUIPMENT
MAST
ANTENNA
DAGR ANTENNA MOUNT
BRACKET,MOUNTING
ANTENNA
INSTALLATION KIT,ELECTRONIC EQ.
INSTALLATION AND EQ. KIT,DATA
PROCESSING
MOUNT, PLATE ASSY, PWR SUPPLY
POWER SUPPLY ASSY
BATTERIES, TROJAN 12 VOLT
POWER SUPPLY BOX
BATTERY TRAY MOUNT
POWER SUPPLY BRACKET ASSY
PANEL,PROTECTION,ELECT SYSTEM
COVERS, LOUVER, ALTERED ITEM
DATA PLATE, PWR SUPPLY ASSY
RIVET,BLIND
CLAMP,LOOP
SCREW,MACHINE
WASHER,FLAT
NUT,PLAIN,ASSEMBLED WASHER
WASHER,LOCK
NUT,PLAIN,HEXAGON
WASHER,FLAT
WASHER,LOCK
CABLE ASSY,(W-100) PWR SUPPLY ASSY
13
Title
04/02/09
CSV File Import
Basic CSV (ms-dos) columnar data
MIL-STD-1388-2B “Short Names”
PLISNOHG LSACONXB
INDCODHG ITNAMEHA
REFNUMHA CAGECDXH REFNCCHA REFNVCHA ESSCODHG
SHLIFEHA UNITMSHA UMPRICHE UNITISHA UIPRICHD SMRCODHG
AAAA
A
A
RADAR, FLAT
AR
ABC-DEF
12345
3
2
1
0 EA
20000.15EA
20000.15 PEODD
AAAJ
AAAA
B
STAND, RADAR 123-ABC
13131
3
2
3
0 EA
355.1 EA
355.1 PAODD
AAAK
AAAAAA
C
ROTOR
ASSEMBLY
35425-112
12345
3
2
3
0 EA
255 EA
255 PAFHH
AAAL
AAAAAAAA D
GEAR, ROTOR 24525-234
32342
2
2
1
0 ST
123.99 ST
123.99 PAFZZ
AAAL
AAAAAAAA
24525-234
32342
AAAM
AAAAAAAB D
3
2
1
0 ST
120 ST
120 PAFZZ
AAAM
AAAAAAAB
AAAN
AAAAAB
C
AAAP
AAAB
B
GEAR, ROTOR 24525-234-1
32342
24525-234-1
32342
FLYWHEEL,
ROT
3253-842
12121
5
2
3
0 EA
65.25 EA
65.25 PA0ZZ
FIXTURE
42R545-2
12345
2
2
3
0 EA
400.56 EA
400.56 PEOZZ
14
Title
04/02/09
CSV File Import
Column data automatically maps to a table and data
element if a match to a data name/title is found as
the column name in the first row of csv data.
A Bold title below
Column name
Indicates data is
Mapped to a
powerLOG element
15
Title
04/02/09
CSV File Import
Field Values are used to create “constant” data
entries, e.g., EIAC, ALC, LCN-Type.
Enter values for
Data elements
here.
16
Title
04/02/09
CSV File Import
LCN Structure tab.
17
Title
04/02/09
CSV File Import
• LCNs can be created from a field value entry (One LCN
Only), imported data column, or hierarchical data
relationships.
• What Hierarchical data Works
– PLISN and NHA PLISN
– Reference Number and NHA Reference Number
– Unique Component to Unique Assembly Identifier
• What doesn’t work
– Indenture Codes (not uniquely identifying)
– BOM Part Index columns (multiple columns each representing
a different level)
– Any Row of data that is “orphaned” by no relationship built.
18
Title
04/02/09
CSV File Import
Table Data Import View.
Review the
depth of tables
data created.
Review attributes
to be imported.
Review LCNs
Generated.
19
Title
04/02/09
CSV File Import
Post Import Updates and Review
• Review record PLISN/LCN counts with csv
worksheet rows.
(Includes Header Row)
20
Title
04/02/09
CSV File Import
Post Import Updates and Review
(Cont)
• Create XC PCCN/UOC if necessary.
• Map LCNs to UOC (PCCN/UOC tab to UOC-HO work
area & check identical LCN map).
• Check numeric data with significant leading zeros, e.g.,
CAGE or NSN NIINs. Update this data if the leading
zeros did not import correctly.
• Assign PLISNs to database using LSAR-152 PLISN
Assignment/Reassignment if necessary.
21
Title
04/02/09
CSV File Import
CSV Template
• Applies to Columns, Field Chooser, and LCN creation
options.
• Makes it easy to re-import the same spreadsheet or
spreadsheet format.
22
Title
04/02/09
CSV File Import
Provisioning Data Import Mapping
HG
HG-F
HG
HA
HA-K
HA-K
PLISN
LCN
Prov IC
Item Name
Reference No
CAGE
TARGET
SOURCE
PLISNOHG
LSACONXB
INDCODHG
ITNAMEHA
REFNUMHA
CAGECDXH
HA
HA
HA
HA
HA-M*
HD-K
HA-M*
HE-K
RNCC
RNVC
EC
SL
UM
UM Price
UI
UI Price
REFNCCHA
REFNVCHA
ESSCODHG
SHLIFEHA
UNITMSHA
UMPRICHE
UNITISHA
UIPRICHD
HG
HA
HA
HA
HA
HA
HA
HA
SMR
DeMil
CTIC
PLT
HCI
PSPC
PMIC
ADPEC
SMRCODHG
DEMILIHA
CTICODHA
PRDLDTHA
HARDCIHG
PHYSECHA
PMICODHA
ADPEQPHA
HB-K
HB-K
HB
HB
HI
HH-K
HH
HH
Add Refno
Add CAGE
Add RNCC
Add RNVC
Remarks
NHA PLISN
NHA-IND
ORR
ADDREFHB
ADCAGEHB
ADRNCCHB
ADRNVCHB
REMARKHI
NHAPLIHH
NHAINDHH
OVHREPHH
M* Mandatory for entry of UM/UI Prices.
23
Title
04/02/09
CSV File Import
Provisioning Data Import Mapping (cont)
HG
HG
HG Maint Replace Rates-Mod
PPL List
Qty Assy
MRR-1
MRR-2
PPLPTDHG
QTYASYHG
MRRONEHG
MRRTWOHG
HA
HA
HA
MRR Mod
Spec Mat'l
PLCC-TTE
Spec Main
MRRMODHG
SPMACCHA
DDPLCCHA
SMAINCHA
HG Maintenance Task Distribution
MTD-O
MTD-F
MTD-H
MTD-L
MTD-D
MTD-CBD
MTD-CAD
OMTDOOHG
FMTDFFHG
HMTDHHHG
LMTDLLHG
DMTDDDHG
CBDMTDHG
CADMTDHG
RCT-O
RCT-F
RCT-H
RCT-L
RCT-D
RCT-Con
ORCTOOHG
FRCTFFHG
HRCTHHHG
LRCTLLHG
DRCTDDHG
CONRCTHG
HG Repair Cycle Time
HG Replacement Task Distribution
HG
RTD-O
RTD-F
RTD-H
RTD-L
RTD-D
LRU
ORTDOOHG
FRTDFFHG
HRTDHHHG
LRTDLLHG
DRTDDDHG
LRUNITHG
24
Title
04/02/09
CSV File Import
Provisioning Data Import Mapping (cont)
HK-F
HK-K*
HK-K*
HK-M
HK
HL
HJ-K
HJ
TMC
Figure No
Item No
TM-FGC
Qty-Fig
Prov Nomen
Ref Des
Ref Des C
TMCODEXI
FIGNUMHK
ITEMNOHK
TMFGCDHK
QTYFIGHK
PROVNOHL
REFDESHJ
RDCODEHJ
HQ
HP
Change Auth
HP-K
Intch Cd
HP
Serial From
HQ
Serial To
RS PLISN
RSP-Ind
HP
LCN Nomen
XB
LCN-IC
XB
CANUMBHP
INTCHCHP
FMSRNOHQ
TOSRNOHQ
RSPLISHP
RSPINDHP
LCNAMEXB
LCNINDXB
When using the MIL-STD-1388-2B “short names” to identify column data, all
map directly to the correct table except Figure Number and Item Number.
These must be changed from HJ Table (as migrating keys) to the HK (parent
table).
25
Title
04/02/09
Merging CSV data
into powerLOG
Use an Ad-Hoc Query to select the parent keys
for the csv data that you want to merge. (In
this example, it is Part Application Data (HG
Table) to enter RPSTL (HK table) data
Note that the Item Name is also Selected for Information only.
26
Title
04/02/09
Merging CSV data
into powerLOG
Highlight all the data and perform a “CTRL C”
Then open up excel, place the cursor in the
first cell and hit “CTRL V”
HG Table keys Query Results
Results pasted into Excel
27
Title
04/02/09
Merging CSV data
into powerLOG
Add a row for column headers and new columns for
HK table RPSTL data and as a minimum add the
new keys and mandatory data for the HK data
(Figure-Item Numbers and TM-FGC) for each row
28
Title
04/02/09
Merging CSV data
into powerLOG
Insert data by repeating the copying a row of
data, DO NOT ALTER THE HG TABLE KEYS,
and add the changed HK Data information
29
Title
04/02/09
Merging CSV data
into powerLOG
Convert the excel file to csv, then import.
30
Title
04/02/09
Merging CSV data
into powerLOG
Map Columns and add Field constants (EIAC-ALC-LCN type.)
31
Title
04/02/09
Merging CSV data
into powerLOG
Preview import data and Import.
When doing a
CSV import
don’t believe
this. ALWAYS
VERIFY
32
Title
04/02/09
Merging CSV data
into powerLOG
Use Multi-Record Editor to review results
33
Title
04/02/09
CSV File Import
Provisioning Specific Data Import
Lessons Learned
•
•
DO NOT create a column for UOC in the csv data. This will cause
each LCN created/imported to have an associated XC Model
Record. Instead create an XC model record after import or create
a model record through field Chooser for one specific model LCN.
Use the HO table to map the imported LCNs to the model record
after import.
If the data entered contains multiple values for the same PLISN,
e.g., Reference Designators, then a create and assign a specific
column for LCN in the csv file and use this column for LCN
Structure option at import. If the Target - Source logic is used
for LCN creation, multiple LCNs will be created for the multiple
data rather than grouping it under a single LCN/PLISN.
34
Title
04/02/09
CSV File Import
Pitfalls to a Successful csv import
(The Fine Print)
•
A CSV file may alter data in a way that changes the data value. Such
things as Data with leading significant zeros should be carefully reviewed
both in the CSV file and after import to assure the zeros are maintained.
•
Input Files may contain columns of constant data or the data may be
selected through the “Field Chooser” option. A common mistake is to select
critical element from the field chooser without also specifying the key
values for the data. An example of this is PCCN and UOC from the XC
table. If these are entered on the Field Chooser, without the associated
XC data keys, the PCCN and UOC entered will be created for every LCN
imported or generated.
•
Text fields may contain special control characters, e.g., the degree symbol,
tabs, or quotations, which may affect database operations. These may be
discovered using the TextPad or Notepad products and a Search command,
or may be discovered after import by using the Multi-Record Editor and
double clicking the Text fields. An indicator that data is corrupt are Java
Exception Messages when attempting to run reports after the data is
imported. A typical error will include the phrase “Invalid byte 1 of 1 byte
UTF8 sequence”.
•
The Input data may contain extra characters and/or two data elements may
be combined into one data column.
35
Title
04/02/09
CSV File Import
Pitfalls to a Successful csv import (cont)
•
Hidden or unseen characters in powerLOG keys can wreak havoc with file
structure logic, e.g., trailing spaces in a Left-Justified LCN. The spaces are
considered when viewing the LCNs Structure length, however the LCN cannot be
key changed. It must be deleted, then replaced with a correct key entry.
•
When entering a spreadsheet with rows of data from multiple tables, it is
normally defaulted to the parent table. If results are not what are expected,
then attempt to remap the key data to a different table, and preview the
results again, before committing the import.
•
Always back up your data files prior to importing data that is being merged with
existing powerLOG data, since it is very easy to create unintended data or data
relationships with the CSV importer. In the same vein, be sure to perform at
least a sample review of the data created in powerLOG after the import. A
typographical error in key data or hidden special characters may create
unintended consequences.
•
Multiple rows of data in the CSV file must be deleted related to a particular
LCN to be created if the LCNs creation is based on “source” and “target”
columns. Otherwise a situation, such as creating multiple LCNs with a duplicate
PLISN value similar to the view below may occur.
36
Title
04/02/09
PMR/1552 and
LSAR-036 Imports
PMR/1552 File
036 File
37
Title
04/02/09
PMR/1552 and
LSAR-036 Imports
1552 File
LSAR-036 File
• Also Imports PMR F
to M (less K) format
data
• Imports ICAPS basic
1552 A-E format
data
• Imports LMP/CCSS
LSAR-036 exports
• Imports ICAPS LSAR036-2A/2B formats
38
Title
04/02/09
PMR/1552 and
LSAR-036 Imports
PMR/1552 File
DARCOM-Form 1731 (A-E are 1552)
LSAR-036
Layout
39
Title
04/02/09
1552 and 036A/B
• Differences are not obvious to the untrained eye.
– 1552 -01A Reference Number is 16 positions (with an
overflow), for 036A/B it is 32.
– While the data fields are located in different cards/
positions from 1552 to 036A/B, there are only subtle
differences between 036A/B formats.
• LCN found in Remarks on 083L card. 036A/B LCN is
found on the 01H card (036A LCN is 11 characters
with 1 position ALC – 036B LCN is 18 characters with
2 position ALC).
• LSAR-036A/B MRR-Mod is 6 positions on 036A, and 7
positions on 036B. Data on remainder of 01C is
shifted right one position.
40
Title
04/02/09
PTD Files Import
• Things to check when something goes terribly wrong.
– Hiccups in the import file, e.g., a page break, space or blank
text line will cause the import to stop. A control or special
character will stop processing – Never edit the file in word –
use notepad instead.
• Use TextPad® or similar software with capabilty to view
spaces and special characters.
– Model or “A” Indenture PLISN Record(s) must be contained
in the data and at the beginning of the list. This record must
contain a UOC.
– If you Cannot keep the Original LCNs at import.
• Every PLISN 01H’s (036) or 83L’s (PMR) must have an
LCN
• Cross checking the data using software such as TextPad®
can be used to find and add missing LCNs.
41
Title
04/02/09
PTD Files Import
• When something goes terribly wrong (Continued).
– When all else fails, play “high-low” with the data file.
• Divide the PLISNs roughly in half and attempt to
import each half. If one side imports and one doesn’t
disgard the half that imported and divide the bad file
again.
• Although time consuming even a problem with a large
file can be isolated by the halving method.
42
Title
04/02/09
Importing LSAR-036 Change
Data
PowerLOG can import change only 036 data also
known as an LSAR-036 Wrap-around.
•
•
•
New LCNs in the changed file do not import.
Messages for PLISN A044:
INSERT on table 'HG' caused a violation of foreign key constraint
'R_XB_HG' for key (G09DEL,D03AC09AA0,00,P). The statement
has been rolled back.java.sql.SQL Integrity Constraint Violation
Exception: INSERT on table 'HG' caused a violation of foreign key
constraint 'R_XB_HG' for key (G09DEL,D03AC09AA0,00,P). The
statement has been rolled back.
New PLISNs with new or no LCN also do not import
Messages for PLISN A011A:
PLISN block is missing 01A or 01H cards Changes for PLISN
A011A for PCCN G09DEL cannot be processed because this item
is not in the database.
New PLISNs with same Reference Number/LCN keys
Overwrites the Old PLISN data. – (No log message)
43
Title
04/02/09
Provisioning Utilities and
Data Generation
•
•
•
•
PLISN Utilities
Pre-Made Database Alterations
LSAR-152 PLISN Assignment
LSAR-032
– Federal Item Cross Reference (FIXR) a.k.a. RDE xml file
– Type LSR transactions flat text file – one way (out) only
– RDE Provisioning RESPONSE xml import
• Calculations
– MRR-1 and MRR-2
– Quantity per End Item
44
Title
04/02/09
PLISN Utilities
To Clean up NHA
PLISN relationships,
assign provisioning
control data, and
calculate QPEI.
45
Title
04/02/09
Pre-Made Database Alterations
Provides standard updates to the database based on
the specified conditions.
46
Title
04/02/09
Pre-Made Database Alterations
• Example: Set blank MRR Modifier to 111111
47
Title
04/02/09
LSAR-152 PLISN Assignment
Reassignment
• Uses LCN logic/structure as basis
– Checks for breaks in top-down breakdown structure
Check these LCNs for
missing parent LCNs
48
Title
04/02/09
LSAR-152 PLISN Assignment
Reassignment
• Uses LCN logic/structure as basis
– If no break in structure for basic (ALC – OO breakdown),
groups items by matched ALCs
Updates database with:
PLISN
NHA PLISN
NHA PLINS Indicator
Indenture Code
Prior Item PLISN
Warning Only
ALCs different
Than 00 were
returned to
00 breakdown
Location.
Options for:
Model PLISN Reserve
PLISN Type
PLISN Gap
Insert/Overlay
49
Title
04/02/09
LSAR-032
Provisioning Screening
Two Paths in PowerLOG to submit screening requests
RDE xml
Standard LSR text
Choose
RDE and
segments
Choose
DLSC tape
(text) here
50
Title
04/02/09
LSAR-032 Export Files
RDE export xml
vs.
<?xml version="1.0" encoding="UTF-8"?>
<RDEProvisioningScreeningSubmittal
xmlns:r032="http://www.logsa.army.mil/alc/powerLOG-J/2003/report/lsar032">
<header>
<date>Dec 2, 2009</date>
<system_or_end_item_provisioning_contract_control_number>PCCN01</system_or_end_
item_provisioning_contract_control_number>
<type_screen_code>F</type_screen_code>
<output_segments>ABCEGHMW</output_segments>
</header>
<contents>
<item>
<ref_cage_data>
<reference_number>ABC-DEF</reference_number>
<cage_code>12345</cage_code>
</ref_cage_data>
<system_or_end_item_provisioning_contract_control_number>PCCN01</system_or_end_
item_provisioning_contract_control_number>
<plisn>AAAA</plisn>
</item>
<item>
<ref_cage_data>
<reference_number>123-ABC</reference_number>
<cage_code>13131</cage_code>
</ref_cage_data>
<system_or_end_item_provisioning_contract_control_number>PCCN01</system_or_end_
item_provisioning_contract_control_number>
<plisn>AAAJ</plisn>
</item>
File is in report folder, [PCCN].rde
“LSR” text
ONE WAY ONLY. LSR type screening
results do not Import automatically.
LSRZ013AR9335APCCN01AAAA 124X F9911C2 2 12345ABC-DEF
LSRZ013AR9335APCCN01AAAJ 124X F9911C2 2 13131123-ABC
LSRZ013AR9335APCCN01AAAK 124X F9911C2 2 1234535425-112
LSRZ013AR9335APCCN01AAAL 124X F9911C2 2 3234224525-234
LSRZ013AR9335APCCN01AAAM 124X F9911C2 2 3234224525-234-1
LSRZ013AR9335APCCN01AAAN 124X F9911C2 2 121213253-842
LSRZ013AR9335APCCN01AAAP 124X F9911C2 2 1234542R545-2
1
1
1
1
1
1
1
File is in report folder, LSAR-032.tap
51
Title
04/02/09
FIXR (RDE) Import
FIXR URL: http://www.dlis.dla.mil/FIXR/
For Portal online Registrations
LSAR-032 RDE xml
Provisioning Screening
Submittals posted
here.
RESPONSE
Screening results
Posted here.
52
Title
04/02/09
FIXR (RDE) Import
• File is returned as [PCCN]_RESPONSE.xml
• After choosing the powerLOG RDE IMPORT, the
following import summary screen and template appears:
Summary results
Select individual
Elements by
Segment
Select all Exact,
Partial Matches
Key change
Obsolete Reference
Numbers
Select de-select
All elements
53
Title
04/02/09
FIXR (RDE) Import
The second screen contains line by line selections
• If a screened Reference Number returns multiple NSN matches, then
the user must specify which NSN to select by reviewing ARNs and
Cataloging UI data, etc.
Selection
Required for
Multi-NSNs
returned
No-Match
Items
54
Title
04/02/09
FIXR (RDE) Import
If “Import Key Change of HA Reference Number and CAGE” option is
chosen, then the screen below appears when obsolete (RNCC/RNVC
values of 5/9) are returned. “To” parts are selected based on
RNCC/RNVC values of 2/2, 3/2, 5/2, then 7/2. If multiple items are
returned with the same higher precedence RNCC/RNVC values, then
the user must specify which CAGE-Reference Number to change.
Multiple Reference
Numbers with same
RNCC/RNVC precedence.
A Selection is required.
Reference Numbers
with only one higher
Precedence RNCC/
RNVC.
55
Title
04/02/09
FIXR (RDE) Import
A report is produced documenting the key field changes.
Original powerLOG
CAGE/
Reference Number
RNCC/RNVC
Always
5/9
New powerLOG
CAGE/
Reference Number
With RNCC/RNVC
Displayed.
56
Title
04/02/09
FIXR (RDE) Import
Forty-three Importable Data Elements
DATA ELEMENT
POWERLOG FIELD (DED)
DLIS TAG - DRN
1
National Item Identification Number (NIIN)
(Mandatory)
HA.NIINSNHA (253)
NCB_CD_4130
I_I_NBR_4131
2
NSN Federal Supply Class (Mandatory)
HA.FSCNSNHA (253)
FSG_3994
FSC_WI_FSG_3996
3
Item Name
HA.ITNAMEHA (182)
ITEM_NAME
4
Item Name Code
HA.INAMECHA (183)
PINC_3084
INC_4080
5
Demilitarization Code
HA.DEMILHA (076)
DEMIL_CD_0167
6
Criticality Code
HA.CRICODHA (066)
CRITL_CD_FIIG_3843
7
ADP Equipment Code
HA.ADEPEQPHA (027)
ADPEC_0801
8
Precious Metal Indicator Code
HA.PMICODHA (293)
PMIC_0802
9
Hazardous Code
HA.HAZCODHA (154)
HMIC_0865
10
Acquisition Method Code
HA.ACQMETHA (003)
AMC_2871
11
Acquisitiion Method Suffix Code
HA.AMSUFCHA (004)
AMSC_2876
12
Item Management Code
HA.ITMMGCHA (181)
IMC_2744
13
Additional Reference Number (ARN)
HB.ADDREFHB (006)
REF_NBR_3570
14
ARN CAGE
HB.ADCAGEHB (046)
CAGE_CD_9250
15
ARN RNCC
HB.ADRNCCHB (338)
RNCC_2910
16
ARN RNVC
HB.ADRNVCHB (339)
RNVC_4780
17
Unit of Issue
HA.UNITISHA (488)
UI_3050
18
Physical Security and Pilferage Code
HA.PHYSECHA (291)
CIIC_2863
19
Shelf Life
HA.SHLIFEHA (377)
SLC_2943
20
Unit of Issue Price
HD.UIPRICHD (490)
UNIT_PR_7075
21
Quantity per Unit Pack
HF.QTYUPKHF (321)
QUP_6106
22
Cushioning and Dunnage Material
HF.CUSHMAHF (067)
CUSH_DUN_MAT_5164
23
Intermediate Container Code
HF.INTCONHF (174)
INTMD_CTNR_CD_5167
57
Title
04/02/09
FIXR (RDE) Import
Importable Data Elements (continued)
24
25
DATA ELEMENT
Intermediate container Quantity
Packing Code
POWERLOG FIELD (DED)
HF.INCQTYHF (175)
HF.PKGCODHF (283)
DLIS TAG - DRN
INTMD_CTN_QTY_5152
LVL_A_PKG_CD_5170
LVL_B_PKG_CD_5171
MINM_PK_RQ_CD_5172
26
Method of Preservation
HF.MEPRESHF (239)
MTHD_PRSRV_CD_5160
27
28
29
30
31
Optional Procedure Indicator
Packaging Category Code
Preservation Material Code
Special Marking Code
Special Packaging Instruction Number
HF.OPTPRIHF (279)
HF.PACCATHF (282)
HF.PRSMATHF (295)
HF.SPEMRKHF (394)
HF.SPINUMHF (396)
OPTNL_PRO_IND_5173
PKG_CTGY_CD_5159
PRSRV_MAT_CD_5162
SP_MKG_CD_5169
SPI_NBR_5175
32
33
34
35
36
37
SPI Number Revision
Unit Container Code
Unit Container Level
Cushioning Thickness
Unit Pack Cube
Unit Pack Length (Length, Width, and Height)
HF.SPIREVHF (397)
HF.UNICONHF (486)
HF.UCLEVLHF (487)
HF.CUSTHIHF (068)
HF.UNPKCUHF (494)
HF.LENUPKHF, HF.WIDUPKHF,
HF.DEPUPKHF (494)
SPI_REV_5176
UNIT_CTNR_CD_5166
UNIT_CTNR_LVL_5168
THK_CUSH_DUN_5165
UP_CU_5155
UP_SZ_5154
38
39
40
41
Unit Pack Weight
Wrapping Material
Document Availability Code
Container NSN
HF.UNPKWTHF (495)
HF.WRAPMTHF (517)
HA.DOCAVCHA
HF.CONNSNHF
UP_WT_5153
WRAP_MAT_CD_5163
SEG C: DAC_2640
SEG W: CTNR_NSN_5178
42
Unit Weight
HA.UWEIGHHA (497)
SEG W: UNPKG_ITM_WT_5157
43
Unit Dimensions
HA.ULENGTHA, HA.UWIDTHHA,
HA.UHEIGHHA
SEG W: UNPKG_ITM_DIM_5158
58
Title
04/02/09
Data Calculations
Compute MRR-1/2 Based on Task Frequency
59
Title
04/02/09
Data Calculations
Maintenance Replacement Rate
Formula
PLEASE NOTE:
The Formula will not
work without CA and CI table
Task Data.
N
MRRI = Σ TFi * QTY per TASKi
i-1
Where:
N = number of H function tasks (for assembly) or
J function Tasks (for repair parts) for a given
LCN/ALC (assembly) or items indentured lower
LCNs/ALCs (repair parts).
TFi = Task Frequency (DED 430)
QTY-TSK = Quantity per Task (DED 319)
MRRII = MRRI * MRR Ratio
Where:
MRRI (DED 211)
MRR Ratio = Utility Selection.
60
Title
04/02/09
Data Calculations
• Compute Quantity per End Item – Two approaches
– Utility- PLISN
– LSAR-036 option (cannot narrow PLISN selection)
• Three options available
61
Title
04/02/09
Data Calculations
Option 1 Calculation (most common)
N
M
QPEI = Σ [ Σ QPAj ] i
i=1
j=1
Where:
N = Number of applications for unique part
M = Number of indenture levels
i = Application of unique part
j = Indenture level of application
Basic Rule: Multiply QPA’s up and add across.
62
Title
04/02/09
Data Calculations
Option 1 QPEI Example
For each application
Of a CAGE/Reference
Number
Multiply Up
Quantity per
Assembly
Then Add across
Each application
63
Title
04/02/09
Provisioning Review
Drill Down
•
•
•
•
•
•
•
PLISN view/PLISN Tree Error Report
LSAR-126 LCN/PCCN Tree
LSAR-080 Bill of Materials
LSAR-068 Task Code/SMR Comparisons
Multi-Record Editor Templates – Data depth
PowerLOG Edits (LMP) – LSAR Business Rules
Provisioning Edits – Data and Interrelationships
64
Title
04/02/09
Provisioning Review
PLISN view/PLISN Tree Error Report
65
Title
04/02/09
Provisioning Review
LSAR-126 LCN/PCCN Tree
66
Title
04/02/09
Provisioning Review
LSAR-080 Bill of Materials
Review UOCs
mapped to
Assembly and
Components
here
67
Title
04/02/09
Provisioning Review
LSAR-080 Bill of Materials
Error List
Error Code 1. If an item is SMR coded, with "Z" or "B" in the fourth position, but parts are
contained below this item with source codes other than K- or XA, then this error is output
(appears on Part I with asterisks by both the assembly/part location).
Error Code 2. An item does not have an identifiable NHA, e.g., if the Indenture structure lists
the item as an "F" and the logical NHA by file sort is a "D", this error is output (Part II
only).
Error Code 3. No IC. This item appears on Part II only, when the selection is made by PCCN.
If the selection is by LCN, the item is shown on both Parts I and II.
Error Code 4. This is an item whose SMR code is blank or incomplete (without 3rd/4th
positions).
Error Code 5. SMR recoverability (5th position) codes invalid based on the repair code (4th)
Error Code 6. An assembly is SMR-coded repairable (e.g., SMR-4 is not Z or B), but has no
parts breakout beneath it.
Error Code 7. A warning that the item is identified as part of a kit, by NHA Indicator of
Asterisk.
68
Title
04/02/09
Provisioning Review
LSAR-068 Task Code to SMR Verification
CI Table work area
Compare Task
And SMR codes
Third position.
69
Title
04/02/09
Provisioning Review
Multi-Record Editor Templates
70
Title
04/02/09
Provisioning Review
Multi-Record Editor Templates Continued
71
Title
04/02/09
Provisioning Review
Multi-Record Editor Templates
• For data entry, can be set to match the
requirements of the Contract/Program.
– Specific data required by contract, e.g., PLT, SMR, etc.
– Specific fields required by program, e.g., only MTDRTD-RCT for O/M levels O, F, D.
• For data review, can be set to match the
requirements of the Contract.
– To perform a quick check of data depth and obvious
irregularities.
72
Title
04/02/09
Provisioning Review
PLISN Detailed Data check
Combined H Table Work Area
All H tables
available
Scroll bar rather
Than tab for
HA-HG tables
73
Title
04/02/09
Provisioning Review
LMP Edits
• Range from basic data checks – is the data present
to cross-data integrity – MTD-RTD-RCT subfields
and SMR.
• Found under the PowerLOG (business rules) edits
and the provisioning edits (both with LMP buttons)
– 15 PowerLOG LMP edits
– 54 Provisioning LMP Edits (combined edits used by
TACOM and CECOM)
• Program-specific edits can be saved and reloaded
into powerLOG.
74
Title
04/02/09
Provisioning Review
PowerLOG Edits (LMP)
75
Title
04/02/09
Provisioning Review
Provisioning Edits (LMP)
76
Title
04/02/09
Provisioning Product Reports
• LSAR-036 PTD
– html and text versions
– Full File and Change Only data
• LSAR-151 Provisioning Parts List Index (PPLI)
– One line per PLISN List accompanying the LSAR-036
delivery
77
Title
04/02/09
LSAR-036 Format
78
Title
04/02/09
LSAR-036
Report Selection and Statistics
Options Available
PCCN (required)
UOCs (Required)
PTD List (Required)
List, Test, Live Run
PLISN Ranges
Change Authority
Overhaul PLISN
TM-Code/WUC Display
Report Data Header display
Full Effectivity UOC (USMC)
L Cards Merge (USAF)
Quantity per End Item
Same As PLISNs
Data Fields Filter Out
79
Title
04/02/09
LSAR-036
Report Data with card/position locator
80
Title
04/02/09
LSAR-036
Report Data with Data Header Option
81
Title
04/02/09
LSAR-036 Format
Deliverable Text File data
[PCCN].036
82
Title
04/02/09
LSAR-036 Format
Delivered Provisioning Data
• LSAR-036 “Live Run” Option
• PTD Baseline generated.
• Text file created.
Also Recommend: Perform PowerLOG-J
database Backup; or export powerLOG,
and PTD Baseline. Keep these and the
LSAR-036 text, database exports
and/or backup file archived/stored.
83
Title
04/02/09
Key and Associated Data
For Initial and Change Only
(Or How to make standard fixed flat file behave “relationally”)
KEY DATA
CAGE
H TABLE
036 CARD/ BLOCK
HB
A02/5
A02/6
C/29
Additional Reference Number
NHA PLISN
HH
ASSOCIATED DATA
H TABLE
036 CARD/ BLOCK
RNCC
HB
A02/7
RNVC
HB
A02/8
NHA Indicator
HH
C/30
ORR
HH
C/31
UOC
XC
D/43
None
Reference Designation
HJ
D/44
RDOC (Generated)
N/A
D/45
RDC
HJ
D/46
Serial Number Effectivity
HQ
F/68
Prorated ELIN
HP
G/75
Prorated Quantity
HP
G/76
Interchangability Code
HP
F/67
Replaced Superseding PLISN
HP
F/70
R/S PLISN Indicator
HP
F/71
DCN-UOC
HR
F/74
Total Item Changes
HP
F/69
Quantity Shipped
HP
F/72
Quantity Procured
HP
F/73
Change Authority No
HP
F-G/66
Serial Number Effectivity
HQ
F/68
None
DCN-UOC
HR
F/74
None
TM Code
HK
J/80
Basis of Issue (BOI)
HM
Figure Number
HK
J/81
TM Chg Number
HK
Item Number
HK
J/82
TM Indenture Code
HK
TM-Functional Group Code
HK
J/86
Quantity Per Figure
HK
TM Code
HK
K/80
Provisioning Nomenclature
HL
K/91
Figure Number
HK
K/81
Item Number
HK
K/82
BOI-CTRL
HM
J/87
BOI QTY-AUTH
HM
J/87
BOI-EI
HM
J/87
BOI-LVL
HM
J/87
84
Title
04/02/09
LSAR-036 Change Transactions
Provisioning Baseline File
85
Title
04/02/09
LSAR-036 Change Transactions
Change Only Transaction Rules
(Or Don’t attempt to do this on your own)
a. Several data elements are combined/updated as one field. These are the
Reference Number and CAGE on the 01A card, and all CSN for Remarks,
b. Remarks; Provisioning Nomenclature within its TM Code, Figure and Item Number
keys; and Material. Since an update to Remarks, Provisioning Nomenclature, or
Material may change field length, all of the original data is deleted using data element
deletes (or "G" TOCC) in either the standard or key data delete format, respectively,
prior to updating these elements. This means that the entire narrative, i.e., "01H",
"02H" and "03H", will be deleted prior to adding in the new narrative.
c. The CSN will always begin with CSN "01" for any CFI update transaction. An
exception is the CFI "A" update of an Additional Reference Number which will begin
with CSN "02". If there are multiple data updates of a PLISN CFI, the CSN will be
incremented by one for each multiple update required. The TOCC type within a set of
CFI is also used to determine the CSN. Delete transactions (TOCC "G") are grouped for
determination of the CSN for a PLISN CFI. If a CFI update includes both delete/change
transactions, the CSN will be re-sequenced back to "01" when the transactions
transition from the delete to the change types.
d. Deletion transactions will always appear before change transactions within a given
CFI. A new PLISN can only have a blank TOCC, which will include an incremented CSN
for multiple CFI data.
86
Title
04/02/09
LSAR-036 Change Transactions
Change Only Transaction Rules (Cont)
e. There are no "reserved" Additional Reference Numbers (ARN) (e.g., the "02A" may
have been reserved for drawing numbers in previous provisioning systems). It is
necessary to control ARN, e.g., drawing number, by using the Reference Number
Category Code (RNCC). RNCC "D" indicates a drawing reference number and RNCC
"C", or "7" depicts non-definitive Military Specifications or Standards. The ARN will
be displayed on CSN based upon a sort in ascending CAGE and ARN (first 29
positions).
f. DCN-UOC and Serial Number Effectivity are depicted as subordinate keys, and as
such, multiple entries against a single Change Authority Number are permitted. The
same is true of BOI-CTRL within a TM Code Figure-Item Number combination key, or
Figure-Item Number within a TM Code key.
g. Multiple, independent key data deletes/updates contained on the same CFI, e.g.,
UOC and Reference Designation are consolidated on one card record under the
appropriate TOCC.
h. Identical key data within a PLISN record will be merged and processed as a single
update transaction. Care should be exercised to ensure this condition does not exist
in the file.
87
Title
04/02/09
LSAR-036 Change Transactions
Change Only Transaction Rules (Cont)
i. If multiple, subordinate key data are contained within another key, e.g., Basis of Issue
Control within a TM Code-Figure Number Item Number combination key and DCN-UOC
within a Change Authority key, the non-multiple associated data, i.e., TM Indenture or Total
Item Changes, only appear on the first CSN containing the basic key.
j. If an entire PLISN record is deleted from the PBF, a one-line record in the image of the
PLISN deletion transaction will remain on the PBF. If that exact, deleted PLISN is
reinstated/reestablished in the data tables, it must match the CAGE and Reference Number
that were contained on the record when it was originally deleted.
k. If both Prorated ELIN and Prorated Quantity are null, do not output "G" card.
l. Work Unit Code (WUC) and TM Functional Group Code are contained in different tables
and, therefore, may exist concurrently. If both codes exist, the TM information should
show on the "01J" and consecutive "J" cards and the WUC should show on the last "J" card
by itself. Note: There are no key data elements required for processing on a "J" card that
contains a WUC.
m. The subfields for Replacement Task Distribution (RTD), Maintenance Task Distribution
(MTD), and Repair Cycle Time (RCT) representing values for the Operations/Maintenance
Levels are processed independently. If an Organizational (O) level RTD value is moved from
O level to Maintainer/Direct Support (F) level, then two transactions are generated, a TOCC
G with a G in RTD-O, and a TOCC M with the value in RTD-F.
88
Title
04/02/09
LSAR-036 Change Transactions
Report Data Image
Text File
89
Title
04/02/09
LSAR-151 PPL Index
PLISN and Reference Numbers index
90
Title
04/02/09
Provisioning and CSV data
Guides are available from LOGSA
91
Title
04/02/09
92
Title
04/02/09
BACKUPS
93
Title
04/02/09
LMP Edits
Standard Edits used
LMP Edits used by TACOM and CECOM
CECOM
TACOM
LMP Default
CECOM
010
010
010
339
020
020
020
350
350
350
030
030
030
360
360
360
040
040
040
380
050
390
060A
410
070
070
420
085
085
430
120
120
440
130
130
460
140
140
500
150
510
510
510
160
520
520
520
170
170
525
190
190
050
060A
120
140
060A
150
160
160
TACOM
LMP Default
339
380
390
390
410
420
420
430
440
460
460
500
525
530
530
210
210
210
540
540
540
230
230
230
550
550
550
240
240
560
250
251
560
250
580
580
251
590
590
260
260
600
600
270
270
660
660
660
670
670
670
720
280
280
310
310
720
720
320
780
780
780
325
325
790
790
790
326
326
820
820
820
820
320
94
Title
04/02/09
Open Provisioning
powerLOG System Changes
Change No.
PLJ-851
PLJ-891
PLJ-997
PLJ-998
PLJ-1000
PLJ-1002
PLJ-1007
PLJ-1017
PLJ-1021
PLJ-1031
PLJ-1032
PLJ-1036
PLJ-1041
PLJ-1062
PLJ-1072
PLJ-1073
PLJ-1074
PLJ-1077
PLJ-1079
PLJ-1085
PLJ-1087
PLJ-1091
PLJ-1092
PLJ-1093
CHANGE TITLE
LSAR-036 Selection Output Field Filter Tab
LSAR-036 J card deleted completely bug.
LSAR-032 record count incorrect
Provisiononing Edit 560 - Change Overhaul Quantity to Overhaul Replacement Rate
LSAR-080 Report Selection by LCN-UOC Issues Involving Sequential LCNs
QPEI Calculation Java Error - exceeds 5 characters
LSAR-080 Report run by PLISN, then LCN retains first selection PLISN PCCN as Selection Criteria
CSV File Meta data - Name mapping of originating HK keys versus HJ migrating non-mandatory Key
LSAR-080 Report False Type 5 Maintenance-Recoverability Combinations Error
Multi-Record Editor - Key Change of LCNs from P to F
LSAR-030 Bulk Item Null Pointer Exception
Utilities/Edit/Provisioning/525 Has no Description link
Multi-Record Edit - HA Table - Production LeadTime delete (PRDLDTHA)
LSAR-036 Change Transaction - Multiple added J and K cards, 2nd K not recognized
HA Reference Number with Trailing space and subordinate Child Tables without it
Null pointer on 170 Edit
NHA PLISN Header on LSAR-036 report
LSAR-036 Reference Designation Import
New or Modified Utility for resorting Item Numbers for Figure Numbers Identified as "BULK"
HA Shelf Life Code
Typo in LSAR-155
In PowerLOG Provisioning Edits, text same for Edits 520 and 525. Edit 525 reads edit number 520.
LSAR-032 RDE portal XML generation option missing PLISNs
HY Table Java exception
95
Title
04/02/09