Description

There are several requirements that were not included in the previous PRs and due to the nature of the implementation I think it would be better to just gather them together in this one PR for this issue.

Description

Should be able to add/define ConditionRatings for an AssetType.

• entity ConditionRating with a single-member composite key condition:Integer and desc:String.

• UI for reviewing, adding and defining new conditions.

• testing functionality.

Expected outcome

Be able to describe the condition of an asset and to plan appropriate maintenance and/or replacement activities.

• a document describing progress on the project, as well as how to use the implemented application

• has to be written in latex, with proper version control

The Bulk Upload feature helps you upload or update multiple documents at the same time without needing to go to Add new document and select each document individually.

Description
System Engineer must be able to bulk upload and register Assets from a completed project. So that, all Assets developed/delivered by the project can be tracked and depreciated, and maintenance can be planned, scheduled and performed on them.

Acceptance criteria
In a bulk upload:
Asset description/record is created and associated with the relevant Asset Type;
A new, unique Asset Id has been generated and assigned to the Asset;
Relevant information (mandatory Asset attributes based on Asset Type) has been captured/populated.

This can be done with the usage of functionality which we provide for AC05 case ( register and classify an Asset).

Description
Implement an opportunity to record the Role, Business Unit or Organisation that owns an Asset (or Asset Type)

Expected outcome
The system engineer knows who manages the budget for the Asset (or Asset Type).

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Acceptance criteria
Asset / Asset Type is associated with the applicable Asset Owner and
the date/time of the association is recorded.

Description

We need to come up with a good way to handle key generation in case of an exception after an entity had its ID assigned but the database transaction was rolled back.

The idea is that we need to somehow store the key that was assigned to our asset even without saving the asset in the database. I.e. when we create Asset1 and then create and save Asset2 before Asset1, then actually Asset2 will have key 1 and Asset1, to the confusion of the user, will be 2. This is something that shouldn't happen and therefore we need to find a solution.

Approach to solving the problem

Check if asset wasn't saved at all -- if that's true, then simply generate a number and save the asset. If we get an exception and the asset is not saved, we reset the number to default.

Expected outcome

In case of concurrent changes, everything should work properly and the data shouldn't be "lost" because of running into problems with the ID being already assigned.

If the loading rate is 120% then error must be raised

Description

There needs to be a possibility to mark the Asset entity as a regulatory asset (see: activatable as example).

• set Asset as regulatory

• check for service interruptions

Expected outcome

Asset can be classified as a regulatory asset.
If an Asset is regulatory and there has been a service interruption (ServiceStatus is 'interrupted', for example), we need to be able to report it.

Description

The main idea behind the implementation is that users (accountant, systems engineer, maintenance planner, maintenance planner) can change the assets to Capex that were raised to buy/pay for them - or the project that designed them / created them.

This is to ensure that assets can be tracked, depreciated and disposed of properly.

