This document proposes moving the requirements document (RD) process from an antiquated email and hard copy system to a digital system using SharePoint for collaboration, tracking RDs through approval processes, and allowing access to historical approved documents. It analyzes options like using the existing SharePoint implementation and DISA cloud storage. The recommendations are to approve funding for a pilot program to develop the new digital process and collaboration portal.

1. Processing Agility for Requirements Document (RD) Dave Clark Five (minus Dave) 24 Sept 2010

2. Antiquated process Email based Hard copy storage Inability to search historical requirements Collaboration is unavailable Tracking or visibility in process difficult Current Situation

3. End user – identifies need Technical user – translates need to technology used to meet need Configuration Manager – recommends specific technology from identified need Subject Matter Experts (SME) – technological expert in field Approvers – validate need at various levels in process Customer/Consumer

4. Creation of standard form and adoption Added capability for electronic signatures Tracking of RD through approval process Collaboration on disapproved documents for resubmission Ability to access historical, approved documents Capability/Challenge/Solution

5. Ability to use current SharePoint implementation in Korea Ability to pull Active Directory user from DAA level for approvals Provided storage within DoD via DISA cloud Solution leverages approved, available applications Givens/Assumptions

6. Collaboration Standardization Tracking of RD Customer Service Searchability Key Requirements

7. Benefits Standardization on single form for submission Capability to track document through process Ability to re-use approved RDs for future purchases (Searchability)Challenges Changing culture to leverage collaboration Training Converting approved RD to searchable document

8. Cloud Reference Model – Private Cloud

9. Cloud Reference Model – Private Cloud

10. Utilize digital signatures in approval process Ensure only authenticated users have access to RDs Security

11. Private Cloud vs Public Cloud Collaboration Tool (SharePoint or current standard) Integrating digital signatures into approval process Options/Architectures Considered

12. Radar Chart Data

13. Radar Chart

14. Privacy – authenticated users Regulatory Compliance – STIGs applied according to DoD policies in place Transparency – only from mil network Certification – DoD based Terminology for Key Performance Metrics Reliability – 80% Durability – backup or replication in place Automation – monthly standard reports; on-demand custom reports Monitoring – Office and personal are in place SLA Considerations

15. Create standardized form Training Develop collaboration portal page DISA cloud storage service Approx $500 / server / month Based on outsourcing impediment Savings seen in time to develop and approve RDs Reporting accuracy Economic Analysis

16. Current situation Serial process Proposed Parallel process – during collaboration Serial process – approval sequence Searchable archives Questions? Conclusions

17. Approve funding for pilot Form 4 ~ 5 person Tiger Team to develop standard form Develop collaboration page Create click by click webpage for approving authorities Converting archived, approved RDs to digital, searchable media (back 3 years) Recommendations

18. Capability to assign priority to RD Future ability to assist contracting in verifying RD completion Ability to change providers for collaboration as more services move from local control to cloud delivery Proposed Strategy

19. Fund pilot Need additional information Disapprove pilot Executive Decision