Towards an Enhanced Technical Management Framework

Technical Information Handling in the 20’s

Microsoft Office generated files (docx, xlsx, pptx, mppx files, complemented with their pdf/a files for long term archival) will be abandoned or discontinued in favor of dedicated web-services similar to EDH documents or on-line collaborative authoring and editing tools such as Authorea.

3D CAD software (CATIA-like packages) will also be abandoned or discontinued in favor of web-services similar to OnShape for instance (see

Various web-based templates will be proposed to contributors to author and edit key technical documents such as project proposals, project management plans, CDR’s, project risk registers, engineering specs, ECR’s, manufacturing & assembly plans, various procedures and reports, operation and maintenance manuals, etc.

Breakdown into Processes

The “very top components” of a technical management framework are conveniently shown on Fig.\ref{fig:choreography}: the core activities (a.k.a. primary processes: study, develop, O&M, hand over) are complemented by pilot processes (a.k.a. managerial processes, i.e. mainly strategic planning and decisions and guidance w.r.t. applicable rules and standards) and support processes (information handling, configuration management, etc.). The openSE ( facility lifecycle shown on Fig.\ref{fig:facilityLifecycle} car also serve as a starting point for setting up a list of processes related with technical management at large.

\label{fig:choreography} The top-level processes of a technical management frameworks (adapted from Michael Porter’s value chain).