SECTION C Descriptions and Specifications
C-302 SPECIFICATIONS/PERFORMANCE WORK SCHEDULE
The work under this contract shall be performed in accordance with the following Performance Work Schedule.
CLAUSES INCORPORATED BY FULL TEXT
The contractor shall provide the Command and Control Systems Department (Code 5.3) with the necessary engineering and technical support services in the Modeling and Simulation competency area in support of the following Communities of Interest (COI): Acquisition, Training, Analysis, Planning, Testing and Evaluation, and Experimentation.
SSC-C supports customers and sponsors in the Navy, Department of Defense (DoD), Joint Programs Office, and other Federal Agencies. The Command and Control Department (Code 5.3) provides program management, software development, systems engineering, operational planning, technical expertise, technical support and management in support of SSC-C and its customers. In order to provide these services, knowledge, expertise and experience in M&S policies and practices of M&S that supports Acquisition, Training, Analysis, Planning, Testing and Evaluation, and Experimentation is essential. Specifically, Code 5.3 provides SSC-C customers and sponsors with program knowledge and experience in operation of Command, Control, Communications, Computer, Intelligence, Surveillance, and Reconnaissance (C4ISR) systems: subject matter experts (SME’s) for joint military operations; and, providing simulation operators, engineers, and technical support personnel required to conduct M&S activities. M&S activities include, but are not be limited to, Exercise Support, Verification, Validation and Accreditation (VV&A) activities, Campaign Analysis, Acquisition, Planning, and Training Support.
To keep pace with advances in commercial technology while lowering procurement and life-cycle costs, the government has committed itself to reducing the number of military standards and specifications used in its procurement processes, while relying more on commercial standards and practices. Using the recommended commercial standards and practices, the government will be able to ensure M&S capabilities are provided to the customer in a timely manner.
Work to be performed will be accomplished through issuance of individual task orders. Tasks will specify efforts in one or more of the following technical support areas: Program Management, Systems Engineering, Operational M&S Support, Strategic Planning and Policy Support, and M&S Software Development, M&S IT Support, Logistics, and Training. Executed task statements shall reference one or more technical areas and define the objectives, scope, individual sub-tasks to be accomplished and required deliverables. No work will commence on a task until the task order has been approved and signed by the Government Procuring/Administrative Contracting Officer (PCO/ACO).
2.0 APPLICABLE DOCUMENTS AND REFERENCES
In accordance with the Federal Acquisition Streamlining Act of 1994, all military and government specifications and standards have been eliminated from this PWS, but all work and resulting products shall be accomplished using the most acceptable industry standards and best commercial practices. This does not relieve the contractor from responsibility of meeting these requirements and in fact makes the contractor more liable to provide a quality service and/or product. All work and resulting products shall be accomplished by the contractor using the most acceptable industry standards and commercial practices, unless specified otherwise in the Delivery/Task Order. It is the contractor’s responsibility to meet these requirements and provide quality service and/or products. Unless otherwise specified, the document’s effective date of issue is the date on the request for proposal. Additional applicable documents may be included in specific Delivery/Task Order. Below is a list of suggested specifications, standards and military instructions applicable to this PWS.
IEEE/EIA 12207.1 Software Life Cycle Processes – Life Cycle Data
MIL-HDBK-831 Preparation of Test Reports
NISO-Z39.18Scientific and Technical Reports – Elements, Organization, and Design
ISO 9000 (Series) Quality Management and Quality Assurance Standards
MIL-STD-3022 Verification, Validation and Accreditation Documentation
DOD 5000.59 M&S Management
DOD 5000.61 Verification, Validation, and Accreditation
DOD 5010.12 Procedures for the Acquisition and Management of Technical Data
OPNAVINST Department of the Navy Automatic Data Processing
5239.1A Security Program Instruction
OPNAVINST Department of the Navy M&S Management
SECNAVINST Department of the Navy Modeling and Simulation Program
DI-MSSM-81750 Data Item Description; Department of Defense (DOD) Modeling and Simulation (M&S) Accreditation Plan
DI-MSSM-81751 Data Item Description; Department of Defense (DOD) Modeling and Simulation (M&S) Verification and Validation (V&V) Plan
DI-MSSM-81752 Data Item Description; Department of Defense (DOD) Modeling and Simulation (M&S) Verification and Validation (V&V) Report
DI-MSSM-81753 Data Item Description; Department of Defense (DOD) Modeling and Simulation (M&S) Accreditation Report
3.0 TECHNICAL REQUIREMENTS.
The contractor shall provide support within the parameters specified in each individual Task Order. Executed task orders shall each have their own Performance Work Statement/Objectives that will reference one or more technical areas, which are specified in the following sub-paragraphs.
The contractor shall be able to provide program management support at the sponsor level and at the contract level. Regardless of the level of support, the ultimate objective is ensuring the government’s requirements are met on schedules and within costs.
Program management and other essential personnel must be in place at the time of contract award to preclude delays in on-going projects/programs.
Some programs shall require a contractor to work closely with the government project manager and support the needs of the program at the sponsor level. As directed in task orders, coordination of meetings, preparing budget drills, developing agenda items, attending high-level meetings, generating minutes, and tracking action items may be required. Program support may require significant coordination and interface with various DoD and non-DoD activities located in and out of CONUS.
3.1.2 Contract Administration and Management
The Program Manager (PM), shall work closely with the government Contracting Officer, Contracting Officer’s Representative (COR), and if assigned, the Delivery Order Contracting Officer’s Representative (DOCOR) to coordinate all tasks on this contract. The PM shall be ultimately responsible for ensuring the contract administration is productive and meets all government contracting requirements. The contractor shall be responsible for providing any required support documentation in a timely manner so as to not disrupt the contract award process. To address urgent requirements, the contractor shall have processes established in order to provide all necessary documentation and resources any time during the day in order to facilitate a timely Delivery Order (DO) award or modification. During the life of each task order, the PM shall initiate periodic reviews with the government project engineer. Inadequate contract management support can adversely affect a contractor’s annual performance rating.
Contract Documentation Support
The PM shall be responsible for ensuring that all contract deliverables are tracked and submitted on time throughout the life of contract. The following documents are typical, but not limited to:
Performance Work Statement/Statement of Work
Meeting Agenda and Minutes
Plans of Action and Milestone
Illustrations (using charts and graphs) of manpower planning schedules
Monthly contract and DO status and progress reports (CDRL A001)
Earned Value Management System (EVMS)
The Contractor shall establish, maintain, and use in the performance of this contract, an Earned Value Management System (EVMS) in accordance with ANSI/EIA-748. Although the EVMS is not required to be validated, the Government (COR/DOCOR) will determine the level of EVM compliance on a delivery order basis. The EVMS shall be capable of the following:
Relate resource planning to schedules and technical performance requirements,
Integrate technical performance, cost, schedule, and risk management,
Provide the integrated management information to plan the timely performance of work, budget resources, account for costs, and measure actual performance against the spend plan. The contractor shall be able to sort, report, and account for tasking and expenditures by the assigned tasks. The EVMS shall have the capability to predict, isolate, and identify variances and the factors causing the variances.
The contractor shall developand maintain an Integrated Master Schedule (IMS) (included in the Technical Report CDRL A0018) by logically networking detailed program activities. The schedule shall contain the planned events and milestones, accomplishments, exit criteria, and activities from contract award to the completion of the contract. The contractor shall quantify risk in hours, days, or weeks of delay and provide optimistic, pessimistic, and most likely duration for each IMS activity and event,
The contractor shall engage jointly with the Government’s program manager in Integrated Baseline Reviews (IBRs) to evaluate the risks inherent in the contract’s planned performance measurement baseline. Initially, this shall occur as soon as feasible but not later than six months after contract award, and subsequently, following all major changes to the baseline. Each IBR should verify that the contractor is using a reliable performance measurement baseline, which includes the entire contract scope of work, is consistent with contract schedule requirements, and has adequate resources assigned. Each IBR should also record any indications that effective Earned Value Management (EVM) is not being used. IBRs should also be conducted on subcontracts that meet or exceed the EVM threshold. The prime contractor shall lead the subcontractor IBRs, with active participation by the Government.
3.1.5 Project Management M&S Planning
Project Management M&S Planning tasking includes but is not limited to;
Assist Program Manager in scheduling integration and execution events and delivery deadlines for new functionality;
Preparing equipment shipping
Developing integration test schedules;
Providing recommendations for hardware requirements;
Maintaining document repositories necessary for event preparation, information management and execution;
Preparing status reports and monitor schedules;
Determining contractor staffing requirements for development tasks and execution support, including all direct support for simulation and technical operations, C4ISR, Network, communications, installation, de-installation and support staffs;
Attending related conferences, and meetings.
3.2 Modeling and Simulation Systems Engineering Support:
The contractor shall provide support services for M&S planning, analyses and studies, requirements identification, design, documentation development, test and integration and systems engineering technical support
3.2.1 M&S Concept Planning
The contractor will be required to conceptualize, plan and develop M&S systems in support of DoD objectives. The contractor must have working knowledge of legacy and current simulations and provide leadership in development of future simulations. Tasking includes but is not limited to;
Develop a conceptual model of the system or event
Lead the assessment of command processes through the dynamic use of M&S systems:
Take charge of the process goals that provide the impetus for most experiments;
Lead the “What could be” discussion of electronic technology processes;
Assess future weapon and system development for incorporation in M&S system growth;
Primary knowledge source of leading edge weapon-to-simulation modeling;
Perform Verification and Validation activities on M&S projects including preparing the supporting documentation.
M&S Analysis and Studies
The contractor shall provide support services to conduct engineering studies and analyses, trade studies, technology assessments, and special interest studies. The support shall include but not be limited to the following:
Research and prepare engineering and project management analysis reports
Provide technical analyses of proposals
Make recommendations based on analyses
Identify and evaluate the impact of new and emerging technologies
Conduct data collections and quantitative analyses, evaluations, and simulations
Review and evaluate proposals and performance
Perform technical analyses of investigative case information
Analyze and report on information obtained from various sources and in various formats
Prepare written reports of investigative, technical or analytical findings
Conduct comparison studies of various program elements and cost/benefit studies of proposed or existing functionality of various subsystems and components’
Conduct engineering review and technical evaluations of designs, functional specifications, test specifications, plans; user procedures test results, test reports, and technical reports.
M&S Requirements Identification and Analysis
The contractor shall provide support services to include but not be limited to the following:
Identify, document and prioritize requirements in support of developing the M&S conceptual model
Investigate alternative M&S methods, systems and equipment
Evaluate system configuration and compatibility
Evaluate system and equipment design concepts
Provide recommendations and support to ensure product interfaces are clearly defined
Define data elements, data format, reports, and the connectivity needs between systems
Define the scope of any customizations
Design workflow functionality that allows tracking of data from collection to identify data input requirements, and new or modified software object classes, their attributes, and interactions between object classes, events and methods
Develop data architectures and data acquisition methods
3.2.4 M&S Design
The contractor shall develop C4ISR simulation interfaces to allow the core simulation federation to simulate and to be controlled by real world C4ISR systems. Identify requirements for Simulation-C4ISR system interactions, develop detailed planning for systems interfaces (OSD’s), and identify areas for software improvements. Additional tasks include but are not limited to:
Verification of simulation to C4ISR system integration;
Operation of C4ISR interfaces;
Understanding the operational application of C4ISR systems, including but not limited to, Intelligence support systems, Command and Control Systems, and Targeting systems;
Coordinate with developmental C4ISR systems used to support critical experimental development of doctrine and concepts Systems Integration Requirements;
Coordinate architecture and design of systems capabilities and interfaces, establish and coordinate software development requirements to meet objectives, establish project timelines and set software/hardware configuration and delivery schedules, monitor operations and performance of all applications, lead technical planning meeting and conferences, and conduct other cross-system coordination tasks as required.
M&S Documentation Development
The contractor shall provide technical writing support services to produce technical and user documentation. The support shall include but not be limited to the following:
Develop formal interface documents
Prepare technical documentation for the design, development, integration, test and evaluation, and installation of systems and equipment.
Revise system, subsystem and interface control documents
Develop system documentation, user documentation, technical documentation for tests and evaluations, system test and evaluation plans, test plans, procedures, and reports
Maintain, review and update system documentation
Modify existing documentation to reflect program modifications
M&S Integration, Test and Evaluation
Design and conduct systems integration testing of C4ISR and simulation systems. Identify testing requirements through coordination with various domain experts and systems engineers, develop test schedules and detailed test plans to verify systems performance and interfaces, identify manpower requirements for test events, coordinate administrative details and logistics for test events, direct on-site test events to include conducting daily test coordination meetings, overseeing and monitoring test events, tracking progress and generating daily and post-test event wrap up reports.
The contractor shall provide support services to conduct systems integration testing and to confirm the accuracy, completeness, and conformance of test requirements, test objectives, test plans and schedules. The support shall include but not be limited to the following;
Design and conduct systems integration testing of C4ISR and simulation systems.
Perform system and equipment integration in accordance with documentation, drawing, test plans, and procedures
Develop and integrate hardware and software systems for testing and evaluation
Identify testing requirements through coordination with various domain experts and systems engineers,
Develop test schedules and detailed test plans to verify systems performance and interfaces,
Identify manpower requirements for test events,
Coordinate administrative details and logistics for test events,
Direct on-site test events to include conducting daily test coordination meetings, overseeing and monitoring test events,
Track progress and
Generate daily and post-test event wrap up reports.
Proved test planning inputs, and assist in the planning and connection design for tests
Participate in technical testing in accordance with test procedures and other documentation
Test and monitor system demonstrations, applications, and functional architectures
Develop, test and revise prototypes of programs, techniques and processes
Identify and repair deficiencies found during testing and evaluation that require correction and further testing
Conduct post-implementation review to determine the success of deployments.
M&S Systems Technical Engineering Support
Review technical documentation, specifications, and proposals.
Research specifications and other technical documents
Provide technical assistance with projects and engineering tasks.
Establish and maintain systems and/or integration services.
Support development of unified capabilities.
Provide technical support to develop and deploy systems
Assist in the development of system engineering processes and procedures
Specify, prototype, model, demonstrate and manage systems
Determine measures required to achieve compliance with system requirements
Develop demonstration scenarios for enhancements of prototype systems
Develop system approaches for improvements, installation, maintenance of systems, subsystems, or components.
Evaluate and recommend products and equipment solutions
3.2.8Systems Configuration Support
The contractor shall provide system configuration support for information systems as required for experimentation and/or training event execution. Includes system configuration, hardware management, and network services configuration (email, web, etc.). Tasking includes but is not limited to;
Analysis of hardware/application software requirements and list of required items;
Provide technical support for INFOSEC requirements for experiment, exercise and concept event systems;
Provide detailed hardware/software inventory management, including worldwide shipping capability;
Hardware, system software, and application software configuration and license management for systems, including multiple platform type and multiple operation system (OS) requirements for extensive systems at multiple locations;
The contractor shall be fully qualified in the federation of live, constructive & virtual environments required to support experimentation. Must be proficient in architecture development and able to provide real-time at-sea simulation of live C4ISR systems from simulation centers ashore and afloat, interfacing over satellite networks. The contractor shall provide technical support and subject matter expertise for simulation planning, installation, integration, testing, systems administration and experiment execution. The contractor will provide operators with expertise to both carry out planned scenarios and make adjustments to meet changing operational requirements during exercises. For purposes of the Department of the Navy, the Fleet Synthetic Training Events using JSAF as part of the Navy Continuous Training Environment (NCTE) provides the context for the following training and support requirements. For purposes of the Department of Defense, the Joint National Training Capability (JNTC) provides the context for the following training and support requirements.
3.3.1 Event Execution Support
The contractor shall provide simulation and C4ISR support for execution of Exercises, other M&S experiments and demonstrations (such as I/ITSEC). Taskings include but are not limited to;
Implementation of new models and C4ISR interface capabilities as required;
Software modifications required to support integration of new systems;
Identification, set up, and configuration of simulation and C4ISR interface systems and hardware;
Integration testing, both off site and on site;
Management of equipment transport and inventory;
Network architecture design, implementation, and management;
Manpower planning to support simulation, C4ISR, Communications and Networking systems for operational, experimental and exercises support events;
Close coordination with contractor and government agencies to support procurement, shipment, installation design and actual installation of systems in active ships, submarines and aircraft as required to support event requirements;
The Government anticipates issuing task orders to support up to three major events within a one-year period, with capability to expand, as required to support up to two major events, four laboratory events and possibly 6 “minor” events in a one-year period;
Maintain close liaison with Naval Doctrine, concepts and developmental agencies for development of representation requirements, operational interface, and analysis requirements;
Proven capacity to develop monitoring capability for simulation, C4ISR and communications systems for capture, storage and processing of analytical information for after action analysis.
3.3.2 Event Design Support Requirements
The contractor must have experience in logistics systems and operations for coordination of simulation and logistics C4ISR systems. The contractor shall provide simulation and C4ISR support for event design of Exercises, other M&S experiments and demonstrations. Taskings include but are not limited to;
Coordination and liaison with event leadership to determine the optimum simulation- C4ISR federation to support the event;
Coordination to provide expertise for networking, communications, simulation support, monitoring systems;
Scenario development support, including;
Terrain development required for simulation operations, critical system operations (bathymetric data, hydrographic data);
Terrain detail modeling to support interaction of C4ISR systems and simulation systems, including terrain intensification, development of visual database models for video simulations in support of C4ISR requirements;
Terrain development to support highly detailed modeling of undersea systems to support live/simulation interaction in similar environments;
Scenario Event design and implementation development;
Provide realistic scenario design to support current and future operations, providing realistic stimulation of subject audiences for experiments and exercises.
3.4 Strategic Planning and Policy Support
The contractor shall provide analysis and recommendations in order to define and develop functional IT capabilities and organizational policies and procedures in accordance with Navy, Joint and Federal directives. Contractor shall provide support to SSC-C to ensure strategic alignment of resources and business processes to attain NMSO programmatic goals. Taskings include but are not limited to;
Define strategic business priorities for the SSC-C organization to align with NMSO Vision, Mission and overall Business Strategy;
Prioritize enterprise business transformation initiatives;
Provide support for the development and maintenance of a SPAWARSYSCEN Charleston IT functional infrastructure requirement definition;
Ensure accountability and fact-based decision making via an integrated enterprise Architecture business approach;
Represent stakeholders in a non-voting capacity at the Executive level;
Develop plans, policies and directives; review, analyze and provide recommendations on process, decision points, technical solutions, fielding and migration efforts and schedules, acquisition decisions, funding and programmatic as directed by the Government POC;
Providing M&S plans, policy, procedures, standards and approval of exceptions.
Coordination of Common and Cross Cutting (C&CC) Initiatives between M&S Communities of Interest
Review M&S future requirements to determine and develop courses of actions on broad range of topics
3.5 Modeling & Simulation Software Development and Support
For each software development type delivery order, the contractor shall define a software development approach appropriate for the computer software effort to be performed under the task order. This approach shall be documented in a task order level Software Development Plan (SDP). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort (CDRL A017).
The SDP shall define the offeror’s proposed life cycle model and processes used as a part of that model. In this context, the term “life cycle model” is as defined in IEEE/EIA Std. 12207.0. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of the required task order. In accordance with the framework defined in IEEE/EIA Std. 12207.0, the SDP shall define the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Std. 12207 does not prescribe how to accomplish the task, the offeror must provide this detailed information so the government can assess whether the offeror’s approach is viable.
The SDP shall contain the information defined by IEEE/EIA Std. 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in table 1 of IEEE/EIA Std. 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include, as minimum, specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification.
Knowledge and experience in the software development of Joint Semi-Automated Forces (JSAF) software to support Fleet Synthetic Training Events software is essential.
For purposes of the Department of the Navy, the Fleet Synthetic Training Events using JSAF as part of the Navy Continuous Training Environment (NCTE) provides the context for the following simulation and software development support requirements. For purposes of the Department of Defense, the Joint National Training Capability (JNTC) provides the context for the following training and support requirements.
Provide trained and proficient operators in software simulations. The government desires trained and proficient operators in the Joint Semi Automated Forces (JSAF) software. This support is critical to operate a robust simulation capable of providing enhancements and simulation support for experimentation, demonstrations, and exercises, as required. The contractor shall develop and conduct operations with the Joint Semi-Automated Forces (JSAF) simulation and utilize the federated simulations of the NWDC Core of federated simulations, including associated C4ISR systems. NWDC Core Federated systems include JSAF, the NWDC JSAF C4ISR Interface Device, Multi-Link Tactical Data Link Simulation Trainer (MLST3), GCCS-M, UAVsim, MUSE, AutoSIGs, Land Attack Warfare System, and the necessary HLA to DIS interfaces. Taskings include but are not limited to;
Provide Configuration Management for JSAF simulation software to include revision control, merge support, release management, and release documentation. Maintain bug list and manage change requests.
3.5.2 Software Development
The contractor shall provide support services for the design, development, engineering, installation, testing, analysis and maintenance of software. The contractor shall be required to participate in meetings to determine requirements, define project scope, and review project status. The contractor shall provide software development and engineering services including but not limited to the following;
Prepare a Software Development Plan
Develop, Test and Operate software necessary to support M&S Activities
Develop applications and provide software design support
Provide software support, maintenance and enhancement based on industry standards and best practices
Develop and integrate new software functionality
Develop and modify software to integrate Commercial-Off-The-Shelf (COTS), Government-Off-The-Shelf (GOTS) and legacy systems functionalities
Design and develop software services in accordance with accepted government and industry Service Oriented Architecture (SOA) standards and specifications
Perform detailed requirements analysis;
Develop implementation plan, schedules, and resource requirements. Assign tasks to developers and monitor development and deliverables;
Provide development status reports.
Determine software and integration architecture;
Work with software developers from other projects to merge reusable M&S code and otherwise leverage other development activities;
Assess developer performance, capabilities, and determine training requirements.
Provide Software Development Management
3.6 Modeling and Simulation IT Support
Provide support to the Navy’s M&S Communities to meet their M&S IT and data needs and objectives by enabling M&S interoperability, reuse, and efficiency. This effort will connect common and cross-cutting M&S data across RDA, Analysis, and Training by federating the means to search across existing authoritative data sources and repositories using and conforming to net centric standards. Taskings include but are not limited to those which ensure credibility and confidence with the application of M&S results throughout the Navy and DoD.
The Logistic support will be an integral part to the Modeling and Simulation effort, tracking, and shipping of M&S hardware and equipment for Limited Objective Experiments, Fleet Exercises, Laboratory Integration, and Technical Trade Shows. The Logistic support will include, but is not limited to the following:
Coordinating the shipment and tracking of equipment with government contacting personnel and commercial carriers;
Maintain and update the storage, and when necessary, the replacement of systems;
Coordinate the setup and necessary security for administration of conferences and integration periods held at NWDC and SSC-C;
Inventory maintenance, storage, shipping and receiving, packing and packaging of M&S equipment;
Maintenance of the M&S government property account records and inventory data base management;
Provide recommendations for equipment procurement required to support M&S experiments;
Preparation of equipment for shipment and receiving for M&S related operations, travel to the alternate sites and receipt confirmation and inventory;
Recommendations for M&S hardware and software;
Other logistics activities as required.
The contractor shall design, plan and implement a variety of training scenarios to train individuals in the use of live, constructive & virtual simulations to support M&S experimentation. Taskings include but are not limited to;
Determine training needs of technical staff and recommend training plan. Monitor execution of training plan and perform periodic assessments of staff skill sets;
Develop and conduct training programs, seminars, documentation, tutorials, etc;
Provide and assign mentors and programming coaches;
Determine and set up the necessary hardware to support the training programs for the Training Audience;
Provide both technical assistance and Subject Matter experts to assist in the execution of the required training programs;
Provide, on request, a certification test for individual personnel that determines their ability to operate hardware and software to a given standard.
4.0 QUALITY ASSURANCE
4.1 Quality Assurance Program.
Upon contract award, the Prime contractor shall have and maintain a quality assurance process that meets contract requirements and program objectives while ensuring customer satisfaction and defect-free products/process. The quality system shall be documented and contain procedures, planning, and all other documentation and data necessary to provide an efficient and effective quality system based on their internal auditing system. The quality system shall be made available to the government for review at both a program and worksite services level during predetermined visits. Existing quality documents that meet the requirements of this contract may continue to be used. The Contractor shall also require all subcontractors to possess a quality assurance and control program commensurate with the services and supplies to be provided as determined by the Prime’s internal audit system. The Government reserves the right to disapprove the Contractor’s and/or subcontractor’s quality system or portions thereof when the quality system(s) fails to meet contractual requirements at either the program or worksite services level. The Government reserves the right to participate in the process improvement elements of the contractor’s quality assurance plan as needed. At minimum, the contractor’s quality system shall meet the following key criteria:
Establish capable processes
Monitor and control critical product and process variations
Establish mechanisms for feedback of field product performance
Implement and effective root-cause analysis and corrective action system
Continuous process improvement
4.2 Quality Management Documentation.
In support of the contract’s Quality Assurance Surveillance Plan/Contractor Performance Assessment Reporting System (QASP/CPARS) (see Contract Attachment A), the contractor shall provide the following documents: 10 days after issuance of Task Order: Integrated Master Schedule (CDRL A018); Monthly: Contractor CPARS Draft Approval Document (CDAD) Report (CDRL A019).
4.3 Capability Maturity Model Integration (CMMI).
Task orders shall require the contractor to have processes in place that shall coincide with the government’s quality management processes. As required, the contractor shall use best industry practices including ISO/IEC 15288 for System life cycle processes and ISO/IEC 12207 for Software life cycle processes. The contractor shall provide technical program and project management support that will mitigate the risks to successful program execution including employment of Lean Six Sigma methodologies in compliance with SSCC requirements and with the SSC Engineering Process Office (EPO) Capability Maturity Model Integration (CMMI) program. As part of a team, the contractor shall support projects at SSCC that are currently, or in the process of, being assessed under the SSC EPO CMMI program. The contractor shall be required to utilize the processes and procedures already established for the project and the SSC EPO CMMI program and deliver products that are compliant with the aforementioned processes and procedures.
4.4 Program Reviews.
The contractor shall conduct informal contract status reviews, for each functional task and subject to the approval of the Government, with Government personnel, at a Government designated location (Government Project Office or Contractor’s Facility). The reviews shall be conducted as directed by the Government and shall include as a minimum; cost and schedule control, technical performance, problems and their proposed solutions, and changes in project personnel
The nature of the work required by the proposed contract will require close liaison. Therefore, the contractor’s facility in which the majority of the work under the contract is performed must be located within a 20-mile radius of North Charleston, South Carolina or Norfolk, Virginia. The facility shall accommodate sufficient resident professional staff to provide quick reaction capability to time-sensitive requirements. The facility must have adequate buildings or equipment sufficient for performance of the work required under individual task orders. Supervision, management and administration of the contractor’s present or proposed facility shall be within the geographical location requirement herein.
Contractors located outside the 20-mile radius shall submit a letter of intent to establish a facility within the specified radius. The letter of intent must: (1) state the proposed facility(s) will be available and operational within 30 days after contract award; and (2) describe the geographic location of the proposed facility(s), along with a description of the facility(s) to be offered. The below-listed facilities are required.
No classified storage area will be necessary for this contract.
Security constraints necessary to support integration, test and evaluation functions require that the contractor shall have laboratory space certified by the Defense Investigative Service (DIS) as a “secret closed area” in accordance with DOD 5220.22-M.
Technical and management meetings, reviews, discussions, system evaluations, etc., will be required. These efforts shall be designed by the Contracting Officer’s Representative (COR) or Delivery Order COR or the Contract SSC-C Engineer for the particular task order and may consist of telephone conversations, electronic mail, face-to-face meetings. As directed under the individual task orders, the contractor will be required to provide the necessary meeting facilities to support meetings such as the Operator Advisory Group (OAG), Integrated Product Team (IPT) meetings and those mentioned above.
Some of the individual task orders issued against this contract may require personnel having Top Secret/Special Compartmented Information (TS/SCI) clearances. The requirement for personnel to have a TS/SCI clearance will be made on a case-by-case basis at the government’s request. All KEY personnel performing under this contract must have, or be able to obtain, at least a Secret clearance.
6.0 Travel Requirements.
The contractor shall be required to travel to locations within the Continental limits of the United States (CONUS) as well as sites outside the Continental limits of the United States (OCONUS) both shore and afloat as identified in each individual Delivery/Task Order issued as appropriate. Contractor employees who deploy to locations that require immunizations must do so in accordance with Department of Defense Instruction (DoDI) 6205.4, Department of the Navy (DON), and Space and Naval Warfare Systems Center, Charleston, Instruction (SPAWARSYSCENCHASINST) 12910.1. The contractor shall submit all requests for visitation to the COR for processing at least one week before departing for work site. The work under this contract shall be performed at the following places of performance:
Space and Naval Warfare Systems Center (SPAWARSYSCEN), Charleston, SC.
Navy Warfare Development Command (NWDC), Newport, RI.
Contractor facilities in Charleston, SC, or Norfolk, VA.
Various CONUS and OCONUS locations as required by the specific tasking contained in the delivery order.
7.0 DELIVERABLES AND DOCUMENTATION MEDIA
The contractor shall ensure all deliverables, data, correspondence, etc., are provided in a manner consistent with the spirit and intent of SECNAVINST 5216.5 and Navy Style Manual formats. The data shall be provided on hard copy, and on electronic media such as CD-ROM, 2M or larger USB flash drive or Zip Disk. All data shall be provided in a format that is compatible with SSC-C Charleston corporate standard software configuration and Navy Marine Corps Intranet (NMCI) as specified. Contractor shall conform to SSC-C corporate standards within 30 days of contract award unless otherwise specified. The Contractor is referred to Navy Instructions (e.g. SECNAVINST 5216.5) and Navy Manuals (e.g. Navy Style Manual).
a. Word Processing Microsoft Word
b. Technical Publishing PageMaker/Interleaf/SGML
c. Spreadsheet/Graphs Microsoft Excel
d. Presentations Microsoft PowerPoint
e. Graphics PICT/CGM
f. Scheduling Microsoft Project
g. Drawings - Vector AutoCAD/Visio
h. Geographic Information System (GIS) ArcInfo/ArcView
The contractor shall provide the following documentation deliverables as applicable and as required in the individual delivery orders:
A Plan of Action and Milestones (POA&M) - The POA&M will be updated and reviewed on a regular basis - depending on the proximity to major events (monthly as a minimum). The POA&M will be a coordinated schedule of activities with critical milestones required to conduct M&S support to the M&S event. The schedule should include items such as planning and operational exchange meetings, technical exchange meetings, model development, interface/federate development, integration, and testing scenario development. The content will be in contractor format and will be updated throughout the planning and execution phases. (CDRL A002)
Developed M&S Scenarios for execution during Exercises -- M&S scenarios are derived from operational and planning interchanges for the Exercise correlated with relevant scenarios and Master Scenario Event Lists (MSELs). The M&S Scenario Plan will be a living document through out the life of a Exercise. Based on the flexible and adaptive nature of a Exercise, changes to the scenario prior to and during execution can be expected. The Principle Investigator will provide M&S Scenario Development input to the Exercise Planner. (CDRL A006)
Technical Summary Report -- Inputs for the final Technical Summary Report to include software interfaces to C4ISR systems and other federates, topology of equipment and other hardware interfaces, will be included in this report. Report purpose is to record all relevant elements of the event. The content will be in contract format and delivered within seven working days following an exercise. (CDRL A007)
Schedule of M&S Lab Technical Support and Personnel tasking -This will be a coordinated schedule of activities to include items such as planning and technical exchange meetings, model enhancements, interface/federate development, integration, testing, demonstrations, and experiments. The schedule will continually look ahead one calendar year. The schedule will be updated monthly (No later than the 15th). Long range/large scale projects (outside the 12 month window) may be noted with available details. The content of this report will be in contractor format and will be reviewed at all program management reviews. (CDRL A008)
Trip Reports - Trip reports will contain a detailed description of topics discussed, decisions made, action items assigned, scheduling information, and other related information. The report will be delivered by e-mail three working days following the trips. (CDRL A009)
Software Development - Preparation of Developer and User Documentation for Analysis and Application Software. This product will document the development processes used for a particular application. It allows a third party to understand and follow the build process from beginning to end. Deliverable schedule for this document will be delivered NLT two weeks following the development of a new software product or the enhancement of an existing software product. (CDRL A010)
Periodic Software Releases (Including Release Notes) - This deliverable will archive, with correct documentation, major software releases. Deliverable schedule for this product will be delivered NLT two weeks following a major M&S event (e.g. Fleet Training Exercise, Concept Laboratory Experiments). (CDRL A011)
Software Development Schedule - Lists all milestones and developer activities. The schedule will be projected as far forward as is known or is being planned. The content will be in contractor format or as directed by the tasking. Deliverable schedule for this schedule will be delivered quarterly. It will be included as a separate section of the first semi-monthly report for the months of April, July, October and December. (CDRL A012)
Monthly Software Bug Status Report - This will give insight into and archive current problems being experienced with current software projects. It will allow the tasking lead and the M&S Technical Lead the ability to assign priority to existing bug problems. Deliverable schedule forthis report will be included as a separate section of the second semi-monthly report for each month. (CDRL A013)
System Requirements Specification – For all software developed, the Systems Requirements Specification (SRS) shall provide the traceability matrix for requirements as developed in coordination with stakeholders. Delivery schedule for this product will be NLT two weeks following task order award. (CDRL A014)
System Design Specification – A System Design Specification shall be developed that describes the design considerations, assumptions, constraints, development methods, architecture and subsystem architecture of the system design. The system capabilities, reliability, sustainability and maintainability should be addressed for the intended purpose. The System Design Specification shall be closely coordinated with the SRS to ensure traceability to requirements. The delivery schedule for this product is NLT than two weeks following task order award. (CDRL A015)
Source Code – Code shall be provided upon completion of software development in the media described above. Delivery schedule for this product shall be NLT four weeks following completion of software development. (CDRL A016)
Software Development Plan – For each software development type delivery order, the contractor shall define a software development approach appropriate for the computer software effort to be performed under the task order. This approach shall be documented in a task order level Software Development Plan (SDP). Delivery schedule for this product shall be NLT two weeks following task order award. (CDRL A017)
Technical Miscellaneous Report – a report required at the request of the Government COR to describe status of current issues, problems and plan of action for resolution or presentations. (CDRL A018)
Integrated Master Schedule and Report – a technical report containing cost and schedule data including planned events and milestones, accomplishments, exit criteria, and activities as a continuum from contract award to the completion of the contract. The report shall contain a quantification of risk in hours, days, or weeks of delay and provide optimistic, pessimistic and most likely duration for each IMS activity and event.(CDRL A019)
CPARS Draft Approval Document (CDAD) Monthly Report – a performance monitoring report that provides the contractor input in the form of a self assessment with DOCOR approval or evaluation and COR/PCO adjudication in the event of a disagreement (CDRL A020)
Contract Attachment A
(Attach excel spread sheet file here)