QUESTIONS AND ANSWERS POSED AT PM AESIP & PM GFEBS INDUSTRY DAY 5 APRIL RESPONSES NOTED IN RED.

Transcription

1 QUESTIONS AND ANSWERS POSED AT PM AESIP & PM GFEBS INDUSTRY DAY 5 APRIL RESPONSES NOTED IN RED. AESIP 1. How do you plan to handle the various funding from all the Services at SOCOM? GFEBS already handles inter-service funding 2. CECOM has an established STAMIS SEC support structure. Are there any plans to leverage CECOM SEC for ERP Programs? Yes. The ASSC will take advantage of CECOM as needed. 3. Are there plans to have separate, parallel ERP support structures? What about the establishment of Army ERP support/help desk at the Shared Services Center? The same help desk for the whole enterprise is only good when solution is same (e.g., Windows). This does not work well with different functional solutions but we are consolidating level 2 & 3 helpdesk at ASSC. 4. Which of the AESIP SAP components are slated to migrate to SAP HANA, and what is the timeframe for the migration? LMP is implementing SAP HANA for a small Business Intelligence (BI) capability mostly to see if we can get it to work with DoD security 5. Has AESIP adopted canonical model communication and transformation protocols? Are you using SAP SOA PI, Oracle SOA, etc? We are using SAP MDM and PI at AESIP. The model is standard SAP. It is an all SAP stack. 6. Will GCSS-Army and LMP be required to implement the same auditability controls that GFEBS did? Yes 7. Can the GFEBS controls be reused? We (AESIP, GCSS-Army, LMP, and GFEBS) have a monthly forum where we discuss the status of auditability and preparedness to discuss the end state. We reuse information as much as possible.

2 8. Are all these controls expected to be completely automated? No. the majority are Standard Operating Procedure-like in nature (e.g., What is the acquisition value of the captured Iraqi tank? Do you have an x-ray machine?). 9. Will the Army consider moving current ERP systems to a secure cloud environment to reduce cost? Has the Army done a business case to determine if a cloud environment would be efficient? This is really an Army Data Center Consolidation Plan (ADCCP) question being managed outside of this acquisition. Work at DA continues on where we go next. 10. How can the Army have a viable approach to an Enterprise if HQ AES, TEWLS, IPPS-A and GFEBS are not part of an integrated sustainment approach? They may be eventually but we are starting with a baseline set of systems. They (the named systems in the question) are more different than alike. IPPS-A is where much of the current analysis is being performed and the legacy systems are more of a problem. 11. Will GFEBS and IPPS-A follow the standard processes of the Army SSC? GFEBS - Not at this time. Maybe someday. IPPS-A is not part of the ERP Services acquisition at this time. 12. Will the OBT work also be covered? ASSC does do work for OBT but is using other contracts. We will look at this for inclusion in this acquisition. 13. How will integration among systems be contracted? We will use this contract mechanism. 14. The Army stated ERP policy is to move legacy to ERP. How will Army address the many ERP solutions that will be covered in the future if the contract is AESIP & GFEBS? If they come into the scope of the ERP s they are covered. They will be included in different task orders. 15. What is the accreditation status of ERP and its Components? We are all accredited and have Authority to Operate (ATO s). 16. What significant security challenges remain?

3 Challenges are keeping up with the changes and strong desire for certain technologies (e.g., mobile phones with camera s, GPS locations services, mobile o/s s) 17. Of the systems currently integrated with AESIP, what percentage of overall transactions is routed through AESIP? Probably 70% because of the volume of materiel and requisitions. 18. Of the systems currently integrated with AESIP, does AESIP directly manage (own and maintain) interface control agreements (ICA s) with relative programs? Or, are the ICA s managed by the respective programs/systems? They are essentially contracts between the systems. 19. Does AESIP provide a centralized source for management and/or oversight/guidance for interface control agreements? They are essentially contracts between the systems. If they require data from AESIP, AESIP must be part of the design. 20. It was noted that Business Intelligence (BI) provides detailed visibility of tactical program/system (i.e. GCSS-Army) transactions. Is the BI configuration owned/managed by GFEBS? (or Jointly) Each system has a BI (system/tool). BI s are used for more than reporting. 21. Data Quality and Data Governance are integral to any ERP, including producing auditable reports. Can you speak to the Army s Data Quality struggles and issues and how you plan to address? It did not appear to be incorporated in the recent RFI. Data governance is run by DA CIO/G-6 and has a formal process. The Data Steward for the logistics domain is DA G-4 and AMC LOGSA is the execution arm for much of it. Sustainment services include data quality. 22. Is there any intent to merge all Army ERP systems into one platform or to maintain all systems separately in parallel at the Shared Services Center? No. But we are: Considering a streamlined contracting mechanism. Technically we also are integrating o Common SAN o COOP o Software o Virtualization

