Credit Transfer | Credit Trade screen to be built based on wireframe and including history |3| [v0.0.3-alpha]

https://trello.com/c/1XtO2C6o

https://trello.com/c/XDtqOGCb/335-authorisation-restrict-the-use-of-the-accept-button-to-the-respondent-of-a-buy-sell-type-credit-transaction-3

https://trello.com/c/YRDX1Nqq/419-coding-standards-refactor-front-end-core-architecture-in-order-to-reduce-the-amount-of-code-required-to-be-written-for-each-feat

https://trello.com/c/Gds5taYd/292-ui-react-modified-to-accommodate-the-change-of-the-api-providing-child-records-as-part-of-gets-1-coding-standards

DEVELOPING THE TRANSPORTATION FUELS REPORTING SYSTEM WEBSITE BACK-END (BCDX-MEM-003)

Code Repo: https://github.com/bcgov/tfrs
Wiki: https://github.com/bcgov/tfrs/wiki

OVERVIEW OF OPPORTUNITY

The Transportation Fuels Reporting System is being designed to streamline compliance reporting for transportation fuel suppliers in accordance with the Renewable & Low Carbon Fuel Requirements Regulation.

We want you to use the previously developed layout and design templates (Views) and complete the back-end development work. The main focus of this effort will be in improving the /server component of the application.

BACKEND DEVELOPMENT:

• A Python/Django server was developed that implements a REST interface and database design for the initial specification of the TFRS application. Additional back-end development work is needed to refine the server by reusing a Swagger Code Generator mechanism to generate the code for a revised Swagger specification and refactor/add custom functions as needed to implement the new REST API.
• One key path in the Swagger specification is the /api/User. Extend the User API implementation to associate a user with their authentication information received in the HTTP header information. Specifically, all users in the system will be authenticated by Siteminder (via an independent process) such that Siteminder information (UserID, UserGUID) will be available in the HTTP header. Extract that information and use it to find in the database information about the user accessing the application.
• The Swagger Code Generator currently generates (amongst other code) Python/Django Models for the definitions defined in the Swagger specification. Django's ORM capabilities are subsequently used to generate the Database Model from those generated Models. Work is needed to extend the Code generator and to override some Django ORM capabilities to alter the behaviour of the generated database model. This effort will mimic comparable features implemented in the C#/.NET Core/Entity-Framework version of the generator.
  • Change the item naming style to meet the NRS Standard (e.g. all upper case names with '_' separators, no table prefixes)
  • Push comments describing the items in the design (e.g. tables and attributes) into the database metadata
  • Force the database to use UUIDs as keys vs. traditional sequential IDs
  • Extend tables to include standard auditing fields, populated via application and/or database triggers.

USER STORIES

As a trading partner I need to be able to navigate through a series of self-service screens to:

1. view information regarding past, proposed and pending credit-related activity including a real-time credit balance and list of activities that may impact that balance.
2. enter and submit the information required to propose a credit transaction to a trading partner; accept a proposed trade from a trading partner and submit that transaction proposal to the Director for approval.
3. view the information entered by the user on Transaction Details screen before proposing it to a trading partner or submitting it to the Director for approval.
4. review before authorising the transaction and submitting it to the Director for approval or saving it for future.
5. post a credit transfer opportunity. The offer needs to have the same information that a credit transaction proposal would have, without the transfer partner. Offer and credit transfers are separate entities.
6. respond to a credit transfer opportunity with acceptance of the terms, or respond to the credit transfer opportunity with a proposal that has modified terms

The Low Carbon Fuels Branch staff need to be able to:

1. input transactions to award credits for a "Part 3 Agreement" or to add validated fuel supply credits or to retire credits used for offsets in annual compliance reporting.
2. sort and search the list of all transactions and be able to export/download the tabular data for analysis in excel.
3. add companies, contacts, users, roles and permissions through the Swagger API
4. recommend approval of a proposed low carbon fuel credit transfer
5. approve the credit transfers
6. retire credits from or adjust a company's credit balance

ACCEPTANCE CRITERIA

To be paid for this opportunity, you will:

1. Participate as a part of our team's sprint planning workshop from 1pm to 4pm on June 28th, 2017 at 3rd Floor - 1012 Douglas Street in Victoria, BC. The planning session can be rescheduled if the selected individual is not available at that time.

