Project

General

Profile

Actions

Task #199

closed

Deliverable #235: BCA of repository operations

Develop Business Case Analysis

Added by Doug Fraser over 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
10/28/2022
Due date:
08/02/2023
% Done:

100%

Estimated time:

Description

3.3.26 Develop user, governance, and top-level repository services technical documentation, to include use cases, business processes, technical workflow, automation, tenant configurations, which shall align to the PEO Digital offices and portfolio divisions to enable Agile service delivery.

3.3.28 Perform a business analysis of repository operations using a business case analysis (BCA) format. Design the findings into the operating methods of the repository.


Files

Actions #1

Updated by Lloyd Osafo over 2 years ago

  • % Done changed from 0 to 10
Actions #2

Updated by Lloyd Osafo about 2 years ago

  • Due date changed from 05/28/2023 to 06/02/2023
  • % Done changed from 10 to 20
Actions #3

Updated by Lloyd Osafo about 2 years ago

  • Due date changed from 06/02/2023 to 07/31/2023
Actions #4

Updated by Lloyd Osafo about 2 years ago

  • % Done changed from 20 to 30

Construct of the engineering business cases uploaded in the ORE for adopting to PEO Digital new organizational structure

Actions #5

Updated by Tom Eden about 2 years ago

Not sure what "Construct of the engineering business cases uploaded in the ORE for adopting to PEO Digital new organizational structure" means. Recommend we develop a detailed schedule for building this BCA. This is a critical deliverable that needs to be done ASAP so it can inform other work on this task order and shape work in that may be required in a follow-on task order.

Actions #6

Updated by Jacob Halle about 2 years ago

Uploaded screenshot of initial BCA outline for further discussion and population. Once we do internal synch, we can establish a meeting with PM to obtain feedback of any gaps we should include in the BCA, process, and governance taskers.

Actions #7

Updated by Jacob Halle about 2 years ago

Coordinating with COO for knowledge management usage of the ORE. Follow up discussion from our last weekly meeting is for the gov to establish follow on discussion with appropriate stakeholders to refine other use cases from the engineers perspective to solidify and leverage Navy's onboarding process developed and consumable in Service Now to minimize duplication of efforts.

Actions #8

Updated by Christina LaRussa-Martin about 2 years ago

These two requirements need to be further defined (collaboration between 2Twelve and PEO). They are difficult to decipher and therefore a challenge to implement. I'll go back to the team that developed TO#1 for clarification of intent.

Actions #9

Updated by Jacob Halle about 2 years ago

Concur, recommend connecting with Germaine (COO) and Kermit (CSBO).

Actions #10

Updated by Christina LaRussa-Martin about 2 years ago

Will set up a meeting with Germaine, Kermit, and Steve Escobar since TO #1 is funded by Portfolio 3 - Infrastructure Services. These may be moved to a later task order. I'll set something up.

What has been done that this feature is 30% complete?

Actions #11

Updated by Jacob Halle about 2 years ago

Christina Larusso desired agenda from email for biweekly synch - Feb 2

Discuss what a user will expect to see when logging into the ORE. There are several Orchestrated Apps shown, which demonstrates the art of the possible. However, I don’t believe all those capabilities will be available upon release. So for initial fielding, what do we expect to see and when someone selects an option, like “Cloud Native Remote Desktop” what will they find. Let’s walk through it and discuss. This may also help as we develop use cases.

For example: Code Repository:

SANDI team may post here

Bill Huggins and SVT may post test scripts here

Flank Speed may post PowerShell scripts here

Use Case David Bates had provided:

Based on a Ticket, a change is needed to a configuration file.

Need a custom form in ORE for what should change. That information is pushed into NatoBot, which kicks off an automation script to apply requested changes to a device.

Not sure I have the steps correct. Need to review expectations of what the ORE will do.

Question – WHO (function) would make a change such as this? Where would the ticket be stored requesting this change?

Actions #12

Updated by Jacob Halle about 2 years ago

Christina Larusso question: Feature #199 PWS section 3.3.26 and 3.3.28. What has been done from prototype to now? Shows as 70% complete.

Please see attachment of outline previously uploaded that 2 Twelve continues to build the BCA in more detail and will show government when prepared to discuss. We have made progress on the outline to discuss with government whenever the proper stakeholders are available. Please note that this task is marked as 30% (not 70%).

Actions #13

Updated by Jacob Halle about 2 years ago

In regard to David Bates use case of Nautobot integratin with the ORE ("Need to review expectations of what the ORE will do.):

Please see feature implementation of nautobot/netbox attached for additional view of the implementation of the APIs please see attachment of simulation of nautobot in Feature 105.

Questions 2 Twelve needs to understand:
Is the application provisioned and consumable in the core node? If not, when will it be provisioned? 2 Twelve will need the API endpoint to the specific data requested and the tokens to connect as proven in our simulation and screenshot attachment of this product.

Note: the ORE will archive the content, which is predominantly CSV, as shown in the screenshots.

Actions #14

Updated by Jacob Halle almost 2 years ago

  • Status changed from New to In Progress
Actions #15

Updated by William McKelvy almost 2 years ago

Christina, see your message re: TO#1, BCA and need to setup meeting w/ Germaine and Steve. Ready when you are.

Actions #16

Updated by Jacob Halle almost 2 years ago

Actions #17

Updated by Jacob Halle almost 2 years ago

  • Due date changed from 07/31/2023 to 08/02/2023
Actions #18

Updated by Jacob Halle almost 2 years ago

Actions #19

Updated by Jacob Halle almost 2 years ago

  • Parent task set to #235
Actions #20

Updated by Jacob Halle almost 2 years ago

  • Tracker changed from Feature to Task
Actions #21

Updated by Jacob Halle almost 2 years ago

  • % Done changed from 30 to 60
Actions #22

Updated by Oscar Robertson over 1 year ago

This would be an excellent candidate to go over in our weekly meeting to see where we're at. Thanks!

Actions #23

Updated by Jacob Halle over 1 year ago

Sounds good. We provided a draft in April. It would be good to review any feedback and gaps we might not have captured from a Government perspective.

Actions #24

Updated by Oscar Robertson over 1 year ago

Can the government get an update on this task?

Actions #25

Updated by Jacob Halle over 1 year ago

This deliverable is complete. See attached final BCA pdf.

Actions

Also available in: Atom PDF