1. Integration
1.1. Identify which items are not currently captured from business documentation
1.2. Solution to gather additional attributes
1.3. Need to architecture validate future state sources and method for passing data from OSS systems to BP
2. Documentation
2.1. Generate Config
2.1.1. 1.Config Lines with place holder variables
2.1.1.1. Config lines need to be placed in NETCONF format
2.1.2. 3. Define customer specific attributes
2.1.2.1. Current state source
2.1.2.1.1. Review/Config what VPS currently pulls from as source
2.1.2.2. Future state source
2.1.2.3. Mock Ups
2.1.3. 2. Define Sequencing
3. Functionality and Development
3.1. BP pull in data from source systems to generate and apply customer config
3.1.1. Generate
3.1.1.1. Validation
3.1.1.1.1. Make sure all BP needs are present
3.1.1.2. Proper Sequencing to apply config
3.1.1.3. Access to generated CLI config
3.1.1.3.1. Ability to copy and paste
3.1.2. Apply
3.1.2.1. Systematically applied
3.2. We want to set up as components so that we can further develop MAC later on (Not in Scope for TurnKey)
3.3. Error Handling
3.3.1. Config Generation Validation
3.3.1.1. Not all source values are present/formatted
3.3.1.1.1. BP will produce error
3.3.1.1.2. Field Tech will call into data trans
3.3.1.1.3. Data trans will have the ability to update the Configuration parameters in the UI using existing transaction
3.3.1.1.4. Once parameters are updated - config application can be activated from existing transaction
3.3.1.1.5. UI Development:
3.3.2. Config Application
3.3.2.1. Router doesn't accept config line
3.3.2.1.1. BP will produce error
3.3.2.1.2. Field Tech will call into data trans
3.3.2.1.3. Data trans will have the ability to update the Configuration parameters in the UI using existing transaction
3.3.2.1.4. Once parameters are updated - config application can be re- activated from existing transaction
3.3.2.1.5. Development