ge-aerospace/powershell-scripts
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove all emojis from markdown documentation

Browse Source 
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
cproudlock
2025-12-10 11:03:45 -05:00
parent fc6be8a876
commit 96cb1dd946
22 changed files with 256 additions and 256 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
docs/TECHNICAL_ARCHITECTURE.md
View File

@@ -86,7 +86,7 @@ The GE Manufacturing Asset Management System is a comprehensive PowerShell-based
- Gateway and subnet mapping
```
#### `Get-GERegistryInfo` ⭐ **New in v3.0**
#### `Get-GERegistryInfo` **New in v3.0**
```powershell
# Dual registry architecture analysis
- 32-bit registry path: HKLM:\SOFTWARE\GE Aircraft Engines
@@ -109,7 +109,7 @@ The GE Manufacturing Asset Management System is a comprehensive PowerShell-based
### Phase 1: System Discovery
```
PC Environment → System Info Collection → Classification Engine
PC Environment System Info Collection Classification Engine
│
├─ Hardware Identification (WMI/CIM)
├─ Operating System Analysis
@@ -119,7 +119,7 @@ PC Environment → System Info Collection → Classification Engine
### Phase 2: Manufacturing Intelligence
```
Registry Analysis → Manufacturing Config → Service Architecture
Registry Analysis Manufacturing Config Service Architecture
│
├─ GE Aircraft Engines Detection (32-bit/64-bit)
├─ DualPath Configuration Analysis
@@ -129,7 +129,7 @@ Registry Analysis → Manufacturing Config → Service Architecture
### Phase 3: Network Topology
```
Network Interfaces → Machine Network Detection → Communication Analysis
Network Interfaces Machine Network Detection Communication Analysis
│
├─ Active Interface Enumeration
├─ Machine Network Identification (192.168.*.*)
@@ -139,7 +139,7 @@ Network Interfaces → Machine Network Detection → Communication Analysis
### Phase 4: Data Consolidation
```
Collected Data → JSON Serialization → API Payload Construction
Collected Data JSON Serialization API Payload Construction
│
├─ System Information Packaging
├─ Manufacturing Configuration JSON
@@ -149,7 +149,7 @@ Collected Data → JSON Serialization → API Payload Construction
### Phase 5: Centralized Storage
```
Dashboard API → Database Normalization → Relational Storage
Dashboard API Database Normalization Relational Storage
│
├─ PC Table (Basic System Information)
├─ PC_DNC_Config Table (Manufacturing Settings + Registry Architecture)
@@ -158,9 +158,9 @@ Dashboard API → Database Normalization → Relational Storage
└─ Machines Table (Auto-populated from PC machine numbers)
```
### Phase 6: Machine Auto-Population ⭐ **New in v3.2**
### Phase 6: Machine Auto-Population **New in v3.2**
```
PC Data Collection → Machine Number Extraction → Automated Machine Creation
PC Data Collection Machine Number Extraction Automated Machine Creation
│ │ │
├─ Registry Scan ├─ Hostname Patterns ├─ Machine Records
├─ DNC Detection ├─ GE Machine Numbers ├─ PC Relationships
@@ -190,12 +190,12 @@ function Get-GEMachineNumber {
# Pattern matching for GE hostname conventions
if ($Hostname -match '[HG](\d{3})') {
$machineNum = $Matches[1]
return "M$machineNum" # Convert H123/G123 → M123
return "M$machineNum" # Convert H123/G123 M123
}
}
```
### Machine Auto-Population Architecture ⭐ **New in v3.2**
### Machine Auto-Population Architecture **New in v3.2**
The system automatically creates machine records from shopfloor PC data using a multi-phase approach:
@@ -210,7 +210,7 @@ function Get-GEMachineNumber {
# Priority 2: Hostname pattern matching
if ($Hostname -match '[HG](\d{3})') {
return "M$($Matches[1])" # H3103 → M3103
return "M$($Matches[1])" # H3103 M3103
}
}
```
@@ -260,7 +260,7 @@ END
- **Multiple PC Handling**: Machine 0615 has 5 connected PCs
- **Role Classification**: Control, HMI, Engineering, Backup PCs identified
### Dual Registry Architecture Handling ⭐ **New in v3.0**
### Dual Registry Architecture Handling **New in v3.0**
```powershell
# Intelligent priority system prevents data overwrites
if ($geInfo.DualPathEnabled -eq $null) {