| 1 | English French  Notes   Complete/Exclude
 | 
|---|
| 2 | Multiple fields can occur many times within one EQUIPMENT CATEGORY                      
 | 
|---|
| 3 | (#6911) file record.  All occurrences of these fields are examined.                     
 | 
|---|
| 4 | The index number of the multiple with invalid data is displayed on                      
 | 
|---|
| 5 | this report.                    
 | 
|---|
| 6 | If any lookup field on this report is left with invalid data, it                        
 | 
|---|
| 7 | will be converted as empty into CoreFLS.                        
 | 
|---|
| 8 | CoreFLS Data Cleansing Report Instructions                      
 | 
|---|
| 9 | in the CoreFLS system. If fields appearing on this report are left empty, the                   
 | 
|---|
| 10 | This report examines the following non-required fields:                 
 | 
|---|
| 11 |    TECHNICIAN (RESPONSIBLE SHOP Multiple) (#6911.01,1)                  
 | 
|---|
| 12 |    FREQUENCY (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,.01)                       
 | 
|---|
| 13 |    PROCEDURE (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,4)                 
 | 
|---|
| 14 |      file that fall between the beginning and ending names entered                      
 | 
|---|
| 15 | The report lists records in alphabetical order by Equipment Category name.                      
 | 
|---|
| 16 | FIELD NAME - name of the non-required field                     
 | 
|---|
| 17 |      (Note: Frequency and Procedure fields may display a set of two multiple                    
 | 
|---|
| 18 |      numbers separated by a comma. The first number represents the Responsible                  
 | 
|---|
| 19 |      Shop multiple number. The second number represents the Frequency multiple                  
 | 
|---|
| 20 |      number. If the second multiple number (Frequency multiple number) for                      
 | 
|---|
| 21 |      these two fields is missing, there are no occurrences of the field's                       
 | 
|---|
| 22 |      Frequency or Procedure for the Responsible Shop. There must be a                   
 | 
|---|
| 23 |      Frequency and Procedure for each Responsible Shop in order for a PM to                     
 | 
|---|
| 24 |      be generated for the Equipment Category.)                  
 | 
|---|
| 25 | ** Special Note *************************************************                       
 | 
|---|
| 26 | The index number of the multiple with missing data is displayed on                      
 | 
|---|
| 27 | If these non-required fields remain empty, the following will                   
 | 
|---|
| 28 | occur during CoreFLS conversion:                        
 | 
|---|
| 29 | TECHNICIAN (#6911.01,1) - will be converted into CoreFLS as empty                       
 | 
|---|
| 30 | FREQUENCY (#6911.13,.01) - a PM will not be created for the                     
 | 
|---|
| 31 |                             Equipment Category                  
 | 
|---|
| 32 | PROCEDURE (#6911.13,4) - the PM description will be defaulted to                        
 | 
|---|
| 33 |                           the FREQUENCY (#6911.13,.01) followed by                      
 | 
|---|
| 34 |                           a hyphen (dash) and Equipment Category                        
 | 
|---|
| 35 | EQUIPMENT CATEGORY (#6911) file that have invalid or missing (empty) values in                  
 | 
|---|
| 36 | the fields that are being converted into the CoreFLS system.  The report                        
 | 
|---|
| 37 | examines five fields to determine if there is a valid value in each.  If there                  
 | 
|---|
| 38 | is no value in the field, it is considered to be empty. If there is a value in                  
 | 
|---|
| 39 | a lookup-type (a.k.a. pointer) field, the report examines the value to ensure                   
 | 
|---|
| 40 | that it is valid.                       
 | 
|---|
| 41 |      FREQUENCY (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6911.13,.01)                     
 | 
|---|
| 42 | This report lists the overall count of the number of problem records and                        
 | 
|---|
| 43 | fields detected.                        
 | 
|---|
| 44 |      have at least one empty required field                     
 | 
|---|
| 45 |      have invalid data in any of the lookup fields                      
 | 
|---|
| 46 |      that have nothing in at least one non-required field                       
 | 
|---|
| 47 |      INV: invalid data                  
 | 
|---|
| 48 | FIELD NAME - name of the field from the EQUIPMENT CATEGORY (#6911) file                 
 | 
|---|
| 49 | LOOKUP FIELDS W/ INVALID DATA - count of the number of lookup fields that                       
 | 
|---|
| 50 |      contain an invalid value  (                        
 | 
|---|
| 51 |  appears in this column if the field is                 
 | 
|---|
| 52 |      not a lookup field.)                       
 | 
|---|
| 53 | displayed on the detail reports.                        
 | 
|---|
| 54 | Equipment Inventory compile in progress. Please try again later.                        
 | 
|---|
| 55 | Last Equipment Inventory compile done on                        
 | 
|---|
| 56 | *** Warning: Please compile the list of Equipment Inventory first ***                   
 | 
|---|
| 57 | This report is sorted by station. You may select a single station number or ALL.                        
 | 
|---|
| 58 | Please select a station (1-                     
 | 
|---|
| 59 |  The list below contains the stations that have been found in the                       
 | 
|---|
| 60 |  STATION (#60) field in the EQUIPMENT INV. (#6914) file.                        
 | 
|---|
| 61 | ZZ no station                   
 | 
|---|
| 62 |  to display the records with no entry in the                    
 | 
|---|
| 63 | CoreFLS Data Cleansing Report (File# 6914 - EQUIPMENT INV.)                     
 | 
|---|
| 64 | Do you wish to queue the Equipment Inventory compile?                   
 | 
|---|
| 65 | Enter 'YES' to queue the Equipment Inventory compile or '^' to abort the compile.                       
 | 
|---|
| 66 | <Equipment Inventory Compile Aborted>                   
 | 
|---|
| 67 | CoreFLS Data Cleansing Reports Equipment Inventory List                 
 | 
|---|
| 68 | Compile's TaskMan ID is                         
 | 
|---|
| 69 | Compiling Equipment Inventory list ...                  
 | 
|---|
| 70 | *** Aborted: another Equipment Inventory compile is currently running ***                       
 | 
|---|
| 71 | CoreFLS Equipment Inventory List by Field                       
 | 
|---|
| 72 | CoreFLS Equipment Inventory List by Record                      
 | 
|---|
| 73 | the CoreFLS system. If fields appearing on this report are left empty, the                      
 | 
|---|
| 74 | Before you use this report, you may want to run the compile to ensure you                       
 | 
|---|
| 75 | are viewing the most recent modifications.                      
 | 
|---|
| 76 | next to the field number                        
 | 
|---|
| 77 |    TOTAL ASSET VALUE (#12) -                    
 | 
|---|
| 78 | Total Asset Val                 
 | 
|---|
| 79 |    USE STATUS (#20)                     
 | 
|---|
| 80 |    STARTING MONTH (RESPONSIBLE SHOP Multiple) (#6914.04,2)                      
 | 
|---|
| 81 |    CRITICALITY (RESPONSIBLE SHOP Multiple) (#6914.04,2.7)                       
 | 
|---|
| 82 |    LEVEL (RESPONSIBLE SHOP/FREQUENCY Multiple) (#6914.43,3)                     
 | 
|---|
| 83 |    STANDARD GENERAL LEDGER (#38) -                      
 | 
|---|
| 84 |    STATION NUMBER (#60) -                       
 | 
|---|
| 85 |    BUDGET OBJECT CODE (#61) -                   
 | 
|---|
| 86 | Admin Office                    
 | 
|---|
| 87 | The report is sorted by station number.  When printing or viewing this                  
 | 
|---|
| 88 | report, you may select a single station number or ALL. Select                   
 | 
|---|
| 89 | to display the records with no entry in the STATION (#60) field.                        
 | 
|---|
| 90 | The totals for each station are as follows:                     
 | 
|---|
| 91 |       file assigned to the station                      
 | 
|---|
| 92 |       that have one or more empty non-required fields                   
 | 
|---|
| 93 |       fields that are empty                     
 | 
|---|
| 94 | REC IEN - lists the EQUIPMENT INV. (#6914) file internal record number                  
 | 
|---|
| 95 | MFGR. EQUIPMENT NAME - name of the equipment (if there is a value in this                       
 | 
|---|
| 96 |      field, you may use it to select the Equipment Inventory item)                      
 | 
|---|
| 97 |      (Note: Frequency, Level, and Procedure fields may display a set of two                     
 | 
|---|
| 98 |      multiple numbers separated by a comma. The first number represents the                     
 | 
|---|
| 99 |      Responsible Shop multiple number. The second number represents the                 
 | 
|---|
| 100 |      Frequency multiple number.)                        
 | 
|---|
| 101 | *** Special Note ************************************************                       
 | 
|---|
| 102 |    STARTING MONTH (#6914.04,2)                  
 | 
|---|
| 103 | (#6914) file record. All occurrences of these fields are examined.                      
 | 
|---|
| 104 | on this report.                 
 | 
|---|
| 105 | If the non-required fields are left empty, the following will occur                     
 | 
|---|
| 106 | during CoreFLS conversion:                      
 | 
|---|
| 107 |   FREQUENCY (#6914.43,.01) - a PM will not be created for the                   
 | 
|---|
| 108 |                              equipment item                     
 | 
|---|
| 109 |   PROCEDURE (#6914.43,4) - the PM description will be defaulted to                      
 | 
|---|
| 110 |                            the FREQUENCY (#6914.43,.01) followed by                     
 | 
|---|
| 111 |                            a hyphen (dash) and Equipment Category                       
 | 
|---|
| 112 | All other non-required fields will be converted as empty.                       
 | 
|---|
| 113 | EQUIPMENT INV. (#6914) -                        
 | 
|---|
| 114 | Totals for Station                      
 | 
|---|
| 115 | with Required Fields Missing Data                       
 | 
|---|
| 116 | with Lookup Fields w/ Invalid Data                      
 | 
|---|
| 117 | with Non-Required Fields Missing Data                   
 | 
|---|
| 118 | Total records                   
 | 
|---|
| 119 | Total fields                    
 | 
|---|
| 120 | Level                   
 | 
|---|
| 121 | Work Performed                  
 | 
|---|
| 122 | Resp Shop                       
 | 
|---|
| 123 | Criticality                     
 | 
|---|
| 124 | Starting Month                  
 | 
|---|
| 125 | MFGR. EQUIPMENT                 
 | 
|---|
| 126 | W/INVALID DATA                  
 | 
|---|
| 127 | EQUIPMENT INV. (#6914) file that have invalid or missing (empty) values in                      
 | 
|---|
| 128 | examines 30 fields to determine if there is a valid value in each. If there                     
 | 
|---|
| 129 | viewing the most recent modifications.                  
 | 
|---|
| 130 |    ENTRY NUMBER (#.01)                  
 | 
|---|
| 131 |    PARENT SYSTEM (#2)                   
 | 
|---|
| 132 |    MFGR. EQUIPMENT NAME (#3) -                  
 | 
|---|
| 133 | Mfgr Equip Name                 
 | 
|---|
| 134 |    EQUIPMENT CATEGORY (#6) -                    
 | 
|---|
| 135 | Equip Category                  
 | 
|---|
| 136 |    TYPE OF ENTRY (#7)                   
 | 
|---|
| 137 |    VENDOR POINTER (#10) -                       
 | 
|---|
| 138 | Vendor                  
 | 
|---|
| 139 |    ACQUISITION SOURCE (#13.5) -                         
 | 
|---|
| 140 | Acq Source                      
 | 
|---|
| 141 |    CATEGORY STOCK NUMBER (#18) -                        
 | 
|---|
| 142 | Cat Stock Number                        
 | 
|---|
| 143 |    SERVICE POINTER (#21) -                      
 | 
|---|
| 144 | Service Ptr                     
 | 
|---|
| 145 |    RESPONSIBLE SHOP (Multiple) (#6914.04,.01) -                         
 | 
|---|
| 146 |    INVESTMENT CATEGORY (#34) -                  
 | 
|---|
| 147 | Investment Cat                  
 | 
|---|
| 148 |    WORK PERFORMED (EQUIPMENT HISTORY Multiple) (#6914.02,9)                     
 | 
|---|
| 149 | The report is sorted by station number. When printing or viewing this report,                   
 | 
|---|
| 150 | you may select a single station number or ALL. Select                   
 | 
|---|
| 151 | display the records with no entry in the STATION (#60) field. The report lists                  
 | 
|---|
| 152 | the overall count of the number of problem records and fields detected.                 
 | 
|---|
| 153 |      file assigned to the station                       
 | 
|---|
| 154 |      that have invalid data in any of the lookup fields                 
 | 
|---|
| 155 |  appears in this column if the field                    
 | 
|---|
| 156 |      is not a lookup field.)                    
 | 
|---|
| 157 |      non-required fields (                      
 | 
|---|
| 158 |  appears in this column if non-required                 
 | 
|---|
| 159 |      does not apply to this field.)                     
 | 
|---|
| 160 |    RESPONSIBLE SHOP (#6914.04,.01)                      
 | 
|---|
| 161 |    WORK PERFORMED (#6914.02,9)                  
 | 
|---|
| 162 | system.  CoreFLS is unable to function when a required field is empty;                  
 | 
|---|
| 163 | Mfr Equip Name                  
 | 
|---|
| 164 |      assigned to the station                    
 | 
|---|
| 165 |      one or more empty required fields                  
 | 
|---|
| 166 | FIELD NAME - name or abbreviation of the required field                 
 | 
|---|
| 167 | The only two fields that you cannot correct in this manner are the ENTRY                        
 | 
|---|
| 168 | NUMBER (#.01) and the WORK PERFORMED (#6914.02,9) fields. To correct these                      
 | 
|---|
| 169 | fields, contact the IRM or ADPAC for assistance.                        
 | 
|---|
| 170 | The following is a multiple-type field:                 
 | 
|---|
| 171 | If the required fields are left empty, the following will occur                 
 | 
|---|
| 172 |    ENTRY NUMBER (#.01) - the entire record will not be converted                        
 | 
|---|
| 173 |    MFGR. EQUIPMENT NAME (#3) - the EQUIPMENT CATEGORY (#6) field                        
 | 
|---|
| 174 |                                will be used as a default                        
 | 
|---|
| 175 |    CMR (#19) - two dashes (--) will be used as a default                        
 | 
|---|
| 176 |    LOCATION (#24) - the station number will be used as a default                        
 | 
|---|
| 177 |    WORK PERFORMED (#6914.02,9) - the equipment work order will not                      
 | 
|---|
| 178 | All other required fields will be converted as empty.                   
 | 
|---|
| 179 | INV. (#6914) file that contain an invalid value in a lookup-type or pointer                     
 | 
|---|
| 180 | This report is sorted by station number. When printing or viewing this                  
 | 
|---|
| 181 |      file assigned to the station.                      
 | 
|---|
| 182 |      have an invalid value in one or more of the lookup fields                  
 | 
|---|
| 183 | FIELD NAME - name or abbreviation of the lookup field                   
 | 
|---|
| 184 |      multiple number.)                  
 | 
|---|
| 185 | SHOP (#6914.04,.01) field. To correct this field, contact the IRM or ADPAC                      
 | 
|---|
| 186 | for assistance.                 
 | 
|---|
| 187 | If any of the lookup fields on this report is left with invalid                 
 | 
|---|
| 188 | Fund                    
 | 
|---|
| 189 | Serial #                        
 | 
|---|
| 190 | Type of Entry                   
 | 
|---|
| 191 | Entry Number                    
 | 
|---|
| 192 | Parent System                   
 | 
|---|
| 193 | WORK ORDER # (#6920)                    
 | 
|---|
| 194 | Work Order compile in progress. Please try again later.                 
 | 
|---|
| 195 | Last Work Order compile done on                         
 | 
|---|
| 196 | *** Warning: Please compile the list of Work Orders first ***                   
 | 
|---|
| 197 |  found in the LOCATION (#3) field in the WORK ORDER #                   
 | 
|---|
| 198 |  no entry in the LOCATION (#3) field.                   
 | 
|---|
| 199 | CoreFLS DATA QUALITY REPORT (File# 6920 - WORK ORDER)                   
 | 
|---|
| 200 | Do you wish to queue the Work Order compile?                    
 | 
|---|
| 201 | Enter 'YES' to queue the Work Order compile or '^' to abort the compile.                        
 | 
|---|
| 202 | <Work Order Compile Aborted>                    
 | 
|---|
| 203 | CoreFLS Data Cleansing Reports Work Order List                  
 | 
|---|
| 204 | Compiling Work Order list ...                   
 | 
|---|
| 205 | *** Aborted: another Work Order compile is currently running ***                        
 | 
|---|
| 206 | CoreFLS Work Order List by Field                        
 | 
|---|
| 207 | CoreFLS Work Order List by Record                       
 | 
|---|
| 208 | WORK ORDER                      
 | 
|---|
| 209 | ORDER # (#6920) file that contain an invalid value in a lookup-type or pointer                  
 | 
|---|
| 210 | field. An invalid value is defined as a value that either does not have an                      
 | 
|---|
| 211 |      ENTERED BY (#7.5)                  
 | 
|---|
| 212 |      ASSIGNED TECH (TECHNICIANS ASSIGNED Multiple) (#6920.02,.01)                       
 | 
|---|
| 213 |      SHOP (TECHNICIANS ASSIGNED Multiple) (#6920.02,2) -                        
 | 
|---|
| 214 | Tech Assigned- Shop                     
 | 
|---|
| 215 |      EQUIPMENT ID# (#18)                        
 | 
|---|
| 216 |      WORK ACTION (Multiple) (#6920.035,.01)                     
 | 
|---|
| 217 |      WORK CENTER CODE (#35.5)                   
 | 
|---|
| 218 | records with no entry in the LOCATION (#3) field.                       
 | 
|---|
| 219 |      an invalid value in one or more of the lookup fields                       
 | 
|---|
| 220 |      invalid data                       
 | 
|---|
| 221 | REC IEN - lists the WORK ORDER # (#6920) file internal record number                    
 | 
|---|
| 222 | WORK ORDER NUMBER - WORK ORDER # (#.01) field                   
 | 
|---|
| 223 | Use AEMS/MERS to enter a valid value in the lookup field. If you have any                       
 | 
|---|
| 224 | difficulties correcting these fields, contact the IRM or ADPAC for assistance.                  
 | 
|---|
| 225 |      ASSIGNED TECH (#6920.02,.01)                       
 | 
|---|
| 226 |      WORK ACTION(#6920.035,.01)                 
 | 
|---|
| 227 | (#6920) file record. All occurrences of these fields are examined.                      
 | 
|---|
| 228 | **** Conversion Note *********************************************                      
 | 
|---|
| 229 | WORK ORDER # (#6920) file that have invalid or missing (empty) values in the                    
 | 
|---|
| 230 | fields that are being converted into the CoreFLS system.  The compile examines                  
 | 
|---|
| 231 | 12 fields to determine if there is a valid value in each.  If there is no                       
 | 
|---|
| 232 | value in the field, it is considered to be empty. If there is a value in a                      
 | 
|---|
| 233 | lookup-type (a.k.a. pointer) field, the compile examines the value to ensure                    
 | 
|---|
| 234 |      TASK DESCRIPTION (#6)                      
 | 
|---|
| 235 |      WORK PERFORMED (#39)                       
 | 
|---|
| 236 | This report is sorted by division. When printing or viewing this report, you                    
 | 
|---|
| 237 | contain an invalid value  (                     
 | 
|---|
| 238 |      to this field.)                    
 | 
|---|
| 239 | LOCATION and EQUIPMENT ID# are two fields that are checked                      
 | 
|---|
| 240 | together. It is required that at least one of these two fields                  
 | 
|---|
| 241 | have data for CoreFLS.  In other words if both fields are empty                 
 | 
|---|
| 242 | for a record, the record is flagged to be corrected. Entering data                      
 | 
|---|
| 243 | in either of the two fields corrects the record so it no longer                 
 | 
|---|
| 244 | appears on the report. These fields are noted on this report as                 
 | 
|---|
| 245 | Location/Equip ID#                      
 | 
|---|
| 246 | the detail reports.                     
 | 
|---|
| 247 | Entered By                      
 | 
|---|
| 248 | Shop                    
 | 
|---|
| 249 | Work Center Code                        
 | 
|---|
| 250 | Work Action                     
 | 
|---|
| 251 | Assigned Tech                   
 | 
|---|
| 252 | the CoreFLS system.  If fields appearing on this report are left empty, the                     
 | 
|---|
| 253 | Each row contains the following columns:                        
 | 
|---|
| 254 | *** Conversion Note  *********************************************                      
 | 
|---|
| 255 | TASK DESCRIPTION (#6) - Data in WORK PERFORMED (#39) will be used                       
 | 
|---|
| 256 |                         as the default. If both fields are empty                        
 | 
|---|
| 257 |                         then the Task Description will be                       
 | 
|---|
| 258 |                         converted as empty                      
 | 
|---|
| 259 | ENTERED BY (#7.5) - Default is                  
 | 
|---|
| 260 | PRIORITY (#17) - Default is 0 (zero)                    
 | 
|---|
| 261 | STATUS (#32) - when STATUS is empty and:                        
 | 
|---|
| 262 |    DATE COMPLETED is:     DATE STARTED is:     DEFAULT STATUS is:                       
 | 
|---|
| 263 |      empty                  not empty                                   
 | 
|---|
| 264 | In Progress                     
 | 
|---|
| 265 |      empty                  empty                                       
 | 
|---|
| 266 | Waiting for Approval                    
 | 
|---|
| 267 |      not empty              > 6 months*                                 
 | 
|---|
| 268 |      not empty              =< 6 months*                                
 | 
|---|
| 269 |                             *from the scheduled deployment date                 
 | 
|---|
| 270 |     WARNING: Fields in                  
 | 
|---|
| 271 |  orders may not be editable after                       
 | 
|---|
| 272 |     conversion to CoreFLS                       
 | 
|---|
| 273 | WORK CENTER CODE (#35.5) - If the first two characters of the                   
 | 
|---|
| 274 |                            Work Order # is                      
 | 
|---|
| 275 |  then the default                       
 | 
|---|
| 276 |                            will be                      
 | 
|---|
| 277 | , otherwise the default                 
 | 
|---|
| 278 | WORK ORDER # (#6920) -                  
 | 
|---|
| 279 |  Enter RETURN to continue                       
 | 
|---|
| 280 | you must enter valid data in these fields prior to conversion.                  
 | 
|---|
| 281 | the records with no entry in the LOCATION (#3) field.                   
 | 
|---|
| 282 |      file assigned to the division                      
 | 
|---|
| 283 | Use AEMS/MERS to enter a valid value in either of these two fields. If you                      
 | 
|---|
| 284 | have any difficulties correcting these fields, contact the IRM or ADPAC                 
 | 
|---|
| 285 | together.  It is required that at least one of these two fields                 
 | 
|---|
| 286 | have data for the CoreFLS conversion.  In other words, if both                  
 | 
|---|
| 287 | fields are empty for a record, the record is flagged to be                      
 | 
|---|
| 288 | corrected. Entering data in either of the two fields corrects the                       
 | 
|---|
| 289 | record so it no longer appears on the report. These fields are                  
 | 
|---|
| 290 | noted on this report as                         
 | 
|---|
| 291 | converted into CoreFLS.                 
 | 
|---|
| 292 |  found in the DIVISION (#.6) field in the ENG SPACE                     
 | 
|---|
| 293 |  to display the records with no                 
 | 
|---|
| 294 |  entry in the DIVISION (#.6) field.                     
 | 
|---|
| 295 | CoreFLS DATA QUALITY REPORT (File# 6928 - ENG SPACE)                    
 | 
|---|
| 296 | ENG SPACE (#6928) file that have invalid or missing (empty) values                      
 | 
|---|
| 297 | in the fields that are being converted into the CoreFLS system.  The report                     
 | 
|---|
| 298 | examines eight fields to determine if there is a valid value in each. If there                  
 | 
|---|
| 299 | in a lookup-type (a.k.a. pointer) field, the report examines the value to                       
 | 
|---|
| 300 | ensure that it is valid.                        
 | 
|---|
| 301 |      ROOM NUMBER (#.01)                 
 | 
|---|
| 302 |      BUILDING FILE POINTER (#.51) -                     
 | 
|---|
| 303 | ####################    ####################    ####################    
 | 
|---|
| 304 | ####################    ####################    ####################    
 | 
|---|
| 305 | ####################    ####################    ####################    
 | 
|---|
| 306 | ####################    ####################    ####################    
 | 
|---|
| 307 | ####################    ####################    ####################    
 | 
|---|