SOLICITATION NOTICE
D -- Army Response Team (ART)
- Notice Date
- 2/3/2012
- Notice Type
- Presolicitation
- NAICS
- 541519
— Other Computer Related Services
- Contracting Office
- ITEC4, NCR PARC (NCR-CC), Directorate of Contracting, 2461 Eisenhower Avenue, Alexandria, VA 22331-0700
- ZIP Code
- 22331-0700
- Solicitation Number
- W91QUZ12R0017
- Response Due
- 5/31/2012
- Archive Date
- 7/30/2012
- Point of Contact
- Alyssa A. Murray, 703-325-2440
- E-Mail Address
-
ITEC4, NCR PARC (NCR-CC)
(alyssa.a.murray.civ@mail.mil)
- Small Business Set-Aside
- Total Small Business
- Description
- This pre-solicitation notice provides advance notice of the issuance of a combined synopsis solicitation, and includes attached draft Performance Work Statement (PWS). The combined synopsis solicitation will be posted on FEDBID (http://www.fedbid.com), not FBO, approximately February 13, 2012. The ACC-NCR point of contacts are Gregory Anderson, gregory.b.anderson.civ@mail.mil and alyssa.a.murray.civ@mail.mil. The "Response Date" of MAY 31, 2012 is archival date only. Performance Based Work Statement Army Response Team (ART) 1Scope This Performance Based Work Statement, (PBWS) defines the requirement for improving IT support, systems and services for the Army's procurement community. The three primary focal points include: the analysis and development of a strategic roadmap for the Information Technology (IT) systems and services supporting the Army's procurement function; the development, implementation and facilitation of a robust IT Governance process incorporating engagement across all stakeholders; and the ongoing deployment, upgrade, and sustainment of the Department of Defense (DoD) Standard Procurement System (SPS), the contract writing software known as Procurement Desktop-Defense (PD ), and its integrations. 2Applicable Documents Federal Acquisition Regulation (FAR) DOD Federal Acquisition Regulation Supplement (DFARS) Army Federal Acquisition Regulation Supplement (AFARS) DoD 5000 series and related major acquisition program policies. Army Regulation 25-2 Army Regulation 25-1 3Program Requirements 3.1Program Management and Control The contractor shall monitor and control program scope through the understanding of the DASA(P) EBSD organization mission, vision, and goals. The contractor shall plan, manage, integrate and control the requirements defined in this PWS and successfully complete the work required. The contractor shall resolve any issues and problems brought to their attention by the Army during the performance of this contract. The contractor shall monitor contract performance and ensure the accurate and timely submission of reports. The contractor shall provide management services for the contract, including the following, at a minimum: 3.1.1Schedule Management The contractor shall develop a comprehensive Work Breakdown Structure (WBS) that outlines the necessary tasks and demonstrates the understanding of each task as it relates to desired program outcomes. The project manager shall identify project milestones, maintain an Integrated Master Schedule (IMS), and report progress against this schedule on a monthly basis. The Work Breakdown Structure (WBS) shall be delivered within 15 days of contract award. The Integrated Master Schedule (IMS) shall be updated and delivered monthly. 3.1.2Risk Management The contractor shall develop a Risk Management Plan, and implement a Risk Assessment Matrix as a method to track and manage program risks. The Risk Management Plan shall include the analysis of likely risks, as well as mitigation strategies and action plans to assist the project should common problems arise. The Risk Assessment Matrix serves as a register where risks are identified, assessed, and prioritized based on the probability of the risk occurring and the potential consequence to the program. Risk assessments shall be conducted on an ongoing basis to ensure the timely application of resources to minimize, monitor, and control the probability and/or impact of unfortunate events or to maximize the realization of opportunities. The Risk Management Plan shall be delivered within 30 days of contract award, and updated as-needed. The Risk Assessment Matrix shall be updated as-needed. 3.1.3Resource Management The contractor ensure proper resources are allocated to successfully complete the work outlined in this PWS, monitor the completion of each task, and provide a detailed Resource Plan that outlines the allocation of resources in support of each task. The Resource Plan shall be updated and delivered monthly. 3.1.4Management Reporting The contractor shall submit weekly Project Status Reports that contain updates on project schedule, identified risks, mitigation strategies, resource constraints, known issues, and open actions. The contractor shall participate in Quarterly Progress Meetings with the Army to review current support requirements, highlight any notable trends or systemic issues, and identify any contract or service level concerns. These meetings will occur at either the Contractor or government facility. Additional meetings may be scheduled as required by either the Army or Contractor. The contractor will assist in producing agenda, which will be exchanged at least three workdays prior to each meeting. Project Status reports shall be delivered weekly. Progress meetings shall be held at least once each quarter, or more often as-needed. 3.2Strategic Planning and Organizational Performance The DASA(P) EBSD provides the necessary tools, techniques and policies for the Army's procurement community. Improving the Information Technology (IT) support, systems and services for this community of contracting professionals is a core mission area for the EBSD. The contractor shall facilitate the development of a DASA(P) EBSD Strategic Plan to refine and focus efforts around core mission areas; in addition, the contractor shall perform an Organizational Assessment to ensure that the necessary resources are allocated to key initiatives, and an Stakeholder Analysis and Communications Plan to more effectively educate others on the role of the DASA(P) in support of the IT systems and services relied on by the Army's procurement function. 3.2.1Army Contracting Strategic Plan for Technology The contractor shall aid in the development of a DASA(P) EBSD Strategic Plan by facilitating strategy sessions with key DASA(P) personnel, recording minutes of sessions, and delivering a Strategic Plan that includes an assessment of current-state IT capabilities (systems and services), and maps a plan/road-map for future technology that aligns with DoD direction. The Strategic Plan shall be delivered within 90 days of contract award, and updated quarterly. 3.2.2Organization Assessment The contractor shall conduct a comprehensive Manpower and Workload Assessment of the DASA (P) EBSD organization to ensure that resources are properly aligned to the mission. The assessment shall identify current strengths and weaknesses of the organizational system (e.g. what is working well and not working so well), in order to identify the necessary future changes and measures of success. Based on the assessment, the contractor shall develop an Organization Design Document that takes into account all People, Process, and Technology impacts. The Organization Design Document should consist of an organization chart that includes key functions/lines, reporting relationships, number of staff, skill-sets required, and span of control. In addition, the Design should not only recommend appropriate staffing levels, but shall contain other resource requirements - such as technology and infrastructure needs. Based on an approved Organization Design Document, the contractor shall provide the recommended Transition Plan to include performance measures and metrics that identifies what a successful organization transition looks like. The Manpower and Workload Assessment shall be delivered within 30 days of contract award. The Organization Design Document shall be delivered within 60 days of contract award. The Transition Plan shall be delivered within 60 days of Design Document approval. 3.2.3Stakeholder Management The contractor shall develop a Stakeholder Management Plan by facilitating sessions with key DASA(P) personnel to conduct a comprehensive stakeholder analysis. The analysis should identify all internal and external stakeholders who shall be impacted or who are interested in the EBSD Strategic Planning effort. Specifically, the analysis shall take into consideration the stakeholder's level of interest, level of support, potential impact on the effort, information needs, and best methods to communicate. The Stakeholder Management Plan shall be delivered within 30 days of contract award, and updated quarterly. 3.2.4Communications Strategy The contractor shall develop a Communications Strategy Plan to engage all identified stakeholders appropriately based on their known communications preferences and information needs. An effective communications strategy provides sufficient information in the right format and at the right time such that the objectives of a project can be affected without surprise or disruption, and yield the most positive outcome or experience possible. The plan shall combine the integration of all available communication tools, avenues, functions and sources in order to maximize the impact on stakeholders. Regardless of communication method, each engagement is important, must have purpose, and must be documented in the plan. The Communications Strategy Plan shall be delivered within 60 days of contract award, and updated quarterly. 3.3Technical and Functional Support for SPS The contractor shall provide information technology/engineering services to support the hardware/software infrastructure of the U.S. Army's SPS operational user community. The Army's acquisition and SPS goals shall be achieved by approximately 8,100 acquisition professionals through the user of the software suite comprised of PD, the PD Adapter, the SPS Legacy Integrations, PRweb, and/or other government (or contractor) owned interfacing processes. The goal is to enable the various Army Commands (ACOMs); Army Service Component Commands (ASCCs); Direct Reporting Units (DRUs); and other Agencies to sustain operational success with PD current and future versions. The contractor shall man and manage a centralized Service Desk operation to include an incident, change, and problem management solution for support issues. Contractor provides initial response to end-user requests for assistance within one hour. An in-depth knowledge of the SPS program is required. This requirement includes the overall implementation and support lifecycle of the system, as well as functional and technical architecture, system administration, and trainer expertise for the Procurement Desktop - Defense (PD2) software. The contractor supporting this effort requires resources capable of diagnosing, troubleshooting and resolving issues across a wide spectrum of technologies including, but not limited to: PD, PRweb, PD Adapter, Sybase ASE, PowerBuilder, webMethods Integration Server, Citrix XenApp, Citrix Provisioning Server, VMware, MS SQL Server, MS Windows Server, and Sun Solaris. In addition, the administration team is expected to run reports as needed using ACBIS, the FPDS-NG site, the EDA site, or other Army or DoD Business Intelligence systems. Each member of the proposed technical administration team will be required to meet the certification requirements in AR 25-1 and AR 25-2. These regulations require personnel with elevated privileges of a government system or network to possess the Security+ certification AND a secondary certification in a relevant technology field (such as the GSLC, GISF, CAP, TIA Net+, A+, Network+, or SSCP certifications). 3.3.1Service Model In order to sustain operational success, the Army requires a comprehensive Service Model - a plan for the efficient delivery and management of shared IT services by improving processes across service providers that support networks, applications, databases and systems. The contractor shall develop an exhaustive IT Support Plan that focuses on the end-user, the Army contracting professional. The contractor shall document the comprehensive list of IT services that are available to the various acquisition professionals, including a description of the service, the agreed upon service levels, how to obtain the service, who is authorized to obtain the service, and escalation procedures in case a service is not adequately being provided. The contractor will perform an analysis of these existing services through service provider interviews and end-user surveys. The contractor will propose methods on improving or streamlining the existing Service Model to include a focus on Help Desk and Support processes and procedures. The contractor shall collect metrics from existing systems and generate a monthly Metrics Report to ensure adequate resources are aligned properly to accommodate both peak and non-peak service levels. The plan shall propose the requirements for a centralized Service Desk operation to include an incident, change, and problem management solution for support issues. The contractor shall also provide support to in the development of Service Level Agreements (SLAs) in support of the holistic Service Model. Agreements that document collaborative business arrangements (through contracts, SLAs, MOUs, etc.) should serve the needs of the Army contracting professional, should be well defined with clear accountability and contain performance-based metrics, when possible. The IT Support Plan shall be delivered within 60 days of contract award. The Metrics Report shall be updated and delivered monthly. 3.3.2SPS-Army Enclave Configuration Management The contractor shall define a comprehensive Configuration Management (CM) process in order to create and maintain a baseline record of all the components of the infrastructure for the purpose of maintaining system integrity and traceability. Infrastructure includes the hardware, software, network appliances, storage, and other components that comprise the SPS-Army system. The contractor shall develop an Architectural System Design Document that documents the baseline infrastructure and Configuration Management Plan that documents the systematic configuration control process when changes to system components are necessary. Within the CM Plan, the contractor shall establish clearly defined roles and responsibilities of all SPS-A service providers - and will document these items in a responsibility assignment (RACI) matrix. The Architectural System Design Document shall be delivered within 30 days of contract award, and updated quarterly. The Configuration Management Plan shall be delivered within 30 days of contract award, and updated quarterly. 3.3.3SPS-Army Enclave Operational Support The contractor shall field an SPS-A System Administration Team that will provide the necessary Functional and Technical support to maintain the day-to-day operations of the systems hosted within the SPS-A Enclaves. Effective provisioning of support requires resources with skill sets capable of diagnosing, troubleshooting and resolving issues across a wide spectrum of technologies including, but not limited to: PD, PRweb, PD Adapter, Sybase ASE, PowerBuilder, webMethods Integration Server, Citrix XenApp, Citrix Provisioning Server, VMware, MS SQL Server, MS Windows Server, and Sun Solaris. The contractor shall provide initial response to end-user requests for assistance within one hour. Each member of the proposed technical administration team will be required to meet the certification requirements in AR 25-1 and AR 25-2. These regulations require personnel with elevated privileges of a government system or network to possess the Security+ certification AND a secondary certification in a relevant technology field (such as the GSLC, GISF, CAP, TIA Net+, A+, Network+, or SSCP certifications). Additional responsibilities include the documentation and execution of SPS-A Operations and Maintenance Standard Operating Procedures, to include: log review/analysis, database consistency checks, database backups/restores, integration upkeep, implementation of SPS Service Releases and Sybase Application upgrades, clause and standard data updates, user maintenance, and other routine tasks. In some cases, duties shall include assisting users with PD -related functional matters and to support changes to the site-specific security model. In addition, the administration team is expected to run reports as needed using ACBIS, the FPDS-NG site, the EDA site, or other Army or DoD Business Intelligence systems. The SPS-A Operations and Maintenance SOP shall be delivered within 15 days of contract award, and updated as-needed. 3.3.4Portal Management The contractor shall conduct an Analysis of Alternatives (AoA) to address the Portal requirements of the SPS-A program. The SPS-A portal should present diverse content and applications to users through a consistent, unified Web-based interface. The contractor shall provide information on various collaboration toolsets and content management systems that are available to be deployed in an Army environment. These tools are critical to the future vision of the program - they enable individuals that are not physically co-located to work together, share information, and leverage contracting knowledge across the globe. In addition, a robust content management system would allow the internal SPS-A Administration team to better support the contracting user community through the use of blogs, wikis, and document publishing. Once a decision is made, the contractor shall implement and maintain the solution based on the recommendations provided to the Government. Technical expertise and support shall be required to manage and curate the content posted to the Army SPS web portal and ensure that project deliverables and work products are available to the general user population. As the content on the portal becomes out dated it shall be changed within 2 working days. The Portal AoA shall be delivered within 30 days of contract award. The Portal Implementation should be completed 90 days after Government decision. 3.3.5Technology Lifecycle Management The contractor shall provide the Government with expert advice for the on-going optimum configuration of the SPS software components within the hosted environments that make up the SPS-Army Consolidated Enclaves. Support is required in determining both current and future hardware, software, and network configurations to support the core PD contract writing software; the PRweb software; and the integration software components. The contractor will develop a Technology Lifecycle Management Plan to account for the technology refresh of the infrastructure within the SPS-Army enclaves. To assure continued supportability throughout its lifecycle, the contractor will conduct an analysis to address issues of capability enhancement, technology vendor roadmaps, and end-of life support issues that may require premature technology refresh requirements. Effective and accurate license management is also essential to include in such a plan. The Technology Lifecycle Management Plan shall be delivered within 90 days of contract award. 3.3.6Continuity of Operations The contractor shall develop a Continuity of Operations Plan (COOP) to provide a repeatable methodology for the successful backup and recovery for all components within the SPS-A enclave. The contractor shall conduct an analysis of the existing COOP and Disaster Recovery (DR) strategy employed by the SPS-A Administration Team, and shall develop a more complete and testable procedure that will align with defined Army COOP guidance and vendor best practices. The contractor shall conduct a test of the COOP with end-user support. The Continuity of Operations Plan shall be delivered within 45 days of contract award. The Continuity of Operations Plan shall be successfully tested within 90 days of contract award, and semi-annually. 3.3.7Information Assurance The contractor shall aid the Government in complying with the Army's Information Assurance (IA) processes and procedures in support of the SPS-A Enclaves. Specifically, the contractor shall provide direct input into the Plan of Action & Milestones (POA&M) template as part of the DoD Information Assurance Certification and Accreditation Process (DIACAP). Input to the Plan of Action & Milestones shall be delivered within 30 days of contract award, and updated quarterly. 3.3.8Performance Management The contractor shall develop a Performance Management Plan to outline the identification, collection, monitoring, and measurement of performance metrics necessary to assess the health of the SPS-A environments. The plan should focus on Reliability, Availability, Maintainability, and Scalability of the systems within the SPS-A enclave, and the optimization of application delivery to the end-user. In order to address Delivery Optimization strategy, the contractor shall look at network optimization (to include the use of WAN optimizers) and software optimization (configuration changes to the baseline). In addition, the Performance Management Plan should collect data from both the data center and the end-point. The Performance Management Plan shall be delivered within 45 days of contract award. 3.3.9 End of Fiscal Year User Support Center The contractor shall establish an End of Fiscal Year User Support Center (EOFYUSC) will be established to support end-of-year contractual operations. While as yet to be determined, the precise period of performance of the EOFYUSC shall be no more than seven (7) calendar days prior to the start of Fiscal Year. The dates and times of EOFYUSC operation will be determined with written notice by the contracting officer. A minimum of one (1) functional analyst and one (1) technical engineer will be on duty in the EOYUSC at all times. The contractor will establish A dedicated phone number for the users to call during this time. During the hours of operation, the EOYUSC staff will perform the following tasks: A daily status report shall be developed that tracks the number of calls received, category with a description of the issue and resolution plan. Daily status reports shall be emailed to the DASA (P), BO&ESD, ABCAS and the Desk Officer. Implementation of the EOYUSC shall be at the discretion of the DASA (P), BO&ESD. 3.3.10 Travel The Contractor may be required travel worldwide to conduct on-site assist visits to help resolve operational issues and provide additional support for system administrators and functional end-users. On-site travel will be required to perform maintenance (other than routine maintenance, which is the responsibility of the site) to the PD software. Travel decisions will be based on an evaluation of the criticality of site's issue(s) and alternatives. Travel by contractor personnel will be at the discretion and direction of the Contracting Officer's Representative (COR) and will be coordinated and approved prior to commencement. Travel will be reimbursed in accordance with the Joint Travel Regulation (JTR). 3.3.11 Conferences and Meetings When required, the Contractor shall participate in conferences. Support at conferences and meetings will include sharing product knowledge, technical and procurement expertise, implementation experience, and an understanding of the Army's business model and SPS deployment objectives. The contractor will be required to take minutes at all meetings attended. The Contractor will engage in teaming with the Army to provide: Data to facilitate strategic decisions (bullet papers, white papers, etc.) Support for key Army briefings, conferences and demonstrations. Periodic metrics of Army issues to include Help Desk trend analysis and action plan development/implementation. 4Period of Performance The contract Period of Performance (PoP) runs 18 months, from April 1, 2012 through September 30, 2013, including base and option period, subject to the Government's option to extend the term of the contract. There will be two-week transition period commencing March 15, 2012. 5Deliverable Schedule The following is a schedule of deliverables that are required in conjunction with the PWS: PWS SectionDeliverableFrequencyDelivery Date 3.1.1Schedule ManagementWork Breakdown Structure Upon AwardWithin 15 days of contract award and maintain the schedule throughout the life of the contract 3.1.1Schedule ManagementIntegrated Master ScheduleMonthlyIn accordance with project plan 3.1.2Risk ManagementRisk Management PlanAs-NeededWithin 30 days of contract award 3.1.2Risk ManagementRisk Assessment MatrixAs-NeededIn accordance with project plan 3.1.3Resource ManagementResource Management Plan MonthlyIn accordance with project plan 3.1.4Management ReportingProject Management Status Reports WeeklyIn accordance with project plan 3.1.4Management ReportingProject Management Progress MeetingsQuarterlyIn accordance with project plan 3.2.1Army Contracting Strategic Plan for TechnologyStrategic Plan QuarterlyWithin 90 days of contract award 3.2.2Organization Assessment Manpower and Workload AssessmentUpon AwardWithin 30 days of contract award and maintain throughout the life of the contract 3.2.2Organization AssessmentOrganization Design DocumentUpon AwardWithin 60 days of contract award and maintain throughout the life of the contract 3.2.2Organization AssessmentTransition PlanUpon ApprovalWithin 60 days of Design Document approval. 3.2.3Stakeholder Management Stakeholder Management Plan QuarterlyWithin 30 days of contract award and maintain throughout the life of the contract 3.2.4Communications Strategy Communications Strategy PlanQuarterlyWithin 60 days of contract award 3.3.1Service Model DescriptionIT Support PlanUpon AwardWithin 60 days of contract award and maintain throughout the life of the contract 3.3.1Service Model DescriptionMetrics ReportMonthlyIn accordance with project plan 3.3.2SPS-Army Enclave Configuration ManagementArchitectural System Design Document QuarterlyWithin 30 days of contract award 3.3.2SPS-Army Enclave Configuration Management Configuration Management Plan QuarterlyWithin 30 days of contract award 3.3.3SPS-Army Enclave Operational Support SPS-A Operations and Maintenance SOP As-NeededWithin 15 days of contract award and maintain throughout the life of the contract 3.3.4Portal ManagementPortal AoA Upon AwardWithin 30 days of contract award 3.3.4Portal ManagementPortal ImplementationUpon DecisionWithin 90 days of contract award 3.3.5Technology Lifecycle ManagementTechnology Lifecycle Management PlanUpon AwardWithin 90 days of contract award and maintain throughout the life of the contract 3.3.6Continuity of OperationsContinuity of Operations Plan Upon AwardWithin 45 days of contract award and maintain throughout the life of the contract 3.3.6Continuity of OperationsContinuity of Operations TestSemi-AnnuallyWithin 90 days of contract award 3.3.7Information AssurancePlan of Action & MilestonesQuarterlyWithin 30 days of contract award and maintain throughout the life of the contract 3.3.8Performance ManagementPerformance Management PlanUpon AwardWithin 45 days of contract award and maintain throughout the life of the contract. Nothing follows.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/notices/92e42c4defa7719886ad55bcb25421ae)
- Place of Performance
- Address: ITEC4, NCR PARC (NCR-CC) Directorate of Contracting, 2461 Eisenhower Avenue Alexandria VA
- Zip Code: 22331-0700
- Record
- SN02667114-W 20120205/120203234013-92e42c4defa7719886ad55bcb25421ae (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |