Task #128
closed
Simulation 6 Integration ServiceNow Platform (Not prioritized as 1 of the 6 simulation)
Added by Doug Fraser over 2 years ago.
Updated over 1 year ago.
Description
Integration with ServiceNow modules procured by Navy that need to be archived in ORE via servicenow API
require ServiceNow modules and API access (security tokens)
Success Criteria-
Design architecture to specify service now modules
simulation and understanding of API' connection to identified service now modules
Action required
Validate service modules Government (engineering) is leveraging so 2 Twelve can work the API definition end points to consume Service now API
Obtain data content from these service Government desires to archive in the ORE beyond the Wiki pages and documents
Need to engage COO & CSBO (Kermit) with Engineering (Brandon & Nick) on the Modules PEO has procured for an API end point for ORE simulation to API. This will aid the PEO in maintaining data neutrality and independence so data of archiving final artifacts/products/configs from desperate environments and hosted on Navy controlled storage and controlled authentication keys that the NDP core node will provide.
- Due date set to 05/31/2023
- Tracker changed from Feature to Task
- Due date changed from 05/31/2023 to 08/02/2023
Other simulation were prioritized above service now integration. However, the ORE as designed with open API standard will just need API endpoint authentication tokens from service now and can consume service endpoint from Service now once the Navy matures on their journey in their consumption of critical service and identifies critical data required for archiving in the ORE for operational resiliency.
- Status changed from New to Closed
- Subject changed from Simulation 6 Integration ServiceNow Platform to Simulation 6 Integration ServiceNow Platform (Not prioritized as 1 of the 6 simulation)
- Due date deleted (
08/02/2023)
Also available in: Atom
PDF