4 We are working on a plan for a common security enclave 23. What type of contracts are being planned to support the SSC in Sustaining LMP & GCSS Army? Small Business/Large Business? The market research is currently underway and will determine the strategy. 24. Is GCSS-Army sustainment part of or separate from Army Shared Services? The current plan is to transition sustainment of GCSS Army to the Army SSC. 25. Will there be 3 IDIQ s like AESIP? What are the anticipated IDIQ dollar value(s)? How many awards do you anticipate? The market research is currently underway and will determine the strategy. 26. What is the approximately timeframe the Army is looking for this new contract to be awarded? Quarter 2 Fiscal Year One the Army ERPs going to into sustainment (2017), is the Army going to do the operations and maintenance (O&M) of these systems or will that be contracted out. O&M (sustainment) of the ERPs will be accomplished through a combination of Government and contractor support. Each program is determining its own sustainment strategy, some of which may include leveraging the Army SSC. 28. Is the procurement functionality in LMP or an interface to PADDS? LMP maintains an interface to both PADDS and SPS to support procurement capability. 29. Who are the Small Businesses supporting Army SSC? The list of Small Business contractors are currently listed on the RFI Q&A link. 30. Small Businesses were recently interviewed as part of this process, does this mean that the Army intends to have Small Business set asides? All Small Businesses that responded to the Army ERP Services RFI were given the opportunity to participate in a one-on-one. The market research is currently underway and will determine the strategy.

5 31. Will everyone have access to your slides from today? Yes. All presentations, Q&A s and attendance list will be posted at: AESIP & GFEBS ASSC 32. LMP & GFEBS are Fully Integrated and plans are in process to move operations to Government. Sites, however, are struggling with using the systems for many reasons (Discipline, Consistency of use, Data, Process, and Maturity of Users). What actions are being taken to help user sites to assimilate/conform/mature in system use? (Sites claim AMD & above levels must fund help) At LMP and GFEBS, we are over the major learning issues. There will be ongoing training programs and refreshers. 33. How big is your database? Which database is being used? Do we get a copy of this presentation? GFEBS: Currently 80 Terabytes (TB) with growth to 100 TB over the next 12 months. Oracle database. LMP: LMP Production storage is approximately 98 TB. LMP non production environments (including COOP, QAS, training, etc) is 240 TB (note that the 98 TB that backs up production in the COOP is included in this number). AESIP Hub: Production storage is 16,408 Gigabytes (GB) and non-production is 11,604 GB Yes, you will get a copy. 34. What is the relationship of SAP NS2 and Shared Services Center? The SSC has had a formal partnership with SAP and now NS2 for years to support federal solutions and support the Picatinny Enova system. 35. Why isn t the Army exploring the use of Small Business GWACs and DoD-wide contracts? Market research is currently underway and will help determine the contracting approach. 36. Is the Center of Expertise (COE) limited to only Army ERP? Or are organizations such as SOCOM areas for expansion for the SAP systems? The COE is now titled the Army SSC. Army SSC is not limited to only Army ERPs. The scope of the ERP Services acquisition is the AESIP, GCSS-Army, LMP, and GFEBS requirements. There are other Army requirements that the Army SSC will perform that are outside the coverage of the contract.

6 37. Why Picatinny and not ALTESS (in PEO-EIS)? Picatinny is not the only location of the Army SSC. The Army SSC is a virtual organization and includes CECOM SEC, ARDEC SEC, Redstone NEC and ALTESS today. ALTESS data center capabilities will be used by the Army SSC under a functional support agreement. Picatinny will not be a data center hosting activity. 38. Why are you using Oracle in the lab? Where in the Army is Oracle used? I thought it was all SAP. Oracle is used as a common database in PM AESIP Hub and other ERPs. 39. Does the Army SSC have the physical facilities and resources to support LMP sustainment requirements? The Army SSC is a lead system integrator that will leverage organic and contractor resources across AMC and the Army. Thus the facility requirement will not be totally at one installation. Picatinny is the location of the Army SSC and the ARDEC Software Engineering Center. Picatinny is a large installation that has existing facilities to support the anticipated Government and contract resources. 40. In the configuration management of each SAP system (LMP, AESIP, GCSS-Army) are there separate Solution Management systems being used to manage the development changes, support notifications, or testing? Each ERP program currently has its own approach to configuration management. The AESIP Hub, LMP, GCSS-Army, and LMP all use solution manager and CHARM. 41. If Solution Manager is used, do the different products use CHARM to manage the help desk issues? LMP is currently under transition from CSC. Use of CHARM will be determined as we move forward. 42. What are the major workstreams or areas of focus for the sustainment phase of ERP? For phase 2 of ERP? The initial workstreams for the transition of LMP will be the same as currently performed by CSC. As the Army SSC matures in terms of the LMP operations, these workstreams may be adjusted. The PMO LMP and Army SSC will perform in process reviews among CSC and functional stakeholders to determine workload and workstream priorities. 43. Could you describe the knowledge transfer processes you have been successful in using to migrate programs to sustainment within Army SSC? Prepare cost, schedule, and performance plan that includes: Scope Metrics In process reviews