2. Spend a minimum of 2 hours per weekday (Tuesday - Thursday, excluding holidays, between the hours of 8:30 AM and 5:00 PM) working in person with us at our office (1012 Douglas Street in Victoria, BC) for the duration of your work. We want you to work side-by-side with our front-end developer and DevOps specialist to implement the desired functionality in our dev environment.

3. Use the existing code generator and write the required custom code to implement the back-end
   a. model,
   b. controller,
   c. form endpoints,
   d. validation of form data, and
   e. automated tests for the revised set of REST end-points.

   The Swagger definition for the application is in the TFRS github repo in the APISpec folder.
   

4. Extend the *User API as appropriate to relate the User information from the HTTP request header to a user record in the TFRS database.

5. Extend the existing swagger code generator to produce additional code that will result in a Database Model that meets the Database Architecture Standards of the Natural Resources Sector (NRS), and use the revised generator to generate the TFRS Database Model

6. Use Trello to document the work completed, to demonstrate completion of the work in this opportunity, and include as appropriate references and links on each trello task to github commits

7. Conduct knowledge transfer with the Ministry Full Stack Developer.

HOW TO APPLY

Please send a proposal by 16:00 PST, 26 June 2017.

Within your email, indicate your acceptance of the Code With Us terms, you must attach a copy of the terms along with any information requested in the "Acceptance" section of the document.

If we are satisfied with the proposals we receive, we will assign this opportunity by 16:00 PST, 27 June 2017 with work proposed to start as soon as possible on/after 28 June 2017.

PROPOSAL EVALUATION CRITERIA

Please email your proposal to [email protected].

Please reference the issue name "Developing the Transportation Fuels Reporting System website back-end (BCDX-MEM-003)" in your proposal.

SCORING CRITERIA

Please provide:

• Your confirmation of being able to meet all of the Acceptance Criteria by 4 August 2017.
• A short (around 200 words or less would be nice) summary of your experience working with agile projects (40 points).
• References to your relevant experience and demonstrated ability to do the work (60 points).
• (preferred) a link to examples of your work (e.g. GitHub projects).

INFORMATIONAL OPEN HOUSE

On 22 June 2017 and 23 June 2017, we will host two information sessions from 12pm to 1pm, for interested developers to talk with our team about the work. If you'd like to attend, please email [email protected].

Please also feel free to ask questions via the comments section on the issue in GitHub.

QUESTIONS?

Please provide comments below

Fuel Suppliers required to submit their compliance report can use this feature to manage that correspondence including

• File Upload
• Correspondence History
• Notifications

User subscriptions for email and sms alerts on: credit transfer status changes (draft, proposed, accepted, approved, rejected, rescinded, completed) credit transfer opportunities (opportunity to buy or sell)

When you create a credit transfer, it brings you back to the credit transactions list. But when you click on "view", the page loads with an error
https://trello.com/c/cvQbhkUv/534-ui-credit-transfer-view-screen-wont-load-2

As a TFRS Developer, I want to document best practices and procedures for implementing Back-End Development so that future TFRS Developers will be able to create code that is consistent and of high quality.

Context:
The back-end is in the middle of a refactor and we should point out the difference between the old code & the new code, and how to write code moving forward.https://trello.com/c/UdlHGkTr/529-dev-documentation-back-end-development-1

https://trello.com/c/mThFMGbl/282-api-get-fix-for-bulk-load-issue-from-von-project-1

https://trello.com/c/8xkpHz7C/317-credit-transfer-initiator-can-submit-a-credit-transfer-proposal-and-see-appropriate-buttons-3

https://trello.com/c/p5y8gF4l

Story:
As a TFRS Developer, I want to fix the browser URL inconsistencies so that...

