Project

General

Profile

Actions

Task #170

closed

Provide periodic updates to ORE documentation

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

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

100%

Estimated time:

Description

3.2.23 Continuously update relevant documentation to assist with the operation and maintenance of the platform and support to tenant activities.

Actions #1

Updated by Doug Fraser over 2 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Doug Fraser about 2 years ago

  • % Done changed from 70 to 80
Actions #3

Updated by Lloyd Osafo about 2 years ago

  • Due date changed from 12/28/2022 to 05/31/2023
Actions #4

Updated by Christina LaRussa-Martin about 2 years ago

This appears to be a poorly written requirement/feature. Has the government defined "relevant documentation"? What are tenant activities? Does 2Twelve need assistance get getting clarification regarding this requirement?

Actions #5

Updated by Jacob Halle about 2 years ago

This requirement is part of the systems engineering transformation to modernization of moving from paper-based documentation to a more configuration-based documentation for cloud native infrastructure. This requirement focuses on the Triton platform that supports the application of the ORE so users can have a cloud native experience from a consumption perspective. With each update to the ORE requires update to the platform to support new features to ensure that the ORE maintains high availability to stakeholders consuming services. In a cloud native world, the platform updates with version releases, patches, to ensure proper integration with the feature builds that are being implemented in the ORE as part of task 2.
For example, different video formats will require the platform and object storage to be modified to enable faster upload and processing by the user on certain sized videos.
2 Twelve does not need assistance with this feature. We have experienced with cloud native platforms to update and support feature releases.
This requirement has enabled the government to have flexibility for requesting engineering documentation for features outside of the system.

Actions #6

Updated by Jacob Halle almost 2 years ago

  • Tracker changed from Feature to Task
Actions #7

Updated by Jacob Halle almost 2 years ago

  • Due date changed from 05/31/2023 to 08/02/2023
Actions #8

Updated by Jacob Halle almost 2 years ago

  • % Done changed from 80 to 90
Actions #9

Updated by Oscar Robertson almost 2 years ago

Good Afternoon! Brent and I need to understand what "relevant documentation" is being updated. For example, what documents were uploaded that changed the percentile from 80 to 90% complete?

Actions #10

Updated by Jacob Halle almost 2 years ago

This includes updates to all the documentation as we do feature updates such as User Guides, NIST scans, API and architecture documentation, SEISA documentation, CONOPS, Use Cases, process documents, onboarding documents. Also includes what was provided to MR Trajan for AMA and DADMS.

We'd be happy to walk you through any of these specifically on one of our calls.

Actions #11

Updated by Oscar Robertson over 1 year ago

Can Brent and Gerald get an update on what's been done in terms of CONOPS and Use Cases?

Actions #12

Updated by Jacob Halle over 1 year ago

Hi Gerald,
Our understanding was that Government was using input from our BCA and OTA pre production materials to develop a draft CONOPS for our input. However, our BCA has elements of the CONOPS and we can add the Gaps to assist Gov with the CONOPS to tailor it to the organization structure or Modern Service Delivery (MSD). We are also working to draft a visual that will be leveraged as an operational view to support CONOPS.

Please let us know if you need more assistance or if you want 2 Twelve to fill in other gaps. In that case we would need to set up another call to get more information on what the Government would require. We have industry expertise that would enable us to provide useful input on what government needs from an operations/sustainment perspective and the functions that need to be accounted (e.g. managing running code, cloud native applications, etc.)

Actions #13

Updated by Oscar Robertson over 1 year ago

Yes, the government (Brent) has shared the DRAFT CONOPS to 2Twelve for input. Awaiting status.

Actions #14

Updated by Jacob Halle over 1 year ago

Great. We'll plan to discuss some feedback at the meeting today.

Actions #15

Updated by Jacob Halle over 1 year ago

  • % Done changed from 90 to 100
Actions #16

Updated by Jacob Halle over 1 year ago

  • Status changed from In Progress to Closed
Actions

Also available in: Atom PDF