7 Artifact IV&V (Physical and functional configuration audits) Skills transfer by presentation; document review, and shared-desk work for a set period and time appropriate to the function Joint sign-off by the departing and gaining personnel and project leads that transition is successfully complete 44. Are all current Small Businesses supporting the Army SSC providing their staffing onsite, at Picatinny Arsenal, NJ? The majority of work being executed under the AESIP Small Business contracts is being performed at Picatinny. The virtual nature of the Army SSC allows for mixed staffing depending on program and stakeholder requirements. 45. Is Army SSC s expectation that future contract staff will be on-site at Picatinny? Future work may be performed offsite or at other AMC/Army sites depending upon PM requirements and Army SSC lead system integrator work assignments to non-picatinny organizations. 46. It is understood that transition/sustainment support contracts recently awarded were set-aside for Small Business. Is the Army SSC s expectation that future ERP transition/sustainment support contracts will be set-aside for Small Business and/or 8(a) firms (i.e. SDVOSB)? The market research is currently underway and will determine the strategy. ADDITIONAL ARMY SHARED SERVICE INFORMATION CAN BE FOUND AT: GFEBS 47. Has Army Contract Writing System always been under GFEBS? If not, when did it move over? Deferred until ACWS Brief 48. What lessons learned can you share regarding your Audit Readiness efforts? We implemented the Governance Risk & Compliance (GRC) tool to manage risks and provisioning. Included in this was a structured Segregation of Duties (SOD) policy and process. Had documented internal control processes (e.g., role design and approvals) Brought on independent auditors Added internal controls and documentation at the system administrator level 49. What impact does drawdown have on GFEBS positive? Negative? At this time, it is minimal impact. We are looking for our industry partner to assist us in being proactive in dealing with this

8 and any changes. 50. How does GFEBS and other ERP systems support DISA s JIE (Joint Info Enterprise)? We are looking at using DISA facilities to support the GFEBS-SA effort. 51. There was mention of Audit Readiness for both GFEBS and GCSS-A. Can you state the contractor(s) performing that work for both programs? Also, can you state the corresponding contract vehicle(s)? The contract is currently managed by ASA(FM&C) DASA-FO and the current contractor is IBM. Additional inquiries regarding this contract should be directed to ASA(FM&C) DASA-FO. 52. Why can t you standardize on the interfaces for GFEBS? We have standardized our process and leverage wherever feasible from one interface to another. However, we are dealing with many differing existing systems such as LMP and SPS which have varying infrastructure and design than GFEBS. We are looking for our industry partner to recommend wherever we can make improvements that are more efficient and can result in sustainment savings. 53. What are your lessons learned from GFEBS? Audit readiness as discussed above. Close interaction with our Sponsors, Process Owners and Commands Real-time memory management brought on as needed 54. What best practices will you leverage in the future? Continue to leverage SAP Industry Best Practices, strive for single army solutions within GFEBS, obtain buy-in from our Sponsors and Process Owners. 55. What is preferred contacting vehicle for BI capability? All contracted effort will be under the Single Sustainment Contract as briefed today. Army Contract Writing System (ACWS) 56. Is the Army acquisition strategy considering breaking up solution providers from the system integrator services? We are in the process of conducting market research that will determine acquisition strategy.

9 57. Is there a preference for a solution that is pre-categorized with ERP specifically GFEBS (i.e. SAP based system) or are you open to stand alone non-erp systems? There is no preference at this time. We are in the process of conducting market research that may have an impact on this decision. 58. Is ACWS conducting market research? And if so, how can a company offer a demo of their COTS solution. Yes, we plan to issue RFIs and a sources sought notice. 59. Will you be publishing the results of your AoA? TBD 60. Will you be able to replace SPS by the date set by DoD? The intent is to replace SPS NLT than the prescribed sunset date. 61. What portion of the contract is going to be set aside for small business? Unknown at this time. We are in the process of conducting market research which will determine small business strategy. 62. Is this related to the Army Procurement Execution Program (APEX)? Yes, APEX was the previous name for ACWS. 63. Does the Army has a contract vehicle preference or will this be a full and open competition? We intend to utilize full and open competition. 64. Do you anticipate a significant amount of legacy system data migration requirements to the target system? If yes, would consider separating that work from the system integrator working directly for the data owner? The Government does not currently have a response for this question. 65. Is ACWS fully funded? If so, how much? I could not find a budget line item for it. Where does the budget reside? No. The requirement definition will drive this. 66. Will ACWS be considered a new start? Yes.

10 67. Does the Army anticipate making a product selection prior to issuing an RFP for system integration No. 68. Does the Army have a software preference to meet the ACWS requirement? No. 69. Will you prescribe the technology (software) for this requirement? No. 70. Do you anticipate an extension for SPS? No. 71. Has the Government started meeting software vendors? Yes, for market research purposes. 72. With the current investment in SAP, why not leverage the business application of SAP for ACWS? Federal regulation requires competition for this requirement. 73. When do you think the ACWS RFP will be released and awarded? Anticipated RFP release is early Fiscal Year 14. Award is anticipated for late Fiscal Year The original vision for a tactical contract writing system was in GCSS-Army using DFPS and GCSS-Army SATCOM links. How will GFEBS support MTOE contracts during early phases of deployment (Iraq lessons learned)? All requirements for the contract writing system will be analyzed.