Information:
The front-end UI previously used hashHistory for the URL, which comes up with the hash in front of the routes (/#/). It now currently uses browserHistory which doesn't need the hash anymore, but for some reason, the app still uses the hash. This also causes problems when submitting forms as it appends the "?" into the URL. These should be taken out as well since we don't really submit to the web server; we use ajax calls to the api.

This is a big blocker for functional tests, as it can't successfully traverse our URL paths when an action happens.https://trello.com/c/JZnjEW7x/494-routing-fix-inconsistencies-in-browser-url-3

BCeID and IDIR users can be searched for against each of those directories, and selected for access to the system.

https://trello.com/c/2kxFdxGj/107-2-authentication-make-the-url-send-a-host-header

https://trello.com/c/4MTGiOEo/228-authorization-add-client-side-current-user-concept-that-tracks-the-organization-of-the-user-1

CreditTrade | Update the backend code such that when a Trade is approved it is marked as completed and the trade is executed |2| !

https://trello.com/c/lmNNUp5v

https://trello.com/c/uuUOCGlN/508-org-controls-control-for-viewing-a-credit-transfer-3

https://trello.com/c/EZ3DPc4D/217-credit-transfer-edit-a-saved-draft-credit-transfer-3

post a credit transfer opportunity. The offer needs to have the same information that a credit transaction proposal would have, without the transfer partner. Offer and credit transfers are separate entities.

https://trello.com/c/s3MwdUgd/312-login-display-user-name-in-app-header

• Roles for Gov
• Roles for Fuel Suppliers
• Permissions for Gov
• Permissions for Fuel Suppliers

https://trello.com/c/s3EN0LtO/325-credit-transfer-create-a-new-credit-transfer-1

As a TFRS PO, I want all of the recognized Part 3 fuel suppliers to be loaded into the system so that when I eventually enter historical transactions the associated credits go to the correct company.

Info:
Initial load of data (company names; credit balance of zero)https://trello.com/c/bx0w7hpH/532-historical-data-loading-initial-company-information-1

;
https://trello.com/c/hQaBLcMG/65-display-username-and-company-avatar;
2017-09-28T19:00:00.000Z;

Add logging to Django + Openshift

https://trello.com/c/ldYNnUli/507-org-controls-control-for-credit-transfer-list-2

• Market summary (Low Carbon Fuels Credit Market)
• Sort/Filter lists
• Export lists
• History of a transaction

Story:
As a TFRS Developer, I want all the ID columns to be descriptive of their table names.

Information:
In Card 315, two items were skipped due to complexity:

• Rename all "Id" fields to be Id (Won't be implemented due to complexity)
• Rename all “id” fields to be
Id and all FKs to be Id except where there is more than one FK in a table – e.g. initiatorId and respondentId in the CreditTrade table. (Won't be implementing the first one due to complexity)

These changes should still be implemented. A good time to revisit this is when we get close to upgrading to Django 2.x or changing to a different framework for the API

django2.0, ormhttps://trello.com/c/mdE2i0xF/425-data-model-rename-the-id-column

User Story: As a Fuel Supplier Signing Authority, I want to be able to send a credit transfer to another Fuel Supplier so that they can review the transaction before sending it to the Branch.

Scenario:
GIVEN that I am an Organizational user
AND my Organization type is Fuel Supplier
AND I have been assigned a Signing Authority role
AND I am selling 10,000 credits at $150 / credit to Very Good Fuels
WHEN I click propose (TBD: send?) and accept the confirmation alert with the required statements from the Reg (Card #381)
THEN the transaction history record is saved on the Credit Transactions (account activity) list
AND the status changes to proposed (TBD: Sent?)
AND I am returned to the Credit Transactions (account activity) page
AND the transaction record for the transfer is visible at the top of the Credit Transactions list

Demo:
Show that the External user is able to send a credit transfer proposal to a trading partner
Show the Send button (label TBD - Confirm, Certify, Sign, Sign Off)
Show that the status of the transfer is updated
https://trello.com/c/8xkpHz7C/317-credit-transfer-initiator-can-submit-a-credit-transfer-proposal-and-see-appropriate-buttons-3

Story:
As a low carbon fuel credit trader I want to be sure that trades can only be edited before the trade is proposed to the trade partner so that the agreed upon balances of credits are exchanged

Scenario 1:
GIVEN that I am a credit trade initiator
WHEN I save a draft credit trade proposal
THEN the user is returned to the Credit Transactions (account activity) page
AND the transaction appears in the top of the Credit Transactions (account activity) list
AND the transaction item shows an edit icon in the edit column of the list
AND the edit icon can be clicked to edit the transaction

Scenario 2:
GIVEN that I am a credit trade initiator
WHEN I propose a credit transfer to another fuel supplier
THEN the user is returned to the Credit Transactions (account activity) page
AND the transaction appears in the top of the Credit Transactions (account activity) list
AND the transaction does not show an edit icon in the edit column of the list

Update the Credit Transfer page (http://dev.lowcarbonfuels.gov.bc.ca/#/credittransfer/3) make the sentence editable only if the trade is New (unsaved) or CreditTradeStatus is "Draft".https://trello.com/c/EZ3DPc4D/217-credit-transfer-edit-a-saved-draft-credit-transfer-3

https://trello.com/c/buhUbtZx

Authenticate users view list of companies update company details Add contacts to a company

The Transportation Fuels Reporting System is being designed to streamline compliance reporting for transportation fuel suppliers in accordance with the Renewable & Low Carbon Fuel Requirements Regulation. We want you to complete back-end development of the first set of screens which will enable Credit Trading.

DEVELOPING THE TRANSPORTATION FUELS REPORTING SYSTEM WEBSITE BACK-END (BCDX-MEM-002)

You can find our current code base at https://github.com/bcgov/tfrs.

We want you to use the previously developed layout and design templates (Views) and complete the back-end development work. The site should deliver the following functionality:

User Stories

As a trading partner I need to be able to navigate through a series of self-service screens to:

• view information regarding past, proposed and pending credit-related activity including a real-time credit balance and list of activity that may impact that balance.
• enter the information required to propose a credit transaction to a trading partner; accept a proposed trade from a trading partner and submit that transaction proposal to the Director for approval.
• view the information entered by the user on Transaction Details screen before proposing it to a trading partner or submitting it to the Director for approval.
• review before authorising the transaction and submitting it to the Director for approval or saving it for future.

The Low Carbon Fuels Branch staff need to be able to:

• Input transactions to award Part 3 Agreement or fuel supply credits or adjust balances based on new information to users through the same process as above
• Run queries to produce periodic (quarterly, annually, etc.) reports on credit transaction activity with the following variables:
  - Number of transfers
  - Total credits traded
  - Avg. market value
  - Min/max value

ACCEPTANCE CRITERIA

To be paid for this opportunity, you will:

1. Participate as a part of our team’s sprint planning workshop from 10:00 PM - 12:00 PM on April 10, 2017 at 1012 Douglas Street in Victoria, BC.
2. Spend a minimum of 2 hours per weekday (Tuesday - Thursday, excluding holidays, between the hours of 8:30 AM and 5:00 PM) working in person with us at our office (1012 Douglas Street in Victoria, BC) for the duration of your work. We want you to work side-by-side with our front-end developer and DevOps specialist to implement the desired functionality in our dev environment.
3. Develop the back-end model, controller, form endpoints, validation of form data, automated tests for all applicable code for each of the following views:

      i.    Credit Trading Dashboard containing summary views of 
               Credit Balance, 
               Notifications, and 
               Transaction Activity
      ii.   Credit Trade Create Transaction view
      iii.  Credit Trade Transaction Summary view
      iv.   Credit Trade Account Balance view
      v.    Credit Trade Alerts view
      vi.   Credit Trade Notifications view
      vii.  Credit Trade Alert Settings view

4. A notification microservice for communicating transaction events via text or email
5. Develop an OpenAPI (Swagger) specification

HOW TO APPLY

Please send a proposal to by 16:00 PST, Tuesday, April 4, 2017.

With your email, to indicate your acceptance of the Code With Us terms, you must attach a copy of the terms along with the required information asked for in the "Acceptance" section of the document.

If we are satisfied with the proposals we receive, we will assign this opportunity by 16:00 PST, Friday, April 7, 2017 with work proposed to start on Monday, April 10, 2017.

Informational Open House

On Tuesday, March 21th and 22nd, from 12:00-1:00 PM, we will be hosting a drop-in session for interested developers to talk with our team about the work. If you’d like to attend, please email [email protected].

Please also feel free to ask questions via the comments section on the issue in GitHub.

PROPOSAL EVALUATION CRITERIA

Please email your proposal to [email protected].

Please reference the issue name "Developing the Transportation Fuels Reporting System website back-end (BCDX-MEM-002)" in your email.

Scoring criteria:

• Your confirmation of being able to commit the time to meet all of the Acceptance Criteria by April 28, 2017.
• A short (around 200 words or less would be nice) summary of your experience working with agile projects (40 points).
• References to your relevant experience and demonstrated ability to do the work (60 points). For example, a link to your GitHub projects.

QUESTIONS?

Please provide comments below

As a TFRS Developer, I want to document best practices and procedures for implementing Front-End Development so that future TFRS Developers will be able to create code that is consistent and of high quality. https://trello.com/c/QL6NnCnK/528-dev-documentation-front-end-development-1

User Story: As a Signing Authority, I want to be able to accept a credit transfer proposal from another Fuel Supplier so that I can send it to the Branch for review.

Scenario:
GIVEN that I am an Organizational user
AND my Organization type is Fuel Supplier
AND my role is Signing Authority
AND I have received a Credit Transfer Proposal from another fuel supplier
WHEN I click Accept and agree to the confirmation alert with the required statements from the Reg (Card #382)
THEN the transaction history record is saved on the Credit Transactions (account activity) list
AND the status changes to Accepted (TBD:?)
AND I am returned to the Credit Transactions (account activity) page
AND the transaction record for the transfer is visible at the top of the Credit Transactions list

Demo:
Show the Accept button (label TBD - Confirm, Certify, Sign, Sign Off)
Show that the external user (recipient) is able to Accept a credit transfer that they have received.
Show that the status of the transfer changes to Accepted (TBD:?) after the button is clicked.https://trello.com/c/yDdoFhEx/319-credit-transfer-accept-a-credit-transfer-3

• credit transaction
• transaction lists and dashboard
• credit balance
• notifications

DEVELOPING THE TFRS WEBSITE FRONT-END (BCDX-MEM-004)

Code Repo: https://github.com/bcgov/tfrs
Wiki: https://github.com/bcgov/tfrs/wiki

OVERVIEW OF OPPORTUNITY

The Transportation Fuels Reporting System is being designed to streamline compliance reporting for transportation fuel suppliers in accordance with the Renewable & Low Carbon Fuel Requirements Regulation.

We want you to replace the previously developed Django screen templates (Views) with a REACT / REDUX based front end using the Balsamiq screens we have produced. The REACT front end will utilize the REST API that is currently being developed.

BACKEND DEVELOPMENT:

• A Python/Django server was developed that implements a REST interface and database design for the specifications of the TFRS application.
• The database is implement in POSTGRESQL
• Users in the system are authenticated by Siteminder (via an independent process) however roles authorization is going to be developed in a future milestone.

MILESTONES

As a trading partner I need to be able to navigate through a series of self-service screens to:

1. view information regarding past, proposed and pending credit-related activity including a real-time credit balance and list of activities that may impact that balance.
2. enter and submit the information required to propose a credit transaction to a trading partner; accept a proposed trade from a trading partner and submit that transaction proposal to the Director for approval.
3. view the information entered by the user on Transaction Details screen before proposing it to a trading partner or submitting it to the Director for approval.
4. review before authorising the transaction and submitting it to the Director for approval or saving it for future.
5. post a credit transfer opportunity. The offer needs to have the same information that a credit transaction proposal would have, without the transfer partner. Offer and credit transfers are separate entities.
6. respond to a credit transfer opportunity with acceptance of the terms, or respond to the credit transfer opportunity with a proposal that has modified terms

The Low Carbon Fuels Branch staff need to be able to:

1. input transactions to award credits for a "Part 3 Agreement" or to add validated fuel supply credits or to retire credits used for offsets in annual compliance reporting.
2. sort and search the list of all transactions and be able to export/download the tabular data for analysis in excel.
3. add companies, contacts, users, roles and permissions through the Swagger API
4. recommend approval of a proposed low carbon fuel credit transfer
5. approve the credit transfers
6. retire credits from or adjust a company's credit balance

ACCEPTANCE CRITERIA

To be paid for this opportunity, you will:

1. Participate as a part of our team's sprint planning workshop from 1pm to 4pm on July 18th, 2017 at 3rd Floor - 1012 Douglas Street in Victoria, BC. The planning session can be rescheduled if the selected individual is not available at that time.
2. Spend a minimum of 2 hours per weekday (Tuesday - Thursday, excluding holidays, between the hours of 8:30 AM and 5:00 PM) working in person with us at our office (1012 Douglas Street in Victoria, BC) for the duration of your work. We want you to work side-by-side with our back-end developer to implement the desired functionality in our dev environment.
3. Develop the screens in REACT using the balsamiq wireframes with the following directions:
   a. Implement a Client REST web service to consume the provided Swagger REST API Specifications,
   b. Use the Gov 2.0 Bootstrap Skeleton for look and feel,
   c. implement the provided Behavior Driven Development scenarios and system messaging,
   d. create the NavUnit templates for automated functional testing,
   e. create functions for validation of form data,
4. Use Trello to document the work completed, to demonstrate completion of the work in this opportunity, and include as appropriate references and links on each trello task to github commits
5. Conduct knowledge transfer with the Ministry Full Stack Developer and Front-End Developer.

HOW TO APPLY

Please send a proposal by 16:00 PST, 14 July 2017.

Within your email, indicate your acceptance of the Code With Us terms, you must attach a copy of the terms along with any information requested in the "Acceptance" section of the document.

If we are satisfied with the proposals we receive, we will assign this opportunity by 16:00 PST, 17 July 2017 with work proposed to start as soon as possible on/after 18 July 2017.

PROPOSAL EVALUATION CRITERIA

Please email your proposal to [email protected].

Please reference the issue name "Developing the TFRS website back-end (BCDX-MEM-004)" in your proposal.

SCORING CRITERIA

Please provide:

• Confirmation that you can meet all the Acceptance Criteria by 17 August 2017
• Your Approach for meeting each of the Acceptance Criteria. (60 points)
• Your Experience working with relevant agile projects (40 points).

NOTE:
In your Experience, include a description of the work you have done recently that demonstrates your capability to deliver similar work and (preferred) a link to examples of your work (e.g. GitHub projects). If needed, explain how your experience is relevant.
In your Approach you should explain how you will work with us. For example, you may identify certain tools, techniques or methodologies that you would use and explain how you might use them.

INFORMATIONAL OPEN HOUSE

On 7 July 2017, we will host an information session from 12pm to 1pm, for interested developers to talk with our team about the work. If you'd like to attend, please email [email protected].

Please also feel free to ask questions via the comments section on the issue in GitHub.

QUESTIONS?

Please provide comments below

Story:
As a Signing Authority for my organization, I want to have the ability to accept credit transfer proposals that are sent to my company by other fuel suppliers so that I can buy/sell credits to achieve compliance with the Regulation.

Scenario:
GIVEN that I am an Organization
AND my organization type is Fuel Supplier
AND my role is Signing Authority
AND I have received a request to buy/sell credits from/to another fuel supplier
WHEN I am viewing the requested Credit Transfer Proposal in TFRS
THEN I am able to see the Accept button

Demo:
Show that Signing Authorities have access to an Accept button when viewing proposed credit transfers
Show that other roles within the organization do no have access to the Accept button

Original title of card (for context):
Associate a credit transfer record with the initiating organization and the respondent organization and implement logic to restrict the use of the Accept button

https://trello.com/c/XDtqOGCb/335-authorisation-restrict-the-use-of-the-accept-button-to-the-respondent-of-a-buy-sell-type-credit-transaction-3

https://trello.com/c/ae6NmdsW/483-credit-transfer-creating-a-new-credit-transfer-creates-two-rows-instead-of-one-bug-1

Story:
As a Signing Authority for my organization, I want to have the ability to accept credit transfer proposals that are sent to my company by other fuel suppliers so that I can buy/sell credits to achieve compliance with the Regulation.

Scenario:
GIVEN that I am an Organization
AND my organization type is Fuel Supplier
AND my role is Signing Authority
AND I have received a Proposal to buy/sell credits from/to another fuel supplier
WHEN I am viewing the requested Credit Transfer Proposal in TFRS
THEN I am able to see the 'Sign 2/2' button (formerly Accept button)

Demo:
Show that Signing Authorities have access to a 'Sign 2/2' button when viewing proposed credit transfers
Show that other roles within the organization do no have access to the 'Sign 2/2' button

Original title of card (for context):
Associate a credit transfer record with the initiating organization and the respondent organization and implement logic to restrict the use of the Accept button

https://trello.com/c/BMNkUGPF/498-credit-transfer-restrict-the-use-of-the-accept-button-to-the-respondent-of-a-buy-sell-type-credit-transaction-3

input transactions to award credits for a "Part 3 Agreement" or to add validated fuel supply credits or to retire credits used for offsets in annual compliance reporting.

retire credits from or adjust a company's credit balance.

enter and submit the information required to propose a credit transaction to a trading partner; accept a proposed trade from a trading partner, and submit and/or recommend that credit transfer to the Director for approval.

TFRS has 4 projects, dev, test, prod and tools. We need to backup the projects and figure out how to restore them in case of emergency.
https://docs.openshift.com/container-platform/3.6/admin_guide/backup_restore.html

Can this be done on an automated schedule?

Story:
As the TFRS PO, I want to ensure that all of our projects are backed up appropriately and regularly so that we can easily and speedily recover from disasters that might affect our uptime and/or productivity.

Demo:
Demonstrate backup process
Show where backups are stored and backup frequencyhttps://trello.com/c/mqT4vQR8/349-backup-backup-tfrs-projects-3

This is a fixed-price opportunity governed by the terms of the BCDevExchange's lightweight procurement model, Code With Us.

Background

The Transportation Fuels Reporting System is the being designed to Streamlined compliance reporting for transportation fuel suppliers in accordance with the Renewable & Low Carbon Fuel Requirements Regulation. We want you to conduct UX Design and Development of the first set of screens which will enable Credit Trading and Compliance Reporting.

Description

You can find our current code base here. We want you to produce layout and design templates with hooks for the developer to write code for. The site should deliver the following functionality:

User Stories

As a trading partner I need to be able to navigate through a series of self-service screens to:

• view information regarding past, proposed and pending credit-related activity including a real-time credit balance and list of activity that may impact that balance.
• enter the information required to propose a credit transaction to a trading partner; accept a proposed trade from a trading partner and submit that transaction proposal to the Director for approval.
• view the information entered by the user on Transaction Details screen before proposing it to a trading partner or submitting it to the Director for approval.
• review before authorizing the transaction and submitting it to the Director for approval or saving it for future.

The Low Carbon Fuels Branch staff need to be able to:

• Input transactions to award Part 3 Agreement or fuel supply credits or adjust balances based on new information to users through the same process as above
• Run queries to produce periodic (quarterly, annually, etc.) reports on credit transaction activity with the following variables: # transfers, total credits traded, avg. market value, min/max value

Stretch goals (time permitting) - As a fuel supplier I need to be able to navigate through a series of self-service screens to:

• Report each fuel that I supplied in BC
• Report each fuel that I transferred as part of a fuel transfer agreement or a notional transfer
• Report that the total volume of fuels supplied is less than 75 million Litres and elect to be exempt

Informational Open House

On Monday, March 7th and 8th, from 12:00-1:00 PM, we will be hosting a drop-in session for interested developers to talk with our team about the work. If you’d like to attend, please email [email protected].

Please also feel free to ask questions via the comments section below.

Acceptance Criteria

To be paid for this opportunity, you will:

1. Participate as a part of our team’s sprint planning workshop from 1:00 PM - 3:00 PM on March 13, 2017 at 1012 Douglas Street in Victoria, BC.
2. Spend a minimum of 2 hours per weekday (Monday - Friday, excluding holidays, between the hours of 8:30 AM and 5:00 PM) working in person with us at our office (1012 Douglas Street in Victoria, BC) for the duration of your work. We want you to work side-by-side with our lead developer and designer to apply the the new theme and deliver the desired functionality in our dev environment.
3. Deliver hi-fidelity screens that are ready for a developer to insert the database connection code for each of the following:

• Main Landing page
• Credit Trading home page
• Credit Trade Transaction details page
• Credit Trade Transaction Summary page
• Credit Trade Transaction Confirmation/Receipt page
• Shadow Box screen for content to collect information

Stretch goals - time permitting:

• Fuel Reporting home page
• Fuel Reporting Submission Details page
• Fuel Reporting Submission Summary page
• Fuel Reporting Submission Confirmation/Receipt page

How to Apply

Submit your proposal by 16:00 PST, Thursday, March 9, 2017.

Proposal Evaluation Criteria

We will evaluate and score the proposals we receive by the following criteria. If we are satisfied with the proposals we receive, we will assign the work by 16:00 PST, Friday, March 10, 2017 with work proposed to commence on Monday, March 13, 2017.

Please email your proposal to [email protected]

Please reference the issue name "Developing the Transportation Fuels Reporting System website front-end (BCDX-MEM-001)" in your email.

With your proposal, you must attach a copy of the Code-with-Us Terms, with the required information asked for in the “Acceptance” section of the Terms inserted into the document (Mandatory).

Scoring criteria:

• Your confirmation of being able to commit the time to meet all of the Acceptance Criteria by March 31, 2017.
• A short (around 200 words or less would be nice) summary of your experience working with agile projects (40 points).
• References to your relevant experience and demonstrated ability to do the work (60 points). For example, a link to your GitHub projects.

Questions?

Please post a comment below.

https://trello.com/c/yDdoFhEx/319-credit-transfer-accept-a-credit-transfer-3