Functionalities can be made as a separate class or implemented directly in the Asset class. Therefore, in the previous way(realization of users' story), it is best to implement a separate class in the services directory.

Expected outcome

Capex or Project number is recorded against the specific Asset(s) that were acquired/developed;

And Asset(s) can be selected/tracked by the Capex or Project that they are associated to;

And (planned/unplanned) maintenance costs over the lifetime of the Asset(s) can be determined through the Work Orders associated to them.

Description
System Engineer, Maintenance Planner, Maintenance Scheduler must have the right to register and classify an Asset

Expected outcome
System Engineer, Maintenance Planner, Maintenance Scheduler can track and depreciate Asset. Also, its maintenance can be planned, scheduled, and performed on it if required.

Acceptance criteria
Asset description/record is created and associated with the relevant Asset Type.
A new, unique Asset Id has been generated and assigned to the Asset.
Relevant information (mandatory Asset attributes based on Asset Type) has been captured/populated.

#2 - here we develop functionality for System Engineer to add and define Asset Class.

Description

Should convert AssetClass master from simple to compound.

Expected outcome

An improved AssetClass master.

This is a spin-off issue within the larger issue describing AC08 in #33.

The description of this particular functionality is included in:

1. TG-Demo-Team/asset-acquision#13
   and
2. TG-Demo-Team/asset-acquision#14

Progress:

• add Project entity

• add the corresponding UI

• create a project property for AssetFinDet

Description
Entity 'AssetSchedulingDet' should be created as a one-2-one association with Asset. The following properties should be present at the beginning:

• acquireDate: Date -- the date/time when the asset was created or purchased.

• isMaintenanceBy: the Role, Business Unit or Organisation -- who is responsible for planning & scheduling maintenance & repairs of the Asset.

An instance of 'AssetSchedulingDet' should be saved at the same time as a new instance of Asset.

Expected outcome
There is information about who schedules maintenance & repairs the Asset.

Description

Should be able to add/define ServiceStatuses.
Possible states are: planned, operational, not in use, under repair, etc.

• entity ServiceStatus with a single-member composite key name:String and desc:String.

• UI for reviewing, adding and defining new states.

• testing functionality.

Expected outcome

This will enable us to describe the current state of an asset
(by associating it to the appropriate service status)

Identified that an Asset is a 'regulatory'/'key service' Asset properly

Description

add/define a new Asset Type (subsets of Asset Classes)

• activatable entity AssetType with a single-member composite key name:String and desc:String.

• property assetClass: AssetClass to allocate asset types to asset classes.

• UI for reviewing, editing and creating new asset type instances.

Expected outcome

Asset Type description/record is created and associated to the relevant Asset Class.

Description

The main idea behind the implementation is that the system engineer was able to use data from existing Assets for new Assets (that is, it would be necessary to implement a data call from other objects of the same class). This is to avoid repeatedly entering the same data for multiple Assets.

Expected outcome

Users can select pre-populated fields/information from an Asset to be replicated/copied to other Assets.

Description

Adding an alternate layout for the main application to be more responsive.

add better tests for:

• ConditionRating class

• ServiceStatus class

• AssetDao and testing of the key generation error

Description

• Create an entity AssetServiceStatus with the following properties:

1. service status
2. currentStatus
3. currentOwnership

• Cover the implemented functionality with tests

Excpected outcome
I know the status of the Asset, where it is, whether it is currently in service and what maintenance it requires.

Acceptance criteria
Asset is associated to the relevant Service Status and the date/time of the association/change of state is recorded.

Description

Specify the loading/usage rate of an asset.

• MaintenancePlanner entity with String:name, String:description and Decimal:rate.

• maintenancePlanner property for Asset.

Expected outcome

The typical/average loading or usage rate is recorded and captured for the Asset.

User Story

Description

Create entity type AssetClass.

Expected Outcome

Ability to create and edit asses classes.

It would be nice for all the Asset Acquisition related modules to throw our own exception.

in #27 we implemented a custom exception module, now once the other changes are merged for condition rating, asset- classes etc, we should modify the exception calls to AssetAcquisitionModuleException.

Description

• Create an activatable entity AssetClass with a single-member composite property name: String. Also need property desc: String that is required.

• Create Asset Class Master.

• Create Asset Class Centre.

Expected outcome

The ability for users to enter, modify and search for asset classes.

Description
Entity 'AssetControlDet' should be created as a one-2-one association with Asset. The following properties should be present at the beginning:

• acquireDate: Date -- the date/time when the asset was created or purchased.

• isOverseeingBy: the Role, Business Unit or Organisation -- who controls/operates the Asset (or Asset Type).

An instance of 'AssetControlDet' should be saved at the same time as a new instance of Asset.

Expected outcome
There is information about who controls the asset

Description

There needs to be a possibility to mark the Asset entity as a key service asset.

• set Asset as key service

• check for service interruptions

Approach

Clarify what is a key service asset.

Expected outcome

Asset can be classified as a key service asset.
If an Asset is a key service asset and there has been a service interruption (ServiceStatus is 'interrupted', for example), we need to be able to report it.

• Make sure that the rate will be in the range from 0 to 100(create a validator).
• Fix input format so it contains "%" symbol.
• Cover with unit tests.