GM-X ERP for Blockchain - The PROJECT MANAGEMENT subsystem

By Nelson Nones

20th August 2020

Introduction
Project data: PM_DOCUMENT; PM_ISSUE; PM_SCHEDULE_HDR; PM_SCHEDULE

Introduction

blah blah blah

Project data

Figure 1 - Projects

PM_DOCUMENT table

This holds all external files and documents which have been uploaded. This then makes them available for viewing online.

Field	Type	Description
rdcaccount_id	number	Identifies the user's account where '1' = shared and anything higher is private.
documentId	number	Identity number which is generated automatically by the system.
cultureCode	string	Optional. Identifies the language in which the document is written.
documentURL	string	The filename of the attached document in the file system. This will be stored in the gm-x/documents folder with a random file name which will be generated by the system as a GUID.
documentName	string	The name of the attached document.
documentType	string	A value chosen from the following list: Acceptance test plan Authorization Bug documentation Change request Deliverable Demo script Functional spec Integration test plan Initial project plan Issue documentation Meeting agenda Meeting minutes Next milestone plan Organization chart Other Presentation Proposal Project plan Staffing plan Revised project plan Requirements trace Risk assessment Risk management plan Services agreement Software package Status report Technical manual Technical spec Template Test script Unit test plan User help User manual User requirements spec Validation master plan Work package Work plan
documentVersion	string	Optional. The version number of the attached document.
documentOrigFilename	string	The original filename on the source computer, including the file extension, from which this file was uploaded.
documentfilename	string	The filename part of documentOrigFilename excluding the file extension.
documentfiletype	string	The file extension extracted from documentOrigFilename
documentKeyWords	string	Optional. A list of user-defined keywords which help describe the document. These can be referenced in a search screen.
documentEffectiveDate	date	Optional. The date on which this document comes into force.
documentDiscontinueDate	date	Optional. The date on which this document ceases to be effective.
role_id	string	Optional. An entry taken from the MNU_ROLE table in the MENU database.
viewcount	number	A count maintained by the system which shows how many times the document has been viewed.

PM_ISSUE table

This holds the details of any issues which have been raised.

Field	Type	Description
rdcaccount_id	number	Identifies the user's account where '1' = shared and anything higher is private.
issueId	number	Identity number which is generated automatically by the system.
issueDate	date	Optional. The date on which this issue was raised.
site	string	Optional. Identifies the site/location at which this issue was raised. Only relevant if the organisation has more than one site.
issueDescription	string	Optional. A brief description of the issue.
issueNotes	string	Optional. Additional notes describing this issue.
issueStatus	number	A value chosen from the following list: 1 = Closed 2 = Deferred 3 = Open
issueClosedDate	date	Optional. The date on which this issue was closed.
issueDeferredToDate	date	Optional. The date to which this issue has been deferred.
issueOwner	string	Optional.
issueSupporter	string	Optional.
issueResolution	string	Optional. A description of how this issue was resolved.

PM_SCHEDULE_HDR table

This identifies each project for which activities will be recorded.

Field	Type	Description
rdcaccount_id	number	Identifies the user's account where '1' = shared and anything higher is private.
schedule_id	number	Identity number which is generated automatically by the system.
schedule_desc	string	A short description.
schedule_notes	string	Optional. A long description
is_active	boolean	a YES/NO flag.
start_date	date	The date on which this project started.
end_date	date	The date on which this project ended.

PM_SCHEDULE table

This holds details of each activity within a project.

Field	Type	Description
rdcaccount_id	number	Identifies the user's account where '1' = shared and anything higher is private.
schedule_id	number	Links to an entry on the PM_SCHEDULE_HDR table.
seq_no	number	A sequence number which is generated by the system. This starts at 1 for each project.
activityDescription	string	A brief description of this activity.
pStart	date	Start date.
pEnd	date	End date.
pColor	string	Identifies the colour which will be used for this activity when it is displayed on a Gantt chart. The colour will be chosen from a dropdown list.
pLink	string	Optional.
pMile	boolean	Is this a milestone? Yes or No.
pRes	string	Resource name.
pComp	number	Percentage complete.
pGroup	boolean	Is this the parent of a group? Yes or No.
pParent	number	If this activity is a member of a group then this identifies the seq_no of the parent activity of that group.
pOpen	boolean
pDepend	numeric	Optional. If this activity is dependent on another activity being complete before it can be started then this is the seq_no of that activity.
pCaption	string	Optional.

Date created: 20th August 2020