Task #204
closedDeliverable #236: Three government personnel projects within the ORE
Implement up to three government personnel projects in ORE
Added by Doug Fraser over 2 years ago. Updated over 1 year ago.
100%
Description
3.3.29 Implement up to three (3) government personnel projects within the enterprise repository. These projects will be the result of business analysis and prioritized by the Government as the highest three in priority.
Files
ORE automation 20230217.pdf (471 KB) ORE automation 20230217.pdf | Jacob Halle, 07/25/2023 07:46 PM | ||
NSO MDD Docker screenshot.png (202 KB) NSO MDD Docker screenshot.png | Jacob Halle, 07/25/2023 07:46 PM | ||
ORE_NDMS project.pdf (558 KB) ORE_NDMS project.pdf | Jacob Halle, 07/27/2023 04:22 PM |
Updated by Lloyd Osafo over 2 years ago
- Due date changed from 09/28/2023 to 08/03/2023
Updated by Christina LaRussa-Martin about 2 years ago
I am not clear on what is meant by this feature. Need to define government personnel projects and how it is separate from the Proof of Concepts. If 2Twelve is also unclear, I will engage the APEO-E shop for clarification.
Updated by Christina LaRussa-Martin about 2 years ago
Please hold off on starting this feature until we discuss and can obtain clarification.
Updated by Jacob Halle almost 2 years ago
- Due date changed from 08/03/2023 to 08/02/2023
Updated by Jacob Halle almost 2 years ago
- Status changed from New to In Progress
Updated by Oscar Robertson over 1 year ago
Christina LaRussa-Martin wrote in #note-3:
Please hold off on starting this feature until we discuss and can obtain clarification.
What else needs to be discussed?
Updated by Jacob Halle over 1 year ago
We are currently working testing effort with Bill Huggins, but there is 1 more needed.
1) In relation to Knowledge Management:
We have synced the CISCO NSO vendor repository. But there have been some conversations for other knowledge management repositories for syncing (e.g. NDMS hosted by Leidos) to support decommissioning. ORE pointing to CUI object store with advanced cloud native solutions of bring your own encryption key and HSPD12 PIV compliant can now support storing this content for the Gov.
2) We have a follow up with Bill concerning automated testing because right now software testing is done manually. We're obtaining his current process documentation to see where we can implement automation. In addition, the team reviewed NDP SDN test plan and provided feedback which was manually intensive and did not adhere to software defined principles of repeatability.
Per PWS there is one more Gov directed (totaling 3) effort that we can execute once Gov/PEO identifies what that effort is. We can provide input if required on areas that ORE can provide value for these efforts.
Updated by Jacob Halle over 1 year ago
- % Done changed from 30 to 70
First two government projects complete. Jacob to upload final documents.
NDMS ongoing, Jacob will upload engagement email.
Updated by Oscar Robertson over 1 year ago
Can the government get an update on this task?
Updated by Jacob Halle over 1 year ago
- File ORE automation 20230217.pdf ORE automation 20230217.pdf added
- File NSO MDD Docker screenshot.png NSO MDD Docker screenshot.png added
- Status changed from In Progress to Closed
- % Done changed from 70 to 100
See attached screenshots for examples of services for project 1 and 2.
For project 3, NDMS integration:
-Team shared phase plan with Leidos
-System is provisioned and ready to ingest NDMS data
-System is already integrated with CISCO ecosystem (NSO) which is the foundation of identified target future state
So, the ORE is prepared to manage NDMS data once a final decision has been made on backup/replacement.
Therefore, the deliverable on this project from 2 Twelve is complete.
Updated by Jacob Halle over 1 year ago
- File ORE_NDMS project.pdf added
See attached screenshot for NDMS project plan (project #3).
Updated by Jacob Halle over 1 year ago
- File ORE_NDMS project.pdf ORE_NDMS project.pdf added