AMS: adjust schedule format
Add projects, add MDDL
This commit is contained in:
parent
f13e1e2ee2
commit
f7ee72a66b
4 changed files with 262 additions and 135 deletions
|
|
@ -1,3 +1,5 @@
|
|||
.. _projects:
|
||||
|
||||
##################
|
||||
Project Management
|
||||
##################
|
||||
|
|
|
|||
50
documents/project/mddl.rst
Normal file
50
documents/project/mddl.rst
Normal file
|
|
@ -0,0 +1,50 @@
|
|||
Master Document and Delivery List
|
||||
#################################
|
||||
|
||||
The MDDL is a comprehensive, hierarchical catalog of all the documents and files
|
||||
related to the test reactor project. The MDDL includes information such as
|
||||
document number, revision, title, and maturity status (e.g., completion
|
||||
percentage). This serves as a central reference point, providing an overview of
|
||||
the project's documentation and helping team members find relevant and
|
||||
up-to-date information. Furthermore, the MDDL helps maintain organization,
|
||||
control, and versioning of documents.
|
||||
|
||||
* Program Deliverables
|
||||
* Full set of QA program procedures, including engineering and
|
||||
configuration management
|
||||
|
||||
* Design Deliverables
|
||||
* Design basis events and plant functions
|
||||
* System Design Documents for all systems (including requirements/functions,
|
||||
equipment list, parameters)
|
||||
* Long-lead equipment list
|
||||
* Probabilistic Risk Assessment (PRA) model
|
||||
* General arrangement (3D model and extracted drawings)
|
||||
* P&ID drawings for all systems
|
||||
* Engineering simulator software
|
||||
* Training simulator software
|
||||
* Plant safety model (i.e. RELAP)
|
||||
* Core models (i.e. CASMO/SIMULATE)
|
||||
* Shielding models (i.e. MCNP)
|
||||
* Balance of plant model (i.e. Flownex)
|
||||
* Fuel performance models (i.e. FRAPCON and FRAPTRAN)
|
||||
* Pipe restraint models
|
||||
* Equipment models (i.e. SolidWorks)
|
||||
* Civil/structural models, coupled to ship motions (i.e. ANSYS)
|
||||
* Emergency planning documents
|
||||
* Plant Technical Specifications
|
||||
* Plant Operating Procedures
|
||||
|
||||
* Project Management Deliverables
|
||||
* Resource-loaded schedule out to TTP operation
|
||||
* Bottoms-up parametric cost estimate model and reports
|
||||
|
||||
* Regulatory Submittals
|
||||
* Topical Reports
|
||||
* Argument that Ship is the site (and so construction can occur before CP)
|
||||
* Argument that TTP is a prototype reactor (104 license option)
|
||||
* Argument
|
||||
* Construction Permit Application
|
||||
* Preliminary Safety Analysis Reports
|
||||
* Environment Report
|
||||
* Operating Permit Application
|
||||
20
documents/project/projects.yaml
Normal file
20
documents/project/projects.yaml
Normal file
|
|
@ -0,0 +1,20 @@
|
|||
# Data regarding the various project the company is working on.
|
||||
# The abbreviations drive document/record numbering
|
||||
projects:
|
||||
- name: Training and Test Platform
|
||||
abbrev: TTP
|
||||
description: >
|
||||
The FOAK AMS nuclear ship, owned and operated by AMS and used for training and testing.
|
||||
Effectively it produces the information validating the commercial readiness of
|
||||
higher-powered ships. It's intended to be of the same design as the commercial
|
||||
power plant, but may be downrated e.g. from 50 MWe to 10 MWe.
|
||||
- name: Integration Shipyard
|
||||
abbrev: ISH
|
||||
description: >
|
||||
The shipyard that integrates nuclear power plants into pre-built ships.
|
||||
- name: Nuclear Ready
|
||||
abbrev: NRDY
|
||||
description: >
|
||||
Standard interfacing information that defines how to make a ship that can
|
||||
easily be outfitted with a nuclear power system at the Integration
|
||||
Shipyard.
|
||||
Loading…
Add table
Add a link
Reference in a new issue