100 likes | 249 Views
Achieving New Nuclear Virtual Plant Configuration Management. Data Model Overview. Training (Personnel Qualification Records Centric). Operations (Component Tag, Setpoint, Tech Spec, Location Centric). Engineering (Component Tag or other Unique Identifier, Location Centric).
E N D
Achieving New Nuclear Virtual Plant Configuration Management
Data Model Overview Training (Personnel Qualification Records Centric) Operations (Component Tag, Setpoint, Tech Spec, Location Centric) Engineering (Component Tag or other Unique Identifier, Location Centric) Overlap of data shared by all Work Control/Maintenance (Unique ID, Work Order, Test Measurement Results Centric) Supply Chain (Piece/Parts, Manufacture/Model Centric) HP/Chemistry (Measured Data, Centric)
Equipment Life Cycle Work Process Phase IV: Purchase Order / Vendor Drawings & Models Phase I: Equipment Data Development Phase III: Equipment Specs & RFQ Phase II: Budget Estimate Phase V: Fabricate /Deliver/Install Phase VI: Operations and Maintenance access engineering information As Installed Authorize Project Conceptual Design Bid Approval Pay Fab Approval Owner Operator ProjectAuth BudgetEstimate PayRequest FabReview PerformanceReq BidReview Production Design Application Exchanges Receipt, Inspection, Installation & Commission Fab Review & Approval Authorization Estimate Preliminary Design Bid Eval & Award Application Exchanges BidDesign Bid Package Tagged List FabAuth EPC Care, Install + Spares BudgetRFQ Purchase Order BidRFQ Supplier / Distributor AsShipped VendorDocs Receive PO BidQuote Fabricate Ship Invoice BudgetQuote Design Review Bid Quote POSpec Design Review Budget Quote Approval Drawings transaction = AEX usage scenarios FabDwg
What is XML? • XML is an eXtensible Markup Language • It is derived from HTML (HyperText Markup Language), but is much more rigorous • It is not really a language, but a data format. • XML is a universally defined, human readable, extensible data format. • It is ideal for data interchange between two processes.
How should we use XML? • Documents • XML separates a document into 3 parts: • XSD – schema – defines the rules for the structure of the document • XML – the actual data of the document (no formatting rules – just hints). • XSLT – the rules for presenting the document
What is an XML Schema? An XML Schema is an XML formatted file containing the set of rules for an XML document. Example: <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" <xs:element name="Root"> <xs:complexType> <xs:attribute name="A1"/> </xs:complexType> </xs:element> </xs:schema>
What does a schema specify? A schema can specify: • Element names • Attribute names • Element hierarchy and organization. • Allowable element usage. • Allowable element and attribute values including • Type of value (number, string, date, …) • Range of values (positive integer, >5, <=100.1…) • Choices of values (“pump”,”valve”,”pipe”,…) • Pattern of values (“###-###-####”,”#####-####”…)