Mazent Technology

Performance Work Statement (PWS) Parser

Post your entire PWS in the textbox, then hit the parse button. The data will be parsed by 1) Section Numbers (i.e. 3.1.1), 2) Everything after the section number up to the first period or carriage return & 3) All remaining text

3.2.1 Navy Electronic Procurement System (ePS) Navy Electronic Procurement System (ePS) is a Business Category II (BCAT 2) level program that provides the Department of Navy (DoN) contracting workforce with secure agile contract writing and management capabilities in an effort to better support the Warfighter. Navy ePS supports Department initiatives, providing an End-to-End (E2E) process perspective and Better Buying Power (BBP). The system facilitates audit readiness, reduces infrastructure and sustainment costs, and meets 100% of the E2E contract writing and procurement requirements for the DoN Integrated Contracting Environment (DICE). The Navy ePS program will use a third party vendor to develop and integrate the system (System Integrator). The contractor shall provide support at the Echelon II PMO level in multiple disciplines as identified below for the delivery of ePS by the System Integrator. 3.2.1.1 ePS Requirements Analysis and Management The objective of this effort is to identify, assess, analyze, document, trace and verify business, functional, and technical requirements that will drive changes to business processes and system components (e.g., application changes, infrastructure, networks). The contractor shall perform the following activities in support of ePS Requirements Analysis and Management: 3.2.1.1.1 Establish and maintain a process for documenting, analyzing, tracing, prioritizing and obtaining concurrence on requirements, controlling change, and communicating to relevant stakeholders. 3.2.1.1.2 Conduct analysis and documentation activities, using appropriate tools and techniques, to identify and document business, functional, procedural, and technical requirements. 3.2.1.1.3 Ensure, enable, and validate the full traceability of requirements through the analysis, design, build/configure, testing, and release management processes. 3.2.1.1.4 Use industry standard frameworks: Information Technology Infrastructure Library (ITIL), DoD frameworks as proposed by DISA Information Technology Service Management (ITSM) and Lean Six Sigma tools for defining and improving processes. 3.2.1.1.5 Support the ITSM tool by providing a subject matter expert (SME). 3.2.1.2 ePS Application Development Support. The objective of this effort is to conduct activities related to the development and configuration of ePS system application and data components. These services shall be delivered in accordance with common application system development lifecycles (SDLC) methodologies (e.g., Waterfall, Agile, Iterative) which follow leading industry trends, practices, tools and standards. The contractor shall perform the following activities in support of ePS Application Development Support: 3.2.1.2.1 Conduct analysis activities to confirm and document business, functional, procedural, and technical requirements. 3.2.1.2.2 Conduct functional analysis and design activities to support establishment of a functional or business design of the system components while working closely with system users or stakeholder. 3.2.1.2.3 Conduct technical analysis and design activities to support establishment of the technical design of the system to enable effective and efficient system design aligned with the business and functional requirements while working closely with system users or stakeholders, System Integrator and other technical teams. 3.2.1.2.4 Support Waterfall and Agile program management processes by establishing and communicating project/program milestones and by providing support for the iterative process of product delivery for customer feedback and review. 3.2.1.3 ePS Systems Engineering. The contractor shall perform the following activities in support of ePS Systems Engineering: 3.2.1.3.1 Plan, coordinate and perform government and industry defined System Engineering (SE) activities, analysis, assessments and reviews for the purpose of ensuring plans and processes provide clear guidance to Program teams to minimize integration and technical issues. 3.2.1.3.2 Ensure SE processes and disciplines are effectively integrated into Program Operations. 3.2.1.3.3 Support update of SE documentation, artifacts, and plans (e.g., the Systems Engineering Plan (SEP)) to account for acquisition policy changes, engineering planning updates and the progression of the Program in its acquisition lifecycle. 3.2.1.4 ePS Technical Infrastructure Architecture. The Navy is currently undergoing efforts to consolidate and relocate Information Technology (IT) data centers and IT hardware across the Navy enterprise and commercial vendors. This initiative includes the use of Cloud service providers [Platform as a Service (PaaS), Server as a Service (SaaS), Software as a Service (SaaS), and Infrastructure as a Service (IaaS)]. Other vendors or government organizations will provide most actual data center services (Infrastructure or platforms as a service) related to the provisioning, positioning, powering, configuration, and technical administration of storage, processor, and network components under the general architectural-level oversight of the team members providing services. The Contractor shall provide the following services in support of ePS technical hardware and system software infrastructure components: 3.2.1.4.1 Manage the technical infrastructure architecture (e.g., hardware & system software, network and data infrastructure components) ensuring ongoing appropriate levels of capability, capacity, performance, throughput, and availability in accordance with prescribed levels described in the requirements documents and/or technical specifications. 3.2.1.4.2 Support the necessary capacity planning activities to ensure the availability and performance of infrastructure to support software systems and/or networks as workloads change over time. 3.2.1.4.3 Support maintenance of and regularly reconfirm the effectiveness of all technology and processes to ensure the logical and physical integrity of the systems. System integrity assurance, backup, and recovery strategy (CDRL A005) shall be updated annually. 3.2.1.4.4 Support management of the versions of all hardware and software components to ensure that all components are near to current release levels and are covered by standard Original Equipment Manufacturer (OEM) vendor maintenance programs or services. 3.2.1.4.5 Coordinate with the appropriate Information Assurance (IA), Cyber, and data center functions to ensure infrastructure components meet Security Technical Implementation Guide/Information Assurance Vulnerability Alert (STIG/IAVA) compliance and all Information Assurance and Cyber related requirements. 3.2.1.4.6 Manage all DoD related repository requirements related to software, hardware and technical standards to include, but not limited to: DON Application and Database Management System (DADMS), DoD IT Portfolio Repository (DITPR)-DON, Navy Information Dominance Approval System (NAV-IDAS), and DoD Architecture Framework (DODAF). 3.2.1.4.7 Assess systems and new components for adherence to Section 508 compliance. 3.2.1.4.8 Provide for data assurance and data integrity through definition of backup policy and the use of up-to-date backup technologies. 3.2.1.5 ePS Technical Application Configuration The contractor shall provide the following services in support of the technical administration activities necessary for the effective technical design, build, configuration, operation, issue diagnosis and billing of the applicable ePS application software systems: 3.2.1.5.1 Conduct detailed analysis to remediate performance and throughput issues at the system, transaction, data base, and user levels. 3.2.1.5.2 Assess requirements (e.g., development, unit test, system test, production, disaster recovery) to support System Development Life-cycle (SDLC) efforts and general operations. 3.2.1.6 ePS Configuration Management. Configuration Management (CM) consists of systems engineering, control and governance process for establishing and maintaining consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational description throughout its full life-cycle. CM’s primary purpose is to effectively manage, control, and maintain artifacts which describe the system components, their requirements, and interrelationships to enable effective control, ensure quality, and maintain integrity as the system is developed or changes over time. For purposes of this task order, the collection of CM artifacts, documentation, and data will be referred to as the Technical Data Package (TDP). CM related artifacts and processes shall follow appropriate government policy, standards, and directives, and shall align to leading industry practices. Appropriate metrics shall be developed and fully enabled to measure the effectiveness of the CM processes and quality of the CM artifacts. The contractor shall perform the following activities in support of ePS Configuration Management: 3.2.1.6.1 Support establishment and maintenance of the baseline, related components and documentation that aligns with CM leading practices and which defines the system or subsystem architecture, components, and any changes. 3.2.1.6.2 Prepare for and participate in CM audits and reviews. 3.2.1.7 ePS Data Analysis and Data Base Administration. The Contractor shall provide the following services in support of the logical, business, and technical administration activities necessary for the effective technical design, build, configuration, operation, and issue diagnosis of the ePS technical data components (e.g., data analysis and technical data base management services): 3.2.1.7.1 Conduct the business and data analysis and design activities to enable efficient data structures required to support IT applications and general data repositories. 3.2.1.7.2 Execute the analysis, design, build and configuration activities necessary for the initial build and periodic refresh of technical data base and file components (e.g., data bases, table spaces, tables, indices). 3.2.1.7.3 Ensure that adequate logging, backup and recovery processes are available and operational in order to maintain the integrity of all systems’ data in the event of facility, system, or component failure. 3.2.1.7.4 Support configuration, monitoring and maintenance of the data base management system (DBMS) software and other related specialized software to ensure availability, reliability, performance, and integrity of all system data. 3.2.1.7.5 Support continuous monitoring of the data and related application components to detect, diagnose, and resolve performance and functional anomalies. 3.2.1.8 ePS Test, Evaluation, and Quality Assurance. Contractor shall provide the following testing, evaluation, validation, and quality assurance services in support of the regular and ongoing functional and technical changes to ePS applications and system components within the portfolio. This shall include support for full development life-cycle testing (e.g., Unit, System, Integration, Regression), though initial Unit testing is expected to primarily be the responsibility of the system/application development teams. 3.2.1.8.1 Support test events (e.g., major releases, scheduled releases, and non-scheduled releases). 3.2.1.8.2 Support development of manual and automated test scripts, in alignment with functional and technical design specifications, as necessary to ensure the effectiveness and correctness of system changes and to ensure system changes to not break existing system functionality. 3.2.1.8.3 Validate that functional test plans confirm the requirements for the change and are adequate to test the change during a unit, system, or regression test event. 3.2.1.8.4 Document and provide test event metrics (CDRL A006) (e.g., efficiency, timeliness, quality). 3.2.1.8.6 Execute quality assurance processes (e.g., reviews and validation against requirements) as necessary to ensure high quality processes, system components, and documentation are aligned with business, functional and technical requirements. 3.2.1.8.7 Verify system changes align with the business and functional requirements (e.g., requirements traceability) identified in design documentation. 3.2.1.9 ePS Release Management The contractor shall provide Release Management support including software configuration management & version control (CMVC) and the timely and accurate migration of system components through the system landscape instances to production. The contractor shall also provide support of managing the regular, off-cycle or special release or migration of system changes across the non-production environments and then into the production environment. The contractor shall perform the following activities in support of ePS Release Management: 3.2.1.9.1 Manage the systematic process (e.g. planning, scheduling, packaging and releasing) of system and application changes through the development to the production environment using the specific program tools applicable for each environment. 3.2.1.9.2 Review, analyze, and document release failures and monitor corrective actions where required. 3.2.1.9.3 Analyze accepted work items to ensure proper coordination of production release scheduling requirements. 3.2.1.9.4 Monitor the overall release and migration processes, identify metrics, and prepare status reports as necessary. 3.2.1.9.5 Monitor planned work and release items to ensure appropriate quality and completeness prior to preparation for production release. 3.2.1.9.6 Support and lead required board and team meetings in order to provide a controlled method of documenting and approving the movement of changes (e.g., transports), action items and maintenance activities to be conducted in the Quality and Production environments. 3.2.1.9.7 Support development of Release Notes (CDRL A007) for each scheduled release. 3.2.1.10 ePS Technical Program Tools Management. NIWC Atlantic uses and relies on a variety of technical tools (e.g., librarian, repository, testing, debugging, code development) to enable and leverage effective business and technical processes and information. The contractor shall provide support of the technical and functional administration activities required to install, configure and maintain (e.g., administer) the tools based on business, technical, standardization, and process requirements identified by other functions within ES department or end-customer user base. Specific tools include, but are not limited to: IBM Rational Quality Manager, Rational Team Concert, Dynamic Object Oriented Requirements System (DOORS), WorkSoft (testing), SharePoint (data and information repository), Event Tracker (server monitoring). The contractor shall perform the following activities in support of ePS Technical Program Tools Management: 3.2.1.10.1 The contractor shall provide inputs to a monthly Integrated Master Schedule (IMS) (CDRL A008) and support the development of a Contract Work Breakdown Structure (CWBS) (CDRL A009). The IMS shall support the Engineering Team, the A&A Team, and the Transition team. The IMS is intended as a tool for day-to-day tracking of the program/project that rolls up to increasingly higher summary levels of tasks/subtasks. 3.2.1.10.2 Support the technical analysis, design, installation, build and configuration activities (e.g., technical system administration and functional configuration) necessary for the initial build, installation, configuration and periodic refresh of applicable Technical Program tools. 3.2.1.10.3 Provide ongoing assessment of the readiness of the tools (e.g., capacity planning, performance monitoring). 3.2.1.10.4 Assess and manage licensing requirements and compliance of the tools. 3.2.1.10.5 Provide assessment and diagnosis of the tools in the event of issues or processing anomalies; identify requirements and assess new tool options as requested by the COR. 3.2.1.10.6 Coordinate and work with Original Equipment Manufacturer (OEM) and personnel to diagnose and correct technical issues with the tools. 3.2.1.10.7 Ensure ongoing backup capabilities to ensure minimal disruption in the event of tool software or data failure. 3.2.1.11 ePS Risk Management. Effective Risk Management is the execution of processes in order to identify, assess, minimize, and mitigate risks and issues to any aspect, process, or work product of the program/project. The contractor shall follow and incorporate the required program or project’s Risk Management methodology and incorporate the required Government, DoD, DON, and Command mandates. The contractor shall provide the following services in support of ePS Risk Management. 3.2.1.11.1 Support the risk management processes, tools, and documentation requirements in accordance with the Command’s or Program’s Risk Management requirements and plans. 3.2.1.11.2 Administer and implement the Program Risk Management processes, tools and tool improvements, and maintain the risk database. 3.2.1.11.3 Maintain and update risk management plans. 3.2.1.11.4 Provide forecasting and evaluation of project/program risks together with the identification of procedures to avoid or minimize their impact. 3.2.1.11.5 Participate in, conduct, or facilitate periodic monthly Risk Committee and Risk Management board meetings. 3.2.1.12 ePS Training Support. The contractor shall perform the following activities in support of ePS Training Support: 3.2.1.12.1 Provide SMEs to conduct training and support the development of training materials to include tools, applications, technical management processes, and IT skill sets. 3.2.1.12.2 Prepare technical/training inputs to program briefing materials including inputs to Capability Support Plans (CSP), Training Packages, Training Situation Documents (TSD), Training Planning Methodologies (TRPPM), and Naval Training Support Plans (NTSP). 3.2.1.13 ePS Integrated Logistic Support. The contractor shall perform the following activities in support of ePS Integrated Logistic Support: 3.2.1.13.1 Provide Integrated Logistic Support (ILS) subject matter expertise to support ILS processes and documentation updates. 3.2.1.13.2 Participate in required working group meetings, IPT sessions, in-process reviews, and other meetings. 3.2.1.13.3 Assist in the preparation, documentation and maintenance of acquisition strategies, strategic plans, and other formal acquisition, program, or system documentation. 3.2.1.13.4 Provide ILS subject matter expertise in the preparation of materials for the Independent Logistics Assessment (ILA) and provide support at ILA meetings. 3.2.1.14 ePS Cloud Transition Support. As the Navy continues its efforts to consolidate data centers and applications more various commercial and local cloud options are being considered. This item addresses the efforts necessary to assess a component’s viability for cloud hosting, describe the basic technical requirements, estimate costs, and develop an appropriate transition plan and schedule. The contractor shall provide the following support for ePS Cloud Transition: 3.2.1.14.1 Identify, describe, and establish prioritization criteria for cloud hosting requirements and alternatives. 3.2.1.14.2 Working with appropriate cloud service providers, develop basic cost models and prepare the requirements for support within a cloud model. 3.2.1.14.3 Design the high level technical infrastructure model (CDRL A011). 3.2.1.14.4 Develop a Service Design Package (CDRL A012) from requirements and program specifications of a DoD application transitioning into an Impact Level 2 (IL2) or higher DoD cloud environment, indicating all tasks and activities, as well as a reasonable and appropriate schedule for transition efforts. 3.2.1.14.5 Support cloud transition activities related to the re-hosting of applications into a cloud environment. 3.2.1.14.6 Design performance benchmarks and models to assess the technical feasibility of cloud hosting, including performance, throughput, reliability, and availability. 3.2.1.14.7 Support the administrative and financial activities necessary to operate within the cloud and initiate appropriate activities to ensure cost and service levels are met. 3.2.1.14.8 Support modernization and refactoring of a DoD application onto PaaS, SaaS, SaaS and IaaS technologies utilizing approved DoD tools. 3.2.1.14.9 Support development operations in transitioning of a DoD application into the cloud environment leveraging Agile continuous integration and continuous deployment (CI/CD), while developing an effective pipeline that is automated. 3.2.1.15 ePS Enterprise Business Systems Strategy. As the Navy continues its efforts to consolidate data centers and applications significant efforts are underway to assess needs and define a cohesive, effective, and efficient portfolio of integrated business system. The contractor shall provide the following in support of ePS Enterprise Business Systems Strategy: 3.2.1.15.1 Support the identification and assessment of business, processes, and technical requirements for integrated IT systems. 3.2.1.15.2 Align business requirements to or with a Government business strategy. 3.2.1.15.3 Design a targeted or comprehensive business systems architecture model including: data, processes, networks, and systems. 3.2.1.15.4 Support development of high level enterprise/portfolio transition plan and/or deployment plan that is reasonable, technically feasible, and aligned to the business strategy and direction of the enterprise. 3.2.1.15.5 Support development of cost estimates and budget plans appropriate for development, deployment, sustainment, and transition/rationalization of the IT systems and components. 3.2.1.15.6 Identify, describe, and establish prioritization criteria for cloud hosting requirements and alternatives. 3.2.2 Program Management Warfare (PMW) 220 Support. PMW 220 support encompasses all engineering services across the acquisition life cycle. PMW 220 is responsible for the Navy's Business Systems to include Navy Enterprise Resource Planning (NERP), ePS and Standard Labor Data Collection and Distribution Application (SLDCADA). The contractor shall provide the following support for PMW 220 business systems to include Technical Infrastructure Architecture and Cloud Transition Support. 3.2.2.1 PMW 220 Technical Infrastructure Architecture. The Navy is currently undergoing efforts to consolidate and relocate Information Technology (IT) data centers and IT hardware across the Navy enterprise and commercial vendors. This initiative includes the use of Cloud service providers [Platform as a Service (PaaS), Server as a Service (SaaS), Software as a Service (SaaS), and Infrastructure as a Service (IaaS)] support. The contractor shall provide services in support of technical infrastructure architecture design and oversight activities necessary for the effective technical design, build, configuration, operation, monitoring, issue diagnosis and issue resolution of the Production and non-Production systems and infrastructure components of the supported systems. The Contractor shall provide the following services in support of the PMW220 Technical Infrastructure Architecture. 3.2.2.1.1 Complete the necessary capacity planning activities to ensure the availability and performance of infrastructure to support software systems and/or networks as workloads change over time. 3.2.2.1.2 Coordinate with the appropriate IA, Cyber, and data center functions to ensure infrastructure components meet Security Technical Implementation Guide/Information Assurance Vulnerability Alert (STIG/IAVA) compliance and all Information Assurance and Cyber related requirements. 3.2.2.1.3 Prepare and review appropriate System Change or Outage Requests (SCOR) for infrastructure changes to be made by data center and other technical administration personnel. 3.2.2.1.4 Maintain close coordination and high levels of communications with the data center support teams and their managers. 3.2.2.1.5 Support the technical aspects of systems’ interface processing (e.g., middleware) including working with partner organizations to ensure high levels of technical and operational effectiveness for all interfaces. 3.2.2.1.6 Provide for data assurance and data integrity through definition of backup policy and the use of up-to-date backup technologies. 3.2.2.1.7 Support design for full recoverability of all system and application components (e.g., application, hardware, data, network connectivity). 3.2.2.2 PMW 220 Cloud Transition Support. As the Navy continues its efforts to consolidate data centers and applications, various commercial and local cloud options are being considered. This item addresses the efforts necessary to assess a component’s viability for cloud hosting, describe the basic technical requirements, estimate costs, and develop an appropriate transition plan and schedule. The contractor shall provide the following activities to support PMW220 Cloud Transition: 3.2.2.2.1 Identify, describe, and establish prioritization criteria for cloud hosting requirements and alternatives. 3.2.2.2.2 Working with appropriate cloud service providers, develop basic cost models and prepare the requirements for support within a cloud model. 3.2.2.2.3 Design the high level technical infrastructure model (CDRL A011). 3.2.2.2.4 Develop a Service Design Package (CDRL A012) from requirements and program specifications of a DoD application transitioning into an Impact Level 2 (IL2) or higher DoD cloud environment, indicating all tasks and activities, as well as a reasonable and appropriate schedule for transition efforts. 3.2.2.2.5 Design performance benchmarks and models to assess the technical feasibility of cloud hosting, including performance, throughput, reliability, and availability. 3.2.3 Naval Network Warfare Command (NETWARCOM) Cyber Engineering Team (CET). NETWARCOM CET was previously known as the Naval Enterprise Networks System Engineering Team (NENSET). This program under the cognizance of Fleet Readiness Directorate (FRD) 300, has gone through a series of strategic changes that have led to the title change of NENSET to CET. The CET project provides direct support to the NETWARCOM (Commander, Task Force 1010) in its mission to operate and secure Navy Enterprise Networks and communications systems within the Navy’s portion of the DoDIN to deliver warfighting capability to Joint and Naval operations; coordinate and mass Space capabilities in support of Naval operations. In support of the CET mission, NIWC Atlantic provides engineering and technical support services at the strategic, operational, and tactical levels to engineer solutions to the challenges resident within the current Naval Enterprise Networks. The contractor shall support NIWC Atlantic CET directly by providing subject matter experts in the specific functional areas of technical writing and knowledge management. Specifically, the contractor shall provide the following services: 3.2.3.1 Establish and maintain a process for documenting, analyzing, tracing, prioritizing and obtaining concurrence on requirements, controlling change, and communicating to relevant stakeholders. 3.2.3.2 Document, update and maintain plans, reports and requirements (including Test Plans, After Action Reports, PowerPoint Presentations, Spreadsheets, Visio diagrams, Adobe PDF documents, Instructions, Standard Operating Procedures, and technical handbooks).